[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
Reproduced again: 1. Logged out from Xorg session 2. Logged in again with default of Xorg selected, it logs into Wayland 3. Logged out once more and clicked the selected Xorg menu entry again. 4. Logged back in - now into Xorg. 5. Created the attached journal.txt. There are no crash reports in /var/crash and nothing relevant on the whoopsie website for my ID, the last one there is from June before upgrade and different anyway. If I understand it right I don't have to do the apport workaround thing as this is not a stable release. Let me know if otherwise pls. Sorry that my tardiness caused unhappiness, I was just busy and not abandoning Ubuntu after 15 years due to a minor bug in a beta :) ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+attachment/5531770/+files/journal.txt ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945008] Re: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect
** Summary changed: - Log in with Wayland although Xorg looks selected in session menu. Need to reselect + Logs in with Wayland although Xorg looks selected in session menu. Need to reselect -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1945008 Title: Logs in with Wayland although Xorg looks selected in session menu. Need to reselect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1945008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904237/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu
Desktop Bugs, 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu
Desktop Bugs, 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu
Desktop Bugs, 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu
Desktop Bugs, 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807276 Title: Cannot open Onscreen Keyboard in Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1807276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1846255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
(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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
I 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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1720089 Title: Desktop isn't part of "places" (left bar) in artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1720089 Title: Desktop isn't part of "places" (left bar) in artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805047/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805047/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 app
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795483/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 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 Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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)
>From the upstream report: "A possible explanation would be that gnome-settings-daemon is not handling one of the keys that it should be handling. And gnome-settings-daemon also disables the kernels handling of the RFKill keys at the same time. What you could do: Check which key is emitted using "xev" Check the low level key that is fired using "evemu-record" (you'll need to try different input devices) To be honest, the most likely explanation is that the following xkeyboard-config bugfix has not been merged into ubuntu yet: https://bugs.freedesktop.org/show_bug.cgi?id=100970, patch https://patchwork.freedesktop.org/patch/155965/ which should be in 2.24." And: "Just to make this clear. The above means that this is likely a downstream bug in Ubuntu which needs to upgrade (or patch) xkeyboard-config. i.e. if "XF86RFKill" is not mapped, then xkeyboard-config is outdated and the symptoms you describe fit perfectly." The "xev" output that I get is: KeyPress event, serial 38, synthetic NO, window 0x381, root 0x1a8, subw 0x0, time 1318232, (131,-31), root:(1962,997), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 38, synthetic NO, window 0x381, root 0x1a8, subw 0x0, time 1318232, (131,-31), root:(1962,997), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ** Bug watch added: freedesktop.org Bugzilla #100970 https://bugs.freedesktop.org/show_bug.cgi?id=100970 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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)
As per analysis result in upstream report ** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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)
In the upstream report for gnome-shell (https://gitlab.gnome.org/GNOME /gnome-shell/issues/555) some analysis steps were kindly provided. It seems that the actual cause is that gnome-settings-daemon's rfkill plugin fails to turn on airplane mode. Following the instructions, I can turn it on with the suggested test command: gdbus call --session --dest org.gnome.SettingsDaemon.Rfkill \ --object-path /org/gnome/SettingsDaemon/Rfkill \ --method org.freedesktop.DBus.Properties.Set \ org.gnome.SettingsDaemon.Rfkill AirplaneMode '' '' turns if off again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
Sorry my earlier removal of the tag was unintentional, readding ** Tags added: universalaccess -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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)
Got instructions from upstream. Probably not a gnome-shell issue but I will need a few days to run tests and figure out where the problem ist ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726692] Re: Screen backlight adjustment stopped working on MacBook Pro 5, 4 and other hardware
** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/726692 Title: Screen backlight adjustment stopped working on MacBook Pro 5,4 and other hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/726692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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)
Filed as https://gitlab.gnome.org/GNOME/gnome-shell/issues/555 ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
They had both been there from the start, but I typoed it into an ii when adding "cosmic" tag and so I restored the original -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 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
** Description changed: 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 reprot is also reference as evidence further down). + 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 reference 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 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 documentation for 18.04.1 describes it incorrectly 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) ** Description changed: 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 reference as evidence further down). + 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 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 documentation for 18.04.1 describes it incorrectly and contributes to the confusion. Bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 I refer you to
[Bug 1740599] Re: Selecting multiple files and dragging them to file manager is broken in a Wayland session
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1740599 Title: Selecting multiple files and dragging them to file manager is broken in a Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1740599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791551] [NEW] Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
Public bug reported: 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 reprot is also reference 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 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 documentation for 18.04.1 describes it incorrectly 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) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic cosmic osk touch ** Tags added: cosmic osk touch ** Summary changed: - Activation of new on-screen keyboard of Gnome 3.28 is difficult to discover in Wayland and not possible in X + Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X ** Description changed: - The new OSK does not auto-activate reliably by selecting any text widget as the Gnome 3.29 release notes claim: + 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 Hence it is necessary to have a way for manual activation. This is possible in Wayland by swiping up 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 documentation for 18.04.1 describes it incorrectly 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-consiste
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
Bug report for discoverability: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
Bug report for Ubuntu documentation: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
** Tags removed: universalaccess -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
Duh. In the above comment, it should have been: "1. (**Chrome** [not Gnome], Firefox, Qt, whatever other toolkits...) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
So after much hair pulling I contacted the author of the above mentioned Gnome extension and he set me on the right track (thank you): 1. Auto-summon of OSK only works with application/toolkit support. Text widgets in alien (non-Gnome or non-Gtk?) toolkits don't summon the OSK (Gnome, Firefox, Qt, whatever other toolkits; I don't know if this is even standardized by freedesktop.org. 2. Because of alien toolkits there is always a need to summon on demand. Since Gnome 3.28 in Ubuntu 18.04, you can summon on a touch screen by swiping up from the bottom of the screen. However, this ONLY works in a Wayland session, not in X. I can confirm that it does. None of this is described in the Gnome 3.28 release notes or the Ubuntu 18.04 help. These are clearly documentation bugs. 3. Judging by the confusion int his bug report and the many questions on Askubuntu,com, it seems that the swiping up eluded even those users who have access to the feature because they use Wayland. Quite clearly this is not sufficiently discoverable, which IMHO is a bug. (Of course this is not helped by the buggy docs) 4. The Gnome extension to summon on-demand (https://extensions.gnome.org/extension/1061/on-screen-keyboard-button/) does NOT work with touch in Ubuntu 18.04 (Gnome 3.28) according to the author, and neither does it in Cosmic (3.30). It works with the mouse but this is awkward to say the least. The author will hopefully be able to look into it but it may take some time. 5. I don't know why in Gnome 3.30 (Cosmic) the auto-summon only works for Activities and Applications menus search boxes, and not elsewhere in Gnome as far as I can find. Hard to believe that this is a bug in every Gnome application, maybe a Gtk bug? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
** Tags added: touch universalaccess -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740599] Re: Selecting multiple files and dragging them to file manager is broken in a Wayland session
It seems to me that either the bug title is overly specific or the issue is slightly different with Gnome 3.30 in Cosmic. In Cosmic it happens for single files as well, but only when dragging between desktop and a nautilus window. It's fine to drag between nautilus windows, and you can drag from Trash to desktop, but not from desktop to Trash. If others can repro this as well the bug title should be changed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1740599 Title: Selecting multiple files and dragging them to file manager is broken in a Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1740599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
** Tags added: cosmic ** Tags removed: highdpi ** Tags added: highdpii ** Tags removed: highdpii ** Tags added: highdpi -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720089] Re: Desktop isn't part of "places" (left bar) in artful
Just realized that Gnome 3.30 and/or the new theme in Cosmic shows all "Places" icons in black & white, so bookmarking makes no difference to this. Though the inconsistency with the colorful icon in the Home folder remains -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1720089 Title: Desktop isn't part of "places" (left bar) in artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
The Ubuntu help for 18.04 says that you need to activate it in the Accessibility settings, and "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 Neither is true for me: 1. I don't need to enable it in Accessibility in order to trigger in Activities and Applications 2. If I do enable it, it doesn't trigger outside of these two menus anyway -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
Gnome 2.28 release notes: https://help.gnome.org/misc/release- notes/3.28/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
I notice that the release notes for Gnome 2.28 say "The new keyboard automatically activates when a text area is selected". If this worked, no activation button would be needed as far as I can tell, and I suppose this is why there is none. However as I said in my previous comment this is not the case for me -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760399] Re: New On-screen keyboard cannot be manually triggered to appear
There is an extension to show a panel button to trigger it: https://extensions.gnome.org/extension/1061/on-screen-keyboard-button/ Unfortunately, its panel button itself does not react to touch at least for me (on Cosmic, Gnome 3.30, Wayland), which kind of defeats the purpose That said, in Gnome 3.30 the new OSK (from 2.28) automatically appears for me when I touch certain text entry fields, even when it is not enabled in Accessibility settings. This is IMHO the best solution. However, detection is either buggy or needs application support, as it works for me only in gnome-shell directly, e.g. the search field in Activities, but not anywhere else, not even first-class Gnome apps like Web or Videos -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard cannot be manually triggered to appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1760399/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726692] Re: Screen backlight adjustment stopped working on MacBook Pro 5, 4 and other hardware
I still have the same machine (upgraded/reinstalled to each Ubuntu version since) and the problem has not happened in agesa -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/726692 Title: Screen backlight adjustment stopped working on MacBook Pro 5,4 and other hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/726692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720089] Re: Desktop isn't part of "places" (left bar) in artful
Still the same in Cosmic. In the upstream bug it does not seem that they want to add it back by default (as expected really), so I'd think it's up to Ubuntu if files on desktop remain in contrast to upstream. "António Fernandes @antoniof · 8 months ago Developer The Desktop folder should become bookmarkable: #187 (closed) Starting with version 3.28, nautilus will not handle the "files on desktop background" feature." The #187 is closed because bookmarking is already possible. https://gitlab.gnome.org/GNOME/nautilus/issues/187 However, bookmarking is a poor replacement: - It gets listed in the bookmarks section, far away from Home and Documents where it really belongs as a central feature of file management in Ubuntu. - As bookmark, he icon (in Cosmic) has black & white outline style which is inconsistent with the prominent colorful Desktop icon that is shown inside the Home folder -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1720089 Title: Desktop isn't part of "places" (left bar) in artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720089] Re: Desktop isn't part of "places" (left bar) in artful
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1720089 Title: Desktop isn't part of "places" (left bar) in artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740599] Re: Selecting multiple files and dragging them to file manager is broken in a Wayland session
Same for me on Cosmic 18.10, fresh install and up to date. I works in X session. I can repro it also with a single file. nautilus version 1:3.26.4-0ubuntu3 ** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1740599 Title: Selecting multiple files and dragging them to file manager is broken in a Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1740599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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)
** Description changed: 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 of trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: + 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 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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)
** Description changed: 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. - 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: + No difference when booting 18.04.1 live image + + This laptop seems not the only one with this problem. I got the idea of 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 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console
** Description changed: 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. - This laptop seems not the only one with this problem. I got the idea of trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: + 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] + 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 + 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 ** Summary changed: - Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console + Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) -- You received this bug notification because
[Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console
In case it matters, the keyboard backlight is filed as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791372 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791367] Re: Airplane mode key on Asus UX561UD laptop not working under X or Wayland but working on console
Bios version is the latest from Asus ** Summary changed: - Airplane mode key on Asus UX561UD laptop not working under X or Wayland but working on console + Airplane mode key on Asus UX561UD laptop not working in gnome-shell (X or Wayland) but working on console ** Summary changed: - Airplane mode key on Asus UX561UD laptop not working in gnome-shell (X or Wayland) but working on console + Airplane mode key on Asus Zenbook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console ** Summary changed: - Airplane mode key on Asus Zenbook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console + Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791367] Re: Airplane mode key on Asus UX561UD laptop not working under X or Wayland but working on console
Forgot to add: Nvidia binary drivers are installed but Nvidia is switched off via Prime setting in nvidia-settings. Running with Intel drivers -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791367] [NEW] Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console
Public bug reported: 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. This laptop seems not the only one with this problem. I got the idea of 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 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic has-workaround reproducible ubuntu wayland-session ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726692] Re: Screen backlight adjustment stopped working on MacBook Pro 5, 4 and other hardware
This is still the same in a new install of Quantal (and IIRC it also was the same in Precise. However, I had not made a reinstall of Precise, but upgraded from Oneiric, so I didn't have to actually do anything to make it work, and therefore I am not sure) ** Tags added: quantal ** Changed in: gnome-power-manager (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/726692 Title: Screen backlight adjustment stopped working on MacBook Pro 5,4 and other hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/726692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 85291] Re: filesystems are never fsck'ed if they live on removable USB disks
** Tags added: quantal ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-volume-manager in Ubuntu. https://bugs.launchpad.net/bugs/85291 Title: filesystems are never fsck'ed if they live on removable USB disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-volume-manager/+bug/85291/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
