[Bug 317474] Re: [Intrepid] Dell V505 AIO-Printer does not print
On Jaunty with kernel 2.6.28-14.18 and cups 1.3.9-17ubuntu3.2 there is no problem printing. -- [Intrepid] Dell V505 AIO-Printer does not print https://bugs.launchpad.net/bugs/317474 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 352269] Re: gnome-keyring-daemon stalls after upgrading to jaunty beta
I hope this is the right report. ** Attachment added: gdb-gnome-keyring.txt http://launchpadlibrarian.net/24621997/gdb-gnome-keyring.txt -- gnome-keyring-daemon stalls after upgrading to jaunty beta https://bugs.launchpad.net/bugs/352269 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 352269] [NEW] gnome-keyring-daemon stalls after upgrading to jaunty beta
Public bug reported:
Binary package hint: gnome-keyring
After upgrading to jaunty gnome-keyring-daemon wound not run. Trying to
save any passwords (e.g. mail-notification) it would say it could not
save any. When I followed the instructions in another forum saying one
should remove ~/.gnome2/keyrings folder and restart, it firstly went
well letting gnome-keyring-daemon come up again and save passwords.
After another update (uptodate version from ubuntu repositories) it,
however, started stalling again after I logged into my account. Now,
even the solution mentioned above does not work anymore.
Starting gnome-keyring-daemon from console shows the following error
message:
** Message: couldn't set environment variable in session: The name
org.gnome.SessionManager was not provided by any .service files
GNOME_KEYRING_SOCKET=/tmp/keyring-2cOEK8/socket
SSH_AUTH_SOCK=/tmp/keyring-2cOEK8/socket.ssh
GNOME_KEYRING_PID=5785
I started this bug report using apport ('ubuntu-bug gnome-keyring').
Hopefully, the report is attached to this entry.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: gnome-keyring 2.26.0-0ubuntu3
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-keyring
Uname: Linux 2.6.28-11-generic i686
** Affects: gnome-keyring (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
gnome-keyring-daemon stalls after upgrading to jaunty beta
https://bugs.launchpad.net/bugs/352269
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 352269] Re: gnome-keyring-daemon stalls after upgrading to jaunty beta
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24565107/Dependencies.txt -- gnome-keyring-daemon stalls after upgrading to jaunty beta https://bugs.launchpad.net/bugs/352269 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 144730] Re: CAPI/ISDN driver does not work in gutsy
Thanks for your feedback (and being in the same sort of trouble for my probs I had with ISDN and feisty were pretty much left open). Well, at least your workaround works fine. I am, though, totally not sure if that is what we have to put up with, especially since I am not able to establish an ISDN-based internet connection over gnome's network applet. After having installed the packages mentioned above in either, feisty or edgy, I was able to use the device '/dev/isdn'. Using gutsy, however, this device does not even appear. -- CAPI/ISDN driver does not work in gutsy https://bugs.launchpad.net/bugs/144730 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 144730] CAPI/ISDN driver does not work in gutsy
Public bug reported: Binary package hint: capiutils On the most recently updated gutsy release I have been experiencing a pretty severe problem with - I guess - the 'capiutils' package. I have not been able to use my AVM Fritz!Card PCI v2.0 installing it as follows: Packages: avm-fritz-firmware avm-fritz-firmware-2.6.22-12 (3.11+2.6.22.4-12.3) capiutils (1:3.10.20070306-0ubuntu3) libcapi20-3 (1:3.10.20070306-0ubuntu3) pppdcapiplugin (1:3.10.20070306-0ubuntu3) /etc/modules: capi capidrv In /etc/isdn/capi.conf I uncommented the 'fcpci' line. I then experienced problems shutting down/ rebooting my computer as it would hang up and basically do nothing. At that time I didn't associate that problem with ISDN/Capi. When I recently decided to uninstall ISDN support (packages mentioned above) I could narrow the problem down to the 'capiutils' and 'libcapi20-3' packages as they would cause a system wide hang-up whereas the other ones would just uninstall fine. I would have liked to include some log files, though I don't know which ones to attach. Please let me know if you need more information (and please be detailed since I'm not that experienced). ** Affects: isdnutils (Ubuntu) Importance: Undecided Status: New -- CAPI/ISDN driver does not work in gutsy https://bugs.launchpad.net/bugs/144730 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 70871] Re: Crash while trying to save the ISDN Config
Still network-admin would shut down without saving anything if I tried to set up a ISDN based connection. -- Crash while trying to save the ISDN Config https://bugs.launchpad.net/bugs/70871 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
You're right. It's similar to bug #94558 and can be solved with the stated solution. -- 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 114804] sensor-applet starts showing wrong devices
Public bug reported: Binary package hint: sensors-applet Using Feisty GNOME sensor-applet always starts with same devices selected. Even though I have changed the devices to show, it would start with the inital devices after logging out and in again. ** Affects: sensors-applet (Ubuntu) Importance: Undecided Status: Unconfirmed -- 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 70871] Re: Crash while trying to save the ISDN Config
I just tried to backtrace the error using the instructions as given on https://wiki.ubuntu.com/Backtrace. In order to reproduce the problem I just launched network-admin (using gdb) and entered the connection data with my internet provider. My configuration is: AVM FritzCard PCI 2.0 with modules fcpci, capi and capifs loaded in /etc/modules. avm-fritz--firmware-2.6.20-15 (3.11+2.6.20.5-15.20) capiutils (1:3.10.20070306-0ubuntu1) libcapi20-3 (1:3.10.20070306-0ubuntu1) pppdcapiplugin (1:3.10.20070306-0ubuntu1) ** Attachment added: gdb-network-admin.txt http://librarian.launchpad.net/7333624/gdb-network-admin.txt -- Crash while trying to save the ISDN Config https://bugs.launchpad.net/bugs/70871 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 70871] Re: Crash while trying to save the ISDN Config
Sorry, the modules loaded are: capi, capidrv, fcpci -- Crash while trying to save the ISDN Config https://bugs.launchpad.net/bugs/70871 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 70871] Re: Crash while trying to save the ISDN Config
** Changed in: network-manager (Ubuntu) Sourcepackagename: None = network-manager -- Crash while trying to save the ISDN Config https://bugs.launchpad.net/bugs/70871 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 97206] Re: error on booting up mounting an external usb-drive
Thanks for replying to my report. I just found out that the problem cannot be reproduced anymore after one of the recent kernel updates. -- error on booting up mounting an external usb-drive https://bugs.launchpad.net/bugs/97206 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 106169] Re: Latest kernel update does not boot (7.04)
*** This bug is a duplicate of bug 106063 *** https://bugs.launchpad.net/bugs/106063 Same error here. I suppose your undetectable harddrive uses S-ATA? All of my other harddisks (P-ATA and external usb drives) are detected without any problems. Here is what the log file says: Log of fsck -C -R -A -a Fri Apr 13 11:50:48 2007 fsck 1.40-WIP (14-Nov-2006) Boot: clean, 32/68272 files, 25345/136521 blocks (check in 5 mounts) Musik: clean, 15861/19546112 files, 16994568/39070072 blocks fsck.ext3: Unable to resolve 'UUID=d298ff9e-6230-4f64-ba48-e33f4752b8ff' Videos: clean, 416/19546112 files, 25097004/39072088 blocks fsck died with exit status 8 -- Latest kernel update does not boot (7.04) https://bugs.launchpad.net/bugs/106169 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 70871] Re: Crash while trying to save the ISDN Config
** Changed in: Ubuntu Status: Unconfirmed = Confirmed -- Crash while trying to save the ISDN Config https://bugs.launchpad.net/bugs/70871 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 70871] Re: Crash while trying to save the ISDN Config
Same here using newest Ubuntu 7.04 (feisty). Since I don't know what information you would like to have me attach, here is just what Michael Kofler did: root# capiinfo Number of Controllers : 1 Controller 1: Manufacturer: AVM GmbH CAPI Version: 2.0 Manufacturer Version: 3.11-07 (49.23) Serial Number: 101 ... root# lspci | grep -i avm 02:05.0 Network controller: AVM Audiovisuelles MKTG Computer System GmbH Fritz!PCI v2.0 ISDN (rev 01) root# lspci | grep -i avm 02:05.0 Network controller: AVM Audiovisuelles MKTG Computer System GmbH Fritz!PCI v2.0 ISDN (rev 01) [EMAIL PROTECTED]:~# lsmod | egrep -i 'isdn|capi|avm|hisax' capi 17344 0 capifs 5896 2 capi capidrv29972 1 isdn 138208 1 capidrv slhc6784 1 isdn kernelcapi 39924 3 capi,capidrv,fcpci -- Crash while trying to save the ISDN Config https://bugs.launchpad.net/bugs/70871 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 97206] error on booting up mounting an external usb-drive
Public bug reported: I use an partitioned external USB-drive which I try to permanently mount as /dev/sdb1 and /dev/sdb2. It actually works quite well except it stops boot procedure printing the following error. At prompt I just enter 'exit' and it will just boot fine mounting the drives at the right locations. The drives are formatted as ext3 each. fsck 1.40-WIP (14-Nov-2006) fsck.ext3: No such file or directory while trying to open /dev/sdb1 /dev/sdb1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device fsck.ext3: No such file or directory while trying to open /dev/sdb2 /dev/sdb2: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device fsck died with exit status 8 ProblemType: Bug Architecture: i386 Date: Wed Mar 28 00:47:29 2007 DistroRelease: Ubuntu 7.04 Uname: Linux bjoern 2.6.20-13-386 #2 Sun Mar 25 00:18:53 UTC 2007 i686 GNU/Linux ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- error on booting up mounting an external usb-drive https://launchpad.net/bugs/97206 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61371] Re: Package 7.0.68~ubuntu1~dapper1 does not work
Confirmed. -- Package 7.0.68~ubuntu1~dapper1 does not work https://launchpad.net/bugs/61371 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
