I see this sometimes on Jaunty - 2.6.28-12-generic #43-Ubuntu SMP Fri
May 1 19:31:32 UTC 2009 x86_64 GNU/Linux with nvidia-glx-180 - I can
semi-regularly reproduce it using OpenOffice or sometimes vim or
emacs... this is with compiz enabled. Haven't yet had a chance to see if
I can reproduce it usi
Attached output of lspci -vvnn on my machine (MacBook Pro 5,1 with
Nvidia 9600M GT)
** Attachment added: "Output of lspci -vvnn"
http://launchpadlibrarian.net/27490454/lspci.txt
--
display corruption with nvidia driver
https://bugs.launchpad.net/bugs/281519
You received this bug notification
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 Ubunt
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 Ub
After a bunch of messing around and with some good advice from Kacper,
plus Jim Rorie's comment above, I've been able to get the subwoofer
enabled on the MBP5,1 - again this was mainly Kacper's work I really
just helped test it.
So Kacper has updated his patch against alsa-driver-1.0.19 to enable
Yeah you'll need to do a clean patch P. Dunbar.
--
Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5,1)
https://bugs.launchpad.net/bugs/337314
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
P. Dunbar - The reason you need to manually specify the model=mb5 is
that Kacper hasn't added the model number for MBP5,2 to the driver -
only MBP5,1 - if you could provide the output of 'cat
/proc/asound/card0/codec#0' then we can add it to the patch.
If the behaviour with the YouTube Dolby Test
Whoops just noticed you already posted it - I've attached an updated
form the of the patch with the MBP5,2 model in it too now, so no-one
should need to manually specify the model as mb5.
** Attachment added: "Updated patch with MBP5,2 model number as well"
http://launchpadlibrarian.net/2652139
I just noticed the following patch on the Ubuntu wiki for MBP5,1/5,2
(https://help.ubuntu.com/community/MacBookPro5-1_5-2/Jaunty)
http://qwe.pl/~kacper/alsa-driver-1.0.19-mb51.patch
which adds a new model mbp5,1 to the intel hda audio driver in alsa
1.0.19 - will try and test it tonight and see h
I'm currently rebuilding alsa-driver-1.0.18 in jaunty with this patch -
applied relatively cleanly - to test on my mbp51 so will let you know
how it goes shortly...
--
Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5,1)
https://bugs.launchpad.net/bugs/337314
You received this
I can also confirm that it pretty much works - in that I now get sound
from the left speaker finally but overall the sound seems more tinny -
ie. has a lot less bass and is more treble-y - is there some difference
between what the new mb5 model uses and the old mbp3 model which may
have affected t
Nikos - you'll need to rebuild alsa-driver from source again since the
kernel version has now changed when you upgraded it and the modules
which you built previously are for the old version (2.6.28-11-generic)
--
Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5,1)
https://bug
I can confirm this now works in 2.6.28-12-generic
--
MacBook Pro 5,1 bluetooth requires reset before it can be used
https://bugs.launchpad.net/bugs/332443
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
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 cou
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] MacB
** 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 detecte
** 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 inst
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 rea
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 libsenso
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 list
just wanted to say I got hit by this really unintuitive bug when
installing intrepid on my new macbook pro - F11 is used in emacs for
devhelp-word-at-point and so I cant use this without disabling mouseemu
- I think this is totally bogus - F keys should do what they are - ie
send F key events - to
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 - d
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 Ubuntu
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 mo
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 2
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
https://bugs.launchpa
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
I am seeing this same bug on my MacBook Pro 5,1 with Ubuntu 8.10 using
the mactel-support ppa with all relevant packages from the PPA installed
and kernel modules loaded. This includes the updated package of gnome-
power-manager from the PPA, and the only way to fix the problem is to
disable the 'U
Seems I needed to adjust the correction_factor gconf key in gnome-power-
manager - in good light, the light sensor would be
cat /sys/devices/platform/applesmc.768/light
(4,0)
and then covering it with my hand, I'd get
cat /sys/devices/platform/applesmc.768/light
(0,0)
So it seems to be reading
I am also seeing this on Ubuntu 8.10 64-bit, fully updated - I am also
using the proprietary nvidia driver with an nvidia 7600GS with compiz
enabled.
I think this is a bug in the proprietary nvidia driver as the recent
180.06 BETA driver claims to fix this problem:
from: http://www.nvnews.net/vbu
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
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
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 work
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 see
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 00
** 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"
http
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
You
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 o
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 no
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 notificatio
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 ins
@Chris - Right click on the volume icon on your gnome panel and open the
volume control dialog. Make sure the device is selected as NVIDIA HDA
something (sorry I'm writing this from memory at work). Then click the
Preferences button and enable the checkbox labelled 'Source' or 'Channel
Options' or
@Luke (themuso) - is the provided output's from alsa-info.sh enough or
do you need more info? I am relatively comfortable hacking on kernel
stuff (although have never really played with audio drivers) so if there
is anything you want me to try, let me know as it would be great to try
and get this f
This patch is about making the applesmc driver report sensible values
for the ambient light sensor - it has already been integrated into the
applesmc dkms package in the mactel ppa so if you're running that then
you've already got it and don't need to do anything with the patch
itself.
--
Backlig
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 p
@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
https:/
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
https:/
Are you sure you are using the latest version?
That string "trying to load icon"... does not appear anywhere in 1.7.6.
Can you try it with the latest version?
--
Applet crash at startup
https://launchpad.net/bugs/51575
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
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
This has been fixed upstream and will be available in the next release
of sensors-applet.
--
normal font label is misaligned according to others applets and menus in gnome
panel
https://launchpad.net/bugs/45547
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
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, 2006-08
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
https://
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
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
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 du
any chance this could actually get committed or even a comment from one
of the packagers as to what the intention is?
--
dvipdfm segfaults every time
https://launchpad.net/bugs/66474
--
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: Un
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 Gent
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
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
You
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 becaus
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 notific
@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 l
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"
http://launchpadlibrarian.net/9896078/sen
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 hav
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
ubuntu-bugs@lists.ubu
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.
--
Sens
@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
https://bugs.launchpad.ne
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:
*** 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
https://bugs.lau
*** 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 receive
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 dif
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
** 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
ubuntu-bugs@lists.
** 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.
--
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 th
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
ubuntu-bugs@lists
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
You shouldn't need to remove and re-add it - just log out and log back
in to restart it, or do a killall sensors-applet from the panel, then
click reload when the dialog box pops up telling you it died - this way
you can keep your original settings. To make sensors-applet detect new
stuff on the fl
Can you run the following from the commandline:
strace -p `pidof sensors-applet`
and then open and close the preferences dialog, and post the output
here.
Also, sensors-applet outputs stuff of the command-line too, so if you could run
it from the commandline:
/usr/lib/gnome-panel/sensors-appl
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
https://bugs.launchpad.net/bugs/
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
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 sensors-apple
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
htt
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
--
sensors-
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 = scsi_S
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.
--
h
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
@Sander50: What workaround??
@pitti: In general I think it *doesn't* work fine to eject all usb
devices - especially external USB hard drives - flash drives seem to
work okay - except they can't be remounted afterwards and need to be
physically removed and reinserted first - but I have an external
But it seems like this (not being able to eject devices using nautilus /
drive-mount applet) is definitely a new problem - at least for me I
never had problems like this before, and thus this a regression for me -
has anything else changed such as the method used to eject the devices
which could ac
Interestingly, while I can't eject my external usb harddrive, I can
still eject my usb thumb drive, so I have attached the output from
DebuggingRemovableDevices from the wiki with first the usb flash (thumb)
drive which can be correctly ejected, and then the external usb
harddrive which can't be ej
udev.log with thumb drive
** Attachment added: "udev.log with thumb drive"
http://librarian.launchpad.net/7336300/udev.log
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
** Attachment added: "lshal with thumb drive"
http://librarian.launchpad.net/7336301/lshal.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
dmesg with thumb drive - note before running these debugging steps I had
previously inserted and ejected the drives a couple times so only the
last bit is probably relevant
** Attachment added: "dmesg with thumb drive"
http://librarian.launchpad.net/7336304/dmesg.txt
--
do not eject all USB/F
devices.txt listing sd* devices in /dev
** Attachment added: "devices.txt"
http://librarian.launchpad.net/7336305/devices.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
other outputs requested - ie id etc
[EMAIL PROTECTED]:~$ id
uid=1000(alex) gid=1000(alex)
groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),110(netdev),111(lpadmin),113(powerdev),114(scanner),116(admin),1000(alex)
[EMAIL PROTECTED]:~$ id hal
id: hal: No such u
Now is attached the same but when the external usb harddrive is attached
- I also tried ejecting it so the output in gvm from trying to do that
is there too
** Attachment added: "gvm.log with external usb harddrive"
http://librarian.launchpad.net/7336311/gvm.log
--
do not eject all USB/Firewi
** Attachment added: "lshal with external usb harddrive"
http://librarian.launchpad.net/7336312/lshal.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
1 - 100 of 1235 matches
Mail list logo
