[Bug 281519] Re: display corruption with nvidia driver
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 using metacity. -- display corruption with nvidia driver https://bugs.launchpad.net/bugs/281519 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 281519] Re: display corruption with nvidia driver
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360399] Re: Tracker Evolution Eplug missing
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 249955] Re: Changing temperature unit converts fan limits
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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 enables the subwoofer now and adds the id for the MBP5,1 so you shouldn't have to manually add model=mb5, it should now automatically be detected! I've attached the latest patch to this bug report as well. He is also going to forward the patch upstream to Alsa so it should be included in a future release - lets hope it make it into Karmic! This should hopefully resolve all the issues in this bug now. I have to say, its pretty awesome to have sound working completely now! ** Attachment added: "Patch to enable L&R speakers + subwoofer and MBP5,1 id automatically" http://launchpadlibrarian.net/26500515/alsa-driver-1.0.19-mb51.patch -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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 is the same under Linux now as Mac OSX then I would say this bug is fixed by this patch. -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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/26521394/alsa-driver-1.0.19-mb51.patch -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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 how it goes...if anyone else has tried it can you provide any feedback whether it works or not? -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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 this? Does anyone else also think this is the case or is it just me? -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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://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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 332443] Re: MacBook Pro 5, 1 bluetooth requires reset before it can be used
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364965] [NEW] Stable NVIDIA driver 180.51 released - please upgrade in Jaunty
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 could be updated (although I realise with the release imminent this is unlikely, but perhaps if it could get pushed to jaunty-updates that'd be great). --- Version: 180.51 Operating System: Linux x64 (AMD64/EM64T) Release Date: April 21, 2009 Release Highlights * Added support for the following GPUs: GeForce 9600 GSO 512 GeForce 9400 GT GeForce GTS 250 GeForce GT 140 GeForce GT 130 Updated nvidia-bug-report.sh to compress its log file; running `nvidia-bug-report.sh` now produces "nvidia-bug-report.log.gz". * * Addressed a problem that could lead to intermittent hangs and system crashes on some GeForce 9 and later GPUs. * Fixed an X server crash when viewing the website www.tim.it. * Fixed a DisplayPort interaction problem with power management suspend/resume events. * Fixed rendering corruption in the OpenGL 16-bit RGB Workstation Overlay. * Fixed a recent VDPAU regression that caused aborted playback >and hangs when decoding some H.264 clips on G84, G86, G92, G94, G96, and GT200 GPUs. * Fixed occasional X driver memory management performance problems when a composite manager is running. * Improved compatibility with recent Linux kernels. * Reduced CPU usage of nvidia-smi utility for reporting Quadro Plex information. * Fixed compatibility problem with LandMark GeoProbe. * Fixed an interaction problem that could corrupt the EDID of the Fujitsu Technology Solutions Celsius H270 notebook's internal flatpanel. * Fixed a bug that could interfere with the detection of display devices attached to secondary GPUs when first starting X after cold boots. * Fixed a problem that could result in temporary stalls when moving OpenGL application windows on GeForce 8 and later GPUs. * Fixed a bug that prevented VGA fonts from being saved/restored correctly on GeForce 8 and later GPUs. ** Affects: nvidia-graphics-drivers-180 (Ubuntu) Importance: Undecided Status: New -- Stable NVIDIA driver 180.51 released - please upgrade in Jaunty https://bugs.launchpad.net/bugs/364965 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 338083] Re: [Jaunty] MacBook 5.1 will not reboot (Restart).
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] MacBook 5.1 will not reboot (Restart). https://bugs.launchpad.net/bugs/338083 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362760] Re: Only one nvidia temperature can be detected
** 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 detected https://bugs.launchpad.net/bugs/362760 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105291] Re: sensors-applet should recognize newly installed hddtemp
** 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 installed hddtemp https://bugs.launchpad.net/bugs/105291 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364965] Re: Stable NVIDIA driver 180.51 released - please upgrade in Jaunty
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 reason to push for an SRU. I'll see about producing a patch to update the current package for Jaunty. Unfortunately, I can't really fulfill the other requirements of testing it in the current development release of Ubuntu etc since at the moment there is no development release (given Jaunty was just released). Other than a patch against the current 180.44 package in Jaunty I can't really do much else from what I can see, but am happy to do anything else you can suggest to try and get the SRU done. -- Stable NVIDIA driver 180.51 released - please upgrade in Jaunty https://bugs.launchpad.net/bugs/364965 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 230850] Re: sensors-applet ignores /etc/sensors3.conf
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 libsensors3.conf directly, it is done via libsensors. So if there is indeed a bug, it is in libsensors (or lm- sensors package) not sensors-applet. -- sensors-applet ignores /etc/sensors3.conf https://bugs.launchpad.net/bugs/230850 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 230680] Re: sensors-applet reads incorrect output from hddtemp
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120102] Re: Mouseemu uses strange defaults
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 remap them as mouse clicks is too unintuitive. this should be disabled by default, and those that need it can enable it. -- Mouseemu uses strange defaults https://bugs.launchpad.net/bugs/120102 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285815] Re: Backlight keeps getting darker on MacBookPro
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 - do you have access to any other machines which you could provide info for and I'll see what I can do about hacking on the driver. -- Backlight keeps getting darker on MacBookPro https://bugs.launchpad.net/bugs/285815 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285815] Re: Backlight keeps getting darker on MacBookPro
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 that is one candidate I would suggest - problem is that I think we'll need to be able to easily adjust it - I suggest instead what we do initially is add another sysfs file for applesmc called light_scaling or something similar which can by written to by root and that will then be used to scale the light sensor value by the driver - users can then experiment to find a good value - then for each model we can collect the scaling values which users report working well for them an integrate them into a fixed table in the driver - but we can also leave the light_scaling file available so it can be set manually still. What do you reckon? -- Backlight keeps getting darker on MacBookPro https://bugs.launchpad.net/bugs/285815 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285815] Re: Backlight keeps getting darker on MacBookPro
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251830] Re: Mouseemu installed, not wanted
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 more trouble than its worth -- Mouseemu installed, not wanted https://bugs.launchpad.net/bugs/251830 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285815] Re: Backlight keeps getting darker on MacBookPro
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 bytes are a big endian 16-bit value of the ambient light value but is somehow scaled down from the first one and perhaps has a different dynamic range next 2 bytes are a big endian 16-bit value of the ambient light value with a maximum value of 1023 last 2 bytes I got no idea about So I've cooked up a patch to use the value which reports 1023 as max which just basically divides this by 4 to give us a value which we can return with a maximum of 255 like the max value on the older machines. It also seems the right sensor doesn't ever report anything so we just return 0 for this. Please test the attached patch and if possible can this be merged into the applesmc-dkms mactel package? ** Attachment added: "report light sensor value correctly on newer MacBooks" http://launchpadlibrarian.net/21099779/applesmc-dkms-light-sensor-fix.patch -- Backlight keeps getting darker on MacBookPro https://bugs.launchpad.net/bugs/285815 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285815] Re: Backlight keeps getting darker on MacBookPro
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.launchpad.net/bugs/285815 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251830] Re: Mouseemu installed, not wanted
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 breaks a bunch of stuff as mentioned in this bug, and also remaps F11 and F12 which is completely unintuitive and broken. -- Mouseemu installed, not wanted https://bugs.launchpad.net/bugs/251830 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285815] Re: Backlight keeps getting darker on MacBookPro
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 'Use ambient light to adjust LCD brightness' option in g-p-m. Perhaps the light sensor reading is not correct? I am familiar with linux kernel development and debugging (just not on the MacBook Pro - this is my first) am just not too sure where to start debugging this one - any ideas? -- Backlight keeps getting darker on MacBookPro https://bugs.launchpad.net/bugs/285815 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285815] Re: Backlight keeps getting darker on MacBookPro
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 quite low, changing correction_factor to 1 seems to give some appropriate results... I am a little concerned about the 0 reading from the right sensor though - is this something specific to the applesmc driver on MBP 5,1 or is it more indicative of some hardware fault?? -- Backlight keeps getting darker on MacBookPro https://bugs.launchpad.net/bugs/285815 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 287179] Re: Window border is drawed corrupted
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/vbulletin/showthread.php?t=123072 "Fixed a regression that could result in window decoration corruption when running Compiz using Geforce 6 and 7 series GPUs." -- Window border is drawed corrupted https://bugs.launchpad.net/bugs/287179 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 341230] Re: Booting linux crashes on 2009 White Macbook (hardware version ID "MacBook5, 2") unless you use acpi=off
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 341367] Re: Update to 3.1
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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, 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 328529] Re: Ubuntu 8.10 - blueman 1.0 not seeing any devices
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 seeing any devices https://bugs.launchpad.net/bugs/328529 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 332443] [NEW] MacBook Pro 5, 1 bluetooth requires reset before it can be used
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 004 Device 003: ID 05ac:8213 Apple, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x05ac Apple, Inc. idProduct 0x8213 bcdDevice0.07 iManufacturer 1 Apple, Inc. iProduct2 Bluetooth USB Host Controller Attached is a patch for the btusb driver in the linux kernel which ensures the device is reset when the driver is loaded. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Package: linux-image-2.6.27-11-generic 2.6.27-11.27 ProcCmdLine: root=UUID=aebd4f4f-ce67-4806-b4d5-ffb98eb102b3 ro quiet splash crashkernel=384M-2G:6...@16m,2G-:1...@16m ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.27-11.27-generic SourcePackage: linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 332443] Re: MacBook Pro 5, 1 bluetooth requires reset before it can be used
** 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://launchpadlibrarian.net/22939699/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/22939700/Dependencies.txt ** Attachment added: "HalComputerInfo.txt" http://launchpadlibrarian.net/22939701/HalComputerInfo.txt ** Attachment added: "LsUsb.txt" http://launchpadlibrarian.net/22939702/LsUsb.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/22939703/Lspci.txt ** Attachment added: "ProcCpuInfo.txt" http://launchpadlibrarian.net/22939704/ProcCpuInfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/22939705/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/22939706/ProcModules.txt -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 332443] Re: MacBook Pro 5, 1 bluetooth requires reset before it can be used
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
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 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362760] Re: Only one nvidia temperature can be detected
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 194976] Re: sensors-applet crashed with SIGSEGV in g_type_check_instance_is_a()
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337935] Re: [Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty)
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 instead allow bcm5974 to claim it? -- [Jaunty] MacBook 5.1 touchpad not fully supported (Alpha 5 of Jaunty) https://bugs.launchpad.net/bugs/337935 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337947] Re: [Jaunty] No sound output with MacBook 5.1
@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 'Channel Source' (sorry again I can't really remember what the option is called). This should then provide an option back in the volume control dialog to select either 2 or 6 channel. Also make sure you enable 'Line Out' and set the line out volume (since this controls the volume of the speakers). You should then get sound out of atleast the right speaker - the left one doesn't appear to work - see bug https://bugs.edge.launchpad.net/ubuntu/+source/alsa-driver/+bug/337314 -- [Jaunty] No sound output with MacBook 5.1 https://bugs.launchpad.net/bugs/337947 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 337314] Re: Left speaker doesn't work, controls mixed up on Apple MacBook[Pro] (5, 1)
@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 fixed. Also any ideas you have as to how to go about fixing this would be great as I can try and implement any possible solution that you might think of, but I don't have any real experience with the linux sound system (let alone the hda driver) to even know where to begin looking to try and solve this so any pointers / hints you could give would be greatly appreciated. -- 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285815] Re: Backlight keeps getting darker on MacBookPro
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. -- Backlight keeps getting darker on MacBookPro https://bugs.launchpad.net/bugs/285815 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51575] Re: Applet crash at startup
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 pointer is now referencing NULL, yet it is never re-assigned so I can only assume another call somewhere is overwriting the local pointer... Unfortunately I cannot reproduce the bug myself, so I am going to need to get you to try and track it down for me. Can you please provide as much info about your system as possible: What architecture are you using (amd64, x86 etc)? Which version of Ubuntu are you using? Did you do a clean install of it (Ubuntu) or upgrade from breezy? Which version of gcc are you using? What sensors interfaces are you using? Could you also please post the output when running /usr/libexec/sensors- applet from the command line - this would be very handy? And any other info you could give would be great. Have any other versions of sensors-applet worked for you? There could also be perhaps some misconfiguration with gnome-panel or gconf, so if you could try creating a new test user on your system, and running the applet as that new user that would be good (this should rule out any issues with old configuration data etc). Thanks Alex (developer of Sensors Applet) -- 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
[Bug 51575] Re: Applet crash at startup
@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://launchpad.net/bugs/51575 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51575] Re: 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 https://launchpad.net/bugs/51575 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51575] Re: Applet crash at startup
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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51575] Re: 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
[Bug 45547] Re: normal font label is misaligned according to others applets and menus in gnome panel
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/mailman/listinfo/ubuntu-bugs
[Bug 51575] Re: [Bug 51575] Re: Applet crash at startup
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-22 at 00:02 +, Sam Morris wrote: > 1.7.7 is now in Debian, hopefully it will be pulled into Ubuntu soon > > ** Changed in: sensors-applet (Ubuntu) >Status: Needs Info => Fix Committed > -- 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
[Bug 66474] Re: dvipdfm segfaults every time
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65298] Re: Fail to build with emacs-snapshot
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
[Bug 54643] Re: Crasher: auto-fill in comments crashes emacs
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-bugs
[Bug 60023] emacs-snapshot-gtk regularly crashes on edgy amd64
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 during auto-fill actions, and these are most likely related to bug #54643 [Crasher: auto-fill in comments crashes emacs]. Is there any chance an updated version from Debian can be synced to the edgy tree to try and resolve some of these issues, as emacs- snapshot is unusable at the moment. ** Affects: emacs-snapshot (Ubuntu) Importance: Untriaged Status: Unconfirmed -- emacs-snapshot-gtk regularly crashes on edgy amd64 https://launchpad.net/bugs/60023 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66474] Re: dvipdfm segfaults every time
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
[Bug 48935] Re: No thermal monitor support on AMD X2
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
[Bug 66474] dvipdfm segfaults every time
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: Undecided Status: Unconfirmed -- 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
[Bug 66474] Re: dvipdfm segfaults every time
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 Gentoo Bugzilla http://bugs.gentoo.org/show_bug.cgi?id=94901 BTW - I tried linking this bug report to the Gentoo one (using the +Upstream link) but wasn't sure which "Product" I needed to specify since tetex or any of its derivates are not listed to be able to choose from, and since this is a required field, I couldn't do it. -- 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
[Bug 66474] Re: dvipdfm segfaults every time
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 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 + pretty sure will fix it.. patch is attached later in comments. -- 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
[Bug 94558] Re: gnome sensors applet 1.7.10 does not save changed preferences
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 85635] Re: Volumes change name when mounted/unmounted in Nautilus
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 because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147188] Re: Sensors-applet report Core 2 Duo temp as A (Ampere)
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147188] Re: Sensors-applet report Core 2 Duo temp as A (Ampere)
@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 latest version, rather than one that is 2 versions old. -- 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147188] Re: Sensors-applet report Core 2 Duo temp as A (Ampere)
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/sensors-applet-patch-LP147188 -- 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147188] Re: Sensors-applet report Core 2 Duo temp as A (Ampere)
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 have CC-BY-SA 2.5 license as far as I know, so there is no real need to restrict it. Besides, the old icons look extremely poor and unintegrated with the standard Ubuntu desktop compared to the newer ones. Besides, to ship the old ones requires more work for distributions since they must replace the ones shipped in the source tarball. -- 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147188] Re: Sensors-applet report Core 2 Duo temp as A (Ampere)
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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147188] Re: Sensors-applet report Core 2 Duo temp as A (Ampere)
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. -- 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69800] Re: Please package original icons from source
@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.net/bugs/69800 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 147188] Re: Sensors-applet report Core 2 Duo temp as A (Ampere)
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 => Confirmed -- 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115685] Re: Sensors Applet doesn't remember Preferences
*** 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.launchpad.net/bugs/115685 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114804] Re: sensor-applet starts showing wrong devices
*** 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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176589] Re: compiz randomly freezes X
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 different sucessive backtraces, each of which is similar - so it seems like compiz is perhaps doing something - I will attach the first 3 or so. This was reproduced using the method described in comment https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/176589/comments/31 and the stack trace was taken about 2 minutes after the lockup - it took me that long to fire up my second computer and ssh in to grab the stacktrace. Am happy to keep reproducing and to provide more stack traces if needed. ** Attachment added: "backtrace of compiz during lockup" http://launchpadlibrarian.net/13585868/compiz-backtrace-2008.04.20.16.06.12-6157.txt -- compiz randomly freezes X https://bugs.launchpad.net/bugs/176589 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176589] Re: compiz randomly freezes X
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 little debugging info. ** Attachment added: "another stacktrace - completely different" http://launchpadlibrarian.net/13585898/compiz-backtrace-2008.04.20.16.06.42-6157.txt -- compiz randomly freezes X https://bugs.launchpad.net/bugs/176589 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200449] Re: i8k fan speed values are wrong
** 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124934] Re: Warning colors limits must be configurable / device specific
** 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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105291] Re: sensors-applet doesn't recognize newly installed hddtemp
@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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124934] Re: Warning colors limits must be configurable / device specific
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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124934] Re: Warning colors limits must be configurable / device specific
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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105291] Re: sensors-applet doesn't recognize newly installed hddtemp
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 fly (instead of at startup) would make it too processor intensive for nomal use - ie. to have it continously scanning for new additions.. -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94558] Re: gnome sensors applet 1.7.10 does not save changed preferences
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-applet (or if you compiled from source /usr/libexec/sensors-applet) and then add it to the panel, and finally go open and close the prefs dialog, that'd be great. -- 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 list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59945] Re: no nvidia support
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/59945 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178255] NVCtrl.h and NVCtrlLib.h should be installed in /usr/include/NVCtrl not /usr/include
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 or build with nvidia support. nvidia-settings (1.0+20070502-1ubuntu3) hardy; urgency=low * Install NVCtrl.h and NVCtrlLib.h in debian/rules. * Add usr/include to debian/dirs. * With these changes, it will be possible to build sensors-applet with support for nvidia hardware, see LP: #59945. Could the install path for these 2 headers please be changed, since this (/usr/include/NVCtrl) is more standard for other distro's as well (ie Fedora and Gentoo both use this instead). ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New -- NVCtrl.h and NVCtrlLib.h should be installed in /usr/include/NVCtrl not /usr/include https://bugs.launchpad.net/bugs/178255 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99209] Re: sensors-applet bad display
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-applet loads the old list of sensors, which are wrong since libsensors has changed the name of the chip, but we also detect these 'new' sensors and show them as well - hence each gets listed twice, and all display error since libsensors has changed the name of the chip and the old ones are invalid. You can try removing the applet and readding it to your panel which will get rid of the old sensors list. This should really be filed as a bug against libsensors in that case. -- sensors-applet bad display https://bugs.launchpad.net/bugs/99209 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114804] Re: sensor-applet starts showing wrong devices
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200097] Re: sensors-applet crashed with SIGSEGV in g_list_first()
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-applet crashed with SIGSEGV in g_list_first() https://bugs.launchpad.net/bugs/200097 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109498] hddtemp is broken on sata drives for 2.6.20 kernel
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_SG_IO(device, cdb, sizeof(cdb), buffer, cmd[3] * 512, sense, sizeof(sense), dxfer_direction); - /* Verify SATA magics */ - if (sense[0] != 0x72 || sense[7] != 0x0e || sense[9] != 0x0e || sense[10] != 0x00) + /* Verify SATA magic */ + if (sense[0] != 0x72) return 1; else return ret; Perhaps we should just sync to latest version? ** Affects: hddtemp (Ubuntu) Importance: Undecided Status: Unconfirmed -- hddtemp is broken on sata drives for 2.6.20 kernel https://bugs.launchpad.net/bugs/109498 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109498] Re: hddtemp is broken on sata drives for 2.6.20 kernel
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. -- hddtemp is broken on sata drives for 2.6.20 kernel https://bugs.launchpad.net/bugs/109498 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94558] Re: gnome sensors applet 1.7.10 does not save changed preferences
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
@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 hard drive which at the moment can't even be ejected - and the same is occurring for anumber of other users - see bug #99498 - which is a pretty bad regression as they can only me unmounted / ejected from the command-line So I agree - in general we should only eject those devices which NEED ejection - ipods and the like - but those which can be happily unmounted - usb flash and hard drives to name a few - should NOT require eject... -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
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 account for it - ie. I can only eject the device from the command line if I use sudo, but it cannot be ejected using nautilus or the drive-mount applet or using eject as a normal user and thus this problem would appear to be some sort of permissions problem... -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
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 ejected... ** Attachment added: "g-v-, log when connecting thumb drive" http://librarian.launchpad.net/7336296/gvm.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 bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
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 bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
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/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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
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 bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
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 user [EMAIL PROTECTED]:~$ id haldaemon uid=107(haldaemon) gid=112(haldaemon) groups=112(haldaemon),24(cdrom),25(floppy),46(plugdev),113(powerdev) [EMAIL PROTECTED]:~$ uname -a Linux navajo 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
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/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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63090] Re: do not eject all USB/Firewire devices
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
