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 437028 - crash in Evolution: This error seems to appe...
crash in Evolution: This error seems to appe...
Status: RESOLVED DUPLICATE of bug 436788
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-05-08 23:05 UTC by prenna
Modified: 2007-06-11 21:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description prenna 2007-05-08 23:05:22 UTC 
What were you doing when the application crashed?
This error seems to appear every time the "appointment pop-up" wants to appear...


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Free
Icon Theme: gnome

Memory status: size: 74964992 vsize: 74964992 resident: 10334208 share: 8495104 rss: 10334208 rss_rlim: 4294967295
CPU usage: start_time: 1178645965 rtime: 17 utime: 13 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/evolution-alarm-notify'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237395744 (LWP 5105)]
[New Thread -1317016672 (LWP 5125)]
[New Thread -1239446624 (LWP 5109)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 133164

Thread 1 (Thread -1237395744 (LWP 5105))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libpthread.so.0
  • #2 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/libc.so.6
  • #6 abort
    from /lib/i686/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
  • #11 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (7 sec old) ---------------------
Input File     : '/usr/share/amsn/skins/default/sounds/online.wav'
Sample Size    : 16-bit (2 bytes)
Sample Encoding: signed (2's complement)
Channels       : 2
Sample Rate    : 44100
play sox: Error writing: Error writing sample file.  You are probably out of disk space.

Time: 00:00.09 [00:00.72] of 00:00.81 ( 11.4%) Output Buffer:   0.00 play sox: Error writing: Error writing sample file.  You are probably out of disk space.
Done.
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x40
--------------------------------------------------
Comment 1 palfrey 2007-05-09 11:17:28 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 André Klapper 2007-06-11 21:23:26 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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