[Bug 1564209] Re: Doesn't recognise own reviews
** Changed in: rnr-server Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1564209 Title: Doesn't recognise own reviews To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1564209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1564209] Re: Doesn't recognise own reviews
@fgallina or @kelvin: Can you check the background for these decisions. I'm not 100% but from memory RnR used to use the SSO (well, LP) username when it has one for the user (as SSO users don't always have a username, it depends whether they have an LP account), so I don't know that we can provide a username consistently. But in Robert's case I'd imagine it's for a user who certainly does have a username (his own account?) The only consistent options I can imagine are: 1) always return the consumer key - @Robert - can you use that instead to identify (sorry, I don't know the background), and will this break anything (doubt it, if they're not broken already - if it does currently return either) 2) add a separate consumer_key which always has the consumer key. Rodney is keen for (1) so that it's consistent with the click rnr api: 21:47 < noodles> dobey: could you use a different key from the result, I mean if consumer_key was added separately? 21:48 < dobey> noodles: well i think we should match what we're doing for click; and i think software-center might be doing this comparison already anyway 21:57 < dobey> noodles: so, imo, always returning the consumer_key value for everyone in reviewer_username there, would be best 21:59 < noodles> dobey: Right, but that's exactly what Robert *doesn't* want, unless he could also identify with the consumer key? 21:59 < dobey> noodles: he can identify with the consumer key -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1564209 Title: Doesn't recognise own reviews To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1564209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246624] Re: Reminders from Google are displayed as “This is an event reminder”
This issue is fixed on Ubuntu 13.10, evoluion version 3.10.3-0ubuntu3~saucy1. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1246624 Title: Reminders from Google are displayed as “This is an event reminder” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1246624/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246624] Re: Reminders from Google are displayed as “This is an event reminder”
Confirmed here too. Interesting thing I noticed is that when you click Edit, the event name is in the Summary field. Perhaps Google's Calendar API changed and has become misaligned with what Evolution expects. Would love a fix or workaround! ** Attachment added: Screenshot from 2014-01-12 22:39:07.png https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1246624/+attachment/3947396/+files/Screenshot%20from%202014-01-12%2022%3A39%3A07.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1246624 Title: Reminders from Google are displayed as “This is an event reminder” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1246624/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1011504] [NEW] Rhythm box freezes consistently
Public bug reported: I seem to get about 1.5 songs out of Rhythm box until it freezes. I haven't worked out the cause, only that it's consistent, and isn't related to which music I play (although all my music is ogg). I didn't watch to see if the following message appeared right when it freezes, but nonetheless, the terminal shows: ~$ rhythmbox (rhythmbox:18803): GStreamer-WARNING **: Trying to join task 0x7f6a0402a0c0 from its thread would deadlock. You cannot change the state of an element from its streaming thread. Use g_idle_add() or post a GstMessage on the bus to schedule the state change from the main thread. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 CheckboxSubmission: f26299558349e6bfa9a64225e1770925 CheckboxSystem: 669b662da410063cc918e0f60cf6cddf Date: Mon Jun 11 10:51:55 2012 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100224.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: Upgraded to precise on 2012-01-16 (146 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/1011504 Title: Rhythm box freezes consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1011504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1011504] Re: Rhythm box freezes consistently
-- 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/1011504 Title: Rhythm box freezes consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1011504/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872701] Re: Not possible to enter correct password after screen lock
Hi, I've just had enough of doing CTRL-ALT-F1 login, kill gnome- screensaver etc., to look more into this and can confirm that, at least for me: With two keyboard layouts (layout1 and layout2) 1) lock the screen with CTRL-ALT-l 2) touch mouse to bring up screensaver dialog 3) switch keyboard layout to layout2 (and note keyboard indicator indicates layout change) 4) enter password *as if layout1 was active* [1] 5) screen is unlocked 6) switch back to layout1 Repeat, but this time skip step 3 - screen is still unlocked. That is, it seems that although the screensaver dialog indicates that it changes the layout - it is always using the one layout. Brian can you confirm this? If I get a chance, I'll take a look at the source and see if there's something I can pick off. [1] I had to type it in to an editor as I only know the keystrokes using layout2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Not possible to enter correct password after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/872701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872701] Re: Not possible to enter correct password after screen lock
Right - here's the same bug as what I've described reported upstream (but found on Ubuntu 11.10 also): https://bugzilla.gnome.org/show_bug.cgi?id=662992 ** Bug watch added: GNOME Bug Tracker #662992 https://bugzilla.gnome.org/show_bug.cgi?id=662992 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Not possible to enter correct password after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/872701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872701] Re: Keyboard layout doesn't change
** Summary changed: - Not possible to enter correct password after screen lock + Keyboard layout doesn't change ** Description changed: - STR: - 1) Lock the screen - 2) Move mouse to force password dialog to appear - 3) Set correct keyboard layout and enter password - 4) Returned to desktop + With two keyboard layouts (layout1 and layout2, where layout1 is the default for the session) + 1) lock the screen with CTRL-ALT-l + 2) touch mouse to bring up screensaver dialog + 3) switch keyboard layout to layout2 (and note keyboard indicator indicates layout change) + 4) enter password *as if layout1 was active* [1] + 5) screen is unlocked + 6) switch back to layout1 - AR: - At step 3, no matter which keyboard layout I set (I have US and US-dvorak and toggle with double-shift) the password which I enter is never accepted. I am forced to switch to a tty, login there (with the same password) and `pkill -f gnome-screensaver` to get back to my desktop. - - Note: I use multiple layouts on another oneiric laptop and do not see - this issue. + Repeat, but this time skip step 3 - screen is still unlocked. That is, + it seems that although the screensaver dialog indicates that it changes + the layout - it is always using the one layout. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Wed Oct 12 09:20:40 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110817) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: gnome-screensaver (Ubuntu) Status: Incomplete = Confirmed ** Description changed: With two keyboard layouts (layout1 and layout2, where layout1 is the default for the session) 1) lock the screen with CTRL-ALT-l 2) touch mouse to bring up screensaver dialog 3) switch keyboard layout to layout2 (and note keyboard indicator indicates layout change) 4) enter password *as if layout1 was active* [1] 5) screen is unlocked 6) switch back to layout1 Repeat, but this time skip step 3 - screen is still unlocked. That is, it seems that although the screensaver dialog indicates that it changes the layout - it is always using the one layout. + Upstream bug-report: https://bugzilla.gnome.org/show_bug.cgi?id=662992 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Wed Oct 12 09:20:40 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110817) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Keyboard layout doesn't change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/872701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 872701] Re: Not possible to enter correct password after screen lock
On Thu, Oct 13, 2011 at 1:45 PM, Sebastien Bacher seb...@ubuntu.com wrote: Thank you for your bug report, could you run gnome-screensaver --debug and see what isl in the debug log when unlocking fails? The following log is from: 1) lock screen 2) When password prompt appears, switch keyboard layout to correct layout for entering password, enter password (fails) 3) Switch back to original layout and try again (fails) 4) kill via tty (where same password is used to login) http://paste.ubuntu.com/707329/ It seems that it really is getting an incorrect password - one possibility that could make sense would be if the keyboard layout was being applied incorrectly. Let me know if there's anything else I can do. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Not possible to enter correct password after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/872701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 872701] Re: Not possible to enter correct password after screen lock
On Thu, Oct 13, 2011 at 3:50 PM, Marc Deslauriers marc.deslauri...@canonical.com wrote: Can you paste the appropriate section of your auth.log file? Also, could you paste the output of the following commands: ls -l /etc/shadow ls -l /dev/null Thanks! Oct 13 15:24:19 michael-1015PEM unix_chkpwd[22678]: password check failed for user (michael) Oct 13 15:24:19 michael-1015PEM gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=michael Oct 13 15:24:26 michael-1015PEM unix_chkpwd[22681]: password check failed for user (michael) Oct 13 15:24:26 michael-1015PEM gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=michael Oct 13 15:24:50 michael-1015PEM sudo: michael : TTY=tty1 ; PWD=/home/michael ; USER=root ; COMMAND=/bin/ls $ less /var/log/auth.log $ ls -l /etc/shadow -rw-r- 1 root shadow 1014 2011-08-25 10:53 /etc/shadow $ ls -l /dev/null crw-rw-rw- 1 root root 1, 3 2011-10-10 08:29 /dev/null Thanks Marc -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Not possible to enter correct password after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/872701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872701] [NEW] Cannot enter correct password after suspend
Public bug reported: STR: 1) Suspend the computer 2) Resume so that screen lock dialog waits for password 3) Set correct keyboard layout and enter password 4) Returned to desktop AR: At step 3, no matter which keyboard layout I set (I have US and US-dvorak and toggle with double-shift) the password which I enter is never accepted. I am forced to switch to a tty, login there (with the same password) and kill X - or is there an easier workaround where I can unlock the screensaver with a command? Note: I use multiple layouts on another oneiric laptop and do not see this issue. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Wed Oct 12 09:20:40 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110817) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Cannot enter correct password after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/872701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872701] Re: Cannot enter correct password after suspend
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Cannot enter correct password after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/872701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872701] Re: Not possible to enter correct password after screen lock
** Summary changed: - Cannot enter correct password after suspend + Not possible to enter correct password after screen lock ** Description changed: STR: - 1) Suspend the computer - 2) Resume so that screen lock dialog waits for password - 3) Set correct keyboard layout and enter password - 4) Returned to desktop + 1) Lock the screen + 2) Move mouse to force password dialog to appear + 3) Set correct keyboard layout and enter password + 4) Returned to desktop AR: - At step 3, no matter which keyboard layout I set (I have US and US-dvorak and toggle with double-shift) the password which I enter is never accepted. I am forced to switch to a tty, login there (with the same password) and kill X - or is there an easier workaround where I can unlock the screensaver with a command? + At step 3, no matter which keyboard layout I set (I have US and US-dvorak and toggle with double-shift) the password which I enter is never accepted. I am forced to switch to a tty, login there (with the same password) and `pkill -f gnome-screensaver` to get back to my desktop. Note: I use multiple layouts on another oneiric laptop and do not see this issue. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Wed Oct 12 09:20:40 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110817) ProcEnviron: - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Not possible to enter correct password after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/872701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 854622] Re: Could not install libglib2.0
On Fri, Sep 30, 2011 at 3:39 AM, Steve Langasek steve.langa...@canonical.com wrote: Please show 'ls -ld /usr/share/doc/libglib2.0*'. I'm pretty sure one of the directories is wrongly symlinked to the other, which means that unpacking libglib2.0-data after libglib2.0-0 *overwrites* the libglib2.0-0 changelog /on the filesystem/. $ ls -ld /usr/share/doc/libglib2.0* drwxr-xr-x 2 root root 4096 2011-09-21 15:18 /usr/share/doc/libglib2.0-0 drwxr-xr-x 2 root root 4096 2011-09-20 10:02 /usr/share/doc/libglib2.0-bin drwxr-xr-x 2 root root 4096 2011-09-20 10:18 /usr/share/doc/libglib2.0-cil lrwxrwxrwx 1 root root 12 2010-02-28 08:38 /usr/share/doc/libglib2.0-data - libglib2.0-0 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/854622 Title: Could not install libglib2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/854622/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 854622] Re: Could not install libglib2.0
On Tue, Sep 27, 2011 at 12:51 PM, Michael Nelson michael.nel...@canonical.com wrote: Not that I'm aware of (see below), but it is possible that I've sudo'd a symlink at some point - I don't remember doing so, and don't see why I would have (we do most our dev work in a virtualenv), but I guess I'm trying to say don't spend too much time on this if it's likely to be something stupid I've done on my box (which is entirely possible. Hi Martin, if no one else is seeing this, and you can't reproduce it, it is entirely possible that I'd added a symlink at some point to test something and failed to remove it. If that looks likely from the current state, then I'm happy to remove whichever symlink is incorrect and update my system again :) Sorry for possibly having wasted your time :/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/854622 Title: Could not install libglib2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/854622/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 854622] Re: Could not install libglib2.0
On Tue, Sep 27, 2011 at 11:23 AM, Martin Pitt martin.p...@ubuntu.com wrote: In such a situation, could you please give me the output of ls -l /usr/share/doc/*glib2.0*/changelog.Debian.gz dpkg -S /usr/share/doc/*glib2.0*/changelog.Debian.gz $ ls -l /usr/share/doc/*glib2.0*/changelog.Debian.gz -rw-r--r-- 1 root root 1672 2011-09-19 08:31 /usr/share/doc/libglib2.0-0/changelog.Debian.gz lrwxrwxrwx 1 root root 35 2011-09-20 10:02 /usr/share/doc/libglib2.0-bin/changelog.Debian.gz - ../libglib2.0-0/changelog.Debian.gz -rw-r--r-- 1 root root 2026 2011-07-12 10:55 /usr/share/doc/libglib2.0-cil/changelog.Debian.gz -rw-r--r-- 1 root root 1672 2011-09-19 08:31 /usr/share/doc/libglib2.0-data/changelog.Debian.gz -rw-r--r-- 1 root root 1473 2011-07-12 00:51 /usr/share/doc/libtaglib2.0-cil/changelog.Debian.gz $ dpkg -S /usr/share/doc/*glib2.0*/changelog.Debian.gz libglib2.0-0: /usr/share/doc/libglib2.0-0/changelog.Debian.gz libglib2.0-bin: /usr/share/doc/libglib2.0-bin/changelog.Debian.gz libglib2.0-cil: /usr/share/doc/libglib2.0-cil/changelog.Debian.gz libglib2.0-data: /usr/share/doc/libglib2.0-data/changelog.Debian.gz libtaglib2.0-cil: /usr/share/doc/libtaglib2.0-cil/changelog.Debian.gz to see which changelog.Debian.gz gets claimed by which package, and which are symlinks? Michael, did you happen to get the glib packages from a different place than the archive, Not that I'm aware of (see below), but it is possible that I've sudo'd a symlink at some point - I don't remember doing so, and don't see why I would have (we do most our dev work in a virtualenv), but I guess I'm trying to say don't spend too much time on this if it's likely to be something stupid I've done on my box (which is entirely possible. i. e. can you please give me the output of apt-cache policy libglib2.0-0 $ apt-cache policy libglib2.0-0 libglib2.0-0: Installed: 2.29.92-0ubuntu1 Candidate: 2.29.92-0ubuntu1 Version table: *** 2.29.92-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages 100 /var/lib/dpkg/status Thanks. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/854622 Title: Could not install libglib2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/854622/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 837743] Re: battery idle brightness may be brighter than user selected brightness
FWIW, I see the same behaviour on a fresh Oneiric install (on an Asus 1015PEM). Let me know if I can provide any further details (here or on bugzilla). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/837743 Title: battery idle brightness may be brighter than user selected brightness To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/837743/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 546810] Re: Initial login does not request password
On Thu, Apr 22, 2010 at 5:44 PM, Sebastien Bacher seb...@ubuntu.com wrote: the issue is a bit weird - is there anything special about your account or the way it's authentificated there? No, it happens when clicking on any account. - does it happen with other accounts too? - did you tweak the gdm configuration at some point to not show the user list or something? Not that I remember, I'm not sure what I've confused here - the user list (ie. list of accounts) is always displaying correctly? It's the password that I'm not being prompted for as above? could you also look in syslog if there any error displayed? does it I couldn't see find anything relevant. happen if you use enter to select the user rather than clicking? a screenshot of the language question could be useful too if you can take a photo or something Sorry for the incredibly bad quality but: http://people.canonical.com/~michaeln/tmp/account_selection.jpg http://people.canonical.com/~michaeln/tmp/account_selected.jpg -- Initial login does not request password https://bugs.launchpad.net/bugs/546810 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
Re: [Bug 546810] Re: Initial login does not request password
On Thu, Apr 22, 2010 at 2:44 PM, Sebastien Bacher seb...@ubuntu.com wrote: Thank you for your bug report. Do you still get the issue? You click on your username and don't get asked for a password is that the issue, the description is not so clear about it. Does it happen every time you try to select an user on first try? Hi Sebastien, I just went and checked (it's my wife's computer). Here are the details: It happens every time the machine is started. The login screen displays the 3 accounts as well as an Automatic login (with a small timer). But if I click *my own* account, I am not prompted for my password, instead I am asked to select a language and click Login (as if it was a guest or automatic account itself?). To work around this, I can either: 1) Simply click login, which will take a few seconds before it brings up the account list again and I click on my account and am prompted for my password as per normal, or 2) click on cancel, which displays the account list again and I click on my account and am prompted for my password as per normal. Hope that helps. -- Initial login does not request password https://bugs.launchpad.net/bugs/546810 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 546810] Re: Initial login does not request password
Hi Ian, It was an upgrade from Karmic. Also, it doesn't seem to be restricted to the initial login after the upgrade. I've seen the same issue a number of times when logging in on that machine (not being prompted for my password, hitting login, and being brought back to the same login page but this time prompted for the password as normal), although I haven't noticed a pattern. Let me know if there's any other info/files I can provide. -- Initial login does not request password https://bugs.launchpad.net/bugs/546810 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 546810] [NEW] Initial login does not request passord
Public bug reported: Binary package hint: gdm After running the upgrade and restarting the machine, everything went fine and I was prompted to select the account as per usual. AR: When I clicked on my account I was initially instructed Choose your language and then click Login. ER: When I click on my account I should be prompted for my password and then, if necessary, prompted to select a language? Clicking on login simply brought me back to the account selection again, I clicked again on my account and was prompted for my password as per normal. I wouldn't normally report such a small glitch, but am doing so as part of the lucid-upgrade-test work ;) ProblemType: Bug Architecture: i386 Date: Thu Mar 25 12:16:20 2010 DistroRelease: Ubuntu 10.04 Package: gdm 2.29.92-0ubuntu5 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 SourcePackage: gdm Uname: Linux 2.6.32-17-generic i686 ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid lucid-upgrade-testing -- Initial login does not request passord https://bugs.launchpad.net/bugs/546810 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 546810] Re: Initial login does not request passord
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/41945736/Dependencies.txt -- Initial login does not request passord https://bugs.launchpad.net/bugs/546810 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 351404] Re: UI work for adding p3a subscriptions
** This bug has been marked a duplicate of bug 351403 Key ID required on p3a user subscriptions ** This bug is no longer a duplicate of bug 351403 Key ID required on p3a user subscriptions ** This bug has been marked a duplicate of bug 45000 Icon in notification area gets invisible ** This bug is no longer a duplicate of bug 45000 Icon in notification area gets invisible -- UI work for adding p3a subscriptions https://bugs.launchpad.net/bugs/351404 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee (via bug 45000). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
