After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 551151 - crash in Clock: crash when having two or...
crash in Clock: crash when having two or...
Status: RESOLVED DUPLICATE of bug 546834
Product: gnome-panel
Classification: Other
Component: clock
2.22.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-06 19:42 UTC by louizatakk
Modified: 2008-09-07 13:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description louizatakk 2008-09-06 19:42:36 UTC
Version: 2.22.2

What were you doing when the application crashed?
crash when having two or more tasks in evolution


Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.14-108.fc9.x86_64 #1 SMP Mon Aug 4 13:46:35 EDT 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10499905
Selinux: Permissive
Accessibility: Enabled
GTK+ Theme: Cobra-Blue
Icon Theme: Echo

Memory status: size: 490934272 vsize: 490934272 resident: 21409792 share: 14258176 rss: 21409792 rss_rlim: 18446744073709551615
CPU usage: start_time: 1220728764 rtime: 459 utime: 384 stime: 75 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/clock-applet'

[Thread debugging using libthread_db enabled]
[New Thread 0x7f700befb7f0 (LWP 31250)]
[New Thread 0x41c65950 (LWP 817)]
0x000000386380e86f in __libc_waitpid (pid=<value optimized out>, 
    stat_loc=<value optimized out>, options=<value optimized out>)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);


----------- .xsession-errors ---------------------
Content-Type: application/x-msnmsgrp2p
P2P-Dest: louizatakk@gmail.com
+ >O] xWf;o/Z,9"fhQqz0\'tZHD*io4>>RkiWPQm;NpA\nE\r)$g@lH\rd1l4;BOC7brb6qdA<O|HP%r-+nF%pxXX]O756CB$3[<<N-.k\t(91{\n:!&oo+g%X@EIdQjSF34qP}\r# |\t_P+\neJ5KS\ru-@`,[p=j)Q=QjPV4UE"n _R]yJqy~T"mT6[>)$$)!Tn]
*** Is your sound server running?
*** See: http://www.pulseaudio.org/wiki/Troubleshooting
aplay: main:564: audio open error: Connexion refusée
*** PULSEAUDIO: Unable to connect: Connection refused
*** Is your sound server running?
*** See: http://www.pulseaudio.org/wiki/Troubleshooting
aplay: main:564: audio open error: Connexion refusée
*** PULSEAUDIO: Unable to connect: Connection refused
*** Is your sound server running?
*** See: http://www.pulseaudio.org/wiki/Troubleshooting
aplay: main:564: audio open error: Connexion refusée
--------------------------------------------------
Comment 1 Philip Withnall 2008-09-07 13:05:39 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 546834 ***