More info about this: Apparently (thanks exploder for finding this out)
removing compizconfig-settings-manager and python-compizconfig fixes the
problem.
--
Unable to start applications after suspend/hibernation
https://bugs.launchpad.net/bugs/49221
You received this bug notification because you
Same problem here with Gutsy based LinuxMint Daryna. I can log off and
back on the system but can not shut down after log off and back on. I
have to Ctrl, Alt, Backspace restart the system and then shut down.
--
Unable to start applications after suspend/hibernation
Hi,
We're seeing this problem in Linux Mint 4.0 Daryna BETA021 (Gutsy based) with
gnome-session 2.20.0-0ubuntu2.
-- https://bugs.launchpad.net/linuxmint/+bug/158984
--
Unable to start applications after suspend/hibernation
https://bugs.launchpad.net/bugs/49221
You received this bug
Fixed with #12389
** Changed in: gnome-session (Ubuntu)
Status: Confirmed = Fix Released
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Does that email also imply that the workaround for this is to wait until
the fade-out effect behind the logout dialog has finished before
choosing 'Hibernate'?
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
That's how I understood it, but I'm the opposite of an expert. Running
compiz or beryl in feisty, the logout fade is simply gone, though the
same old choppy fade is still used for gksudo.
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
Joachim:
The brief tests that I've done seem to suggest that is the case (but
this is entirely empirical evidence).
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Yes, I always start suspend via the logout dialog (the red Standby
Logo button in the panel, then the yellow standby button in the lower
left corner). I'm not certain what you mean by waiting, as the logout
dialog always appears directly here.
--
Unable to start applications after
Suspend isn't working for me in Feisty, but in Edgy I always suspended
using the logout menu. I noticed that deleting the files in /tmp/.ICE-
unix/ on a funky resume allowed me start apps but not to immediately
reopen the logout menu.
--
Unable to start applications after suspend/hibernation
FYI, there are more details by Scott Robinson in a thread on the ubuntu-
devel-discuss ML ([Bug 49221] How to solve it, and why I'm not fixing
it.)
https://lists.ubuntu.com/archives/ubuntu-devel-
discuss/2007-March/000422.html
--
Unable to start applications after suspend/hibernation
If the gnome-session freezing issue occurs, please note the following:
* Did you start the suspend via the Logout Dialog?
* After waiting 5 - 15 minutes (depends on the initial conditions) did the
Logout Dialog appear?
I'm reasonably certain I have tracked down the bug in
The networking stop/start commands don't fix it for me either.
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Occurred again. This time, I checked loopback interface before
restarting it:
lo Encapsulamento do Link: Loopback Local
inet end.: 127.0.0.1 Masc:255.0.0.0
endereço inet6: ::1/128 Escopo:Máquina
UP LOOPBACK RUNNING MTU:16436 Métrica:1
pacotes
Stopping/starting networking does not help for me (also using network
manager).
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Also, in my case, I can fix the problem issuing the commands below:
sudo /etc/init.d/networking stop
sudo /etc/init.d/networking start
As I use network manager, these commands affect only loopback interface.
I didn't check loopback interface before restarting it. Will do next
time.
--
Em Fri, 16 Feb 2007 14:21:02 -
Sebastien Bacher [EMAIL PROTECTED] escreveu:
Might be the same problem than bug http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=406608. Do people still have the socket pointed
by SESSION_MANAGER in place when they get that problem?
Occurred here in one of
Might be the same problem than bug http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=406608. Do people still have the socket pointed by
SESSION_MANAGER in place when they get that problem?
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
I have no idea what you may mean here. Is there some way I can help?
Some file I can read or send to you to answer the question?
Sebastien Bacher wrote:
Might be the same problem than bug http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=406608. Do people still have the socket pointed by
My current investigation indicates the issue is related to the Ubuntu
custom login/logout dialog.
Specifically, the 13_smoother_fading patch. I'm still investigating, but
I believe it is related to the time jumping during the fade event.
*grumbles about how bloated gnome-session has become*
--
I can confirm this is occurring in feisty too. For whatever reason,
gnome-session is not writing back a response to connections. The
connections are being accepted, which means the gdk mainloop (as the
g_io_add_watch is driven by it) is still running.
I'm going to examine the source code more, as
Upgraded to feisty i386 yesterday, and it is still there (happening more
often than ever).
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I just resumed from suspend today. Some things were slightly odd; for
instance, the screensaver didn't start up. I'm not sure why... At any
rate, I resumed from suspend, and could click on stuff fine.
Then I went to network-manager, which was actually listing the nearby
networks (possibly due
Setting the date to 2008 didn't reproduce the bug. Which is a strike
against my theory that clock-shifts are causing the problem.
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Same problem happens to me. (Using up-to-date Edgy).
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I have this problem too, on an MSI 270, Sempron, i386. I've certainly
had the problem in Dapper, possibly before, now in Edgy. I didn't
report it, because I figured my report would surely be a duplicate...
Blacklisting psmouse doesn't help; furthermore IIRC the pointer is
consistent about
Hello!
Are there any updates on this? This bug still appears here, with a fresh
install of edgy.
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
With an upgrade to Edgy the bug seems not to happen any more on my
system.
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I still see this problem every now and then (on an uptodate edgy).
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Ok, I kept my home directory, containing all the .gnome2, .gconf* etc.
Maybe the source of the bug is contained therein. Grepping for gnome-session
there did not dig up something interesting.
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
I does still happen on Edgy albeit significantly less often than it used
to on Dapper.
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I had this problem on two computers. On one it was still a problem
after a fresh install of edgy (maybe with a held over /home? I forget).
On the other it was a problem almost every time I suspended after an
upgrade (before the upgrade suspend didn't work at all), but then it
disappeared on a
** Summary changed:
- Unable to start applications after hibernation
+ Unable to start applications after suspend/hibernation
--
Unable to start applications after suspend/hibernation
https://launchpad.net/bugs/49221
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
32 matches
Mail list logo
