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 434126 - crash in Panel: Nothing on panel but I w...
crash in Panel: Nothing on panel but I w...
Status: RESOLVED DUPLICATE of bug 434074
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-04-28 14:10 UTC by anxare
Modified: 2007-04-28 18:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description anxare 2007-04-28 14:10:21 UTC 
Version: 2.18.1

What were you doing when the application crashed?
Nothing on panel but I was configuring Azureus.


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.1 2007-04-27 (Gentoo)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-gentoo-r1 #1 PREEMPT Fri Mar 9 16:27:56 EET 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 180273152 vsize: 180273152 resident: 23072768 share: 15704064 rss: 23072768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1177768833 rtime: 258 utime: 236 stime: 22 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 46982948345264 (LWP 24037)]
0x00002abb103d8ad5 in waitpid () from /lib/libpthread.so.0

+ Trace 131098

Thread 1 (Thread 46982948345264 (LWP 24037))

  • #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 ??
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_remove
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libgnome-menu.so.2
  • #7 ??
    from /usr/lib/libgnome-menu.so.2
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (60 sec old) ---------------------
open uri = file:///mnt/win_64/back72838B1F.jpg
No running windows found
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:63: error: unexpected identifier `style', expected character `}'
Creating /home/antti/.azureus
Creating /home/antti/.azureus/gentoo.config
/usr/bin/azureus: line 72: /dev/stderr: Lupa evätty
Ikkunointiohjelman varoitus:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400256 (Ohjattu as)
Ikkunointiohjelman varoitus:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Ikkunointiohjelman varoitus:Virheellinen WM_TRANSIENT_FOR ikkuna 0x24001ff kohteelle 0x24004a5 (Azureuksen).
DEBUG::Sat Apr 28 17:08:06 EEST 2007::org.gudy.azureus2.ui.swt.welcome.WelcomeWindow$3::runSupport::268:
    AEThread::run::69
org.gudy.azureus2.plugins.utils.resourcedownloader.ResourceDownloaderException: Error on connect for 'http://web.azureusplatform.com:80/az-web/releasenotes?version=2.5.0.4&locale=fi_FI': 404 Not Found
	at org.gudy.azureus2.pluginsimpl.local.utils.resourcedownloader.ResourceDownloaderURLImpl.download(ResourceDownloaderURLImpl.java:486)
	at org.gudy.azureus2.ui.swt.welcome.WelcomeWindow$3.runSupport(WelcomeWindow.java:257)
	at org.gudy.azureus2.core3.util.AEThread.run(AEThread.java:69)
--------------------------------------------------
Comment 1 palfrey 2007-04-28 18:00:37 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 434074 ***