** Tags added: lucid
--
closed Laptop Lid to reliably keep Backlight off
https://bugs.launchpad.net/bugs/41994
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing list
I can't reproduce it with ubuntu fully up-to-date now (not that I ever
knew how to trigger it, is was simply always triggered here on login).
--
nautilus crashed with SIGSEGV in g_mount_spec_match_with_path()
https://bugs.launchpad.net/bugs/528299
You received this bug notification because you
** This bug is no longer a duplicate of bug 49579
screen doesn't lock when panel menu is open
--
Screensaver does not activate while mouse pointer on tooltip
https://bugs.launchpad.net/bugs/205574
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 49579 ***
https://bugs.launchpad.net/bugs/49579
Well, if the Hint objects manage themselves, yes. But in my vague memory
gtk Hints didn't work like this (nor did on any widgetset I've seem).
--
Screensaver does not activate while mouse pointer on tooltip
Wait. Didn't you, Chris, said that CPU use is taken into account when
dimming? Isn't this bug requesting/arguing that blank timeout should be
fixed i.e. should not take CPU use into consideration? So should the dim
timeout be taken out of the equation for blank timeout?
--
gnome-power-manager
*** This bug is a duplicate of bug 49579 ***
https://bugs.launchpad.net/bugs/49579
Another thing that suggests this is not a duplicate: I can suspend
and/or lock the screen (with Ctrl+Alt+L) while showing the hint.
--
Screensaver does not activate while mouse pointer on tooltip
The original poster says:
(...)
As a second step, it then uses cpu load as an additional measure.
(...)
This is great for determining when to suspend or hibernate. But it is
counter intuitive for turning off the display. There are a large number
of bugs filed againt g-p-m for display
Teej, do you mean you can't reproduce the bug?
Chris, you want to set status Wontfix, then OK, it's your decision and you're a
Canonical dev, but this is not Fixed.
--
gnome-power-manager put display to sleep timer incorrect when CPU is being used
https://bugs.launchpad.net/bugs/289322
You
I'm measuring with AC plugged on, so there's no dimming.
--
gnome-power-manager put display to sleep timer incorrect when CPU is being used
https://bugs.launchpad.net/bugs/289322
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
OMG. It's been sometime since I tested running on battery. Now unplugging from
AC doesn't reduce backlight brightness, and the display doesn't dim after
1min+...
Does g-p-m count dimming even on AC? Maybe this is the problem? And maybe CPU
detection is too sensible (mine shows 4% in use)? Is
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Fix Released
--
Locking the screen in a dualhead configuration results in one monitor being
still visible
https://bugs.launchpad.net/bugs/417722
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Can you still reproduce this? I can't reproduce it in Lucid.
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Incomplete
--
screensaver does not blank screen if no activity since (auto) login
https://bugs.launchpad.net/bugs/403922
You received this bug notification because you are
Any gtk hint seems to trigger the bug. For example, try the gnome-panel.
Tested is on Lucid.
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Confirmed
--
Allow screensaver to activate while mouse pointer on tooltip
https://bugs.launchpad.net/bugs/205574
You received this bug
*** This bug is a duplicate of bug 49579 ***
https://bugs.launchpad.net/bugs/49579
It also prevents the monitor from blanking. Not cool.
--
Allow screensaver to activate while mouse pointer on tooltip
https://bugs.launchpad.net/bugs/205574
You received this bug notification because you are
** Tags added: lucid
--
screen doesn't lock when panel menu is open
https://bugs.launchpad.net/bugs/49579
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
boga: what do you mean by idle?
Testing on Lucid, I caught such random rewrite only once while the screensaver
was not active. While the screensaver is active, there was no rewrite, after
more then 30min (screensaver timeout was set to 1min).
--
gnome-screensaver rewrites its config when idle
*** This bug is a duplicate of bug 49579 ***
https://bugs.launchpad.net/bugs/49579
I'm not so sure this is the same bug, because in this case there's not
even a fade out. Or maybe the other bug has changed since the original
post. In this case, the hint problem should be mentioned on the
*** This bug is a duplicate of bug 49579 ***
https://bugs.launchpad.net/bugs/49579
Reading the upstream bug, it doesn't seem to be the same bug really.
Unless gtk implementation of hints grabs the mouse, which doesn't seem
to be very necessary to say the least...
--
Allow screensaver to
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/43468388/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43468389/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/43468390/Disassembly.txt
** Attachment
Pedro: Yes, it seems so. Please see bug
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/558696 .
--
nautilus crashed with SIGSEGV in g_mount_spec_match_with_path()
https://bugs.launchpad.net/bugs/528299
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Follow up (sorry for the spam): I can't reproduce any random rewrite either
while idling (with screen saver inactive) or during normal use. The apparently
random rewrite is because gnome waits quite some time to write the file after
changing the setting.
Obs. For inactive I don't mean disabled
Everything I reported is against Lucid, fully updated at the time of the report.
Chris: can you please clear the terminology on dimming the screen and
blanking the screen? BTW I still see the problem of the notebook LCD
un-dimming/backlight going back on for no reason.
--
gnome-power-manager
Simple test:
1) Unplugged external keyboard and mouse to avoid interference.
2) Set Put display to sleep when inactive for: to 1min.
3) Time for display to go off with some applications open: 2:34min.
4) Time for display to go off with all applications closed: 1:12min.
So, the CPU or something
It seems to be fixed, thanks.
--
eog crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
https://bugs.launchpad.net/bugs/513397
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in ubuntu.
--
desktop-bugs mailing list
Do you mean it occurs now or whether it occurred in Lucid timeframe?
It's been some time since I last saw this bug, but it's never been easily
reproducible and it definitely occurred during Lucid development.
It occurred more frequently when changing the view while loading a very large
In some notebooks with crappy BIOS - i.e. mine - this message actually
can make sense - in an annoying way -, because the ACPI (?) reports the
battery is discharging even for the natural discharge, while the
notebook is plugged.
--
Battery Discharging is a horribly worded message
It's hard to confirm/debug this issue because timeout isn't respected
most of the time.
--
gnome-power-manager needs different idleness definition for turning off display
https://bugs.launchpad.net/bugs/289322
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Ok, a simple experiment doesn't seem to confirm this bug exactly.
1) I set up the put display to sleep when inactive to 1 minute.
2) Leave the desktop idle with the programs (I'm using) open (firefox, pidgin,
hgtk, gnome-terminal, etc): it takes 3:34min to turn off display.
3) Leave a
BTW, the screensaver timeout is precise. In exactly 1min the screen
starts to fade out.
--
gnome-power-manager needs different idleness definition for turning off display
https://bugs.launchpad.net/bugs/289322
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
(sorry for the spam)
It seems the display is never turned of if there's a window with urgency
state! (blinking on the taskbar)
Screensaver kicks in normally.
--
gnome-power-manager needs different idleness definition for turning off display
https://bugs.launchpad.net/bugs/289322
You received
It's impossible to do anything with the nautilus bug raging on. At the time I
could make the desktop usable by using pcmanfm (just by accident, because I
installed XFCE).
Dual screen needs too many other compromises anyway: must disable (radeon)
kernel modeset, disable DRI in xorg.conf,
What are the steps to reproduce? There's none in this report.
Some of the related bugs (other distros) don't seem to be related at all.
Session management is working in Lucid and IIRC was working o Karmic too, but
wasn't working in Jaunty, so what's bug about now?
--
.xsession-errors: 'Failed
Ok, thanks, I can confirm. Odd thing is can't find a reference for that
file anywhere in $HOME or /tmp, and removing the only .ms file there was
doesn't get a new one created (after a logout)...
--
.xsession-errors: 'Failed to read saved session file'
https://bugs.launchpad.net/bugs/150721
You
This is definitely fixed in Ubuntu/Karmic. Should it be marked as fixed
upstream too?
--
Totem sets the GNOME global volume when changing volume and mutes volume
between videos
https://bugs.launchpad.net/bugs/391239
You received this bug notification because you are a member of Ubuntu
Desktop
Too bad neither 'gdm' nor 'gnome-session' have packages for debug symbols.
Anyway dual screen setup isn't that great with metacity/gtk either
(e.g. no easy way to move from screen to another), and I finally got
the panels to work on dual-monitor single-screen setup. The only
annoying part is
Is it my impression or the latest xserver-xorg-core upgrade fixed it?
--
Nautilus crashes when there are multiple XScreens
https://bugs.launchpad.net/bugs/508890
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
Shame on me for not reporting the version (Yes I meant version
2:1.7.3.902-1ubuntu12).
And I apology too for the false alarm :-/ It seems some lxde/pcmanfm
upgrade hooked out the faulty nautilus process.
--
Nautilus crashes when there are multiple XScreens
https://bugs.launchpad.net/bugs/508890
Public bug reported:
Binary package hint: nautilus
I'm trying to use a dual screen setup (two screen sections, two device
sections for the same card in xorg). Both desktops show fine, but a
nautilus process is continuously started and crashed (occupying 100% of
a cpu core).
Obs. Two screen
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38833788/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/38833789/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/38833790/ProcMaps.txt
** Attachment
Maybe it's not a nautilus bug after all. See my other report:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/518103
--
Nautilus crashes continuoulsy in dual screen setup (nautilus crashed with
signal 5 in gdk_x_error())
https://bugs.launchpad.net/bugs/518092
You received this bug
Public bug reported:
Binary package hint: gnome-panel
In a dual-screen setup (not a dual-monitor single-screen setup), trying
to drag a Drawer applet from (the panel of) a screen to another
triggered the crash in gnome-panel (which didn't respawn). Re-launching
gnome-panel (from a terminal I
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38851076/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/38851077/Disassembly.txt
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/38851078/GConfNonDefault.txt
** Visibility changed to: Public
--
eog crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
https://bugs.launchpad.net/bugs/513397
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in ubuntu.
--
desktop-bugs mailing list
43 matches
Mail list logo
