| Summary: | [abrt] turpial-1.6.6-2.fc16: Process /usr/bin/python was killed by signal 6 (SIGABRT) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | fishears <f1she4rs> | ||||||||||||
| Component: | turpial | Assignee: | Edwind Richzendy Contreras Soto <richzendy> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | richzendy | ||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | i686 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:ea07549e4da2b4b4effbcb362b4fdcf3fcd0f047 | ||||||||||||||
| Fixed In Version: | turpial-1.6.6-3.fc15 | Doc Type: | Bug Fix | ||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2011-12-22 22:50:12 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
fishears
2011-12-01 07:33:07 UTC
Created attachment 538965 [details]
File: dso_list
Created attachment 538966 [details]
File: smolt_data
Created attachment 538967 [details]
File: var_log_messages
Created attachment 538968 [details]
File: maps
Created attachment 538969 [details]
File: backtrace
I'm trying to reproduce this error and I could not, I'm working in to release an update which corrects another bug, I will put you close this bug also automatically, could test it and report back if you have this bug again? turpial-1.6.6-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/turpial-1.6.6-3.fc15 turpial-1.6.6-3.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/turpial-1.6.6-3.fc16 Package turpial-1.6.6-3.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing turpial-1.6.6-3.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16770/turpial-1.6.6-3.fc15 then log in and leave karma (feedback). Sorry its taken a while to get this tested. The bug still exists in turpial-1.6.6-3.fc16 You can install cairomm and cairo-gobject and test again? is very weird this error I already have those packages installed to the latest version. Do you have test versions you want me to install? ask why I did not see in the attached https://bugzilla.redhat.com/attachment.cgi?id=538965, and the only difference libraries cairo between that I have installed and listed in the attachment were those, I was checking on the internet and the same problem has arisen in packages like pidgin or Gwibber, there is little information on how to solve, you have the same versions I have of these libraries, the problem is rare and associated with a place as a bug in cairo (cairo is not dependence to turpial): http://developer.pidgin.im/ticket/13810 and also are the only person who has reported that problem, you can try turpial in debug mode? from the terminal (gnome-terminal) run the following command: turpial-d and copies the output to the comments of this bug, so I can get much more information to make formal report to the developers of turpial results of 'turpial -d'
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
DEBUG:Sound:Started with driver Linux
DEBUG:Gtk:Cargado modo GTK Simple
DEBUG:Services:Iniciado
DEBUG:API:Iniciado
DEBUG:Controller:Iniciando Turpial v1.6.6
DEBUG:Config:CACHEDIR: /home/jb/.cache/turpial/twitter/f1she4rs/images
DEBUG:Config:CONFIGFILE: /home/jb/.config/turpial/twitter/f1she4rs/config
DEBUG:Config:MUTEDFILE: /home/jb/.config/turpial/twitter/f1she4rs/muted
DEBUG:Config:FILTEREDFILE: /home/jb/.config/turpial/twitter/f1she4rs/filtered
DEBUG:Config:Cargando configuración
DEBUG:Config:Loaded user configuration
DEBUG:Config:Leyendo sección Auth
DEBUG:Twitter:Iniciado
DEBUG:TurpialHTTP:No se detectaron proxies en el sistema
DEBUG:API:Iniciando autenticacion segura
DEBUG:TwitterHTTP:Obtain a request token
DEBUG:TwitterHTTP:REQUEST (via headers)
DEBUG:TwitterHTTP:parameters: {'oauth_nonce': '86034649', 'oauth_timestamp': 1323158949, 'oauth_consumer_key': 'j0uEGFlrexq9XE3OuFQBA', 'oauth_signature_method': 'HMAC-SHA1', 'oauth_version': '1.0', 'oauth_signature': 'xXbjEL7+gRlRIMQdKgoJrKZFWbo='}
DEBUG:TwitterHTTP:GOT
DEBUG:TwitterHTTP:key: 8Gop4V2TaYltQXmmPCTquyQ6efQ6ntWc7N8rIBeA
DEBUG:TwitterHTTP:secret: lvmzfWY72PfO2UUaeaaA2UHGWsnJWJ3l1cahrpjn4k
DEBUG:TwitterHTTP:callback confirmed? true
DEBUG:TwitterHTTP:Authorize the request token
DEBUG:TwitterHTTP:REQUEST (via url query string)
DEBUG:TwitterHTTP:parameters: {'oauth_token': '8Gop4V2TaYltQXmmPCTquyQ6efQ6ntWc7N8rIBeA'}
http://api.twitter.com/oauth/authorize?oauth_token=8Gop4V2TaYltQXmmPCTquyQ6efQ6ntWc7N8rIBeA
** Message: console message: http://api.twitter.com/oauth/authorize?oauth_token=8Gop4V2TaYltQXmmPCTquyQ6efQ6ntWc7N8rIBeA @6: Viewport argument value "device-width;" for key "width" not recognized. Content ignored.
** Message: console message: http://api.twitter.com/oauth/authorize?oauth_token=8Gop4V2TaYltQXmmPCTquyQ6efQ6ntWc7N8rIBeA @6: Viewport argument value "1.0;" for key "initial-scale" was truncated to its numeric prefix.
** Message: console message: http://api.twitter.com/oauth/authorize?oauth_token=8Gop4V2TaYltQXmmPCTquyQ6efQ6ntWc7N8rIBeA @6: Viewport argument value "1.0;" for key "maximum-scale" was truncated to its numeric prefix.
(turpial:1757): GnomeShellBrowserPlugin-DEBUG: plugin loaded
ERROR: Invalid browser function table. Some functionality may be restricted.
** (turpial:1757): DEBUG: NP_Initialize
** (turpial:1757): DEBUG: NP_Initialize succeeded
** (turpial:1757): DEBUG: NP_Initialize
** (turpial:1757): DEBUG: NP_Initialize succeeded
** (turpial:1757): DEBUG: NP_Initialize
** (turpial:1757): DEBUG: NP_Initialize succeeded
** (turpial:1757): DEBUG: NP_Initialize
** (turpial:1757): DEBUG: NP_Initialize succeeded
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.4) (fedora-60.1.10.4.fc16-i386)
OpenJDK Client VM (build 20.0-b11, mixed mode)
** Message: console message: https://api.twitter.com/oauth/authorize @6: Viewport argument value "device-width;" for key "width" not recognized. Content ignored.
** Message: console message: https://api.twitter.com/oauth/authorize @6: Viewport argument value "1.0;" for key "initial-scale" was truncated to its numeric prefix.
** Message: console message: https://api.twitter.com/oauth/authorize @6: Viewport argument value "1.0;" for key "maximum-scale" was truncated to its numeric prefix.
python: cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed.
Aborted (core dumped)
turpial-1.6.6-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. I don't understand how this bug can be closed when it still exists in turpial-1.6.6-3.fc16. You say "the problem is rare and associated with a place as a bug in cairo (cairo is not dependence to turpial)"... If you are trying to explain that this is a cairo bug and that turpial does not depend on cairo then why does turpial cause a crash in cairo? All I want to know is how to get this bug fixed. If that means filing a new report with cairo then please tell me to do that. cairo it is only a guess, I'm not really sure why, as I said the error is pretty rare and we could not play, when you're the only one who has reported this error. The bug was closed automatically by the system fedora QA is normally sent to close some bugs when building a new version for users to test the new version and reopen if the bug still persists I've reported this bug upstream developers turpial: http://dev.turpial.org.ve/issues/444 You can do in your terminal: rpm -qa | grep gtk And paste your out here? I have a clue Thank you. The output is here: gtk-vnc2-0.4.3-1.fc15.i686 gtk3-immodule-xim-3.2.2-2.fc16.i686 ibus-gtk3-1.4.0-11.fc16.i686 gtk-murrine-engine-0.98.1.1-2.fc15.i686 PackageKit-gtk-module-0.6.20-1.fc16.i686 spice-gtk3-0.7.39-1.fc16.i686 gtk3-3.2.2-2.fc16.i686 webkitgtk3-1.6.1-1.fc16.i686 gtksourceview3-3.2.3-1.fc16.i686 transmission-gtk-2.42-2.fc16.i686 pygtk2-2.24.0-3.fc15.i686 gnome-python2-gtkspell-2.25.3-37.fc16.i686 libchamplain-gtk-0.12.0-2.fc16.i686 NetworkManager-gtk-0.9.2-1.fc16.i686 libcanberra-gtk2-0.28-3.fc16.i686 gtk-sharp2-2.12.11-1.fc16.i686 libcanberra-gtk3-0.28-3.fc16.i686 adwaita-gtk2-theme-3.2.1-2.fc16.i686 PackageKit-gtk3-module-0.6.20-1.fc16.i686 python-slip-gtk-0.2.17-1.fc16.noarch clutter-gtk-1.0.4-1.fc16.i686 xdg-user-dirs-gtk-0.8-6.fc15.i686 ibus-gtk2-1.4.0-11.fc16.i686 pygtk2-libglade-2.24.0-3.fc15.i686 avahi-ui-gtk3-0.6.30-4.fc16.i686 webkitgtk-1.6.1-1.fc16.i686 gtkmm30-3.2.0-1.fc16.i686 adwaita-gtk3-theme-3.2.1-2.fc16.i686 gtkhtml3-4.2.2-1.fc16.i686 usermode-gtk-1.108-1.fc16.i686 gtk2-immodule-xim-2.24.8-2.fc16.i686 gtk2-engines-2.20.2-2.fc15.i686 pinentry-gtk-0.8.1-4.fc16.i686 gtk-unico-engine-1.0.1-2.fc16.i686 gtkspell-2.0.16-2.fc15.i686 gtk2-2.24.8-2.fc16.i686 pywebkitgtk-1.1.8-1.fc16.i686 libreport-gtk-2.0.7-1.fc16.i686 authconfig-gtk-6.1.16-2.fc16.i686 turpial-1.6.6-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. |