I'm confirming this bug, as I'm hit by it as well.
Furthermore, I have actually disabled gnome-power-manager's locking in
gconf-editor, so I'm kind of surprised to actually see the screen locked after
a suspend/resume cycle.
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Confirm
Thanks Dan,
That workaround definitely has something to do with this problem. It
seems to have solved the problem here. "Seems" because, I'm only getting
a dark screen, not the actual screensaver I've chosen, but that's
probably a different problem.
Unredirecting full screen might not be the thin
I'm a bit too busy right now to do anything useful, but I thought I'd
just add this bit of information: It seems this problem occurs only when
compiz is active. When metacity is managing windows, the screensaver
activates just fine.
--
Screensaver doesn't start
https://bugs.launchpad.net/bugs/278
** Tags added: gnome-screensaver intrepid
--
Screensaver does not start
https://bugs.launchpad.net/bugs/274926
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.
** Attachment added: "gnome-screensaver-output"
http://launchpadlibrarian.net/17988174/gnome-screensaver-output
** Description changed:
For some reason gnome-screensaver doesn't start. The screen starts
fading out but then immediately returns me to the desktop. This is true
when the scr
Public bug reported:
For some reason gnome-screensaver doesn't start. The screen starts
fading out but then immediately returns me to the desktop. This is true
when the screensaver should be activated automatically, as well as when
I manually run gnome-screensaver-command -a.
I have attached the
The packages from Ted Gould's repository fixes my issue. Thanks a lot!
(I hope the updated package will be pushed to Hardy).
I'm not sure if this is the same bug/feature as above, but after
manually changing the backlight (using the brightness applet), gpm does
not seem to dim on idle.
--
Dim on
** Summary changed:
- gnome-power-manager does not restore brightness after idle dim
(2.22.0-0ubuntu1)
+ gnome-power-manager does not restore brightness after idle dim
** Description changed:
Binary package hint: gnome-power-manager
After the latest update to gnome-power-manager, a bunch
Alright, I have now made sure that 04_brightness_events.patch causes
this issue. Reverting that patch re-introduces some of the old problems,
but at least squashes this bug. I'll see if I can attach my package, and
you can see if it solves it for you guys as well. Next step, I guess, is
to try to f
I'm just thinking: If this bug is not going to be fixed before Hardy is
shipped, it might be a good idea to disable the dimming feature of gpm
by default. New users will just be very confused when all of a sudden -
sometimes with no obvious reason - the screen gets dimmed and won't come
back up aga
I see this too.
I wonder if it's a duplicate of bug 210090? Can anyone confirm it is?
--
google calendar does not load
https://bugs.launchpad.net/bugs/201248
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
@Bruce: I wasn't sarcastic writing "I guess all the devs must be
seriously overworked", judging from various comments across different
bug reports, it really seems like they are overworked. I hope they also
know how to take it easy.
@Others with the same problem: Real life issues are starting to t
I guess all the devs must be seriously overworked, ey? It would be nice
to have at least some input from someone who's actually working on
Hardy. This bug is pretty well confirmed by now (and really annoying!).
(OT question to Jisakiel: I've ordered the xps m1330 with the intel
chipset. Does it wo
Yes! Exactly.
/apps/gnome-power-manager/actions/sleep_type_battery is set to 'nothing' whereas
/apps/gnome-power-manager/actions/sleep_type_ac 'suspend'.
This is very strange, and changing the first key to 'suspend' fixes this
bug for me.
Obviously, there's something wrong with the gconf schema.
I have made a translation to Swedish of nautilus-share. It's kind of
made in a rush, but I'd like to submit it somewhere, although I have no
clue where.
--
nautilus-share untranslated
https://bugs.launchpad.net/bugs/208707
You received this bug notification because you are a member of Ubuntu
Desk
I changed status of this bug to confirmed (I keep forgetting that the OP
can do that).
Kirby, perhaps you should file another bug regarding the AC power on/off
transition, as it might be related to this but not identical...
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete =>
After the latest updates everything seems to work fine for me; the
xrandr module in gnome-settings-daemon as well as the gnome-display-
properties utility. This is on 855GM hardware, using the intel driver.
Cheers!
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197
** Attachment added: "Output of gnome-power-bugreport.sh"
http://launchpadlibrarian.net/12725942/gnome-power-bugreport.sh.output
--
gnome-power-manager does not restore brightness after idle dim (2.22.0-0ubuntu1)
https://bugs.launchpad.net/bugs/203494
You received this bug notification becaus
This particular issue is fixed with the latest update to gnome-power-
manager (2.22.0-0ubuntu1)
** Changed in: gnome-power-manager (Ubuntu)
Status: New => Fix Released
--
gnome-power-manager does not handle backlight properly on fujitsu platforms
https://bugs.launchpad.net/bugs/197253
You
Public bug reported:
Binary package hint: gnome-power-manager
After the latest update to gnome-power-manager, a bunch of things were
fixed, but at least one thing is now broken on my fujitsu-siemens
lifebook p7010: gpm properly dims the backlight of the screen when the
computer is idle for 30 sec
I'm trying to run this through gdb, but it seems there are no debugging
symbols for gnome-settings-daemon, and I can't find any dbg package that
goes with it.
I'll attach the output of gdb anyway, in case there might be something
useful, but I doubt it.
** Attachment added: "gdb-gnome-settings-da
>Will try it now and get back later.
Woops, forgot to get back, but I forgot because everything worked just fine :-)
Thanks for the update!
--
[hardy] two batteries display when left clicking on g-p-m
https://bugs.launchpad.net/bugs/177570
You received this bug notification because you are a memb
Sebastien, thanks for pointing out some of those comments.
I'm sure there's a way to settle on a reasonable solution, not necessarily
based on the subjective desires of the ones who most easily make themselves
heard. But, I understand, any such thing is for the next cycle :-)
However,
>(In the m
I completely agree with Johan, not tying the nautilus search to the
search utility provided by the distribution gives a really non-
integrated feeling to it all. After all, most users should be searching
for files in their home folders, not in /etc (what would they be doing
with files outside of ho
Confirming, I see the same problem on a Lifebook P7010, 855GM (intel
driver).
--
error starting GNOME Settings Daemon
https://bugs.launchpad.net/bugs/199960
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
This is some really bad news.
I understand that some people have no need to index their home dirs, but I (and
I assume many others) do.
Before this update I used control-F basically all the time to navigate to
different parts of my file system (I'm a novelist, and I often forget what my
document
Ah, I'm glad we're finally building it from git, 0.5.10 is really not on par
with the latest changes.
Will try it now and get back later.
--
[hardy] two batteries display when left clicking on g-p-m
https://bugs.launchpad.net/bugs/177570
You received this bug notification because you are a membe
>(likely lack of xrandr 1.2 support)
Just for the record, Bryce, I'm sure using xrandr 1.2. I switch between,
external, internal and dual screen setups all the time using randr and xrandr
1.2.
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this
@Bryce: Not true, I mentioned I'm using the intel driver which indeed
has proper xrandr 1.2 support. Do you want me to post my xorg.conf?
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/197153
You received this bug notification because you are a member of Ubuntu
Desk
I'm using the ~3 debs and they seem to work just fine for me so far.
@Bart: That's because gnome-power-manager has not finished profiling
your batteries yet, after a few charges/discharges it will report that
more accurately than acpi -b.
--
01_proc_sys_batteries.patch causes a regression making
@Daniel: I'm sorry, I momentarily forgot that the summary of this bug
had changed since I first filed it. When I filed it the summary was
something like "incorrect profiling files created", and indeed the
profiling files created in ~/.gnome2/gnome-power-manager are called
'profile-generic_id-generi
After running gconftool-2 --recursive-unset /apps/gnome-power-manager,
the brightness applet started to work again. In fact it and gpm's
automatic backlight manipulation worked perfectly fine for a while, but
just now, as I switched to battery power it started to be flaky again,
behaving the way I
Here's the patch that fixes this bug:
http://gitweb.freedesktop.org/?p=hal.git;a=commit;h=85390b2b5b45253f64867895204d95bf2e1dc357
--
hal not reading information about sysfs batteries correctly
https://bugs.launchpad.net/bugs/194052
You received this bug notification because you are a member of
I'm stumbling upon the same problem, using the intel driver. Should I
attach any information or is there enough now to debug this issue?
By the way, what exactly does it mean that gnome-settings-daemon has
xrandr to capabilities?
--
gnome-settings-daemon crashed with SIGSEGV
https://bugs.launchp
> Please file new reports for new bugs. The double battery issue is confirmed
> fixed.
Indeed, as I mentioned a few comments back, people should take a look at bug
194052 in order to help finding a solution to what I think is a common problem
for all of us.
--
[hardy] two batteries display whe
I can now confirm that I still have the problem, but it now it might be
related to Bug 194052.
--
gpm reports 'on battery' instead of 'fully charged'
https://bugs.launchpad.net/bugs/188494
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to g
*** This bug is a duplicate of bug 43572 ***
https://bugs.launchpad.net/bugs/43572
I have the same problem on lifebook p7010. Perhaps there should be a
separate bugreport for each model? How's this progressing anyway?
** Attachment added: "lshal output"
http://launchpadlibrarian.net/101235
37 matches
Mail list logo
