I confirm, this is fixed. Thanks!
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
This appears to be fixed in Jaunty now. If gnome-power-manager is not
running, gnome-session doesn't wait around before displaying the dialog.
** Changed in: gnome-session (Ubuntu)
Status: Triaged => Fix Released
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bug
This bug still appears on hardy.
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
This seems to be a deadlock with regards to the session manager. I also
have g-p-m disabled in my session options... When I replace /usr/bin
/gnome-power-manager by a shell script that starts the real gnome-power-
manager under strace, I get the following debugging output:
-> Output of str
I need to confirm what Arthur Furlan told. I also had this problem of waiting a
long long time before the quit window comes.
I had also unchecked "gnome-power-manager", thinking it would be unnecessary
for my desktop computer.
I tried the tip of Arthur : I re-checked the "gnome-power-manager" i
** Changed in: gnome-session (Ubuntu)
Status: Confirmed => Triaged
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
It looks like there are actually several bugs here.
One is that "gnome-session-save --kil" calls gnome-power-manager and
takes 30 seconds to time out. It should check if gnome-power-manager is
running before making the call, and skip that step if it isn't. This
should be easy to fix, and can be wo
Hello, I think that I found a solution... I tested (and retested) and it works
for me.
To discover what's the problem that was causing the longer time I executed
$ tail -f ~/.xsession-errors
and then I executed
$ gnome-session-save --kil
that is the same command that runs when you clic
I am writing to confirm same bug on my GF's PC. I may have disabled gpm on it,
to try and make her PC faster... I will re-enable it and see what happens.
I will enable it and see what happens then... BTW, though, does that mean we
could have a fix coming soon? -- since Jani Monoses seems to have
G'day All,
I also geeting the same problem, but not on the main console. I only get
this problem when I login using XDMCP from a remote terminal. I have
g-p-m running, so all I can think of is that g-p-m does not interact
correctly when running from a remote session. This bug is very
frustrating a
I see this too on two computers since Hardy where g-p-m is disabled. The logout
dialog code checks to see if suspend and hibernate buttons are to be added and
asks g-p-m. However if it is not running it does not get the answer and it
blocks. g-p-m is started by this but possibly too late to answ
Same thing happened to me as Chocwise 100%, except when I googled it I
found the solution on this page.
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed as well. I use Hardy Final now, had the Problem from the start
because I upgraded from Gutsy and had the gnome-power-manager disabled
before already. Googled a little and found that workaround with
reenabling gnome-power-manager. The Shutdown-Dialog starts now
immediately.
--
System ->
** Changed in: gnome-session (Ubuntu)
Importance: Low => Medium
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Gnome-session checks that if gpm is running and asks hal to start it
(?), which it does. So, there's no way to actually disable gnome-power-
manager now, and IMO this is should deserve a priority higher than
"low"...
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/12
Extra detail: after changing panel -> logout -> login -> problem
reappears of course.
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
After i cleanet my settings, newe had this problem agene and can't
reproduce it anymore.
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
And after today's update: Problem is back!
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
After todayś update: Not anymore an issue. WoRks fine
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
no problem for me in Hardy Beta
On Sun, Mar 30, 2008 at 3:16 PM, 323232 <[EMAIL PROTECTED]> wrote:
> Encoutered bug after upgrading Hardy Beta
> + powermanager is enabled
> + Quit does not respond after login
> + After starting an application -like fire fox- the quit box (Logout,
> Quit, Restart
Encoutered bug after upgrading Hardy Beta
+ powermanager is enabled
+ Quit does not respond after login
+ After starting an application -like fire fox- the quit box (Logout, Quit,
Restart etc) appears and a can logout.
+ After loging out and login (to an other account) -> same issue
--
System
I encountered this bug after upgrading to hardy.
I can confirm:
- enabling gnome-power-manager in the session solves the problem
- I received the same error messages than André in .xsession-errors
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received
When this bug happens, the below (identical) lines are written to
~/.xsession-errors. The logout dialog appears at the same time as the
second time this message is logged. It appears as if it gives up trying
to connect to PowerManager after a given time.
** (x-session-manager:5639): WARNING **: Co
This bug is triggered for me too if I disable gnome-power-manager in my
session. I have reproduced it with both Gutsy and alpha 5 of Hardy. Let
me know if I can provide any information that may be helpful in
resolving this issue.
--
System -> Quit takes a long time to appear
https://bugs.launchpa
** Tags added: qa-hardy-desktop
** Tags removed: qa-hardy-list
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubunt
i think for most the proble was only the disable gnome-power-manager
On Mon, 14 Jan 2008 14:22:03 +0530, Sebastien Bacher <[EMAIL PROTECTED]>
wrote:
> Did everybody subscribed to this bug broke his session by disabling
> gnome-power-manager or is there users having a bug using the normal
> ubu
I had the bug just after installing ubuntu. So it was with the normal
configuration. I have another Ubuntu 7.10 virtualized using Virtual Box and
it is affected by this bug, so you can try if you want.
Good luck
On Jan 14, 2008 9:52 AM, Sebastien Bacher <[EMAIL PROTECTED]> wrote:
> Did everybody
Did everybody subscribed to this bug broke his session by disabling
gnome-power-manager or is there users having a bug using the normal
ubuntu configuration?
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a m
** Description changed:
Immediately after logging in, selecting System -> Quit takes more than a
minute for the window to appear.
If waiting a few minutes after logging in, then selecting System -> Quit
is much more responsive.
Also, when having to wait more than a minute for the w
I discovered that I too had been affected by this bug after a dumb
attempt to speed things up a little and removing gnome-power-manager
from the list of startup applications. Adding it back to the startup
applications and adding it to my current session corrected the issue
immediately as well as re
This bug will be fixed when a developer will find and fix the problem.
Anybody ( that has some programming skills ) can work on this. For your
problem, I'm sure that you can find a solution that doesn't require to
disable GPM. However, I think that you'll get the what you need here :
https://answer
The bug will be fixed when somebody will have a clear description of the
issue and a way to trigger it easily so it can be debugged. The current
comments are not really useful, it's clear some people have the issue
but none of those are able to debug and fix it apparently and there is
not enough in
"So when this bug will be fixed??"
I'm holding my breath (!) but as it is a low priority setting i guess we
have a long wait and/or it will be carried over into the next release??
Looks like i will have to dig out those micro$oft disks...
--
System -> Quit takes a long time to appear
https://bug
Same problem here...was having real problems with the cpu scaling and
system freezes making my PC unuseable. After much searching I switched
the scaling function off in the bios and disabled the gnome power
manager etc. At last I can use the PC to do some work instead of
screaming at the screen al
I confirm the guillaume's solution works. It solved my problem.
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubunt
So when this bug will be fixed??
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
I see "logout dialogue takes a very long time to appear" and "no options
for suspending/hibernating (not always, though, but mostly) on a desktop
(upgraded time and time again since 5.04), a laptop (upgraded from 7.04,
then to 7.10), another laptop (upgraded from 7.04 to 7.10) and a desktop
install
** Tags added: qa-hardy-list
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Hi!
I had the same bug and it seems to be resoved for me now! I did two
things and I can't tell wich one was the good one:
Firstly, on my desktop computer I re-enabled gnome-power-manager.
Secondly, I changed my /etc/hosts file by adding my hostname in the 127.0.0.1
line.
http://ubuntuforums.or
Hi again, I dunno but somebody in the thread/related thread mentions problems
with "gnome-power-manager". My problem is that quitting takes one minute or so.
This problem did not occur with Feisty. So I tried down grading just this
package
plus two dependencies to Feisty versions. This seems to f
Could you describe how the package is busy rather than advising users to
downgrade to a version not tested on gutsy?
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
* WORKAROUND **
There is a workaround. The "gnome-power-manager_2.20.0-0ubuntu6" package is
buggy.
Just down grade to Fiesty version:
wget
http://uk.archive.ubuntu.com/ubuntu/pool/main/g/gnome-power-manager/gnome-power-manager_2.18.2-0ubuntu3_amd64.deb
wget
http://uk.archive.ubuntu.com
The same with gnome-power-manager both disabled and enabled. The same
setup worked well in Feisty.
gnome-panel is unresponsive until "System>Quit" window appears.
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you a
** Tags added: desktop-next-lts
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
I'm experiencing this problem and have gnome-power-manager enabled in
the session box. It affects the gnome-panel applet as well as the awn
power button applet. It appears to me that gnome-session-save is
hanging. I have a strace of that script running that ends in a kill
because it hangs when run
Let me add that I was bitten by this bug as well.
I installed using Gutsy beta i386 alternative CD on a desktop computer,
the gnome power manager is not started in System -> Preferences ->
Sessions dialog after installation.
Enable the power manager in the Session dialog fixes the long delay.
--
Setting to Confirmed. Indeed if I remove (like I did) gnome-power-
manager from the autostart list (System->Preferences->Sessions), gnome-
session-save --kill or clicking the Quit icon or selecting System->Quit
results in ca. 60s wait. If I cancel it, the next time it works as
normal. If I logout a
I had disabled it in Feisty, so I don't remember, but I suppose that I
had removed the entry about the power manager in
system->Preferences->Sessions. Seems like I didn't disable it since it
wasn't in the list at all.
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/1
How did you remove it from your session?
** Changed in: gnome-session (Ubuntu)
Status: Confirmed => Incomplete
Target: tribe-4 => None
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of
As mentioned in my previous comment, it still happens if the user has no
gnome-power-manager in his session (which worked fine in Feisty). I'm
reopening the bug, just to make sure you know about it since I don't
know if you want to support that case.
** Changed in: gnome-session (Ubuntu)
St
Ok, I've experienced the problem with compiz disabled too, so nevermind
my post. The true workaround (found thanks to a post at lwn) is to have
gnome-power-manager in your session (which I had removed since I don't
have a laptop).
--
System -> Quit takes a long time to appear
https://bugs.launchp
I've seen this same behavior with compiz disabled as well.
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I have this problem with an updated gutsy as of now (27/09). sudo ifdown etc...
doesn't seem to change anything.
It's probably related to compiz since when I disable the effects, it works
normally.
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received
I am running tribe5 with all the updates as of 2007-Sep-06 noon HST, and I
still have this problem.
sudo ifdown lo
sudo ifup lo
seems to make the response to a quit work at normal speed.
I also have the problem that when I right click, I cannot open a terminal. The
option is there but nothing ha
This has not been observed any more since Tribe 3, and both the "compiz
session connect" hang and the gnome-power-manager interface renaming
bugs have been fixed since then. Therefore I am closing this.
Please reopen if it still happens on Tribe 4 for you. Thank you!
** Changed in: gnome-session
It is also very likely that this was related to compiz. Check gnome-
session-properties, which program currently tries to attach to the
session. For me, compiz often failed to connect and then timed out after
60 seconds. After it, the other services connected to the session (which
are responsible f
When this happens, it might be caused by an unconfigured loopback
interface. To fix that, type this into a terminal:
sudo ifdown lo
sudo ifup lo
ifdown makes sure that /var/run/network/ifstate doesn't list lo
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
Y
Marc - this seems to be resolved with Tribe 3 can you confirm this?
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
Installed with Tribe-2, the problem was there. I re-installed with
Tribe-3 and it the problem seems to have been fixed.
Thanks
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for your bug. Do you still have the problem? Does it happen
every time? Do you use compiz?
** Changed in: gnome-session (Ubuntu)
Importance: Undecided => Low
Status: New => Incomplete
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You rec
Marc can you confirm this?
Do we need more information on this one?
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: gnome-session (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs
Target: tribe-3 => tribe-4
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Also nm-applet and gnome-power-manager icons take a while to appear
The splash screen waits on gnome-volume-manager.
Changing the start order of /usr/lib/evolution/2.12/evolution-alarm-
notify to 60 (previous value = 50) fixes the problem: All items in the
session start promptly.
This is for gut
** Changed in: Ubuntu
Target: None => tribe-3
--
System -> Quit takes a long time to appear
https://bugs.launchpad.net/bugs/123078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
64 matches
Mail list logo