crash in gnome-applet-timer-2.1.2-6.fc12 at hb-open-type-private.hh

[Christoph Wickert]

Forwarded from https://bugzilla.redhat.com/show_bug.cgi?id=566967

abrt 1.0.6 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/lib64/timer-applet/timer-applet
--oaf-activate-iid=OAFIID:TimerApplet_Factory --oaf-ior-fd=24
component: gnome-applet-timer
executable: /usr/bin/python
kernel: 2.6.31.12-174.2.22.fc12.x86_64.debug
package: gnome-applet-timer-2.1.2-6.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Boot computer with loadinit = 3.
2. startx into Gnome.
3. Timer applet failed on X starting

[David (david-redhat-bugs)]

abrt 1.0.6 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/lib64/timer-applet/timer-applet --oaf-activate-iid=OAFIID:TimerApplet_Factory --oaf-ior-fd=24
component: gnome-applet-timer
executable: /usr/bin/python
kernel: 2.6.31.12-174.2.22.fc12.x86_64.debug
package: gnome-applet-timer-2.1.2-6.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Boot computer with loadinit = 3.
2. startx into Gnome.
3. Timer applet failed on X starting

[David (david-redhat-bugs)]

Created attachment 395287
File: backtrace

[Christoph (christoph-redhat-bugs)]

I'm confused. The bug is filed against the timer appler and you say it crashes, but the backtrace contains nothing related to python or the applet.

As which user are you logging in?

[David (david-redhat-bugs)]

I logged in as my usual user without any elevated privileges.

I don't know a whole lot about debugging or programming, but upon reviewing my backtrace I found the following:

Core was generated by `python /usr/lib64/timer-applet/timer-applet --oaf-activate-iid=OAFIID:TimerAppl'.
Program terminated with signal 11, Segmentation fault.

Please let me know anything I can do to help with this.

-Dave

[Christoph (christoph-redhat-bugs)]

I'm afraid not. Your backtrace indicates that python itself crashed but we don't know how the applet managed to crash the interpreter. A python backtrace looks like in bug 567264.

[David (david-redhat-bugs)]

How to reproduce
-----
1. Run computer in Gnome with multiple applications running. Keyboard and Mouse freeze up, but computer is able to shutdown normally when the power button is pressed.
2. Restart computer with loadinit 3
3. startx

Comment
-----
Timer app fails upon Gnome start.

[David (david-redhat-bugs)]

How to reproduce
-----
1. Computer failed to boot past udev for the new kernel
2. Boot into old kernel and reinstall udev
3. Start system with loadinit 3
4. startx

Comment
-----
applet-timer fails upon gnome start.

[Christoph (christoph-redhat-bugs)]

Although I'm still a little puzzled about this report, I forwarded it to the new maintainer at https://bugs.launchpad.net/fedora/+bug/606453

Therefor I'm now closing the bug UPSTREAM because this is where further investigation should take place. Feel free to add yourself to the upstream bug report in order to follow any changes. Even if you don't, will be notified once this bug is resolved in Fedora. If I need more information, I will get back to you.

Thanks for reporting this bug.

[Kenny Meyer (knny-myer)]

The issue is not Timer Applet, there is no such file and according to the back-trace the error seems to be somewhere in the pango library.

I will reassign this to the Pango Bug Tracker.

[Red (red-redhat-bugs)]

Removing external tracker bug with the id 'https://bugzilla.redhat.com/show_bug.cgi?id=566967' as it is not valid for this tracker