Bug 98646 - gnome-panel 2.10.2 'already running'
|
Bug#:
98646
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: gnome@gentoo.org
|
Reported By: bzdurqa@wp.pl
|
|
Component: GNOME
|
|
|
URL:
|
|
Summary: gnome-panel 2.10.2 'already running'
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-07-11 03:59 0000
|
Of course one needs to revert the patch from Fedora, so I attached proper one
;)
Patch works for me. Thanks! IMHO this patch needs to be included ASAP.
smproxy has been removed in gnome-session-2.10.0-r3, which should resolve this
bug. Thanks for reporting this issue.
*** Bug 100561 has been marked as a duplicate of this bug. ***
*** Bug 104007 has been marked as a duplicate of this bug. ***
(In reply to comment #6)
> *** Bug 104007 has been marked as a duplicate of this bug. ***
This bug dates to July, but there's no new version in the portage tree
(In reply to comment #7)
> (In reply to comment #6)
> > *** Bug 104007 has been marked as a duplicate of this bug. ***
>
> This bug dates to July, but there's no new version in the portage tree
>
The bug is fixed. At least in gnome-panel-2.10.2 it is.
(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #6)
> > > *** Bug 104007 has been marked as a duplicate of this bug. ***
> >
> > This bug dates to July, but there's no new version in the portage tree
> >
> The bug is fixed. At least in gnome-panel-2.10.2 it is.
>
The bug is not fixed. Not in gnome-panel-2.10.2. The problem happened
after I updated gnome-panel to 2.10.2. The source is not patched. Neither
'panel-session.c' nor 'main.c'. There's no reference to any patch on 2.10.2
ebuild. Reemerging doens't fix the problem. The bug is not fixed.
Henrique,
This is not a bug in gnome-panel, it's a problem with gnome-session, which is
resolved in gnome-session-2.10.0-r3, as stated on comment #4.
(In reply to comment #10)
> Henrique,
> This is not a bug in gnome-panel, it's a problem with gnome-session, which is
> resolved in gnome-session-2.10.0-r3, as stated on comment #4.
Ok. But gnome-session-2.10.0-r3 is still on testing.