[Desktop-packages] [Bug 1945008] [NEW] Log in with Wayland although Xorg looks selected in session menu. Need to reselect
Public bug reported: After upgrade to Impish. 1. Log in with Xorg session 2. Log out 3. Check gdm session menu > Xorg is displayed as selected 4. Log in > Wayland is running 5. Log out 6. Check gdm session menu > Xorg is displayed as selected 7. Choose Xorg again anyway 8. Log in 9. Success. Xorg is running Reproduces every time for me. Despite Xorg always showing as selected, it uses Wayland unless I click the Xorg session again ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 24 21:05:34 2021 InstallationDate: Installed on 2018-09-13 (1106 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gdm3 UpgradeStatus: Upgraded to impish on 2021-09-24 (0 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1945008 Title: Log in with Wayland although Xorg looks selected in session menu. Need to reselect Status in gdm3 package in Ubuntu: New Bug description: After upgrade to Impish. 1. Log in with Xorg session 2. Log out 3. Check gdm session menu > Xorg is displayed as selected 4. Log in > Wayland is running 5. Log out 6. Check gdm session menu > Xorg is displayed as selected 7. Choose Xorg again anyway 8. Log in 9. Success. Xorg is running Reproduces every time for me. Despite Xorg always showing as selected, it uses Wayland unless I click the Xorg session again ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 24 21:05:34 2021 InstallationDate: Installed on 2018-09-13 (1106 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gdm3 UpgradeStatus: Upgraded to impish on 2021-09-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+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 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
Thank you, I tested the new values and it all works as expected for me. However, not sure what it is but the 225% value seems to change the rendering in an unpleasant way. Not sure if it's only not being used to it, but for the time being it feels more "comfortable" reverting to 200% and upping the font scaling a bit, as I did before. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: In Progress Status in gnome-control-center source package in Hirsute: In Progress Bug description: [ Impact ] On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." [ Test case ] In a setup with a display with HighDPi resolution (higher than 2880x1800) - Open gnome-control-center display panel - Scaling should show 5 level buttons to select - Selecting higher values will show all the selectable values closer to the chosen one - Any value could be used from 100% up to 400% (maximum varies on resolution) [ Regression potential ] Control center won't show any scaling value, or scaling value may be wrong. --- ProblemType: BugDistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+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 1904237] Re: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Daniel, I am affected as well like in the previous bug. Model is Dell XPS 9575 2-in-1. Shall I run the apport-collect as well? -- 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/1904237 Title: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Incomplete Bug description: mutter 3.36.6-1ubuntu0.20.04.2 shows again the incorrect behavior that was fixed in https://bugs.launchpad.net/mutter/+bug/1880596 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-13 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: mutter 3.36.6-1ubuntu0.20.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-13 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904237/+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 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
@albertvaka
I realize it stopped working for me as well, 20.04 with mutter
3.36.6-1ubuntu0.20.04.2
Still same machine as in above posts, Dell XPS 9575 2-in-1
No idea if same problem reappeared or it's an entirely new one
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Released
Bug description:
[ Impact ]
OSK doesn't appear in X11 when disabling physical keyboard
[ Test case ]
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this
disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search:
- The OSK appear
4. Swipe from bottom of screen in order to summon OSK on demand:
- occurred on Ubuntu 18.04 through 19.10)
[ Regression potential ]
The OSK shows when not needed in setup with no touch-screen or with
touch screen but when not required.
---
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
for the other and then Launchpad somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04.
Only the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under
Xorg, but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said
to have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage:
gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe
[Desktop-packages] [Bug 1871011] Re: USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict)
** Summary changed: - USB scanning broken on focal --> hpmud and ippusbxd conflict + USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1871011 Title: USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict) Status in HPLIP: Invalid Status in hplip package in Ubuntu: Expired Status in ippusbxd package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy Printer/scanner is an Officejet 4635. Scanning previously worked just fine a few months ago. Regression? To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1871011/+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 1871011] Re: USB scanning broken on focal --> hpmud and ippusbxd conflict
** Also affects: ippusbxd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1871011 Title: USB scanning broken on focal by ippusbxd (was: hpmud and ippusbxd conflict) Status in HPLIP: Invalid Status in hplip package in Ubuntu: Expired Status in ippusbxd package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy Printer/scanner is an Officejet 4635. Scanning previously worked just fine a few months ago. Regression? To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1871011/+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 1873748] Re: Simple Scan stops working after upgrade to 20.04
*** This bug is a duplicate of bug 1871011 *** https://bugs.launchpad.net/bugs/1871011 This bug was set as a duplicate of bug #1871011, bug #1871011 is invalid/expired and the issue still persists. I just connected a new Canon LiDE 300 USB scanner on Ubuntuj 20.04 and Xsane reported "device busy" until I googled (https://forums.linuxmint.com/viewtopic.php?f=51=329760 with also mentions other scanners) and uninstalled ippusbxd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1873748 Title: Simple Scan stops working after upgrade to 20.04 Status in sane-backends package in Ubuntu: Confirmed Status in simple-scan package in Ubuntu: Confirmed Bug description: My HP5200 All-in-Oneder worked fine under 19.10, but after upgrading to 20.04, simple-scan can no longer connect to the scanner although the printer still works fine. This is fairly critical to my work flow and I had to boot and use Windows 10 (major ick) to work around this. NOT GOOD. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.0-0ubuntu1 Uname: Linux 5.6.5 x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Apr 20 00:42:22 2020 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.5 root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash console=tty1 console=ttyS0 panic=-1 vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd11/26/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1873748/+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 1871011] Re: USB scanning broken on focal --> hpmud and ippusbxd conflict
The ippusbxd grabbing the printer/scanner does not seem to be limited to HP, I had same with Canon LiDE 300 scanner and other scanners mentioned here: https://forums.linuxmint.com/viewtopic.php?f=51=329760 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1871011 Title: USB scanning broken on focal --> hpmud and ippusbxd conflict Status in HPLIP: Invalid Status in hplip package in Ubuntu: Expired Bug description: On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy Printer/scanner is an Officejet 4635. Scanning previously worked just fine a few months ago. Regression? To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1871011/+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 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
@michel.ekimia, please see bug #1880596 -- 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/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-settings-daemon source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
Maybe I should add that I qualify the OSK appearing in laptop mode under X as
"Success" because:
-This is how it behaved until 19.10 both under X and Wayland
-In the upstream bug it was mentioned that the laptop vs tablet mode detection
would not work under X and so the new behavior under Wayland (no OSK in laptop
mode) could not (yet) be duplicated
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Committed
Bug description:
[ Impact ]
OSK doesn't appear in X11 when disabling physical keyboard
[ Test case ]
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this
disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search:
- The OSK appear
4. Swipe from bottom of screen in order to summon OSK on demand:
- occurred on Ubuntu 18.04 through 19.10)
[ Regression potential ]
The OSK shows when not needed in setup with no touch-screen or with
touch screen but when not required.
---
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
for the other and then Launchpad somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04.
Only the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under
Xorg, but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said
to have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage:
gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Fix released, see the new bug #1880596. Should this one be marked a duplicate of bug #1880596? -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
And thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Committed
Bug description:
[ Impact ]
OSK doesn't appear in X11 when disabling physical keyboard
[ Test case ]
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this
disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search:
- The OSK appear
4. Swipe from bottom of screen in order to summon OSK on demand:
- occurred on Ubuntu 18.04 through 19.10)
[ Regression potential ]
The OSK shows when not needed in setup with no touch-screen or with
touch screen but when not required.
---
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
for the other and then Launchpad somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04.
Only the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under
Xorg, but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said
to have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage:
gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1880596/+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 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
Installed mutter 3.36.3-0ubuntu0.20.04.1 from -proposed.
This fixes the bug for me on the Dell XPS 9575 (could not test on the Asus
Zenbook)
Tested:
1. Logged into Xorg session
2. In laptop mode (physical keyboard enabled):
- Touch Activities > Search: Success, OSK appears
- Touch Show Applications > Search: Success, OSK appears
- Open gnome-term > touch input area: Success, OSK appears
- Open gedit > touch test areas: Success, OSK appears
- Open Firefox > touch search box: Success, OSK appears
- Open GnuCash (gtk application) > touch: OSK appears, but is flakey. This is
as I remember it always to be
- Swiped up from bottom of screen to summon OSK as needed: Success, OSK appears
- In all test cases: touched DownArrow button on OSK: Success, OSK disappears
3. Folded display to tablet mode (physical keyboard disabled):
- Same tests, same behavior
4. Log out and into Wayland session:
- Same tests and successes in tablet mode. In laptop mode, the OSK never
appears as expected due to the design decision mentioned above*
* Still rather infuriating that you can touch a textfield but are not
allowed to enter anything
** Tags removed: verification-needed
** Tags added: verification-done-focal
** Tags removed: verification-needed-focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Committed
Bug description:
[ Impact ]
OSK doesn't appear in X11 when disabling physical keyboard
[ Test case ]
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this
disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search:
- The OSK appear
4. Swipe from bottom of screen in order to summon OSK on demand:
- occurred on Ubuntu 18.04 through 19.10)
[ Regression potential ]
The OSK shows when not needed in setup with no touch-screen or with
touch screen but when not required.
---
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
for the other and then Launchpad somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04.
Only the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under
Xorg, but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said
to have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet,
[Desktop-packages] [Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
Will be fixed in 3.36.3:
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242#note_823253
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
for the other and then Launchpad somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04.
Only the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under
Xorg, but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said
to have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+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 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for https://gitlab.gnome.org/GNOME
/gnome-shell/-/issues/2378. I set one for the other and then Launchpad
somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
- 3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
+ 3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
for the other and then Launchpad somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch a (supported) text input field, such as
gnome-shell > Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@seb128: Created the new bug #1880596 -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertable laptops in tablet mode with physical keyboard disabled
sudo libinput list-devices > list-devices.txt:
was generated in laptop mode i.e. with the physical keyboard enabled.
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
- Related upstream bugs:
+ Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
+
+ [Note: Please someone add a bug watch for https://gitlab.gnome.org/GNOME
+ /gnome-shell/-/issues/2378. I set one for the other and then Launchpad
+ somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
-
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
** Attachment added: "list-devices.txt"
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+attachment/5376642/+files/list-devices.txt
** Summary changed:
- [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertable laptops in tablet mode with physical keyboard disabled
+ [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertible laptops in tablet mode with physical keyboard disabled
** Summary changed:
- [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertible laptops in tablet mode with physical keyboard disabled
+ [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertible laptops in tablet mode when physical keyboard disabled
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
[Desktop-packages] [Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertable laptops in tablet mode with physical keyboard disabled
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
- Related upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
+ Related upstream bugs:
+ https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
+ https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
- (On Wayland there is a different changed behavior with the OSK not
- appearing in the device's laptop mode, i.e. with the physical keyboard
- enabled. This seems intended and a different issue as per
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872)
+ (On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
+ https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
- This bug report was created on Dell XPS 9575 2-in-1, where the bug
reproduces.
+
+ This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertable laptops in tablet mode with physical
keyboard disabled
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
for the other and then Launchpad somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT:
[Desktop-packages] [Bug 1880596] [NEW] [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertable laptops in tablet mode with physical keyboard disabled
Public bug reported:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell fields
like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text fields
of foreign toolkits that are expected not to trigger the OSK automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing in
the device's laptop mode, i.e. with the physical keyboard enabled. This seems
intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly Wayland
and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
** Affects: gnome-shell
Importance: Unknown
Status: Unknown
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1242
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Importance: Unknown
Status: Unknown
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertable laptops in tablet mode with physical
keyboard disabled
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@seb128: A new bug for each device? I am the OP and I reproduced this on two different foldable laptops (Dell XPS and Asus Flip), should I open a new bug for each? (When opening this here bug, I used ubuntu-bug on the Dell XPS) -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Related Bug #1851931 ? -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Thanks. It does look to me that the keyboard issue is probably separate and certainly warrants a bug, in particular if it is a regression and those 2-in-1s switched fine with Ubuntu 19.10. But I am just a mere user here, @vanvugt will know. -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Thanks. So it seems as follows, correct? This here bug report refers only to running under Xorg in Focal, where ... - the OSK does not work at all on the properly supported devices (at least the ones listed), - neither per autosummon nor on demand by swiping, - regardless of a physical keyboard not being available. This is a regression compared to Eoan. However the OSK is working in Focal as expected [1] on Wayland, on supported devices where the physical keyboard gets properly disabled. As far as I know, it is not expected for autosummon to work for KeePassXC etc., but in this case I can summon on demand in Wayland by swiping from bottom of screen. (But can't under Xorg) [1] It seems it is expected that even in Wayland the OSK is only available when the physical keyboard is disabled, according to discussion on this gnome-shell report: "On Screen Keyboard shows up on Wayland despite there is a physical keyboard" https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 The above gnome-shell #2353 is linked from the gnome-shell report that seems to be related to the issue in this here bug, as @esjarc mentioned in the duplicate Bug #1874017, i.e.: "OSK isn't activated without physical keyboard" https://gitlab.gnome.org/GNOME/gnome-shell/issues/2378 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2353 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@esjarc, does the keyboard get disabled when you fold your machines? It does on mine, as it should be. I'm just wondering where the difference comes from -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@esjrac, you wrote in the duplicate Bug #1874017 that the issue occurs for you under Wayland as well. Can you repro this also in the tablet mode of the foldable devices that you mentioned there? I am asking because for me this occurs under Wayland only if the devices are laptop mode. In tablet mode, the OSK comes up fine (both auto by touching textfield and when summoned by swiping). I can still repro this (with gnome 3.36.1 on Focal) with foldable devices as described in the OP above, i.e. with: Dell XPS 9575 2-in-1 Asus Zenbook Flip UX561UD However under Xorg the OSK does not come up in tablet mode either -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
*** This bug is a duplicate of bug 1807276 *** https://bugs.launchpad.net/bugs/1807276 @esjarc, as the OP of this report I agree and also commented as much in the other #1807276 already. -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
Still reproducible with Ubuntu 20.04 beta with gnome-control-center 1:3.36.1-1ubuntu4 and gnome-3.36.1, where the option to enable fractional scaling is exposed in the GUI -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+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 1807276] Re: Cannot open Onscreen Keyboard in Xorg
But it worked before for me before, see duplicate https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556 And the part where it does not appear at all occurred in the past and was fixed: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 -- 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/1807276 Title: Cannot open Onscreen Keyboard in Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Ubuntu 18.10 / GNOME Shell 3.30.1 ALSO Ubuntu 18.04 LTS / GNOME Shell 3.28.1 Steps to reproduce on our end: - Login (Xorg as default) - Attempt to swipe up with finger from below screen RESULT: It draws a thin vertical (desktop) selection box, but no OSK - Logout - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland' - ps -e | grep Xwayland #shows 'Xwayland' process is running - Repeat swipe up with finger from below screen RESULT: OSK shows up as expected This has been verified both in 1920x1080 as well as 3840x2160 resolutions (also with various scaling options selected) Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome- shell/issues/839 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1807276/+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 1866556] [NEW] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Public bug reported: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Summary changed: - On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg + On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal ** Description changed: After upgrading to Focal, the OSK never appears for me under Xorg - - Does appear automatically when selecting text fields - - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan) + - Does not appear automatically when selecting text fields + - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) - Under Wayland, both these things work if the laptop is in tablet mode - (but not if it is in regular laptop mode). + Under Wayland, both these things continued to work after the Focal + upgrade if the laptop is in tablet mode (but not if it is in regular + laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 - Asus Zenbook flip UX561UD. + Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: New Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+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 1832124] Re: Right-click file on desktop > Move to Trash frequently crashes gnome-shell
I'm the OP and I can't. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Right-click file on desktop > Move to Trash frequently crashes gnome- shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: In 19.04 Disco fully up to date. Reproduced on two different machines: 1. Log into Wayland session (did not try with X) 2. touch ~/Desktop/testfile 3. Right-click testfile on Desktop > Move to Trash -> gnome-shell crashes in around 50% of instances in my case. I did not find out what's the difference. I do run a few other gnome-shell extensions, but all from the Ubuntu repos except for Remove Accessibility. There are quite some occurrences of org.gnome.Shell.desktop in journalctl, though I didn't correlate yet as the issues seems easy to repro. If you can't repro, pls let me know and I can look for clues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.3-1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 9 12:51:20 2019 InstallationDate: Installed on 2018-09-13 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-12 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+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 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
On Eoan (on the Dell XPS 9575 mentioned before), the OSK auto-summons nearly everywhere as far as I can tell, incl. Chrome. The only application I use and found so far where this does not work is Gnucash. There is even an improvement in X that helps in this case: the OSK now can be summoned by swiping up from the bottom screen edge, in the same way as it previously worked only on Wayland. -- 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/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-settings-daemon source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
Holy cow, I completely misunderstood the UI. Sorry for bothering!!! ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) Status in gnome-terminal package in Ubuntu: Invalid Bug description: There is no cursor in gnome-terminal. Issue persists after reboot. Must have happened after some recent update as I use gnome-terminal not all the time but regularly and it is immediately noticeable when editing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 20:34:14 2019 InstallationDate: Installed on 2018-09-13 (382 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-09-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+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 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
And regarding "Can you recall when was the last time the cursor showed up correctly for you? (Like, about 1 day ago, about 1 week ago...?) Was that on disco, or eoan beta?" I cannot be sure, but it probably was within the last week that it still worked with the custom theme I had. I am tempted to say that this was "definitely" on eoan beta: - As mentioned, I had switched to the custom theme because of a change of background color due to the system theme, and that was definitely well after my upgrade to eoan (which was nearly a month ago) - I am "pretty" sure that I would have noticed if the cursor had disappeared right after switching to the custom theme as you can't edit a command line without a cursor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) Status in gnome-terminal package in Ubuntu: New Bug description: There is no cursor in gnome-terminal. Issue persists after reboot. Must have happened after some recent update as I use gnome-terminal not all the time but regularly and it is immediately noticeable when editing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 20:34:14 2019 InstallationDate: Installed on 2018-09-13 (382 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-09-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+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 1846255] Re: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
Thanks. My results: No cursor visible with the command running. No cursor with any of the three cursor shapes selected (and blinking off). Colors: This did it. My system theme option was unchecked (I did that recently after some Yaru (I think) update in Eoan changed the background color from purple to gray). Therefore I had a custom theme, which did work before the cursor problem appeared: Default: white text (#FF), purple background (#3E0937) Bold: checked, same colors Cursor color: checked, same colors So now I checked the system theme option again and restarted the gnome- terminal. The background color is back to purple as it should be and the cursor is back. Thanks! However, there still seems to be a problem: When I uncheck the system theme option again (using the same custom colors) and restart the terminal, the cursor is gone again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) Status in gnome-terminal package in Ubuntu: New Bug description: There is no cursor in gnome-terminal. Issue persists after reboot. Must have happened after some recent update as I use gnome-terminal not all the time but regularly and it is immediately noticeable when editing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 20:34:14 2019 InstallationDate: Installed on 2018-09-13 (382 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-09-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+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 1846255] [NEW] No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan)
Public bug reported: There is no cursor in gnome-terminal. Issue persists after reboot. Must have happened after some recent update as I use gnome-terminal not all the time but regularly and it is immediately noticeable when editing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 20:34:14 2019 InstallationDate: Installed on 2018-09-13 (382 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-09-06 (24 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1846255 Title: No cursor in gnome-terminal 3.34.0-1ubuntu2 (eoan) Status in gnome-terminal package in Ubuntu: New Bug description: There is no cursor in gnome-terminal. Issue persists after reboot. Must have happened after some recent update as I use gnome-terminal not all the time but regularly and it is immediately noticeable when editing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 20:34:14 2019 InstallationDate: Installed on 2018-09-13 (382 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-09-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+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 1843645] Re: Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. General interface font has no effect?
I had forgotten to add that I am running Wayland. Anyways, the problem is now fixed with latest updates (Possibly mutter (3.34.0-2) with changelog "Fixes starting up of gsd-xsettings on Wayland"?) ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1843645 Title: Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. General interface font has no effect? Status in firefox package in Ubuntu: Fix Released Bug description: Firefox 69.0+build2-0ubuntu1 HiDPI display, 3840 x 2160 After a full update on Sept 10 (previously it was fine on Eoan): - The Firefox UI font is tiny, content is fine. - Thunderbird is the only other affected application. - Changing interface font, font size, and font scaling in Gnome Tweaks has no effect on the Firefox/Thunderbird UI fonts, but works elsewhere. - Changing layout.css.devPixelsPerPx in about:config (either at -1 or positive values like 2.5 or 4) changes the widget size correctly but has no effect on the UI font. - Changing Scale in Gnome Settings > Devices > Displays > Scale also affects everything except these font sizes - In addition to the fonts, the window's min/max/close buttons are also tiny. The UI elements within the window have the correct size, e.g. back/forward and other buttons, address bar itself (but not the font within), etc. The tiny window buttons also only affect the Firefox and Thunderbird windows, other windows have normal buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843645/+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 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
Sorry, "appear *behind* the Ubuntu dock" the -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Some extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+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 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
gnome-shell-extension-workspaces-to-dock universe, version: 51-1 When active, the Activities and Application menus stop working, incl. Super key. In addition the window management breaks, windows appear being the Ubuntu dock. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Some extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+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 1843645] Re: Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. General interface font has no effect?
** Description changed: Firefox 69.0+build2-0ubuntu1 HiDPI display, 3840 x 2160 After a full update on Sept 10 (previously it was fine on Eoan): - The Firefox UI font is tiny, content is fine. - Thunderbird is the only other affected application. - Changing interface font, font size, and font scaling in Gnome Tweaks has no effect on the Firefox/Thunderbird UI fonts, but works elsewhere. - Changing layout.css.devPixelsPerPx in about:config (either at -1 or positive values like 2.5 or 4) changes the widget size correctly but has no effect on the UI font. - Changing Scale in Gnome Settings > Devices > Displays > Scale also affects everything except these font sizes + - In addition to the fonts, the window's min/max/close buttons are also tiny. The UI elements within the window have the correct size, e.g. back/forward and other buttons, address bar itself (but not the font within), etc. The tiny window buttons also only affect the Firefox and Thunderbird windows, other windows have normal buttons -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1843645 Title: Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. General interface font has no effect? Status in firefox package in Ubuntu: New Bug description: Firefox 69.0+build2-0ubuntu1 HiDPI display, 3840 x 2160 After a full update on Sept 10 (previously it was fine on Eoan): - The Firefox UI font is tiny, content is fine. - Thunderbird is the only other affected application. - Changing interface font, font size, and font scaling in Gnome Tweaks has no effect on the Firefox/Thunderbird UI fonts, but works elsewhere. - Changing layout.css.devPixelsPerPx in about:config (either at -1 or positive values like 2.5 or 4) changes the widget size correctly but has no effect on the UI font. - Changing Scale in Gnome Settings > Devices > Displays > Scale also affects everything except these font sizes - In addition to the fonts, the window's min/max/close buttons are also tiny. The UI elements within the window have the correct size, e.g. back/forward and other buttons, address bar itself (but not the font within), etc. The tiny window buttons also only affect the Firefox and Thunderbird windows, other windows have normal buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843645/+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 1843645] [NEW] Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. General interface font has no effect?
Public bug reported: Firefox 69.0+build2-0ubuntu1 HiDPI display, 3840 x 2160 After a full update on Sept 10 (previously it was fine on Eoan): - The Firefox UI font is tiny, content is fine. - Thunderbird is the only other affected application. - Changing interface font, font size, and font scaling in Gnome Tweaks has no effect on the Firefox/Thunderbird UI fonts, but works elsewhere. - Changing layout.css.devPixelsPerPx in about:config (either at -1 or positive values like 2.5 or 4) changes the widget size correctly but has no effect on the UI font. - Changing Scale in Gnome Settings > Devices > Displays > Scale also affects everything except these font sizes ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: eoan hidpi ** Summary changed: - Tiny UI fonts in Firefox (and Thunderbird) after update in eoan. Maybe doesn't doesn't honour custom interface font? + Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. Maybe doesn't doesn't honor custom interface font? ** Summary changed: - Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. Maybe doesn't doesn't honor custom interface font? + Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. Maybe doesn't doesn't honor general interface font? ** Description changed: Firefox 69.0+build2-0ubuntu1 HiDPI display, 2840 x 2160 - - The UI font is tiny, content is fine. + After a full update on Sept 10 (previously it was fine on Eoan): + + - The Firefox UI font is tiny, content is fine. - Thunderbird is the only other affected application. - Changing interface font, font size, and font scaling in Gnome Tweaks has no effect on the Firefox/Thunderbird UI fonts, but works elsewhere. - Changing layout.css.devPixelsPerPx in about:config (either at -1 or positive values like 2.5 or 4) changes the widget size correctly but has no effect on the UI font. - Changing Scale in Gnome Settings > Devices > Displays > Scale also affects everything except these font sizes ** Description changed: Firefox 69.0+build2-0ubuntu1 - HiDPI display, 2840 x 2160 + HiDPI display, 3840 x 2160 After a full update on Sept 10 (previously it was fine on Eoan): - The Firefox UI font is tiny, content is fine. - Thunderbird is the only other affected application. - Changing interface font, font size, and font scaling in Gnome Tweaks has no effect on the Firefox/Thunderbird UI fonts, but works elsewhere. - Changing layout.css.devPixelsPerPx in about:config (either at -1 or positive values like 2.5 or 4) changes the widget size correctly but has no effect on the UI font. - Changing Scale in Gnome Settings > Devices > Displays > Scale also affects everything except these font sizes ** Summary changed: - Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. Maybe doesn't doesn't honor general interface font? + Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. Maybe doesn't honor general interface font? ** Summary changed: - Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. Maybe doesn't honor general interface font? + Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. General interface font has no effect? ** Tags added: hidpi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1843645 Title: Tiny UI fonts in Firefox (and Thunderbird) after update in Eoan. General interface font has no effect? Status in firefox package in Ubuntu: New Bug description: Firefox 69.0+build2-0ubuntu1 HiDPI display, 3840 x 2160 After a full update on Sept 10 (previously it was fine on Eoan): - The Firefox UI font is tiny, content is fine. - Thunderbird is the only other affected application. - Changing interface font, font size, and font scaling in Gnome Tweaks has no effect on the Firefox/Thunderbird UI fonts, but works elsewhere. - Changing layout.css.devPixelsPerPx in about:config (either at -1 or positive values like 2.5 or 4) changes the widget size correctly but has no effect on the UI font. - Changing Scale in Gnome Settings > Devices > Displays > Scale also affects everything except these font sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843645/+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 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
With GNOME Shell 3.33.91: gpaste 3.30.2-1ubuntu3 (universe) gnome-shell-extension-suspend-button 0~git20180827-2 (universe) Both marked as "Error loading extension" in Tweaks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Some extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+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 1832124] Re: Moving file to Trash frequently crashes gnome-shell
** Summary changed: - Moving file to Trash requently crashes gnome-shell + Moving file to Trash frequently crashes gnome-shell ** Summary changed: - Moving file to Trash frequently crashes gnome-shell + Right-click file on desktop > Move to Trash frequently crashes gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Right-click file on desktop > Move to Trash frequently crashes gnome- shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: In 19.04 Disco fully up to date. Reproduced on two different machines: 1. Log into Wayland session (did not try with X) 2. touch ~/Desktop/testfile 3. Right-click testfile on Desktop > Move to Trash -> gnome-shell crashes in around 50% of instances in my case. I did not find out what's the difference. I do run a few other gnome-shell extensions, but all from the Ubuntu repos except for Remove Accessibility. There are quite some occurrences of org.gnome.Shell.desktop in journalctl, though I didn't correlate yet as the issues seems easy to repro. If you can't repro, pls let me know and I can look for clues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.3-1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 9 12:51:20 2019 InstallationDate: Installed on 2018-09-13 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-12 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+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 1832124] [NEW] Moving file to Trash requently crashes gnome-shell
Public bug reported: In 19.04 Disco fully up to date. Reproduced on two different machines: 1. Log into Wayland session (did not try with X) 2. touch ~/Desktop/testfile 3. Right-click testfile on Desktop > Move to Trash -> gnome-shell crashes in around 50% of instances in my case. I did not find out what's the difference. I do run a few other gnome-shell extensions, but all from the Ubuntu repos except for Remove Accessibility. There are quite some occurrences of org.gnome.Shell.desktop in journalctl, though I didn't correlate yet as the issues seems easy to repro. If you can't repro, pls let me know and I can look for clues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.3-1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 9 12:51:20 2019 InstallationDate: Installed on 2018-09-13 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-12 (147 days ago) ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Moving file to Trash requently crashes gnome-shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: In 19.04 Disco fully up to date. Reproduced on two different machines: 1. Log into Wayland session (did not try with X) 2. touch ~/Desktop/testfile 3. Right-click testfile on Desktop > Move to Trash -> gnome-shell crashes in around 50% of instances in my case. I did not find out what's the difference. I do run a few other gnome-shell extensions, but all from the Ubuntu repos except for Remove Accessibility. There are quite some occurrences of org.gnome.Shell.desktop in journalctl, though I didn't correlate yet as the issues seems easy to repro. If you can't repro, pls let me know and I can look for clues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.3-1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 9 12:51:20 2019 InstallationDate: Installed on 2018-09-13 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-12 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+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 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating
(I still get the "Failed to apply DRM plane", but the immediate unrotation does not happen anymore. This is at least in Wayland, could not check X) -- 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/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating Status in gnome-shell package in Ubuntu: Confirmed Status in iio-sensor-proxy package in Ubuntu: Confirmed Bug description: on a dell xps 15 2-in-1 (model 9575), I've enabled iio-sensor-proxy functionality by doing: modprobe intel-ish-ipc echo "8086 a135" > /sys/bus/pci/drivers/intel_ish_ipc/new_id This makes `monitor-sensor` display rotation events, and gnome-shell auto-rotate the screen upon receiving them. However, immediately after rotating, the screen rotates back to its normal orientation (unless I quickly lock rotation), displaying the following in journalctl: Oct 10 09:06:19 taplop gnome-shell[2616]: Failed to apply DRM plane transform 1: Invalid argument Oct 10 09:06:20 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Oct 10 09:06:20 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Oct 10 09:06:20 taplop kernel: [drm] VCE initialized successfully. Oct 10 09:06:27 taplop kernel: amdgpu :01:00.0: GPU pci config reset ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:06:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+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 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating
I cannot reproduce this anymore on Ubuntu 19.04, gnome-shell 3.32 -- 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/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating Status in gnome-shell package in Ubuntu: Confirmed Status in iio-sensor-proxy package in Ubuntu: Confirmed Bug description: on a dell xps 15 2-in-1 (model 9575), I've enabled iio-sensor-proxy functionality by doing: modprobe intel-ish-ipc echo "8086 a135" > /sys/bus/pci/drivers/intel_ish_ipc/new_id This makes `monitor-sensor` display rotation events, and gnome-shell auto-rotate the screen upon receiving them. However, immediately after rotating, the screen rotates back to its normal orientation (unless I quickly lock rotation), displaying the following in journalctl: Oct 10 09:06:19 taplop gnome-shell[2616]: Failed to apply DRM plane transform 1: Invalid argument Oct 10 09:06:20 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Oct 10 09:06:20 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Oct 10 09:06:20 taplop kernel: [drm] VCE initialized successfully. Oct 10 09:06:27 taplop kernel: amdgpu :01:00.0: GPU pci config reset ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:06:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+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 1740894] Re: KEY_RFKILL is not passed to userspace
Confirm that it also works with Cosmic on the Asus ZenBook Flip UX561UD from my comment #1 xkb-data 2.23.1-1ubuntu1.18.10.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xorgproto source package in Bionic: Fix Released Status in libxkbcommon source package in Cosmic: Fix Released Status in xkeyboard-config source package in Cosmic: Fix Released Status in xorgproto source package in Cosmic: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
FYI, fix for Wayland: bug #1816808 -- 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/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-settings-daemon source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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 1791548] Re: Incorrect description for activation of new on-screen keyboard with Gnome 3.28 (Ubuntu 18.04.1 LTS) and 3.30 (Ubuntu Cosmic 18.10)
*** This bug is a duplicate of bug 1760399 *** https://bugs.launchpad.net/bugs/1760399 So according to the resolution in bug #1760399, the Universal Access is supposed to be enabled after all to make OSK appear in X, and with the resolution it now actually works. Hence the description in the help seems to be (have become) correct at least for X (though it would help to mention swiping up on Wayland). I suppose this warrants setting it as duplicate ** This bug has been marked a duplicate of bug 1760399 New On-screen keyboard does not appear automatically when selecting some text fields -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1791548 Title: Incorrect description for activation of new on-screen keyboard with Gnome 3.28 (Ubuntu 18.04.1 LTS) and 3.30 (Ubuntu Cosmic 18.10) Status in gnome-user-docs package in Ubuntu: New Bug description: The docs seem to give an incorrect or at least incomplete and misleading description: "The on-screen keyboard is automatically enabled if you use a touchscreen 1. Open the Activities overview and start typing Universal Access. 2. Click on Universal Access to open the panel. 3. Switch on Screen Keyboard in the Typing section. When you next have the opportunity to type, the on-screen keyboard will open at the bottom of the screen." -- https://help.ubuntu.com/stable/ubuntu-help/keyboard-osk.html The Gnome 3.28 release notes say something different, but this is also incorrect: "The new keyboard automatically activates when a text area is selected, ..." -- https://help.gnome.org/misc/release-notes/3.28/ As far as I can tell the behavior is the same in X session and Wayland session, with the one important difference that there is no way to manually activate the OSK in X. * Neither in X nor in Wayland does the keyboard always automatically activate when selecting a text area. * As far as I can tell is not necessary to activate it in Universal Access either in X or Wayland. If I enable it, I can see no difference in the reliability of auto activation. E.g., in the Activities search box it auto activates in either case (Wayland or X, activated in Universal Access or not). If it does not auto activate, e.g. in Gnome apps like gnome-terminal or gedit, or in non-Gnome like Firefox, enabling it in UA does not help either. * It can be summoned in Wayland by swiping up on a touch screen, but this does not work in X. There is no known way to manually activate it in X. (A gnome-shell extension exists but does not work with Gnome 3.28 or 3.30. Also there should be no need to hunt for an unofficial extension for this basic functionality) The situation is still the same in Cosmic. This documentation issue is particularly troublesome because even in the best case, Wayland, there is no UI hint for how to summon it, and it is difficult to discover. There are several questions on Askubuntu and the answers that existed so far show that basically no-one understood the whole story (for links see my other bug report on discoverability, below) I also refer you to my comments on the bug report, "New On-screen keyboard cannot be manually triggered to appear": https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1760399/comments/10 New bug report for poor discoverability of swiping up in Wayland: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-docs 18.04.4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 9 22:47:11 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2185 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) PackageArchitecture: all SourcePackage: ubuntu-docs UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1791548/+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 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
Sorry for spamming, I should have clicked the source link on OMGUbuntu, experimental is apparently expected: https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling- in-wayland-landed/ -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: Fix Released Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. Workaround == You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS by running the following command in a terminal and then restarting your computer. Note that this is an experimental feature and is not fully supported by either Ubuntu or GNOME. gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After restarting your computer, you should find additional scale options in Settings > Devices > Displays. If you change your mind and want to get back to supported status, run: gsettings reset org.gnome.mutter experimental-features To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+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 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
(Note that adding scale-monitor-framebuffer to experimental mutter settings was already the workaround mentioned in Bug Description, so not new) -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: Fix Released Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. Workaround == You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS by running the following command in a terminal and then restarting your computer. Note that this is an experimental feature and is not fully supported by either Ubuntu or GNOME. gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After restarting your computer, you should find additional scale options in Settings > Devices > Displays. If you change your mind and want to get back to supported status, run: gsettings reset org.gnome.mutter experimental-features To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+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 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
I have this now on Disco in Wayland and with update to mutter 3.32 (incl. proposed, except gnome-settings-daemon at 3.31.91-1ubuntu1), but apparently I had to add scale-monitor-framebuffer to the gsettings key org.gnome.mutter.experimental-features (as mentioned by https://www.omgubuntu.co.uk/2019/03/best-gnome-3-32-features). Is this expected? I also still have the limited options as in gnome-control-center bug #1795483 from my comment #34 above. (100, 125, 150, 175, 200), with 200 still too small on this display (15" with 3840*2160) -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: Fix Released Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. Workaround == You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS by running the following command in a terminal and then restarting your computer. Note that this is an experimental feature and is not fully supported by either Ubuntu or GNOME. gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After restarting your computer, you should find additional scale options in Settings > Devices > Displays. If you change your mind and want to get back to supported status, run: gsettings reset org.gnome.mutter experimental-features To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+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 1800727] Re: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed
** Description changed: + Airplane mode works (enable and disable) after the eventual fixes in bug + #1740894 and the regression does not occur. + + [Original report] + Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in order to pass KEY_RFKILL to userspace. Despite the issue described in bug #1740894, on Dell XPS 15 9575 the airplane mode key actually worked flawlessly out-of-the-box after installing Cosmic at beginning of September, using xkb-data 2.23. Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to the following issue: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xkb-data 2.23.1-1ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 22:13:45 2018 Dependencies: - + DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu InstallationDate: Installed on 2018-09-13 (47 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai - Bus 001 Device 004: ID 27c6:5395 - Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai + Bus 001 Device 004: ID 27c6:5395 + Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1800727 Title: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: Airplane mode works (enable and disable) after the eventual fixes in bug #1740894 and the regression does not occur. [Original report] Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in order to pass KEY_RFKILL to userspace. Despite the issue described in bug #1740894, on Dell XPS 15 9575 the airplane mode key actually worked flawlessly out-of-the-box after installing Cosmic at beginning of September, using xkb-data 2.23. Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to the following issue: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xkb-data 2.23.1-1ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
And I can confirm that it is fixed on Disco as well -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Status in xkeyboard-config source package in Disco: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Fixed by bug #1740894, confirmed in Cosmic and Disco ** Changed in: xkeyboard-config (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1800727] Re: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed
Fixed by changed in bug #1740894 ** Changed in: xkeyboard-config (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1800727 Title: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in order to pass KEY_RFKILL to userspace. Despite the issue described in bug #1740894, on Dell XPS 15 9575 the airplane mode key actually worked flawlessly out-of-the-box after installing Cosmic at beginning of September, using xkb-data 2.23. Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to the following issue: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xkb-data 2.23.1-1ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 22:13:45 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu InstallationDate: Installed on 2018-09-13 (47 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1800727/+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 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
I can confirm on Disco that this is definitely better, but not completely solved for me: gnome-settings-daemon 3.30.2-2ubuntu1 Screen Keyboard is off in Universal Access settings * Good in both X and Wayland: 1. Touch Activities on panel 2. Touch "type to search" box -> OSK comes up. 3. Close OSK with ArrowDown icon 4. Touch "type to search" box again -> OSK comes up again. (Same good behavior for: Applications on dock -> "Type to search" GDM login screen -> password field) * Good only in X, not good in Wayland: 1. Two applications side by side e.g. gnome-term and gedit 2. Switch windows by touching -> In X, OSK comes up on focus change, but not in Wayland . So in X it is good so far but ... 3. Close OSK by ArrowDown icon 4. Touch _same_ window again (and hence no focus switch) -> no OSK even in X 1. Start on an empty workspace: Firefox, nautilus, epiphany, and others: 2. Touch text entry fields -> OSK comes up in X but not in Wayland * Bad in both X and Wayland: 1. Go to empty workspace 2. Launch gnome-term, LibreOffice Writer or Calc, others: -> no OSK. However in X (but not Wayland) ... 3. Switch focus by touching any menu on Gnome panel 4. Touch gnome-term again -> Now OSK comes up * Bad in X when OSK does not come up automatically: When OSK does not appear automatically, there is still no way to summon it on demand. (While in Wayland swiping up still works as workaround but remains difficult to discover) -- 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/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: In Progress Status in gnome-settings-daemon source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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 1720089] Re: Desktop isn't part of "places" (left bar) in artful
(This is in Disco, nautilus 1:3.31.90-1ubuntu2) -- 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/1720089 Title: Desktop isn't part of "places" (left bar) in artful Status in nautilus package in Ubuntu: Fix Released Bug description: Artful re-enabled the desktop, but it is not showing up in the left bar of nautilus [This used to be called "places"?]. I'm talking about this bar: https://pasteboard.co/GMqxauJ.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720089/+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 1720089] Re: Desktop isn't part of "places" (left bar) in artful
Confirming what Olivier wrote, I see it in X but not Wayland -- 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/1720089 Title: Desktop isn't part of "places" (left bar) in artful Status in nautilus package in Ubuntu: Fix Released Bug description: Artful re-enabled the desktop, but it is not showing up in the left bar of nautilus [This used to be called "places"?]. I'm talking about this bar: https://pasteboard.co/GMqxauJ.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720089/+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 1808861] Re: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
I have hundreds of gigs free disk space and 16 GB or RAM of which typically only 50% is even used -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: Invalid Status in chromium-browser package in Ubuntu: Invalid Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1808861] Re: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
I keep getting this with dbus. First on Cosmic (fresh install) regularly, now after update to Disco again. ERROR: apport (pid 17063) Sat Jan 12 23:06:33 2019: wrote report /var/crash/_usr_bin_dbus-daemon.1000.crash ERROR: apport (pid 18123) Sat Jan 12 23:07:21 2019: called for pid 17953, signal 6, core limit 18446744073709551615, dump mode 1 ERROR: apport (pid 18123) Sat Jan 12 23:07:21 2019: ignoring implausibly big core limit, treating as unlimited ** Attachment added: "apport.log" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+attachment/5228764/+files/apport.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: Confirmed Status in chromium-browser package in Ubuntu: Invalid Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+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 1805047] Re: [Dell XPS 15 9575] gnome-shell crashes with segfault on suspend-by-lid-close in Wayland session
Oopsie, indeed the crash on lid close is gone after disabling extensions. Even the very act of turning off the overall extension switch in Tweaks crashes the session. Will figure out the culprit extension then. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1805047 Title: [Dell XPS 15 9575] gnome-shell crashes with segfault on suspend-by- lid-close in Wayland session Status in gnome-shell package in Ubuntu: Invalid Bug description: In an X session, suspend and wakeup works when initiated either by lid close or from panel menu. In a Wayland session, suspend and wakeup works only when initiated from panel menu. However, gnome-shell segfaults when suspend is initiated by lid close. When reopening the lid, I am back at the login screen for a new session. (When suspend-on-lid-close is disabled in Gnome Tweaks, gnome-shell and the Wayland session survive the lid close) In dmesg I find the gnome-shell segfault every time, here on the second line: [ 139.420519] wlp2s0: deauthenticating from e0:28:6d:5d:ab:1b by local choice (Reason: 3=DEAUTH_LEAVING) [ 139.964629] gnome-shell[4166]: segfault at fbc8 ip 7fd049223eb8 sp 7ffdda00d6e0 error 5 in libst-1.0.so[7fd0491fd000+2b000] [ 139.964633] Code: 00 00 48 8d 3d 67 78 00 00 e9 44 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d eb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d [ 140.063376] rfkill: input handler enabled [ 140.603550] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 140.723020] [drm] UVD and UVD ENC initialized successfully. [ 140.832956] [drm] VCE initialized successfully. [ 140.951177] PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 25 21:13:44 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (72 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) 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/1805047/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
This is most likely going to be fixed by the changes discussed in bug #1740894 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1797178] Re: gnome-shell activities / application icon touches not fully registering
@Joe, at least in Wayland (did not test in X yet) the touch does not register when I touch anywhere right at the edge of the display. That goes for the whole perimeter of the display. E.g., srollbars of maximized windows on the right, dock launchers on the left, and the Gnome panel menu top right are not triggered in this case. The same goes for the Activities menu, but when I aim e.g. for the middle of Activities or the middle of the panel menu, they are triggered fine. And I can never repro this "flash", either the touch is ignored or the Activities open properly. -- 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/1797178 Title: gnome-shell activities / application icon touches not fully registering Status in gnome-shell package in Ubuntu: New Bug description: On a dell xps 15 2-in-1 (model 9575), the touchscreen mostly works. However, in gnome-shell, touching the top-left 'Activities' menu results in a quick flash of the menu button, but not the launching of the overview. Once in the overview (via mouse/keyboard/swipe-from- left), touching on an application icon (in either the left tray or the applications grid) results in the application icon flashing, but not activating. A long-touch will bring up a menu in which touching on "new window" works properly. Additionally, touching the "show applications" grid button works, as do other components of the top bar, its only the the "activities" menu button and app icon launchers that are "registering" a touch but not activating properly. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:13:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+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 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating
@Joe: Can you confirm that you see the unrotation behavior and the log entry, "gnome-shell[5422]: Failed to apply DRM plane transform 1: Invalid argument" only in a Wayland session? I just realized that this is the case for me. In an X session, the rotation works perfectly whatever the display angle (below or above 180 degrees) and the error does not appear in the log. -- 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/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating Status in gnome-shell package in Ubuntu: Confirmed Status in iio-sensor-proxy package in Ubuntu: Confirmed Bug description: on a dell xps 15 2-in-1 (model 9575), I've enabled iio-sensor-proxy functionality by doing: modprobe intel-ish-ipc echo "8086 a135" > /sys/bus/pci/drivers/intel_ish_ipc/new_id This makes `monitor-sensor` display rotation events, and gnome-shell auto-rotate the screen upon receiving them. However, immediately after rotating, the screen rotates back to its normal orientation (unless I quickly lock rotation), displaying the following in journalctl: Oct 10 09:06:19 taplop gnome-shell[2616]: Failed to apply DRM plane transform 1: Invalid argument Oct 10 09:06:20 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Oct 10 09:06:20 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Oct 10 09:06:20 taplop kernel: [drm] VCE initialized successfully. Oct 10 09:06:27 taplop kernel: amdgpu :01:00.0: GPU pci config reset ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:06:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+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 1805047] [NEW] [Dell XPS 15 9575] gnome-shell crashes with segfault on suspend-by-lid-close in Wayland session
Public bug reported: In an X session, suspend and wakeup works when initiated either by lid close or from panel menu. In a Wayland session, suspend and wakeup works only when initiated from panel menu. However, gnome-shell segfaults when suspend is initiated by lid close. When reopening the lid, I am back at the login screen for a new session. (When suspend-on-lid-close is disabled in Gnome Tweaks, gnome-shell and the Wayland session survive the lid close) In dmesg I find the gnome-shell segfault every time, here on the second line: [ 139.420519] wlp2s0: deauthenticating from e0:28:6d:5d:ab:1b by local choice (Reason: 3=DEAUTH_LEAVING) [ 139.964629] gnome-shell[4166]: segfault at fbc8 ip 7fd049223eb8 sp 7ffdda00d6e0 error 5 in libst-1.0.so[7fd0491fd000+2b000] [ 139.964633] Code: 00 00 48 8d 3d 67 78 00 00 e9 44 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d eb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d [ 140.063376] rfkill: input handler enabled [ 140.603550] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 140.723020] [drm] UVD and UVD ENC initialized successfully. [ 140.832956] [drm] VCE initialized successfully. [ 140.951177] PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 25 21:13:44 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (72 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic package-from-proposed third-party-packages wayland-session -- 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/1805047 Title: [Dell XPS 15 9575] gnome-shell crashes with segfault on suspend-by- lid-close in Wayland session Status in gnome-shell package in Ubuntu: New Bug description: In an X session, suspend and wakeup works when initiated either by lid close or from panel menu. In a Wayland session, suspend and wakeup works only when initiated from panel menu. However, gnome-shell segfaults when suspend is initiated by lid close. When reopening the lid, I am back at the login screen for a new session. (When suspend-on-lid-close is disabled in Gnome Tweaks, gnome-shell and the Wayland session survive the lid close) In dmesg I find the gnome-shell segfault every time, here on the second line: [ 139.420519] wlp2s0: deauthenticating from e0:28:6d:5d:ab:1b by local choice (Reason: 3=DEAUTH_LEAVING) [ 139.964629] gnome-shell[4166]: segfault at fbc8 ip 7fd049223eb8 sp 7ffdda00d6e0 error 5 in libst-1.0.so[7fd0491fd000+2b000] [ 139.964633] Code: 00 00 48 8d 3d 67 78 00 00 e9 44 9c fd ff 0f 1f 40 00 41 57 41 56 41 55 41 54 55 53 48 83 ec 28 48 63 1d eb 74 01 00 48 01 fb <48> 8b 6b 08 48 85 ed 74 17 48 83 c4 28 48 89 e8 5b 5d 41 5c 41 5d [ 140.063376] rfkill: input handler enabled [ 140.603550] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 140.723020] [drm] UVD and UVD ENC initialized successfully. [ 140.832956] [drm] VCE initialized successfully. [ 140.951177] PM: suspend entry (deep) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 25 21:13:44 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (72 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) 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/1805047/+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 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: acpid (Ubuntu) Status: Confirmed => Invalid ** Package changed: linux (Ubuntu) => upower (Ubuntu) ** Changed in: upower (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1791372 Title: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image Status in acpid package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Bug description: Repro: 1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully updated -> Keyboard backlight should come on or change but doesn't. The gnome-shell pop-up icon for the keyboard backlight appears for both keys, but the icon's "progress" bar is not visible. Kernel version is linux-image-4.17.0-9-generic This is the same in X and Wayland session. In case it matters, Nvidia binary drivers are installed but Nvidia is switched off via Prime setting in nvidia-settings. Running with Intel drivers The keyboard backlight works perfectly when booting from the 18.04.1 desktop live image. When turning on light with 18.04.1, it is off again after rebooting into 18.10. (However 18.04.1 seems to freeze when shutting down from menu, I have to hard-shut it off). Most other important Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound) except for the airplane mode key. However the airplane mode key only fails in gnome-shell but works on the console (this is filed as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367) (Not working are a key that seems to mean "display off" and another of unclear purpose that never worked on any laptop I ever saw, maybe "presentation mode" as it seems to depict a flip chart or projection screen). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-9-generic 4.17.0-9.10 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: angela16196 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 22:08:12 2018 InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.17.0-9-generic N/A linux-backports-modules-4.17.0-9-generic N/A linux-firmware1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1791372/+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 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
The update fixed the issue on the Asus ZenBook UX561UD mentioned in comment #10 (i.e. Bug #1791372) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) 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/linux/+bug/1796550/+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 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
** Description changed: On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" - After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. - [Note: either something changed with latest updates from today or I made a mistake before and overlooked the 100%. I get *5* experimental options: - 100, 125, 150, 175, and 200%] + After applying and rebooting, the options offered change to 100, 125, + 150, 175, and 200%. Note that there is no value larger than 200% which + is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+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 1740894] Re: KEY_RFKILL is not passed to userspace
And your fix helps: Still with SRU version installed: $ cat /sys/class/dmi/id/modalias dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: So, edit edit /lib/udev/hwdb.d/60-keyboard.hwdb: evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnXPS159575:pvr* KEYBOARD_KEY_88=unknown $ sudo udevadm hwdb --update $ sudo udevadm trigger evemu-record shows KEY_UNKNOWN: # Waiting for events # E: 0.01 0004 0004 0028 # EV_MSC / MSC_SCAN 28 E: 0.01 0001 001c # EV_KEY / KEY_ENTER0 E: 0.01 # SYN_REPORT (0) -- +0ms E: 3.143316 0004 0004 0136 # EV_MSC / MSC_SCAN 136 E: 3.143316 0001 00f0 0001 # EV_KEY / KEY_UNKNOWN 1 E: 3.143316 # SYN_REPORT (0) -- +3143ms E: 3.143370 0004 0004 0136 # EV_MSC / MSC_SCAN 136 E: 3.143370 0001 00f0 # EV_KEY / KEY_UNKNOWN 0 E: 3.143370 # SYN_REPORT (0) -- +0ms >>> RESULT: The disabling of the airplane mode works now (and enabling still works). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: Thank you very much. With the SRU version installed (I hope that's right): sudo evemu-record Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Sleep Button /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: Wacom HID 486A Pen /dev/input/event6: Wacom HID 486A Finger /dev/input/event7: Intel HID events /dev/input/event8: Intel Virtual Button driver /dev/input/event9: Intel HID 5 button array /dev/input/event10: Integrated_Webcam_HD: Integrate /dev/input/event11: Integrated_Webcam_HD: Integrate /dev/input/event12: DELL080D:00 06CB:7A13 Touchpad /dev/input/event13: Dell WMI hotkeys /dev/input/event14: Video Bus /dev/input/event15: HDA Intel PCH Headphone Mic /dev/input/event16: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event17: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event18: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event19: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event20: HDA Intel PCH HDMI/DP,pcm=10 Select the device event number [0-20]: 4 # EVEMU 1.3 # Kernel: 4.18.0-11-generic # DMI: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: # Input device name: "AT Translated Set 2 keyboard" # Input device ID: bus 0x11 vendor 0x01 product 0x01 version 0xab41 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 1 (KEY_ESC) # Event code 2 (KEY_1) # Event code 3 (KEY_2) # Event code 4 (KEY_3) # Event code 5 (KEY_4) # Event code 6 (KEY_5) # Event code 7 (KEY_6) # Event code 8 (KEY_7) # Event code 9 (KEY_8) # Event code 10 (KEY_9) # Event code 11 (KEY_0) # Event code 12 (KEY_MINUS) # Event code 13 (KEY_EQUAL) # Event code 14 (KEY_BACKSPACE) # Event code 15 (KEY_TAB) # Event code 16 (KEY_Q) # Event code 17 (KEY_W) # Event code 18 (KEY_E) # Event code 19 (KEY_R) # Event code 20 (KEY_T) # Event code 21 (KEY_Y) # Event code 22 (KEY_U) # Event code 23 (KEY_I) # Event code 24 (KEY_O) # Event code 25 (KEY_P) # Event code 26 (KEY_LEFTBRACE) # Event code 27 (KEY_RIGHTBRACE) # Event code 28 (KEY_ENTER) # Event code 29 (KEY_LEFTCTRL) # Event code 30 (KEY_A) # Event code 31 (KEY_S) # Event code 32 (KEY_D) # Event code 33 (KEY_F) # Event code 34 (KEY_G) # Event code 35 (KEY_H) # Event code 36 (KEY_J) # Event code 37 (KEY_K) # Event code 38 (KEY_L) # Event code 39 (KEY_SEMICOLON) # Event code 40 (KEY_APOSTROPHE) # Event code 41 (KEY_GRAVE) # Event code 42 (KEY_LEFTSHIFT) # Event code 43 (KEY_BACKSLASH) # Event code 44 (KEY_Z) # Event code 45 (KEY_X) # Event code 46 (KEY_C) # Event code 47 (KEY_V) # Event code 48 (KEY_B) # Event code 49 (KEY_N) # Event code 50 (KEY_M) # Event code 51 (KEY_COMMA) # Event code 52 (KEY_DOT) # Event code 53 (KEY_SLASH) # Event code 54 (KEY_RIGHTSHIFT) # Event code 55 (KEY_KPASTERISK) # Event code 56 (KEY_LEFTALT) # Event code 57 (KEY_SPACE) # Event code 58 (KEY_CAPSLOCK) # Event code 59 (KEY_F1) # Event code 60 (KEY_F2) # Event code 61 (KEY_F3) # Event code 62 (KEY_F4) # Event code 63 (KEY_F5) # Event code 64 (KEY_F6) # Event code 65 (KEY_F7) # Event code 66 (KEY_F8) # Event code 67 (KEY_F9) # Event code 68 (KEY_F10) # Event code 69 (KEY_NUMLOCK) # Event code 70 (KEY_SCROLLLOCK) # Event code 71 (KEY_KP7) # Event code 72 (KEY_KP8) # Event code 73 (KEY_KP9) # Event code 74 (KEY_KPMINUS) # Event code 75 (KEY_KP4) # Event code 76 (KEY_KP5) # Event code 77 (KEY_KP6) # Event code 78 (KEY_KPPLUS) # Event code 79 (KEY_KP1) # Event code 80 (KEY_KP2) # Event code 81 (KEY_KP3) # Event code 82 (KEY_KP0) # Event code 83 (KEY_KPDOT) # Event code 85 (KEY_ZENKAKUHANKAKU) # Event code 86 (KEY_102ND) # Event code 87 (KEY_F11) # Event code 88 (KEY_F12) # Event code 89 (KEY_RO) # Event code 90 (KEY_KATAKANA) # Event code 91 (KEY_HIRAGANA) # Event code 92 (KEY_HENKAN) # Event code 93 (KEY_KATAKANAHIRAGANA) # Event code 94 (KEY_MUHENKAN) # Event code 95 (KEY_KPJPCOMMA) # Event code 96 (KEY_KPENTER) # Event code 97 (KEY_RIGHTCTRL) # Event code 98 (KEY_KPSLASH) # Event code 99
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
As an additional check I once more installed the SRU version (and rebooted): $ apt-cache policy xkb-data xkb-data: Installed: 2.23.1-1ubuntu1.18.10.1 Candidate: 2.23.1-1ubuntu1.18.10.1 Version table: *** 2.23.1-1ubuntu1.18.10.1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu cosmic-proposed/main i386 Packages 100 /var/lib/dpkg/status 2.23.1-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu cosmic/main i386 Packages Now the problem occurs again. I.e. the first key press still enables the airplane mode just like with the non-SRU version, but the second key press fails to disable the mode: 1.Press key (STILL OK) -> Airplane mode enables. The airplane mode icon appears in the Gnome panel. Wifi turns off. BT turns off. 2. Press key again (THIS IS NOW BROKEN) -> Airplane mode appears to disable momentarily: For a short moment the airplane mode icon disappears from the Gnome panel. HOWEVER, then the airplane mode immediately and automatically re-enables. The airplane mode icon reappears in the panel, Wifi and BT remain off. - does that command works to get out of airplane mode? (Command: gdbus call etc.) Yes, this still works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastian: I reinstalled the non-SRU version: $ apt-cache policy xkb-data xkb-data: Installed: 2.23.1-1ubuntu1 Candidate: 2.23.1-1ubuntu1.18.10.1 Version table: 2.23.1-1ubuntu1.18.10.1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu cosmic-proposed/main i386 Packages *** 2.23.1-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status - on a stock XPS with the non-SRU version, what keycode do you get in xev I press Fn+Pos1 and I get: FocusIn event, serial 39, synthetic NO, window 0x201, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 39, synthetic NO, window 0x0, keys: 4294967246 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 MappingNotify event, serial 39, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyPress event, serial 39, synthetic NO, window 0x201, root 0x1ce, subw 0x0, time 272898, (-557,525), root:(1274,1553), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 39, synthetic NO, window 0x201, root 0x1ce, subw 0x0, time 272898, (-557,525), root:(1274,1553), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False - on a stock cosmic what happens when you use the key 1.Press key -> Airplane mode enables. The airplane mode icon appear in the Gnome panel. Wifi turns off. BT turns off 2. Press key again -> Airplane mode disables. The airplane mode icon disappears from the Gnome panel. Wifi turns on. BT turns on. I.e., it works perfectly. Every time I press the key, the airplane mode changes into the other state (on or off) - does that command works to get out of airplane mode? (Command: gdbus call etc.) Yes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
To be clear, the above debugging output is with xkb-data 2.23.1-1ubuntu1.18.10.1 installed and therefore the DISabling of airplane mode by the dedicated key being broken $ aptitude show xkb-data Package: xkb-data Version: 2.23.1-1ubuntu1.18.10.1 State: installed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: That's the thing, on the Dell XPS 15 9575 there IS a regression with xkb-data 2.23.1-1ubuntu1.18.10.1. On this machine, the airplane mode key worked perfectly out-of-the-box (i.e., the key enabled AND disabled the airplane mode) with the development version of Cosmic, using xkb-data 2.23. See my comment #13 further up in this bug. Here's the debug output for gnome-settings-daemon: [*** Airplane mode is off, Wifi and BT are on ***] /usr/lib/gnome-settings-daemon/gsd-rfkill -v (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 'WLAN' (idx=1): soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 'BLUETOOTH' (idx=11): soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added Bluetooth rfkill with ID 11 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.185: Registered client at path /org/gnome/SessionManager/Client29 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.187: Opened rfkill-input inhibitor. [*** Here I am pressing the airplane mode key to enable Airplane mode > Wifi/BT goes off ***] (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: RFKILL event: idx 1 type 1 (WLAN) op 2 (CHANGE) soft 1 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: Changed rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.352: RFKILL event: idx 11 type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.353: Changed Bluetooth rfkill with ID 11 [*** Here I am pressing the airplane mode key again to DISable Airplane mode > Wifi/BT should go back on. This fails and the airplane mode re- engages immediately as described ***] (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 1 type 1 (WLAN) op 2 (CHANGE) soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 11 type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed Bluetooth rfkill with ID 11 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 1 type 1 (WLAN) op 2 (CHANGE) soft 1 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 11 type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed Bluetooth rfkill with ID 11 [*** Here I am pressing DISabling Airplane mode from the Gnome panel menu > Wifi/BT goes back on. This works ***] (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 1 type 1 (WLAN) op 2 (CHANGE) soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 11 type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed Bluetooth rfkill with ID 11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: Yes, enable/disable airplane mode works from gnome-control-center. It also works to disalbe it from the Gnome panel manu. (Remember that it previously also could be enabled and disabled with the dedicated Fn+Pos1 key as long as xkb-data was 2.23). As for the verification-failed: I obviously accept the maintainers' decision. If you think that the xkb-data update is the right path forward despite this regression, by all means please go ahead. It would be good to fix the regression though. It seems that a very similar machine is sold as a Developer Edition with Ubuntu (Dell Precision 5530, https://bartongeorge.io/2018/05/24/welcome-the-new-dell-precision- developer-editions/) The failed disable of the airplane mode (i.e., failed re-enable of Wifi/BT) leaves this in journalctl: Nov 06 00:00:49 chronic systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 06 00:00:49 chronic NetworkManager[777]: [1541458849.3593] manager: rfkill: WiFi now enabled by radio killswitch Nov 06 00:00:49 chronic systemd[1]: Started Load/Save RF Kill Switch Status. Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 118809 Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 90118 Nov 06 00:00:50 chronic kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2459] device (wlp2s0): device not up after timeout! Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2462] manager: rfkill: WiFi now disabled by radio killswitch Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2514] manager: rfkill: WWAN hardware radio set enabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2516] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2584] manager: rfkill: WWAN hardware radio set disabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2586] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1797178] Re: gnome-shell activities / application icon touches not fully registering
FWIW and FYI, I cannot repro this on Cosmic with Dell XPS 15 9575 -- 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/1797178 Title: gnome-shell activities / application icon touches not fully registering Status in gnome-shell package in Ubuntu: New Bug description: On a dell xps 15 2-in-1 (model 9575), the touchscreen mostly works. However, in gnome-shell, touching the top-left 'Activities' menu results in a quick flash of the menu button, but not the launching of the overview. Once in the overview (via mouse/keyboard/swipe-from- left), touching on an application icon (in either the left tray or the applications grid) results in the application icon flashing, but not activating. A long-touch will bring up a menu in which touching on "new window" works properly. Additionally, touching the "show applications" grid button works, as do other components of the top bar, its only the the "activities" menu button and app icon launchers that are "registering" a touch but not activating properly. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:13:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Gunnar: Sure, happy to sacrifice my airport key :) New bug #1800727 for the XPS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1800727] [NEW] [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed
Public bug reported: Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in order to pass KEY_RFKILL to userspace. Despite the issue described in bug #1740894, on Dell XPS 15 9575 the airplane mode key actually worked flawlessly out-of-the-box after installing Cosmic at beginning of September, using xkb-data 2.23. Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to the following issue: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xkb-data 2.23.1-1ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 22:13:45 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu InstallationDate: Installed on 2018-09-13 (47 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic package-from-proposed ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1800727 Title: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed Status in xkeyboard-config package in Ubuntu: New Bug description: Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in order to pass KEY_RFKILL to userspace. Despite the issue described in bug #1740894, on Dell XPS 15 9575 the airplane mode key actually worked flawlessly out-of-the-box after installing Cosmic at beginning of September, using xkb-data 2.23. Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to the following issue: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xkb-data 2.23.1-1ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 22:13:45 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu InstallationDate: Installed on 2018-09-13 (47 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
A few weeks ago I submitted the similar Bug #1791367 for airplane mode key not working on Asus ZenBook Flip UX561UD. We did some tests updating xkb-data via ppa by Gunnar Hjalmarsson (gunnarhj). This update worked on the Asus, but broke the airplane mode key on Dell XPS 15 9575 2-in-1 where it had worked out-of-the-box with Cosmic and xkb-data 2.23. Now tested the update to 2.23.1 from -proposed and am seeing the same issue on the Dell as in #1791367: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. I can test the Asus as well in a few days, but based on previous results I expect that it will work there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
Some feedback for Cosmic: FWIW, I can confirm that the update did NOT break the keyboard backlight key on Dell XPS 15 9575, where it had already worked flawlessly out-of- the-box with Cosmic since installation in early September (contrary to the bug description above stating that "keyboard backlight control keys don't work in cosmic") At the time also submitted the similar bug #1791372, "Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image". I can test this update on the Asus as well but cannot report result before Sunday, Oct 4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Committed Status in upower source package in Cosmic: Fix Committed Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) 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/linux/+bug/1796550/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Added comment to the other bug #1740894: Same issue on the Dell as we had here, the new update to 2.23-1 from -proposed breaks disabling the airplane mode on the Dell XPS 15 9575. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1740894] Re: KEY_RFKILL is not passed to userspace
** Tags removed: verification-needed-cosmic ** Tags added: verification-failed-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1407882] Re: Firefox won't automatically adjust the toolbar / tab and content size under high resolution environment in Ubuntu 14.04.1
** Changed in: firefox (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1407882 Title: Firefox won't automatically adjust the toolbar / tab and content size under high resolution environment in Ubuntu 14.04.1 Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 14.04.1 + update + AMD video driver on a 3840x2160 high-resolution laptop 2. Boot to desktop with the highest resolution (3840x2160) 2. Open Firefox browser, ,make sure that it is on the latest version (34.0) Actual results: Toolbar / tab is too small, and the content size needs to be manually enlarged. Expected results: Toolbar / tab and the content size should be larger in this high resolution environment. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 34.0+build2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1664 F pulseaudio /dev/snd/controlC1: ubuntu 1664 F pulseaudio BuildID: 20141127111021 CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Channel: Unavailable CurrentDesktop: Unity Date: Tue Jan 6 02:48:38 2015 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 10.101.46.1 dev wlan0 proto static 10.101.46.0/24 dev wlan0 proto kernel scope link src 10.101.46.53 metric 9 Locales: extensions.sqlite corrupt or missing Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) VLC Multimedia Plugin (compatible Videos 3.10.1) - /usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla) DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so (totem-mozilla) Windows Media Player Plug-in 10 (compatible; Videos) - /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla) QuickTime Plug-in 7.6.6 - /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=34.0/20141127111021 RelatedPackageVersions: rhythmbox-mozilla 3.0.2-0ubuntu2 totem-mozilla 3.10.1-1ubuntu4 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: BBE4C1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rnBBE4C1:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1407882/+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 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
I cannot confirm this on my machine. I do not know if what I see it intended behavior, but what I see is still not what either the Gnome 2.28 release notes or the Ubuntu help say should happen. When I enable the OSK in universal access, the OSK opens way too often but not always when it should. This is same in X or Wayland: - Opens when typing on keyboard into Activities or Applications search box. (I don't know if this is good behavior for universal access, but it is not good behavior for general touch use: When I type on the keyboard I don't need an OSK. ) - Opens when I touch into Activities or Applications search box. (OK) - Opens when I start a gnome-term even before I touch it or type into it. But it does not open when I switch focus and touch into an already-open gnome-term. (Not OK) - Does not open with Firefox or Chrome. (May be technically unavoidable, but then requires a way to open the OSK on demand) - In Wayland, swiping up of from the bottom of the screen opens OSK. This does not work in X and I don't see another way) Turning OSK off in Universal access, the behavior becomes better for general touch use as the OSK does not uselessly appear when typing, only when touching - at least in those cases when it does. Otherwise the behavior is unchanged compared to being on in Universal Access. -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X Status in gnome-shell package in Ubuntu: Confirmed Bug description: The new OSK does not auto-activate reliably by selecting any text widget as the Gnome 3.28 release notes claim: "The new keyboard automatically activates when a text area is selected, ..." -- https://help.gnome.org/misc/release-notes/3.28/ This does not work with text widgets of alien toolkits (Chrome, Firefox, Qt, ...). Even in Gnome this does not work everywhere, for me (Cosmic, 3.30) it does only for the search boxes of Activity and Application menus, not anywhere else that I can find. Not even epiphany, gedit, or other first-class Gnome applications. It is the same in Ubuntu 18.04 according to Bug #1760399 (this report is also referenced as evidence further down). Does this need a separate bug report? Is it a bug in Gnome libraries, Gtk libraries, or in each individual application where it does not work who is using these libraries? Hence it is necessary to have a way for manual activation. This is possible in Wayland by swiping up from bottom of screen on a touch screen, but there is no UI hint for this and I banged my head bloody until I stumbled on the solution. In the default X session the swipe does not work and hence it cannot be manually activated at all. The Ubuntu help for 18.04.1 describes it incorrectly/incompletely and contributes to the confusion. Bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 I refer you to user confusion on the following links, note that the previously available answers on Askubuntu all provide incorrect or incomplete solutions: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 (I added a description in comment #10 earlier today) Askubuntu (I added new answers earlier today): https://askubuntu.com/questions/1057485/ubuntu-18-04-no-on-screen-keyboard/1073461#1073461 https://askubuntu.com/questions/1035622/screen-keyboard-not-showing-up-in-firefox-ubuntu-18-04/1073756#1073756 https://askubuntu.com/questions/1036983/cannot-consistently-bring-up-on-screen-keyboard/1073754#1073754 https://askubuntu.com/questions/1058176/how-to-make-ubuntu-18-04-on-screen-keyboard-work-with-google-chrome/1073743#1073743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 9 23:04:26 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2185 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+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 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
Thanks Efthimios. I am still a little unclear about what the intended behavior is. Should it auto open when touching a text field e.g. in Chrome? And are you using X or Wayland and it you enable the OSK in Universal Access? Thanks. FWIW, for me on Cosmic it is still as described in the description at least on Wayland, I did not try X recently -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X Status in gnome-shell package in Ubuntu: Confirmed Bug description: The new OSK does not auto-activate reliably by selecting any text widget as the Gnome 3.28 release notes claim: "The new keyboard automatically activates when a text area is selected, ..." -- https://help.gnome.org/misc/release-notes/3.28/ This does not work with text widgets of alien toolkits (Chrome, Firefox, Qt, ...). Even in Gnome this does not work everywhere, for me (Cosmic, 3.30) it does only for the search boxes of Activity and Application menus, not anywhere else that I can find. Not even epiphany, gedit, or other first-class Gnome applications. It is the same in Ubuntu 18.04 according to Bug #1760399 (this report is also referenced as evidence further down). Does this need a separate bug report? Is it a bug in Gnome libraries, Gtk libraries, or in each individual application where it does not work who is using these libraries? Hence it is necessary to have a way for manual activation. This is possible in Wayland by swiping up from bottom of screen on a touch screen, but there is no UI hint for this and I banged my head bloody until I stumbled on the solution. In the default X session the swipe does not work and hence it cannot be manually activated at all. The Ubuntu help for 18.04.1 describes it incorrectly/incompletely and contributes to the confusion. Bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 I refer you to user confusion on the following links, note that the previously available answers on Askubuntu all provide incorrect or incomplete solutions: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 (I added a description in comment #10 earlier today) Askubuntu (I added new answers earlier today): https://askubuntu.com/questions/1057485/ubuntu-18-04-no-on-screen-keyboard/1073461#1073461 https://askubuntu.com/questions/1035622/screen-keyboard-not-showing-up-in-firefox-ubuntu-18-04/1073756#1073756 https://askubuntu.com/questions/1036983/cannot-consistently-bring-up-on-screen-keyboard/1073754#1073754 https://askubuntu.com/questions/1058176/how-to-make-ubuntu-18-04-on-screen-keyboard-work-with-google-chrome/1073743#1073743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 9 23:04:26 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2185 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
No worries, as the Dell shows it seems not a no-brainer anyway, so better to postpone. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating
Thank you. I had written bug #1792813 about the sensors not being found with kernel 4.18. This is fixed in the mainline 4.19 (see the other report). The incorrect automatic back rotation also happens with 4.19. However, note that what exactly happens depends on whether the keyboard vs display angle is smaller or larger than 180 degrees. I am copying my description from the other bug with some edits for brevity and to fix errors: monitor-sensor output detects the correct orientation in all attempts. When the screen auto-rotates back, monitor-sensor does NOT output a switch to "normal". So I suppose the sensor outputs remain correctly detected and the switching back happens elsewhere. The issue may be connected to a hardware quirk in how the rotation is implemented on the Dell XPS, which similarly also occurs in Windows (https://www.dell.com/community/XPS/Dell-XPS-13-9365-Rotation-lock-unavailable-grayed-out-EXPLAINED/td-p/6075400): * Laptop mode, i.e. keyboard-to-screen angle SMALLER than 180 degrees: In Windows, this automatically engages the rotation lock, i.e. the screen does not rotate at all. * Tent/tablet mode, i.e. keyboard-to-screen angle LARGER than 180 degrees: In Windows, this releases the rotation lock automatically. In Ubuntu, the rotation lock in the Gnome panel does NOT automatically engage if the angle is smaller than 180 degrees, but rotation behavior depends on angle: * Angle SMALLER than 180: - Orientation "left-up": screen rotates to portrait correctly, but immediately switches back to normal. - Orientation "right-up": screen rotates to portrait correctly and in most attempts stays like this, but occasionally it immediately switches back to normal. - Orientation "bottom-up": screen rotates rotates upside-down correctly, but immediately switches back to normal. - Orientation "normal": screen always rotates back correctly (if it didn't automatically switch back anyway). * Angle LARGER than 180: - Orientation "left-up": screen rotates to portrait correctly and in most attempts stays like this, but occasionally it immediately switches back to normal. - Orientation "right-up": screen rotates to portrait correctly and apparently randomly either stays like this or immediately switches back to normal. - Orientation "bottom-up": screen rotates rotates upside down correctly most of the time (but occasionally doesn't). - Orientation "normal": screen always rotates back correctly (if it didn't automatically switch back anyway). So the "left-up" and "right-up" behaviors seem somewhat (but not entirely) swapped depending on the keyboard-screen angle. -- 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/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating Status in gnome-shell package in Ubuntu: Confirmed Status in iio-sensor-proxy package in Ubuntu: Confirmed Bug description: on a dell xps 15 2-in-1 (model 9575), I've enabled iio-sensor-proxy functionality by doing: modprobe intel-ish-ipc echo "8086 a135" > /sys/bus/pci/drivers/intel_ish_ipc/new_id This makes `monitor-sensor` display rotation events, and gnome-shell auto-rotate the screen upon receiving them. However, immediately after rotating, the screen rotates back to its normal orientation (unless I quickly lock rotation), displaying the following in journalctl: Oct 10 09:06:19 taplop gnome-shell[2616]: Failed to apply DRM plane transform 1: Invalid argument Oct 10 09:06:20 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Oct 10 09:06:20 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Oct 10 09:06:20 taplop kernel: [drm] VCE initialized successfully. Oct 10 09:06:27 taplop kernel: amdgpu :01:00.0: GPU pci config reset ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:06:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+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 1407882] Re: Firefox won't automatically adjust the toolbar / tab and content size under high resolution environment in Ubuntu 14.04.1
I am not the OP, but I have the same resolution, 3840x2160 on 15.6" display. Using Firefox 63 (as of today's update) on Cosmic, I still have to set layout.css.devPixelsPerPx to 2.5 in about:config for a usable Firefox. In both X and Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1407882 Title: Firefox won't automatically adjust the toolbar / tab and content size under high resolution environment in Ubuntu 14.04.1 Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Install Ubuntu 14.04.1 + update + AMD video driver on a 3840x2160 high-resolution laptop 2. Boot to desktop with the highest resolution (3840x2160) 2. Open Firefox browser, ,make sure that it is on the latest version (34.0) Actual results: Toolbar / tab is too small, and the content size needs to be manually enlarged. Expected results: Toolbar / tab and the content size should be larger in this high resolution environment. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: firefox 34.0+build2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1664 F pulseaudio /dev/snd/controlC1: ubuntu 1664 F pulseaudio BuildID: 20141127111021 CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Channel: Unavailable CurrentDesktop: Unity Date: Tue Jan 6 02:48:38 2015 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 10.101.46.1 dev wlan0 proto static 10.101.46.0/24 dev wlan0 proto kernel scope link src 10.101.46.53 metric 9 Locales: extensions.sqlite corrupt or missing Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) VLC Multimedia Plugin (compatible Videos 3.10.1) - /usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla) DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so (totem-mozilla) Windows Media Player Plug-in 10 (compatible; Videos) - /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla) QuickTime Plug-in 7.6.6 - /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=34.0/20141127111021 RelatedPackageVersions: rhythmbox-mozilla 3.0.2-0ubuntu2 totem-mozilla 3.10.1-1ubuntu4 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: BBE4C1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rnBBE4C1:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1407882/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
No stop, disregard, SORRY!!! I don't know how, but I messed up, the update was not installed and I misread some check. Now I definitely do have the update installed and IT WORKS on the Asus. It still breaks the Dell though :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
I see the same behavior on a display with the same dimensions on a different laptop: Asus ZenBook Flip 15 UX561UD 15.6 inch 16:9, 3840 x 2160 pixel, 282 PPI On both the Dell and the Asus: Without the experimental setting, options offered are 100, 200 (too small), 300 (too large), 400%. With the experimental setting, options are 100, 125, 150, 175, 200 (still too small) ** Description changed: On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" - After applying and rebooting, the options offered change to 125, 150, - 175, and 200%. Note that there is no value larger than 200% which is too - small on this display at least for me. + After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. + [Note: either something changed with latest updates from today or I made a mistake before and overlooked the 100%. I get *5* experimental options: + 100, 125, 150, 175, and 200%] In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. [Note: either something changed with latest updates from today or I made a mistake before and overlooked the 100%. I get *5* experimental options: 100, 125, 150, 175, and 200%] In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago)
[Desktop-packages] [Bug 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Test result on the Asus ZenBook Flip UX561UD: Sadly no improvement with the upgraded xkb-data 2.24 from the ppa. Behavior is completely the same as with the standard 2.23.1, the airplane mode key does not work in gnome-shell but works on the console. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: To the release team: Asking for FFe since it appears to be a good idea to fix this bug through an upgrade to latest version of xkeyboard- config rather than just patching a single upstream commit. Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu /xkeyboard-config [Original description] Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
** Description changed: On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available - scaling options in the Gnome 3.30.1 (Cosmic) display settings are - limited to 100, 200, 300, and 400%. This is insufficient as 200% is too - small and 300% is too large. The missing fractional scaling options are - dealt with in bug #1687246. However, the currently available - experimental feature to enable fractional scaling (provided in the bug - description of #1687246) does not solve the problem on my machine: + scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, + on Cosmic) display settings are limited to 100, 200, 300, and 400%. This + is insufficient as 200% is too small and 300% is too large. The missing + fractional scaling options are dealt with in bug #1687246. However, the + currently available experimental feature to enable fractional scaling + (provided in the bug description of #1687246) does not solve the problem + on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 125, 150, 175, and 200%. Note that there is no value larger then 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) therefore advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 125, 150, - 175, and 200%. Note that there is no value larger then 200% which is too + 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) therefore advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available scaling options in the gnome-control-center (version: 1:3.30.0-0ubuntu1, on Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After
[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
Daniel, new gnome-control-center bug #1795483 -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: In Progress Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. Workaround == You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS by running the following command in a terminal and then restarting your computer. Note that this is an experimental feature and is not fully supported by either Ubuntu or GNOME. gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After restarting your computer, you should find additional scale options in Settings > Devices > Displays. If you change your mind and want to get back to supported status, run: gsettings reset org.gnome.mutter experimental-features To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+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 1795483] [NEW] Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
Public bug reported: On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available scaling options in the Gnome 3.30.1 (Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 125, 150, 175, and 200%. Note that there is no value larger then 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) therefore advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) Status in gnome-control-center package in Ubuntu: New Bug description: On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available scaling options in the Gnome 3.30.1 (Cosmic) display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 125, 150, 175, and 200%. Note that there is no value larger then 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) therefore advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+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 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Anything I can do? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: To the release team: Asking for FFe since it appears to be a good idea to fix this bug through an upgrade to latest version of xkeyboard- config rather than just patching a single upstream commit. Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu /xkeyboard-config [Original description] Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
For my 15" display with 3840*2160, without the workaround I get 100, 200 (too small), 300 (too large), and 400. Is it intentional that with the experimental workaround from the first comment enabled, I have 125, 150, 175 and 200% but nothing above it? The maximum of 200% is too small and I use a 1.20 font scaling in Tweaks, so I'd be looking for an option to scale by 240%. -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: In Progress Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. Workaround == You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS by running the following command in a terminal and then restarting your computer. Note that this is an experimental feature and is not fully supported by either Ubuntu or GNOME. gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After restarting your computer, you should find additional scale options in Settings > Devices > Displays. If you change your mind and want to get back to supported status, run: gsettings reset org.gnome.mutter experimental-features To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+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 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Sorry for typo in previous comment, should have been OFF at the end: Updated 2.24-0ubuntu1, rebooted: 1. Press Fn+Pos1 -> Works same as before. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", icon remains in panel, Wifi and BT remain *OFF* [not "on"] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: To the release team: Asking for FFe since it appears to be a good idea to fix this bug through an upgrade to latest version of xkeyboard- config rather than just patching a single upstream commit. Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu /xkeyboard-config [Original description] Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Thanks, Gunnar. I could not test it yet on the Asus from this bugreport, it will take a few days until I can get my hands on this one. However, I tested with my own Dell XPS 15 9575 and it breaks the Airplane mode switch there, which works perfectly with the standard xkb- data=2.23.1-1ubuntu1 from Cosmic: 2.23.1-1ubuntu1: 1. Press Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Works. Pop-up says "Airplane mode disabled", icon disappears from panel, Wifi and BT are on. Updated 2.24-0ubuntu1, rebooted: 1. Press Fn+Pos1 -> Works same as before. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", icon remains in panel, Wifi and BT remain on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Triaged Bug description: To the release team: Asking for FFe since it appears to be a good idea to fix this bug through an upgrade to latest version of xkeyboard- config rather than just patching a single upstream commit. Proposal available at https://launchpad.net/~gunnarhj/+archive/ubuntu /xkeyboard-config [Original description] Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK
[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Upstream: The NoSymbol (rather than XF86RFKill) tells me that this is exactly the issue. Closing as a downstream issue. For downstream: The reason that the regression happened is commit 3810072d rfkill: Add property to Rfkill helper to inhibit kernel handling https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/3810072d2b3776c1183303adc8cd9f50732841a2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Following upstream suggestion ** Package changed: gnome-settings-daemon (Ubuntu) => xkeyboard-config (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: New Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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
