reassign to lm-sensors not sensors-applet
** Package changed: sensors-applet (Ubuntu) = lm-sensors (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1062310
Title:
ubuntu
I think he meant the lm-sensors version not sensors-applet.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/683591
Title:
sensors-applet randomly picks up duplicates
--
From the debug output it looks like there are already duplicate entries
for some sensors saved in sensors-applet's settings - basically what is
happening is that libsensors is not providing consistent naming of
sensors across reboots - so on first boot sensors-applet gets the list
of sensors from
I can confirm this crash on edgy amd64.
Can the new release from debian please be synced to edgy?
Cheers
--
Crasher: auto-fill in comments crashes emacs
https://launchpad.net/bugs/54643
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: emacs-snapshot-gtk
emacs-snapshot-gtk regularly crashes on edgy amd64 for a number of
different file-types. Sometimes this seems to be a relatively random
event, and will occur when simply scrolling through a file, while other
times it regularly occurs
Thanks Sam... I know its probably quite annoying for distributors, but I
plan on releasing another bugfix release later today...but I think
better to have the current release as stable as possible even if that
means making releases every week (although hopefully not :)
Thanks
Alex
On Tue,
Confirmed - running edgy with all current updates.
Any chance of a fix?
--
Fail to build with emacs-snapshot
https://launchpad.net/bugs/65298
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Thermal monitor support
This is irrelevant to the sensors-applet package
--
No thermal monitor support on AMD X2
https://launchpad.net/bugs/48935
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Everytime I try to use dvipdfm it segfaults, no matter what document I
use as input.
This bug also exists in Debian, and Gentoo have a patch which I am
pretty sure will fix it.
http://bugs.gentoo.org/attachment.cgi?id=87212
** Affects: tetex-bin (Ubuntu)
Importance:
I think this is related to the handling of timezones, and so may only be
reproduceable if you are using a specific timezone - ie. I am in
Adelaide/Australia, which is GMT +9.30 - I suspect the segfault only occurs on
half timezones as well, but I have not fully investigated it.
More info in
The actual patch use by Gentoo is slightly different than the one in the
bug report, and so I have attached it here.
** Attachment added: Patch to fix segfault in dvipdfm
http://librarian.launchpad.net/4861784/tetex-3.0_p1-dvipdfm-timezone.patch
** Description changed:
Everytime I try to
I have rebuilt tetex-bin with the patch applied and can confirm it fixes
the crash, can this patch please be applied and committed as dvipdfm is
useless without it.
--
dvipdfm segfaults every time
https://launchpad.net/bugs/66474
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Currently the sensors-applet package (1.7.8) does not contain the original
icons which are distributed with the source tarball of the current package
(1.7.8), but instead contains old icons from an earlier version.
Please can Ubuntu package the correct icons, especially
Public bug reported:
Previously when I had vmware-player installed under Dapper, when using a
virtual machine, vmware-player would display a list of the usb devices
on my host machine which can then be connected to the virtual machine.
However, after performing a clean install of edgy,
Ahh thanks for that. Muchly appreciated. Any chance this will be turned
on (mounting of usbfs) automatically in the release of Edgy?
--
[edgy] vmware-player cannot see usb devices
https://launchpad.net/bugs/62707
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Well since it has not been officially deprecated, and one of the
packages in the repos requires it to be mounted to work correctly,
wouldn't it make sense to have it automounted from fstab as default?
--
[edgy] vmware-player cannot see usb devices
https://launchpad.net/bugs/62707
--
Public bug reported:
When a USB flash drive is connected to the computer, it is automatically
mounted, but after unmounting it, it cannot be remounted (even though
the icon is still present under Computer with the Mount this volume
option available - which fails with an error if we try to use it)
** Attachment added: Video describing inconsistent bahaviour with usb devices
http://librarian.launchpad.net/4555444/usb_devices.ogg
--
inconsistent handling of external usb devices
https://launchpad.net/bugs/63090
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
What part other than a small image library which was originally distributed by
Red Hat as GPL is available as source code?
It is still a proprietary product - just because it is free (beer) doesn't make
it Free (freedom).
VMWare need to make the modifications, OR distributors need to ensure it
I am commenting both on this bug - it looks like it is identical to
#186058, but I chose this one to comment on since it was reported first.
Attached is a backtrace of compiz.real during the lockup whilst it is
running at 99% while I am running Hardy Release Candidate. I ended up
taking about 6
second stacktrace - this was taken about 30 seconds after the one
attached above (during the same lockup) but is seemingly completely
different - forgot to mention I used the script attached to bug #186058
to get the stacktraces. This one is almost useless though I don't know
why since it contains
Can you try the attached debdiff, since I don't have a working amd64
install of hardy yet, I'm not sure if this will definitely fix it, but
hopefully it is correct.
** Attachment added: debdiff to fix segfault
http://launchpadlibrarian.net/12685850/potential-segfault-fix.debdiff
--
Benjamin, you are seeing a different problem - in your case I am pretty
sure that what is happening is that sometimes when you boot up
libsensors / lm-sensors will name the chip differently (try running the
command 'sensors' in a terminal and see if the chip name is different),
and so
I just noticed Fedora package libNVCtrl separately and ship it under
core as it appears to be GPL 2, so this could be easily shipped in
Debian as well - will file a bug there too.
https://admin.fedoraproject.org/pkgdb/packages/name/libXNVCtrl
--
no nvidia support
Public bug reported:
Binary package hint: nvidia-settings
The recent hardy package added the NVCtrl headers to allow sensors-
applet to be built against it, however sensors-applet expects them to be
installed in /usr/include/NVCtrl rather than just /usr/include, and so
actually fails to see them
** Changed in: sensors-applet (Ubuntu)
Status: New = Invalid
--
i8k fan speed values are wrong
https://bugs.launchpad.net/bugs/200449
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Could you please post the output of:
netcat localhost 7634
cheers
--
sensors-applet reads incorrect output from hddtemp
https://bugs.launchpad.net/bugs/230680
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The version of sensors-applet in Hardy uses libsensors3, which seems to
have a habit of naming the sensors slightly differently than the
previous version of libsensors. So if the name of the sensors is
different, your previous configuration may not be applied. sensors-
applet does not read
This looks to be a pretty weird bug - it appears as though some memory
corruption is occuring somewhere between the start of
sensors_applet_init() (at this point the pointer sensors_applet is non-
null as it should be) but by the time the call to
sensors_applet_update_active_sensors() occurs, the
@pls: Thanks for the detailed info - I have managed to track down
another bug and have fixed it - which version are you using by the way?
I will release a new version within the next 1/2 hour, so if you could
build it from source and try it, that would be great.
--
Applet crash at startup
You need to run it from the command line, and then add it to the panel -
otherwise it will sit there doing nothing as you observed, waiting to be
added to the panel. Please try running it from the command-line, then
add it to the panel, and post back the output.
--
Applet crash at startup
Excellent. Please feel free to mark this as solved.
--
Applet crash at startup
https://launchpad.net/bugs/51575
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: hddtemp
See bug report in sensors-applet for symptoms
Requires this patch from Debian (see existing debian bug report for actual
error):
--- hddtemp-0.3-beta15.orig/src/satacmds.c
+++ hddtemp-0.3-beta15/src/satacmds.c
@@ -80,8 +80,8 @@
ret =
Debian bug report concerning same issue:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404310
Note the patch provided in the debian bug report is too strict, so we
should just use the one from the debian package, as listed above
This bug is causing bug #94558 reported in sensors-applet.
--
Filed #109498 against hddtemp which is the real culprit
--
gnome sensors applet 1.7.10 does not save changed preferences
https://bugs.launchpad.net/bugs/94558
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
The bug in hddtemp prevents the saving of ALL configuration data, so you
will need to either disable hddtemp by uninstalling it, or upgrade it to
a version which does not have the bug in it.
--
gnome sensors applet 1.7.10 does not save changed preferences
https://bugs.launchpad.net/bugs/94558
The naming could definitely be better, as with multiple devices, it is
not easy to identify which one is which when you want to unmount / eject
a specific one.
--
Volumes change name when mounted/unmounted in Nautilus
https://bugs.launchpad.net/bugs/85635
You received this bug notification
This is a known bug with the version that was shipped with Feisty
(7.04). This has been fixed with the version shipped in the soon to be
released Gutsy (7.10) version of Ubuntu.
** Changed in: sensors-applet (Ubuntu)
Assignee: (unassigned) = Alex Murray (pragmatine)
Status: New
Sorry, I just noticed that the version shipped with Gutsy is 1.7.12,
whereas this was fixed in 1.8.0 - (latest release is 1.8.1) so
unfortunately this is not fixed in gutsy.
--
Sensors-applet report Core 2 Duo temp as A (Ampere)
https://bugs.launchpad.net/bugs/147188
You received this bug
@albert - For some reason unknown to me, Ubuntu choose not to package
the original icons with sensors-applet and also fail to keep up to date
with the latest version, so as an upstream developer there is not much I
can do.
@Fredrik - I agree, and it would be simple to solve by Ubuntu packing
the
Hi albert - thanks for your industrious work.
Could you instead use the following patch which I have attached - it
also includes one minor change to ensure it works properly with the
voltage sensors
** Attachment added: Fix backported from upstream
I realise why (ie. Debian choose not to ship them, and since in general
Ubuntu just uses packages straight from Debian, Ubuntu does not ship
them) however, it would be great if Ubuntu could choose to actually ship
them, since in general there are many packages Ubuntu ships by default
which also
I already did a while ago - Bug 69800.
--
Sensors-applet report Core 2 Duo temp as A (Ampere)
https://bugs.launchpad.net/bugs/147188
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I should also say thanks muchly to albert and cesare, thanks for your work in
making sensors-applet in Ubuntu better for all users, as upstream I appreciate
it. I will try and get more involved with motu in the future so I can help more
directly with patches and the like.
Thanks again.
--
@Sam - I have emailed Philip again to see if he would be willing to change the
license so will let you know what response I get.
@Cesare - thanks again, your work in improving sensors-applet in Ubuntu is
greatly appreciated.
--
Please package original icons from source
Looks like a duplicate of bug #94558
--
sensor-applet starts showing wrong devices
https://bugs.launchpad.net/bugs/114804
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
*** This bug is a duplicate of bug 94558 ***
https://bugs.launchpad.net/bugs/94558
Duplicate of bug #94558.
** This bug has been marked a duplicate of bug 94558
gnome sensors applet 1.7.10 does not save changed preferences
--
Sensors Applet doesn't remember Preferences
*** This bug is a duplicate of bug 94588 ***
https://bugs.launchpad.net/bugs/94588
** This bug has been marked a duplicate of bug 94588
[apport] sabayon-apply crashed with ValueError in c2py()
--
sensor-applet starts showing wrong devices
https://bugs.launchpad.net/bugs/114804
You
** Changed in: sensors-applet (Ubuntu)
Status: New = Invalid
--
Warning colors limits must be configurable / device specific
https://bugs.launchpad.net/bugs/124934
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
@DouglasCaixeta: If the drive is listed in the Sensors list, simply
enable it by checking the Enable checkbox.
--
sensors-applet doesn't recognize newly installed hddtemp
https://bugs.launchpad.net/bugs/105291
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This should be closed as invalid.
--
Warning colors limits must be configurable / device specific
https://bugs.launchpad.net/bugs/124934
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
You can already do this by changing the Sensor Low and High limits under
sensor preferences.
--
Warning colors limits must be configurable / device specific
https://bugs.launchpad.net/bugs/124934
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
3.2.0 has been released:
ftp://ftp.gnome.org/pub/gnome/sources/ekiga/3.2/
--
Update to 3.1
https://bugs.launchpad.net/bugs/341367
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
My MacBookPro 5,1 with Intrepid boots and runs fine without acpi=off so
at least for me this is not needed.
--
Booting linux crashes on 2009 White Macbook (hardware version ID MacBook5,2)
unless you use acpi=off
https://bugs.launchpad.net/bugs/341230
You received this bug notification because
Public bug reported:
The bluetooth chip in the new Apple MacBook Pro 5,1 (and I suspect the
new Apple MacBook Aluminium although I don't have one of these to test
with) does not work until it is manually reset by issuing a
hciconfig hci0 reset
The device is identified as (from lsusb -v):
Bus
** Attachment added: Patch to add BTUSB_RESET flag for usb device id of
bluetooth on MBP 5,1
http://launchpadlibrarian.net/22939697/btusb-mbp51.patch
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/22939698/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
Should have made it clear the patch is against the 2.6.27 kernel in
Intrepid. It should also apply cleanly against the current kernel in
Jaunty as well, although I haven't tested that yet.
--
MacBook Pro 5,1 bluetooth requires reset before it can be used
https://bugs.launchpad.net/bugs/332443
Try running:
sudo hciconfig hci0 reset
In a terminal and see if you get any different behaviour after that -
the built in bluetooth on my MacBookPro seems to always need a reset
like this before I can successfully use it - in my case it is a driver
problem.
--
Ubuntu 8.10 - blueman 1.0 not
Public bug reported:
NVIDIA have released 180.51 as the latest stable driver - see
http://www.nvnews.net/vbulletin/showthread.php?t=122606 under current
releases:
Current releases
Current official release: 180.51 (x86 / x86_64)
Would be great if the package in Jaunty
I can also confirm my MBP5,1 with latest Jaunty updates (uname -rv:
2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009) does not
reboot either .
@Colin: there must be something different in your setup I guess... have
you changed anything which may have got it working?
--
[Jaunty]
** Bug watch added: SourceForge.net Tracker #2659148
http://sourceforge.net/support/tracker.php?aid=2659148
** Also affects: sensors-applet via
http://sourceforge.net/support/tracker.php?aid=2659148
Importance: Unknown
Status: Unknown
--
Only one nvidia temperature can be
** Bug watch added: SourceForge.net Tracker #1905614
http://sourceforge.net/support/tracker.php?aid=1905614
** Also affects: sensors-applet via
http://sourceforge.net/support/tracker.php?aid=1905614
Importance: Unknown
Status: Unknown
--
sensors-applet should recognize newly
Thanks Philip. As Marc mentioned above, this is a killer bug for anyone
with a Fujitsu Celsius H270 netbook, so for anyone who happens to
install Jaunty on one of these machines and enables the restricted
nvidia driver, their machine will be bricked. Given this I think this is
definitely a good
Can this get uploaded for Jaunty before release? Would be a shame to
ship tracker when it can't index evolution email.
--
Tracker Evolution Eplug missing
https://bugs.launchpad.net/bugs/360399
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This has been fixed in upstream version 2.2.4, and so to fix this in
Ubuntu we should simply need to update the package to this latest
release.
--
Changing temperature unit converts fan limits
https://bugs.launchpad.net/bugs/249955
You received this bug notification because you are a member of
Since I have upgraded to Jaunty I thought I should post the output of
running alsa-info.sh here (since previously I had only run it under
Intrepid) on my MacBook Pro 5,1.
http://www.alsa-
project.org/db/?f=7676cad3f19446207d351db82e5ef324fcb615e8
--
Left speaker doesn't work, controls mixed up
This has been fixed in sensors-applet 2.2.3 upstream, so a simple update
of the package in the repo from 2.2.1 to 2.2.3 would fix this. Please
file a separate bug for the update request.
--
Only one nvidia temperature can be detected
https://bugs.launchpad.net/bugs/362760
You received this bug
Can you provide more information as to when the crash happened - ie. did
it happen at start-up, or after sensors-applet had been running for a
while etc?
--
sensors-applet crashed with SIGSEGV in g_type_check_instance_is_a()
https://bugs.launchpad.net/bugs/194976
You received this bug
Mm, this line says the trackpad is added as a raw input device:
[ 10.121135] apple 0003:05AC:0236.0002: input,hidraw2: USB HID v1.11
Keyboard [Apple, Inc. Apple Internal Keyboard / Trackpad] on
usb-:00:04.0-6/input0
-- Is there a way to blacklist usbhid so it does not claim the device,
to
Output from alsa-info.sh script run on my MacBook Pro 5,1 running Ubuntu
8.10 Intrepid:
http://www.alsa-
project.org/db/?f=247450a1667370684d30c31008d124f15c8f3a19
Note: Under Intrepid ONLY the headphones work, I cannot get any sound
output from the speakers at all.
--
Left speaker doesn't
See this is totally bogus - its a massive WTF? Why does my F11 produce a
middle mouse click? (especially since lots of applications use F11 for
fullscreen as well, this breaks them too) - mouseemu should definitely
not override F11 and F12 and it should not be installed by default, it
causes way
By improving the driver, do you mean getting it to scale values based
upon which machine it is running on to report a larger dynamic range
under 'normal' light conditions? This should be relatively straight
forward, provided we can obtain some data about which machines report
these lower values -
I guess we need to first get the values which the light sensor reports
for each of the different models under varying light conditions - then
we can identify which models need correcting / scaling for - ie. as I
mentioned before my MBP 5,1 reports only 4 out of 255 in a reasonably
well lit room so
See new bug report which I just opened for a patch to add light_scale to
applesmc-dkms https://bugs.launchpad.net/mactel-support/+bug/315485
--
Backlight keeps getting darker on MacBookPro
https://bugs.launchpad.net/bugs/285815
You received this bug notification because you are a member of
Thanks for the feedback rydberg - after looking into it some more it
seems the new MBP / MBA's use the 10 byte light value from the left
sensor as follows:
first 2 bytes seem to always be 01
next 2 bytes are a big endian 16-bit value of the ambient light value with a
maximum value of 65535
next
Actually scrub the previous patch - this one is much simpler and doesn't
break the case for the old machines.
** Attachment added: Improved patch
http://launchpadlibrarian.net/21101822/applesmc-dkms-light-sensor-fix.patch
--
Backlight keeps getting darker on MacBookPro
As mentioned in bug
https://bugs.launchpad.net/ubuntu/+source/mouseemu/+bug/120102/comments/6
I really think mouseemu should not be installed by default on machines
it is not needed on - see rydberg's comment above
https://bugs.launchpad.net/ubuntu/+source/mouseemu/+bug/251830/comments/19
- since
This is not a bug - what has happened here is that while your machine
was locked, someone has come along and selected 'Leave a message' and
typed in 'Give me your password!' - then when you come and unlock the
screen, the message they left it displayed for you..
Try it for yourself.
--
Funny
To reproduce, lock your screen, then click the leave a message button,
and type in ' Give me your password' or whatever you want, then click
OK. Finally unlock the screen and voila!
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete = Invalid
--
Funny Dialog Box?
I can also confirm that the screen brightness hotkeys work fine on my
MacBook Pro 5,1 with Karmic x86_64.
--
Brightness hotkeys not working on MacBook 5,2 and 4,1
https://bugs.launchpad.net/bugs/434071
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am pretty sure this should be fixed if you install the package 'linux-
backports-modules-alsa-karmic-generic' - please try this and see if it
fixes your sound problems before trying to manually patch the drivers.
--
New iMac (9,1, March 09) headphone jack works, speakers do not
Since this bug is in relation to the suspend resume test script failing
(and not a general failure of suspend and resume) it is a little hard to
verify under Karmic since I don't think the script is designed for
Karmic. If the test script is still used by Ubuntu developers then I am
happy to see
Public bug reported:
Latest version in debian testing is 0.8.0 would be great if this could
get synced for lucid.
http://packages.debian.org/search?keywords=json-glib
** Affects: json-glib (Ubuntu)
Importance: Undecided
Status: New
--
Please sync json-glib to latest stable
** Bug watch added: Linux Kernel Bug Tracker #14355
http://bugzilla.kernel.org/show_bug.cgi?id=14355
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=14355
Importance: Unknown
Status: Unknown
--
Huawei E169 USB dongle not working with kernel 2.6.31-12.40
Just wondering if hyperair's patch will get applied to Ubuntu's banshee
before Karmic is released?
--
design problem? infinite wait for long queue
https://bugs.launchpad.net/bugs/334809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Pretty much each time the kernel gets updated in Karmic I have to re-
install (sudo apt-get install --reinstall bcmwl-kernel-source) the bcmwl
driver since the dkms rebuild doesn't seem to actually work correctly
(even though it appears to succeed).
Recently the nvidia driver was changed to use
I've started getting this in the last few days recently.. not too sure
what (ie xorg-server or maybe gnome-power-manager) has changed
recently... was working great until this.
--
Session active, not inhibited, screen idle notification after screen blacks
out during normal operation
I think this affects me too on latest Karmic since my screen backlight
never goes off even though I have set gnome-power-manager to put it to
sleep after 5 minutes - running latest Karmic updates on NVIDIA 9600M GT
with proprietary nvidia-glx-185 drivers installed from official ubuntu
repo. Any
This seems to be a serious regression to me - bug #426765 (which seems
to be a dup on this) suggests that commit
http://cgit.freedesktop.org/xorg/xserver/commit/?id=c1d901d723c3bee523736eacc15b44a7dff484fe
needs to be applied to xorg-server to fix this - so I suggest this bug
should be marked
Is this a dup of #413168
--
DPMS events reset event timer causing gnome-power-manager to exit idle state
almost immediately after a blank event
https://bugs.launchpad.net/bugs/426765
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm still seeing this (ie a large queue of notifications which quickly
become irrelevant) with banshee when skipping tracks (ie. the
notification for the track I skipped 20 seconds ago is currently showing
and it will be at least a minute until the notification for the now
playing track is shown
This occurs intermittently for me - sometimes I boot successfully and X
starts automatically, sometimes I need to do CTRL-ALT-F7 to get it to
come up..(and sometimes my machine rarely gets stuck and X doesn't come
up at all...)
--
X doesn't start automatically any more after installing
I've seen this a couple times, and am attaching my xorg log from the
last time it happened - it also looks like the nvidia driver is failing
to initialise - could this be some weird usplash / xsplash conflict
where usplash still has the framebuffer but x (via the nvidia driver) is
now trying to
@Bryce: I am pretty sure the Ubuntu xorg-server is still missing one of
the fundamental upstream patches to fix this issue - as Ive said on a
number of other bug reports which report this issue still, the following
patch is still needed:
I've uploaded a patched version of xorg-server to my PPA which should
fix this if you want to test it:
https://launchpad.net/~alexmurray/+archive/ppa
--
Karmic upgrade not shutting off backlight after time
https://bugs.launchpad.net/bugs/413168
You received this bug notification because you are
Yep, I've also got the same patch applied in my PPA and can confirm this
fixes the screen blanking.
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*** This bug is a duplicate of bug 413168 ***
https://bugs.launchpad.net/bugs/413168
I've uploaded a patched version of xorg-server to my PPA which should
fix this if you want to test it:
https://launchpad.net/~alexmurray/+archive/ppa
--
[karmic] display doesn't go to DPMS sleep
I've uploaded a patched version of xorg-server to my PPA which should
fix this:
https://launchpad.net/~alexmurray/+archive/ppa
--
Monitors do not sleep
https://bugs.launchpad.net/bugs/436574
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've uploaded a patched version of xorg-server to my PPA which should
fix this:
https://launchpad.net/~alexmurray/+archive/ppa
--
g-p-m does not turn off the display after specified time-out
https://bugs.launchpad.net/bugs/415589
You received this bug notification because you are a member of
This patch was recently applied to xorg-server in Ubuntu ( (see
https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/413168/comments/19) and it is waiting approval by release
team I think - https://lists.ubuntu.com/archives/karmic-
changes/2009-September/009738.html
--
Apply
1 - 100 of 1171 matches
Mail list logo
