GNOME Bugzilla – Bug 87681
endless panel restart loop when there's already a panel running
Last modified: 2020-11-06 20:24:08 UTC
if there's already a panel registered with bonobo-activation, the panel will pop up a dialog saying so, and then it exits. however, it has told the SM to restart itself... so the SM restarts it and itpops up the dialog again. this will go on forever. the panel should pop up a dialog with 2 buttons... and then tell the Sm not to restart it...
Jacob: the checking for another panel happens before before setting the restart style, so this shouldn't happen - and I can't reproduce it.
doesn't the SM remember/think it's a restart still? i still get this from time to time... so i'd think it should be needinfo
Okay, marking as NEEDINFO. As you said Jacob, the SM might remember the restart style and apply it. I thought so to, that's why I tested it. Didn't seem to happen for me ... In any case it would be a gnome-session bug if it did do that.
Jacob: can you still reproduce ? Here, I can't reproduce.
I had the same problem here. Mark : what information can I provide ?
What exactly did you do to trigger the bug? If I have a panel running and start another panel from the command line I get the dialog and then the panel exits - the panel doesn't get re-spawned ...
I just saved my session. The next time I logged in, there were two panels which were launched. In the "current session" tab of the session properties, I could see that these were "gnome-panel" and "gnome-panel --sm-config-prefix /gnome-panel-something/". I removed the first one and it works perfectly now.
You saved your session while the dialog was open or ... ?
Sorry, I should have said that. No, IIRC, it was when I logged out.
So, what happened here is that somehow two gnome-panel entries got saved into your session. I'm trying to understand where the second entry came from. Any idea what you did to cause this to happen ?
Absolutely no idea. Mmmmhhhh... It's possible that I compiled and installed HEAD, then did 'killall gnome-panel' and launched gnome-panel. Not sure. I'll try to reproduce the bug.
Thanks ... I'll mark it as NEEDINFO again in the mean time :-)))
How funny. I thought I solved the problem. I just logged out and logged in (without saving the session) and I have the problem right now. Mmmmhhhh... Mark, do you want me to try to remove the "gnome-panel --sm-config-path ..." from the session and to try to reproduce the bug by saving a new session or do you want to study my case right now ? Note that I'll go home soon, so you may have the answers to your questions only tomorrow.
(There's no rush on this - anytime that suits you) If there are two gnome-panel entries in your session file with RestartStyleHint=2, then this behaviour is to be expected. So what I need to know is how to get into that situation in the first place - i.e. a reproducable test case, starting with no saved session (just copy your session file out of the way), to save a session with two gnome-panel entries with RestartStyleHint=2. Thanks ...
Hi Mark. Here's how I can reproduce the thing : 1. Create a fresh new user on your system so you're sure he has no specific GNOME config. 2. Log in with this user. 3. Open a terminal and do 'killall gnome-panel' until you have something like 'No processes killed' (not sure what it is in english) 4. Launch a new panel from your cvs tree. 5. Save your session when you log out. 6. Log in. A guess : the problem here is that the two panels are not the same executable. The first one is /usr/bin/gnome-panel (or something like that) and the second one is ~/cvs/gnome-panel-HEAD/gnome-panel/gnome-panel
bug still here. One example: https://bugzilla.ubuntu.com/3185 I got this yesterday after playing with the gnome-session-save command: $ grep panel .gnome2/session | grep Program 11,Program=gnome-panel 14,Program=gnome-panel Updating the version to 2.9
The bug is still here in gnome 2.10, and it would really be a relief to have this fixed in gnome 2.12 eventually. Sorry that I can't help much more, but I just wanted you to know that it still exists in 2.10/2.11 afaik.
I'm using AltLinux.org Sisyphus (at-the-edga chaotic sea of software. Last release was far too long). Recently i stumbled upon that. And it was not me alone. http://article.gmane.org/gmane.linux.altlinux.sisyphus/26643 - this is the lates discussion, alas in russian and of little help to You. I stumbled upon this one or too packet releases before 2.12 - i think it was 2. 11.92 * Втр Сен 06 2005 Alexey Rusakov <ktirf@altlinux.ru> 2.12.0-alt1 - 2.12.0 - Removed more excess buildreqs. * Втр Авг 30 2005 Alexey Rusakov <ktirf@altlinux.ru> 2.11.92-alt1 - 2.11.92 - Scrollkeeper dependency fixes. - Removed excess buildreqs. * Срд Апр 13 2005 Yuri N. Sedunov <aris@altlinux.ru> 2.10.1-alt1 - 2.10.1 ~~~~~~~~~~~~~~~~ I'm novice to Linux. In those April days i used Gnome as root (before i managed to became sudoer :-) ) And it was ok. In our maillist one told that session applications are stored at ~/.gnome2/ sessions - so i wanted to compare `clean` root's config with newer faulty one. I did not found gnome-smproxy on my machine - neither as file, nor as registered in apt package, nor in gconf-editor. Maybe it is some alias hardcoded into gnome, God knows. But i found that in root's session file there are 4 entries, and the user had only 3. The extra record was to launch that very gnome-smproxy with Priority=0. Since Priority==0 or since now such binary exists - session settings GUI does never show it in the list, and it is not always easy to say were too look for info. Without advice about ~/gnome2/session i looked through gconf and .gnome and .x*........ I wish Linux have nifty GUI tools like Win32 sysinternals.com RegistryMonitor, FileMon, DiskMon, ProcessExplorer :-) I noticed that both root and user had dot-file in ~/.gnome2 It consisted of ".." It was named after gnome-smproxy and had some random salt at the tail of name. The --sm-config-prefix of CloneCommand and RestartCommand of gnome-smproxy entry had different salt!!! So i concluded that the sault in session file and in .dot file are out of sync for long and do not matter any more. So i added some cut of that entry to user's session file. I made id like another ones, differing only in last digit. I incremented num_cients. And i just dropped *Command which are out of sync or out of my understanding for this particular entry. <bdv@localhost:~/.gnome2> zsh 477 % grep 3, session 3,id=117f000001000110815114100000102300003 3,RestartStyleHint=2 3,Priority=0 3,Program=gnome-smproxy 3,CurrentDirectory=/home/bdv Since that time i re-logged in and rebooted twice. It seems to work now. What is the magic in that settings, why it is not auto-created if it is required, why it is not shown in sesions properties GUI - i cannot say. Perhaps i will hear it here :-) Good hunt!
Forgot to mention, i tried to switch locale (with GDM) from KOI8-r to UTF-8 This fixed captions on some Qt apps, like KJumpingCute, but killed others, like MultiGnomeTerminal, so in a while i reverted back. It seems to me - i got that "panel already launched" soon after that. Was it occasional, or did i some kind of killall (#15) by this - i do not know.
for some strange reason suddenly got Gnome not starting: splash screen popped up, progressed to launching panel - and there stopped. In SysLog i saw launch of ivman (one of programs from session-manual), and... silence. The reason was stange: somehow in session-manual appeared command to launch gnome-smproxy, copied from session. Again i feel sorry that Gnome was hanging giving no error nor any details of what had happened and what it is waiting for.
This dialog just showed its ugly face when the panel crashed in 2.14. I wonder... why should the dialog exist at all? It doesn't provide any meaningful information to the user nor lets her do anything of relevance. "I've detected a panel already running, and will now exit." Ok... thank you very much mr dialog. I already knew that a panel was running because I can see it on my screen. What do I care if you just discovered it? Utterly meaningless. :)
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.