[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
As recommended by the Gnome-shell developers a bug upstream with Mutter is opened. https://gitlab.gnome.org/GNOME/mutter/-/issues/1356 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1356 https://gitlab.gnome.org/GNOME/mutter/-/issues/1356 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Also I'm happy to use a workaround. I'm just a bit disappointed that devilspie no longer works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Thank you for your further input Daniel. The issue is that the stable version of ChromisPOS that I'm using the source code was destroyed by a commit error. I'm working together with the developer providing resources to get the unstable version production ready but that is taking more time than I can afford to wait as gnome-shell's and Ubuntu's development is outpacing what the single developer for ChromisPOS can take on. I'll certainly subscribe to those bugs on remote support. I'll let Zoho also know about these two remote support bugs as they are also working on an internal fix to build into their Zoho Assist SAAS solution, maybe they can assist there too. > I suggest any software that wants a window A to reliably appear over window B > ... I'd prefer to have no dialog boxes at all popping up and have Window A modify itself. Then there is no reliance on the Window Manager at all. :D Thanks again for thinking along on this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Reported this Upstream under https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3011 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
This is interesting. When running gnome-shell in Wayland the window placement seems to be correct. I've been testing it a bit. Unfortunately Wayland doesn't allow for remote desktop access so I can't help my customers when something goes wrong. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Wish me luck, fingers crossed. I'm going to create the issue on Gnome's bug tracker now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
@Daniel van Vugt Thanks for your understanding and advice. Do you have any recommendations for an alternative window manager that is: - Officially Supported by Canonical under the support contract - Touchscreen Friendly - Secure - Has a sidebar on the left (the product I sell is designed around the Unity design) Gnome is supposed to be the de-facto standard Linux desktop for most distributions. I still don't understand why all these regression bugs are entering Gnome, and the Gnome developers are so hostile to listening to the users and use cases of their desktop. See the gitlab board you pointed me to where the dev, on the subject of the on screen keyboard, just says, nope, I designed it this way, not listening to reason of more than 30 people and then locks the ticket. Even you said "If that's true then this is not a bug." in regards to window placement. Which is just mind boggling, of course it's a bug when the window manager clearly prevents the end user from using the system. There also needs to be an easier way to report things upstream. At the moment everything has to be typed over into a new ticket from Launchpad to Github. Can't there just be some kind of export ticket to GitHub markup? Thanks again for any recommendations on Canonical supported Window Managers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
And the cashier side ** Attachment added: "Cashier side of the setup" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394700/+files/Bug1888098_opposingScreensCashier.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
And before anyone starts anything about freeloading. I donate several thousand euros per year and a lot of my time to open source projects. So, let's not go there. Once again thank you. I hope that it's much clearer now what is not working as expected in Ubuntu 20.04's iteration of Gnome Desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
So you can see what the system looks like when installed ** Attachment added: "Opposing Screens Customer" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394699/+files/Bug1888098_opposingScreensCashier.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Some more fun, the onscreen keyboard follows the misplaced dialog box to the non-touchable monitor. ** Attachment added: "Screen Keyboard opens on non touchable area" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394696/+files/Bug1888098_ScreenKeyboardOnNonTouchMonitor.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
And here is proof that there are no extensions enabled ** Attachment added: "No Extensions enabled" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394697/+files/Bug1888098_ProofAllExtensionsDisabled.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Here is an extra treat so you can see why block Caribou is very necessary and the gnome onscreen keyboard implementation makes the system completely unusable. ** Attachment added: "Extra treat why the block caribou extension was on." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394695/+files/Bug1888098_whyGnomeKeyboardIsOff.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Here is a photo so you can see that the Center New Window option does nothing. At least it stopped doing the Easter Egg of putting things halfway between two monitors that's a plus. :D ** Attachment added: "Photo Center new window doesn't do anything" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394694/+files/Bug1888098_CenterNewWindowIgnored.jpeg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Thanks for have a new look at this Oh and I forgot to mention this is with the option Center New Windows turned ON in Gnome Tweak Tool Which should theoretically do the same as the DCONF edit line, right? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Here is a photo so it's easier to understand what the issue is. ** Attachment added: "Photo of the issue faced" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394688/+files/2020-07-21_Bug%20-1888098_GnomeWindowPlacementBug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Removing the extensions has the same effect. Block Caribou 36 is necessary as the Point of Sale system (Open source) already has all the buttons and keyboard that are necessary for the use of the Point of Sale system. Yet it contains text entry fields which pop up the on-screen keyboard. There are more touchscreen applications that tablets, such as Kiosks and Point of Sale systems. "gsettings set org.gnome.mutter center-new-windows true" is an easter- egg joke, it puts the windows halfway between the two screens, then stacks them on top of each other. "I think this is probably occurring because the primary display is occupied by a window already. So any more new windows go to the next display that has empty space. If that's true then this is not a bug. And hopefully #3 is good enough." This is a serious bug as the screens are opposing one another. There are two different people with two different information goals looking at each screen. Both screens are occupied by full screen windows. One is the point of sale interface for the cashier and the other is the customer display screen showing the products the customer is purchasing. The expected behavior is to put the window on the same monitor to where the button to open the new window has been pressed. I'll see if I can muster up some screenshots to make it more visual as to what is going on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] [NEW] Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Public bug reported: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
There is a workaround via xinput map-to-output "Weida Hi-Tech CoolTouch® System" eDP-1 There needs to be some kind of detection to do this automatically and create a systemD systemctl file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in GNOME Settings Daemon: Fix Released Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Trusty: Confirmed Status in unity-settings-daemon source package in Trusty: Fix Released Bug description: SRU Request: Laptops and all-in-one systems with touchscreens don't currently map the touch input device onto the internal display. As a result, when the screen changes (e.g. the main output is rotated or an external output is connected), the touch input device maps onto the entire screen, regardless of the only relevant area, thus making the touchscreen completely useless. [Impact] * The touchscreen becomes unusable if an external output is connected or if the main output is rotated. [Test Case] * Either plug in an external monitor or rotate the internal monitor - Expected: the touchscreen should respond to touch as usual. - Bad behavior: the touchscreen is unusable and responds by selecting areas other than the one the user actually selects. [Regression Potential] * Low, it only affects the main touchscreen (tablets or multiple touchscreens are not supported) and it only adds a feature that is currently missing. [Other Info] * N/A --- My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller])
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Here is the xinput list-props while the second screen (AOC) is disconnected Here the touch works as expected xinput list-props 11 Device 'Weida Hi-Tech CoolTouch® System': Device Enabled (169): 1 Coordinate Transformation Matrix (171): 0.50, 0.00, 0.50, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Calibration Matrix (308): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Calibration Matrix Default (309): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Send Events Modes Available (291): 1, 0 libinput Send Events Mode Enabled (292):0, 0 libinput Send Events Mode Enabled Default (293):0, 0 Device Node (294): "/dev/input/event4" Device Product ID (295):9589, 49920 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in GNOME Settings Daemon: Fix Released Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Trusty: Confirmed Status in unity-settings-daemon source package in Trusty: Fix Released Bug description: SRU Request: Laptops and all-in-one systems with touchscreens don't currently map the touch input device onto the internal display. As a result, when the screen changes (e.g. the main output is rotated or an external output is connected), the touch input device maps onto the entire screen, regardless of the only relevant area, thus making the touchscreen completely useless. [Impact] * The touchscreen becomes unusable if an external output is connected or if the main output is rotated. [Test Case] * Either plug in an external monitor or rotate the internal monitor - Expected: the touchscreen should respond to touch as usual. - Bad behavior: the touchscreen is unusable and responds by selecting areas other than the one the user actually selects. [Regression Potential] * Low, it only affects the main touchscreen (tablets or multiple touchscreens are not supported) and it only adds a feature that is currently missing. [Other Info] * N/A --- My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
There is a regression of this bug in Ubuntu 20.04 using the default Gnome desktop Setup is a Shuttle POS P511 using a Weida CoolTouch controller with driver integrated into the Linux kernel Second screen is a AOC USB-3.1 Display Link monitor without display capabilities only (no touch). When the AOC screen is disconnected the touch works normally. When the AOC screen is connected the touch is out of sync and touches over both screens from the Shutlle/Weida screen. Here is xinput list-props with both screens connected. xinput list-props 11 Device 'Weida Hi-Tech CoolTouch® System': Device Enabled (169): 1 Coordinate Transformation Matrix (171): 0.50, 0.00, 0.50, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Calibration Matrix (308): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Calibration Matrix Default (309): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Send Events Modes Available (291): 1, 0 libinput Send Events Mode Enabled (292):0, 0 libinput Send Events Mode Enabled Default (293):0, 0 Device Node (294): "/dev/input/event4" Device Product ID (295):9589, 49920 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in GNOME Settings Daemon: Fix Released Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Trusty: Confirmed Status in unity-settings-daemon source package in Trusty: Fix Released Bug description: SRU Request: Laptops and all-in-one systems with touchscreens don't currently map the touch input device onto the internal display. As a result, when the screen changes (e.g. the main output is rotated or an external output is connected), the touch input device maps onto the entire screen, regardless of the only relevant area, thus making the touchscreen completely useless. [Impact] * The touchscreen becomes unusable if an external output is connected or if the main output is rotated. [Test Case] * Either plug in an external monitor or rotate the internal monitor - Expected: the touchscreen should respond to touch as usual. - Bad behavior: the touchscreen is unusable and responds by selecting areas other than the one the user actually selects. [Regression Potential] * Low, it only affects the main touchscreen (tablets or multiple touchscreens are not supported) and it only adds a feature that is currently missing. [Other Info] * N/A --- My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins:
[Desktop-packages] [Bug 1858860] Re: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
Done https://github.com/storaged-project/udisks/issues/723 ** Bug watch added: github.com/storaged-project/udisks/issues #723 https://github.com/storaged-project/udisks/issues/723 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1858860 Title: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive Status in gnome-disk-utility package in Ubuntu: New Bug description: Use case: As a user of hot swap-able SATA disks using a Harddrive Riser over eSATA. I need a safe, easy and convenient way to remove the hot swap-able SATA disk without rebooting and without having to go to the command line. When attempting to eject an harddisk or a solid state disk using the eject button in "Gnome Disk Utility" it issues the 'eject' command which results in an IOCTL error. The correct commands the eject button in the GUI should issue to eject a SATA HDD or SSD are: # where X is the drive letter of the drive being worked with # -Y Put drive to sleep sudo hdparm -Y /dev/sdX # remove the device from the kernel sudo sh -c 'echo 1 > /sys/block/sdX/device/delete' Please see the screen shots for the error. This should be an easy fix (20 minutes) for someone who is good a programmer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 21:07:32 2020 InstallationDate: Installed on 2018-11-11 (423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858860] Re: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
The Source code file location where this happens I'm pretty sure is here: /src/disks/gduwindow.c /* */ static void eject_cb (UDisksDrive *drive, GAsyncResult *res, gpointer user_data) { GduWindow *window = GDU_WINDOW (user_data); GError *error; error = NULL; if (!udisks_drive_call_eject_finish (drive, res, )) { gdu_utils_show_error (GTK_WINDOW (window), _("Error ejecting media"), error); g_error_free (error); } g_object_unref (window); } static void eject_ensure_unused_cb (GduWindow *window, GAsyncResult *res, gpointer user_data) { UDisksObject *object = UDISKS_OBJECT (user_data); if (gdu_window_ensure_unused_finish (window, res, NULL)) { UDisksDrive *drive = udisks_object_peek_drive (object); udisks_drive_call_eject (drive, g_variant_new ("a{sv}", NULL), /* options */ NULL, /* cancellable */ (GAsyncReadyCallback) eject_cb, g_object_ref (window)); } g_object_unref (object); } static void on_devtab_drive_eject_button_clicked (GtkButton *button, gpointer user_data) { GduWindow *window = GDU_WINDOW (user_data); gdu_window_ensure_unused (window, window->current_object, (GAsyncReadyCallback) eject_ensure_unused_cb, NULL, /* GCancellable */ g_object_ref (window->current_object)); } /* */ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1858860 Title: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive Status in gnome-disk-utility package in Ubuntu: New Bug description: Use case: As a user of hot swap-able SATA disks using a Harddrive Riser over eSATA. I need a safe, easy and convenient way to remove the hot swap-able SATA disk without rebooting and without having to go to the command line. When attempting to eject an harddisk or a solid state disk using the eject button in "Gnome Disk Utility" it issues the 'eject' command which results in an IOCTL error. The correct commands the eject button in the GUI should issue to eject a SATA HDD or SSD are: # where X is the drive letter of the drive being worked with # -Y Put drive to sleep sudo hdparm -Y /dev/sdX # remove the device from the kernel sudo sh -c 'echo 1 > /sys/block/sdX/device/delete' Please see the screen shots for the error. This should be an easy fix (20 minutes) for someone who is good a programmer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 21:07:32 2020 InstallationDate: Installed on 2018-11-11 (423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858860] Re: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
Translation of the Error message to English: Removal of the medium has failed Error ejecting /dev/sdi: Command-line `eject"/dev/sdi"' exited with a non-zero status 1: eject: could not eject, last error: Incorrect ioctl() for device (udisks-error-quark, 0) So you can see in the error message that the incorrect command was used for the type of drive. ** Attachment added: "The Error in Dutch" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+attachment/5318663/+files/2020-01-08%282%29EjectSATAHDD_wrongCommand.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1858860 Title: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive Status in gnome-disk-utility package in Ubuntu: New Bug description: Use case: As a user of hot swap-able SATA disks using a Harddrive Riser over eSATA. I need a safe, easy and convenient way to remove the hot swap-able SATA disk without rebooting and without having to go to the command line. When attempting to eject an harddisk or a solid state disk using the eject button in "Gnome Disk Utility" it issues the 'eject' command which results in an IOCTL error. The correct commands the eject button in the GUI should issue to eject a SATA HDD or SSD are: # where X is the drive letter of the drive being worked with # -Y Put drive to sleep sudo hdparm -Y /dev/sdX # remove the device from the kernel sudo sh -c 'echo 1 > /sys/block/sdX/device/delete' Please see the screen shots for the error. This should be an easy fix (20 minutes) for someone who is good a programmer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 21:07:32 2020 InstallationDate: Installed on 2018-11-11 (423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858860] [NEW] Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
Public bug reported: Use case: As a user of hot swap-able SATA disks using a Harddrive Riser over eSATA. I need a safe, easy and convenient way to remove the hot swap-able SATA disk without rebooting and without having to go to the command line. When attempting to eject an harddisk or a solid state disk using the eject button in "Gnome Disk Utility" it issues the 'eject' command which results in an IOCTL error. The correct commands the eject button in the GUI should issue to eject a SATA HDD or SSD are: # where X is the drive letter of the drive being worked with # -Y Put drive to sleep sudo hdparm -Y /dev/sdX # remove the device from the kernel sudo sh -c 'echo 1 > /sys/block/sdX/device/delete' Please see the screen shots for the error. This should be an easy fix (20 minutes) for someone who is good a programmer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 21:07:32 2020 InstallationDate: Installed on 2018-11-11 (423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "The Eject Button in Gnome Disk Utility" https://bugs.launchpad.net/bugs/1858860/+attachment/5318659/+files/2020-01-08%281%29EjectSATADriveButton.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1858860 Title: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive Status in gnome-disk-utility package in Ubuntu: New Bug description: Use case: As a user of hot swap-able SATA disks using a Harddrive Riser over eSATA. I need a safe, easy and convenient way to remove the hot swap-able SATA disk without rebooting and without having to go to the command line. When attempting to eject an harddisk or a solid state disk using the eject button in "Gnome Disk Utility" it issues the 'eject' command which results in an IOCTL error. The correct commands the eject button in the GUI should issue to eject a SATA HDD or SSD are: # where X is the drive letter of the drive being worked with # -Y Put drive to sleep sudo hdparm -Y /dev/sdX # remove the device from the kernel sudo sh -c 'echo 1 > /sys/block/sdX/device/delete' Please see the screen shots for the error. This should be an easy fix (20 minutes) for someone who is good a programmer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 21:07:32 2020 InstallationDate: Installed on 2018-11-11 (423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714804] Re: Aardvark Daily: Indicator-Multiload doesn't show full-width
I can confirm that Martin Vysny's solution/workaround works in Ubuntu 18.04.1LTS. (this was not the case in Ubuntu Alpha when I reported this bug) Please note that you have to reboot (or log-off and logon again) for the system-monitor to show up in the gnome-tweaks extensions page. Time to say goodbye to indicator-multiload and thank Michael Hofmann for the years of enjoyment we had from his software indicator-multiload. Thank you Michael -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1714804 Title: Aardvark Daily: Indicator-Multiload doesn't show full-width Status in System Load Indicator: New Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: In Ubuntu Indicator-Multiload is an essential application as it shows that computer is actually doing something even when an application is giving no feedback for a long period of time. Conky is not an option as it gets hidden behind full screen applications. Unfortunately the move to Gnome has broken indicator-multiload so that it can't show all of the indicators. CPU Memory Network Swap System Load Disk I've tried the developers suggestion of installing TopIcons and TopIconsplus to no avail. I see that Ubuntu App-Indicator is also installed so maybe app-indicator extension is broken in Gnome and not indicator-multiload. Anyway steps to reproduce: Install Ubuntu 16.04.x LTS Install indicator-multiload Open the settings of indicator-multiload by clicking on it and choosing settings Click all of the sources on You will now see 6 panels showing the earlier described graphs. Now install Ubuntu 17.10 Daily Install indicator-multiload Mouse over the top bar to faintly get an idea where indicator-multiload is running click on it and open the settings Click all of the sources on You will now see tiny faint lines which give no clue whatsoever as to what is going on with the machine. Please fix either app-indicator extension or indicator-multiload to work with Gnome. Thanks ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: indicator-multiload 0.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 3 19:12:33 2017 InstallationDate: Installed on 2017-09-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: indicator-multiload UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/1714804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
So here is the upstream answer: Window decorations are client-side on wayland, that means they are just another part of the application window the same way as the products you are viewing. We cannot tell what parts of the window are decorations, or whether there are in fact any decorations at all. It's entirely up to applications to adjust to window state changes if they desire. (In the X11 session, there is a _GTK_HIDE_TITLEBAR_WHEN_MAXIMIZED hint that applications can set, and you'll find extensions that apply that to any windows. But X11 is a legacy technology at this point, and we won't add any features based on that.) As Ubuntu 18.04 is a LTS release still using X11 for compatibility can the Ubuntu project please add the _GTK_HIDE_TITLEBAR_WHEN_MAXIMIZED hint as a toggle? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce Start Ubuntu Login to Unity Choose logoff Choose Ubuntu (which should have the label Gnome-hell) Note this is the only way to get Gnome-hell to start, starting it directly just shows a black screen and dumps you back to the greeter. (already created a bug report for that) Open a program Choose the Maximize icon al the way over on the right (thanks Gnome-shell devs for causing more Mouse Arm for people with Hi-res screens, instead of just moving the mouse up to the top to click my button, I now have to move it all the way across the screen to the right) The window maximizes but not to full screen. I get a weird double bar, with the clock bar and the window title bar wasting valuable pixels. On my professional systems at work, this means I can display one less product on the screen, products being more important than the titel of the window. Please hide the window title when maximized. (or make it at least optional) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:53:59 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
BTW> Workaround to the buttons on the right (which only makes sense for right to left languages ) was to install Gnome-tweak tool. In Left to Right languages having the buttons on the left means less mouse travel on high res screens to click the button. This was just good well thought out and tested design. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce Start Ubuntu Login to Unity Choose logoff Choose Ubuntu (which should have the label Gnome-hell) Note this is the only way to get Gnome-hell to start, starting it directly just shows a black screen and dumps you back to the greeter. (already created a bug report for that) Open a program Choose the Maximize icon al the way over on the right (thanks Gnome-shell devs for causing more Mouse Arm for people with Hi-res screens, instead of just moving the mouse up to the top to click my button, I now have to move it all the way across the screen to the right) The window maximizes but not to full screen. I get a weird double bar, with the clock bar and the window title bar wasting valuable pixels. On my professional systems at work, this means I can display one less product on the screen, products being more important than the titel of the window. Please hide the window title when maximized. (or make it at least optional) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:53:59 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
Reported upstream to the Gnome-shell devs https://gitlab.gnome.org/GNOME/gnome-shell/issues/493 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps to reproduce Start Ubuntu Login to Unity Choose logoff Choose Ubuntu (which should have the label Gnome-hell) Note this is the only way to get Gnome-hell to start, starting it directly just shows a black screen and dumps you back to the greeter. (already created a bug report for that) Open a program Choose the Maximize icon al the way over on the right (thanks Gnome-shell devs for causing more Mouse Arm for people with Hi-res screens, instead of just moving the mouse up to the top to click my button, I now have to move it all the way across the screen to the right) The window maximizes but not to full screen. I get a weird double bar, with the clock bar and the window title bar wasting valuable pixels. On my professional systems at work, this means I can display one less product on the screen, products being more important than the titel of the window. Please hide the window title when maximized. (or make it at least optional) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:53:59 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698351] Re: Search in Nautilus Files does not allow sorting of results
Example of search query that Nautilus refuses to sort. ** Attachment added: "Example of where nautilus is not sorting" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1698351/+attachment/5176511/+files/Selectie_012.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1698351 Title: Search in Nautilus Files does not allow sorting of results Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: The version of nautilus/Files included with Ubuntu 17.04 no longer allows sorting of search results. Previously, sort was achieved by clicking on the column header titles. This no longer works. It represents a significant regression in the search feature. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1698351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787294] Re: ".ico" icon files are shown as random noise
Here is a PNG of the icon so you can see what it looks like if you are also on 18.04 with this bug. I used icotool -x pos.ico to extract the icons from the .ico file as PNGs ** Attachment added: "PNG version of the icon" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176039/+files/pos_5_48x48x8.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787294] Re: ".ico" icon files are shown as random noise
And interestingly enough. Nautilus also displays the preview of the file as noise. ** Attachment added: "Nautilus also shows the icon as noise." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176038/+files/Schermafdruk%20van%202018-08-16%2000-36-31.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787294] Re: ".ico" icon files are shown as random noise
Here is a screenshot of the icon in gnome-hell ** Attachment added: "Corrupted Icon" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176036/+files/Schermafdruk%20van%202018-08-16%2000-33-47.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787294] Re: ".ico" icon files are shown as random noise
And here is the actual .ico file ** Attachment added: "the pos.ico file referred to by the desktop file" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176037/+files/pos.ico -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787294] [NEW] ".ico" icon files are shown as random noise
Public bug reported: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
See here in this screenshot. The 50px are used for the Application which is much more important than gnome-shell. ** Attachment added: "Opera browser gets rid of the title bar when maximized." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+attachment/5176025/+files/Schermafdruk%20van%202018-08-16%2000-11-52.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce Start Ubuntu Login to Unity Choose logoff Choose Ubuntu (which should have the label Gnome-hell) Note this is the only way to get Gnome-hell to start, starting it directly just shows a black screen and dumps you back to the greeter. (already created a bug report for that) Open a program Choose the Maximize icon al the way over on the right (thanks Gnome-shell devs for causing more Mouse Arm for people with Hi-res screens, instead of just moving the mouse up to the top to click my button, I now have to move it all the way across the screen to the right) The window maximizes but not to full screen. I get a weird double bar, with the clock bar and the window title bar wasting valuable pixels. On my professional systems at work, this means I can display one less product on the screen, products being more important than the titel of the window. Please hide the window title when maximized. (or make it at least optional) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:53:59 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787288] Re: gnome-shell window title bar wastes space when maximized
See the screenshot 50px have been wasted here! On my 1280x1024 production screens for my business 50px is an extra line of text. Two if I use a smaller font. I noticed that the Opera browser has figured out a way around this and hides the unnecessary title bar when maximized. Maybe we can learn from Opera and make this behavior default? ** Attachment added: "50px wasted." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+attachment/5176024/+files/Schermafdruk%20van%202018-08-16%2000-07-34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce Start Ubuntu Login to Unity Choose logoff Choose Ubuntu (which should have the label Gnome-hell) Note this is the only way to get Gnome-hell to start, starting it directly just shows a black screen and dumps you back to the greeter. (already created a bug report for that) Open a program Choose the Maximize icon al the way over on the right (thanks Gnome-shell devs for causing more Mouse Arm for people with Hi-res screens, instead of just moving the mouse up to the top to click my button, I now have to move it all the way across the screen to the right) The window maximizes but not to full screen. I get a weird double bar, with the clock bar and the window title bar wasting valuable pixels. On my professional systems at work, this means I can display one less product on the screen, products being more important than the titel of the window. Please hide the window title when maximized. (or make it at least optional) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:53:59 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787288] [NEW] gnome-shell window title bar wastes space when maximized
Public bug reported: Steps to reproduce Start Ubuntu Login to Unity Choose logoff Choose Ubuntu (which should have the label Gnome-hell) Note this is the only way to get Gnome-hell to start, starting it directly just shows a black screen and dumps you back to the greeter. (already created a bug report for that) Open a program Choose the Maximize icon al the way over on the right (thanks Gnome-shell devs for causing more Mouse Arm for people with Hi-res screens, instead of just moving the mouse up to the top to click my button, I now have to move it all the way across the screen to the right) The window maximizes but not to full screen. I get a weird double bar, with the clock bar and the window title bar wasting valuable pixels. On my professional systems at work, this means I can display one less product on the screen, products being more important than the titel of the window. Please hide the window title when maximized. (or make it at least optional) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:53:59 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1787288 Title: gnome-shell window title bar wastes space when maximized Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce Start Ubuntu Login to Unity Choose logoff Choose Ubuntu (which should have the label Gnome-hell) Note this is the only way to get Gnome-hell to start, starting it directly just shows a black screen and dumps you back to the greeter. (already created a bug report for that) Open a program Choose the Maximize icon al the way over on the right (thanks Gnome-shell devs for causing more Mouse Arm for people with Hi-res screens, instead of just moving the mouse up to the top to click my button, I now have to move it all the way across the screen to the right) The window maximizes but not to full screen. I get a weird double bar, with the clock bar and the window title bar wasting valuable pixels. On my professional systems at work, this means I can display one less product on the screen, products being more important than the titel of the window. Please hide the window title when maximized. (or make it at least optional) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:53:59 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787282] [NEW] Ubuntu 18.04.1 Nautilus can't sort search results by Name, Size, Type or Location by clicking on the column title
Public bug reported: Steps to reproduce Switch to LightDM Switch to Unity (gnome wouldn't let me log in so I was looking for the log file) Open Nautilus in the search bar type ".log" (without the quotes) All the log files in your home directory are shown Click on Name column nothing happens click on the Size column nothing happens Click on a folder in nautilus containing items Click on the Name column The column gets sorted by name Click on the size column the column gets sorted by size The behavior should be the same whether or not you have searched but it's not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Aug 15 22:52:39 2018 InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "screenshot of the area not sorting" https://bugs.launchpad.net/bugs/1787282/+attachment/5175959/+files/Selectie_012.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1787282 Title: Ubuntu 18.04.1 Nautilus can't sort search results by Name, Size, Type or Location by clicking on the column title Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce Switch to LightDM Switch to Unity (gnome wouldn't let me log in so I was looking for the log file) Open Nautilus in the search bar type ".log" (without the quotes) All the log files in your home directory are shown Click on Name column nothing happens click on the Size column nothing happens Click on a folder in nautilus containing items Click on the Name column The column gets sorted by name Click on the size column the column gets sorted by size The behavior should be the same whether or not you have searched but it's not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Aug 15 22:52:39 2018 InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1787282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778421] [NEW] Ubuntu 18.04 vino does not start up at boottime unable to login with gdm over vino
Public bug reported: == Release == Description:Ubuntu 18.04 LTS Release:18.04 Ubuntu Gnome desktop gdm login manager == Package version == vino: Geïnstalleerd: 3.22.0-3ubuntu1 Kandidaat: 3.22.0-3ubuntu1 Versietabel: *** 3.22.0-3ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status == Expected occurrence == set up two users on the system Install vino Enable remote desktop sharing for both users Set a password (8 char wtf) reboot Open Remmina on another computer Set up the connection vnc over ssh double click the connection Remmina VNC shows the gdm login screen and allows me to choose a user Enter that users desktop do some work Choose Switch User Switch to the other user and use that desktop logoff the users show the gdm screen == What really happens == >From step double click the connection Remmina show a black screen, no gdm ss -lnt shows no services listening on port 5900 physically login behind the machine that is going to be placed remotely restart remmina am able to log in to the logged in desktop switch users vino sends a black screen from gdm log in physically to the 'remote' machine vino still sends a black screen reboot the computer more black screen in 16.04 I used X11vnc together with a systemctrl x11vnc.service file which worked fine. This is also broken in 18.04. Tried a vino.service file from one of the forums didn't work vino fails with vino.service - description about the service Loaded: loaded (/lib/systemd/system/vino.service; enabled; vendor preset: ena Active: failed (Result: exit-code) since Sun 2018-06-24 20:18:23 CEST; 26min Process: 1147 ExecStart=/usr/lib/vino/vino-server (code=exited, status=1/FAILU Main PID: 1147 (code=exited, status=1/FAILURE) jun 24 20:18:23 computer systemd[1]: Started description about the service jun 24 20:18:23 computer vino-server[1147]: Unable to init server: Kon nie jun 24 20:18:23 computer vino-server[1147]: Kan scherm ‘’ niet openen jun 24 20:18:23 computer vino-server[1147]: Voer ‘vino-server --help’ uit jun 24 20:18:23 computer systemd[1]: vino.service: Main process exited, co jun 24 20:18:23 computer systemd[1]: vino.service: Failed with result 'exi lines 1-12/12 (END) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 24 20:23:08 2018 InstallationDate: Installed on 2018-06-23 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vino (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1778421 Title: Ubuntu 18.04 vino does not start up at boottime unable to login with gdm over vino Status in vino package in Ubuntu: New Bug description: == Release == Description: Ubuntu 18.04 LTS Release: 18.04 Ubuntu Gnome desktop gdm login manager == Package version == vino: Geïnstalleerd: 3.22.0-3ubuntu1 Kandidaat: 3.22.0-3ubuntu1 Versietabel: *** 3.22.0-3ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status == Expected occurrence == set up two users on the system Install vino Enable remote desktop sharing for both users Set a password (8 char wtf) reboot Open Remmina on another computer Set up the connection vnc over ssh double click the connection Remmina VNC shows the gdm login screen and allows me to choose a user Enter that users desktop do some work Choose Switch User Switch to the other user and use that desktop logoff the users show the gdm screen == What really happens == From step double click the connection Remmina show a black screen, no gdm ss -lnt shows no services listening on port 5900 physically login behind the machine that is going to be placed remotely restart remmina am able to log in to the logged in desktop switch users vino sends a black screen from gdm log in physically to the 'remote' machine vino still sends a black screen reboot the computer more black screen in 16.04 I used X11vnc together with a systemctrl x11vnc.service file which worked fine. This is also broken in 18.04. Tried a vino.service file from one of the forums didn't work vino fails with vino.service - description about the service Loaded: loaded (/lib/systemd/system/vino.service; enabled; vendor preset: ena Active: failed
[Desktop-packages] [Bug 1192051] Re: plymouthd spinning at 100% CPU after I log in
Didn't help after all. Plymouth is still using 100% CPU on reboot. Now trying all the suggestions in https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1536771 Disabled plymouth in Grub and dpkg-reconfigured it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1192051 Title: plymouthd spinning at 100% CPU after I log in Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: plymouthd spinning at 100% CPU. Probably triggered by use of this PPA: https://launchpad.net/~mir-team/+archive/system-compositor-testing although that does not change Plymouth. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plymouth 0.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue Jun 18 15:06:38 2013 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationDate: Installed on 2013-06-11 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611) MachineType: LENOVO 4286CTO MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192051] Re: plymouthd spinning at 100% CPU after I log in
I found the conflict with the eGalax Touch Daemon driver. I moved the driver startup from /etc/init.d/eGtouch.sh to userspace as I don't need the touchscreen at login. The strange thing is I have 17 machines with this configuration and only one is exhibiting this behaviour with plymouthd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1192051 Title: plymouthd spinning at 100% CPU after I log in Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: plymouthd spinning at 100% CPU. Probably triggered by use of this PPA: https://launchpad.net/~mir-team/+archive/system-compositor-testing although that does not change Plymouth. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plymouth 0.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue Jun 18 15:06:38 2013 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationDate: Installed on 2013-06-11 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611) MachineType: LENOVO 4286CTO MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192051] Re: plymouthd spinning at 100% CPU after I log in
I've attached an apport report of the runaway process ** Attachment added: "apport.plymouth.b8ut5mm8.apport" https://bugs.launchpad.net/lightdm/+bug/1192051/+attachment/5103196/+files/apport.plymouth.b8ut5mm8.apport -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1192051 Title: plymouthd spinning at 100% CPU after I log in Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: plymouthd spinning at 100% CPU. Probably triggered by use of this PPA: https://launchpad.net/~mir-team/+archive/system-compositor-testing although that does not change Plymouth. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plymouth 0.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue Jun 18 15:06:38 2013 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationDate: Installed on 2013-06-11 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611) MachineType: LENOVO 4286CTO MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192051] Re: plymouthd spinning at 100% CPU after I log in
There is a regression of this bug in 16.04.4LTS Linux computer 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 388 root 20 0 201472 100776 8516 R 95,7 2,9 19:57.46 plymouthd ii liblightdm-gobject-1-0:amd64 1.18.3-0ubuntu1.1 amd64LightDM GObject client library ii lightdm 1.18.3-0ubuntu1.1 amd64Display Manager -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1192051 Title: plymouthd spinning at 100% CPU after I log in Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: plymouthd spinning at 100% CPU. Probably triggered by use of this PPA: https://launchpad.net/~mir-team/+archive/system-compositor-testing although that does not change Plymouth. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plymouth 0.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue Jun 18 15:06:38 2013 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationDate: Installed on 2013-06-11 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611) MachineType: LENOVO 4286CTO MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1192051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1677035] [NEW] GUI: SMART-information and selftests window unable to resize window to read text
Public bug reported: Steps to reproduce: * In the Gnome Disk Utility * Select any drive supporting SMART * click on the gear icon * Choose SMART Info and Selftests * Click on the dividing line between Attribute and Value * Try to drag left or right in order to be able to read the Attribute * Doesn't budge. * Try to grab the bottom right corner of the window to increase it's size so you can read the darn thing. * Doesn't budge. The window seems to be stuck at 950x500 pixels making the contents of the window unreadable in languages with long words like Dutch and German. Please let the user of the computer decide how large or small they want the window. There is no such thing as one-size-fits-all in computer graphical interfaces. Oh and see the screenshot for the example. 179 used-res...csk-total ? 181 program...unt-total ?? And before you say just mouse over. tried that get the message: "There is no description for Attribute 179" Thanks but just make the window resizeable please. Thanks! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-disk-utility 3.10.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-70.91~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-70-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 28 22:22:32 2017 InstallationDate: Installed on 2015-11-15 (498 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: "used-res...cks-total, program...unt-total. unreadable, thus unusable" https://bugs.launchpad.net/bugs/1677035/+attachment/4849231/+files/DisksSmartNotResizeable.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1677035 Title: GUI: SMART-information and selftests window unable to resize window to read text Status in gnome-disk-utility package in Ubuntu: New Bug description: Steps to reproduce: * In the Gnome Disk Utility * Select any drive supporting SMART * click on the gear icon * Choose SMART Info and Selftests * Click on the dividing line between Attribute and Value * Try to drag left or right in order to be able to read the Attribute * Doesn't budge. * Try to grab the bottom right corner of the window to increase it's size so you can read the darn thing. * Doesn't budge. The window seems to be stuck at 950x500 pixels making the contents of the window unreadable in languages with long words like Dutch and German. Please let the user of the computer decide how large or small they want the window. There is no such thing as one-size-fits-all in computer graphical interfaces. Oh and see the screenshot for the example. 179 used-res...csk-total ? 181 program...unt-total ?? And before you say just mouse over. tried that get the message: "There is no description for Attribute 179" Thanks but just make the window resizeable please. Thanks! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-disk-utility 3.10.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-70.91~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-70-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 28 22:22:32 2017 InstallationDate: Installed on 2015-11-15 (498 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1677035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551022] Re: mouse pointer leaves trail
Regression in 16.04.2 this bug has come back. Using Intel i915 driver on a Intel J3160 processor. Connection is dual monitor VGA + HDMI What do you need qua logging or actions to solve this issue? ** Attachment added: "Mouse Pointer Trails" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+attachment/4845654/+files/MousePointerTrails.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1551022 Title: mouse pointer leaves trail Status in xorg package in Ubuntu: Expired Bug description: In my desktop system Kubuntu 15.10 I have the integrated graphic card (Intel HD3000) and a discrete graphic card (Nvidia GTX 550). Some days ago I attached a monitor on the iGPU and enabled it, giving me a triple head system (two monitors on the Nvidia and one on the Intel). From that moment, the mouse pointer started to leave a trail when it pass over something that is animating. I'm using nouveau for the nvidia card. I tried to upgrade to Kubuntu 16.04, but it gives me the same glitch. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: 2016-02-24 01:06:09,804 DEBUG enabling apt cron job DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d] NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF116 [GeForce GTX 550 Ti] [19da:5194] InstallationDate: Installed on 2015-11-19 (106 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic root=UUID=679d8ad1-4664-4abd-a80a-3ac9339425bb ro quiet splash nomdmonddf nomdmonisw irqnodebug vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Tags: xenial ubuntu single-occurrence reproducible has-workaround Uname: Linux 4.4.0-10-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3707:bd07/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-V:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 738063] Re: gnome-keyring-daemon assertion failures when changing password remotely
Problem still exists in Trusty: Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: Gck: gck_module_new: assertion 'funcs != NULL' failed Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: module_instances: assertion 'module' failed Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: egg_error_message: assertion 'error' failed Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: couldn't find secret store module: (unknown) Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: lookup_login_keyring: assertion 'GCK_IS_SESSION (session)' failed Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: create_credential: assertion 'GCK_IS_SESSION (session)' failed Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: egg_error_message: assertion 'error' failed Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: couldn't create new login credential: (unknown) Dec 20 13:17:37 hostname passwd[23986]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/738063 Title: gnome-keyring-daemon assertion failures when changing password remotely Status in gnome-keyring package in Ubuntu: Expired Bug description: Binary package hint: gnome-keyring Changing password remotely results in the following assertion failures in auth.log: Mar 19 09:49:18 gx1 passwd[17883]: pam_unix(passwd:chauthtok): password changed for test123 Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: gp11_module_get_slots: assertion `data->funcs' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_session: assertion `slot' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_keyring: assertion `GP11_IS_SESSION (session)' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: create_credential: assertion `GP11_IS_SESSION (session)' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: egg_error_message: assertion `error' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: couldn't create new login credential: (unknown) Mar 19 09:49:18 gx1 passwd[17883]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match. Mar 19 09:49:18 gx1 passwd[17883]: Passphrase file wrapped Mar 19 09:55:57 gx1 passwd[18305]: pam_unix(passwd:chauthtok): password changed for test124 Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: gp11_module_get_slots: assertion `data->funcs' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_session: assertion `slot' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_keyring: assertion `GP11_IS_SESSION (session)' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: create_credential: assertion `GP11_IS_SESSION (session)' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: egg_error_message: assertion `error' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: couldn't create new login credential: (unknown) Mar 19 09:55:57 gx1 passwd[18305]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match. Mar 19 09:55:57 gx1 passwd[18305]: Passphrase file wrapped To reproduce: sudo adduser --encrypt-home test123 sudo adduser test124 ssh in as both users created above, run passwd and change the password. Have not tested behaviour without ecryptfs-utils installed, but it should be unrelated since both encrypted and unencrypted homedirs behaved the same. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-keyring 2.92.92.is.2.30.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-generic i686 Architecture: i386 CheckboxSubmission: bc3a49cd6e76f0d54c8965120b490eef CheckboxSystem: abf102d6ef41328208f5c1554651535a Date: Sat Mar 19 09:51:57 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/738063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1392064] Re: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf
Solved by using the proprietary non-free driver from eGalax http://www.eeti.com.tw/drivers_Linux.html OpenSource and multiple displays where one is a touchscreen still don't get along very well yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1392064 Title: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf Status in lightdm package in Ubuntu: Expired Bug description: Setup: Ubuntu 14.04.1LTS IIyama 19" Pro-Lite Touchscreen Dell 17" regular monitor Due to another bug in the detection of input devices I had to write a script to tell Ubuntu which screen to use the touch from the touchscreen. so I put the following two entries into a basic bash script based on xinput list and xrandr -q #!/bin/bash xinput map-to-output 12 DVI-I-1 xrandr --output DVI-I-1 --primary = I added this script to /usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf and the contents look like this. [SeatDefaults] greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh session-setup-script=/usr/local/bin/iiyama-touchscreen.sh When I start a user session the touchscreen is calibrated and works normally with the touch happening on the touchscreen. As soon as I logoff into LightDM the touch calibration is off moving the pointer a logarithmic distance from the left of the touchscreen. As soon as I log in again, no problems, touch works great, log back out into the lightDM greeter and boom touch is all crazy. Can lightdm please detect that a touchscreen can only accept touch input and output to the touchscreen device?? Or at least have lightdm actually run the script when given? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 12 22:11:38 2014 InstallationDate: Installed on 2014-11-03 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmConfig: [SeatDefaults] autologin-user=boerske SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1392064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1377857] Re: touchscreen calibration not saved in ubuntu 14.04
I have now 3 IIyama touchscreens with eGalax touchpanels the: 2x IIyama T1931-SR-b (5 wire resistive) IIyama T1931-SAW-b (Acousic Wave) The 1st screen (SR) worked out of the box and retained it's calibration but needed a startup script and udev rule # xinput list # to find the map-to-output value # xrandr # to find the output plug name xinput map-to-output 9 DVI-I-1 The 2nd screen (SR) worked orignally out of the box and after a week it lost it's calibration and was impossible to get calibrated again. As you touch closer to the top right corner the mouse moves more to the left of your finger) The 3rd screen (SAW) doesn't react to touch at all and I'm still fighting with it to get it to work. There needs to be a better way for evdev to save and store the configuration for touchscreens. Especially for screens so well documented like the eGalax touchscreens. # Full documentation can be found on the website of eGalax http://www.eeti.com.tw/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1377857 Title: touchscreen calibration not saved in ubuntu 14.04 Status in xserver-xorg-input-evdev package in Ubuntu: Confirmed Bug description: I have a touchscreen IIYAMA and I'm using Ubuntu 14.04 LTS. I try to configure my touchscreen by Calibrate touchscreen. Later, I save new configuration in : /usr/share/X11/xorg.conf.d/99-calibration.conf I show you one of multiples examples that i used Section InputClass Identifier calibration MatchProductNexio Touch Device(HS) Nexio HID Multi-Touch ATI0420-06 Pen Option Calibration 14533 4620 14533 4620 Option SwapAxes 1 EndSection I am trying multiples options: change SwapAxes values, change Calibration values.. Finally i restart xsever : restart lightdm Ubuntu not save any change. Thanks for all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1377857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1377857] Re: touchscreen calibration not saved in ubuntu 14.04
** Attachment added: here is an output from /proc/bus/input/devices https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1377857/+attachment/4278686/+files/IIyama-T1931SAW_egalax_notes.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1377857 Title: touchscreen calibration not saved in ubuntu 14.04 Status in xserver-xorg-input-evdev package in Ubuntu: Confirmed Bug description: I have a touchscreen IIYAMA and I'm using Ubuntu 14.04 LTS. I try to configure my touchscreen by Calibrate touchscreen. Later, I save new configuration in : /usr/share/X11/xorg.conf.d/99-calibration.conf I show you one of multiples examples that i used Section InputClass Identifier calibration MatchProductNexio Touch Device(HS) Nexio HID Multi-Touch ATI0420-06 Pen Option Calibration 14533 4620 14533 4620 Option SwapAxes 1 EndSection I am trying multiples options: change SwapAxes values, change Calibration values.. Finally i restart xsever : restart lightdm Ubuntu not save any change. Thanks for all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1377857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1392064] [NEW] lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf
Public bug reported: Setup: Ubuntu 14.04.1LTS IIyama 19 Pro-Lite Touchscreen Dell 17 regular monitor Due to another bug in the detection of input devices I had to write a script to tell Ubuntu which screen to use the touch from the touchscreen. so I put the following two entries into a basic bash script based on xinput list and xrandr -q #!/bin/bash xinput map-to-output 12 DVI-I-1 xrandr --output DVI-I-1 --primary = I added this script to /usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf and the contents look like this. [SeatDefaults] greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh session-setup-script=/usr/local/bin/iiyama-touchscreen.sh When I start a user session the touchscreen is calibrated and works normally with the touch happening on the touchscreen. As soon as I logoff into LightDM the touch calibration is off moving the pointer a logarithmic distance from the left of the touchscreen. As soon as I log in again, no problems, touch works great, log back out into the lightDM greeter and boom touch is all crazy. Can lightdm please detect that a touchscreen can only accept touch input and output to the touchscreen device?? Or at least have lightdm actually run the script when given? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 12 22:11:38 2014 InstallationDate: Installed on 2014-11-03 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) LightdmConfig: [SeatDefaults] autologin-user=boerske SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1392064 Title: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf Status in “lightdm” package in Ubuntu: New Bug description: Setup: Ubuntu 14.04.1LTS IIyama 19 Pro-Lite Touchscreen Dell 17 regular monitor Due to another bug in the detection of input devices I had to write a script to tell Ubuntu which screen to use the touch from the touchscreen. so I put the following two entries into a basic bash script based on xinput list and xrandr -q #!/bin/bash xinput map-to-output 12 DVI-I-1 xrandr --output DVI-I-1 --primary = I added this script to /usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf and the contents look like this. [SeatDefaults] greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh session-setup-script=/usr/local/bin/iiyama-touchscreen.sh When I start a user session the touchscreen is calibrated and works normally with the touch happening on the touchscreen. As soon as I logoff into LightDM the touch calibration is off moving the pointer a logarithmic distance from the left of the touchscreen. As soon as I log in again, no problems, touch works great, log back out into the lightDM greeter and boom touch is all crazy. Can lightdm please detect that a touchscreen can only accept touch input and output to the touchscreen device?? Or at least have lightdm actually run the script when given? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 12 22:11:38 2014 InstallationDate: Installed on 2014-11-03 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) LightdmConfig: [SeatDefaults] autologin-user=boerske SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1392064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1392064] Re: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf
Here is a video of the bug, LightDM ignores the settings and moves the pointer to the right https://drive.google.com/file/d/0B4c5GbInagPqZEZvUlQxZ01qX0U/view?usp=sharing Here is a video of a working user session after logging in from LightDM, proving that the script works. https://drive.google.com/file/d/0B4c5GbInagPqNW5BU1BsWGV2cDA/view?usp=sharing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1392064 Title: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf Status in “lightdm” package in Ubuntu: New Bug description: Setup: Ubuntu 14.04.1LTS IIyama 19 Pro-Lite Touchscreen Dell 17 regular monitor Due to another bug in the detection of input devices I had to write a script to tell Ubuntu which screen to use the touch from the touchscreen. so I put the following two entries into a basic bash script based on xinput list and xrandr -q #!/bin/bash xinput map-to-output 12 DVI-I-1 xrandr --output DVI-I-1 --primary = I added this script to /usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf and the contents look like this. [SeatDefaults] greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh session-setup-script=/usr/local/bin/iiyama-touchscreen.sh When I start a user session the touchscreen is calibrated and works normally with the touch happening on the touchscreen. As soon as I logoff into LightDM the touch calibration is off moving the pointer a logarithmic distance from the left of the touchscreen. As soon as I log in again, no problems, touch works great, log back out into the lightDM greeter and boom touch is all crazy. Can lightdm please detect that a touchscreen can only accept touch input and output to the touchscreen device?? Or at least have lightdm actually run the script when given? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 12 22:11:38 2014 InstallationDate: Installed on 2014-11-03 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) LightdmConfig: [SeatDefaults] autologin-user=boerske SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1392064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1256388] [NEW] Yelp Couldn't parse troff special character: 'dq' from man
Public bug reported: Error message: ** (yelp:31227): WARNING **: Couldn't parse troff special character: 'dq' runtime error: file /usr/share/yelp-xsl/xslt/common/icons.xsl line 139 element call-template The called template 'l10n.gettext' was not found. runtime error: file /usr/share/yelp-xsl/xslt/common/html.xsl line 456 element call-template The called template 'l10n.direction' was not found. runtime error: file /usr/share/yelp-xsl/xslt/common/html.xsl line 459 element call-template The called template 'l10n.align.start' was not found. runtime error: file /usr/share/yelp-xsl/xslt/common/html.xsl line 464 element call-template The called template 'l10n.align.end' was not found. lsb_release -rd Description:Ubuntu 12.04.3 LTS Release:12.04 apt-cache policy yelp yelp: Geïnstalleerd: 3.4.1-0ubuntu1 Kandidaat: 3.4.1-0ubuntu1 Versietabel: *** 3.4.1-0ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status When opening a man page in yelp using yelp man:rsync yelp can't seem to parse the double quotes character. see screenshot steps to reproduce: open a terminal (CTRL+ALT+T) type: yelp man:rsync scroll down to the second paragraph in the Description section you'll see ? in black diamonds (�) instead of double quotes (). then open the man page in another terminal CTRL+ALT+T type: man rsync scroll to the same second paragraph in the Description section low and behold double quotes ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: yelp 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 Uname: Linux 3.2.0-57-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 29 18:36:06 2013 MarkForUpload: True SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity ** Attachment added: screenshot showing behaviour https://bugs.launchpad.net/bugs/1256388/+attachment/3919952/+files/2013-11-29_Yelp_parse_error_doublequotes.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1256388 Title: Yelp Couldn't parse troff special character: 'dq' from man Status in “yelp” package in Ubuntu: New Bug description: Error message: ** (yelp:31227): WARNING **: Couldn't parse troff special character: 'dq' runtime error: file /usr/share/yelp-xsl/xslt/common/icons.xsl line 139 element call-template The called template 'l10n.gettext' was not found. runtime error: file /usr/share/yelp-xsl/xslt/common/html.xsl line 456 element call-template The called template 'l10n.direction' was not found. runtime error: file /usr/share/yelp-xsl/xslt/common/html.xsl line 459 element call-template The called template 'l10n.align.start' was not found. runtime error: file /usr/share/yelp-xsl/xslt/common/html.xsl line 464 element call-template The called template 'l10n.align.end' was not found. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 apt-cache policy yelp yelp: Geïnstalleerd: 3.4.1-0ubuntu1 Kandidaat: 3.4.1-0ubuntu1 Versietabel: *** 3.4.1-0ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status When opening a man page in yelp using yelp man:rsync yelp can't seem to parse the double quotes character. see screenshot steps to reproduce: open a terminal (CTRL+ALT+T) type: yelp man:rsync scroll down to the second paragraph in the Description section you'll see ? in black diamonds (�) instead of double quotes (). then open the man page in another terminal CTRL+ALT+T type: man rsync scroll to the same second paragraph in the Description section low and behold double quotes ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: yelp 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 Uname: Linux 3.2.0-57-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 29 18:36:06 2013 MarkForUpload: True SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1256388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp