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 442801 - crash in Evolution: The desktop was beginnin...
crash in Evolution: The desktop was beginnin...
Status: RESOLVED DUPLICATE of bug 426237
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-06-01 06:46 UTC by b.lewkow
Modified: 2007-06-11 21:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description b.lewkow 2007-06-01 06:46:53 UTC 
What were you doing when the application crashed?
The desktop was beginning... Firefox asked to me if i want to restore previous session... I said yes... and then this message...


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-14mdv #1 SMP Wed May 9 21:11:43 MDT 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: 42999808 vsize: 42999808 resident: 5775360 share: 4689920 rss: 5775360 rss_rlim: 4294967295
CPU usage: start_time: 1180680280 rtime: 6 utime: 5 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/evolution-data-server-1.10'

(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 -1222027584 (LWP 5769)]
[New Thread -1225790560 (LWP 5770)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 137156

Thread 1 (Thread -1222027584 (LWP 5769))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libc.so.6
  • #2 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
    from /lib/i686/libc.so.6
  • #3 system
    from /lib/i686/libc.so.6
  • #4 system
    from /lib/i686/libpthread.so.0
  • #5 ??
  • #6 <signal handler called>
  • #7 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
    from /usr/lib/evolution-data-server-1.2/extensions/libecalbackendfile.so
  • #8 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 _ORBIT_skel_small_Bonobo_Unknown_queryInterface
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #13 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  56
  Minor opcode:  0
  Resource id:  0x0
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  156
  Minor opcode:  6
  Resource id:  0x65
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x8094b60 ): KAccel object already contains an action name "play_pause"
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QColor::setRgb: RGB parameter(s) out of range
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  156
  Minor opcode:  6
  Resource id:  0x65
--------------------------------------------------
Comment 1 palfrey 2007-06-01 13:17:29 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:21:33 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 426237 ***