[Bug 248870] Re: Autosave causes document to scroll back to cursor position
I can reproduce something similar with 8.10 by means of creating a table, putting the cursor into the table and typing at least one letter into the table. When moving away from the table to a different page with the mouse scroll wheel, openoffice goes back to the cursor when pressing the "save file" button. I guess this also happens with autosave. ** Changed in: openoffice.org (Ubuntu) Status: Invalid => New -- Autosave causes document to scroll back to cursor position https://bugs.launchpad.net/bugs/248870 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 427046] Re: modem 3g not seen on boot
I have the same problem that the 3g modem is not detected. See attached the syslog output when the modem is not detected by network-manager. Since I cannot post more than one file using the web-gui I will post a second syslog file in the next message... ** Attachment added: "syslog when 3g fails to be detected" http://launchpadlibrarian.net/34859889/nov01.syslog -- modem 3g not seen on boot https://bugs.launchpad.net/bugs/427046 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 427046] Re: modem 3g not seen on boot
It is not always the case that the 3g modem is not detected. See attached a case when it is successfully detected. As mentioned before the order of the messages (actions) in the syslog is different. Maybe this helps to pinpoint the problem. Other observations: 1) the 3g modem detection appears to be less reliable when there are a lot of WLANs nearby. Maybe NetworkManager is delayed when there are lots of WLANs available. Nevertheless this appears to be a race condition, probably caused by the usage of upstart? 2) after suspend the 3g modem is very likely to be successfully detected. My PC is a ASUS eeepc 901A with an integrated 3g modem (Huawei EM770, HSDPA+HSUPA). ** Attachment added: "syslog when 3g modem is detected successfully" http://launchpadlibrarian.net/34860354/oct31.syslog -- modem 3g not seen on boot https://bugs.launchpad.net/bugs/427046 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 527624] [NEW] n900 in PC Suite Mode causes karmic to crash at startup
Public bug reported: I own a N900 and have it attached to my PC in order to charge it and in order to use it as a UMTS modem. http://maemo.nokia.com/n900/ Steps to reproduce the bug 1) Start ubuntu without the N900 attached 2) Plug the N900 using the USB cable and put it in "PC Suite Mode" 3) Reboot 4) During the Reboot the kernel will crash Providing more info about this bug is almost impossible 1) the "fancy" splash screen hides information (if any) 2) I followed the instructions on https://wiki.ubuntu.com/KernelTeam/CrashdumpRecipe only to find out that the ddebs are not available anymore! 3) I compiled the ddebs myself but get following error from apport-retrace $ apport-retrace -s -R /var/crash/linux-image-2.6.31-19-generic.0.crash --- stack trace --- Traceback (most recent call last): File "/usr/bin/apport-retrace", line 286, in print report['Stacktrace'] File "/usr/lib/python2.6/UserDict.py", line 22, in __getitem__ raise KeyError(key) KeyError: 'Stacktrace' 4) I also tried "crash" but this gives following error crash: invalid structure size: x8664_pda FILE: x86_64.c LINE: 584 FUNCTION: x86_64_cpu_pda_init() [/usr/bin/crash] error trace: 452b8f => 4de65b => 4e0114 => 51e645 51e645: SIZE_verify+180 4e0114: (undetermined) 4de65b: x86_64_init+3218 452b8f: main_loop+152 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- n900 in PC Suite Mode causes karmic to crash at startup https://bugs.launchpad.net/bugs/527624 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 527624] Re: n900 in PC Suite Mode causes karmic to crash at startup
$ lsb_release -rd Description:Ubuntu 9.10 Release:9.10 Package Name: linux-image-2.6.31-19-generic ** Attachment added: "uname-a.log" http://launchpadlibrarian.net/39758764/uname-a.log -- n900 in PC Suite Mode causes karmic to crash at startup https://bugs.launchpad.net/bugs/527624 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 527624] Re: n900 in PC Suite Mode causes karmic to crash at startup
** Attachment added: "version.log" http://launchpadlibrarian.net/39758778/version.log -- n900 in PC Suite Mode causes karmic to crash at startup https://bugs.launchpad.net/bugs/527624 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 527624] Re: n900 in PC Suite Mode causes karmic to crash at startup
** Attachment added: "dmesg.log" http://launchpadlibrarian.net/39758790/dmesg.log -- n900 in PC Suite Mode causes karmic to crash at startup https://bugs.launchpad.net/bugs/527624 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 527624] Re: n900 in PC Suite Mode causes karmic to crash at startup
The dmesg.log and the lspci-vnvn.log were performed without the N900 attached. ** Attachment added: "lspci-vnvn.log" http://launchpadlibrarian.net/39758840/lspci-vnvn.log -- n900 in PC Suite Mode causes karmic to crash at startup https://bugs.launchpad.net/bugs/527624 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 566812] Re: USB Modem wont connect after modem hangup
I have the same problem. This error appears after reconnecting a few times. The error is more frequent if the connection fails once due to GSM network problems. After the error appears the modem does not work again until I kill the "modem-manager". IMHO following log message is the most important one: Apr 19 18:04:44 laptop-hostname NetworkManager: stage1_prepare_done(): GSM modem connection failed: (32) Sending command failed: device is not enabled I have no clue what "device is not enabled" means, but it apparently prevents the modem from being used. ** Also affects: modemmanager Importance: Undecided Status: New -- USB Modem wont connect after modem hangup https://bugs.launchpad.net/bugs/566812 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 527624] Re: n900 in PC Suite Mode causes karmic to crash at startup
I tested the restart behavior of lucid also with my n900 in pc-suite mode. As far as I can see the result is the same as for karmic, the kernel crashes. ** Changed in: linux (Ubuntu) Status: Expired => New -- n900 in PC Suite Mode causes karmic to crash at startup https://bugs.launchpad.net/bugs/527624 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 527624] Re: n900 in PC Suite Mode causes karmic to crash at startup
I managed to get a kernel backtrace since the ddeb for the current lucid kernel is currently available at ddebs.ubuntu.com. ** Attachment added: "kernel backtrace" http://launchpadlibrarian.net/49651397/crash.txt -- n900 in PC Suite Mode causes karmic to crash at startup https://bugs.launchpad.net/bugs/527624 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 372218] Re: XFS filesystem - delete large files doesn't update free diskpace
Unix-like operating system don't delete a file on a disk until the last filehandle to the file is closed. Therefore, for log-files you also have to restart the respective daemon (e.g. apache) to have the disk space actually freed. Rebooting the system has the same effect for obvious reasons. -- XFS filesystem - delete large files doesn't update free diskpace https://bugs.launchpad.net/bugs/372218 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 300143] Re: tablet devices show up as non-functional joysticks
I have to second the posting of sothis. I have an Saitek X52pro joystick and cannot use it on jaunty with kernel 2.6.28-15-generic because no /dev/input/js0 device is created! The same joystick works with 2.6.28-14-generic. -- tablet devices show up as non-functional joysticks https://bugs.launchpad.net/bugs/300143 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 300143] Re: tablet devices show up as non-functional joysticks
I don't know if this is the right place to report following bug:
On karmic my X52 pro is not detected again. It appears that the
regression is still active in karmic.
linux-source-2.6.31/drivers/input/joydev.c:854
static const struct input_device_id joydev_blacklist[] = {
/* ... snip */
{
.flags = INPUT_DEVICE_ID_MATCH_EVBIT |
INPUT_DEVICE_ID_MATCH_KEYBIT,
.evbit = { BIT_MASK(EV_KEY) },
.keybit = { [BIT_WORD(BTN_DIGI)] = BIT_MASK(BTN_DIGI) },
}, /* Avoid tablets, digitisers and similar devices */
{ } /* Terminating entry */
};
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
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 175988] Re: netstat lacks -W wide columns option
When I try netstat -W on karmic I actually get "wide" output. Should it be called "fixed" then? -- netstat lacks -W wide columns option https://bugs.launchpad.net/bugs/175988 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 336418] Re: Please merge lm-sensors 3.1.1-4 (main) from Debian unstable (main)
My ASUS M3A32 Board has an it87 sensor on it worked fine on intrepid. With karmic it does not work anymore. Bug#418246 appears to have a solution (adding a kernel option acpi_enforce_resources=lax) but this can be very dangerous according to http://marc.info/?l=linux- kernel&m=125043293401414. The correct solution is to use the asus_atk0110 driver which is correctly loaded by karmic but not supported by lm-sensors-3.0.2 but only starting with 3.1.x. Therefore it is important to merge at least lm-sensors 3.1.1 into karmic! -- Please merge lm-sensors 3.1.1-4 (main) from Debian unstable (main) https://bugs.launchpad.net/bugs/336418 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 730478] [NEW] Intuos 4 touch ring and buttons unusable on Lucid
Public bug reported: The wacom Intuos 4 tablets (S, M, L and XL) have 6-8 buttons and a so- called "touch ring". On my tablet they show up as "Wacom Intuos4 8x13 pad". Due to a bug in xf86-input-wacom, all events of these buttons and "touch ring" end up with the coordinates x=0,y=0 on the screen. The mouse cursor is hence positioned on the top-leftmost position on the screen, basically rendering the pad device useless. This bug has been fixed in xf86-input-wacom-0.10.6 (commit 2038ad187823b770fcb3b5e77dacf4bad27617e6 "Always put the pad in relative mode"), but Lucid has xf86-input-wacom-0.10.5 ** Affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730478 Title: Intuos 4 touch ring and buttons unusable on Lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730488] [NEW] [Lucid] xf86ScaleAxis problems with high resolution devices
Public bug reported: Binary package hint: xorg The xf86ScaleAxis function is used to scale x and y axis values of input devices between different resolutions. Due to internal integer overflow, the acceptable value range for its arguments are limited below their type (signed 32bit integer). This imposes a problem for high resolution devices, like the wacom Intuos 4 L, which have a total horizontal resolution of 65024. Example: when doing a scaling with a range of more than 46340 (Sxhigh-Sxlow), the integer X will wrap into negative values, and truncated to 0 at the end. Among other devices, this problem affects wacom Intuos 4 L and XL tablets when compiling the xf86-input-wacom driver version 0.10.9 and above. Previous versions work, because they don't use the xf86ScaleAxis function. With current xorg releases this problem does not happen either, because a upstream patch (http://lists.x.org/archives/xorg- devel/2010-April/007333.html) already extends the acceptable value range. A solution would be to include this patch into 10.04, because there is still quite a time till the next LTS. If there is a chance for getting this patch included into 10.04 I'm willing to make a patch specific for the current xorg-server-1.7.6 package and test it. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730488 Title: [Lucid] xf86ScaleAxis problems with high resolution devices -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730488] Re: [Lucid] xf86ScaleAxis problems with high resolution devices
** Patch added: "Patch from the xorg repository" https://bugs.launchpad.net/bugs/730488/+attachment/1891113/+files/xf86-scale-high-resolution.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730488 Title: [Lucid] xf86ScaleAxis problems with high resolution devices -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730488] Re: [Lucid] xf86ScaleAxis problems with high resolution devices
I've read some SRU related documentation and decided to supply a debdiff. I did not yet test it. I'm quite new to this stuff, so is this the way to go? ** Patch added: "debdiff from applied patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/730488/+attachment/1892854/+files/xorg-server_1.7.6-2ubuntu7.5.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730488 Title: [Lucid] xf86ScaleAxis problems with high resolution devices -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730488] Re: [Lucid] xf86ScaleAxis problems with high resolution devices
I tested the new xserver-common 2:1.7.6-2ubuntu7.6 and it works perfectly. Steps 1) Compiled and (make-) installed xf86-input-wacom-0.10.10. 2) Restarted x-server: Stylus cursor wraps to zero 3) Activated lucid-proposed in update-manager and performed update 4) Restarted computer: Stylus cursor usable over total x-axis Thanks for the fast inclusion into lucid-proposed. From now on I will use the new xserver and report problems in case I find any. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730488 Title: [Lucid] xf86ScaleAxis problems with high resolution devices -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 765230] Re: long sleep in boot process
I have the same problem with my ASUS setup. mainboard: M3A32-MVP DELUXE cpu: AMD Phenom(tm) II X4 940 Processor ram: 8GB gpu: GeForce 8800 GTS 512 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/765230 Title: long sleep in boot process -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783097] [NEW] USB 3.0 devices not working behind USB 3.0 HUBs
Public bug reported: I have both a Western Digital MyPassport Essential 500GB harddisk and a Seagate FreeAgent GoFlex Desk 2TB working ok on my ASUS U3S6 XHCI controller in USB 3.0 mode. Currently I'm using ubuntu 10.04 (Lucid). When I disconnect the devices, and connect a USB 3.0 hub (DeLock USB 3.0 External HUB 4 Port), the HUB is detected by linux, but no USB 3.0 devices (i.e. the mentioned HDDs) connected to said HUB. USB 2.0 devices connected to the HUB are detected and working properly, though. When connecting the hub, 2109:0810 and 2109:3431 appear in "lsusb". I've got the HUB working in 3.0 mode by means of compiling a kernel from git: dbe79bbe9dcb22cb3651c46f18943477141ca452 (USB 3.0 Hub Changes). I'm not 100% sure if this is the exact commit enabling USB 3.0 HUB operation, but there is strong evidence for it. If this is "the fix", the next ubuntu release (11.10) will likely support USB 3.0 HUBs "out of the box". In addition to 10.04, I also tried the HUB on 11.04 (natty), observing the same problem. For now I'll omit the "default" system information, because I believe the problem is not related to my particular hardware setup. If you request, I'm happy to submit this information too. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783097 Title: USB 3.0 devices not working behind USB 3.0 HUBs -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 730488] Re: [Lucid] xf86ScaleAxis problems with high resolution devices
Hi Yvon The patch makes no change to the ABI nor API. Reading your description I get the impression, the most likely reason for the failure is that the AMD driver overwrites some packaged file of the xorg-server. If there is any update of the xorg-server, it gets re-set to the "clean" state, and is therefore not able to load the Radeon driver anymore. If this is correct, any security update of xorg-server would have the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/730488 Title: [Lucid] xf86ScaleAxis problems with high resolution devices -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 643154] Re: upgrade to maverick interrupted due to overlapping dialog box
I had the same problem at upgrading to maverick. Please find attached my log files. ** Attachment added: "apt.log" https://bugs.launchpad.net/ubuntu/+bug/643154/+attachment/1690116/+files/apt.log -- upgrade to maverick interrupted due to overlapping dialog box https://bugs.launchpad.net/bugs/643154 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 643154] Re: upgrade to maverick interrupted due to overlapping dialog box
** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+bug/643154/+attachment/1690117/+files/history.log -- upgrade to maverick interrupted due to overlapping dialog box https://bugs.launchpad.net/bugs/643154 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 643154] Re: upgrade to maverick interrupted due to overlapping dialog box
** Attachment added: "term.log" https://bugs.launchpad.net/ubuntu/+bug/643154/+attachment/1690118/+files/term.log -- upgrade to maverick interrupted due to overlapping dialog box https://bugs.launchpad.net/bugs/643154 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 643154] Re: upgrade to maverick interrupted due to overlapping dialog box
One additional note: Some time before the system upgrade I did a minor modification to the grub configuration. Apparently, the update process wants to ask which version of the configuration to install. But due to some unknown reason, the window manager is not useable at that time. ** Attachment added: "main.log" https://bugs.launchpad.net/ubuntu/+bug/643154/+attachment/1690119/+files/main.log ** Changed in: ubiquity (Ubuntu) Status: Incomplete => New -- upgrade to maverick interrupted due to overlapping dialog box https://bugs.launchpad.net/bugs/643154 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 598872] [NEW] No support for Atheros AR3011 Bluetooth
Public bug reported: I have a mini USB Bluetooth V2.1+EDR dongle from DeLock which appears to have the AR3011 chip on it. It is not supported by ubuntu yet (kernel 2.6.32-22). Atheros has provided a driver for this chip: http://lwn.net/Articles/363557/ Since Lucid is a LTS release it should provide support for this device. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- No support for Atheros AR3011 Bluetooth https://bugs.launchpad.net/bugs/598872 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 598872] Re: No support for Atheros AR3011 Bluetooth
As I wrote, this "Bug" affects Lucid. I guess the Chip will work with Maverick since it works since 2.6.33. I have compiled a vanilla 2.6.33.5 kernel and can confirm that it works. It is just that Lucid is a LTS release and should IMHO therefore support this Bluetooth dongle. -- No support for Atheros AR3011 Bluetooth https://bugs.launchpad.net/bugs/598872 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
