[Bug 637702] Re: Prompted to unlock keyring twice on log in
I did a fresh install of Ubuntu 11.04. Initially I was still experiencing this problem, however, after a recent update I am now only prompted to unlock my keyring once after login. Can anyone else confirm this? I did not apply any other fix besides applying regular Ubuntu updates. -- 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/637702 Title: Prompted to unlock keyring twice on log in -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 744929] Re: After auto-login, prompted to unlock keyring multiple times
For me, with an early update in Ubuntu 11.04, this bug appears to be fixed. At some point, starting a few days ago, I am now only prompted to unlock my keyring once. I did not apply any type of fix other than running my regular Ubuntu updates. Is anyone else still experiencing this problem with an up-to-date 11.04? -- 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/744929 Title: After auto-login, prompted to unlock keyring multiple times -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 744929] Re: After auto-login, prompted to unlock keyring multiple times
I am the original reporter of #637702. It sounds like the same bug I originally reported, which persisted throughout 10.10. This bug is indeed still affecting me and is very annoying. My current "default" keyring, contains Gwibber, 4 Empathy accounts, Ubuntu One, and 2 Desktop Couch user authentications. My "login" keyring does not contain any access rights. Do other people in this bug report have Empathy and Gwibber as startup applications (or X number of total applications that access the keyring equalling the number of times they're prompted for a keyring password)? It seems as though once the original keyring is created, if a new applications needs keyring access, it will cause a new prompt for your keyring at login. Some solutions presented on askubuntu.com ( http://askubuntu.com/questions/7578/unlock-keyring-promts-three-times- instead-one-time ) suggest deleting the keyring and after you're prompted to create a new keyring at next login, everything works fine. To me, this suggests that the problem is in the process of giving a new application keyring access (if you follow me). I wonder what would happen if someone who that solution "fixed" the problem added a new keyring-accessing application to their startup programs. My guess is then they'd be prompted for their keyring password twice, and the problem would no longer be "fixed" for them. -- 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/744929 Title: After auto-login, prompted to unlock keyring multiple times -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 505645] Re: Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly
Yes, that works as expected now, thanks. Will this update be pushed to Maverick at some point? -- 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/505645 Title: Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505645] Re: Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly
I also wonder if there may be 2 device IDs (0781:74d1 and 0781:74d0) for this device, since it appears that the original poster had a different ID than I did. -- 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/505645 Title: Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 505645] Re: Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly
@Jonathan Ernst It looks like: http://cgit.freedesktop.org/media-player-info/tree/media-players/sandisk_sansa-clip-plus.mpi is different from the contents of /usr/share/media-player-info/sandisk-sansa_clip_plus.mpi on my updated Ubuntu 10.10 machine. The freedesktop site lists: [Device] Product=Sansa Clip+ Vendor=SanDisk AccessProtocol=storage DeviceMatch=usb:0781:74d1; My machine's file has: [Device] AccessProtocol=storage DeviceMatch=usb:0781:74d0; Product=Sansa Clip+ Vendor=SanDisk Maybe that's the reason it's not detected? -- 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/505645 Title: Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505645] Re: Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly
@Jonathan Ernst Thanks for following up on this. However, something is still wrong. I just deleted the ".is_audio_player" file from my Sansa Clip+. I ejected and replugged my Sansa, and now Banshee and Rhythmbox no longer detect it as a media player (i.e. an icon doesn't show up so that I can sync music to it). The player is in MSC mode. When I plug the player in, Nautilus recognizes it as a USB drive (actually 2 separate USB drives because my player also has an optional additional uSDHC card). But when I open Rhythmbox or Banshee, I can't access the drive. I'm using Banshee 1.9.2 and Rhythmbox 0.13.1. $lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 003: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 005: ID 0781:74d1 SanDisk Corp. Sansa Clip+ (msc) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub On a side note, with the .is_audio_player hack, I was able to get Banshee to sync with my Sansa, but the syncing wasn't perfect (some of my meta data was garbled, truncated, blank, etc). I wonder if something didn't get messed up with Banshee when I upgraded from 10.04? No need to answer this, but if you have any thoughts let me know. -- 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/505645 Title: Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 637702] Re: Prompted to unlock keyring twice on log in
No I haven't changed it. -- Prompted to unlock keyring twice on log in https://bugs.launchpad.net/bugs/637702 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 35876] Re: 'Downloading package information' and 'building dependency tree' progress dialogs request focus too often
This is fixed with changes in update-manager in Maverick, just FYI. -- 'Downloading package information' and 'building dependency tree' progress dialogs request focus too often https://bugs.launchpad.net/bugs/35876 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 637702] Re: Prompted to unlock keyring twice on log in
** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/637702/+attachment/1580698/+files/Dependencies.txt -- Prompted to unlock keyring twice on log in https://bugs.launchpad.net/bugs/637702 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 637702] [NEW] Prompted to unlock keyring twice on log in
Public bug reported: Binary package hint: gnome-keyring I recently upgraded from 10.04 (updated) to Maverick beta. After upgrading I noticed I am now prompted to unlock my keyring twice on each boot. I initially had auto-login enabled, but even if I disable that, after I log in, I am still prompted twice for my keyring password. ( http://ubuntuforums.org/showthread.php?p=9838543 ) I was going to try purging and re-installing gnome-keyring (as suggested on the forum post) but this will uninstall ubuntu-desktop and a lot of other stuff, so I'd rather not if there's another way to fix this. Please let me know what more information I can provide. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-keyring 2.92.92.is.2.31.91-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic x86_64 Architecture: amd64 Date: Mon Sep 13 20:06:57 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-keyring ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Prompted to unlock keyring twice on log in https://bugs.launchpad.net/bugs/637702 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 622542] [NEW] Search box should obtain focus at start up
Public bug reported: Binary package hint: rhythmbox When I start Rhythmbox, my "library" pane has focus of the cursor. If I start typing right away, I can locate the first instance of a song title that contains that letter/word/phrase (e.g. if I type "you", my cursor goes to "You Shook Me All Night Long" by AC-DC). This is ineffective because this seems to offer no advantages over focusing "search" immediately but does suffer from a few disadvantages. For example, it does not allow you to immediately search by Artist, Album title, or Genre. It also does not allow you to pull up multiple matches for a given term or title. I submit this is a flawed design (unless you can name some unforeseen reason why the behavior is as is). Ubuntu 10.04 with up to date packages. rhythmbox 0.12.8-0ubuntu7. ** Affects: hundredpapercuts Importance: Undecided Status: New ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Also affects: hundredpapercuts Importance: Undecided Status: New -- Search box should obtain focus at start up https://bugs.launchpad.net/bugs/622542 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568161] Re: Empathy does not remember previous status
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/44990050/Dependencies.txt -- Empathy does not remember previous status https://bugs.launchpad.net/bugs/568161 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 568161] [NEW] Empathy does not remember previous status
Public bug reported: Binary package hint: empathy I start Empathy and it automatically connects to all my accounts. My status is set to the generic "Available". I create a custom status message for "Available", and it works well. Then I completely quit Empathy. A while later I re-start Empathy, and my status has been reset back to the generic "Available". The same is true if I set my Empathy status to the generic "Away". If I quit and re-start Empathy, my status is reset to the generic "Available". The latter may be a "feature" (i.e. a specific design decision), but the former situation definitely seems like a bug. What I expect to happen: My custom status message is preserved, even if I quit Empathy. This is especially true if I created a "Saved Preset" custom message. Ubuntu Lucid amd64 with all updates to-date. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: empathy 2.30.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Apr 21 18:30:16 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Empathy does not remember previous status https://bugs.launchpad.net/bugs/568161 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526552] Re: Music->Close menu item and Ctrl-W do nothing
** Changed in: rhythmbox (Ubuntu) Status: New => Confirmed -- Music->Close menu item and Ctrl-W do nothing https://bugs.launchpad.net/bugs/526552 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35876] Re: 'Downloading package information' and 'building dependency tree' progress dialogs request focus too often
** Also affects: hundredpapercuts Importance: Undecided Status: New -- 'Downloading package information' and 'building dependency tree' progress dialogs request focus too often https://bugs.launchpad.net/bugs/35876 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 540056] Re: "Switch off" is not valid en_US
Per my updated Lucid, "Shut Down" is appearing in the menu applet, but the dialog box that appears asking you to confirm your action still uses "Switch Off" in the window title and the button title. -- "Switch off" is not valid en_US https://bugs.launchpad.net/bugs/540056 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 540056] Re: "Switch off" is not valid en_US
I think "Power Off" or "Power Down" would be much better descriptions than "Switch Off". "Turn off" would also work, but it's a bit colloquial. "Turn Off..." would also be kind of weird without the word "computer" or some other descriptive noun afterwards. I feel the word "Power" reminds the user that they'll be shutting their computer completely off. Agreed that "Switch Off" just sounds odd (to me it sounds very European/British) and it will not translate well, at least to U.S. users. -- "Switch off" is not valid en_US https://bugs.launchpad.net/bugs/540056 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 418064] Re: Apple.com blocking Gstreamer
According to this bug report (linked in the original upstream), a fix should be available upstream. https://bugzilla.gnome.org/show_bug.cgi?id=375867 ** Also affects: totem via https://bugzilla.gnome.org/show_bug.cgi?id=375867 Importance: Unknown Status: Unknown -- Apple.com blocking Gstreamer https://bugs.launchpad.net/bugs/418064 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 485099] Re: F-Spot Photo Manager Edit buttons difficult to find
It looks like perhaps it's working on my 9.10 installations because I've already changed it from Tags -> Edit in the dropdown menu and just left it there. That menu remembers the selection even after F-spot is closed. My concern was with the default 10.04 installation. As I just ran F-spot for the first time in Lucid and the "Edit" menu is automatically displayed, that's all I really wanted. From what you're saying, it also looks like this is the case with 9.10. I'm fairly sure that wasn't the case back in November when I tried, so that must mean something has gotten fixed. Out of curiosity, was your test on a default 9.10 install, or had you run updates? ** Changed in: f-spot (Ubuntu) Status: Triaged => Fix Released ** Changed in: hundredpapercuts Status: Triaged => Fix Released -- F-Spot Photo Manager Edit buttons difficult to find https://bugs.launchpad.net/bugs/485099 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 485099] Re: F-Spot Photo Manager Edit buttons difficult to find
I see that you're right. Something must have gotten fixed along the way. It's also working as expected in Lucid. I'm not sure who or what fixed it. I'll change this to Fix Released then, unless something reverts. -- F-Spot Photo Manager Edit buttons difficult to find https://bugs.launchpad.net/bugs/485099 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 528770] Re: Rhythmbox does not detect Sansa Clip+ (CLIPP or Clip Plus) automatically
apport information ** Tags added: apport-collected ** Description changed: Binary package hint: rhythmbox The Sansa Clip+ (CLIPP or Clip Plus) digital audio player (mp3 player) is not properly detected in Rhythmbox unless a .is_audio_player file is placed in the root of the device. The digital audio player is detected by Nautilus (or hal?) as a USB device. From lsusb: Bus 001 Device 006: ID 0781:74d0 SanDisk Corp. Steps to reproduce: 1. Connect Sansa Clip+ digital audio player 2. Open Rhythmbox 3. Expected: Rhythmbox lists my device in the left pane so that I can add new music to it 4. Observed: Rhythmbox does not detect my digital audio device I have tried adding 0x74d0 to /usr/share/hal/fdi/information/10freedesktop/10-usb-music-players.fdi under the Sansa Clip and Sansa Fuze heading (since they are basically all the same player), but this did not solve the problem. I found elsewhere that adding a (blank) .is_audio_player file to the root of the player allows it to be detected by Rhythmbox. This may be a hal or hal-info bug. I also realize this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+bug/505645 I just made a separate bug report so that I could easily upload apport-bug info. ProblemType: Bug Architecture: amd64 Date: Fri Feb 26 17:31:04 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1) Package: rhythmbox 0.12.6git20100223-0ubuntu1 ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SourcePackage: rhythmbox Uname: Linux 2.6.32-14-generic x86_64 + --- + Architecture: amd64 + DistroRelease: Ubuntu 10.04 + InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1) + Package: rhythmbox 0.12.6git20100223-0ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + LANG=en_US.utf8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-14.20-generic + Tags: lucid lucid + Uname: Linux 2.6.32-14-generic x86_64 + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39840429/Dependencies.txt -- Rhythmbox does not detect Sansa Clip+ (CLIPP or Clip Plus) automatically https://bugs.launchpad.net/bugs/528770 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 528770] Re: Rhythmbox does not detect Sansa Clip+ (CLIPP or Clip Plus) automatically
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39840182/Dependencies.txt ** Also affects: hal-info (Ubuntu) Importance: Undecided Status: New -- Rhythmbox does not detect Sansa Clip+ (CLIPP or Clip Plus) automatically https://bugs.launchpad.net/bugs/528770 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 528770] [NEW] Rhythmbox does not detect Sansa Clip+ (CLIPP or Clip Plus) automatically
Public bug reported: Binary package hint: rhythmbox The Sansa Clip+ (CLIPP or Clip Plus) digital audio player (mp3 player) is not properly detected in Rhythmbox unless a .is_audio_player file is placed in the root of the device. The digital audio player is detected by Nautilus (or hal?) as a USB device. >From lsusb: Bus 001 Device 006: ID 0781:74d0 SanDisk Corp. Steps to reproduce: 1. Connect Sansa Clip+ digital audio player 2. Open Rhythmbox 3. Expected: Rhythmbox lists my device in the left pane so that I can add new music to it 4. Observed: Rhythmbox does not detect my digital audio device I have tried adding 0x74d0 to /usr/share/hal/fdi/information/10freedesktop/10-usb-music-players.fdi under the Sansa Clip and Sansa Fuze heading (since they are basically all the same player), but this did not solve the problem. I found elsewhere that adding a (blank) .is_audio_player file to the root of the player allows it to be detected by Rhythmbox. This may be a hal or hal-info bug. I also realize this is probably a duplicate of https://bugs.launchpad.net/ubuntu/+bug/505645 I just made a separate bug report so that I could easily upload apport-bug info. ProblemType: Bug Architecture: amd64 Date: Fri Feb 26 17:31:04 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1) Package: rhythmbox 0.12.6git20100223-0ubuntu1 ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SourcePackage: rhythmbox Uname: Linux 2.6.32-14-generic x86_64 ** Affects: hal-info (Ubuntu) Importance: Undecided Status: New ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected lucid -- Rhythmbox does not detect Sansa Clip+ (CLIPP or Clip Plus) automatically https://bugs.launchpad.net/bugs/528770 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505645] Re: Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly
I added Rhythmbox to this bug report since at least the player shows up in nautilus (listed as a regular USB device). However, it is not properly detected in Rhythmbox unless a .is_audio_player file is placed in the root of the device. This is a bug. If you'd like me to create a new bug report for Rhythmbox or if you feel the problem is just with hal and not rhythmbox, let me know. ** Also affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- Sansa Clip+ (CLIPP, Clip Plus) digital audio player not recognised properly https://bugs.launchpad.net/bugs/505645 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 498032] [NEW] CD drive does not refresh or update after burning without eject
Public bug reported: Binary package hint: nautilus After burning a cd (with Brasero), the CD still shows up as "Blank CD-R Disc". Ejecting the drive and re-inserting the same CD causes it to show up as "Audio DIsc". I'm assuming that this is a Nautilus problem, but if it's brasero (or something else) go ahead and change things. Steps to reproduce: 1. Insert a blank CD-R into the CD-RW drive. Note that a "Blank CD-R Disc" icon appears on your Desktop. 2. Open Brasero and burn an audio CD 2. When finished, close Brasero. 3. Note the "Blank CD-R Disc" icon is still on your desktop, even though this is now an "Audio Disc". Attempting to double-click the icon opens a blank disc burning window in Nautilus. 4. Eject the drive and re-insert the same disc. It should not show up as "Audio Disc" and double-clicking on it will open the audio CD. Expected result: When Brasero finishes burning a disc, the Nautilus desktop icon should update to "Audio Disc" and double-clicking the desktop icon should open the audio disc in a media player. An acceptable (but less ideal) alternative would be if Brasero ejected the disc automatically (and by default) after burning. Please let me know if I can provide more information. Also, I'm adding brasero to this bug report just in case. Feel free to mark this as invalid if that's the case. ** Affects: brasero (Ubuntu) Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Also affects: brasero (Ubuntu) Importance: Undecided Status: New -- CD drive does not refresh or update after burning without eject https://bugs.launchpad.net/bugs/498032 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 498032] Re: CD drive does not refresh or update after burning without eject
Also, to clarify, this is on Ubuntu 9.10 64-bit -- CD drive does not refresh or update after burning without eject https://bugs.launchpad.net/bugs/498032 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 487396] Re: Brasero fails to write track information when creating audio CD
Seeing this too. Confirming... ** Changed in: brasero (Ubuntu) Status: Incomplete => Confirmed -- Brasero fails to write track information when creating audio CD https://bugs.launchpad.net/bugs/487396 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 206547] Re: Add option to open messages automatically
David's proposal sounds like a good suggestion. -- Add option to open messages automatically https://bugs.launchpad.net/bugs/206547 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 485099] Re: F-Spot Photo Manager Edit buttons difficult to find
Glad you realized my issue was separate from that in the blog post. I was confused by how that post was solving my issue. I submitted this upstream to Gnome's Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=603002 ** Bug watch added: GNOME Bug Tracker #603002 https://bugzilla.gnome.org/show_bug.cgi?id=603002 ** Changed in: f-spot Importance: Undecided => Unknown ** Changed in: f-spot Status: New => Unknown ** Changed in: f-spot Remote watch: None => GNOME Bug Tracker #603002 -- F-Spot Photo Manager Edit buttons difficult to find https://bugs.launchpad.net/bugs/485099 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 485099] Re: F-Spot Edit buttons difficult to find
Sebastien, just curious but has this actually been fixed in F-spot? Or what was the reason for marking it as fixed? -- F-Spot Edit buttons difficult to find https://bugs.launchpad.net/bugs/485099 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 322314] Re: "Automatically connect on startup" setting confusing - users may expect this to run Empathy on login
** Also affects: hundredpapercuts Importance: Undecided Status: New -- "Automatically connect on startup" setting confusing - users may expect this to run Empathy on login https://bugs.launchpad.net/bugs/322314 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 206547] Re: Add option to open messages automatically
I know this is being worked on upstream, but perhaps the papercuts team should give some advice on how best to fix it? ** Also affects: hundredpapercuts Importance: Undecided Status: New -- Add option to open messages automatically https://bugs.launchpad.net/bugs/206547 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 473735] Re: empathty keeps showing "network error" on facebook account
Sorry, accidentally added this to wrong bug report ** Bug watch added: GNOME Bug Tracker #585914 https://bugzilla.gnome.org/show_bug.cgi?id=585914 ** Also affects: empathy via https://bugzilla.gnome.org/show_bug.cgi?id=585914 Importance: Unknown Status: Unknown ** Changed in: empathy (Ubuntu) Status: New => Invalid ** Changed in: empathy (Ubuntu) Status: Invalid => New ** Changed in: empathy (Ubuntu) Status: New => Invalid ** Changed in: empathy (Ubuntu) Status: Invalid => New ** Changed in: empathy Importance: Unknown => Undecided ** Changed in: empathy Status: Unknown => New ** Changed in: empathy Remote watch: GNOME Bug Tracker #585914 => None ** Changed in: empathy Status: New => Invalid -- empathty keeps showing "network error" on facebook account https://bugs.launchpad.net/bugs/473735 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 478178] Re: Empathy is almost impossible to set as a startup application
Added the One Hundred Paper Cuts project to this, since it seemed like you wanted it added... ** Also affects: hundredpapercuts Importance: Undecided Status: New -- Empathy is almost impossible to set as a startup application https://bugs.launchpad.net/bugs/478178 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 411150] Re: URLs are not linkable in status message or contact information
** Also affects: hundredpapercuts Importance: Undecided Status: New -- URLs are not linkable in status message or contact information https://bugs.launchpad.net/bugs/411150 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 485099] Re: F-Spot Edit buttons difficult to find
** Also affects: hundredpapercuts Importance: Undecided Status: New -- F-Spot Edit buttons difficult to find https://bugs.launchpad.net/bugs/485099 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 485144] Re: gnome-volume-control not respecting "Input" with bluetooth headset attached
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/35841479/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/35841480/XsessionErrors.txt ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- gnome-volume-control not respecting "Input" with bluetooth headset attached https://bugs.launchpad.net/bugs/485144 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 485144] [NEW] gnome-volume-control not respecting "Input" with bluetooth headset attached
Public bug reported: Binary package hint: gnome-media I'm not entirely sure if this is a gnome-media bug or a pulseaudio bug (or something else), so I'm filing it under both. Here's my situation. I'm on a desktop with a set of regular old headphones/mic. I set everything up in gnome-volume-control and the mic and headphones work great. Then, when I attach a bluetooth headset (which attaches great on Ubuntu 9.10 btw), I'm now able to select my bluetooth headset for input and output. This also works great! The problem I run into is when I try to set gnome-volume-control to use my headphones/mic while the bluetooth headset is still connected to my system. Even though I specify that I want the Input and Output to be from my sound card and not bluetooth, applications receive my bluetooth headset's input. The output still goes to my regular headphones. If I can provide more info, let me know. ProblemType: Bug Architecture: amd64 Date: Wed Nov 18 19:07:32 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-media 2.28.1-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gnome-media Uname: Linux 2.6.31-14-generic x86_64 ** Affects: gnome-media (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- gnome-volume-control not respecting "Input" with bluetooth headset attached https://bugs.launchpad.net/bugs/485144 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 398447] Re: f-spot should move deleted items to the trash
I believe this is the behavior now, at least as of F-Spot 0.6.1.5 on Ubuntu 9.10 -- f-spot should move deleted items to the trash https://bugs.launchpad.net/bugs/398447 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 485099] [NEW] F-Spot Edit buttons difficult to find
Public bug reported: Binary package hint: f-spot I've been using F-Spot on and off for a year to import photos from my camera and I never realized that it had the ability to do any sort of editing aside from rotating the image. The reason is that even after double-clicking a photo in F-Spot, the "Edit" buttons that can be used to apply effects and adjust the photo's colors are hidden and can only be accessed by clicking on a drop-down menu on the left and selecting "Edit", where "Tags" is selected by default. If The GIMP is to be removed from the default Ubuntu install and F-Spot is expected to comprise the default image editing abilities of Ubuntu, this usability issue needs to be addressed. I'm not sure if this issue is specific to the Ubuntu version of F-Spot or if it is the default behavior of the application. Ubuntu 9.10 64-bit, F-Spot 0.6.1.5 ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- F-Spot Edit buttons difficult to find https://bugs.launchpad.net/bugs/485099 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 95853] Re: Delete file in Nautlus - no warning
Just putting in my 2 cents: Wouter's suggested idea is a fantastic compromise. It allows power users to keep using the delete key without being interrupted by having to confirm an action, but things that are accidentally trashed can be quickly and easily un-done. It'll be interesting to see what the user testing shows. >Perhaps we could have one of those yellow message bars that some >applications use, to tell you you deleted a file and providing a >button to cancel it? It is less intrusive and still provides a clue >about what happened and a way to undo it." -- Delete file in Nautlus - no warning https://bugs.launchpad.net/bugs/95853 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 386150] Re: Nautilus file browser toolbar is complicated, redundant, and ugly
#2: I agree with what "none" said. The stop button may be useful when you need to stop a nautilus action, but not when you're just sitting there browsing a folder. Ideally the button would be removed and a "stop" button could appear somewhere whenever Nautilus is "working". #3: Despite criticism from others, I agree with David. I think proper icons and tooltips negate the need for space-consuming labels. #4: Definitely agree. I'm looking at David's mockups and I still see icons for "Computer" and "Home". Shouldn't these be removed and both of them placed in the "Places" sidebar on the left? That seems to make the most sense. Or maybe leave the "Home". I also agree with the later assessment? Do many people use the Zoom icons? Couldn't the icons be removed and the actions placed in the View menu? I have a question too. Is there a need for Reload? I feel like everything appears instantaneously in Nautilus. Or is this just for using shares and folders on other computers? -- Nautilus file browser toolbar is complicated, redundant, and ugly https://bugs.launchpad.net/bugs/386150 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 266878] Re: Seahorse should be able to verify/handle formats created by gnupg
To clarify, I'd like to be able to clearsign from Nautilus as well. -- Seahorse should be able to verify/handle formats created by gnupg https://bugs.launchpad.net/bugs/266878 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 266878] Re: Seahorse should be able to verify/handle formats created by gnupg
I'm adding this to One Hundred Papercuts. This process is required to sign the Ubuntu Code of Conduct, and I feel like it should be an easier task to accomplish using Nautilus and not having to run gpg from the CLI. ** Also affects: hundredpapercuts Importance: Undecided Status: New -- Seahorse should be able to verify/handle formats created by gnupg https://bugs.launchpad.net/bugs/266878 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 266878] Re: Seahorse should be able to verify/handle formats created by gnupg
Strike that. Wrong place for suggestion, I think. -- Seahorse should be able to verify/handle formats created by gnupg https://bugs.launchpad.net/bugs/266878 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 266878] Re: Seahorse should be able to verify/handle formats created by gnupg
Since this hasn't gotten any response (here or at Gnome), I added a suggestion on the Seahorse Roadmap about this. I hope that's ok: http://live.gnome.org/RoadMap/Seahorse -- Seahorse should be able to verify/handle formats created by gnupg https://bugs.launchpad.net/bugs/266878 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