[Bug 2056595] Re: Lot of SyntaxWarning messages for rhythmbox
Same here:
Setting up rhythmbox-plugins (3.4.7-2ubuntu2) ...
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:64:
SyntaxWarning: invalid escape sequence '\/'
url = re.split('(\/display[^"]*)', entry)[1]
/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/lyrics/AstrawebParser.py:66:
SyntaxWarning: invalid escape sequence '\/'
title = re.split('(\/display[^>]*)([^<]*)', entry)[2][1:].strip()
[...]
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/2056595
Title:
Lot of SyntaxWarning messages for rhythmbox
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2056595/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966048] Re: xrdp fails to bind to localhost
On further digging, I've found that this issue is due to an AppArmor rule, which for some reason was treating localhost differently (as IPv6) than a regular network address (IPv4). Closing. ** Changed in: xrdp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xrdp in Ubuntu. https://bugs.launchpad.net/bugs/1966048 Title: xrdp fails to bind to localhost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1966048/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966048] [NEW] xrdp fails to bind to localhost
Public bug reported: This concerns xrdp 0.9.17-2ubuntu2 in Ubuntu jammy. I want to have xrdp listen on a localhost port. When I configure the server to use [Globals] ... port=tcp://.:3389 in /etc/xrdp/xrdp.ini, and I attempt to start the server, I get an error: # /etc/init.d/xrdp start Starting xrdp (via systemctl): xrdp.serviceJob for xrdp.service failed because the control process exited with error code. See "systemctl status xrdp.service" and "journalctl -xeu xrdp.service" for details. failed! In /var/log/xrdp.log, I see [20220323-05:02:00] [INFO ] address [127.0.0.1] port [3389] mode 4 [20220323-05:02:00] [INFO ] listening to port 3389 on 127.0.0.1 [20220323-05:02:00] [ERROR] trans_listen_address failed [20220323-05:02:00] [ERROR] Failed to start xrdp daemon, possibly address already in use. The port is free. Nothing is using it: $ telnet localhost 3389 Trying ::1... Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused I tried building the latest upstream release of xrdp (v0.9.19 as of this writing) with the same build configuration as the Ubuntu package. It starts without error. Please update the package to v0.9.19. ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xrdp in Ubuntu. https://bugs.launchpad.net/bugs/1966048 Title: xrdp fails to bind to localhost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1966048/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1905759] Re: gnome-shell crashed with SIGABRT in GI_raise()
Hello, Thank you very much! My apologies for attaching the crash file - I hadn't realized this might be problematic. I followed what you indicated (particularly #2) and found the following links: https://errors.ubuntu.com/oops/2f0e2248-3008-11eb-8c9b-fa163e983629 https://errors.ubuntu.com/oops/21ec9802-3008-11eb-b997-fa163e102db1 https://errors.ubuntu.com/oops/5fdb36f4-2f3c-11eb-8677-fa163ee63de6 I think I may have erroneously send multiple of the same crash reports - my apologies if this was the case. Please let me know if there is anything else I might provide. Thanks, Daniel On Thu, Nov 26, 2020 at 9:15 PM Daniel van Vugt <1905...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > > ** Tags added: groovy > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1905759 > > Title: > gnome-shell crashed with SIGABRT in GI_raise() > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Description: Ubuntu 20.10 > Release: 20.10 > > In the middle of work screen will randomly glitch green then revert to > the login screen - behaviour with both Wayland and not Wayland. > Apport.log shows: > > ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: called for pid 2318, > signal 6, core limit 0, dump mode 1 > ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: executable: > /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") > ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: debug: session gdbus > call: (true,) > > ERROR: apport (pid 11042) Thu Nov 26 11:51:51 2020: wrote report > /var/crash/_usr_bin_gnome-shell.1000.crash > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+subscriptions > -- Candidate for Bachelors of Science University of Waterloo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905759 Title: gnome-shell crashed with SIGABRT in GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905759] [NEW] gnome-shell crashed with SIGABRT in GI_raise()
Public bug reported: Description:Ubuntu 20.10 Release:20.10 In the middle of work screen will randomly glitch green then revert to the login screen - behaviour with both Wayland and not Wayland. Apport.log shows: ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: called for pid 2318, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: debug: session gdbus call: (true,) ERROR: apport (pid 11042) Thu Nov 26 11:51:51 2020: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/bugs/1905759/+attachment/5438304/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1905759 Title: gnome-shell crashed with SIGABRT in GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871882] Re: Default session fails when not started by a login manager
I'm not sure that this new title is accurate, as the error condition is brought about specifically by an unusual (albeit legal) way of starting the X session. My scenario involved xrdp, but I could see this happening with an older display manager (xdm?) that does not recognize XDG xsession files. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871882 Title: Default session fails when not started by a login manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871882] Re: gnome-session-bin package cannot function without gnome-session
Autologin is not in use. The only unusual aspect of this login is that it is via xrdp, and because no argument is passed to the initial /etc/X11/Xsession invocation, it uses the default x-session-manager -> gnome-session . If the user logs in via the console, xfce4-session is used instead, masking the problem. (I tested with an empty user home directory, so there is no user config to confound the problem.) On an Ubuntu desktop system, gnome-session-binary loads /usr/share /gnome-session/sessions/gnome-login.session which is provided by gdm3. So the dependency for gnome-session-bin could be stated as "gnome- session | gdm3". The problem can be reproduced by using /usr/bin/gnome-session as the session manager, with neither the gnome-session nor gdm3 packages installed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1871882 Title: gnome-session-bin package cannot function without gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1871882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871882] [NEW] gnome-session-bin package cannot function without gnome-session
Public bug reported: This concerns gnome-session-bin 3.36.0-2ubuntu1 in Ubuntu focal. When I log into a Xubuntu desktop via xrdp, an error occurs, and the session terminates before the desktop is even drawn on the screen. I looked in syslog, and saw this: Apr 9 12:12:23 test-ubuntu64 systemd[1760]: Reached target Tasks to be run before GNOME Session starts. Apr 9 12:12:23 test-ubuntu64 systemd[1760]: Starting GNOME Session Manager (session: gnome)... Apr 9 12:12:23 test-ubuntu64 gnome-session[1900]: gnome-session-binary[1900]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 9 12:12:23 test-ubuntu64 gnome-session-binary[1900]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 9 12:12:23 test-ubuntu64 systemd[1760]: gnome-session-manager@gnome.service: Main process exited, code=exited, status=1/FAILURE I edited /usr/lib/systemd/user/gnome-session-manager@.service to add the --debug option to the gnome-session-binary invocation, and tried again. Now I saw this: Apr 9 12:23:52 test-ubuntu64 systemd[2686]: Reached target Tasks to be run before GNOME Session starts. Apr 9 12:23:52 test-ubuntu64 systemd[2686]: Starting GNOME Session Manager (session: gnome)... Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Enabling debugging Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Enabling debugging Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): hardware acceleration already done if needed Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): hardware acceleration already done if needed Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Finding a graphical session for user 1000 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Finding a graphical session for user 1000 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Considering session 'c4' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Considering session 'c4' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Found session ID: c4 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Found session ID: c4 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Using systemd for session tracking Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Using systemd for session tracking Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for \u2018gsettings-backend\u2019 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: GLib-GIO-DEBUG(+): _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for \u2018gsettings-backend\u2019 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): GsmManager: setting client store 0x559bf9e91e40 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): GsmManager: setting client store 0x559bf9e91e40 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/test-ubuntu64:@/tmp/.ICE-unix/2818,unix/test-ubuntu64:/tmp/.ICE-unix/2818 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): GsmXsmpServer: SESSION_MANAGER=local/test-ubuntu64:@/tmp/.ICE-unix/2818,unix/test-ubuntu64:/tmp/.ICE-unix/2818#012 Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): emitting SessionIsActive Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): emitting SessionIsActive Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): fill: *** Getting session 'gnome' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): fill: *** Getting session 'gnome' Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): fill: *** Looking if /home/skunk/.config/gnome-session/sessions/gnome.session is a valid session file Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): fill: *** Looking if /home/skunk/.config/gnome-session/sessions/gnome.session is a valid session file Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: gnome-session-binary[2818]: DEBUG(+): Cannot use session '/home/skunk/.config/gnome-session/sessions/gnome.session': non-existing or invalid file. Apr 9 12:23:52 test-ubuntu64 gnome-session-binary[2818]: DEBUG(+): Cannot use session '/home/skunk/.config/gnome-session/sessions/gnome.session':
[Bug 1782275] [NEW] Conflict between resolvconf and systemd-resolved dhclient scripts
Public bug reported: I am setting up an Ubuntu 18.04 (bionic) system with ifupdown instead of netplan, as the latter does not meet my needs. I am using resolvconf to update /etc/resolv.conf from DHCP, as in earlier releases. Unfortunately, I am not seeing /etc/resolv.conf (actually a symlink to /run/resolvconf/resolv.conf) being updated; it is only the boilerplate from /etc/resolvconf/resolv.conf.d/head with no server information appended. (My "base" and "tail" files are empty.) I poked around the scripts in /etc, and believe I have found the problem. When resolvconf is installed, the following two files are present: /etc/dhcp/dhclient-enter-hooks.d/resolvconf /etc/dhcp/dhclient-enter-hooks.d/resolved Both of these scripts define the make_resolv_conf() shell function. What I am seeing is that dhclient runs these two scripts in the (alphabetical) order shown, and as the resolved script runs second, it overwrites the resolvconf version of the shell function with its own. As a result, dhclient does not invoke the appropriate update command for resolvconf, even though the hook script was installed correctly. Normally, I would remove the package that is providing the "resolved" script, but this package is systemd, which cannot be removed. I am not sure which of the two packages (resolvconf or systemd) needs to make an accommodation for the other, but it is clear that the current approach does not work. ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1782275 Title: Conflict between resolvconf and systemd-resolved dhclient scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1782275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1131442] Re: gvfsd-trash process survives logout
This issue is no longer observable in a standard console X11 login on Xenial. There is still an issue with GVFS daemons hanging around after an XFCE session that was launched from a terminal (as in a remote X11 session), but that is actually due to dbus-launch not being killed at the end of the session. If dbus-launch is killed, it takes the GVFS daemons with it. I've filed this bug for the dbus-launch issue: https://bugs.launchpad.net/bugs/1577920 ** Changed in: gvfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1131442 Title: gvfsd-trash process survives logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1131442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 550101] Re: Export of keys and keyrings is not available
Jorge: Check in the upstream bugzilla to see if someone's already filed a bug, but if not, then go for it. Very few Ubuntu package maintainers take the initiative to file upstream bugs themselves. If you do file a bug upstream, or a report already exists, please link it here! (As a possible workaround: I've found in the past that if a password keyring is set to have no passphrase, the on-disk file becomes cleartext. Keepass2 should certainly be able to import that.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/550101 Title: Export of keys and keyrings is not available To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/550101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194674] Re: Drop-down fields in PDF forms are not saved
** Bug watch added: GNOME Bug Tracker #703145 https://bugzilla.gnome.org/show_bug.cgi?id=703145 ** Also affects: evince via https://bugzilla.gnome.org/show_bug.cgi?id=703145 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1194674 Title: Drop-down fields in PDF forms are not saved To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1194674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194674] [NEW] Drop-down fields in PDF forms are not saved
Public bug reported: This concerns evince 3.6.1-1ubuntu3 in Ubuntu raring. I have a PDF form in which a couple of fields are multi-option drop-down widgets, e.g. Title: [ Select one ] Mr. Ms. Mrs. The field is initially set to [ Select one ], and I am supposed to select one of the options. I do this, and save a copy of the PDF. When I open the newly-filled PDF file, most of the fields have my information in them, but the drop-downs have reverted to the [ Select one ] state. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1194674 Title: Drop-down fields in PDF forms are not saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1194674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1131362] [NEW] Asks to unlock private key that was already unlocked by ssh-add(1)
Public bug reported:
This concerns gnome-keyring 3.6.1-0ubuntu1 in Ubuntu Quantal.
Normally, I invoke ssh-add(1) manually after logging in. I add a number
of identities, and then connect to other hosts using those identities.
This worked correctly in Ubuntu Oneiric.
Now, with a new Quantal install, when I connect to another host I am
confronted with a dialog to unlock the same private key that should have
been unlocked with ssh-add. If I type in my passphrase again into this
dialog, the connection succeeds and the identity is cached, but of
course the agent should not be requesting the passphrase a second time.
I suspect the problem is that the agent is counting one of my private
keys twice:
$ ssh-add -l
2048 97:ea:51:11:53:94:14:7f:25:f2:b0:f5:a8:54:04:56 foo@bar (RSA)
$ ssh-add ~/.ssh/id_rsa_foo /srv/local/ssh/id_rsa_{blah,xyzzy}
Enter passphrase for /home/skunk/.ssh/id_rsa_foo:
Identity added: /home/skunk/.ssh/id_rsa_foo (/home/skunk/.ssh/id_rsa_foo)
Identity added: /srv/local/ssh/id_rsa_blah (/srv/local/ssh/id_rsa_blah)
Identity added: /srv/local/ssh/id_rsa_xyzzy (/srv/local/ssh/id_rsa_xyzzy)
$ ssh-add -l
2048 97:ea:51:11:53:94:14:7f:25:f2:b0:f5:a8:54:04:56
/home/skunk/.ssh/id_rsa_foo (RSA)
2048 f9:3b:29:60:b3:59:69:e2:c3:d8:09:cd:d2:8b:a0:08 /srv/local/ssh/id_rsa_blah
(RSA)
2048 ac:c2:c3:ac:b9:ae:e5:c9:85:85:71:18:3c:0f:2a:a1
/srv/local/ssh/id_rsa_xyzzy (RSA)
2048 97:ea:51:11:53:94:14:7f:25:f2:b0:f5:a8:54:04:56 foo@bar (RSA)
Notice how the 97:ea:51:11:... key is listed twice in the second ssh-add -l
listing. When the unlock-private-key dialog comes up, it is for the foo@bar
identity, and gnome-keyring's failure to recognize that id_rsa_foo is the
selfsame key is probably the crux of this bug.
** Affects: gnome-keyring (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1131362
Title:
Asks to unlock private key that was already unlocked by ssh-add(1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1131362/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1131442] [NEW] gvfsd-trash process survives logout
Public bug reported: This report concerns gvfs-daemons 1.14.0-0ubuntu6 in Ubuntu Quantal. I log out from an Xfce desktop session, and the process table shows a gvfsd-process is still running. If I log in again, and log out again, two processes. Log in/out again, three processes. And so on. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1131442 Title: gvfsd-trash process survives logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1131442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 861171] Re: Shutdown from greeter does nothing when multiple accounts open
Can you tell who marked those bugs as duplicates? If it wasn't Robert Ancell, they could probably be unmarked. There's a possibility the same codepath is involved in being at the greeter vs. in a session, but he's likely the only person active here who would know for sure. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 932504] [NEW] cannot create /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0//gdk-pixbuf-query-loaders/loaders.cache
Public bug reported: Saw this while installing a slew of X11 packages: [...] Setting up libgtk-3-0 (3.2.0-0ubuntu4) ... Setting up libgtk-3-bin (3.2.0-0ubuntu4) ... Setting up librsvg2-common (2.34.1-2) ... /var/lib/dpkg/info/librsvg2-common:i386.postinst: 15: cannot create /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0//gdk-pixbuf-query-loaders/loaders.cache: Directory nonexistent Setting up libfontenc1 (1:1.1.0-1) ... Setting up libgif4 (4.1.6-9) ... [...] ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/932504 Title: cannot create /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0//gdk-pixbuf- query-loaders/loaders.cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/932504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 219738] Re: gnome-keyring export support not implemented
For what it's worth, if the password on a keyring is set to the empty string---something you can do with seahorse---the keyring will be stored on disk as a plain-text file. The INI-style format leaves a lot to be desired, but at least it's a way to do export and import with gnome- keyring. Other password tools could easily add support for this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/219738 Title: gnome-keyring export support not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/219738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 792085] Re: Automatic remount of safely removed drive
In 11.10, I'm no longer seeing usb-creator remount previously-removed disks on startup. I can't speak to the Nautilus behavior described in this bug, however, as I've never observed it myself. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/792085 Title: Automatic remount of safely removed drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 331443] Re: /etc/init.d/gdm reload fails when gdm is not running
As of the current version in Natty, the behavior is different. The init script has been converted to an Upstart job, and when GDM is not running, it reacts thusly: # reload gdm reload: Unknown instance: # echo $? 1 Good enough for me. ** Changed in: gdm (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/331443 Title: /etc/init.d/gdm reload fails when gdm is not running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/331443/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 591492] [NEW] Cannot prepend user-defined dir to XDG_CONFIG_DIRS
Public bug reported: Binary package hint: gdm This is a wishlist item, filed against gdm 2.30.0-0ubuntu5 in Ubuntu Lucid. I use the Xubuntu desktop. XDG_CONFIG_DIRS is set in /etc/X11/Xsession.d /60xdg_path-on-session (a file provided by gdm) to /etc/xdg/xdg- xubuntu:/etc/xdg (if I haven't set X_D_G myself beforehand). What I want to do, however, is set it to something like $HOME/.my- xdg:/etc/xdg/xdg-xubuntu:/etc/xdg. That is, I want to prepend my own directory to the variable. (The idea is to start with my preferred default settings with an empty ~/.config directory, when I'm starting a brand-new user account. I do this at every new Ubuntu release, and it's less work to hand-maintain some cut-down config files in ~/.my-xdg/ than to go through all the GUI widgets necessary to set my desired settings every six months.) The problem is that, short of using your own ~/.xsession file, there is no way to do this. You can't set/tweak X_D_G accordingly in ~/.profile or ~/.xsessionrc, because those are read before 60xdg_path-on-session. And you can't change what 60xdg_path-on-session does, unconditionally adding the /etc/xdg/... directory as the very first element. This makes it basically infeasible for a user to take advantage of a very useful aspect of the XDG Base Directory system. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- Cannot prepend user-defined dir to XDG_CONFIG_DIRS https://bugs.launchpad.net/bugs/591492 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 584817] Re: Stops updating if dpkg was interrupted
*** This bug is a duplicate of bug 124373 *** https://bugs.launchpad.net/bugs/124373 Jamie, this bug isn't about dpkg itself getting stuck (though I'd like to see that get straightened out); this is about u-u not taking care of the problem itself. The context is that of a system where the user doesn't ever touch the package-management tools, let alone sudo dpkg in a terminal: for example, a home-based kiosk for overnight guests, or a computer-phobic user who runs little more than a Web browser. I believe this bug has security implications, because anything that prevents u-u from installing updates automatically may lead to a vulnerability exposure. I'm particularly concerned about the Firefox version falling behind, as that is the most likely attack vector for an otherwise mostly-default Ubuntu install. -- Stops updating if dpkg was interrupted https://bugs.launchpad.net/bugs/584817 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug (via bug 124373). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 562452] Re: swell-foop fails to start with drm errors
*** This bug is a duplicate of bug 557266 *** https://bugs.launchpad.net/bugs/557266 This isn't a gnome-games bug; this is an issue with the OpenGL driver. I'm seeing the same error with openarena, gltron, etc. ** This bug has been marked a duplicate of bug 557266 [Radeon kernel module] drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream -- swell-foop fails to start with drm errors https://bugs.launchpad.net/bugs/562452 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-games in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 331443] [NEW] /etc/init.d/gdm reload fails when gdm is not running
Public bug reported: Binary package hint: gdm The gdm init script reload action is invoked when installing other packages that affect the configuration. However, if gdm is not running, the script does not behave in a very graceful manner. Observe: # /etc/init.d/gdm reload * Reloading GNOME Display Manager configuration... * Changes will take effect when all current X sessions have ended. # echo $? 1 # What current X sessions?? I believe the script should just exit 0 silently in this case, or at the most complain that gdm isn't running, so it has nothing to do. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- /etc/init.d/gdm reload fails when gdm is not running https://bugs.launchpad.net/bugs/331443 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
