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 423929 - crash in Panel: Trying to set the mail p...
crash in Panel: Trying to set the mail p...
Status: RESOLVED DUPLICATE of bug 422966
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-28 22:16 UTC by dave
Modified: 2007-07-03 12:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description dave 2007-03-28 22:16:35 UTC
Version: 2.18.0

What were you doing when the application crashed?
Trying to set the mail path (at ~/.maildir) in Evolution with server type "Maildir-format mail directories".  It didn't seem to allow me to pick the directory itself, so I selected the "subscription" files in the directory.


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.0 2007-03-26 (Gentoo)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-gentoo-r3-dkg3 #5 Mon Mar 26 10:39:45 PDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 153788416 vsize: 153788416 resident: 23076864 share: 15155200 rss: 23076864 rss_rlim: 18446744073709551615
CPU usage: start_time: 1175119732 rtime: 274 utime: 262 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46938666591040 (LWP 26728)]
0x00002ab0c10a5ad5 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 46938666591040 (LWP 26728))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #4 g_hash_table_remove
    from /usr/lib/libglib-2.0.so.0
  • #5 ??
    from /usr/lib/libgnome-menu.so.2
  • #6 ??
    from /usr/lib/libgnome-menu.so.2
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (65 sec old) ---------------------
SESSION_MANAGER=local/mab:/tmp/.ICE-unix/26677
(gnome-panel:26728): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 24
Initializing nautilus-open-terminal extension
(process:26772): GStreamer-WARNING **: The GStreamer function gst_init_get_option_group() was
	called, but the GLib threading system has not been initialised
	yet, something that must happen before any other GLib function
	is called. The application needs to be fixed so that it calls
	   if (!g_thread_supported ()) g_thread_init(NULL);
	as very first thing in its main() function. Please file a bug
	against this application.
CalDAV Eplugin starting up ...
** (evolution-2.10:27258): DEBUG: mailto URL command: evolution %s
** (evolution-2.10:27258): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Vincent Untz 2007-03-29 15:40:25 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 Bruno Boaventura 2007-04-29 15:47:43 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Karsten Bräckelmann 2007-07-03 12:23:01 UTC
Thanks for taking the time to report this bug.

This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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