bug: 26419 title: gnome-session hangs when "lo" is not correctly configured date-reported: Wed, 30 Nov 2005 22:35:01 -0000 date-updated: Tue, 15 Jan 2013 19:55:35 -0000 reporter: Carlos F. (topopardo-deactivatedaccount) duplicate-of: duplicates: 20638 31144 55742 63661 77318 108761 112840 attachments: patches: tags: qa-jaunty-desktop subscribers: Sebastien Bacher (seb128) Ubuntu Desktop Bugs (desktop-bugs) Nhestor Balingit (nhestor) Ubuntu Bugs (ubuntu-bugs) Carthik Sharma (carthik) houstonbofh (leesharp) Martin Albisetti (beuno) eppy 1 (choppy121212) Milan Bouchet-Valat (nalimilan) Przemek K. (azrael) Lechuan (lechuan) Chris Coulson (chrisccoulson) task: gnome-session status: Expired date-created: Wed, 30 Nov 2005 22:35:01 -0000 date-left-new: Tue, 15 Jan 2013 19:55:32 -0000 date-assigned: Fri, 13 Jan 2006 14:49:26 -0000 date-closed: Tue, 15 Jan 2013 19:55:32 -0000 reporter: Carlos F. (topopardo-deactivatedaccount) watch: https://gitlab.gnome.org/318584 importance: Medium assignee: milestone: task: gnome-session (Ubuntu) status: Invalid date-created: Wed, 30 Nov 2005 22:35:01 -0000 date-closed: Tue, 14 Sep 2010 21:21:46 -0000 reporter: Carlos F. (topopardo-deactivatedaccount) importance: Medium component: main assignee: milestone: Content-Type: multipart/mixed; boundary="===============0937711398880290267==" MIME-Version: 1.0 --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I admit that this is a strange bug. Some day, as usual, I clicked on System->Exit to halt the computer, but after clicking on "Exit", the panel hanged. The shutdown dialog didn't appear and the panel just died, but it d= idn't either reload or segfault, the "report a bug" window didn't appear. I can't provide a backtrace as it is a hang and not a segfault. I opened gnome-panel from a terminal (killing the previous one) and after the hang, = no message appears on the console. If you tell me some flags to run gnome-panel with in order to debug the pro= blem, I'll be happy to help here. http://bugzilla.gnome.org/show_bug.cgi?id=3D318584: http://bugzilla.gnome.org/show_bug.cgi?id=3D318584 --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Daniel Holbach (dholbach) Date: Thu, 01 Dec 2005 09:19:43 -0000 Message-Id: <20060113144926.21012.16129.launchpad@macquarie.warthogs.hbd.com> Thanks for the bug report. To me this sounds a lot like http://bugzilla.ubuntu.com/show_bug.cgi?id=3D18163 - could you have a look,= if this matches your symptoms and if so, tell us? --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Carlos F. (topopardo-deactivatedaccount) Date: Fri, 02 Dec 2005 17:09:11 -0000 Message-Id: <20060113144926.21012.65901.launchpad@macquarie.warthogs.hbd.com> Ok, more info. This morning I tried again to shutdown with System->Exit and it WORKED. Interestingly enough, a few hours later the same day it hanged again. I'm starting to imagine that it has something to do with the running processes = or the hardware. No configuration was changed and no packages were updated.=20 About bug 24307, it seems similar but gnome doesn't hang, only the panel. A= nd if I open a console and run "killall -HUP gnome-panel", it reloads and I can continue working (but the logout dialog doesn't appear either). --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Sun, 04 Dec 2005 17:18:10 -0000 Message-Id: <20060113144926.21012.36053.launchpad@macquarie.warthogs.hbd.com> Do you automatically store your session? Do you use dhclient? Is your loopb= ack correctly configured (ping localhost)? --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Carlos F. (topopardo-deactivatedaccount) Date: Mon, 05 Dec 2005 11:07:23 -0000 Message-Id: <20060113144926.21012.60806.launchpad@macquarie.warthogs.hbd.com> Yes to the first two questions, but you're right, loopback wasn't properly configured. I have new information... if I wait about 5 minutes, the panel "ressurects"= and the logout window is shown at last. In the window list appears a new button "gnome-session" which corresponds to the logout window, but I don't remember there was any button associated to this dialog. If you want a screenshot I can post some. It seems that it was a problem of the loopback device. Some of my /etc/init= .d scripts was screwed up. Thanks for the help. I suppose that we can close the bug now. --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Mon, 05 Dec 2005 12:14:59 -0000 Message-Id: <20060113144926.21012.25357.launchpad@macquarie.warthogs.hbd.com> That's a known gnome-session issue, you need a properly configured loopback= to not have to wait a few minutes before getting the dialog by example: http://bugzilla.gnome.org/show_bug.cgi?id=3D318584 --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Sat, 07 Jan 2006 22:26:39 -0000 Message-Id: <20060113144926.21012.20446.launchpad@macquarie.warthogs.hbd.com> *** Bug 20638 has been marked as a duplicate of this bug. *** --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Carthik Sharma (carthik) Date: Tue, 23 May 2006 17:44:25 -0000 Message-Id: <20060523174425.23695.83583.malone@gandwana.ubuntu.com> Confirmed by others. Thanks. --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Albisetti (beuno) Date: Tue, 20 Mar 2007 15:15:53 -0000 Message-Id: <20070320151553.11398.34574.malone@gandwana.ubuntu.com> Shouldn't this be a higher priority considering this is the default configuration in Feisty? --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Conn O Griofa (psyke83) Date: Tue, 20 Mar 2007 15:43:36 -0000 Message-Id: <20070320154336.5103.64412.malone@gandwana.ubuntu.com> Sebastien, You marked my bug at https://launchpad.net/bugs/94048 as a duplicate of this. However, I haven't noticed any logout bugs; my original bug deals with gnome applications being slow to start. The root problem and solution may be the same (lo interface, and the 127.0.1.1 hostname split), but perhaps the priority of the bug should be reconsidered due to the performance impact system-wide in Feisty's default configuration (see my bug for details, there's no need to spam this one with descriptions of a different symptom). Thanks. :) --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Tue, 20 Mar 2007 16:12:27 -0000 Message-Id: <20070320161227.11342.26353.malone@gandwana.ubuntu.com> what is the default configuration? having an "lo" interface not correctly configured? that's not likely. That's not a GNOME bug if you deconfigured the loopback interface. If the configuration is created with a graphical tool you should rather open a bug on that tool --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Martin Albisetti (beuno) Date: Tue, 20 Mar 2007 16:24:25 -0000 Message-Id: <20070320162425.11398.30627.malone@gandwana.ubuntu.com> Sebastien, I think you should take a look at this forum thread: http://ubuntuforums.org/showthread.php?t=3D388765 It's what the previous bug was reported on. --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Tue, 20 Mar 2007 17:37:56 -0000 Message-Id: <20070320173756.11342.9097.malone@gandwana.ubuntu.com> unduping to no send extra comments on the other bug --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Nicolas Stouff (nico-stouff) Date: Fri, 28 Sep 2007 19:11:10 -0000 Message-Id: <20070928191110.27380.8478.malone@potassium.ubuntu.com> Same problem, or at least, it seems so. Clicking in System -> Quit works well, but the fast-quit applet does not br= ing the shutdown window, instead, only panels and desktop freezes, but my k= eyboard and mouse are still active. My loopback is properly configured. Only changes in Gnome-Panel Config: removed fast-user-switch applet, added = tomboy and OOo quickstart, remove NetworkManager... Tht's all! --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: kailden (kailden) Date: Mon, 29 Oct 2007 23:47:38 -0000 Message-Id: <20071029234738.28137.14124.malone@gandwana.ubuntu.com> I had a similar problem (upon upgrade from feisty to gutsy) and I think it = was a problem with gnome-power-manager. When I ran gnome-power-manager in a terminal, it couldn't find /usr/lib/lib= wnck-1.so-18. I made a symbolic link as follows: sudo ln -s /usr/lib/libwnck-1.so.22 /usr/lib/libwnck-1.so.18 and made sure that gnome-power-manager was running in my gnome session, (System->Preferences->Sessions and check Power Manager) and now there is no hang. --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sebastien Bacher (seb128) Date: Tue, 30 Oct 2007 15:42:08 -0000 Message-Id: <20071030154208.8198.66963.malone@gandwana.ubuntu.com> looks like your issue is a different one and due to a local build, the ubuntu packages have correct libwnck depends --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: kailden (kailden) Date: Wed, 31 Oct 2007 13:28:20 -0000 Message-Id: <20071031132820.22378.74649.malone@gandwana.ubuntu.com> That may be the case..I think at one point I was looking for a way to stop charging a battery at 40% (optimal) when it was on the AC and I may have downloaded the newest gnome-power-manager code, I ran into someone on the ubuntu forums who had a similar problem, and the solution for them was JUST the latter step, adding gnome-power- manager to the session. (http://ubuntuforums.org/showthread.php?t=3D595247&goto=3Dnewpost). I'm sorry neither step fixes your problem...even if the symptoms are similar! --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Chris Coulson (chrisccoulson) Date: Thu, 16 Apr 2009 23:29:07 -0000 Message-Id: <20090416232907.13885.91075.malone@potassium.ubuntu.com> Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance. --===============0937711398880290267== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Vish (vish) Date: Tue, 14 Sep 2010 21:21:44 -0000 Message-Id: <20100914212145.23464.49594.malone@soybean.canonical.com> Thank you for taking the time to report this bug and helping to make Ubuntu= better. We are closing this bug report because it lacks the information we= need to investigate the problem, as described in the previous comments. Pl= ease reopen it if you can give us the missing information, and don't hesita= te to submit bug reports in the future.=20 To reopen the bug report you can click on the current status, under the Sta= tus column, and change the Status back to "New". --===============0937711398880290267==--