I had the same issue after a beta install, and upgrade to final.
Removing the ~/.cache/gestreamer-1.0 folder, as proposed by snerge, also
solved the problem on my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Hi Chuck
i try it, but i will describe something additional ...
First, i wanted to update my current system with the corresponding
menuitem 'System->Systemverwaltung->Aktualisierungsverwaltung'
The update begann ... there will be an update of the mysql-server-5.1
package ... while running dpkg d
** Attachment added: ".etc.apparmor.d.usr.sbin.mysqld.txt"
http://launchpadlibrarian.net/49197545/.etc.apparmor.d.usr.sbin.mysqld.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49197547/Dependencies.txt
** Attachment added: "Df.txt"
http://launchpadlibrarian.n
Public bug reported:
Hallo
über die Aktualisierungsverwaltung wurde mir u.a. ein Update von MySQL
angeboten.
Das habe ich dann auch durchführen wollen.
Die Installation der herunter geladenen Dateien beginnt aber bei dem Paket
mysql-server-5.1 hängt sich der Prozess auf, bzw. gibt keine Rückmel
The Drei-branded software of the v3xx really seems to cause the problem
with NM.
I've debranded my phone today, flashed it with the original Motorola
firmware, and everything works as expected now.
--
NM 0.7: Motorola V3xx HSDPA phone not detected by probe code (fdi attached)
https://bugs.launch
I did some more tests today.
I've tried to connect with a minimal wvdail.conf as discribed in the
wiki on NetworkManager/Hardware/3G/Probing:
Modem = /dev/ttyACM0
Baud = 115200
Init = ATZ
Init2 = AT+CGDCONT=1,"IP","drei.at"
Phone = *99#
Username = dummy
Password = dummy
and I get the same "No ca
I've installed 8.10 beta today and I'm also trying to get connected with
my V3xx.
My phone has not been dedected by NM, so I've created the 10-modem.fdi as
posted above. Now NM dedects my phone after pluggin it in. At the configuration
I've selected my provider (Austria/Drei), so far everything
** Attachment added: "lshal.txt"
http://launchpadlibrarian.net/9669903/lshal.txt
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
** Attachment added: "devices.txt"
http://launchpadlibrarian.net/9669892/devices.txt
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/9669897/dmesg.txt
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
** Attachment added: "udev log when die password dialog pops up, but the disk
won't be mountet"
http://launchpadlibrarian.net/9669889/udev.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a
** Attachment added: "gvm log when die password dialog pops up, but the disk
won't be mountet"
http://launchpadlibrarian.net/9669868/gvm.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a m
** Attachment added: "udev log when the password dialog does not pop up"
http://launchpadlibrarian.net/9669866/udev.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "udev log of the first correcty working session (mounting
and unmounting the disk)"
http://launchpadlibrarian.net/9669849/udev-working.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification
** Attachment added: "gvm log of the first correcty working session (mounting
and unmounting the disk)"
http://launchpadlibrarian.net/9669789/gvm-working.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification be
** Attachment added: "gvm log when the password dialog does not pop up"
http://launchpadlibrarian.net/9669861/gvm.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
Binary package hint: gnome-mount
I'm using a luks encryped USB-HDD, which worked perfectly with Feisty.
But with Gutsy the HDD does not get automounted reliably.
Most oft the time it just works for the first time when the HDD is plugged in.
Which means:
* plug in the HDD, w
17 matches
Mail list logo
