Thanks.
I've been meaning to do this, but have been too busy the last few days...
--
Screensaver does not start
https://bugs.launchpad.net/bugs/274926
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for the patch. I rebuilt consolekit with the patch applied, but I
still seem to have the same problem. Awkwardly, though, the problem
doesn't seem to surface regularly as I'm sure I saw the screensaver
active at least at one point (just by chance, that is). Now, however,
running
The output of dpkg -l consolekit shows version 0.2.10-1ubuntu6.
I've attached the output of gnome-screensaver --no-daemon --debug.
Regards, K.
** Attachment added: output of gnome-screensaver after consolekit upadate
http://launchpadlibrarian.net/18021230/gnome-screensaver-output-2
--
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
** 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
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks for reassigning. Here's the attachment:
** Attachment added: ConsoleKit.conf
http://launchpadlibrarian.net/17988947/ConsoleKit.conf
--
Screensaver does not start
https://bugs.launchpad.net/bugs/274926
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just wanted to toss this in: My experiences are in agreement with the others
above.
My laptop is not state of the art, but it's not at dinosaur either.
I have noticed that sometimes, perhaps even most of the time, after at
few attempts and clicking away the error message packagekit gets the job
Public bug reported:
This is a problem I'm having with the recently updated packagekit 0.3.3 on
intrepid:
Every time I attempt something, such as installing a package, updating the
system or what have you, packagekit says an internal system error has occured
and that The backend took too much
** Attachment added: screenshot.png
http://launchpadlibrarian.net/17776179/screenshot.png
--
packagekit says: The backend took too much time to process the synchronous
request - you need to fork!
https://bugs.launchpad.net/bugs/272410
You received this bug notification because you are a
I'm still having this problem.
Version of package is: 0.9.12-0ubuntu1~ppa5
I've added my user to all the pulse-groups and edited the daemon.conf file
according to the suggestion above.
I'm still experiencing rewinds and underruns.
--
[PPA 0.9.12 regression], Wakeup from ALSA!, Underruns
Public bug reported:
It seems like some paths are hardcoded in gnome-main-menu, notably
$HOME/Documents and $HOME/Desktop. Instead, $HOME/.config/user-dirs.dirs
should be parsed in order to learn which folders are the appropriate
ones with regards to the user's current locale. As things are now,
I don't see this problem anymore. I guess it's fixed with the current
mono libs I'm running on hardy (although I no longer have the
installation where I first saw this issue). I'm not sure if I should
mark this as fix released or invalid, so I'll leave that to a dev
who knows more.
Regards,
K.
Oh yeah, sorry about that. My packages have the same version number as
well so you won't need to recompile the extra modules. However, my
package is based on the kernel in the -proposed repo, so you need to
enable that repo in synaptic or /etc/apt/sources.list.
Well, now there's one package for
@Romario: Strange, the only setting I've changed compared to the
official ubuntu kernel is CONFIG_MODULE_FORCE_UNLOAD. I wish they could
just do that themselves. My packages work for me at least...
Now, can someone change the priority of this bug to high? Pretty please?
--
Intel Core 2 Duo -
I can confirm this, seeing the same on my dell xps m1330.
--
Hardy: FN-up/down keys change brightness too rapidly on DELL XPS m1330
https://bugs.launchpad.net/bugs/226981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I agree. This is extremely annoying. The importance on this bug should
moved up a notch from low.
Could we at least have a kernel update with CONFIG_MODULE_FORCE_UNLOAD
enabled, please?
--
Intel Core 2 Duo - Resume from suspend, CPU Frequency Scaling is gone on CPU1
By the way, is there any upstream bug report for this?
--
Intel Core 2 Duo - Resume from suspend, CPU Frequency Scaling is gone on CPU1
https://bugs.launchpad.net/bugs/183033
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Sorry to be spamming this bug report. I thought I'd share this (while we're
waiting for a real solution):
http://www.naderehvandi.net/backup/linux-image-2.6.24-17-generic_2.6.24-17.31ubuntu1_amd64.deb
http://www.naderehvandi.net/backup/linux-image-2.6.24-17-generic_2.6.24-17.31ubuntu1_i386.deb
Yes, still a problem in hardy. I have to manually add fujitsu-laptop to
/etc/modules.
Should I attach the output of dmidecode? lspci?
--
fujitsu_laptop not loaded automatically on lifebook p7010
https://bugs.launchpad.net/bugs/196683
You received this bug notification because you are a member
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
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
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
** 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
Cool, thanks for seeking out a patch for this.
Glad to help!
--
Patch to make the intel driver aware of the fujitsu-laptop /sys interface
https://bugs.launchpad.net/bugs/197620
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
If he comes up with a fix that they commit to git, make sure to let me
know
Alright, I'll let you know through this bug if anything interesting
happens upstream.
--
occasional hard crash on vt switch
https://bugs.launchpad.net/bugs/204603
You received this bug notification because you are a
If he comes up with a fix that they commit to git, make sure to let me
know
Alright, I'll let you know through this bug if anything interesting
happens upstream.
@jhansonxi: It would nice if you could find the time to jump on the bug
report upstream as well. I'm sure it gives a lot to have logs
I think I misunderstood the original post here. The vertical line is
never a problem for me, because it's only visible before my laptop
enters suspend, not only any VT switch (it might have been there
sometimes on a normal VT switch, but has definitely disappeared after a
couple of switches back
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have this issue too, although it seems to be harmless.
@Frode: Did you just install the .deb straight out of Debian's
experimental?
--
Display corruption in VTs on Intel 855GME
https://bugs.launchpad.net/bugs/210600
You received this bug notification because you are a member of Ubuntu
Bugs,
@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
I'm glad I found this bug. The solution seems to work for me. So the fix
needs to go to pulseaudio then?
--
mpd no access to soundcard using pulseaudio
https://bugs.launchpad.net/bugs/192735
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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
I was absolutely positive I had replied to the comment before the last
already, but seems I haven't.
It seems the good old ForceEnablePipeA hack is needed on my laptop. The
strange thing is that it hasn't been needed ever before, so I don't
understand why now. As with jhansonxi, vesa eliminates
I filed a report upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=15310
--
occasional hard crash on vt switch
https://bugs.launchpad.net/bugs/204603
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I see the white line as well, something I think is related to the new
drm module. However, as far as I can tell, the white stripe is just a
visual artifact, it does not affect anything whatsoever.
If the ForceEnablePipeA worked well for you, don't forget to file a bug
report upstream so that the
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
Of course, it's been changed to nautilus-share, which supports sharing folders
anonymously.
Is it really nautilus-share that's supposed to be the replacement comes
Hardy? I was of the impression that nautilus-share wasn't very well
localized. At least it's not translated at all to Swedish.
--
I've made a local translation of nautilus-share to Swedish (I need it
for parts of my household). How do I go about submitting my translation?
Perhaps it's of use to others. nautilus-share doesn't seem to be a
registered project at launchpad (at least I couldn't find it). Also, for
some reason the
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
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 =
Public bug reported:
I haven't found any bug exactly like this although some seem to be very similar.
Using an up-to-date hardy installation I've had this problem plaguing me
for some time now. Every now and then during VT-switch, everything turns
black, the hard drive led keeps blinking and
** Attachment added: Xorg log file from time of crash
http://launchpadlibrarian.net/12783678/Xorg.0.log.old
--
occasional hard crash on vt switch
https://bugs.launchpad.net/bugs/204603
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: xorg.conf
http://launchpadlibrarian.net/12783692/xorg.conf
--
occasional hard crash on vt switch
https://bugs.launchpad.net/bugs/204603
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Forgot to specify when I filed the bug
** Changed in: xserver-xorg-video-intel (Ubuntu)
Sourcepackagename: None = xserver-xorg-video-intel
--
occasional hard crash on vt switch
https://bugs.launchpad.net/bugs/204603
You received this bug notification because you are a member of Ubuntu
Bugs,
This seems to be the exact same problem on debian: http://www.mail-
archive.com/[EMAIL PROTECTED]/msg469396.html
However, I have not yet tried the master branch of the intel driver.
Will attempt to build it and see if it helps.
--
occasional hard crash on vt switch
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
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
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
** 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 because
Haha! I had completely forgotten about this bug. I no longer see it in
Hardy.
Cheers,
Khashayar
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Incomplete = Fix Released
--
PCMCIA 6-in-1 IDE card reader fails with -12 (exception Emask 0x0)
https://bugs.launchpad.net/bugs/94464
You
Update: The patch is now in current git:
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=commit;h=e04908853db74dc76718f6bc0dfb23b5ab3c5837
Please consider adding it to the intel driver.
--
Patch to make the intel driver aware of the fujitsu-laptop /sys interface
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:
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
Hi,
No, in an email, Jesse Barnes suggested I'd add that line to the intel driver
source code in order to make things work. I said I could do this in the
meanwhile, until the bug gets fixed. However, I might have misunderstood things
and the bug might in the end be fixed in the xbacklight
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
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
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 194719 ***
https://bugs.launchpad.net/bugs/194719
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
Just tried, still seeing the problem. It might be related to another bug
though (bug 194052), which causes the profiling not to work for me.
However, I have use_profile_time set to false, as well as
set_time_for_policy, so it shouldn't matter.
I'm not sure how to further give more information.
Public bug reported:
Binary package hint: gnome-power-manager
After the latest fixes to hal (see Bug 177570), gpm now correctly reports two
batteries instead of four on my laptop. However, I now have at least one new
problem. The files created by gpm to keep track of the profiling of the
** Attachment added: output of gnome-power-manager
http://launchpadlibrarian.net/12134427/profiling-problem-gpm-output.txt
--
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
** Attachment added: output of lshal
http://launchpadlibrarian.net/12134429/profiling-problem-lshal.txt
--
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 Ubuntu
Bugs, which is
The new package causes other problems for me. I have filed a new bug
(bug 194052). Please confirm if you see the same!
--
[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 member of Ubuntu
Bugs,
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 when
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
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
@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
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
@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
(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
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 have now made some tests and the xbacklight utility seems to be completely
irrelevant to this problem.
This is purely a hal issue.
The problem is basically this, to be more consice:
1) The fujitsu-laptop module creates /sys/class/backlight/fujitsu-laptop
2) Hal sees the interface, hence gpm
Public bug reported:
Since kernel 2.6.24 there is a fujitsu-laptop module that enables
backlight control on some intel fujitsu laptops. The small patch that is
attached enables the xbacklight tool to use this interface and control
the backlight.
The patch is incredibly small, it just adds one
** Attachment added: patch to make the intel driver of fujitsu-laptop
http://launchpadlibrarian.net/12350745/add-fujitsu.patch
--
Make the intel driver available of the fujitsu-laptop /sys interface
https://bugs.launchpad.net/bugs/197620
You received this bug notification because you are a
** Summary changed:
- Make the intel driver available of the fujitsu-laptop /sys interface
+ Make the intel driver aware of the fujitsu-laptop /sys interface
--
Make the intel driver aware of the fujitsu-laptop /sys interface
https://bugs.launchpad.net/bugs/197620
You received this bug
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
** Attachment added: output of lshal
http://launchpadlibrarian.net/12339914/lshal.txt
--
gnome-power-manager does not handle backlight properly
https://bugs.launchpad.net/bugs/197253
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: hal
I file this bug against hal as this is probably where it will end up
anyway.
After loading the fujitsu-laptop module (which creates a backlight
interface under /sys/class/backlight/fujitsu-laptop), gpm believes it
can handle backlight settings.
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
For me, at least, the old behavior (i.e. gpm reporting twice the amount
of actual batteries), also caused other issues, such as absurd notes on
remaining power, suspend and other things being triggered when they
shouldn't (and not triggered when they should), and so on.
I think we should try to
Thought I'd point out that this bug is very closely related to bug
194052.
--
01_proc_sys_batteries.patch causes a regression making gnome-power-manager not
detecting the battery properly
https://bugs.launchpad.net/bugs/194719
You received this bug notification because you are a member of
Public bug reported:
I have no clue against which package this bug should be filed really,
I'm just guessing it's against linux-image (possibly udev?).
The platform specific fujitsu_laptop module is not automatically loaded
after a clean install of Ubuntu Hardy Heron on my lifebook p7010. This
Sure, I can create that file, but what should it contain? Perhaps just
options fujitsu_laptop
Do you want me to test whether that module is loaded automatically after a
restart with that file?
--
fujitsu_laptop not loaded automatically on lifebook p7010
https://bugs.launchpad.net/bugs/196683
Another question to the people who have the problem: is the remaining battery
time absurd?
For me it's not quite absurd, but definitely wrong...
--
01_proc_sys_batteries.patch causes a regression making gnome-power-manager not
detecting the battery properly
Oh, I'm sorry, I accidently pressed the needs fixing here too button
on linux-meta, re-adding linux-meta to affected pacakges (not sure how
to remove it again).
Anyway, the problem is indeed identical to bug 119052, which has the bug
assigned to initramfs-tools. Perhaps it should be the same
I have now been using the drm modules from git with 2.6.24, and
everything has worked just fine. The native suspend/resume of the intel
driver (which was merged in 2.6.25) might be the reason for all I know.
I'm quite certain now that the bug cannot be fixed in intel driver, but
rather in the drm
That could very well be the fix. Perhaps someone could build a test
kernel with that patch to try out?
--
[Hardy] [regression] latest update to the intel driver fails suspend
https://bugs.launchpad.net/bugs/190153
You received this bug notification because you are a member of Ubuntu
Bugs, which
Perhaps it is a kernel problem, but I should note that I've as of now
used the old driver version (2.2.0+git20080107-1ubuntu2) during at least
10 suspend/resume cycles with no issues whatsoever. The kernel during
the change of driver has not been changed.
Thought I should mention that.
Thanks.
Aha! More updates: It seems I've been fooling myself all along. The
problem to suspend the laptop is still there, even with the older driver
I mentioned in my previous post. It seems that the problem to enter
suspend is there I'm on battery power, rather than on mains. That is,
suspending on
Alright, sorry to jump the gun too fast. I don't think that patch causes the
problem (which is a relief as I that would seem very odd to me).
Still now, without that patch, my laptop fails to enter suspended mode every
third or fourth time I attempt it to do so.
I will see if I can do better
** Attachment added: xorg log file
http://launchpadlibrarian.net/11829526/Xorg.0.log
--
latest update to the intel driver fails suspend
https://bugs.launchpad.net/bugs/190153
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: xserver-xorg-video-intel
After the latest update to the intel driver in hardy (or possibly the latest
xserver update), suspend stops working on my intel 855GM based laptop. I have
seen a few bug reports that describe a failure to _resume_. I'm seeing
I can now confirm that downgrading to version 2:2.2.0+git20080107 of the intel
driver (the only older version I had hanging around) solves the problem.
With version 2.2.0.90-2ubuntu2, the laptop will not enter suspended mode.
--
latest update to the intel driver fails suspend
Alright, one more update. I rebuilt the latest intel driver
(2.2.0.90-2ubuntu2) from the deb source, without applying
'02_quick_fix.patch', and suspend is now working properly. So I assume
the problem is with this tiny little patch. Hope this helps!
--
latest update to the intel driver fails
heh, that patch is needed or otherwise i965 is totally broken. You can never
win.
You know, it's funny that everybody complains about how the proprietary nvidia
driver is so bad cause it breaks suspend/resume for laptops. Lately, I get the
feeling that the very open source intel driver is
This bug is almost two years old and I'm seeing it on a new Hardy installation
as of today. Please let me know if I should file any information (I'm on a
lifebook p7010) to help debugging, or if this bug is just being ignored for
some reason.
Thanks.
--
g-p-m reports Problem with Suspend
Public bug reported:
When my laptop is on mains it sleeps in accordance with gnome-power-
manager's settings. That is, if I've set it to sleep after 20 minutes of
inactivity, it does precisely that. However, while on battery power this
does not happen. The screen is blanked, but the computer
** Attachment added: verbose output of gpm
http://launchpadlibrarian.net/11742845/gpm.verbose.txt
--
laptop will not sleep after idle time
https://bugs.launchpad.net/bugs/188639
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
By the way, just realized this might be a duplicate of bug #55581, which
is marked invalid due to lack of information.
--
laptop will not sleep after idle time
https://bugs.launchpad.net/bugs/188639
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
201 - 300 of 344 matches
Mail list logo
