[Bug 1772913] Re: Android phone doesn't appear in shotwell
Worth monitoring: https://gitlab.gnome.org/GNOME/shotwell/issues/4 https://bugzilla.redhat.com/show_bug.cgi?id=1584876 ** Bug watch added: Red Hat Bugzilla #1584876 https://bugzilla.redhat.com/show_bug.cgi?id=1584876 ** Also affects: shotwell (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1584876 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1772913 Title: Android phone doesn't appear in shotwell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1772913/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c
Please see bug #228077 for information on the report upstream rejected for gnome-control-center. Leandro, I don't have a US keyboard anymore (nor did a read all the comments here), but if this is still an issue, I don't think a fix will appear anytime soon. Good luck on this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (46226). https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when typing 'c To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 228077] Re: libgtk2 immodules has cedilla disabled in en locales
*** This bug is a duplicate of bug 518056 *** https://bugs.launchpad.net/bugs/518056 ** This bug has been marked a duplicate of bug 518056 cedilla appears as accented c (ć instead of ç) when typing 'c -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/228077 Title: libgtk2 immodules has cedilla disabled in en locales To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/228077/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46226] Re: It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules
*** This bug is a duplicate of bug 518056 *** https://bugs.launchpad.net/bugs/518056 ** This bug is no longer a duplicate of bug 228077 libgtk2 immodules has cedilla disabled in en locales ** This bug has been marked a duplicate of bug 518056 cedilla appears as accented c (ć instead of ç) when typing 'c -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/46226 Title: It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/46226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12893] Re: Shouldn't put .Trash-$USER on removable devices
This bug is more than 10 years old, and all the other projects are marked as Fix Released, so I just closed the last one (Baltix). If you think it's still an issue and worth investigating, feel free to reopen the bug. If this is the case, I suggest you reopen the bug in the upstream bug tracker, where the development actually occurs. I'm sure if you work on a patch, they'll be more than happy to review it and consider merging. This way, many more projects will benefit from your work, instead of just Baltix. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/12893 Title: Shouldn't put .Trash-$USER on removable devices To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/12893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12893] Re: Shouldn't put .Trash-$USER on removable devices
** Changed in: baltix Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/12893 Title: Shouldn't put .Trash-$USER on removable devices To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/12893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 135548] Re: Action on critical battery isn't triggered
** Changed in: gnome-power-manager (Baltix) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/135548 Title: Action on critical battery isn't triggered To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/135548/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480904] Re: Sign in for google doesn't meet modern security standards
Also happens to me sometimes on Ubuntu. ** Also affects: empathy (Ubuntu) Importance: Undecided Status: New ** Changed in: empathy (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1480904 Title: Sign in for google doesn't meet modern security standards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1480904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 165113] Re: gksudo nautilus won't set ownership/permissions on files below
** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/165113 Title: gksudo nautilus won't set ownership/permissions on files below To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/165113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480904] Re: Sign in for google doesn't meet modern security standards
I have since removed and re-added my gtalk accounts, and have been using the workaround of bug #1069531 as often as required (killall signonpluginprocess). I don't know if this bug is related to bug #1069531. Maybe they are the duplicates? If this bug happens to me again, I'll try to find the time to investigate more. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1480904 Title: Sign in for google doesn't meet modern security standards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1480904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 206439] Re: smb password protected share cannot be accessed
** Changed in: gvfs (Baltix) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/206439 Title: smb password protected share cannot be accessed To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/206439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168582] Re: Google talk "Requires Authorization" after suspend/resume
*** This bug is a duplicate of bug 1069531 *** https://bugs.launchpad.net/bugs/1069531 ** This bug has been marked a duplicate of bug 1069531 Cannot login to Empathy after setting up Google online account -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1168582 Title: Google talk "Requires Authorization" after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1168582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1259422] Re: Google authentication error in empathy
*** This bug is a duplicate of bug 1069531 *** https://bugs.launchpad.net/bugs/1069531 ** This bug has been marked a duplicate of bug 1069531 Cannot login to Empathy after setting up Google online account -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1259422 Title: Google authentication error in empathy To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1259422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1064113] Re: can't connect to google apps gchat account "account requires authorisation"
*** This bug is a duplicate of bug 1069531 *** https://bugs.launchpad.net/bugs/1069531 ** This bug has been marked a duplicate of bug 1069531 Cannot login to Empathy after setting up Google online account -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1064113 Title: can't connect to google apps gchat account "account requires authorisation" To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1064113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 642792] Re: ALT+PrtSc not recognised: breaks built-in screenshot function
Added a kernel task to the bug. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- ALT+PrtSc not recognised: breaks built-in screenshot function https://bugs.launchpad.net/bugs/642792 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
Re: [Bug 33288] Re: Evince doesn't handle columns properly
Nigel, has the patch been committed to the Ubuntu package? I believe at this point, no major merges will be done, and this will have to be approved by release teams, so fix committed wouldn't apply. Please correct me if I'm mistaken. regards FF On Seg, 2010-04-19 at 14:06 +, Nigel Babu wrote: Changing to Fix Comitted since, patch has been accepted upstream. ** Tags added: patch-accepted-upstream ** Tags removed: patch-needswork ** Changed in: poppler (Ubuntu) Status: Triaged = Fix Committed ** Changed in: poppler (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned) -- Evince doesn't handle columns properly https://bugs.launchpad.net/bugs/33288 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 13983] Re: Evolution virtual trash / real trash on IMAP server
The upstream bug has a patch that has been considered to work. Can this be targeted for Karmic? If so, can I as a tester help in any way? I have little to none packaging skills, but I'm willing to spend a few hours if it will mean that this patch will make it into Karmic (assuming it's not already part of the next upstream release). Does the Ubuntu Evolution maintainer have info on the status of this patch regarding Karmic, if it's already ? -- Evolution virtual trash / real trash on IMAP server https://bugs.launchpad.net/bugs/13983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 13983] Re: Evolution virtual trash / real trash on IMAP server
** Attachment added: upstream patch - eds part http://launchpadlibrarian.net/30885841/gn206061_eds.patch -- Evolution virtual trash / real trash on IMAP server https://bugs.launchpad.net/bugs/13983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 13983] Re: Evolution virtual trash / real trash on IMAP server
** Attachment added: upstream patch - evo part http://launchpadlibrarian.net/30885863/gn206061_evo.patch -- Evolution virtual trash / real trash on IMAP server https://bugs.launchpad.net/bugs/13983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 211692] Re: F-Spot refused to close, force quit used
I think I found out how to work around this issue. Since an empty test account didn't show the behaviour, I decided moving my dirs and files out of ~ until I got f-spot to work. After a while of some trial and error, I nailed it down to ~/.gnupg. After that, I kept trying until I pinpointed the problem (at least for me) to gpg.conf. Since it was a nearly empty file (only three options, including default key and keyserver), I finally got to the offending option: use-agent Commenting this option was sufficient to make F-Spot close as expected. Could others affected see if this helps you as well? -- F-Spot refused to close, force quit used https://bugs.launchpad.net/bugs/211692 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
Re: [Bug 89983] Re: Feisty reports suspend failed after resuming from suspend
Geek2theCore escreveu: OK... i finally found the operative bug report (the duplicate) and that the sound thing is actually the sound: /usr/share/gnome-power-manager /gpm-suspend-failure.wav which is played on an error, so I just turned the error sound off in the Power Manager preferences. It was that or turn the bug into a feature by making the failure sound a QUIET little wave file that says in a HAL 9000 voice Welcome back. Now close the error message and we'll begin. If I could only get rid of it instead... You have a different bug, Bug #242713. -- Feisty reports suspend failed after resuming from suspend https://bugs.launchpad.net/bugs/89983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150187] Re: [gutsy] [regression] Evince has very bad quality when printing pdf files.
It looks from the patch that it requires cairo 1.8.2, so it would require a non-trivial backport for both hardy and intrepid. Could someone who actually understands it confirm this, and decide if this blocks an eventual SRU? ** Summary changed: - [gutsy] [regression] Evince has very bad quality when printing pdf files. + Evince has very bad quality when printing pdf files. ** Tags added: gutsy hardy intrepid regression -- Evince has very bad quality when printing pdf files. https://bugs.launchpad.net/bugs/150187 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 275806] Re: gnome-keyring-daemon should provide a command line option to GNOME_KEYRING_TEST_PATH
I jut did. http://bugzilla.gnome.org/show_bug.cgi?id=571425 It would help if someone (Sebastian?) could confirm if this functionality is also missing in newer gnome versions, since I use Hardy and 2.22.x is rather oldish. ** Bug watch added: GNOME Bug Tracker #571425 http://bugzilla.gnome.org/show_bug.cgi?id=571425 ** Also affects: gnome-keyring via http://bugzilla.gnome.org/show_bug.cgi?id=571425 Importance: Unknown Status: Unknown -- gnome-keyring-daemon should provide a command line option to GNOME_KEYRING_TEST_PATH https://bugs.launchpad.net/bugs/275806 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 242713] Re: Suspends that are longer than 6 hours will inexplicably claim to fail, but not really fail
I turned on the option to beep if problem occurs, and got a beep this morning, with the new version, so it seems it's not fixed for me, also. -- Suspends that are longer than 6 hours will inexplicably claim to fail, but not really fail https://bugs.launchpad.net/bugs/242713 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
On Sun, Feb 1, 2009 at 3:51 PM, hyperair hyper...@gmail.com wrote: On Sun, 2009-02-01 at 17:42 +, Christophe Sauthier (huats) wrote: Thanks for your work here. The thing is that there is already a new gnome-keyring version available (2.25.5.) which FTBFS for the moment on jaunty. I am currently working with upstream to fix that. I'll integrate your work in the next package for jaunty (this week I think). Okay, awesome. How about SRU for Intrepid after that? -- And Hardy also. Thanks hyperair. -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
On Sat, Jan 31, 2009 at 6:07 AM, hyperair hyper...@gmail.com wrote: On Sat, 2009-01-31 at 05:24 +, Bug Watch Updater wrote: ** Changed in: gnome-keyring Status: New = Fix Released Well, it seems upstream fixed the issue in trunk. So we just have to wait for the next release of gnome-keyring, and it should be fixed there. Or someone who has the proper skills gets the patch for that revision, and tries to use it in ubuntu's version. Maybe then, we can start a SRU process, if it's applicable. Volunteers? -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 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 268141] Re: no ssh-agent after resume from hibernate
** Also affects: gnome-keyring (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=454186 Importance: Unknown Status: Unknown -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 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 220165] Re: gnome-keyring-daemon cached passwords for SSH keys not working after hibernation
*** This bug is a duplicate of bug 268141 *** https://bugs.launchpad.net/bugs/268141 ** This bug has been marked a duplicate of bug 268141 no ssh-agent after resume from hibernate -- gnome-keyring-daemon cached passwords for SSH keys not working after hibernation https://bugs.launchpad.net/bugs/220165 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 268141] Re: no ssh-agent after resume from hibernate
I can confirm that hyperair's workaround works, and it's better, since it requires no user intervention, and it's easier for newbies. I still believe that this is a bug, not a feature, since there appears to be no obvious way to restart the g-k-m after a hibernation/suspend, if the mentioned options are active. I also agree that, for security reasons, the gnome_keyring_hibernate shouldn't come deactivated, because of bug #70752. However, it seems to me that solving bug #70752 by encrypting swap would make hibernation impossible. -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 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
Re: [Bug 150187] Re: [gutsy] [regression] Evince has very bad quality when printing pdf files.
You can recompile evince, same version you're using without any changes to the source. It will be recompiled to use the newest poppler. I did this to use poppler3 in hardy without any issues. On Mon, Jan 19, 2009 at 1:21 PM, Vincenzo Ciancia vincenzo...@yahoo.it wrote: The point is that the backported evince (using prevu) is using libpoppler3 instead of libpoppler4. Is there a quick way to have the backported evince use the backported libpoppler4 or to also build libpoppler3 from the backported poppler from prevu? -- [gutsy] [regression] Evince has very bad quality when printing pdf files. https://bugs.launchpad.net/bugs/150187 You received this bug notification because you are a direct subscriber of the bug. -- [gutsy] [regression] Evince has very bad quality when printing pdf files. https://bugs.launchpad.net/bugs/150187 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 212098] Re: easy file sharing not notifying about logout/login
You got it right, both on my sugestion and in the problem with it. What made me think about this was Colin's 29 and 30 comments. Maybe what I'm proposing is overkill, but let me try to clarify a bit. I think if Bug 238224 gets fixed for hardy, and a one time silent call to gksu makes libpam-smbpass create the NTLM hash, then the whole issue should be fixed for new installs. For old installs, creating sambashare by default and adding the user to it should work, provided the user logs out. Anyway, if the user upgrades this package, she needs to logout anyway, right? Rolling out a point release seems a reasonable moment to ask the user for a logout. A simple bubble notification should suffice, maybe with a link to a more detailed documentation (with whatever mechanism firefox asks for a restart, and the kernel asks for a reboot). I'm not sure what would be the most apropriate would be in user-setup, as indicated in bug 238224, or another package. Since the first already has a patch coming, it's obviously easier to go that route. IMHO, the elegant solution would be to do it in nautilus-share, since it's what needs it, and it's pulled in by ubuntu-desktop, so it would be default anyway. But this wouldn't be nice to non-Gnome *buntu derivatives, so samba-common would be my second most elegant sugestion. Again, the patch already exists for user-setup, and it's fine if the result is to get the group created and the first user in it by default. -- easy file sharing not notifying about logout/login https://bugs.launchpad.net/bugs/212098 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 212098] Re: easy file sharing not notifying about logout/login
I confirm the UI that asks for logout works. I tested on a laptop and a desktop, both on up to date Hardy installs. However it seems rather intrusive to the configuring process, since it doesn't even let the user finish configuring the share - it leaves the share created with default settings, which might not be the intention, and no information on what did or didn't happen. Is it possible to move the question to after the user clicks on the save button, instead of when s/he ticks the share checkbox? This would be far more smooth IMHO. -- easy file sharing not notifying about logout/login https://bugs.launchpad.net/bugs/212098 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 212098] Re: easy file sharing not notifying about logout/login
To other newbies around, here's the procedure I used to confirm. Steps 1-4 are not required, but I wanted to be extra careful: 1- Purge samba, samba-common, libpam-smbpass, and re-install smbclient (which pulls samba-common). 1'- remove the sambashare group 2- Logout, login 3- Try to create a usershare with nautilus, get notified of the need to install packages, accept, install 4- Notice the bug, logout, login, only then sharing is allowed, and shares work 5- remove user account from the sambashare group 6- install updated package 7- logout, login 8- Try to create a usershare with nautilus, get notified of the need to install packages, accept, install 9- get notified that a logout is needed, logout, login, sharing is allowed and shares work -- easy file sharing not notifying about logout/login https://bugs.launchpad.net/bugs/212098 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 212098] Re: easy file sharing not notifying about logout/login
Of course after so many steps, and logouts, I had to make some kind of confusion. Please disregard the part in my first comment about the intrusiveness of the UI - the share is *not* partly created with the 0ubuntu5 package, which is exactly what the bug report is about, duh. Also, if it wasn't clear, in the above confirmation procedure, steps 1-4 are to confirm the bug, 5-9 to confirm that the fix works. About the libpam part of the bug, since it suffices to enter the password for an administrative task, does this have to happen *after* the package is installed? I mean, can't the authentication needed for the package installation itself be somehow used for this? I don't know pam deeply, bug even if it doesn't provide this kind of functionality, gksu should still be cached by the time the installation and configuration finishes, so another call for gksu should silently succeed, taking care of the password sync. Or am I missing something here? -- easy file sharing not notifying about logout/login https://bugs.launchpad.net/bugs/212098 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
Re: [Bug 150187] Re: [gutsy] [regression] Evince has very bad quality when printing pdf files.
On Sun, 2008-11-02 at 11:28 +, Sebastien Bacher wrote: the bug has been fixed upstream now ** Changed in: poppler (Ubuntu) Status: Triaged = Fix Committed In what upstream version will it appear? Will the fix be backported to hardy and/or intrepid? regards FF -- [gutsy] [regression] Evince has very bad quality when printing pdf files. https://bugs.launchpad.net/bugs/150187 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 187127] Re: ssh always asks to unlock private key with no password set
I can't reproduce it with hardy. [EMAIL PROTECTED]:~$ apt-cache policy openssh-server openssh-server: Installed: 1:4.7p1-8ubuntu1.2 Candidate: 1:4.7p1-8ubuntu1.2 Version table: *** 1:4.7p1-8ubuntu1.2 0 500 http://br.archive.ubuntu.com hardy-updates/main Packages 500 http://security.ubuntu.com hardy-security/main Packages 100 /var/lib/dpkg/status 1:4.7p1-8ubuntu1 0 500 http://br.archive.ubuntu.com hardy/main Packages I tried logging with su - to a test user account, and also logging into gnome with that user, to the same result. The title says always, and it didn't happen to me in either environment. I also never seen this bug in normal usage. I attach the full transcript of the first experiment. ** Attachment added: test_wit_su-_transcript.txt http://launchpadlibrarian.net/19067537/test_wit_su-_transcript.txt -- ssh always asks to unlock private key with no password set https://bugs.launchpad.net/bugs/187127 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 187127] Re: ssh always asks to unlock private key with no password set
Is it possible that the reporter suffered from some miscofiguration? If the reporter needs to use ssh keys non-interactively, he could set a password and use a ssh-agent. -- ssh always asks to unlock private key with no password set https://bugs.launchpad.net/bugs/187127 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 138651] Re: evince doesn't display pdf as it should - low quality pdf font
*** This bug is a duplicate of bug 92296 *** https://bugs.launchpad.net/bugs/92296 ** This bug is no longer a duplicate of bug 20310 poor rendering ** This bug has been marked a duplicate of bug 92296 [Feisty] Low quality of text rendering in Evince -- evince doesn't display pdf as it should - low quality pdf font https://bugs.launchpad.net/bugs/138651 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 20310] Re: poor rendering
*** This bug is a duplicate of bug 92296 *** https://bugs.launchpad.net/bugs/92296 ** This bug has been marked a duplicate of bug 92296 [Feisty] Low quality of text rendering in Evince -- poor rendering https://bugs.launchpad.net/bugs/20310 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 92296] Re: [Feisty] Low quality of text rendering in Evince
Links from dup bug #138651 http://www.inference.phy.cam.ac.uk/mackay/network.pdf http://launchpadlibrarian.net/9205489/evince-175percent.png http://launchpadlibrarian.net/9205505/kpdf-175percent.png http://launchpadlibrarian.net/9205536/evince-100percent.png -- [Feisty] Low quality of text rendering in Evince https://bugs.launchpad.net/bugs/92296 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 268141] Re: no ssh-agent after resume from hibernate
I found that to use a workaround to restart gnome-keyring-daemon from command line in a way to reuse the existing socket: the env var GNOME_KEYRING_TEST_PATH. This var should be set to the /tmp/keyring- that was previously in use. For example: GNOME_KEYRING_TEST_PATH=/tmp/keyring-pw7JIX/ gnome-keyring-daemon ** Message: another SSH agent is running at: /tmp/keyring-pw7JIX/ssh GNOME_KEYRING_SOCKET=/tmp/keyring-pw7JIX//socket SSH_AUTH_SOCK=/tmp/keyring-pw7JIX//ssh GNOME_KEYRING_PID=24788 When I next try to use a ssh key, it asks to authenticate again (should it?), and it caches the keyphrase again. -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 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 268141] Re: no ssh-agent after resume from hibernate
There's no command line option to pass a directory to g-k-d in runtime. I'll open a wishlist bug to be triaged for this. -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 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 275806] [NEW] gnome-keyring-daemon should provide a command line option to GNOME_KEYRING_TEST_PATH
Public bug reported: Binary package hint: gnome-keyring Currently gnome-keyring-daemon has no documented command line options. In case the daemon dies or is t should have an option similar to ssh- agent's '-a' option in order to revive the agent using the socket previously created. This functionality exists in form of an environment var (GNOME_KEYRING_TEST_PATH) which can be set to the /tmp/keyring- that contains the socket to be reused, but an option to be run would useful, specially since this functionality is not documented anywhere and was discovered by looking directly in the code. ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- gnome-keyring-daemon should provide a command line option to GNOME_KEYRING_TEST_PATH https://bugs.launchpad.net/bugs/275806 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 268141] Re: no ssh-agent after resume from hibernate
I originally reported this bug against seahorse, since it appears as argument to ssh-agent in the processes list. I'd like to correct the testcase. Although it happened that seahorse died when I decided to post the bug, I cannot reproduce it, therefore I'm forced to attribute this event to chance. I confirm that the ssh-agent is not functional after hibernate, and now I have a new test-case that I can reproduce at will. Test case: 1- ps x | egrep agent|keyring 2- hibernate and thaw 3- ps x | egrep agent|keyring Step 1 returns: 7174 ?Ss 0:00 /usr/bin/ssh-agent /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession 7243 ?Ss 0:00 /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession 7291 ?SL 0:00 /usr/bin/gnome-keyring-daemon Step 3 returns: 7174 ?Ss 0:00 /usr/bin/ssh-agent /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession 7243 ?Ss 0:00 /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession 9489 pts/2S+ 0:00 egrep agent|keyring So, gnome-keyring-daemon is the process that dies. I'm assigning the bug to gnome-keyring package. This is gnome-keyring 2.22.2-0ubuntu1. The relevant directories in /tmp (/tmp/ssh-* and /tmp/keyrin*) are not deleted, but the pipe can't be reused without restarting gnome-keyring- daemon, and there's no documentation on how to restart it reusing the existing socket for this reason I can't use the workaround in bug #99065. Also, why does gnome-keyring-daemon crashes in the first place? The following is the only relevant line in $HOME/.xsession-errors ** Message: another SSH agent is running at: /tmp/ssh- UZKukL7062/agent.7062 This appears to be the same message I get from g-k-d, if I try to start it manually after hibernating. The process daemonizes, but there's no ssh-agent to be used: $ ssh localhost Error reading response length from authentication socket. Enter passphrase for key '/home/philsf/.ssh/id_dsa': ** Changed in: gnome-keyring (Ubuntu) Sourcepackagename: seahorse-plugins = gnome-keyring Status: Incomplete = New -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 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 273862] Re: seahorse notification icon doesn't appear anymore
** Also affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Description changed: I used to have a lock icon in the notification area indicating my ssh keyphrase is cached by the seahorse agent (I guess in feisty I still had it). I never seen it ever since the upgrade to gutsy, and it's also missing in hardy. Note that I didn't change any sort of configuration in Feisty-Gutsy upgrade, so it's a regression in usability. In gconf-editor, I made sure seahorse -- agent -- cache_display is checked, but it doesn't help. I can find no way to enable/disable this option in the Preferences GUI. + + Steps to reproduce: + + - enter ssh passphrase into the seahorse agent prompt + + What should happen: + + - Lock icon should appear in notification area, allowing you to clear + the cache in the GUI + + What happens: + + - No icon appears, although the agent caches the passphrase ** Tags added: regression -- seahorse notification icon doesn't appear anymore https://bugs.launchpad.net/bugs/273862 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 273862] Re: seahorse notification icon doesn't appear anymore
Positive. Check out, for example, bug #129231 I reported in the beginning of Feisty cycle. -- seahorse notification icon doesn't appear anymore https://bugs.launchpad.net/bugs/273862 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 268141] Re: no ssh-agent after resume from hibernate
Related bugs (not dups): bug #99065 and #70752 -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 268141] [NEW] no ssh-agent after resume from hibernate
Public bug reported: Binary package hint: seahorse After resume from hibernate (and not suspend) seahorse-daemon and seahorse-agent processes are not running, and there is no other ssh- agent available making it annoying to use ssh, and impossible to use sftp mounts in nautilus. Steps to reproduce: 1- ps x | grep seahorse 2- hibernate and resume (I use gnome-power-manager) 3- ps x | grep seahorse Step 3 returns nothing for me. Step 1 returns something like: 9554 ?Ss 0:00 seahorse-agent 9560 ?Ss 0:00 seahorse-daemon This is in Ubuntu 8.04, with latest updates. Seahorse version is 2.22.2-0ubuntu1. ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 89983] Re: Feisty reports suspend failed after resuming from suspend
I still get this bug in latest hardy. Here are some possibly relevant logs of it, now it's just happened. Any laptop-specific information needed is probably posted at bug 212660. ** Attachment added: syslog.log http://launchpadlibrarian.net/16869748/syslog.log -- Feisty reports suspend failed after resuming from suspend https://bugs.launchpad.net/bugs/89983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 89983] Re: Feisty reports suspend failed after resuming from suspend
** Attachment added: messages.log http://launchpadlibrarian.net/16869751/messages.log -- Feisty reports suspend failed after resuming from suspend https://bugs.launchpad.net/bugs/89983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 89983] Re: Feisty reports suspend failed after resuming from suspend
** Attachment added: dmesg.log http://launchpadlibrarian.net/16869754/dmesg.log -- Feisty reports suspend failed after resuming from suspend https://bugs.launchpad.net/bugs/89983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 89983] Re: Feisty reports suspend failed after resuming from suspend
** Attachment added: kern.log http://launchpadlibrarian.net/16869757/kern.log -- Feisty reports suspend failed after resuming from suspend https://bugs.launchpad.net/bugs/89983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 89983] Re: Feisty reports suspend failed after resuming from suspend
** Attachment added: user.log http://launchpadlibrarian.net/16869763/user.log -- Feisty reports suspend failed after resuming from suspend https://bugs.launchpad.net/bugs/89983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 89983] Re: Feisty reports suspend failed after resuming from suspend
** Attachment added: lsmod.log http://launchpadlibrarian.net/16869765/lsmod.log -- Feisty reports suspend failed after resuming from suspend https://bugs.launchpad.net/bugs/89983 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 105715] Re: gnome power manager applet is visually misleading
I don't think this bug reflects the linked upstream bug, since both are related to different themes. Uptream icons is probably the ones for the Clearlooks theme, or similar, while Ubuntu uses the Human theme, with a completely different battery icon (green instead of blue). Please see the screenshot attached to the upstream bug. I'm not familiar with the blue icon or how readable it is. The green icon is very readable, yet very misleading as the report says, still in Hardy (2.22.1). -- gnome power manager applet is visually misleading https://bugs.launchpad.net/bugs/105715 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 195095] Re: Get notification about sleep failed even though it seems to have gone well after suspend
*** This bug is a duplicate of bug 199088 *** https://bugs.launchpad.net/bugs/199088 ** This bug has been marked a duplicate of bug 199088 [Hardy] Message: Suspend Problem. Your computer failed to suspend -- Get notification about sleep failed even though it seems to have gone well after suspend https://bugs.launchpad.net/bugs/195095 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 105715] Re: gnome power manager applet is visually misleading
*** This bug is a duplicate of bug 74231 *** https://bugs.launchpad.net/bugs/74231 ** This bug has been marked a duplicate of bug 74231 Icon colour changes at inappropriate times (too early; red, yellow, green) -- gnome power manager applet is visually misleading https://bugs.launchpad.net/bugs/105715 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 199088] Re: [Hardy] Message: Suspend Problem. Your computer failed to suspend
*** This bug is a duplicate of bug 89983 *** https://bugs.launchpad.net/bugs/89983 ** This bug has been marked a duplicate of bug 89983 Feisty reports suspend failed after resuming from suspend -- [Hardy] Message: Suspend Problem. Your computer failed to suspend https://bugs.launchpad.net/bugs/199088 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 195095] Re: Get notification about sleep failed even though it seems to have gone well after suspend
*** This bug is a duplicate of bug 89983 *** https://bugs.launchpad.net/bugs/89983 ** This bug is no longer a duplicate of bug 199088 [Hardy] Message: Suspend Problem. Your computer failed to suspend ** This bug has been marked a duplicate of bug 89983 Feisty reports suspend failed after resuming from suspend -- Get notification about sleep failed even though it seems to have gone well after suspend https://bugs.launchpad.net/bugs/195095 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 93281] Re: Suspend failed message gives false advice
This is probably a dup of bug #161216 (or the other way around). Can someone decide and set it accordingly? -- Suspend failed message gives false advice https://bugs.launchpad.net/bugs/93281 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 161216] Re: Ubuntu reports suspend problem, but provides no detail on what went wrong
** This bug has been marked a duplicate of bug 89983 Feisty reports suspend failed after resuming from suspend -- Ubuntu reports suspend problem, but provides no detail on what went wrong https://bugs.launchpad.net/bugs/161216 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 161216] Re: Ubuntu reports suspend problem, but provides no detail on what went wrong
This is probably a dup of bug #93281 (or the other way around). Can someone decide and set it accordingly? ** This bug is no longer a duplicate of bug 89983 Feisty reports suspend failed after resuming from suspend -- Ubuntu reports suspend problem, but provides no detail on what went wrong https://bugs.launchpad.net/bugs/161216 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 113244] Re: g-p-m does not allow using battery percentage for policy in feisty
*** This bug is a duplicate of bug 135548 *** https://bugs.launchpad.net/bugs/135548 ** This bug has been marked a duplicate of bug 135548 [Gutsy] Action on critical battery isn't triggered - regression -- g-p-m does not allow using battery percentage for policy in feisty https://bugs.launchpad.net/bugs/113244 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 64751] Re: System dies instead of Suspend for Critical Battery
*** This bug is a duplicate of bug 135548 *** https://bugs.launchpad.net/bugs/135548 ** This bug has been marked a duplicate of bug 135548 [Gutsy] Action on critical battery isn't triggered - regression -- System dies instead of Suspend for Critical Battery https://bugs.launchpad.net/bugs/64751 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41215] Re: System dies instead of shutting down
*** This bug is a duplicate of bug 135548 *** https://bugs.launchpad.net/bugs/135548 ** This bug has been marked a duplicate of bug 135548 [Gutsy] Action on critical battery isn't triggered - regression -- System dies instead of shutting down https://bugs.launchpad.net/bugs/41215 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 221454] Re: laptop does not hibernate on low battery
*** This bug is a duplicate of bug 135548 *** https://bugs.launchpad.net/bugs/135548 ** This bug has been marked a duplicate of bug 135548 [Gutsy] Action on critical battery isn't triggered - regression -- laptop does not hibernate on low battery https://bugs.launchpad.net/bugs/221454 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 135479] Re: No low battery warning on Samsung X11-T5500 notebook
*** This bug is a duplicate of bug 135548 *** https://bugs.launchpad.net/bugs/135548 ** This bug has been marked a duplicate of bug 135548 [Gutsy] Action on critical battery isn't triggered - regression -- No low battery warning on Samsung X11-T5500 notebook https://bugs.launchpad.net/bugs/135479 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 135548] Re: [Gutsy] Action on critical battery isn't triggered - regression
** Tags added: data-loss -- [Gutsy] Action on critical battery isn't triggered - regression https://bugs.launchpad.net/bugs/135548 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 135548] Re: [Gutsy] Action on critical battery isn't triggered - regression
Upstream bug report says it's solved. Why is the solution not patched in Ubuntu? BTW, the workaround in comment 18 works for me, on a Lenovo 3000 v100 (Ubuntu 8.04). -- [Gutsy] Action on critical battery isn't triggered - regression https://bugs.launchpad.net/bugs/135548 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 216762] Re: Power manager on battery critical event
*** This bug is a duplicate of bug 135548 *** https://bugs.launchpad.net/bugs/135548 ** This bug has been marked a duplicate of bug 135548 [Gutsy] Action on critical battery isn't triggered - regression -- Power manager on battery critical event https://bugs.launchpad.net/bugs/216762 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 92296] Re: [Feisty] Low quality of text rendering in Evince
Bug #20310 also links to the same upstream bug. Are this and that one dups? (sure seems like). If someone decides to mark that as a dupe of this one (or the other way around), there might be interesting information there to repost here, for a centralized view of the issue. I'll try to link the screenshots. Screenshot comparing evince with kpdf http://launchpadlibrarian.net/1511057/Evince_Kpdf.png Screenshots from Bug #138651 (dupe from #20310) http://launchpadlibrarian.net/9205489/evince-175percent.png http://launchpadlibrarian.net/9205505/kpdf-175percent.png http://launchpadlibrarian.net/9205536/evince-100percent.png -- [Feisty] Low quality of text rendering in Evince https://bugs.launchpad.net/bugs/92296 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 128074] Re: strange font behaviour - connected letters
Even though it's not critical, I think it's important to fix this for hardy. It's a very bad advertising for an otherwise very good application (evince), and degrades the visibility of Ubuntu in general not to be able to properly handle what is expected to be a simple task, in the view of lay people (and indeed works with other apps). I decided to try fool evince into using poppler3 from intrepid. Intrepid version compiles fine on Hardy, and I managed to replace them with an ugly hack with symlinks between libpoppler.so.3/libpoppler.so.2 and libpoppler-glib.so.3/libpoppler-glib.so.2. Not surprisingly, it was very unstable, and evince crashed on mouseover actions, so I couldn't select/copy to test for other bugs (bug #33288 for example). But it kind of worked. I'm attaching a new screenshot of the result. It's still not perfect, the fi string still appear as an undefined (to me at least) ascii character (look for the first sentence in the abstract: We describe a unified Also appear in the last two of the abstract). Even so, readbility has improved vastly in this case. Unfortunately, I can't use this hack for production use, since they cause evince to crash more often than not. Is there a way to backport the needed patch(es) to -updates, or should I file a bug to hardy-backports so the whole 0.8.x is backported? ** Attachment added: Screenshot-097561u480.png http://launchpadlibrarian.net/15681507/Screenshot-097561u480.png -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128074] Re: strange font behaviour - connected letters
Even though it's not critical, I think it's important to fix this for hardy. It's a very bad advertising for an otherwise very good application (evince), and degrades the visibility of Ubuntu in general not to be able to properly handle what is expected to be a simple task, in the view of lay people (and indeed works with other apps). I decided to try fool evince into using poppler3 from intrepid. Intrepid version compiles fine on Hardy, and I managed to replace them with an ugly hack with symlinks between libpoppler.so.3/libpoppler.so.2 and libpoppler-glib.so.3/libpoppler-glib.so.2. Not surprisingly, it was very unstable, and evince crashed on mouseover actions, so I couldn't select/copy to test for other bugs (bug #33288 for example). But it kind of worked. I'm attaching a new screenshot of the result. It's still not perfect, the fi string still appear as an undefined (to me at least) ascii character (look for the first sentence in the abstract: We describe a unified Also appear in the last two of the abstract). Even so, readbility has improved vastly in this case. Unfortunately, I can't use this hack for production use, since they cause evince to crash more often than not. Is there a way to backport the needed patch(es) to -updates, or should I file a bug to hardy-backports so the whole 0.8.x is backported? -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128074] Re: strange font behaviour - connected letters
Sebastien, upstream says the patch was reintroduced a while ago. I still have this issue in hardy. -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 46226] Re: It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules
*** This bug is a duplicate of bug 228077 *** https://bugs.launchpad.net/bugs/228077 ** This bug has been marked a duplicate of bug 228077 libgtk2 immodules has cedilla disabled in en locales -- It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules https://bugs.launchpad.net/bugs/46226 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 228077] Re: libgtk2 immodules has cedilla disabled in en locales
Sebastien, I opened it in http://bugzilla.gnome.org/show_bug.cgi?id=532204, and promptly got an answer (notabug). I had to reopen it because I strongly disagree with the justification given, but I won't pursue this ad infinitum. In the event of it being denied again, can this issue be be solved in the Ubuntu (maybe Debian) side? ** Bug watch added: GNOME Bug Tracker #532204 http://bugzilla.gnome.org/show_bug.cgi?id=532204 ** Also affects: gtk via http://bugzilla.gnome.org/show_bug.cgi?id=532204 Importance: Unknown Status: Unknown -- libgtk2 immodules has cedilla disabled in en locales https://bugs.launchpad.net/bugs/228077 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 228077] Re: libgtk2 immodules has cedilla disabled in en locales
New comment from upstream (which I find satisfactory). Maybe then we should change the package from gtk to gnome-*? Comment #3 from Owen Taylor(gtk+ developer, points: 25) 2008-05-08 17:44 UTC [reply] English is also the second language of many people who ues C+acute as their first language. While their are certainly numerically more people who speak languages with the cedilla, there are some major languages (Polish in particular) that go the other way. (http://en.wikipedia.org/wiki/%C4%86, though I think the list there is not exhaustive.) There is a perfectly good way of representing I want a English UI but preferences for some other lanugage ... the LC_* variables. (GTK+ checks LC_CTYPE for picking the default IM module.) The fact that there is no good interface for setting this in GNOME is not a reason to change GTK+. As a bonus, this will give people the right collation, currency values, thousands separators, and so forth. ** Changed in: gtk+2.0 (Ubuntu) Status: New = Incomplete -- libgtk2 immodules has cedilla disabled in en locales https://bugs.launchpad.net/bugs/228077 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 228077] Re: libgtk2 immodules has cedilla disabled in en locales
** Changed in: gtk+2.0 (Ubuntu) Status: Incomplete = Invalid ** Bug watch added: GNOME Bug Tracker #333104 http://bugzilla.gnome.org/show_bug.cgi?id=333104 ** Also affects: gnome-control-center via http://bugzilla.gnome.org/show_bug.cgi?id=333104 Importance: Unknown Status: Unknown ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- libgtk2 immodules has cedilla disabled in en locales https://bugs.launchpad.net/bugs/228077 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 228077] Re: libgtk2 immodules has cedilla disabled in en locales
** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: New = Confirmed -- libgtk2 immodules has cedilla disabled in en locales https://bugs.launchpad.net/bugs/228077 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 228077] Re: libgtk2 immodules has cedilla disabled in en locales
** Bug watch added: Red Hat Bugzilla #432963 https://bugzilla.redhat.com/show_bug.cgi?id=432963 ** Also affects: gnome-control-center (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=432963 Importance: Unknown Status: Unknown -- libgtk2 immodules has cedilla disabled in en locales https://bugs.launchpad.net/bugs/228077 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 228077] [NEW] libgtk2 immodules has cedilla disabled in en locales
Public bug reported: Binary package hint: libgtk2.0-0 [EMAIL PROTECTED]:~$ lsb_release -rd Description:Ubuntu 8.04 Release:8.04 [EMAIL PROTECTED]:~$ apt-cache policy libgtk2.0-0 libgtk2.0-0: Installed: 2.12.9-3ubuntu3 One can't use dead keys to input a c+cedilla in en_US (probably other en_* locales). I had this on Gutsy. Now in Hardy, I thought I should report, since it's annoying, and the fix is documented. Steps to reproduce: - enable deadkeys - Open gnome-terminal (or firefox) and enter ' + c What you should get: ç What you do get: ć Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ): Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and include :en in the cedilla line 6c6 cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa --- cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa:en ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New -- libgtk2 immodules has cedilla disabled in en locales https://bugs.launchpad.net/bugs/228077 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 61919] Re: sticky notes should stay when user clicks on desktop
You are correct, Dante, it still works as advertised. I get the expected behaviour after clearing gnome/gconf config dot-files and reconfiguring from scratch. I agree it's a desirable wishlist, even though I like it the way it is. Hope upstream gets it done by the next gnome release. -- sticky notes should stay when user clicks on desktop https://bugs.launchpad.net/bugs/61919 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 61919] Re: sticky notes should stay when user clicks on desktop
I agree with Andy. It worked according to the documentation on Feisty, but on Gutsy they don't hide anymore when clicking on the Desktop. -- sticky notes should stay when user clicks on desktop https://bugs.launchpad.net/bugs/61919 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 128074] strange font behaviour - connected letters
Public bug reported: Binary package hint: evince Hello, in a particular PDF I have, the letters seem strangely connected, and some appear as symbols. The same file appears nicely in xpdf and adobe reader. I'm including a screenshot. How can I provide better information to get it fixed? ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128074] Re: strange font behaviour - connected letters
I forgot to mention I'm using Feisty. Here's the screenshot. ** Attachment added: evince-feisty.png http://launchpadlibrarian.net/8561960/evince-feisty.png -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 128074] Re: strange font behaviour - connected letters
And here's the original file. evince prints it ok, FWIW (except for bug #120861, but that can be worked around). ** Attachment added: Pybus_et_al_2000_Genetics.pdf http://launchpadlibrarian.net/8561964/Pybus_et_al_2000_Genetics.pdf -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120861] Re: printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely
Just to add that after purging and recreating all printer configurations, I am now able to print in bw with evince, provided everytime I open it, I change from 'Normal Color', to 'Grayscale'. Still annoying, but at least it works. -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely https://bugs.launchpad.net/bugs/120861 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 120861] Re: printout mode always starts with Normal (Color cartrigde) only, skipping black cartridge completely
** Summary changed: - printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely + printout mode always starts with Normal (Color cartrigde) only, skipping black cartridge completely -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartridge completely https://bugs.launchpad.net/bugs/120861 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
Re: [Bug 120861] Re: printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely
Sebastien, If there is a fix, can I get/apply the fix or workaround still in feisty? -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely https://bugs.launchpad.net/bugs/120861 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 120861] Re: printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/8107923/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/8107924/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/8107925/ProcStatus.txt -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely https://bugs.launchpad.net/bugs/120861 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120861] printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely
Public bug reported: Binary package hint: evince This doesn't happen to acroread or kpdf. Other gtk apps that use gnome print system (openoffice and firefox) also don't suffer, so I am reporting on evince only. Everytime I start evince, the Advanced tab in Print option in General menu is reconfigured so that it only uses the color cartridge. Even if I change Printout Mode and/or Resolution, Quality, Ink Type and Media Type to use the black cartridge, evince seems to ignore this and still uses only the color cartridge. This is especially bad for me since I currently only have a black cartridge, so paper comes out completely white, making evince useless for printing PDFs. This happens on two Feisty computers (desktop and laptop) I have here. Not sure if it's relevant, but the printer is a HP OfficeJet 4255, using hpijs (recommended) - HPLIP 1.7.3 OfficeJet 4200 driver. ProblemType: Bug Architecture: i386 Date: Sun Jun 17 12:57:03 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/evince Package: evince 0.8.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: evince ProcCwd: /home/philsf ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:pt_PT SourcePackage: evince Uname: Linux peralta 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux ** Affects: evince (Ubuntu) Importance: Undecided Status: Unconfirmed -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely https://bugs.launchpad.net/bugs/120861 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
