[Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
This bug should be fixed with https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2003 I cannot reproduce the issue anymore when this change is applied on my system. Can someone initiate that this fix is backported into Ubuntu 21.04? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942622] Re: Gnome control center displays tab crashes if you unplug all monitors
The link is: https://errors.ubuntu.com/oops/47a66160-0f28-11ec-b051-fa163e6cac46 -- 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/1942622 Title: Gnome control center displays tab crashes if you unplug all monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942622] Re: Gnome control center displays tab crashes if you unplug all monitors
** Description changed: 1. Open gnome control center. 2. Open the "Displays" tab 3. Unplug ALL monitors 4. Plug a monitor back in. 5. Gnome Control center has crashed + + ps. + Also tested this on Ubuntu 21.04 using a live USB stick and interestingly Gnome control center does not crash but freezes instead and has to be force quit. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 19:25:36 2021 InstallationDate: Installed on 2021-08-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1942622 Title: Gnome control center displays tab crashes if you unplug all monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1942622] [NEW] Gnome control center displays tab crashes if you unplug all monitors
Public bug reported: 1. Open gnome control center. 2. Open the "Displays" tab 3. Unplug ALL monitors 4. Plug a monitor back in. 5. Gnome Control center has crashed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 19:25:36 2021 InstallationDate: Installed on 2021-08-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1942622 Title: Gnome control center displays tab crashes if you unplug all monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800650] [NEW] gedit highlights indexes of multidimensional arrays as comments in Perl mode
Public bug reported: In gedit's Perl highlight mode, variables of all kinds ($var, %hash, @array etc.) are highlighted in dark green. The same usually works for the last index of an array as well ($#array) but only if the array is one-dimensional. With multidimensional arrays, the proper syntax is more complicated: $#{$array[0]} should give the last index of the first element of an array of arrays. Here gedit however interprets the number sign (#) as the mark of a comment and highlights the rest of the line in blue. The expected behavior would be to highlight $#{$array[0]} in dark green like all other variables. See the attached screenshot. Description:Ubuntu 18.04.1 LTS Release:18.04 gedit: Installed: 3.28.1-1ubuntu1 Candidate: 3.28.1-1ubuntu1 Version table: *** 3.28.1-1ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 12:27:38 2018 InstallationDate: Installed on 2017-02-13 (624 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to bionic on 2018-05-31 (151 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot gedit perl multi-array index.png" https://bugs.launchpad.net/bugs/1800650/+attachment/5207156/+files/Screenshot%20gedit%20perl%20multi-array%20index.png -- 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/1800650 Title: gedit highlights indexes of multidimensional arrays as comments in Perl mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1800650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1781634] [NEW] SIGFPE on GtkMessageDialog
Public bug reported: Trying to open a gtk2 message box crashes the hosting program. Easiest way I've been able to reproduce this is to run gtk-demo from the gtk2.0-examples package, and try to spawn a message dialog from the Dialog and Message Boxes demo. Nothing is printed to stdout or stderr. I'm running Ubuntu MATE 18.04, and the libgtk2.0-0 package version is 2.42.32-1ubuntu1. I do not recall this happening on the other bionic system running in the office, so it could be related to UI scaling for my HiDPI displays. That's just a hunch, though. ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New -- 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/1781634 Title: SIGFPE on GtkMessageDialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1781634/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1781262] Re: manually closing notification popups causes error messages in journal
Add error messages in plain text since additional line breaks were added by launchpad in the original message. ** Attachment added: "Error messages in plain text from journal (hostname redacted)" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781262/+attachment/5162516/+files/2018-07-11-error_msg.txt ** Description changed: closing a notification popup by clicking on the [x] in the notification - popup produces following log meassges: + popup produces error messages in the journal. - Jul 11 19:11:40 hostname gnome-shell[2920]: Object St.Button (0x55ae4b19da10), has been already finalized. Impossible to set any property to it. - Jul 11 19:11:40 hostname gnome-shell[2920]: Object St.Button (0x55ae4b19da10), has been already finalized. Impossible to set any property to it. - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: == Stack trace for context 0x55ae4569e340 == - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #0 0x55ae45a49ab0 i resource:///org/gnome/shell/ui/messageList.js:504 (0x7f78902b4de0 @ 83) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #1 0x7ffcdae43760 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f78903b5de0 @ 71) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #2 0x7ffcdae43830 b self-hosted:917 (0x7f78903f12b8 @ 394) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #3 0x55ae45a49a20 i resource:///org/gnome/shell/ui/messageTray.js:1461 (0x7f78902a2a28 @ 121) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #4 0x7ffcdae457b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f78903b5de0 @ 71) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #5 0x55ae45a49978 i resource:///org/gnome/shell/ui/messageTray.js:1448 (0x7f78902a29a0 @ 406) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #6 0x7ffcdae46390 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f78903b5de0 @ 71) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #7 0x55ae45a498c0 i resource:///org/gnome/shell/ui/messageTray.js:1249 (0x7f78902a2340 @ 729) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #8 0x7ffcdae46f70 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f78903b5de0 @ 71) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #9 0x55ae45a49828 i resource:///org/gnome/shell/ui/messageTray.js:1067 (0x7f78902a0e68 @ 124) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #10 0x7ffcdae47b60 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f78903b5de0 @ 71) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #11 0x7ffcdae47c30 b self-hosted:917 (0x7f78903f12b8 @ 394) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #12 0x7ffcdae47d20 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f78903d3230 @ 386) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #13 0x55ae45a49798 i resource:///org/gnome/shell/ui/messageTray.js:487 (0x7f789029dc48 @ 50) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #14 0x7ffcdae48980 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f78903b5de0 @ 71) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #15 0x55ae45a49718 i resource:///org/gnome/shell/ui/calendar.js:775 (0x7f78902aad58 @ 44) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #16 0x7ffcdae49c90 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f78903d3230 @ 386) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #17 0x55ae45a49690 i resource:///org/gnome/shell/ui/messageList.js:372 (0x7f78902b4670 @ 22) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #18 0x7ffcdae4a8e0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f78903b5de0 @ 71) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #19 0x55ae45a49618 i resource:///org/gnome/shell/ui/calendar.js:779 (0x7f78902aade0 @ 29) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #20 0x7ffcdae4bbf0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f78903d3230 @ 386) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #21 0x55ae45a49588 i resource:///org/gnome/shell/ui/messageTray.js:487 (0x7f789029dc48 @ 50) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #22 0x7ffcdae4c850 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f78903b5de0 @ 71) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #23 0x55ae45a49508 i resource:///org/gnome/shell/ui/calendar.js:775 (0x7f78902aad58 @ 44) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #24 0x7ffcdae4db60 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f78903d3230 @ 386) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #25 0x55ae45a49480 i resource:///org/gnome/shell/ui/messageList.js:372 (0x7f78902b4670 @ 22) - Jul 11 19:11:40 hostname org.gnome.Shell.desktop[2920]: #26 0x7ffcdae4e7c0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f78903b5de0 @ 71) - Jul 11 19:11:40
[Bug 1781262] [NEW] manually closing notification popups causes error messages in journal
Public bug reported: closing a notification popup by clicking on the [x] in the notification popup produces error messages in the journal. This behavior can be reproduced reliably by calling for example "notify-send test" in a virtual terminal and closing the notification popup manually by clicking the [X] button in the notification popup. EDIT: log messages were removed from the report and attached as txt file to preserve line breaks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 19:19:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-06-26 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1781262 Title: manually closing notification popups causes error messages in journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771880] Re: Seahorse unable to import certificates in Ubuntu 18.04
Can confirm the problem. I really appreciate a fix, as email encryption by s/MIME does not work in evolution since I cannot import certificates. Thanks a lot! Markus -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import certificates in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1771880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774744] [NEW] Impossible to select files with long names in order
Public bug reported: Selecting files with long filenames using Shift and arrow keys causes nautilus in icon view not to advance sequentially or not to advance at all. Here's a test case: 1) Create a new folder and create empty files with long names in it using the command: for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40; do touch "abcdef ghijklmn opqrstuvwxyz ABCDEF GHIJKLMN OPQRSTUVWXYZ$i.txt"; done 2) Open the folder in nautilus, hold Shift down and start selecting files by pressing the right arrow key. Everything goes fine up to the end of the first row. However, when you reach the first file on the second row and press the arrow key again (still holding Shift down), the selection jumps back to the second file of the first row. If you keep on pressing the arrow key, it will repeat the process over and over. So by pressing the right arrow key, you can never reach the end of the folder. As a user, I would expect nautilus to progress sequentially to the second file of the second row and so on up to the end of the folder. In the example, I used default font settings and 50 % zoom. Description:Ubuntu 18.04 LTS Release:18.04 nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 1 23:06:09 2018 GsettingsChanges: b'org.gnome.nautilus.preferences' b'search-view' b"'icon-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'203' b'org.gnome.nautilus.window-state' b'geometry' b"'888x580+117+77'" InstallationDate: Installed on 2017-02-13 (473 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-05-31 (1 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1774744 Title: Impossible to select files with long names in order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods
@Gunnar re: #6 `Alt + Shift` was set by default with the (in my case) upgrade to 18.04. I never set this alternative shortcut myself and there is no way to change it without additional tools. In fact, the entire bug report is about this alternative shortcut being an issue with the current default value. -- 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/1762952 Title: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods
@Gunnar re: #6 I can confirm that this particular alternative shortcut can be deactivated with `gnome-tweaks` by unchecking the checkbox under `Keyboard & Mouse -> Additional Layout Options -> Switching to another layout -> Alt + Shift`. -- 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/1762952 Title: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods
There is another aspect to this issue: It also becomes impossible to execute application-level keyboard shortcuts that contain Alt + Shift, such as `Alt + Shift + R`. What is actually executed: Alt + R and Input method is switched What should have executes: Alt + Shift + R and Input method is unchanged It really needs to be possible to remove or change the `Alternative switch to next source` hotkey `Alt + Shift`. -- 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/1762952 Title: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods
** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1762952 Title: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods
** Attachment added: "Screenshot Keyboard" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762952/+attachment/5110361/+files/Screenshot%20from%202018-04-11%2009-55-09.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] [NEW] Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods
Public bug reported: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot Input Source Options" https://bugs.launchpad.net/bugs/1762952/+attachment/5110359/+files/Screenshot%20from%202018-04-11%2009-49-15.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Switching backwards between applications with Alt + Shift + Tab not possible when using multiple keyboard input methods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727301] [NEW] 229-4ubuntu20 added ARP option breaks existing bonding interfaces
Public bug reported: this breaks existing configurations with bonding on upgrading from 229-4ubuntu19 to 229-4ubuntu20 on xenial as bond interfaces are now by default configured without ARP. Hence you suddenly lose network connectivity on upgrade. Very bad for a SRU. Plus adding "ARP=yes" to the Link section of a .network file does not work. Before this update, bond interfaces (specifically 802.3ad) were defaulting to ARP enabled. After the upgrade, they are created with NOARP set on the link. pre-upgrade: eth0:eth1: bond0: post-upgrade: eth0: eth1: bond0: Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: regression-updates ** Description changed: + this breaks existing configurations with bonding on upgrading from + 229-4ubuntu19 to 229-4ubuntu20 on xenial - this breaks existing configurations with bonding on upgrading from 229-4ubuntu19 to 229-4ubuntu20 - as bond interfaces are now by default configured without ARP. Hence you suddenly lose network connectivity on upgrade. Very bad for a SRU. + as bond interfaces are now by default configured without ARP. Hence you + suddenly lose network connectivity on upgrade. Very bad for a SRU. Plus adding "ARP=yes" to the Link section of a .network file does not work. Before this update, bond interfaces (specifically 802.3ad) were defaulting to ARP enabled. After the upgrade, they are created with NOARP set on the link. pre-upgrade: eth0: eth1: bond0: post-upgrade: eth0: eth1: bond0: Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727301 Title: 229-4ubuntu20 added ARP option breaks existing bonding interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725458] [NEW] System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful
Public bug reported: After not touching my notebook since 30th September (where I did the dist-upgrade to artful and installed all available updates), I did all available updates today (20th October) and the system didn't boot after that. The last message I see is "Reached target Bluetooth". Before that, there are several failed services. GDM doesn't come up. After logging in on tty2, I saw that the root partition was mounted read-only. Inspecting the messages of e.g. systemd-resolved shows that it didn't start because of the read-only filesystem. After remounting it fw, I was able to restart the daemons and could also start GDM and login fine. My fstab shows: UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4errors =remount-ro 0 1 The UUID is correct as "mount / -o remount,rw" works fine. Booting with the previous kernel doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 20 21:46:36 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-26 (451 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago) dmi.bios.date: 09/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81A1 dmi.board.vendor: HP dmi.board.version: 33.76 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible dmi.sys.vendor: HP ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1725458 Title: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
That finally solved it for me, thank you @Eberhard and @all for looking into this and sharing your insights! A few notes: * in addition, I manually deleted file /etc/X11/Xsession.d/20dbus_xdg- runtime which comes with package dbus-user-session (and is actually the only file of the package) but was not removed on uninstall (Idk whether this step is always neccessary) * logout/login was not sufficient to see this solved. Full reboot was required. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685141] Re: System freezes after locking screen
It seems, using the proprietary NVIDIA-driver works for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1685141 Title: System freezes after locking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1685141/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685141] Re: System freezes after locking screen
Meanwhile, this bug even occurs without locking the screen. After two weeks and approx. 30 occurrences only on one of my machines, I consider this bug critical. I don't even know, if the screensaver-package is the right package for reporting. Seems to me as a general/deeper problem, because it influences the whole system's stability. Compared to 16.10, version 17.04 is a big step back in puncto stability. I probably have to switch back to the old reliable version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1685141 Title: System freezes after locking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1685141/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685141] Re: System freezes after locking screen
** Attachment added: "syslog2.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1685141/+attachment/4866358/+files/syslog2.txt ** Description changed: When locking the screen or whenever the screensaver starts automatically, I cannot log in again, but my system completely freezes and I have to restart the computer. In most cases I was able to do the restart by pressing Alt-REISUB, in some cases however I had to do a hard reset. This is a new bug in zesty (Ubuntu 17.04). In the previous version everything worked fine. I tested both the upgrade and a fresh new installation on the same computer. Package is gnome-screensaver version 3.6.1-7ubuntu5. I attach an excerpt from my syslog. Hope this might help to find the bug. I installed zesty on another computer (laptop) as well and there the bug did not appear. So I assume it has something to do with the installed graphics card or graphics driver. Installed graphics card in this case is: NVIDIA Corporation GF108 [GeForce GT 630] (rev a1). + + Update: After a few days the bug now appears on the second computer as + well. However, I could unlock the screen and continue working, until + suddenly (an hour later or so) the whole system froze. I add the kernel- + nullpointer-dereference syslog of this event (syslog2.txt) to the + attachments for this bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1685141 Title: System freezes after locking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1685141/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685141] [NEW] System freezes after locking screen
Public bug reported: When locking the screen or whenever the screensaver starts automatically, I cannot log in again, but my system completely freezes and I have to restart the computer. In most cases I was able to do the restart by pressing Alt-REISUB, in some cases however I had to do a hard reset. This is a new bug in zesty (Ubuntu 17.04). In the previous version everything worked fine. I tested both the upgrade and a fresh new installation on the same computer. Package is gnome-screensaver version 3.6.1-7ubuntu5. I attach an excerpt from my syslog. Hope this might help to find the bug. I installed zesty on another computer (laptop) as well and there the bug did not appear. So I assume it has something to do with the installed graphics card or graphics driver. Installed graphics card in this case is: NVIDIA Corporation GF108 [GeForce GT 630] (rev a1). ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1685141/+attachment/4865973/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1685141 Title: System freezes after locking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1685141/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1678296] [NEW] gnome-calendar crashed with SIGSEGV
Public bug reported: Description:Ubuntu Zesty Zapus (development branch) Release:17.04 gnome-calendar: Installiert: 3.24.0-0ubuntu1 Installationskandidat: 3.24.0-0ubuntu1 Versionstabelle: *** 3.24.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status As a wasn't using the calendar right now but haven't closed it yet, I expected nothing to happen, but a window saying the Calendar has detected a bug appeared ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: gnome-calendar 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Mar 31 21:17:41 2017 Disassembly: No registers. ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2017-03-18 (12 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=de_DE PATH=(custom, user) LANG=de_DE.UTF-8 Registers: The program has no registers now. SegvAnalysis: Failure: invalid literal for int() with base 16: 'program' Signal: 11 SourcePackage: gnome-calendar Stacktrace: No stack. StacktraceTop: ThreadStacktrace: Title: gnome-calendar crashed with SIGSEGV UpgradeStatus: Upgraded to zesty on 2017-03-31 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace zesty ** Information type changed from Private to Private Security ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1678296 Title: gnome-calendar crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1678296/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1241101]
*** Bug 465485 has been marked as a duplicate of this bug. *** -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1241101]
There's no point in delaying a workaround in SWT for this crash. Attachment 253846 still reproduces on Ubuntu 14.04. AFAICS, this is the place where the fix in Ubuntu could eventually show up: http://bazaar.launchpad.net/~indicator-applet-developers/unity-gtk-module/trunk.14.04/view/head:/lib/unity-gtk-action-group.c#L848 Released a simple workaround to master: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=534ed490b51e7b64f0afdbd1595dc7098177d066 -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1241101]
*** Bug 462002 has been marked as a duplicate of this bug. *** -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
Created attachment 120758 Fix printf for unsigned int In pdfsig.cc the NetBeans IDE gave warning: Mismatching the argument type "unsigned int" and conversion specifier "d" The attached patch changes from %d to %u in the printf. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Markus Wernig from comment #104) > I think the correct statement to issue in this case would be that a part > ("revision") of the PDF has been signed and to show the validation result > for that revision, ideally giving the user a chance to view only the signed > part. > > This might even be indispensable when there are multiple signatures applied > to the document. So one idea could be to also use the first offset when checking the signature and in case it is not zero instead of return the status as SIGNATURE_VALID say something like "SIGNATURE_PARTLY_VALID". The pdfsig tool already implements support for multiple signatures/"revisions" but it seems the API does not expose the ByteRange for which the signature covers nor provides an other way to obtain that revision of the document (?). -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
Created attachment 120758 Fix printf for unsigned int In pdfsig.cc the NetBeans IDE gave warning: Mismatching the argument type "unsigned int" and conversion specifier "d" The attached patch changes from %d to %u in the printf. -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
Created attachment 120760 Considering offset 0 and signature only covering part of PDF Note that this patch has not been tested with a non-zero first offset document. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Markus Wernig from comment #104) > I think the correct statement to issue in this case would be that a part > ("revision") of the PDF has been signed and to show the validation result > for that revision, ideally giving the user a chance to view only the signed > part. > > This might even be indispensable when there are multiple signatures applied > to the document. So one idea could be to also use the first offset when checking the signature and in case it is not zero instead of return the status as SIGNATURE_VALID say something like "SIGNATURE_PARTLY_VALID". The pdfsig tool already implements support for multiple signatures/"revisions" but it seems the API does not expose the ByteRange for which the signature covers nor provides an other way to obtain that revision of the document (?). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
Created attachment 120760 Considering offset 0 and signature only covering part of PDF Note that this patch has not been tested with a non-zero first offset document. -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Albert Astals Cid from comment #102) > So we're stuck on "need to use the offset" part, right? > > Could someone try to do make the code use it even if we don't have any pdf > that needs it? I am not sure if it is good to apply the robustness principle on security functions. In those cases it might be better to be defensive and reject signatures not following the recommendation. In this case if the ByteRange does not cover the whole document there could be parts of the document that can be modified without invalidating the signature. Would it then be good to tell the user that the signature has been validated and the document is not modified even though in fact there are parts of the document for which we don't know? -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Albert Astals Cid from comment #102) > So we're stuck on "need to use the offset" part, right? > > Could someone try to do make the code use it even if we don't have any pdf > that needs it? I am not sure if it is good to apply the robustness principle on security functions. In those cases it might be better to be defensive and reject signatures not following the recommendation. In this case if the ByteRange does not cover the whole document there could be parts of the document that can be modified without invalidating the signature. Would it then be good to tell the user that the signature has been validated and the document is not modified even though in fact there are parts of the document for which we don't know? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1520211] Re: EOG tries to open an image, but crashes: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed.
I'm running Ubuntu 14.04 LTS. markus@W530:~/Disk/WorkDocuments/Roche/2015-Spectrum-POC/Pictures$ eog --version GNOME Image Viewer 3.10.2 This problem is not new. Has been bugging me for more than a year. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1520211 Title: EOG tries to open an image, but crashes: eog: ../../../../src/cairo- xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1520211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1520211] Re: EOG tries to open an image, but crashes: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed.
EOG crashes on over 50% of the pictures taken with my Samsung Galaxy S4 phone. markus@W530:~/Pictures$ eog 20151202_091338.jpg eog: /build/buildd/cairo-1.13.0~20140204/src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed. Aborted (core dumped) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1520211 Title: EOG tries to open an image, but crashes: eog: ../../../../src/cairo- xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1520211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1520211] Re: EOG tries to open an image, but crashes: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed.
After some more research I found a solution: Add kernel.shmmax = 536870912 to /etc/sysctl.conf and apply the setting with sysctl -p -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1520211 Title: EOG tries to open an image, but crashes: eog: ../../../../src/cairo- xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1520211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Adrian Johnson from comment #91) > What is the output of "pkg-config --cflags nss"? [user@dev-21 poppler]$ pkg-config --cflags nss -I/usr/include/nss3 -I/usr/include/nspr4 -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Adrian Johnson from comment #91) > What is the output of "pkg-config --cflags nss"? [user@dev-21 poppler]$ pkg-config --cflags nss -I/usr/include/nss3 -I/usr/include/nspr4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
Created attachment 119174 Handle SEC_ERROR_UNTRUSTED_ISSUER When verifying a PDF signed by a certificate issued by a CA not in the trust store I would expect to get an error "Certificate isn't Trusted" however currently the error message actually is the more generic "Unknown issue with Certificate or corrupted data". I tested with http://wwwpriv.primekey.se/~markus/pdfsigner/test-pdfs /signserver-res-test-pdf/sample-signed.pdf: [user@dev-21 utils]$ ./pdfsigverify ~/Downloads/signserver-res-test-pdf/sample-signed.pdf Digital Signature Info of: /home/user/Downloads/signserver-res-test-pdf/sample-signed.pdf Signature #1: - Signer Certificate Common Name: Signer 2 - Signing Time: Nov 23 2011 17:09:42 - Signature Validation: Signature is Valid. - Certificate Validation: Unknown issue with Certificate or corrupted data. Then after adding http://wwwpriv.primekey.se/~markus/pdfsigner/test-pki /signserver-res-test-dss10/DSSRootCA10.cacert.pem as trusted in Firefox: [user@dev-21 utils]$ ./pdfsigverify ~/Downloads/signserver-res-test-pdf/sample-signed.pdf Digital Signature Info of: /home/user/Downloads/signserver-res-test-pdf/sample-signed.pdf Signature #1: - Signer Certificate Common Name: Signer 2 - Signing Time: Nov 23 2011 17:09:42 - Signature Validation: Signature is Valid. - Certificate Validation: Certificate is Trusted. The attached patch adds the NSS error code for untrusted issuer so the error will be "Certificate isn't trusted". -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
Created attachment 119174 Handle SEC_ERROR_UNTRUSTED_ISSUER When verifying a PDF signed by a certificate issued by a CA not in the trust store I would expect to get an error "Certificate isn't Trusted" however currently the error message actually is the more generic "Unknown issue with Certificate or corrupted data". I tested with http://wwwpriv.primekey.se/~markus/pdfsigner/test-pdfs /signserver-res-test-pdf/sample-signed.pdf: [user@dev-21 utils]$ ./pdfsigverify ~/Downloads/signserver-res-test-pdf/sample-signed.pdf Digital Signature Info of: /home/user/Downloads/signserver-res-test-pdf/sample-signed.pdf Signature #1: - Signer Certificate Common Name: Signer 2 - Signing Time: Nov 23 2011 17:09:42 - Signature Validation: Signature is Valid. - Certificate Validation: Unknown issue with Certificate or corrupted data. Then after adding http://wwwpriv.primekey.se/~markus/pdfsigner/test-pki /signserver-res-test-dss10/DSSRootCA10.cacert.pem as trusted in Firefox: [user@dev-21 utils]$ ./pdfsigverify ~/Downloads/signserver-res-test-pdf/sample-signed.pdf Digital Signature Info of: /home/user/Downloads/signserver-res-test-pdf/sample-signed.pdf Signature #1: - Signer Certificate Common Name: Signer 2 - Signing Time: Nov 23 2011 17:09:42 - Signature Validation: Signature is Valid. - Certificate Validation: Certificate is Trusted. The attached patch adds the NSS error code for untrusted issuer so the error will be "Certificate isn't trusted". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
I'm trying to build the branch (on Fedora 21) but obviously I am missing some dependency or not having the right versions etc. Anyone having an idea? Build output: --- [user@dev-21 poppler]$ sudo yum install nspr-devel Loaded plugins: langpacks, post-transaction-actions, yum-qubes-hooks Package nspr-devel-4.10.8-1.fc21.x86_64 already installed and latest version Nothing to do [user@dev-21 poppler]$ make make all-recursive make[1]: Entering directory '/home/user/VersionControlled/poppler' Making all in goo make[2]: Entering directory '/home/user/VersionControlled/poppler/goo' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/user/VersionControlled/poppler/goo' Making all in fofi make[2]: Entering directory '/home/user/VersionControlled/poppler/fofi' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/user/VersionControlled/poppler/fofi' Making all in splash make[2]: Entering directory '/home/user/VersionControlled/poppler/splash' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/user/VersionControlled/poppler/splash' Making all in poppler make[2]: Entering directory '/home/user/VersionControlled/poppler/poppler' make all-am make[3]: Entering directory '/home/user/VersionControlled/poppler/poppler' CXX libpoppler_la-SignatureHandler.lo In file included from SignatureHandler.cc:15:0: SignatureHandler.h:20:24: fatal error: nspr/prprf.h: No such file or directory #include ^ compilation terminated. Makefile:1084: recipe for target 'libpoppler_la-SignatureHandler.lo' failed make[3]: *** [libpoppler_la-SignatureHandler.lo] Error 1 make[3]: Leaving directory '/home/user/VersionControlled/poppler/poppler' Makefile:840: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/home/user/VersionControlled/poppler/poppler' Makefile:642: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/user/VersionControlled/poppler' Makefile:524: recipe for target 'all' failed make: *** [all] Error 2 --- -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Markus Kilås from comment #87) > I'm trying to build the branch (on Fedora 21) but obviously I am missing > some dependency or not having the right versions etc. Anyone having an idea? > > Build output: > --- > [user@dev-21 poppler]$ sudo yum install nspr-devel > Loaded plugins: langpacks, post-transaction-actions, yum-qubes-hooks > Package nspr-devel-4.10.8-1.fc21.x86_64 already installed and latest version > Nothing to do > [user@dev-21 poppler]$ make > make all-recursive > make[1]: Entering directory '/home/user/VersionControlled/poppler' > Making all in goo > make[2]: Entering directory '/home/user/VersionControlled/poppler/goo' > make[2]: Nothing to be done for 'all'. > make[2]: Leaving directory '/home/user/VersionControlled/poppler/goo' > Making all in fofi > make[2]: Entering directory '/home/user/VersionControlled/poppler/fofi' > make[2]: Nothing to be done for 'all'. > make[2]: Leaving directory '/home/user/VersionControlled/poppler/fofi' > Making all in splash > make[2]: Entering directory '/home/user/VersionControlled/poppler/splash' > make[2]: Nothing to be done for 'all'. > make[2]: Leaving directory '/home/user/VersionControlled/poppler/splash' > Making all in poppler > make[2]: Entering directory '/home/user/VersionControlled/poppler/poppler' > make all-am > make[3]: Entering directory '/home/user/VersionControlled/poppler/poppler' > CXX libpoppler_la-SignatureHandler.lo > In file included from SignatureHandler.cc:15:0: > SignatureHandler.h:20:24: fatal error: nspr/prprf.h: No such file or > directory > #include > ^ > compilation terminated. > Makefile:1084: recipe for target 'libpoppler_la-SignatureHandler.lo' failed > make[3]: *** [libpoppler_la-SignatureHandler.lo] Error 1 > make[3]: Leaving directory '/home/user/VersionControlled/poppler/poppler' > Makefile:840: recipe for target 'all' failed > make[2]: *** [all] Error 2 > make[2]: Leaving directory '/home/user/VersionControlled/poppler/poppler' > Makefile:642: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/home/user/VersionControlled/poppler' > Makefile:524: recipe for target 'all' failed > make: *** [all] Error 2 > --- I found a workaround for my build issue by creating symlinks: /usr/include/nspr -> /usr/include/nspr4 /usr/inclyde/nss -> /usr/include/nss3 -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
I'm trying to build the branch (on Fedora 21) but obviously I am missing some dependency or not having the right versions etc. Anyone having an idea? Build output: --- [user@dev-21 poppler]$ sudo yum install nspr-devel Loaded plugins: langpacks, post-transaction-actions, yum-qubes-hooks Package nspr-devel-4.10.8-1.fc21.x86_64 already installed and latest version Nothing to do [user@dev-21 poppler]$ make make all-recursive make[1]: Entering directory '/home/user/VersionControlled/poppler' Making all in goo make[2]: Entering directory '/home/user/VersionControlled/poppler/goo' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/user/VersionControlled/poppler/goo' Making all in fofi make[2]: Entering directory '/home/user/VersionControlled/poppler/fofi' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/user/VersionControlled/poppler/fofi' Making all in splash make[2]: Entering directory '/home/user/VersionControlled/poppler/splash' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/user/VersionControlled/poppler/splash' Making all in poppler make[2]: Entering directory '/home/user/VersionControlled/poppler/poppler' make all-am make[3]: Entering directory '/home/user/VersionControlled/poppler/poppler' CXX libpoppler_la-SignatureHandler.lo In file included from SignatureHandler.cc:15:0: SignatureHandler.h:20:24: fatal error: nspr/prprf.h: No such file or directory #include ^ compilation terminated. Makefile:1084: recipe for target 'libpoppler_la-SignatureHandler.lo' failed make[3]: *** [libpoppler_la-SignatureHandler.lo] Error 1 make[3]: Leaving directory '/home/user/VersionControlled/poppler/poppler' Makefile:840: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/home/user/VersionControlled/poppler/poppler' Makefile:642: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/user/VersionControlled/poppler' Makefile:524: recipe for target 'all' failed make: *** [all] Error 2 --- -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to Adrian Johnson from comment #89) > (In reply to Markus Kilås from comment #88) > > I found a workaround for my build issue by creating symlinks: > > /usr/include/nspr -> /usr/include/nspr4 > > /usr/inclyde/nss -> /usr/include/nss3 > > Are you using configure or cmake? The nss pkgconfig file should contain the > correct include path. After checking out the branch I read INSTALL but did not find any ./configure so I run ./autogen.sh. It first failed for many different reasons which eventually got resolved by installing missing dependencies. After that I run the now generated ./configure and then make. -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Markus Kilås from comment #87) > I'm trying to build the branch (on Fedora 21) but obviously I am missing > some dependency or not having the right versions etc. Anyone having an idea? > > Build output: > --- > [user@dev-21 poppler]$ sudo yum install nspr-devel > Loaded plugins: langpacks, post-transaction-actions, yum-qubes-hooks > Package nspr-devel-4.10.8-1.fc21.x86_64 already installed and latest version > Nothing to do > [user@dev-21 poppler]$ make > make all-recursive > make[1]: Entering directory '/home/user/VersionControlled/poppler' > Making all in goo > make[2]: Entering directory '/home/user/VersionControlled/poppler/goo' > make[2]: Nothing to be done for 'all'. > make[2]: Leaving directory '/home/user/VersionControlled/poppler/goo' > Making all in fofi > make[2]: Entering directory '/home/user/VersionControlled/poppler/fofi' > make[2]: Nothing to be done for 'all'. > make[2]: Leaving directory '/home/user/VersionControlled/poppler/fofi' > Making all in splash > make[2]: Entering directory '/home/user/VersionControlled/poppler/splash' > make[2]: Nothing to be done for 'all'. > make[2]: Leaving directory '/home/user/VersionControlled/poppler/splash' > Making all in poppler > make[2]: Entering directory '/home/user/VersionControlled/poppler/poppler' > make all-am > make[3]: Entering directory '/home/user/VersionControlled/poppler/poppler' > CXX libpoppler_la-SignatureHandler.lo > In file included from SignatureHandler.cc:15:0: > SignatureHandler.h:20:24: fatal error: nspr/prprf.h: No such file or > directory > #include > ^ > compilation terminated. > Makefile:1084: recipe for target 'libpoppler_la-SignatureHandler.lo' failed > make[3]: *** [libpoppler_la-SignatureHandler.lo] Error 1 > make[3]: Leaving directory '/home/user/VersionControlled/poppler/poppler' > Makefile:840: recipe for target 'all' failed > make[2]: *** [all] Error 2 > make[2]: Leaving directory '/home/user/VersionControlled/poppler/poppler' > Makefile:642: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/home/user/VersionControlled/poppler' > Makefile:524: recipe for target 'all' failed > make: *** [all] Error 2 > --- I found a workaround for my build issue by creating symlinks: /usr/include/nspr -> /usr/include/nspr4 /usr/inclyde/nss -> /usr/include/nss3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to Adrian Johnson from comment #89) > (In reply to Markus Kilås from comment #88) > > I found a workaround for my build issue by creating symlinks: > > /usr/include/nspr -> /usr/include/nspr4 > > /usr/inclyde/nss -> /usr/include/nss3 > > Are you using configure or cmake? The nss pkgconfig file should contain the > correct include path. After checking out the branch I read INSTALL but did not find any ./configure so I run ./autogen.sh. It first failed for many different reasons which eventually got resolved by installing missing dependencies. After that I run the now generated ./configure and then make. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301784] Re: cannot search text beginning with Alt(-gr) special character
This affects me, too. I just wanted to find a backslash, and other characters that wouldn't work are {}[]~| on german keyboards. -- 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/1301784 Title: cannot search text beginning with Alt(-gr) special character To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1301784/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 427100] Re: JPEG2000 thumbnail causes browser to crash
You can add the tag vivid.. The bug still exists in Ubuntu 15.04! Please fix it, because it also can used for other bad things besides just crashing Nautilus: http://www.ubuntu.com/usn/usn-1315-1/ Here my dmesg output: [ 9415.337774] nautilus[11166]: segfault at 7f4d50c5c540 ip 7f4d28a3701c sp 7f4d50c5c530 error 7 in libjasper.so.1.0.0[7f4d28a1+4c000] [ 9666.642346] nautilus[11391]: segfault at 7f01295a4540 ip 7f00f39ca01c sp 7f01295a4530 error 6 in libjasper.so.1.0.0[7f00f39a3000+4c000] [ 9685.330281] nautilus[11438]: segfault at 7f778a096540 ip 7f7789c9301c sp 7f778a096530 error 6 in libjasper.so.1.0.0[7f7789c6c000+4c000] [11242.749456] nautilus[14785]: segfault at 7f7f29a9b540 ip 7f7f0064201c sp 7f7f29a9b530 error 6 in libjasper.so.1.0.0[7f7f0061b000+4c000] [11373.131440] nautilus[14976]: segfault at 7fca7d85f430 ip 7fca5c3c601c sp 7fca7d85f420 error 6 in libjasper.so.1.0.0[7fca5c39f000+4c000] I can also confirm that it affects JPEG2000 files with transparency. I had a hard time to figure out the problem and extract the file that was the reason. I moved it to a seperate folder with the console and opened it again, and it crashed every time changing in that folder. Opening the file with GIMP or EOG, started from the console, it was no problem to display it. -- 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/427100 Title: JPEG2000 thumbnail causes browser to crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jasper/+bug/427100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1453336] Re: shotwell fails to import iphone photos
Just ran into this bug as well, is there any resolution or workaround for that? -- 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/1453336 Title: shotwell fails to import iphone photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1453336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 348522] Re: gvfsd-gphoto2 copies files to RAM (unsuitable for really large files)
I'm using ubuntu studio (14.04 / Trusty) with the latest updates and this bug is not fixed here! @30: How come it is fixed in your Trusty version? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/348522 Title: gvfsd-gphoto2 copies files to RAM (unsuitable for really large files) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/348522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 997630] Re: evince and eog broken on remote sessions (X, NX, x2go and VNC)
After updating Trusty from Alpha to stable release evince works without any restrictions over x2go. libgeis1: 2.2.16+14.04.20140303-0ubuntu1 libgrip0: 0.3.7+14.04.20140303-0ubuntu1 evince:3.10.3-0ubuntu10 -- 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/997630 Title: evince and eog broken on remote sessions (X, NX, x2go and VNC) To manage notifications about this bug go to: https://bugs.launchpad.net/geis/+bug/997630/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301257] Re: rhythmbox crashed when syncing with iPad (iOS7.1)
** Changed in: rhythmbox (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1301257 Title: rhythmbox crashed when syncing with iPad (iOS7.1) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1301257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301257] Re: rhythmbox crashed when syncing with iPad (iOS7.1)
Fixed with latest updates ** Changed in: rhythmbox (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1301257 Title: rhythmbox crashed when syncing with iPad (iOS7.1) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1301257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301257] Re: rhythmbox crashed when syncing with iPad (iOS7.1)
** Changed in: rhythmbox (Ubuntu) Status: Fix Released = New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1301257 Title: rhythmbox crashed when syncing with iPad (iOS7.1) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1301257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301257] Re: rhythmbox crashed when syncing with iPad (iOS7.1)
No, after the latest update i could see the content of the iPad in rythmbox. But can't delete or add something. So, i delete all the content with iTunes an put it back to Ubuntu and now the same error occurs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1301257 Title: rhythmbox crashed when syncing with iPad (iOS7.1) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1301257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
There is now a new sponsor. Bounty is up to US $300. I hope there will be some more progress here soon. -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
There is now a new sponsor. Bounty is up to US $300. I hope there will be some more progress here soon. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1301257] Re: rhythmbox crashed when syncing with iPad (iOS7.1)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1301257 Title: rhythmbox crashed when syncing with iPad (iOS7.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1301257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 209284] Re: evince crashed with SIGSEGV in g_closure_invoke()
** Changed in: evince (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/209284 Title: evince crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/209284/+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
xbindkeys is a good workaround, too, but still this is annoying. Sometimes working, sometimes not. -- 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 1288299] [NEW] Gedit crashes whenever it trying to open afile containing ة in the file name
Public bug reported: Gedit crashes when I am trying to open a file containing ة in the file name. It doesn't matter if I use the GUI or open it via a Terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 5 16:06:45 2014 InstallationDate: Installed on 2014-03-05 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140304) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (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 gedit in Ubuntu. https://bugs.launchpad.net/bugs/1288299 Title: Gedit crashes whenever it trying to open afile containing ة in the file name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1288299/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 997630] Re: evince and eog broken on remote sessions (X, NX, x2go and VNC)
In Trusty (libgeis1 (2.2.16+13.10.20130919.4-0ubuntu2), libgrip0 (0.3.7+13.10.20130628-0ubuntu2)) the same behavior over x2go and xrdp (TigerVNC) evince -w $FILE works but normal mode crashs with segfault: [ 4382.584653] evince[9291]: segfault at 0 ip 7fcc9247fe10 sp 7fff196e4bc8 error 4 in libgeis.so.1.3.0[7fcc92479000+24000] -- 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/997630 Title: evince and eog broken on remote sessions (X, NX, x2go and VNC) To manage notifications about this bug go to: https://bugs.launchpad.net/geis/+bug/997630/+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
I tried switching input method to xim. Worked first, but not any longer. Not a reliable workaround. -- 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 1224732] Re: Custom keyboard shortcuts don't work
Affects me, too (saucy). Please correct quickly, this is annoying. -- 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 176181] Re: nautilus crashed with SIGSEGV in g_slice_free1()
** Changed in: nautilus (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/176181 Title: nautilus crashed with SIGSEGV in g_slice_free1() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194328] Re: should check that hibernate is really allowed before listing it
Found a workaround: http://askubuntu.com/questions/145443/how-do-i-use-pm-suspend-hybrid-by-default-instead-of-pm-suspend/145676#145676 -- 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/1194328 Title: should check that hibernate is really allowed before listing it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1194328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194328] Re: should check that hibernate is really allowed before listing it
@seb128 what is the correctly way to do it without teak their config to add hibernate? -- 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/1194328 Title: should check that hibernate is really allowed before listing it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1194328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194328] Re: should check that hibernate is really allowed before listing it
I'm confused. this is a regression and there is no official workaround or fix. and you flag this bug as low priority. how can a regression be a low priority? -- 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/1194328 Title: should check that hibernate is really allowed before listing it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1194328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194328] Re: should check that hibernate is really allowed before listing it
I use hibernation since 13.04 came out 3-4 times a day and it has never failed me. it still works 100% of the time if i enter pm-hibernate. The regression is that you don't respect the policy anymore. -- 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/1194328 Title: should check that hibernate is really allowed before listing it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1194328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1194328] Re: Ubuntu 13.10 Close LID actions Ignored
Still can't select hibernate in power settings ** Attachment added: Bildschirmfoto vom 2013-10-04 16:15:55.png https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1194328/+attachment/3859477/+files/Bildschirmfoto%20vom%202013-10-04%2016%3A15%3A55.png -- 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/1194328 Title: Ubuntu 13.10 Close LID actions Ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1194328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1225698] Re: btrfs ssd gedit deletes files
** Attachment added: This happens after waiting a bit https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1225698/+attachment/3822189/+files/Screenshot%20from%202013-09-15%2017%3A09%3A24.png -- 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/1225698 Title: btrfs ssd gedit deletes files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1225698/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1225698] [NEW] btrfs ssd gedit deletes files
Public bug reported: I have my home directory running on btrfs mounted with the following options: /dev/sda2 on /home type btrfs (rw,relatime,ssd,discard,compress=lzo,subvol=@home) When I use gedit to edit a lua-script (not specifically gedit - it's the underlying component I think, because the same happens with ZeroBrane Studio), the file gets deleted, but saving will not work saying that there has been a conflict. Trying to save anyways will yield many conflict files: mfritsche@volta:~/Documents/btw$ ls fetchPages.lua* fetchPages.lua~fetchPages.lua.u1conflict.1 fetchPages.lua.u1conflict.3 fetchPages.lua.u1conflict fetchPages.lua.u1conflict.2 I have eatmydata installed too. Is there a problem with the combination of btrfs, ssd+discard, eatmydata and gedit? After a while of leaving gedit alone, I can save the file again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 15 17:01:34 2013 MarkForUpload: True SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1225698 Title: btrfs ssd gedit deletes files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1225698/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1225698] Re: btrfs ssd gedit deletes files
u1conflict - files seem to indicate a problem between gedit and ubuntuone ** Package changed: gedit (Ubuntu) = ubuntuone-client (Ubuntu) -- 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/1225698 Title: btrfs ssd gedit deletes files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/1225698/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 124440] Re: Ubuntu needs a way to set mouse scrolling speed
** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) = Markus Kühne (m-kuehne) -- 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/124440 Title: Ubuntu needs a way to set mouse scrolling speed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085526]
(In reply to comment #37) Hi, as I cannot help with coding (on this specific issue), I've opened a bounty on FreedomSponsors: http://www.freedomsponsors.org/core/issue/319/support-for-digital-signatures Anyone interested on this bug is welcome to pledge more money by visiting the above link, this money will probably not be enough for the needed work time, but I see it as a nice reward in exchange for the great contribution that completing this bug is. Greate initiative Nelson! I also put in some coins on this one. Cheers, Markus -- 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/1085526 Title: ubuntu pdf doc viewer will not let me sign a document To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to comment #37) Hi, as I cannot help with coding (on this specific issue), I've opened a bounty on FreedomSponsors: http://www.freedomsponsors.org/core/issue/319/support-for-digital-signatures Anyone interested on this bug is welcome to pledge more money by visiting the above link, this money will probably not be enough for the needed work time, but I see it as a nice reward in exchange for the great contribution that completing this bug is. Greate initiative Nelson! I also put in some coins on this one. Cheers, Markus -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35347] Re: bookmarks need subfolders
+1 for this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/35347 Title: bookmarks need subfolders To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/35347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035431] Re: bluetooh-wizard failed to connect to a keyboard
Couldn't pair my Logitech k810 keyboard Parrot by Starck speaker aswell with those bluetooth gui tools - it just crashes when it would come up to enter the pairing PIN. Systems I'm using are on Mint 14 Nadia (htpc) and Ubuntu 12.10 Quantal (laptop). Jake Brown's comment #9 describes how to workaround this issue! My notes: # sniff bluetooth traffic in a terminal sudo apt-get install bluez-hcidump sudo hcidump -XYt # ...writes a lot of debug information to stdout # scan for bluetooth devices hcitool scan Scanning ... 00:1F:20:91:99:CE Logitech K810 # open an other terminal, add the device sudo bluez-simple-agent hci0 00:1F:20:91:99:CE # switch back to terminal with hcidump output look for a row containing the passkey (pin) - here: 919878 [...] 2013-03-15 19:03:23.734363 HCI Event: IO Capability Response (0x32) plen 9 bdaddr 00:1F:20:*:*:* capability 0x02 oob 0x00 auth 0x04 Capability: KeyboardOnly (OOB data not present) Authentication: General Bonding (No MITM Protection) 2013-03-15 19:03:24.694362 HCI Event: User Passkey Notification (0x3b) plen 10 bdaddr 00:1F:20:*:*:* passkey 919878 [...] # Type pin with bluetooth keys and hit enter; # make connection trusted connect sudo bluez-test-device trusted 00:1F:20:91:99:CE yes sudo bluez-test-input connect 00:1F:20:91:99:CE # for Parrot pin is '', to connect use... sudo bluez-test-audio connect XX:XX:XX:XX:XX:XX -- 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/1035431 Title: bluetooh-wizard failed to connect to a keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1035431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1035431] Re: bluetooh-wizard failed to connect to a keyboard
in case of error try: sudo bluez-simple-agent hci0 00:1F:20:91:99:CE repair ...and repeat procedure -- 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/1035431 Title: bluetooh-wizard failed to connect to a keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1035431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1130399] Re: Nautilus CIFS Windows Share Mount Bug
** Changed in: nautilus (Ubuntu) Status: Triaged = 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/1130399 Title: Nautilus CIFS Windows Share Mount Bug To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1130399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1130399] Re: Nautilus CIFS Windows Share Mount Bug
The GNOME team is not longer working on GNOME 3.4 and will not provide a patch for this bug: --- António Fernandes 2013-04-16 12:24:26 UTC Thank you for testing! GNOME developers are no longer working on version 3.4, so unfortunately there will not be any bug fixes for that version. But it's the version shipped with Ubuntu's LTS release, so you may get a fix from Ubuntu. I suggest going back to your Launchpad report and push for a patch there. Thank you again for testing with the live disk! --- https://bugzilla.gnome.org/show_bug.cgi?id=697869#c3 -- 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/1130399 Title: Nautilus CIFS Windows Share Mount Bug To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1130399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168095] Re: Can't play streaming radios
I'm fairly certain this bug is actually a duplicate of bug #1153934. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1168095 Title: Can't play streaming radios To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1168095/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168095] Re: Can't play streaming radios
I can confirm as well on Ubuntu 13.04, 64 bit (all current updates applied). I upgraded from 12.10 to 13.04 if that makes any difference. Here's one of the the URLs I've tried: http://listen.hardbase.fm/tunein- mp3-pls Same behavior as described above, the player shows the name of the stream in the title bar, followed by (Pause). No music is played. Playing MP3 files located on my disk works without a problem. ubuntu-restricted-extras/-addons is installed. I could play the same stream without problems before the upgrade. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1168095 Title: Can't play streaming radios To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1168095/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168095] Re: Can't play streaming radios
** Tags added: amd64 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1168095 Title: Can't play streaming radios To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1168095/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1130399] Re: Nautilus CIFS Windows Share Mount Bug
After upgrading to ubuntu 12.04.2 (64bit)from 11.04 I experience the same problem. The connection which worked under the older ubuntu is not able to connect anymore. Set up a new one does not solve the problem. using cifs works with: sudo mount -t cifs //server /mountpoint -o username=user,domain=dame Version of Nautilus: 3.4.2 -- 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/1130399 Title: Nautilus CIFS Windows Share Mount Bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1130399] Re: Nautilus CIFS Windows Share Mount Bug
Bug filed at https://bugzilla.gnome.org/show_bug.cgi?id=697869 ** Bug watch added: GNOME Bug Tracker #697869 https://bugzilla.gnome.org/show_bug.cgi?id=697869 -- 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/1130399 Title: Nautilus CIFS Windows Share Mount Bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
Hmm... root@XXX:~# ls -al|fgrep '.goutput' -rw--- 1 markus markus 0 mar 7 23:54 .goutputstream-7M8PTW -rw--- 1 markus markus 0 feb 20 22:55 .goutputstream-8BCVSW -rw--- 1 markus markus 0 mar 11 00:21 .goutputstream-8C5ATW -rw--- 1 markus markus 0 feb 20 15:00 .goutputstream-C4UOSW -rw--- 1 markus markus 0 feb 22 00:02 .goutputstream-CGHSSW -rw--- 1 markus markus 0 mar 10 20:15 .goutputstream-ELRLTW -rw--- 1 markus markus 0 feb 23 00:43 .goutputstream-GA4QSW -rw--- 1 markus markus 0 feb 25 00:00 .goutputstream-SPC6SW -rw--- 1 markus markus 0 feb 20 20:34 .goutputstream-UOW5SW -rw--- 1 markus markus 0 feb 20 18:05 .goutputstream-UV7NSW -rw--- 1 markus markus 0 feb 20 18:26 .goutputstream-WC24SW root@XXX:~# file .goutputstream-* .goutputstream-7M8PTW: empty .goutputstream-8BCVSW: empty .goutputstream-8C5ATW: empty .goutputstream-C4UOSW: empty .goutputstream-CGHSSW: empty .goutputstream-ELRLTW: empty .goutputstream-GA4QSW: empty .goutputstream-SPC6SW: empty .goutputstream-UOW5SW: empty .goutputstream-UV7NSW: empty .goutputstream-WC24SW: empty Why empty files? -- 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/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 966294] Re: gstreamer hangs when accessing webcam (on specific hardware)
Just for the record: Had this problem today with the current 12.10 64-bit installer on a Lenovo E530. The installer was booted via EFI from USB stick. Removing the ubi-webcam.py didn't work. But I noticed a dd process taking ~10% CPU although the installer showed that all files were already copied. A few minutes later this was still the case so I killed that process and voilà - the installer went on and finished successfully. My installation layout: /dev/sda (1TB HDD) /dev/sda1 - /home (999GB) /dev/sda2 - swap (1GB) /dev/sdb (16GB mSATA SSD) /dev/sdb1 - efi (256MB) /dev/sdb2 - / (15.7GB) Maybe it has something to do with it? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/966294 Title: gstreamer hangs when accessing webcam (on specific hardware) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/966294/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1018724] Re: rhythmbox stops playing songs after one second
Same issue here with Rhythmbox under 12.04, however it doesn't happen for all tracks for me. It seems to be limited to music located on my Windows shared folder. Is this happening with music on the local drive for anyone here? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1018724 Title: rhythmbox stops playing songs after one second To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1018724/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740506]
(In reply to comment #19) I know that LibreOffice uses NSS as when I look at digital signatures my certificates from Firefox is availble. However, I don't think the LibreOffice Ubuntu packages require the whole Firefox to be installed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/740506 Title: verify digital signatures To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/740506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 883677] Re: Changing the default alert sound breaks desktop sound theme
You'll find a solution here: http://askubuntu.com/a/88839. -- 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/883677 Title: Changing the default alert sound breaks desktop sound theme To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/883677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 941516] Re: gnome-system-monitor crashed with SIGABRT in raise()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/941516 Title: gnome-system-monitor crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/941516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 875509] Re: Can't change avatar Yahoo
I have the same problem with ICQ. I can't change the Alias or Avatar image for ICQ. -- 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/875509 Title: Can't change avatar Yahoo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/875509/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 898143] [NEW] 11.10 does not save Keys and Passwords in Management
Public bug reported: Hi, when trying to save a password or key in 11.10 - like empathy login information i.e. - I got a failure message, no keys an passwords were saved in seahorse management. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: seahorse 3.2.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Wed Nov 30 13:50:32 2011 ExecutablePath: /usr/bin/seahorse InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 oneiric -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/898143 Title: 11.10 does not save Keys and Passwords in Management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/898143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 898143] Re: 11.10 does not save Keys and Passwords in Management
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/898143 Title: 11.10 does not save Keys and Passwords in Management To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/898143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872733] [NEW] Rhythmbox 2.90.1 VERY unstable
Public bug reported: This version of Rhythmbox is very unstable compared to all previous versions I have been using. It crashes when deleting a podcast, freezes when playing music and drags entire system down, video podcasts do not show any video but only play sound. Nightmare release. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: rhythmbox 2.90.1~20110908-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Wed Oct 12 10:41:08 2011 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) SourcePackage: rhythmbox UpgradeStatus: Upgraded to oneiric on 2011-10-11 (1 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/872733 Title: Rhythmbox 2.90.1 VERY unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/872733/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872733] Re: Rhythmbox 2.90.1 VERY unstable
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/872733 Title: Rhythmbox 2.90.1 VERY unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/872733/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 860665] [NEW] unity and starter have disappeared
Public bug reported: . ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.1.92-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Tue Sep 27 17:27:32 2011 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi oneiric -- 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/860665 Title: unity and starter have disappeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/860665/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs