[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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/desktop-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 Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60373] Printing error with gnome-sudoku
Public bug reported: Hello, using latest dapper, gnome-sudoku (0.4.0-2ubuntu3) and cupsys (1.2.2-0ubuntu0.6.06) I recieve the following error trying to print sudoku puzzles on my HP DeskJet 930C inkjet printer (hplib 0.9.7-4ubuntu1): Printer output: [EMAIL PROTECTED] ENTER LANGUAGE=PCL3 17H10M126Ao-1M1-2Hu300D10L148D14E16Dp0Xg8W,,r1Ab2Mp86Yb33W 4x (without quotations marks) There seems to be no problem printing with cups-pdf (2.2.0-1). I experience, however, the same kind of error trying to print that puzzle from a generated PDF-file. There are no problems with printing other files directly or through PDF. If this error belongs to cupsys-package or any other please inform me. Thanks Björn ** Affects: gnome-games (Ubuntu) Importance: Medium Assignee: Ubuntu Desktop Bugs Status: Needs Info -- Printing error with gnome-sudoku https://launchpad.net/bugs/60373 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs