Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 26400 - gnome-panel segfaulting,
Summary: gnome-panel segfaulting,
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-11 07:23 UTC by Mark Chappell
Modified: 2003-08-18 05:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Chappell 2003-08-11 07:23:32 UTC
Due to running out of disk space recently one of the entries in my gnome-panel
bar, (/home/ee0mdc/.gnome2/panel2.d/default/launchers/larry-00214be04e.desktop)
became emtpy, without me noticing.  When restarting gnome, gnome-panel would
segfault, as me to submit a bug report, then when I clicked on the button to
kill gnome-panel, it would attempt to restart gnome-panel, and segfault again. 
I tracked it down to the aforementioned file, deleted it, and gnome-panel is now
working again.

I'm not sure what modifications, patches, etc. have been applied by the gentoo
team so it seems sensible to post the bug here, then try and find where to post
wrt the gnome site, if you think that's best.

*  gnome-base/gnome-panel
      Latest version available: 2.2.2.2
      Latest version installed: 2.2.2.2
      Size of downloaded files: 2,618 kB
      Homepage:    http://www.gnome.org/
      Description: The Panel for Gnome2
Comment 1 Mike Gardiner (RETIRED) gentoo-dev 2003-08-16 03:23:06 UTC
please have a look at bug 26400 and see if downgrading to gtk+2.2.1 fixes the problem. you really need to be able to reproduce the problem for us to help you fix the bug as well.
Comment 2 Josh Chaney 2003-08-17 13:24:14 UTC
make[5]: Entering directory `/var/tmp/portage/gnome-panel-2.2.2.2-r30/work/gnome-panel-2.2.2.2/help/C/fish'
/bin/sh ../../../mkinstalldirs /var/tmp/portage/gnome-panel-2.2.2.2-r30/image//usr/share/omf/gnome-panel
for file in fish-applet-2-C.omf; do \
        /bin/install -c -m 644 $file.out /var/tmp/portage/gnome-panel-2.2.2.2-r30/image//usr/share/omf/gnome-panel/$file; \
done
/bin/install: cannot stat `fish-applet-2-C.omf.out': No such file or directory
make[5]: *** [install-data-hook-omf] Error 1
make[5]: Leaving directory `/var/tmp/portage/gnome-panel-2.2.2.2-r30/work/gnome-panel-2.2.2.2/help/C/fish'
make[4]: *** [install-data-am] Error 2
Comment 3 Mike Gardiner (RETIRED) gentoo-dev 2003-08-18 00:11:02 UTC
before posting a comment please consider the following:

a) whether what you are posting is even remotely related to the bug topic (in this case i can't see that it is)
b) that you provide some explanation of your problem
c) that you provide us with some information about your system (emerge info is usually a good start)

i have no idea why you've just tacked this on here, and why do you have gnome-panel-2.2.2.2-r30 ? the latest i see in portage is gnome-panel-2.2.2.2
Comment 4 foser (RETIRED) gentoo-dev 2003-08-18 05:29:01 UTC
reporter, an apps response to random input (cause that is what it is) is never given. It just expect things to be there. I don't see what we can do here. You could argue that panel could be made more robust, but it probably isn't worth tracking this odd one out bug (which could be very timeconsuming) vs. the allover health of the project. So thats why i'm closing this bug, thanks for the report anyway.

Obz, not every bug can be tracked down to gtk+-2.2.2 ;) It's quite obvious here that the reporter found the cause and properly handled the problem, the question is what are we able to do with it (not much in this case).

Josh is probably one of the people who likes to break his gentoo install with unsupported extras provided via certain sites. I assume here it is probably the xd2 package. Josh, please take your bugs there and not to us, we do not support those efforts in any way officially. Though i must say it looks like another bug, which seems to be hardware related (you can use the search for that one on here).