[Bug 1317752] [NEW] Right-clicking a file, choosing Open With - Other Application provides no way to run an arbitrary command on the file
Public bug reported: I installed Sublime Text 3 from a third-party source. That installed and worked fine, and it shows up in the Applications menu as normal. When I right click any file (I've tried Makefiles and .txt files), click Open With, then click Other Application, there's a list of possible programs I can open the given file from. Problem is, if the program I want to use isn't on that list, I can't use it--i.e. I can't put in an arbitrary command that can be saved and used in the future. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri May 9 02:03:14 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'800x550+0+24' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-09-26 (224 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-11-01 (188 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1317752 Title: Right-clicking a file, choosing Open With - Other Application provides no way to run an arbitrary command on the file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1317752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1201095] Re: gnome-panel crashes after launching steam game (Thomas was alone)
gnome-system-monitor also crashes. This means that Unity-based setups are also affected. And it also happens on my Thinkpad with Intel graphics, no proprietary drivers of any kind installed. This makes the fglrx theory implausible to me and means it affects fully Canonical-supported setups. Tests to reproduce can be made with the MiniMetro game alpha version from here: http://dinopoloclub.com/minimetro/ Steps to reproduce: -Launch gnome-system-monitor -Launch MiniMetro -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1201095 Title: gnome-panel crashes after launching steam game (Thomas was alone) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1201095/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1298666] Re: Preferences option not present in Edit menu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1298666 Title: Preferences option not present in Edit menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1298666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1298666] Re: Preferences option not present in Edit menu
Okay, this is, of course, not a bug per se but one big fat sign that the GNOME usability people have really been messing things up recently. As it turns out, there are the usual menus in the gedit window (File, Edit, ...). BUT. Because Apple II only had a screen size of 280×192, clearly in 2014 you have to have menus in the GNOME Shell top bar to save screen estate. On a twin 1920x1200 display setup. And to totally confuse users, some menu items, that used to be in the fricking Edit menu for like ages, have to move to that GNOME Shell top bar application menu. Presumably to justify its existence. So, yes, the item is still there - it just moved to another entirely different menu. I guess we all have to drink a bit more of that OS X Koolaid to get just how awesome it is that the menu for application Y on screen 1 is in the Shell title bar on screen 3 mere 80 centimeters away. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1298666 Title: Preferences option not present in Edit menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1298666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1282372] Re: [MIR] colord-gtk
$ ./change-override -c main -S colord-gtkOverride component to main colord-gtk 0.1.25-1.1 in utopic: universe/graphics - main gir1.2-colordgtk-1.0 0.1.25-1.1 in utopic amd64: universe/introspection/optional/100% - main gir1.2-colordgtk-1.0 0.1.25-1.1 in utopic arm64: universe/introspection/optional/100% - main gir1.2-colordgtk-1.0 0.1.25-1.1 in utopic armhf: universe/introspection/optional/100% - main gir1.2-colordgtk-1.0 0.1.25-1.1 in utopic i386: universe/introspection/optional/100% - main gir1.2-colordgtk-1.0 0.1.25-1.1 in utopic powerpc: universe/introspection/optional/100% - main gir1.2-colordgtk-1.0 0.1.25-1.1 in utopic ppc64el: universe/introspection/optional/100% - main libcolord-gtk-dev 0.1.25-1.1 in utopic amd64: universe/libdevel/optional/100% - main libcolord-gtk-dev 0.1.25-1.1 in utopic arm64: universe/libdevel/optional/100% - main libcolord-gtk-dev 0.1.25-1.1 in utopic armhf: universe/libdevel/optional/100% - main libcolord-gtk-dev 0.1.25-1.1 in utopic i386: universe/libdevel/optional/100% - main libcolord-gtk-dev 0.1.25-1.1 in utopic powerpc: universe/libdevel/optional/100% - main libcolord-gtk-dev 0.1.25-1.1 in utopic ppc64el: universe/libdevel/optional/100% - main libcolord-gtk1 0.1.25-1.1 in utopic amd64: universe/libs/optional/100% - main libcolord-gtk1 0.1.25-1.1 in utopic arm64: universe/libs/optional/100% - main libcolord-gtk1 0.1.25-1.1 in utopic armhf: universe/libs/optional/100% - main libcolord-gtk1 0.1.25-1.1 in utopic i386: universe/libs/optional/100% - main libcolord-gtk1 0.1.25-1.1 in utopic powerpc: universe/libs/optional/100% - main libcolord-gtk1 0.1.25-1.1 in utopic ppc64el: universe/libs/optional/100% - main Override [y|N]? y 19 publications overridden. ** Changed in: colord-gtk (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to colord-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1282372 Title: [MIR] colord-gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord-gtk/+bug/1282372/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1265846] Re: gedit crashes when dblclicking on unloaded server bookmark
** Description changed: Ubuntu 13.10, gedit 3.8.3-0ubuntu3 I have a server bookmark added via Nautilus, when it's unconnected and I press it in Nautilus, it connects. But when I doubleclick it in gedit files panel (on the left), gedit crashes. When I doubleclick it while connected, it's ok, problem is only when unconnected. Happens with various servers. + + Edit: Bug still happens in Ubuntu 14.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1265846 Title: gedit crashes when dblclicking on unloaded server bookmark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1265846/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #54) trust_level_to_str(): I'd mention encrypt using OTR to be clearer and avoid confusion my server encryption. Fixed. return _(The conversation is currently unencrypted.); I'd say unencrypted with OTR to stay coherent and crystal clear. Your branch looks good to me. I'm fine merging it to Empathy master as soon as the Gabble branch lands. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317810] [NEW] After booting keyboard language isnt correct.
Public bug reported: Problem exists since 13.10 so i know this bug. I dated Ubuntu up to 14.04 and sometimes the keyborad settings are working and sometimes not. But the Problem exists only after booting the system. I have chose German language but if i want type after booting the special symbols and the correct signs are not able to use. If i look after the keyboard options on the right corner from the desktop so i can see the De-sign... so i guess it should work. But it dont. If i go on this keyborad options and chose the De option again (i chose the chosen) so it works without any futher problems until the next boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20140410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 9 11:17:13 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service InstallationDate: Installed on 2014-02-01 (96 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2014-04-18 (20 days ago) ** Affects: indicator-keyboard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1317810 Title: After booting keyboard language isnt correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1317810/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1069531] Re: Cannot login to Empathy after setting up Google online account
Killing signonpluginprocess worked for me too. 13.10. -- 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/1069531 Title: Cannot login to Empathy after setting up Google online account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1069531/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
From a (very) quick look on the Gabble branch, it seems that all the channel messages are now sent through OTR (if built with it), even when it has not been activated. Is that really what we want? Also, shouldn't we use it only for contact channels? -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1157654] Re: Sound recorder does not work
Hi. I've just installed a Ubunt14.04 amd64 and gnome-sound-recorder does not work. It's the same problem as we can see in the video of James Lewis. If I clik on the red button one more time, I've got this response in a terminal : (gnome-sound-recorder:9720): GStreamer-WARNING **: Element 'gconfaudiosource' already has parent I can record sound on my computer using Adacity without problems. Thanks. ** Attachment added: Result of pactl list sources https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/1157654/+attachment/4108554/+files/pactllistsources.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/1157654 Title: Sound recorder does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/1157654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1316509] Re: GtkFileChooser crashes due to a signal connection left behind by GtkMountOperation
Thanks, sponsored the SRU ** Changed in: gtk+2.0 (Ubuntu) Importance: Undecided = High ** Changed in: gtk+2.0 (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1316509 Title: GtkFileChooser crashes due to a signal connection left behind by GtkMountOperation To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1316509/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317599] Re: Evince doesn't show fi-ligatures in a pdf file
I see the same behavior also in okular. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1317599 Title: Evince doesn't show fi-ligatures in a pdf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1317599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317884] [NEW] Problem during upgrade from 10.4 to 12.1
Public bug reported: cannot copy extracted data for './usr/lib/python2.7/dist- packages/gtk-2.0/gtk/_gtk.so' to '/usr/lib/python2.7/dist- packages/gtk-2.0/gtk/_gtk.so.dpkg-new': unexpected end of file or stream ** Affects: pygtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1317884 Title: Problem during upgrade from 10.4 to 12.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1317884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1315579] Re: When using scim-m17n in gedit, the backspace and delete keys are dysfunctional
Hi, On Sun, May 04, 2014 at 07:22:31AM -, Gunnar Hjalmarsson wrote: Hi Osamu and Aron! Subscribed you to this bug to ask if any of you have heard of a similar problem with m17n in ibus and/or fcitx. I have not heard of any nor I use m17n. But I see others found fcitx works and scim and ibus do not. Quite frankly, this is most likely bug in gedit not following properly. I remember gedit was the only app refusing to work with scim when I was involved. It turned out it was gedit bug not doing right things with its input. So just because fcitx seems to work does not mean it is bug in ibus and scim. If this problem is seen in other apps, then I am worried. Do we see ? I doubt it. Regards, Osamu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1315579 Title: When using scim-m17n in gedit, the backspace and delete keys are dysfunctional To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1315579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317895] [NEW] facebook images isn't shown but instead a link
Public bug reported: When receiving a image in a Facebook message no image is shown, but is instead linked and has to be opened in a browser. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: empathy 3.8.6-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 9 14:41:29 2014 InstallationDate: Installed on 2014-04-09 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323) ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1317895 Title: facebook images isn't shown but instead a link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1317895/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317898] [NEW] no way of sending images or other files using empathy
Public bug reported: There's no way of sending images or other kind of files to contacts in Empathy. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: empathy 3.8.6-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 9 14:44:15 2014 InstallationDate: Installed on 2014-04-09 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323) ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1317898 Title: no way of sending images or other files using empathy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1317898/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1315579] Re: When using scim-m17n in gedit, the backspace and delete keys are dysfunctional
Thanks for your comments, Osamu! Further tests showed that the problem is not m17n specific, but it's scim and gedit that don't work together with respect to the backspace and delete keys. Neither ibus nor fcitx has that issue. (The ibus issue Swarup mention above is something else.) So, is it a bug in gedit and/or scim? For now bug reports have been filed against both packages. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1315579 Title: When using scim-m17n in gedit, the backspace and delete keys are dysfunctional To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1315579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515155] Re: unlocking screensaver hangs when ecryptfs is unmounted
Still observing this on 14.04, and first observed starting in 13.10. I'm not using an encrypted filesystem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/515155 Title: unlocking screensaver hangs when ecryptfs is unmounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/515155/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1283397] Re: videos only take up 1/4 (one quarter/fourth) of the window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-sushi (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1283397 Title: videos only take up 1/4 (one quarter/fourth) of the window To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-sushi/+bug/1283397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1283397] Re: videos only take up 1/4 (one quarter/fourth) of the window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: totem (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1283397 Title: videos only take up 1/4 (one quarter/fourth) of the window To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-sushi/+bug/1283397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1283397] Re: videos only take up 1/4 (one quarter/fourth) of the window
I am using a Lenovo w540 with ubuntu gnome 14.04 my screen has a resolution of 2880 x 1620. let me know if you want me to add further information to this report -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1283397 Title: videos only take up 1/4 (one quarter/fourth) of the window To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-sushi/+bug/1283397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #56) From a (very) quick look on the Gabble branch, it seems that all the channel messages are now sent through OTR (if built with it), even when it has not been activated. Is that really what we want? Yes, that's what pidgin-otr does as well. That's because all received messages needs to be parsed by OTR first because it will catch message starting with ?OTR? because when receiving that it means the other side wants to start an OTR session. In that case the message is considered as internal OTR protocol message and it returns ignore=true so we don't dispaly that to the user. We could avoid passing sending messages to OTR when session is not started indeed. I didn't do that because OTR will just return a copy of the initial message so it doesn't change anything (just wasting CPU cycles), and I prefer not adding any conditions to make damn sure we never have the case where we send something that didn't got encrypted first. Also, shouldn't we use it only for contact channels? I don't think OTR can be used on MUC, or at least that's out of scope for now. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 906472] Re: Emoticons not shown on global menu
*They are blank on the global menu, not in conversations. -- 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/906472 Title: Emoticons not shown on global menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/906472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 906472] Re: Emoticons not shown on global menu
I also have this bug in ubuntu 14.04 where smileys are blank. -- 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/906472 Title: Emoticons not shown on global menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/906472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1238346] Re: on bootup wrong keyboard layout is recognized
@YoBoY tried it out with 14.04 and resolved the problem perfectly. Many thanks Christian -- 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/1238346 Title: on bootup wrong keyboard layout is recognized To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1238346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1265846] Re: gedit crashes when dblclicking on unloaded server bookmark
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a .crash file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding. ** Changed in: gedit (Ubuntu) Importance: Undecided = Low ** Changed in: gedit (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1265846 Title: gedit crashes when dblclicking on unloaded server bookmark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1265846/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1315388] Re: GDM not showing session options
Well, I just installed for the 3rd or 4th time the package gdm, and the problem is solved?! And it was the exact same version that I had already installed!? So, now I have all de xsession/de options available! What as made me very sad is that note a single answer from anyone in launchpad regarding my issue! So I ask myself if theres is any point on reporting bugs and problems here?! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1315388 Title: GDM not showing session options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1315388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224732] Re: Custom keyboard shortcuts don't work
Googling a little shows up that some other people are also affected by this problem: - http://ubuntuforums.org/showthread.php?t=2218418 - http://www.ubuntuask.com/q/answers-after-upgrading-to-ubuntu-14-04-my-shortcuts-keys-and-media-keys-no-longer-work-451842.html - http://askubuntu.com/questions/453709/global-keyboard-shortcuts-broken-in-14-04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1307631] Re: lost focus problem in icon view mode
This bug has been reported here: https://bugzilla.gnome.org/show_bug.cgi?id=729885 ** Bug watch added: GNOME Bug Tracker #729885 https://bugzilla.gnome.org/show_bug.cgi?id=729885 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1307631 Title: lost focus problem in icon view mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1307631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1307631] Re: lost focus problem in icon view mode
** Changed in: nautilus (Ubuntu) Status: Confirmed = Triaged ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=729885 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1307631 Title: lost focus problem in icon view mode To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1307631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1307631] Re: lost focus problem in icon view mode
** Changed in: nautilus Status: Unknown = New ** Changed in: nautilus Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1307631 Title: lost focus problem in icon view mode To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1307631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1316509] Re: GtkFileChooser crashes due to a signal connection left behind by GtkMountOperation
For the record this has now been applied to gtk2 upstream. https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24id=c9da8bddca8f4e75e2ac6d7b362dd90fe7a844bc -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1316509 Title: GtkFileChooser crashes due to a signal connection left behind by GtkMountOperation To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1316509/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317994] [NEW] Rhythmbox doesn't sync mtp device correctly
Public bug reported: I have a SONY player NWZ-E443. I also have a favourite playlist, which I want to sync with the player. So there is the problem. When I syncing second, third and etc times, Rhythmbox deletes 56 files (I do not want why 56 yet) and copies them back. My favourite playlist has 117 songs. mike@mike-laptop:~$ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 mike@mike-laptop:~$ apt-cache policy rhythmbox rhythmbox: Installed: 3.0.2-0ubuntu2 Candidate: 3.0.2-0ubuntu2 Table of versions *** 3.0.2-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: mtp rhythmbox ** Attachment added: Снимок экрана от 2014-05-09 21:26:01.png https://bugs.launchpad.net/bugs/1317994/+attachment/4108840/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202014-05-09%2021%3A26%3A01.png -- 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/1317994 Title: Rhythmbox doesn't sync mtp device correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1317994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317994] Re: Rhythmbox doesn't sync mtp device correctly
** Attachment removed: Снимок экрана от 2014-05-09 21:26:01.png https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1317994/+attachment/4108840/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202014-05-09%2021%3A26%3A01.png ** Attachment added: Screenshot from walkman properties https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1317994/+attachment/4108842/+files/Screenshot%20from%202014-05-09%2021%3A44%3A15.png -- 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/1317994 Title: Rhythmbox doesn't sync mtp device correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1317994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
Just doing the spec right now:
The extra DBus channel interface is implemented using GDBus
so it needs to be exported on a different bus name.
Ugh. Can we not do strange hacks like this, please? Either use the
extensions mechanism, or save it for 1.0.
+ interface name=im.telepathy.v1.Channel.Interface.OTR1
+ tp:causes-havoc=experimental
+ tp:added version=Gabble 0.UNRELEASED(Gabble-specific)/tp:added
If doing this in 0.x, please use o.fd.Channel.Interface.OTR1 and add it
to telepathy-spec (OK to go via extensions/ until we do the spec - tp-
glib dance, though).
In 1.0, certainly add it to the spec.
+ A simple D-Bus API a
+ href=https://otr.cypherpunks.ca/;Off The Record/a.
... API for a...
+ pThe current trust level of this channel:
+ 0=TRUST_NOT_PRIVATE, 1=TRUST_UNVERIFIED, 2=TRUST_PRIVATE,
+ 3=TRUST_FINISHED/p
This deserves a tp:enum and documentation.
I assume the meanings go something like this:
TRUST_NOT_PRIVATE: not using OTR at all? (Can we also see this when using OTR
but something has gone wrong?)
(o.fd.Channel.I.Securable.Encrypted=FALSE,
o.fd.Channel.I.Securable.Verified=FALSE)
TRUST_UNVERIFIED: the channel is encrypted, but you might be talking to
a man-in-the-middle instead of the peer you expected.
(o.fd.Channel.I.Securable.Encrypted=TRUE,
o.fd.Channel.I.Securable.Verified=FALSE)
TRUST_PRIVATE: the channel is encrypted, and the user has indicated that the
peer's key fingerprint is trusted to belong to that peer.
(o.fd.Channel.I.Securable.Encrypted=TRUE,
o.fd.Channel.I.Securable.Verified=TRUE)
TRUST_FINISHED: this channel is over, nothing more should be sent or received
on it.
(o.fd.Channel.I.Securable.Encrypted and o.fd.Channel.I.Securable.Verified keep
their previous values?)
What are the possible state transitions? I assume can only increase?
+ type=(say) access=read
+ pUser's current fingerprint. The first element is a human readable
+ fingerprint that can be displayed to the user so he can communicate it
+ to the other end by other means so he can trust it. The 2nd element is
+ the fingerprint raw data./p
Are these literally the hex and binary versions of the same digest, or
do they have different information content? (Or is the string version
some OTR-specific thing that is easier to transcribe than hex?)
+ property name=RemoteFingerprint
+ tp:name-for-bindings=Fingerprint
+ type=(say) access=read
+ tp:docstring xmlns=http://www.w3.org/1999/xhtml;
What value does this take when the channel is not using OTR? ('', [])?
When we're in the UNVERIFIED state, am I right in thinking that we are
cryptographically guaranteed to have the right fingerprint for who we're
talking to, but the thing that is unverified is that the fingerprint
belongs to the person we wanted to talk to? (i.e. if we're talking to a
man-in-the-middle, this would be the fingerprint of the man-in-the-
middle's key, right?)
Is it possible for this to change? (Presumably from ('', []) to non-
empty, at the same time that the trust changes to UNVERIFIED or
PRIVATE?)
After this has become non-empty, can it change further? (I would hope
not.)
I think it would also be useful to spec that one of the forms of the
remote fingerprint will appear in the message header (0'th part) of each
individual message, perhaps { otr-remote-fingerprint: a string }. That
would make it easy for someone to do either of these things in a race-
condition-free way:
* record in the Logger that the messages were encrypted/verified
* give the Logger a configuration setting [ ] do not log OTR messages
(which it would recognize by seeing that they have an OTR remote fingerprint
--
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/296867
Title:
empathy needs to support OTR encryption
To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
Implementation in Gabble:
+ /* FIXME: There should be no sender for a notification, but setting handle to
+ * 0 makes empathy crash atm. */
+ tp_message_mixin_take_received (G_OBJECT (self),
+ tp_cm_message_new_text (base_conn,
+ tp_base_channel_get_target_handle (base_chan),
+ TP_CHANNEL_TEXT_MESSAGE_TYPE_NOTICE, text));
Is this a message from the OTR library, something like *** Verified
peer fingerprint: b...@example.com ***?
I think using the target handle for this is OK semantically.
However, I suspect remote users can spoof this by sending their own
NOTICE. Messages coming from the OTR library should have a distinctive
message header that an OTR-literate UI can take as evidence that they
were locally-generated.
Ideally, that distinctive message header should be a machine-readable
version of the message, so OTR-literate UIs (Empathy) can discard the
untranslated version from Gabble and display something translated. We've
always had a policy of putting UI strings and their translations in the
UIs, not the CMs.
+ return g_variant_new ((s@ay), display_fp,
+ g_variant_new_fixed_array (G_VARIANT_TYPE_BYTE, fp_raw, 20,
...
+ guchar our_fp_raw[20];
The magic number 20 makes me nervous. Isn't there a constant for length
of a raw OTR fingerprint in bytes in libotr?
If there really isn't, #define'ing our own would be better than nothing.
+static void
+otr_inject_message (void *opdata,
+ const gchar *accountname,
+ const gchar *protocol,
+ const gchar *recipient,
+ const gchar *message)
+{
+ inject_message (opdata, message);
+}
Is @message text/plain or text/html? Telepathy can only do text/plain at
the moment, so if it's text/html, we need to strip tags, then unescape
entities (stuff;).
+static gint
+otr_max_message_size (void *opdata,
+ ConnContext *context)
+{
+ return 0;
+}
We should probably give some guess at what's generally interoperable.
+ msg = otrl_proto_default_query_msg (get_self_id (self),
OTRL_POLICY_DEFAULT);
Do we need to update what otr_policy() would return here, too?
+ bus_name = g_strconcat (tp_base_connection_get_bus_name (base_conn),
+ .OTR, NULL);
I suppose this isn't *so* bad, but the spec should tell the API user
where to find this name.
+ content = wocky_node_get_content_from_child (node, body);
+
+ err = otrl_message_sending (userstate, ui_ops_p, self,
+ get_self_id (self), xmpp, get_target_id (self),
+ priv-instag, content, NULL, new_content,
+ OTRL_FRAGMENT_SEND_ALL_BUT_LAST, NULL,
+ NULL, NULL);
Does otrl_message_sending() expect @content to be text/plain or
text/html? If it expects text/html, we need to escape special characters
with g_markup_escape_text().
Similarly, is @new_content text/plain or text/html? If text/html, we
need to strip tags and unescape entities.
+gchar *
+gabble_im_channel_otr_receiving (GabbleIMChannel *self,
+ const gchar *content)
Same here.
--
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/296867
Title:
empathy needs to support OTR encryption
To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
I would really like im-channel to implement o.fd.Telepathy.Securable - as a starting point we can have the two booleans not be requestable, and just have them set by the OTR code calling a new gabble_im_channel_indicate_security (GABBLE_SECURABLE_ENCRYPTED|GABBLE_SECURABLE_VERIFIED) (or only one of those, or neither of those, as appropriate). I notice we never specified how those properties did change notification, because our only use of them so far was for SASL channels. Let's retcon them to they emit PropertiesChanged in the 0.x and 1.0 spec. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #50) Could we also get a config option that turns this whole feature on/off? I ask because some industries (like the one where I work) require that all electronic communications related to the business get recorded and reviewed by compliance officers and made available to regulatory agencies upon request. I think we do need a connection parameter to control this. I think the possible sensible settings are: - never use OTR, behave exactly as though it was not implemented - start an OTR conversation if the local user or remote peer explicitly requests it - try to start OTR conversations automatically I think that would be most comprehensible as two booleans: something like enable-otr (default false initially, default true after a couple of releases) and enable-opportunistic-otr (not implemented in Xavier's patch, but someone could add it). The writer of Comment #50 would explicitly set enable-otr to false; the people getting excited about this bug would explicitly set enable-otr to true, and when implemented, probably also set enable-opportunistic-otr to true. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
Corner cases: What happens when we try to send a message and the channel is already TRUST_FINISHED? I think we should refuse, for the rest of the lifetime of that channel (until Close()), to avoid the security flaw where we send messages to a channel that just closed. What happens when we close a channel locally? I think the answer should be we terminate the OTR session, and start from an unsecured state next time - even if the channel is in fact going to respawn due to unacknowledged messages. This means the channel needs to reset its Encrypted flag, Verified flag and all OTR state when it respawns. We will still be able to tell the rescued messages were encrypted/verified because the header that I suggested adding will say so. What happens if I'm talking to b...@example.com/Laptop using OTR, and I receive a message from b...@example.com/Phone without OTR? I hope the answer is libotr deals with it and reports OTRL_MSGEVENT_RCVDMSG_UNENCRYPTED. Is it safe (as in, not a security vulnerability) to rely on that? What happens when we receive a message and the channel is already TRUST_FINISHED? I hope the answer is libotr deals with it and reports OTRL_MSGEVENT_RCVDMSG_UNENCRYPTED. Is it safe (as in, not a security vulnerability) to rely on that? -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1241972] Re: Drag and drop from Dash to Desktop doesn't work
@krychek that launcher dragging bug from the dash does not effect me but the desktop one does. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1241972 Title: Drag and drop from Dash to Desktop doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1241972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
** Branch linked: lp:~attente/gnome-settings-daemon/1218322 -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318030] [NEW] Cannot login-without-password when home folder in encrypted
*** This bug is a security vulnerability *** Public security bug reported: Users of which the home folder is encrypted using the CLI (unfortunately there is no GUI option for this, see https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1279766), and for which the 'login without password' is set, cannot login. Steps to reproduce: 1. Using an Administrator account, create a new user in System Settings User Accounts and set a password. 2. Open a shell and encrypt the newly created user folder by 'sudo ecryptfs-migrate-home -u username' 3. Login into the new account: successful 4. Logout and login into the Administrator account and select 'Login without password' for the newly created user. 5. Login into the new account: cannot login (the password field for this users now displays 'Log in' but trying to login results in a flickering screen and back to the login screen. Ubuntu 14.04 x64 (reproducable on two different machines) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1318030 Title: Cannot login-without-password when home folder in encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1318030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
en_GB speaker review of strings: + notify (self, _(An error occurred when encrypting your message and + not sent.)); This sentence no verb. Maybe ... and it was not sent? + notify (self, _(Your message was not sent because %s closed their + connection. Either close your private connection, or refresh it.), + context-username); What does that last sentence mean in Telepathy terms? If it means you should close this channel (i.e. close the Empathy window), perhaps Close this conversation and try again? (Or perhaps we should even auto-close the channel, but we're trying to get away from self-closing channels.) + err_msg = g_strdup (_(You transmitted an unreadable encrypted message.)); Thought bubble: no, I'm pretty sure I didn't :-) If this happens, it's presumably either Gabble's fault, or one of the user's other resources, not anything the user themselves typed. Internal error: transmitted an unreadable... instead, maybe? Same for You transmitted a malformed data message.. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #59)
Ideally, that distinctive message header should be a machine-readable
version of the message, so OTR-literate UIs (Empathy) can discard the
untranslated version from Gabble and display something translated. We've
always had a policy of putting UI strings and their translations in the UIs,
not the CMs.
The more I think about this, the more I think Gabble should not contain
translated strings. It's OK for it to contain strings in the C locale
(international English), but all translation should be taking place
somewhere that already needs to be translated - the UIs.
As a purely practical thing, Gabble does not have any of the translation
machinery, so those strings aren't going to be translated anyway.
Is the OtrlMessageEvent enum sufficiently stable that we can use it in
the D-Bus API directly? That would probably be the easiest way. The only
other information we need to put in the message header is:
- for OTRL_MSGEVENT_SETUP_ERROR: gcry_strerror (err)
(perhaps { otr-error: that string })
- for various codes: the username or account name, which the UI already
knows anyway
- for OTRL_MSGEVENT_RCVDMSG_UNENCRYPTED: the unencrypted message
(perhaps { otr-unencrypted-message: that string })
- for OTRL_MSGEVENT_RCVDMSG_GENERAL_ERR: the message
(perhaps { otr-error: that string })
--
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/296867
Title:
empathy needs to support OTR encryption
To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
+static void
+otr_handle_smp_event (void *opdata,
+ OtrlSMPEvent smp_event,
+ ConnContext *context,
+ unsigned short progress_percent,
+ gchar *question)
+{
+ DEBUG (UNIMPLEMENTED\n);
+}
Is this OK/allowed? Should we at least tell libotr no, I don't
implement SMP?
--
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/296867
Title:
empathy needs to support OTR encryption
To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #58)
Just doing the spec right now:
The extra DBus channel interface is implemented using GDBus
so it needs to be exported on a different bus name.
Ugh. Can we not do strange hacks like this, please? Either use the
extensions mechanism, or save it for 1.0.
I don't want to block on 1.0, and I don't want to write obsolete code
with tp-glib's codegen. So that's the necessary evil in the meantime.
+ interface name=im.telepathy.v1.Channel.Interface.OTR1
+ tp:causes-havoc=experimental
+ tp:added version=Gabble 0.UNRELEASED(Gabble-specific)/tp:added
If doing this in 0.x, please use o.fd.Channel.Interface.OTR1 and add it to
telepathy-spec (OK to go via extensions/ until we do the spec - tp-glib
dance, though).
I can change the iface name but it doesn't matter much. I would like to
avoid extensions/ nightmare though, I don't want to write code using
that in master and port it again in next.
In 1.0, certainly add it to the spec.
Yep, planned to include that in the tp1.0 spec, and consider it private
between gabble and empathy in the meantime.
+ A simple D-Bus API a
+ href=https://otr.cypherpunks.ca/;Off The Record/a.
... API for a...
+ pThe current trust level of this channel:
+ 0=TRUST_NOT_PRIVATE, 1=TRUST_UNVERIFIED, 2=TRUST_PRIVATE,
+ 3=TRUST_FINISHED/p
This deserves a tp:enum and documentation.
I didn't write it because gdbus-codegen does not use it. Opened
https://bugzilla.gnome.org/show_bug.cgi?id=729762 already. But I'll add
it in our spec in the meantime anyway, even if it's just for the html
version of our spec.
I assume the meanings go something like this:
TRUST_NOT_PRIVATE: not using OTR at all? (Can we also see this when using
OTR but something has gone wrong?)
(o.fd.Channel.I.Securable.Encrypted=FALSE,
o.fd.Channel.I.Securable.Verified=FALSE)
yes
TRUST_UNVERIFIED: the channel is encrypted, but you might be talking to a
man-in-the-middle instead of the peer you expected.
(o.fd.Channel.I.Securable.Encrypted=TRUE,
o.fd.Channel.I.Securable.Verified=FALSE)
yes
TRUST_PRIVATE: the channel is encrypted, and the user has indicated that the
peer's key fingerprint is trusted to belong to that peer.
(o.fd.Channel.I.Securable.Encrypted=TRUE,
o.fd.Channel.I.Securable.Verified=TRUE)
yes
TRUST_FINISHED: this channel is over, nothing more should be sent or
received on it.
(o.fd.Channel.I.Securable.Encrypted and o.fd.Channel.I.Securable.Verified
keep their previous values?)
I *think* (need to double check) that in that case you'll still be
sending encrypted messages but the other side won't be able to decrypt
them and will display a message The encrypted message received from %s
is unreadable, as you are not currently communicating privately..
What are the possible state transitions? I assume can only increase?
I think it can only increase unless the local user did something. Like
it can go from PRIVATE to UNVERIFIED if user types /otr untrust. It
currently cannot go back to NOT_PRIVATE because I don't support ending
the otr session, but could add a /otr end for that. pidgin can do
that.
+ type=(say) access=read
+ pUser's current fingerprint. The first element is a human readable
+ fingerprint that can be displayed to the user so he can communicate it
+ to the other end by other means so he can trust it. The 2nd element is
+ the fingerprint raw data./p
Are these literally the hex and binary versions of the same digest, or do
they have different information content? (Or is the string version some
OTR-specific thing that is easier to transcribe than hex?)
It is the same information, the string is utf8 (ascii even) to display,
the ay is hex form (20 bytes, not utf8). libotr has a function to go
hex-ascii but not ascii-hex and when TrustFingerprint is called I need
to tell otr which fingerprint is trusted by telling it the hex form.
That's why I send both over dbus.
+ property name=RemoteFingerprint
+ tp:name-for-bindings=Fingerprint
+ type=(say) access=read
+ tp:docstring xmlns=http://www.w3.org/1999/xhtml;
What value does this take when the channel is not using OTR? ('', [])?
yep.
When we're in the UNVERIFIED state, am I right in thinking that we are
cryptographically guaranteed to have the right fingerprint for who we're
talking to, but the thing that is unverified is that the fingerprint belongs
to the person we wanted to talk to? (i.e. if we're talking to a
man-in-the-middle, this would be the fingerprint of the man-in-the-middle's
key, right?)
That's how I understand it, yes.
Is it possible for this to change? (Presumably from ('', []) to non-empty,
at the same time that the trust changes to UNVERIFIED or PRIVATE?)
when TrustLevel is UNVERIFIED the RemoteFingerprint cannot be empty.
After this has become non-empty, can it change further? (I would hope
not.)
I think it can if the user ends the OTR session, but I didn't implement
that yet. I think if the other end stops the OTR session then
[Bug 296867]
After fixing the obvious things, it would also be good to get someone who understands the OTR protocol and/or libotr to review this (particularly the things I raised in Comment #59 and Comment #62). I don't think there's any such person among the main Telepathy developers, but perhaps one of the 49 people in Cc can give an informed review? -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
A brief glance at Empathy: + return _(The conversation is currently encrypted with + OTR but the remote contact has not been + authentified); There is no such word. I think you mean authenticated and/or identified. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #60) (In reply to comment #50) Could we also get a config option that turns this whole feature on/off? I ask because some industries (like the one where I work) require that all electronic communications related to the business get recorded and reviewed by compliance officers and made available to regulatory agencies upon request. I think we do need a connection parameter to control this. I think the possible sensible settings are: - never use OTR, behave exactly as though it was not implemented - start an OTR conversation if the local user or remote peer explicitly requests it - try to start OTR conversations automatically I think that would be most comprehensible as two booleans: something like enable-otr (default false initially, default true after a couple of releases) and enable-opportunistic-otr (not implemented in Xavier's patch, but someone could add it). The writer of Comment #50 would explicitly set enable-otr to false; the people getting excited about this bug would explicitly set enable-otr to true, and when implemented, probably also set enable-opportunistic-otr to true. It can be done later. ATM the policy is MANUAL and it's the right thing until we have an explicit option. I would consider this non-blocker future enhancement. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #61) I would really like im-channel to implement o.fd.Telepathy.Securable - as a starting point we can have the two booleans not be requestable, and just have them set by the OTR code calling a new gabble_im_channel_indicate_security (GABBLE_SECURABLE_ENCRYPTED|GABBLE_SECURABLE_VERIFIED) (or only one of those, or neither of those, as appropriate). I notice we never specified how those properties did change notification, because our only use of them so far was for SASL channels. Let's retcon them to they emit PropertiesChanged in the 0.x and 1.0 spec. I would consider this non-blocker future enhancement. Atm I'm not proposing the spec to be included in tp-spec, only private to gabbleempathy. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867] Re: empathy needs to support OTR encryption
** Bug watch added: GNOME Bug Tracker #729762 https://bugzilla.gnome.org/show_bug.cgi?id=729762 -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318030] Re: Cannot login-without-password when home folder in encrypted
This sounds like expected behaviour to me -- the login password is used to encrypt the filesystem key. Without a login password at login time, the files should be unavailable, and thus there's no home directory to contain anything of value for the user. There might be a better way to tell the user that a password is required for encrypted home directories though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1318030 Title: Cannot login-without-password when home folder in encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1318030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #68) It doesn't matter, if the message is in the form ?OTR:base64 then it puts new_content to whatever the original message was (html or not). OTR doesn't change anything if user wants to send html message as plaintext, empathy will escape when displaying them. Are you saying that in this message message body?OTR:123123123/body /message the recipient is expected to decrypt 123123123 and treat the result as plain text, but in this message message html xmlns='http://jabber.org/protocol/xhtml-im' body xmlns='http://www.w3.org/1999/xhtml' ?OTR:456456456 /body /html the recipient is expected to decrypt 456456456 and treat the result as HTML? Or what? There must be a rule you can use to determine whether the decrypted content is text/plain or text/html. Text that may contain HTML is not a well-formed concept - either the message lt; is a 4 character reply to remind me how you escape in HTML?, or it's a single U+003C LESS- THAN SIGN character. It can't be both. It is entirely possible that the rule is do whatever Pidgin does, which in practice probably means it's always treated as HTML - that's what my review comments assume. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #69) It can be done later. ATM the policy is MANUAL and it's the right thing until we have an explicit option. I would consider this non-blocker future enhancement. That's OK, but only if MANUAL specifically means do not initiate *or accept* OTR sessions without user input. (In reply to comment #70) I would consider this non-blocker future enhancement. Atm I'm not proposing the spec to be included in tp-spec, only private to gabbleempathy. I don't like private APIs. They have a nasty habit of becoming de facto public APIs as soon as you commit them (and we only recently managed to get rid of Renaming being a private API, despite it not having changed for 5 years). We have API versioning now, so if it's good enough to merge, it's good enough for the spec. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #62) Corner cases: What happens when we try to send a message and the channel is already TRUST_FINISHED? I think we should refuse, for the rest of the lifetime of that channel (until Close()), to avoid the security flaw where we send messages to a channel that just closed. Just tested, OTR refuse to send and a message is displayed. te...@test.collabora.co.uk: Your message was not sent because te...@test.collabora.co.uk closed their connection. Either close your private connection, or refresh it. What happens when we close a channel locally? I think the answer should be we terminate the OTR session, and start from an unsecured state next time - even if the channel is in fact going to respawn due to unacknowledged messages. This means the channel needs to reset its Encrypted flag, Verified flag and all OTR state when it respawns. We will still be able to tell the rescued messages were encrypted/verified because the header that I suggested adding will say so. I don't end the otr session yet (adding a patch now to do that). pending messages are already decrypted so user won't know if they were sent privately or not. Indeed adding the fingerprint in the message parts can be helpful. otoh I would consider this future enhancement, when a new chat window arrives if there is no message telling its private the user should just assume it's not. He can always start a new otr session and ask to repeat to be sure. IMO that's corner case so it's not that bad if user needs to ask repeating. What happens if I'm talking to b...@example.com/Laptop using OTR, and I receive a message from b...@example.com/Phone without OTR? I hope the answer is libotr deals with it and reports OTRL_MSGEVENT_RCVDMSG_UNENCRYPTED. Is it safe (as in, not a security vulnerability) to rely on that? I didn't test what happens with multiple resources, tbh. But if for any reason something unencrypted arrives, it raises OTRL_MSGEVENT_RCVDMSG_UNENCRYPTED. What happens when we receive a message and the channel is already TRUST_FINISHED? I hope the answer is libotr deals with it and reports OTRL_MSGEVENT_RCVDMSG_UNENCRYPTED. Is it safe (as in, not a security vulnerability) to rely on that? it does indeed raise OTRL_MSGEVENT_RCVDMSG_UNENCRYPTED. -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #68) I can change the iface name but it doesn't matter much. I would like to avoid extensions/ nightmare though, I don't want to write code using that in master and port it again in next. OK. I still would prefer to use o.fd.T for the 0.x version though. This deserves a tp:enum and documentation. I didn't write it because gdbus-codegen does not use it. Makes sense, but the documentation value is worth it. I *think* (need to double check) that in that case you'll still be sending encrypted messages but the other side won't be able to decrypt them and will display a message The encrypted message received from %s is unreadable, as you are not currently communicating privately.. It would make sense to get an OTR expert to confirm that how we're handling this is secure. What are the possible state transitions? I assume can only increase? I think it can only increase unless the local user did something. Like it can go from PRIVATE to UNVERIFIED if user types /otr untrust. Ah, that's a good point. Please document that transition (although it can only happen because the user did something odd - but that odd thing might make sense as an undo mechanism). I suppose this means that Securable.Verified can turn off as a result of an undo button, too... It currently cannot go back to NOT_PRIVATE because I don't support ending the otr session, but could add a /otr end for that. pidgin can do that. Please don't. In Pidgin, maybe that feature is OK, because typically only one UI handles a window (Pidgin's D-Bus API aside). In Telepathy, where more than one UI can be interested in a channel, that feature would be an unlikely security flaw: if I type the secret password is weasel and for some reason another process turns off OTR just as I hit Enter, that's Bad™. If the remote peer can turn off OTR, then that elevates that situation to a remotely exploitable security flaw, but AIUI the design of OTR doesn't allow that to happen. It is the same information, the string is utf8 (ascii even) to display, the ay is hex form (20 bytes, not utf8). All hex is UTF-8, because hex is a subset of ASCII, and ASCII is a subset of UTF-8... or do you mean binary? If the machine-readable fingerprint is like adc83b19e793491b1c6e (20 hex digits encoding 80 bits of entropy) that should be a string. If it's like \xad\xc8... (20 bytes encoding 160 bits of entropy, most likely a SHA-1) that should indeed be an 'ay'. As for the human-readable version, do I infer correctly that it is not just hex, but instead an OTR-specific encoding that is easier to transcribe or more dense or something? I think if the other end stops the OTR session then trustlevel goes to FINISHED but you'll still be sending encrypted messages and the other side (pidgin-otr) will say I received an encrypted messages, have no idea what it contains. Need to try that scenario to check. My understanding is that OTR publishes the temporary key at the end in order to provide deniability (although when I looked at the security properties of OTR and XTLS a few years ago I couldn't work out what extra deniability this actually provides...) and so continuing to encrypt messages with it would be Very Bad? But I could be wrong Could be useful, atm the logger still record the conversation. It's a good idea to add that in the message parts. Do you consider that merge blocker? probably users expects their OTR messages to not be stored on disk. otoh if they really care about security and they don't have encrypted HDD I don't know what they are thinking about... I would say putting in the header is a merge blocker, but implementing the preference in the Logger is not. I think using the target handle for this is OK semantically. yeah, probably, but it could be local-error messages, not something sent by the remote end. Hmm. Maybe it should be the self-handle... but we implement delivery reports as messages claiming to be from the peer, and this is fairly similar. You're right, yes. I guess the best is to have a signal on the OTR iface to transmit the OtrlMessageEvent enum. I'd put it in the message header - less OTR-specific API, better graceful degradation for non-OTR-literate clients. About translation, there is messages from otr_error_message() as well. Those are sent to the other end on error. We should probably not translate them at all, I don't want you to receive French messages from me. English is the international language, I guess. In a perfect world we could remember the language of each contact... Oh, I hadn't realised otr_error_message() goes to the peer. I think that deserves a comment. Yes, if we can't do decent l10n, we should say it's the C locale (international English). pidgin-otr says 0 for xmpp as well. OTR encryption can expand a bit the size of messages, but that's not new that user sending huge text could not be interoperable. I don't think gabble tries to prevent it anywhere.
[Bug 1299912] Re: Ubuntu 14.04 report as 13.10
Hello Aaron, or anyone else affected, Accepted gnome-control-center into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- control-center/1:3.6.3-0ubuntu56.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-control-center (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1299912 Title: Ubuntu 14.04 report as 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1299912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318088] [NEW] When Bluetooth is On, WiFi streaming is unusable
Public bug reported: Ubuntu 14.04. Hardware = Lenovo Thinkpad T-540-P With Bluetooth on, stream a video. Constant rebuffering and pauses make it unwatchable. With Bluetoon on, same stream plays well. ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1318088 Title: When Bluetooth is On, WiFi streaming is unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1318088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318090] [NEW] Bluetooth will not pair with Lenovo Bluetooth Keyboard
Public bug reported: Ubuntu 14.04 Lenovo Thinkpad T540P and Lenovo KT1255 bluetooth keyboard With bluetooth turned on, turn on keyboard and search for devices. Device is quickly found. Try to pair with it. A six digit random number is generated by the software with instructions to type it on the keyboard and press enter. Always fails to pair although the number is typed correctly. ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1318090 Title: Bluetooth will not pair with Lenovo Bluetooth Keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1318090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1201180] Re: powerbtn.sh conflicts with logind
Hi, this patch: if pidof systemd-logind /dev/null; then exit 0 fi together with this line: PMS=$PMS unity-settings-daemon are preventing me from using the power button to immediatly shutdown Ubuntu without any confirmation. In my case I want to be able to shut down an Ubuntu VM through acpi from virsh. With the current powerbtn.sh the following configuration lines this won't have much effect :-( gsettings set org.gnome.settings-daemon.plugins.power button-power 'shutdown' gsettings set org.gnome.SessionManager logout-prompt false gsettings set com.canonical.indicator.session suppress-logout-restart-shutdown true -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: powerbtn.sh conflicts with logind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1299912] Re: Ubuntu 14.04 report as 13.10
** Branch linked: lp:ubuntu/trusty-proposed/gnome-control-center -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1299912 Title: Ubuntu 14.04 report as 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1299912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1312349] Re: Microsoft bluetooth mobile keyboard 6000 cannot be used
** Changed in: gnome-bluetooth (Ubuntu Trusty) Status: New = Triaged ** Changed in: gnome-bluetooth (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: gnome-bluetooth (Ubuntu Trusty) Assignee: (unassigned) = Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1312349 Title: Microsoft bluetooth mobile keyboard 6000 cannot be used To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1312349/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1312349] Re: Microsoft bluetooth mobile keyboard 6000 cannot be used
I've uploaded this to the proposed queue for Trusty. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1312349 Title: Microsoft bluetooth mobile keyboard 6000 cannot be used To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1312349/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296867]
(In reply to comment #71) It currently cannot go back to NOT_PRIVATE because I don't support ending the otr session, but could add a /otr end for that. pidgin can do that. Please don't. In Pidgin, maybe that feature is OK, because typically only one UI handles a window (Pidgin's D-Bus API aside). In Telepathy, where more than one UI can be interested in a channel, that feature would be an unlikely security flaw: if I type the secret password is weasel and for some reason another process turns off OTR just as I hit Enter, that's Bad™. I actually added Stop method (/otr stop in empathy) because when the other side (pidgin) stop the OTR session we have to let user disconnect as well to continue in plaintext, otherwise he can't send messages anymore. Or do you think user should close the chat window and open it again in that case? Having that stop method is useful for testing as well :) IMO those methods must always be called on explicit user action, if you have bad apps running on your bus session, you lost already. If the remote peer can turn off OTR, then that elevates that situation to a remotely exploitable security flaw, but AIUI the design of OTR doesn't allow that to happen. Remote end can stop otr and you won't be able to send messages anymore until you stop/start it locally again. It is the same information, the string is utf8 (ascii even) to display, the ay is hex form (20 bytes, not utf8). All hex is UTF-8, because hex is a subset of ASCII, and ASCII is a subset of UTF-8... or do you mean binary? Sorry, mean binary, yes. 20 bytes of randomness. As for the human-readable version, do I infer correctly that it is not just hex, but instead an OTR-specific encoding that is easier to transcribe or more dense or something? It looks like 82AAB578 4FB98B0B AECD3BA4 6083CFE2 E152AD73 so that's actually simple hex with spacing. The formatting can easily be re- implemented client-side, but it's cheap enough to just provide it over dbus. I think if the other end stops the OTR session then trustlevel goes to FINISHED but you'll still be sending encrypted messages and the other side (pidgin-otr) will say I received an encrypted messages, have no idea what it contains. Need to try that scenario to check. My understanding is that OTR publishes the temporary key at the end in order to provide deniability (although when I looked at the security properties of OTR and XTLS a few years ago I couldn't work out what extra deniability this actually provides...) and so continuing to encrypt messages with it would be Very Bad? But I could be wrong. I was wrong indeed. When other end stops the session TrustLevel goes to FINISHED (added a patch to make that happen) and you are not able to send messages anymore, you get an error message back. I think it publish the private key indeed. pidgin-otr says 0 for xmpp as well. OTR encryption can expand a bit the size of messages, but that's not new that user sending huge text could not be interoperable. I don't think gabble tries to prevent it anywhere. Fair enough. I thought OTR had some sort of transparent chunking mechanism that might actually make OTR-over-XMPP more compatible with crap servers than just sending text over XMPP :-) OTR can fragment messages on protocols where it matters. We can indeed make it more interoperate thanks to that... If you have any sensible value in mind? Not blocker anyway. (In reply to comment #72) (In reply to comment #69) It can be done later. ATM the policy is MANUAL and it's the right thing until we have an explicit option. I would consider this non-blocker future enhancement. That's OK, but only if MANUAL specifically means do not initiate *or accept* OTR sessions without user input. It will always accept if remote starts the session. Do you think that's merge blocker? I'm a bit lazy to add a CM param, add UI in empathy, and goa/uoa doesn't make possible to add settings for facebook/google... I'm already tired just thinking about all that :( Simpler solution if you insist: make it per-channel and reject remotely initiated OTR before we call Start method. (In reply to comment #70) I would consider this non-blocker future enhancement. Atm I'm not proposing the spec to be included in tp-spec, only private to gabbleempathy. I don't like private APIs. They have a nasty habit of becoming de facto public APIs as soon as you commit them (and we only recently managed to get rid of Renaming being a private API, despite it not having changed for 5 years). We have API versioning now, so if it's good enough to merge, it's good enough for the spec. I would merge it in spec-next where we don't have that bus-name hack. Ok? -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications
[Bug 296867]
Voilà, added commits to fix most of your comments. What's missing: 1) handle html, I'm not sure to understand what you mean or why it is that important... Maybe you can make the changes that you want? 2) Find a solution if we don't want the other end to be able to initiate an OTR session without approving it first. 3) Fix string spelling. Maybe you can patch them yourself, as I'm not native? :) Anything else I missed in those long comments? -- 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/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246272] Re: Keyboard layout changing randomly
I have this problem on Trusty Tahr, but it doesn't only happen at login. I have three keyboard layouts installed - Danish, Swedish and US English (the actual keyboard layout is US english), and I often find that it happens while I'm in the middle of typing a sentence, suddenly writing ;, ', [ instead of Danish æ, ø, å or Swedish ö, ä, å, and special characters suddenly switching positions.. The indicator sometimes shows e.g. English layout wwhile the actual layout would be e.g. Swedish, but I have not been able to figure out if it is consistent or not, and I have not been able to figure out anything that could change the behaviour. I have had Left Shift+CapsLock mapped to cycle between layouts and thought that maybe I simpoly hit that combination by accident, but after I have changed the mapping to Ctrl+Alt+Space, it still happens, and THAT combination is not easily hit by accident. I have mostly been working in and therefore experiencing the problem in Firefox and GVim. -- 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/1246272 Title: Keyboard layout changing randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1312134] Re: Can't move nautilus window by dragging toolbar
*** This bug is a duplicate of bug 1304329 *** https://bugs.launchpad.net/bugs/1304329 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1312134 Title: Can't move nautilus window by dragging toolbar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1312134/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1304351] [NEW] firefox 200% CPU usage while idle/shutdown: mpegaudioparse0 and mpegaudioparse1 processes
You have been subscribed to a public bug:
Firefox regularly eats up 100% or 200% CPU usage while just gmail and
google calendar pages are opened.
Shutting down firefox does not really shut it down, only the window
disappears, the processes that eat CPU stay, so restarting firefox does
not work until I manually kill these processes.
While they show up as firefox in $ top, I now managed to activate the
thread view where these processes show up as mpegaudioparse0 and
mpegaudioparse1 processes.
Actually this might not be a bug in firefox but in one of the
extensions, e.g., flashplugin, but I am not sure. Firefox should kill
these harshly when exiting, so that restarting firefox is a possible
solution to CPU-eating buggy plugins and extensions.
I am using ubuntu 12.4.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 28.0+build2-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.11.0-19-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: 92HD90BXX Analog [92HD90BXX Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ps 2607 F pulseaudio
/dev/snd/controlC0: ps 2607 F pulseaudio
BuildID: 20140317233623
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xe676 irq 46'
Mixer name : 'IDT 92HD90BXX'
Components : 'HDA:111d76e7,10280494,00100102'
Controls : 28
Simple ctrls : 13
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xe508 irq 17'
Mixer name : 'Nvidia GPU 1c HDMI/DP'
Components : 'HDA:10de001c,10280494,00100100'
Controls : 21
Simple ctrls : 3
Channel: Unavailable
Date: Tue Apr 8 14:25:11 2014
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini
or extensions.sqlite)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
IpRoute:
default via 193.255.160.1 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
193.255.160.0/23 dev eth0 proto kernel scope link src 193.255.160.48
metric 1
Locales: extensions.sqlite corrupt or missing
MarkForUpload: True
MostRecentCrashID: bp-e838124b-7e27-4001-bba3-7c4442140319
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
Profiles: Profile0 (Default) - LastVersion=28.0/20140317233623 (In use)
RelatedPackageVersions:
google-talkplugin 5.2.4.0-1
icedtea-7-plugin 1.2.3-0ubuntu0.12.04.4
rhythmbox-mozilla 2.96-0ubuntu4.3
totem-mozilla 3.0.1-0ubuntu21.1
gnome-shell 3.4.1-0ubuntu2
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/18/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0692FT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
** Affects: totem (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug precise third-party-packages
--
firefox 200% CPU usage while idle/shutdown: mpegaudioparse0 and mpegaudioparse1
processes
https://bugs.launchpad.net/bugs/1304351
You received this bug notification because you are a member of Ubuntu Desktop
Bugs, which is subscribed to totem in Ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1304351] Re: firefox 200% CPU usage while idle/shutdown: mpegaudioparse0 and mpegaudioparse1 processes
Changing to totem-mozilla based on user's feedback. ** Package changed: firefox (Ubuntu) = totem (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1304351 Title: firefox 200% CPU usage while idle/shutdown: mpegaudioparse0 and mpegaudioparse1 processes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1304351/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1316383] Re: Vanilla gnome-control-center 3.8
** Changed in: gnome-control-center (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1316383 Title: Vanilla gnome-control-center 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1316383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1281155] Re: About this Computer shows 13.10 instead of 14.04
** No longer affects: gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1281155 Title: About this Computer shows 13.10 instead of 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1281155/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318112] Re: package python-gnomekeyring 2.32.0+dfsg-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/share/doc/python-gnomekeyring/examples/keyring-async.py' to install new versio
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-python-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1318112 Title: package python-gnomekeyring 2.32.0+dfsg-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/share/doc/python- gnomekeyring/examples/keyring-async.py' to install new version: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-python-desktop/+bug/1318112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318112] [NEW] package python-gnomekeyring 2.32.0+dfsg-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/share/doc/python-gnomekeyring/examples/keyring-async.py' to install new vers
Public bug reported: NI IDEA PERO EL O.S. XUBUNTU ME ESTA DANDO DEMASIADOS PROBLEMAS ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-gnomekeyring 2.32.0+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 AptOrdering: python-gnomekeyring: Install python-gnomekeyring: Configure Architecture: i386 Date: Fri May 9 17:21:53 2014 DpkgTerminalLog: Preparing to unpack .../python-gnomekeyring_2.32.0+dfsg-3_i386.deb ... Unpacking python-gnomekeyring (2.32.0+dfsg-3) over (2.32.0+dfsg-2ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/python-gnomekeyring_2.32.0+dfsg-3_i386.deb (--unpack): unable to move aside `./usr/share/doc/python-gnomekeyring/examples/keyring-async.py' to install new version: Operation not permitted DuplicateSignature: package:python-gnomekeyring:2.32.0+dfsg-2ubuntu1:unable to move aside `./usr/share/doc/python-gnomekeyring/examples/keyring-async.py' to install new version: Operation not permitted ErrorMessage: unable to move aside `./usr/share/doc/python-gnomekeyring/examples/keyring-async.py' to install new version: Operation not permitted InstallationDate: Installed on 2013-06-20 (323 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) SourcePackage: gnome-python-desktop Title: package python-gnomekeyring 2.32.0+dfsg-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/share/doc/python-gnomekeyring/examples/keyring-async.py' to install new version: Operation not permitted UpgradeStatus: Upgraded to trusty on 2014-04-25 (14 days ago) ** Affects: gnome-python-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-python-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1318112 Title: package python-gnomekeyring 2.32.0+dfsg-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/share/doc/python- gnomekeyring/examples/keyring-async.py' to install new version: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-python-desktop/+bug/1318112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1254350] Re: Shut down in unity-2d-panel does not work after upgrade
[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-session (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1254350 Title: Shut down in unity-2d-panel does not work after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1254350/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete = Expired -- 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/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287594] Re: Import fail with error message about photo library not being writeable
[Expired for shotwell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: shotwell (Ubuntu) Status: Incomplete = Expired -- 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/1287594 Title: Import fail with error message about photo library not being writeable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1287594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318112] Re: package python-gnomekeyring 2.32.0+dfsg-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/share/doc/python-gnomekeyring/examples/keyring-async.py' to install new versio
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: gnome-python-desktop (Ubuntu) Importance: Undecided = Low ** Changed in: gnome-python-desktop (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-python-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1318112 Title: package python-gnomekeyring 2.32.0+dfsg-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/share/doc/python- gnomekeyring/examples/keyring-async.py' to install new version: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-python-desktop/+bug/1318112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1246272] Re: Keyboard layout changing randomly
I can confirm comment #29. I'm on Trusty with a german keyboard layout (qwertz). After login all is ok. But sometime later the layout suddenly switches to some englisch layout (qwerty). The indicator still is showing german. Manual switching to US and then back to DE restores the german layout. -- 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/1246272 Title: Keyboard layout changing randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1263088] Re: search, next doesn't change pages when needed
** Changed in: evince Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1263088 Title: search, next doesn't change pages when needed To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1263088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
