Bug#858760: nautilus: "Format..." function gives no feedback while creating filesystem, no way to know if it is finished

Package: nautilus Version: 3.14.1-2 Severity: normal Dear Maintainer, I wanted to encrypt a new USB flash drive. I plugged in the drive and chose "Open in Files". Next in Files I right-clicked on the mounted device and chose "Format...". The dialog opened correctly and allowed me to select

Bug#690734: Perhaps wider distribution of this info...?

I am really glad I thought to look in the BTS for this package for my problem because nowhere else on the web can the information required to get this working be found. I was getting problems with missing symbols. A google search turned up the fact that the LD_LIBRARY_PATH and LD_PRELOAD need some

Bug#661253: Thanks!

Using snapshot.debian.org got me sorted with a downgrade! Now to see if that actually solves the problem for me... :-) I've been using Debian since 1995 and I didn't know that resource was there. Thanks for the tip! Mark -- To UNSUBSCRIBE, email to

Bug#661253: Same problem here

I am seeing same problem here on self-built (2+ years ago) amd64 machine. Have been running fine using wheezy with nvidia driver for ages, latest upgrade to 295.20-1 causing these random X server crashes and hence logouts, essentially rendering the machine unusable in graphical mode. From

Bug#631620: there may be things you could help with

On Sat, Jul 23, 2011 at 5:57 PM, Cristian Ionescu-Idbohrn cristian.ionescu-idbo...@axis.com wrote: Bug #626975 may give you some ideas. The result from 'lsusb' paired with the rules in /lib/udev/rules.d/*hid2hci.rules may be a start point. Well the first thing I notice is that the rules in

Bug#631620: there may be things you could help with

On Sun, Jul 24, 2011 at 8:36 PM, Mark Fletcher mark2...@gmail.com wrote: On Sat, Jul 23, 2011 at 5:57 PM, Cristian Ionescu-Idbohrn cristian.ionescu-idbo...@axis.com wrote: Bug #626975 may give you some ideas. Further follow-up. I've just found something very interesting indeed. Using

Bug#631620: bluez: Logitech keyboard problem is back in 4.94-2

Package: bluez Version: 4.94-2 Severity: important Just upgraded bluez to 4.94-2 as it came into testing sometime this week, and my Logitech bluetooth keyboard and mouse combo (MX5500) stopped working again. I have rolled back to a known working version (4.66-3). I know there was an upgrade

Bug#588034: bluez: Also affecting Logitech MX5500 combo

Package: bluez Severity: normal I can confirm this bug in 4.66-1 and that downgrading to 4.63-2 fixes it. I am using a Logitech MX5500 bluetooth keyboard and mouse combo. The changes in the udev rules file don't look to me like the culprit, but I can't for the life of me figure out what is. --

Bug#589388: This problem isn't down to udev...

Package: udev Severity: normal Please close this bug report. Looks like the problem is actually in bluez not udev. When I downgrade bluez to 4.63-2 from 4.66-1, problem goes away. Thanks Mark -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500,

Bug#589388: udev: Logitech Keyboard Problem AGAIN with 160-1

Package: udev Version: 160-1 Severity: important Following advice in bug #588469 I upgraded udev and libudev to 160-1 (everything else on machine is squeeze). This did not immediately fix the problem (for Logitech MX 5500 wireless keybard and mouse combo). On a hunch I rebooted the machine