[Bug 1917514] [NEW] Add support of AVIF images
Public bug reported: Please add support of AVIF image file format: - https://en.wikipedia.org/wiki/AV1#AV1_Image_File_Format_(AVIF) The latest Chrome and Firefox 87 support AVIF images, but GIMP won't open them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 2 13:17:37 2021 InstallationDate: Installed on 2020-04-26 (310 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gimp (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 gimp in Ubuntu. https://bugs.launchpad.net/bugs/1917514 Title: Add support of AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1917514/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1917514] Re: Add support for AVIF images
** Summary changed: - Add support of AVIF images + Add support for AVIF images ** Description changed: - Please add support of AVIF image file format: + Please add support for the AVIF image file format: - https://en.wikipedia.org/wiki/AV1#AV1_Image_File_Format_(AVIF) The latest Chrome and Firefox 87 support AVIF images, but GIMP won't open them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.18-1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 2 13:17:37 2021 InstallationDate: Installed on 2020-04-26 (310 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gimp 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 gimp in Ubuntu. https://bugs.launchpad.net/bugs/1917514 Title: Add support for AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1917514/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825708] [NEW] Please Include Package Names
Public bug reported: Gnome-Software does not include a software package's name in the details section of each software it catalogs and I want this to be added for the following reasons. 1) When submitting bug reports and feature requests, it is necessary to know the package name. When I use gnome-software to install a piece of software, I expect to be able to go back to gnome-software to discover software's package name. Since it doesn't include this pertinent detail, I'm having to use a number of command to discover it. 2) Although I use gnome-software to discover available software, I always like to collect that software's package name, so I can add to my "sudo apt install" list, so that when I set up my computer from scratch, I can use one command to reinstall all the software packages I've installed previously. These are my two reason, but I'm sure others have more. The bottom line is, the package name is a very pertinent piece of information that gnome-software should include in the details section of each software it catalogs. Look at what is in the details section right now. Hardly any of those details are anything I'll ever be interested in, but the package name is VERY pertinent to me. Please add this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.30.6-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 05:03:55 2019 InstallationDate: Installed on 2019-01-07 (103 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: Gnome-Software does not include a software package's name in the details - section of each software it catalogs and I want this added for the + section of each software it catalogs and I want this to be added for the following reasons. 1) When submitting bug reports and feature requests, it is necessary to - know the package name. I use gnome-software to install a piece of + know the package name. When I use gnome-software to install a piece of software, I expect to be able to go back to gnome-software to discover - the package name of the software it installed. Since it doesn't include - this pertinent detail, I'm having to use a number of command to discover - it. + software's package name. Since it doesn't include this pertinent detail, + I'm having to use a number of command to discover it. 2) Although I use gnome-software to discover available software, I - always like to add its package name to my "sudo apt install" list, so - that when I set up my computer from scratch, I can use one command to - reinstall all the software packages I had previously. + always like to collect that software's package name, so I can add to my + "sudo apt install" list, so that when I set up my computer from scratch, + I can use one command to reinstall all the software packages I've + installed previously. These are my two reason, but I'm sure others have more. The bottom line is, the package name is a very pertinent piece of information that gnome-software should include in the details section of each software it catalogs. Look at what is in the details section right now. Hardly any of those details are anything I'll ever be interested in, but the package name is VERY pertinent to me. Please add this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-software 3.30.6-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 05:03:55 2019 InstallationDate: Installed on 2019-01-07 (103 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) InstalledPlugins: - gnome-software-plugin-flatpak N/A - gnome-software-plugin-snap3.30.6-2ubuntu3 + gnome-software-plugin-flatpak N/A + gnome-software-plugin-snap3.30.6-2ubuntu3 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) -- You received this bug notification because you are a member of Ubuntu
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
So now we have another Ubuntu release: 19.04. Xorg is still the default desktop and you cannot do fractional scaling. No progress to be seen! https://bugs.launchpad.net/ubuntu-gnome/+bug/1723411 ** Tags added: disco -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1568056] Re: Official Package-Names Not Shown in Gnome-Software
*** This bug is a duplicate of bug 1825708 *** https://bugs.launchpad.net/bugs/1825708 ** This bug has been marked a duplicate of bug 1825708 Please Include Package Names -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1568056 Title: Official Package-Names Not Shown in Gnome-Software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1568056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1581760] Re: name of package
*** This bug is a duplicate of bug 1825708 *** https://bugs.launchpad.net/bugs/1825708 ** This bug is no longer a duplicate of bug 1568056 Official Package-Names Not Shown in Gnome-Software ** This bug has been marked a duplicate of bug 1825708 Please Include Package Names -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1581760 Title: name of package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1581760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825708] Re: Please Include Package Names
** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/issues #644 https://gitlab.gnome.org/GNOME/gnome-software/issues/644 ** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/issues/644 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1825708 Title: Please Include Package Names To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1825708/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825959] [NEW] Missing "Additional Search Domain" Feature
Public bug reported: Ubuntu 19.04 uses the gnome-control-panel's network manager, and it is missing the feature of adding "Additional Search Domains". Here's that feature as it looked in Ubuntu 16.04: https://i.imgur.com/ZVMknmP.png Here's that same tab as shown in Ubuntu 19.04 via gnome-control-panel: https://i.imgur.com/XwRPnRS.png And, very importantly, it is also missing for VPN settings: https://i.imgur.com/5x769jY.png This feature helps you ping a computer by name without having to type in the full domain address of that computer. If you are connected to just one network, it might not be necessary. But when you are connected to multiple networks it is very useful because you can put in all the domains you are connected to and then be able to just ping a computer's name without having to type its whole domain too. Essentially, it tells the network manager, if you do not find a computer with this name on the first domain you look for it at, then also look for that computer name on these other domains. This is a regression of functionality (compared to Ubuntu 16.04). Please add it back. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 04:07:24 2019 InstallationDate: Installed on 2019-01-07 (105 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-04-21 (2 days ago) ** Affects: gnome-control-center Importance: Unknown Status: Unknown ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1825959 Title: Missing "Additional Search Domain" Feature To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1825959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825959] Re: Missing "Additional Search Domain" Feature
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #485 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/485 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/485 Importance: Unknown Status: Unknown -- 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/1825959 Title: Missing "Additional Search Domain" Feature To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1825959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825965] [NEW] Missing "Additional DNS Servers"
Public bug reported: Ubuntu 19.04 uses the gnome-control-panel's network manager, and it is missing the feature for adding "Additional DNS Servers". Here's that feature as it looked in Ubuntu 16.04: https://i.imgur.com/j3nF1nu.png Notice the "Additional DNS Servers" feature above. Here's that same tab as shown in Ubuntu 19.04 via gnome-control-panel: https://i.imgur.com/XwRPnRS.png When you auto-connect to a LAN, you will automatically receive a DNS server from dhcp. While that DNS server may be really good at resolving local computers, it may not be able to resolve everything. So, it is nice to both "be able to keep that dns server issued by dhcp" and also "add additional DNS servers" for resolving non-local domains that the issued dns server may not be able to resolve. Essentially, it tells the network manager, if you can't resolve this domain from this local DNS server, try checking with these DNS servers too. This is a regression of functionality (compared to Ubuntu 16.04). Please add it back. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 05:08:01 2019 InstallationDate: Installed on 2019-01-07 (105 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-04-21 (2 days ago) ** Affects: gnome-control-center Importance: Unknown Status: Unknown ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #486 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/486 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/486 Importance: Unknown Status: Unknown -- 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/1825965 Title: Missing "Additional DNS Servers" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1825965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825965] Re: Missing "Additional DNS Servers"
Actually, I think this does work, it is just labeled differently. As long as it allows you to have both the "automatically acquired DNS server" (from DHCP) and at the same time have "Additional DNS Servers", I think we're good here. -- 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/1825965 Title: Missing "Additional DNS Servers" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1825965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825971] [NEW] Scroll to Switch Between Windows of a Single Application
Public bug reported: First of All, you guys have done a fine job at getting the dock in GNOME 3 to be like the wonderful dock from Unity 7. With that said, there is one missing feature that I'm having a hard time doing without. In the Unity7 dock, you could hover over an application's launcher, and then scroll your mouse-wheel to switch between every window instance of that particular application. You cannot do this in the dock provide in Ubuntu 19.04. I'm aware that I can click the launcher to see a list of open window instances, and that's fine (leave that there too), however please at that scroll functionally (like Ubuntu 16.04 had); its a killer feature. Please, pretty please, add that same feature back into this new dock. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu7 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 05:44:22 2019 InstallationDate: Installed on 2019-01-07 (105 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to disco on 2019-04-21 (2 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: First of All, you guys have done a fine job at getting the dock in GNOME 3 to be like the wonderful dock from Unity 7. With that said, there is one missing feature that I'm having a hard time doing without. In the Unity7 dock, you could hover over an application's launcher, and then scroll your mouse-wheel to switch between every window instance of that particular application. You cannot do this in the dock provide in Ubuntu 19.04. + + I'm aware that I can click the launcher to see a list of open window + instances, and that's fine (leave that there too), however please at + that scroll functionally (like Ubuntu 16.04 had); its a killer feature. Please, pretty please, add that same feature back into this new dock. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu7 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 05:44:22 2019 InstallationDate: Installed on 2019-01-07 (105 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to disco on 2019-04-21 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1825971 Title: Scroll to Switch Between Windows of a Single Application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1825971/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768078] Re: gnome-control-center network panel missing DNS search
Also see: - https://gitlab.gnome.org/GNOME/gnome-control-center/issues/485 - https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1825959 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #485 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/485 -- 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/1768078 Title: gnome-control-center network panel missing DNS search To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1768078/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825447] Re: Indicators Scroll events are not emitted in 19.04
https://bugs.launchpad.net/radiotray/+bug/1828069 Screenshot here: https://github.com/ebruck/radiotray-ng/issues/112 ** Bug watch added: github.com/ebruck/radiotray-ng/issues #112 https://github.com/ebruck/radiotray-ng/issues/112 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1825447 Title: Indicators Scroll events are not emitted in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825447/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825447] Re: Indicators Scroll events are not emitted in 19.04
Thank you for fixing this. The app-level volume control is working great now by scrolling on top of the RadioTray icon. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1825447 Title: Indicators Scroll events are not emitted in 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825447/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 413357] Re: file-roller "An error occurred while adding files to the archive."
In Ubuntu 19.04, using Nemo, I'm getting this error for most of the formats that it list I can compress to. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/413357 Title: file-roller "An error occurred while adding files to the archive." To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/413357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
I noticed that 18.04.1 has been released. Has there been any progress for providing fractional scaling (via the default GUI) like was offered in Ubuntu 16.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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
** Tags added: bionic xenial -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
** Tags removed: xenial -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1568056] Re: Official Package-Names Not Shown in Gnome-Software
I do recall posting upstream at some point, but those damn idiots at GNOME rarely grant any suggestion. I'm done with GNOME! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1568056 Title: Official Package-Names Not Shown in Gnome-Software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1568056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723403] [NEW] Gedit doesn't Gain Focus Upon Opening a File in Nautilus
Public bug reported: If you already have one tab open in gedit, and then minimize gedit, if you double click on another file in nautilus, gedit should regain focus, but it does not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gedit 3.22.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 13 06:26:01 2017 InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1723403 Title: Gedit doesn't Gain Focus Upon Opening a File in Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1723403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
I agree with sergeiS 225%. Not 200%! Long live Ubuntu 16.04.5 and Unity 7! -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
Is this really fixed in Ubuntu 18.04? I don't want to waste my time upgrading again unless fractional scaling truly supported. -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
I just install Ubuntu 18.04 in a virtual machine and updated it. I don't see a fix, I see the same disappointment: https://i.imgur.com/tTanPlv.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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292041] Re: Lockscreen doesn't turn off the screen
Maybe lock screen should always happen before the screen turns off? Or, anytime lock screen happens it should also turn off the monitors? Is there any work around that I can apply? My cron job trick no longer works: https://unix.stackexchange.com/questions/505488/ubuntu-16-04-5-ruining-monitors-by-never-turning-them-off -- 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/1292041 Title: Lockscreen doesn't turn off the screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292041] Re: Lockscreen doesn't turn off the screen
Please open this bug back up. It is not fixed! All monitors go off initially, but as soon as the lock-screen happens, my laptop's built-in monitor comes back on and stays on forever. This is an expensive 4K monitor and this bug is burning it up. The only work-around I've found is to turn off screen-lock, which is not acceptable from a security perspective. Please help! -- 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/1292041 Title: Lockscreen doesn't turn off the screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846499] [NEW] e2scrub_all.service is a disabled or a static unit not running, not starting it.
Public bug reported: Upon attempting to upgrade form Ubuntu 19.04 to Ubuntu 19.10. The installation got stuck with this being the last command line output: "e2scrub_all.service is a disabled or a static unit not running, not starting it." ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: eel eely -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1846499 Title: e2scrub_all.service is a disabled or a static unit not running, not starting it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1846499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846499] Re: e2scrub_all.service is a disabled or a static unit not running, not starting it.
I'm going to start tagging by number instead of codenames. Code-names are stupid. ** Tags removed: eel eely ** Tags added: 19.10 eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1846499 Title: e2scrub_all.service is a disabled or a static unit not running, not starting it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1846499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849391] [NEW] Can't Persist Sound Output Selection Between Reboots
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Public bug reported: Each time I reboot Ubuntu 19.10, I have to open gnome-control-center and set the sound output device back to my Laptop's Built-in speakers. Otherwise, it will typically default to HDMI devices that don't even appear to have speakers. Which file are these settings saved to? I'm thinking that maybe that file is corrupted and that if I delete that file maybe Ubuntu 19.10 will start remembering my sound output preferences. I'm also open to other suggestions. Also submitted at AskUbuntu: https://askubuntu.com/questions/1183052/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 16:39:58 2019 InstallationDate: Installed on 2019-10-19 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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 eoan ** Description changed: Each time I reboot Ubuntu 19.10, I have to open gnome-control-center and set the sound output device back to my Laptop's Built-in speakers. Otherwise, it will typically default to HDMI devices that don't even appear to have speakers. - Which file are these settings saved to? I'm think that maybe that file - is corrupted and that if I delete that file maybe Ubuntu 19.10 will + Which file are these settings saved to? I'm thinking that maybe that + file is corrupted and that if I delete that file maybe Ubuntu 19.10 will start remembering my sound output preferences. I'm also open to other suggestions. Also submitted at AskUbuntu: https://askubuntu.com/questions/1183052/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 16:39:58 2019 InstallationDate: Installed on 2019-10-19 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash 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/1849391 Title: Can't Persist Sound Output Selection Between Reboots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849880] [NEW] Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation
Public bug reported: The Gnome Sound Settings tab contains enough options to where you have to scroll down to see them all. Since the scrollbar is so narrow, I use my mouse-scroll-wheel to achieve this scroll navigation. However, while scrolling with the intention of "navigation", if the mouse-cursor passes over the Output Device drop-down-menu, it inadvertently changes the drop-down's selection. The ability to change drop-down-menu selections, using the mouse-scroll- wheel is convenient in some cases, but it become problematic when the user is simply intending to do scroll navigation. I can see a non-advance user accidentally changing sound settings that they had no intention of changing in this design. Plus, even if they do notice the inadvertent changes, they might not know "what to change it back to". It may be better to disable scroll driven option selection changes in these menus. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Oct 25 12:29:32 2019 InstallationDate: Installed on 2019-10-19 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash 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 eoan -- 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/1849880 Title: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849880] Re: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation
I've attached a screenshot. Each drop-down-menu you see can received unintended selection changes during mouse-scroll navigation. ** Attachment added: "sound.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849880/+attachment/5300169/+files/sound.png -- 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/1849880 Title: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849880] Re: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation
Upstream Bug Report: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/745 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #745 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/745 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/745 Importance: Unknown Status: Unknown -- 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/1849880 Title: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849880] Re: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation
Video Showcasing the issue: https://youtu.be/Z6jNCCxC4hA -- 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/1849880 Title: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849880] Re: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation
** Description changed: The Gnome Sound Settings tab contains enough options to where you have to scroll down to see them all. Since the scrollbar is so narrow, I use my mouse-scroll-wheel to achieve this scroll navigation. However, while scrolling with the intention of "navigation", if the - mouse-cursor passes over the Output Device drop-down-menu, it - inadvertently changes the drop-down's selection. + mouse-cursor passes over the Output Device drop-down-menu, or any of the + slider controls, it inadvertently changes those options. The ability to change drop-down-menu selections, using the mouse-scroll- - wheel is convenient in some cases, but it become problematic when the + wheel is convenient in some cases, but it becomes problematic when the user is simply intending to do scroll navigation. I can see a non-advance user accidentally changing sound settings that they had no intention of changing in this design. Plus, even if they do notice the inadvertent changes, they might not know "what to change it back to". It may be better to disable scroll driven option selection changes in these menus. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Oct 25 12:29:32 2019 InstallationDate: Installed on 2019-10-19 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash 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/1849880 Title: Mouse-Scrolling Changes Drop-Down Selections During Scroll Navigation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
I've attached the syslog for easier viewing. ** Attachment added: "syslog.txt" https://bugs.launchpad.net/network-manager/+bug/1849930/+attachment/5300267/+files/syslog.txt ** Description changed: When I add only one L2TP VPN profile to gnome-control-center's Network > - VPN setting, it works fine. + VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request with message ID 3016741680 processing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of request message ID 0, seq 3 Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending pack
[Bug 1849930] [NEW] Additional VPN Breaks First VPN
Public bug reported: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request with message ID 3016741680 processing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of request message ID 0, seq 3 Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 Net
[Bug 1849930] Re: Additional VPN Breaks First VPN
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #746 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746 Importance: Unknown Status: Unknown -- 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/1849930 Title: Additional VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
** Also affects: strongswan 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/1849930 Title: Additional VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
How is it possible that adding an additional VPN profile can corrupted an "already added and working" vpn? Which packages would be responsible for that type of corruption? Most importantly, short of reinstalling Ubuntu 19.10 what would be a workaround that may remove this corruption? For example, many times in the past, when I've had applications get corrupted, I could usually delete some .hiddenFolder or configuration file, and it would repair the corruption after rebooting. Do any of you know which files would have to be deleted to get my VPN situation back to "fresh install quality" (short of actually reinstalling)? -- 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/1849930 Title: Additional VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional VPN Breaks First VPN
** Description changed: When I add only one L2TP VPN profile to gnome-control-center's Network > VPN settings, it works fine. However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't work, but it corrupts the first L2TP VPN so that it too stops working. Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it remains corrupted. Additionally, removing all VPN profiles and re-adding the first one back, doesn't repair the corruption. Rebooting and adding them back doesn't work either. The only thing that works, that I've found, is completely reinstalling Ubuntu 19.10. Please advise better workarounds than reinstalling. + + In case it matters, these additional packages were also required for my + initial VPN setup: + + sudo apt-get install -y network-manager-l2tp network-manager-l2tp-gnome + strongswan Here's what's in the syslog on a failed VPN Connection attempt: Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5632] audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" name="L2TP VPN1" pid=3531 uid=1000 result="success" Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5702] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Started the VPN service, PID 7273 Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.5747] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: Saw the service appear; activating connection Oct 26 02:58:35 workstation5 NetworkManager[1241]: [1572076715.6566] vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP VPN1",0]: VPN connection: (ConnectInteractive) reply received Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec failed: starter is not running Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 IPsec [starter]... Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn '1942cf95-93b1-4e74-a44a-947a46bffb5a' Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec... Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ SA V V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (236 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (156 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ SA V V V V ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) vendor ID Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024 Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[500] to 49.230.24.121[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (244 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 [ KE No NAT-D NAT-D ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, sending keep alives Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 0 [ ID HASH ] Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 49.230.24.121[500] to 192.168.1.2[500] (68 bytes) Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload length, decryption failed? Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed INFORMATIONAL request Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request with message ID 3016741680 processing failed Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of request message ID 0, seq 3 Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 192.168.1.2
[Bug 1849930] Re: Additional VPN Breaks First VPN
This doesn't fix the underlying bug, but I was able to find a workaround that repairs the corruption caused by the bug. See here: https://askubuntu.com/a/1184070/256054 -- 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/1849930 Title: Additional VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
** Also affects: l2tp-ipsec-vpn 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/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
@seb128 : By default, GNOME provides the gnome-control-center for accomplishing this in Ubuntu 19.10. I didn't know I could still use the nm-connection-editor GUI in Ubuntu 19.10. I was simply using what GNOME provided. I'm a big fan of Unity 7, so I'm glad to see that nm-connection-editor GUI again. Thanks. Here are the VPN related packages that I've added to the default Ubuntu 19.10 installation: sudo apt install network-manager-l2tp network-manager-l2tp-gnome strongswan Of these packages, launchpad will not allow specifying these two packages: network-manager-l2tp network-manager-l2tp-gnome I submitted a bug here, but couldn't associate it in the bug header above: https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112 ** Bug watch added: github.com/nm-l2tp/NetworkManager-l2tp/issues #112 https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112 -- 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/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
** Tags added: upgrade-software-version -- 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/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
The actual programmer of this module says we need to upgrade-software- version. 1) https://gitlab.gnome.org/GNOME/gnome-control-center/issues/746#note_634394 2) https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112#issuecomment-547218557 He believes that this issue is fixed in NetworkManager-l2tp 1.2.12 and later. Who at Ubuntu can accomplish getting this upgraded in 19.10 instead of having to wait for 20.04? Ideally, the upgrade should just be provided via the standard Ubuntu Update GUI or CLI: sudo apt update ; sudo apt upgrade At this point, upstream has already addressed this bug in a later version, and it is now up to Ubuntu to upgrade the package in the repositories. What is the likelihood that this will be upgraded in Upgraded 19.10? -- 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/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849930] Re: Additional L2TP VPN Breaks First VPN
I confirm that the packages provided by Douglas Kosovic's PPA work successfully: https://github.com/nm-l2tp/NetworkManager-l2tp/issues/112#issuecomment-548593238 -- 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/1849930 Title: Additional L2TP VPN Breaks First VPN To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851067] [NEW] Screen Lock Recovery has Unnecessary Delays
Public bug reported: You can turn "Sreen Lock" off using gnome-control-center > Privacy > Screen Lock : Off. However, this is bad terminology because you screen will still go into the exact same "Screen Lock" state upon an inactivity timeout, but the only difference is that you don't have to enter your password to regain access to the desktop. While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a couple of behaviors. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press enter. I want to be able to accomplish this also by moving my mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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 eoan -- 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/1851067 Title: Screen Lock Recovery has Unnecessary Delays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1851067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851067] Re: Screen Lock Recovery has Unnecessary Delays
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 Importance: Unknown Status: Unknown -- 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/1851067 Title: Unnecessary Delays Recovering from Screen Lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851067] Re: Screen Lock Recovery has Unnecessary Delays
** Description changed: You can turn "Sreen Lock" off using gnome-control-center > Privacy > - Screen Lock : Off. + Screen Lock : Off: - However, this is bad terminology because you screen will still go into - the exact same "Screen Lock" state upon an inactivity timeout, but the - only difference is that you don't have to enter your password to regain - access to the desktop. + https://gitlab.gnome.org/GNOME/gnome-control- + center/uploads/62e176ed49faf1defaf6e4a36ad86f77/ScreenLock.png + + **Side-note:** this is bad terminology because your screen will still go + into the exact same state that "Screen Lock: On" accomplishes (upon an + inactivity timeout), but the only difference is that you won't have to + enter your password to regain access to the desktop. I would have named + this "Require Password Authentication After Inactivity Timeout" (to me + wordy is better than unclear). While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a - couple of behaviors. + couple of things. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press - enter. I want to be able to accomplish this also by moving my mouse. + the "enter" key. I want to be able to accomplish this also by moving my + mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. + Also, there should be separate setting for "blank screen x time", and + "monitor power off after x time". + + My ideal settings would to make the screen go black after 5 minutes of + inactively and to turn my monitors completely off after 15 minutes of + inactively, and I'd like to control whether each of these requires + password authentication or not. On the 5 minute one, I personally would + note require a password, but I would require a password after monitor + going off. However, on either of these, I expect the desktop to be fully + functional immediately after coming out of these states. At the very + least please remove these unnecessary delays. + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Screen Lock Recovery has Unnecessary Delays + Unnecessary Delays Recovering from Screen Lock -- 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/1851067 Title: Unnecessary Delays Recovering from Screen Lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
I recently submitted a bug about this topic for Ubuntu 19.10: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 -- 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/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
Will that fix change this issue?: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 Other links: - https://askubuntu.com/questions/1187437/override-gnome-3s-slow-screen- lock-recovery - https://www.reddit.com/r/gnome/comments/eocpga/unnecessary_delays_recovering_from_screen_lock/ ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1677198] [NEW] OpenVPN not Working in 17.04
Public bug reported: I can definitely confirm that Network Manager's OpenVPN is not working yet in Ubuntu 17.04. I set up my configuration via import: http://neartalk.com/ss/2017-03-29_001_633x332.png On all earlier versions of Ubuntu, after importing the configuration, I'm able to connect to the VPN. However, in 17.04, connection attempt always give this error immediately: "The VPN Connection disconnected because the VPN Service has stopped" Clearly the VPN Service has NOT stopped. I confirmed this be taking the exact same import-file and imported it into an Ubuntu 16.04 computer and then the VPN connected without issue. Also, with this same import-file I had no issues in Ubuntu 16.10. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1 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: Wed Mar 29 05:25:14 2017 InstallationDate: Installed on 2017-01-30 (58 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago) ** Affects: network-manager Importance: Undecided Status: New ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Description changed: I can definitely confirm that Network Manager's OpenVPN is not working yet in Ubuntu 17.04. I set up my configuration via import: http://neartalk.com/ss/2017-03-29_001_633x332.png On all earlier versions of Ubuntu, after importing the configuration, I'm able to connect to the VPN. However, in 17.04, connection attempt always give this error immediately: "The VPN Connection disconnected because the VPN Service has stopped" + + Clearly the VPN Service has NOT stopped. I confirmed this be taking the + exact same import-file and imported it into an Ubuntu 16.04 computer and + then the VPN connected without issue. Also, with this same import-file I + had no issues in Ubuntu 16.10. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1 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: Wed Mar 29 05:25:14 2017 InstallationDate: Installed on 2017-01-30 (58 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago) ** Also affects: network-manager Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1677198 Title: OpenVPN not Working in 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1677198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1410993] [NEW] Won't launch New Images if Already Open
*** This bug is a duplicate of bug 1393227 *** https://bugs.launchpad.net/bugs/1393227 Public bug reported: The eog image viewer that comes with Ubuntu 14.04 works fine if you double-click on ONE image from a file browsers. However, if you navigate to another folder and then double-click on another image, eog doesn't gain focus like you'd expect, and it stays minimized on the Unity launcher bar. Anytime you double-click on an picture-image-file (jpg, gif, png, etc.), EOG should gain focus and its window should come to the front of the window stack. Currently if the program is already open, it doesn't handle new launchings very well. I think it should either launch multiple instance when you doube-click on a picture in a different folder, or it should focus and display the last picture you double-click on from the file-browser. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 14 15:51:26 2015 InstallationDate: Installed on 2014-11-23 (52 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** This bug has been marked a duplicate of bug 1393227 Second window doesn't appear in forground -- 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/1410993 Title: Won't launch New Images if Already Open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1410993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1393227] Re: Second window doesn't appear in forground
Yeah, I've been experiencing this bug for a long time, and still am in Ubuntu 14.04. I just noticed Valentin Crone's report, after creating this duplicate: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1410993 -- 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/1393227 Title: Second window doesn't appear in forground To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1393227/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1393227] Re: Second window doesn't appear in forground
Yeah, I've noticed this in file-roller too. Maybe they do share the same library and it is that library that is flawed in this regard. ** Also affects: file-roller Importance: Undecided Status: New -- 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/1393227 Title: Second window doesn't appear in forground To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1393227/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1393227] Re: Second window doesn't appear in forground
The eog image viewer that comes with Ubuntu 14.04 works fine if you double-click on ONE image from a file browsers. However, if you navigate to another folder and then double-click on another image, eog doesn't gain focus like you'd expect, and it stays minimized on the Unity launcher bar. Anytime you double-click on an picture-image-file (jpg, gif, png, etc.), EOG should gain focus and its window should come to the front of the window stack. Currently if the program is already open, it doesn't handle new launchings very well. I think it should either launch multiple instance when you doube-click on a picture in a different folder, or it should focus and display the last picture you double-click on from the file-browser. -- 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/1393227 Title: Second window doesn't appear in forground To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1393227/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 437429] Re: No GUI to configure/disable login sound
I wish this was more like Windows 7. See "Play Windows Startup Sound" : http://neartalk.com/ss/2015-06-08_004_1294x554.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/437429 Title: No GUI to configure/disable login sound To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/437429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1210788] Re: gnome-system-monitor won't launch - Timeout was reached
No problem. Thanks your quick attention to the issue. -- 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/1210788 Title: gnome-system-monitor won't launch - Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1210788/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1250532] Re: Very Slow to Show Properties of a File (window dims out)
I just want to report that his remains an issue for me. Is there anything I can do to help this bug along? -- 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/1250532 Title: Very Slow to Show Properties of a File (window dims out) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1250532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1250532] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1250532/+attachment/3948748/+files/Dependencies.txt -- 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/1250532 Title: Very Slow to Show Properties of a File (window dims out) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1250532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1250532] usr_lib_nautilus.txt
apport information ** Attachment added: "usr_lib_nautilus.txt" https://bugs.launchpad.net/bugs/1250532/+attachment/3948749/+files/usr_lib_nautilus.txt -- 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/1250532 Title: Very Slow to Show Properties of a File (window dims out) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1250532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1250532] Re: Very Slow to Show Properties of a File (window dims out)
I upgraded to 14.04 alpha, and this had no effect on fixing the problem. ** Tags added: apport-collected trusty ** Description changed: When I right lick on a file, in Nautilus, and then click properties, I'm experiencing a great deal of lag before the properties are displayed. It doesn't matter if the file is small or large; it takes about 10 seconds before the properties are displayed, and the Nautilus window becomes dim during the wait. I've noticed this behavior since upgrading from Ubuntu 13.04 to 13.10, and have never experienced it prior (using the exact same hardware). dbench says my solid state hard drive's speed is over 400 MB/sec sudo apt-get install dbench ; dbench 4 4 16672 426.89 MB/sec warmup 1 sec latency 14.404 ms 4 35634 418.37 MB/sec warmup 2 sec latency 11.449 ms 4 54492 412.88 MB/sec warmup 3 sec latency 9.392 ms 4 72852 409.45 MB/sec warmup 4 sec latency 11.530 ms 4 91399 406.85 MB/sec warmup 5 sec latency 11.072 ms 4110254 407.92 MB/sec warmup 6 sec latency 12.197 ms My hard drive is very capable of pulling a file's properties quickly, so I'm reporting this as a bug in Nautilus (where I'm experiencing this issue). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 12 09:33:50 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+2258+294'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-10-07 (36 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-10-18 (25 days ago) + --- + ApportVersion: 2.13.1-0ubuntu1 + Architecture: amd64 + DistroRelease: Ubuntu 14.04 + GsettingsChanges: org.gnome.nautilus.list-view default-column-order ['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where'] + InstallationDate: Installed on 2013-10-07 (99 days ago) + InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) + NonfreeKernelModules: wl + Package: nautilus 1:3.8.2-0ubuntu5 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7 + Tags: trusty + Uname: Linux 3.13.0-2-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2014-01-08 (5 days ago) + UserGroups: -- 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/1250532 Title: Very Slow to Show Properties of a File (window dims out) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1250532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1178697] Re: Regression - Can't "Open with" on Folders
*** This bug is a duplicate of bug 1026254 *** https://bugs.launchpad.net/bugs/1026254 ** Tags added: saucy trusty -- 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/1178697 Title: Regression - Can't "Open with" on Folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1178697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back
I upgraded to the 14.04 alpha, and this regression-bug persists; you still cannot "Open With" on a folder in 14.04. I've been using Ubuntu exclusively since version 7.04. Around Ubuntu 12.10 I started noticing this regression. It is so convenient to use "Open With" on folders especially when they contain music or videos. I like being able to right-click on a folder and then open with VLC for example. Without this feature, I have open VLC, and then position its window in a manner that I can drag and drop the folder into VLC. I miss the days when I could just right-click the folder and then > Open With > VLC The same is true for music folders. 1) Right-Click the folder (containing music files) 2) Select "Open With" 3) Select your music application (Audacious in my case). Very handy! We need to bring this back for 14.04 LTS! -- 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/1026254 Title: Open with on folders was removed, Ubuntu should consider patching back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1026254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1178697] Re: Regression - Can't "Open with" on Folders
*** This bug is a duplicate of bug 1026254 *** https://bugs.launchpad.net/bugs/1026254 I upgraded to the 14.04 alpha, and this regression-bug persists; you still cannot "Open With" on a folder in 14.04. I've been using Ubuntu exclusively since version 7.04. Around Ubuntu 12.10 I started noticing this regression. It is so convenient to use "Open With" on folders especially when they contain music or videos. I like being able to right-click on a folder and then open with VLC for example. Without this feature, I have open VLC, and then position its window in a manner that I can drag and drop the folder into VLC. I miss the days when I could just right-click the folder and then > Open With > VLC The same is true for music folders. 1) Right-Click the folder (containing music files) 2) Select "Open With" 3) Select your music application (Audacious in my case). Very handy! We need to bring this back for 14.04 LTS! -- 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/1178697 Title: Regression - Can't "Open with" on Folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1178697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1269817] [NEW] upgrade-software-version to 3.11+
Public bug reported: Gedit 3.11 has been released: http://ftp.gnome.org/pub/GNOME/sources/gedit/ It offers a much more modern look, which can be seen in screen-shots here: http://iloveubuntu.net/gedit-311x-presented-impressive-look-feel I'd like to see this package updated for Ubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8 Uname: Linux 3.13.0-3-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 16 08:15:08 2014 InstallationDate: Installed on 2013-10-07 (101 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to trusty on 2014-01-08 (7 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty upgrade-software-version ** Tags added: upgrade-software-version ** Description changed: Gedit 3.11 has been released: http://ftp.gnome.org/pub/GNOME/sources/gedit/ It offers a much more modern look, which can be seen in screen-shots here: http://iloveubuntu.net/gedit-311x-presented-impressive-look-feel - I like to see this package updated for Ubuntu 14.04. + I'd like to see this package updated for Ubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit 3.10.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8 Uname: Linux 3.13.0-3-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 16 08:15:08 2014 InstallationDate: Installed on 2013-10-07 (101 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to trusty on 2014-01-08 (7 days ago) -- 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/1269817 Title: upgrade-software-version to 3.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1269817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1269817] Re: upgrade-software-version to 3.11+
Ok; that makes sense. -- 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/1269817 Title: upgrade-software-version to 3.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1269817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1250532] Re: Very Slow to Show Properties of a File (window dims out)
You can consider this a work-around, but it is more than that to me. Due to this bug not being resolved, I'm no longer using Nautilus I'm now using thunar, which is not only faster for viewing the properties of a file or folder, it is also faster than Nautilus on every single task you'd do in Nautilus. I'm especially impressed with how fast it views network folders compared to Nautilus. sudo apt-get install thunar -- 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/1250532 Title: Very Slow to Show Properties of a File (window dims out) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1250532/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back
A work-around, if you really need the "open with" (on a folder) feature, is to use Nemo (until Nautilus fixes this regression): sudo apt-get install nemo -- 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/1026254 Title: Open with on folders was removed, Ubuntu should consider patching back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1026254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1178697] Re: Regression - Can't "Open with" on Folders
*** This bug is a duplicate of bug 1026254 *** https://bugs.launchpad.net/bugs/1026254 A work-around, if you really need the "open with" (on a folder) feature, is to use Nemo (until Nautilus fixes this regression): sudo apt-get install nemo -- 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/1178697 Title: Regression - Can't "Open with" on Folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1178697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1178697] Re: Regression - Can't "Open with" on Folders
*** This bug is a duplicate of bug 1026254 *** https://bugs.launchpad.net/bugs/1026254 @Sebastien How do you think I found about nemo? It was on this forum: http://www.reddit.com/r/Ubuntu/comments/1vv3wy/ubuntu_should_replace_nautilus_with_thunar_as/ I'm surprised that you would criticised me for reporting my finding back to this report, giving that it is an excellent work-around for those waiting on Nautilus to fix this regression. In addition to the purposes you mention, the bug tracker has always been (also) a way to discover work-arounds DURING unfixed bugs. -- 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/1178697 Title: Regression - Can't "Open with" on Folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1178697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1178697] Re: Regression - Can't "Open with" on Folders
*** This bug is a duplicate of bug 1026254 *** https://bugs.launchpad.net/bugs/1026254 Respectfully, please consider this: All levels of users come across these bug reports trying to solve their immediate problem. Many will indeed find my comment useful, and consider it a legitimate "workaround", because their immediate problem can be solved with one command: sudo apt-get install nemo I'm a loyal and happy Unity Desktop user, but when a default package regresses, I consider it objective and relevant (as the submitter of this bug report) to indicate the solution I finally implemented. nautilus (ubuntu) can quickly redeem itself be fixing the regression. At that point, my "workaround " will be less relevant. -- 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/1178697 Title: Regression - Can't "Open with" on Folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1178697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1178697] Re: Regression - Can't "Open with" on Folders
*** This bug is a duplicate of bug 1026254 *** https://bugs.launchpad.net/bugs/1026254 That workaround, you mention, was anticipated and stated in my initial submission (at the top of this page). I guess I'm not using the term "regression" correctly. Is "degradation" more appropriate? What word means: "a loss of previously achieved functionality, optimization, or convenience"? Upstream design decisions, are no less subject to scrutiny than regressions. Both are legitimate reasons to submit a bug report. No matter what we call these things, the fact remains that a "feature that was achieved" is now missing from Nautilus. -- 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/1178697 Title: Regression - Can't "Open with" on Folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1178697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1178697] Re: Regression - Can't "Open with" on Folders
*** This bug is a duplicate of bug 1026254 *** https://bugs.launchpad.net/bugs/1026254 I trust you guys will make the best decision. I've done my best to advocate the usefulness of this feature. The main thing I will tell you, is that after you've discovered this feature, you can't go back. My own philosophy on software advancement places priority on two (potentially mutually exclusive) priorities: 1) For the sake of intuitiveness, always provide a contextual menu for each element graphically displayed. Doing so, allows the user to answers the question: "What are all the things I do with this thing?". Another way of saying this is: "Place functionality near as possible to the graphical representation of the thing that the functionality is about". Doing this is most intuitive, and will eliminate mouse travel. 2) Always strive to eliminate the number of steps required to achieve a task, and do this in a manner that does not compromise the intuitiveness (the obviousness) of how to perform that task. In this use case, we have user browsing through their file system with Nautilus. They come across a folder containing a hierarchy of music files. The user decides he would like to recursively enqueue this folder's files into his favorite music player. Due to principle #1, the most intuitive way to do this (giving context and nearness) is to place an option in the context menu that will allow him to recursively enqueue this folder into the application of his choice. This method also fulfills principle #2, because it eliminates these 3 steps: (1) Launch an application. (2) Position the window of that application so that is not on top of the Nautilus window (3) Drag the folder from the Nautilus window into the other application's window. Even a new user, could easily discover the usefulness of this feature, due to intuitiveness of context menus, which always answer the question "What can I do with this thing"? And, any user who has previously discovered this, will prefer it in this exact use case scenario. Additional use cases this serves: - Open folder with k4dirstat, to see what within that folder is taking up the most space on your hard drive - Enqueue Folder into VLC to watch multiple music videos one after the other. Any application that can use a folder as a launching input benefits from this previously achieve (but now missing) feature. -- 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/1178697 Title: Regression - Can't "Open with" on Folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1178697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back
I've done my best to advocate the usefulness of this feature. The main thing I will tell you, is that after you've discovered this feature, you can't go back. My own philosophy on software advancement places priority on two (potentially mutually exclusive) priorities: 1) For the sake of intuitiveness, always provide a contextual menu for each element graphically displayed. Doing so, allows the user to answers the question: "What are all the things I do with this thing?". Another way of saying this is: "Place functionality near as possible to the graphical representation of the thing that the functionality is about". Doing this is most intuitive, and will eliminate mouse travel. 2) Always strive to eliminate the number of steps required to achieve a task, and do this in a manner that does not compromise the intuitiveness (the obviousness) of how to perform that task. In this use case, we have user browsing through their file system with Nautilus. They come across a folder containing a hierarchy of music files. The user decides he would like to recursively enqueue this folder's files into his favorite music player. Due to principle #1, the most intuitive way to do this (giving context and nearness) is to place an option in the context menu that will allow him to recursively enqueue this folder into the application of his choice. This method also fulfills principle #2, because it eliminates these 3 steps: (1) Launch an application. (2) Position the window of that application so that is not on top of the Nautilus window (3) Drag the folder from the Nautilus window into the other application's window. Even a new user, could easily discover the usefulness of this feature, due to intuitiveness of context menus, which always answer the question "What can I do with this thing"? And, any user who has previously discovered this, will prefer it in this exact use case scenario. Additional use cases this serves: - Open folder with k4dirstat, to see what within that folder is taking up the most space on your hard drive - Enqueue Folder into VLC to watch multiple music videos one after the other. Any application that can use a folder as a launching input benefits from this previously achieve (but now missing) feature. -- 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/1026254 Title: Open with on folders was removed, Ubuntu should consider patching back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1026254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back
This concept is the graphical representation of the "piping" which has made the linux command line so powerful. I'd love to see this same power at the GUI level. -- 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/1026254 Title: Open with on folders was removed, Ubuntu should consider patching back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1026254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1272435] [NEW] Add "show in folder" to context menu of file found by Search
Public bug reported: After locating a file using Nautilus's search feature, I'm always wanting to know this question: Where is this file that Nautilus has found for me? When searching for a file, I'm not just trying to find that file, I'm also trying to discover the path that the file is located at (for future reference). I may decide to move that file to another location, if it is not where I want it to be. The fact that I've had to do a search for this file, gives great likelihood to the fact that (in addition to finding the file) I'm wanting to also know WHERE it is. Many file manager's search results, alone, do not answer this relevant question. You may say, why don't you just click "Properties", from the context menu. The problem with this approach, is that, although the dialog attempts to indicate the file's location, instead, it only shows the first portion of the path-location, cropping off the right portion of the path in a manner where the entire path cannot be seen. The best approach I've seen for this, in other applications, is to add "Show in Folder" to the search-result's context-menu, which opens the folder that contains the file and add focus to that file within its folder. With this one step, now the user has achieved multiple objectives: 1) He now knows where the file is, in the context of his file system 2) He is in a perfect position to decide if he wants to move this file elsewhere. There may not be an immediate demand for this feature, but once implemented, I sure that it will become appreciated, relied upon, and expected for future generations. I hope to one day see it as a standard option in all file search utilities. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.8.2-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 24 11:25:42 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-07 (109 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-01-08 (15 days ago) ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1272435 Title: Add "show in folder" to context menu of file found by Search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1272435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1272446] [NEW] File Properties - Location Cannot Be Seen in its Entirety
Public bug reported: The locations of files are ellipsified (and therefore "right-cropped") when viewing the properties of a file. To see this bug, do the following. 1) Open Nautilus 2) Navigate to a file location whose entire path-location is more than 26 characters in length. 3) Right-Click the file, and go to "Properties" 4) Under the "Basic" tab, see the "Location:" field. Now, notice that it is impossible to see the file's location in its entirety! This bug is especially frustrating, after performing a search for a file, because the search results offer no indication of that file's actual path-location, and going to properties of the file (as a search result) only shows the first half its path (making this information effectively useless). Additionally, when I'm looking for this information, I'm typically wanting to copy it to the clipboard. Please ease this task as much as possible. This would be an excellent location to add a small icon button tool-tipped "Copy Location to Clipboard". This suggestion caters to power users without taking anything away from beginners. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.8.2-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 24 11:32:58 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-07 (109 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-01-08 (15 days ago) ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1272446 Title: File Properties - Location Cannot Be Seen in its Entirety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1272446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1272435] Re: Add "show in folder" to context menu of file found by Search
*** This bug is a duplicate of bug 70230 *** https://bugs.launchpad.net/bugs/70230 Please note, I've submitted the properties bug as a separate issue here: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1272446 -- 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/1272435 Title: Add "show in folder" to context menu of file found by Search To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1272435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back
@Sebastien I think all can intelligibly agree that the only reason a context menu could be considered non-intuitive is due to the fact that it often requires a right-click, instead of a left-click. The studies you reference do not address the idea of making a normal left-click produce context menus (which could be used in touch interfaces as well). In situations where the left-click produces the context-menu, even the newest users will find it incredibly intuitive. Right-click-context-menus, are a very small price in intuitiveness for the benefits of always being able to answer the question: "What can I do with this thing"? If I called the shots at Ubuntu, a lot more would be context-menu-driven. To address the non-intuitiveness of right-clicking. You could remind the new user each session (until they disable the notification) the following: "If you don't know what something is, or what you can do with it: RIGHT- CLICK it" Or, another idea is, by default, make *left-clicks* display context menus, and give advanced users the ability move that feature to the right-click menu. Now you have perfect intuitiveness right off the bat, and users can take off their training wheels at any point. This is huge idea for User Friendliness. One day someone is going to get this right. It just makes too much sense: "Show me what I can do with what I'm clicking on". Its that simple. Every UI should keep this concept in mind during design and upgrade. That's my opinion. -- 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/1026254 Title: Open with on folders was removed, Ubuntu should consider patching back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1026254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back
You make a good point about the confusion that can come from too many options being in a context-menu. This can be addressed, however, by putting the numerous and rarely used option under one parent-option labeled "Advanced". -- 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/1026254 Title: Open with on folders was removed, Ubuntu should consider patching back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1026254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1026254] Re: Open with on folders was removed, Ubuntu should consider patching back
Sebastien, show them this: http://www.youtube.com/watch?v=fQhihnb2PV0 When seeing these compared side by side, it may influence their decision for the better. -- 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/1026254 Title: Open with on folders was removed, Ubuntu should consider patching back To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1026254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1292041] Re: Lockscreen doesn't turn off the screen
Maybe upon lock, you can take note of the user's settings and the issue this command after a time out occurs: xset dpms forceoff -- 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/1292041 Title: Lockscreen doesn't turn off the screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1306363] [NEW] Session-Saver Plugin Missing from gedit-plugins
Public bug reported: I open a lot of tabs in gedit, so saving each one of them is cumbersome if I need to reboot or want to continue a project the next day. The session-saver plugin addresses this need, but no longer seems to be included in the gedit-plugins package in Ubuntu 14.04. How can we get that added back? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit-plugins 3.10.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 10 23:49:58 2014 InstallationDate: Installed on 2014-04-03 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140402) SourcePackage: gedit-plugins UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit-plugins (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-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1306363 Title: Session-Saver Plugin Missing from gedit-plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit-plugins/+bug/1306363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1542489] [NEW] New Gedit Can't Show Menu in Title Bar
Public bug reported: Take a look at this screen shot: http://neartalk.com/ss/Gedit-No-Menu.png I like for application menus to show in the Title Bar (not at the top- panel). However, in the new Gedit GUI, the menu is inaccessible if your desktop preference is to show menus in title bar. Unless this changes, I won't use gedit anymore because my preference of showing menus in title bars outweighs my desire to use gedit. Perhaps Ubuntu should consider using Geany as the default text-editor or leafpad. It doesn't make sense for gedit to remain the default text-editor if it cannot play nice with Unity's Desktop-Level menu settings. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 5 15:13:29 2016 InstallationDate: Installed on 2015-10-28 (100 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: Upgraded to xenial on 2016-02-05 (0 days ago) ** Affects: unity Importance: Undecided Status: New ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Also affects: unity Importance: Undecided Status: New ** Description changed: Take a look at this screen shot: http://neartalk.com/ss/Gedit-No-Menu.png I like for application menus to show in the Title Bar (not at the top- panel). However, in the new Gedit GUI, the menu is inaccessible if your desktop preference is to show menus in title bar. Unless this changes, I won't use gedit anymore because my preference of showing menus in title bars outweighs my desire to use gedit. Perhaps - Ubuntu should consider using Geany as the default text-editor or leaf. + Ubuntu should consider using Geany as the default text-editor or + leafpad. It doesn't make sense for gedit to remain the default text-editor if it cannot play nice with Unity's Desktop-Level menu settings. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 5 15:13:29 2016 InstallationDate: Installed on 2015-10-28 (100 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: Upgraded to xenial on 2016-02-05 (0 days ago) -- 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/1542489 Title: New Gedit Can't Show Menu in Title Bar To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1542489/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1542489] Re: New Gedit Can't Show Menu in Title Bar
For now, here's a work-around that seems to work like gedit did before the gui upgrade: sudo apt-get install pluma Pluma seems just like the old gedit, perhaps it is some fork? -- 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/1542489 Title: New Gedit Can't Show Menu in Title Bar To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1542489/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1542489] Re: New Gedit Can't Show Menu in Title Bar
** Description changed: Take a look at this screen shot: http://neartalk.com/ss/Gedit-No-Menu.png I like for application menus to show in the Title Bar (not at the top- panel). However, in the new Gedit GUI, the menu is inaccessible if your desktop preference is to show menus in title bar. Unless this changes, I won't use gedit anymore because my preference of showing menus in title bars outweighs my desire to use gedit. Perhaps - Ubuntu should consider using Geany as the default text-editor or - leafpad. + Ubuntu should consider using pluma as the default text-editor or geany. It doesn't make sense for gedit to remain the default text-editor if it cannot play nice with Unity's Desktop-Level menu settings. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 5 15:13:29 2016 InstallationDate: Installed on 2015-10-28 (100 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: Upgraded to xenial on 2016-02-05 (0 days ago) -- 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/1542489 Title: New Gedit Can't Show Menu in Title Bar To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1542489/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1527590] Re: gedit unusable when menu can't be displayed
Here's a screen-shot of the issue where the typical menu cannot be shown in the title-bar, because gedit is currently utilizing the title bar itself at the application-level (which is overriding the "desktop-environment-level): http://neartalk.com/ss/Gedit-No-Menu.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/1527590 Title: gedit unusable when menu can't be displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1527590/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1527590] Re: gedit unusable when menu can't be displayed
Temporarily, I'm using pluma instead of gedit as a work-around for the menu-not-displaying-in-title-bar-issue: sudo apt-get install pluma Pluma seems to be some previous fork of gedit, and looks like gedit did about two versions ago. Here's a screen shot of pluma, where you can see the correct behavior regarding the title-bar-menu: http://neartalk.com/ss/pluma.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/1527590 Title: gedit unusable when menu can't be displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1527590/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1545026] [NEW] Video Progress Too Subtle on Apple Movie Trailers
Public bug reported: Look where the red arrow is pointing in this screenshot: http://neartalk.com/ss/Totem.png This orange on orange it too subtle to indicate the video is 21 seconds along. I notices that this occurs on the Apple Movie Trailers inclued with Totem. Videos I play from the local file system are orange and white (clearly indicating progress). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: totem 3.18.1-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 12 08:57:50 2016 InstallationDate: Installed on 2016-02-10 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1545026 Title: Video Progress Too Subtle on Apple Movie Trailers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1545026/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1545026] Re: Video Progress Too Subtle on Apple Movie Trailers
** Description changed: Look where the red arrow is pointing in this screenshot: http://neartalk.com/ss/Totem.png This orange on orange it too subtle to indicate the video is 21 seconds - along. I notices that this occurs on the Apple Movie Trailers inclued + along. I noticed that this occurs on the Apple Movie Trailers included with Totem. Videos I play from the local file system are orange and white (clearly indicating progress). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: totem 3.18.1-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 12 08:57:50 2016 InstallationDate: Installed on 2016-02-10 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: totem 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 totem in Ubuntu. https://bugs.launchpad.net/bugs/1545026 Title: Video Progress Too Subtle on Apple Movie Trailers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1545026/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1549250] [NEW] Numerous Empty Categories
Public bug reported: I suspect it is already known that many of the categories list no corresponding software. For example: http://i.imgur.com/Opx4o0a.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.91~git20160224.0779986-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 24 05:28:50 2016 InstallationDate: Installed on 2016-02-10 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1549250 Title: Numerous Empty Categories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1549250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1549250] Re: Numerous Empty Categories
Recent updates show no categories at all: http://neartalk.com/ss/2016-03-01_001_1830x1043.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1549250 Title: Numerous Empty Categories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1549250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1549250] Re: Numerous Empty Categories
Now the categories are back, but some are still empty. Here's an example of an empty one: http://neartalk.com/ss/2016-03-02_001_1200x800.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1549250 Title: Numerous Empty Categories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1549250/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1557981] [NEW] Selected-Tab Hard to Distinguish in Default Ambiance Theme
Public bug reported: The default Theme in Ubuntu 16.04 is called "Ambiance": http://neartalk.com/ss/2016-03-16_005_565x390.png When Gnome-System-Monitor is running under the Ambiance theme, you can barely distinguish which tab is selected: http://neartalk.com/ss/2016-03-16_003_679x497.png Compare this with the non-default theme called "Radiance", where the selected-tab (in Gnome-System-Monitor) is clearly distinguishable at a glance (without eye strain): http://neartalk.com/ss/2016-03-16_004_687x497.png Which package would be responsible for making the selected-tab more distinguishable to the eye in gnome-system-monitor under the default Ambiance theme? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-system-monitor 3.18.2-1 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 16 04:38:11 2016 InstallationDate: Installed on 2016-03-14 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: light-themes Importance: Undecided Status: New ** Affects: light-themes-colors Importance: Undecided Status: New ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Also affects: light-themes Importance: Undecided Status: New ** Also affects: light-themes-colors Importance: Undecided Status: New -- 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/1557981 Title: Selected-Tab Hard to Distinguish in Default Ambiance Theme To manage notifications about this bug go to: https://bugs.launchpad.net/light-themes/+bug/1557981/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1557981] Re: Selected-Tab Hard to Distinguish in Default Ambiance Theme
** Also affects: unity Importance: Undecided Status: New -- 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/1557981 Title: Selected-Tab Hard to Distinguish in Default Ambiance Theme To manage notifications about this bug go to: https://bugs.launchpad.net/light-themes/+bug/1557981/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1568056] [NEW] Official Package-Names Not Shown in Gnome-Software
Public bug reported: The names of a packages (as you would type them when installing via a command prompt) are not indicated in gnome-software. Even when I use gnome-software to locate a package, I still want to know the package's official Ubuntu name, because I usually want to add that package-name to an command install list (sudo apt-get install package1 package2 package3), so that I can install all my packages at once the next time I do a fresh install. That fact that gnome-software can locate packages for me is great. The fact that it doesn't reveal the official name of the packages is lacking (for me). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1~git20160331.78d1aab-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 8 12:18:43 2016 InstallationDate: Installed on 2016-03-14 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1568056 Title: Official Package-Names Not Shown in Gnome-Software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1568056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573206] Re: Ubuntu Software does not install third-party .deb packages
*** This bug is a duplicate of bug 1572871 *** https://bugs.launchpad.net/bugs/1572871 ** This bug has been marked a duplicate of bug 1572871 gnome-software (ubuntu-software) doesn't install third party applications -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1573206 Title: Ubuntu Software does not install third-party .deb packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1573206/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1572871] Re: gnome-software (ubuntu-software) doesn't install third party applications
In earlier versions of Ubuntu, I had no issue installing this deb: https://www.google.com/tools/dlpage/hangoutplugin I haven't yet figured out a way to do it in Ubuntu 16.04: http://askubuntu.com/questions/760305/how-to-install-google-hangouts-plugin-in-ubuntu-16-04 I really need this plug-in, because allows my to do all my phone calls at work via Gmail and my Laptop. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1572871 Title: gnome-software (ubuntu-software) doesn't install third party applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1572871/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1571904] Re: Google Chrome won't install from .deb - missing package
*** This bug is a duplicate of bug 1573206 *** https://bugs.launchpad.net/bugs/1573206 The same is true for this hangouts plugin I use in Firefox. It require this deb: https://www.google.com/tools/dlpage/hangoutplugin But, it won't install. Same is true for this deb: http://torrent-search.sourceforge.net/download -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1571904 Title: Google Chrome won't install from .deb - missing package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1571904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
