[Bug 1813119] Re: In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome- shell/commit/?id=c14508e8bffd496e568dbf9c97b547fccbb4cea6 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1813119 Title: In Ubuntu 19.04, the wrong background (a gradient) flashes up briefly during the login animation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818595] [NEW] Update to 1.46
Public bug reported: https://wiki.ubuntu.com/SnapdGlibUpdates Overview of changes in snapd-glib 1.46 * New API: - snapd_channel_get_released_at - SNAPD_ERROR_DNS_FAILURE * Fix tests breaking due to undefined order of results ** Affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Affects: snapd-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: snapd-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: snapd-glib (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: snapd-glib (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: snapd-glib (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + https://wiki.ubuntu.com/SnapdGlibUpdates + Overview of changes in snapd-glib 1.46 - * New API: - - snapd_channel_get_released_at - - SNAPD_ERROR_DNS_FAILURE - * Fix tests breaking due to undefined order of results + * New API: + - snapd_channel_get_released_at + - SNAPD_ERROR_DNS_FAILURE + * Fix tests breaking due to undefined order of results -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1818595 Title: Update to 1.46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818595/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
Verified on cosmic that mutter version 3.30.2-1~ubuntu18.10.4 has fixed this bug. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- 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/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes
This bug is closed. Please see bug 1760818 instead, or open a new one. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1620806 Title: gedit edit window is transparent when using Ambiance and Radiance themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818456] Re: Horrible video experience with Intel Graphic after new fresh install
1. Can you please provide a screenshot of the problem with 'gedit'. 2. Please remove all PPAs including 'oibaf' before reporting any bugs. We can't support PPAs and in fact they are often the cause of bugs. ** Package changed: xorg (Ubuntu) => gtk+3.0 (Ubuntu) ** Summary changed: - Horrible video experience with Intel Graphic after new fresh install + gedit text area is not showed in a white background but "cloning" everything that were in that screen position ** Also affects: gedit (Ubuntu) Importance: Undecided Status: New ** Changed in: gedit (Ubuntu) Status: New => Incomplete ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1818456 Title: gedit text area is not showed in a white background but "cloning" everything that were in that screen position To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1818456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818456] Re: gedit text area is not showed in a white background but "cloning" everything that were in that screen position
Is it the same as the screenshot in bug 1760818? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1818456 Title: gedit text area is not showed in a white background but "cloning" everything that were in that screen position To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1818456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818456] [NEW] Horrible video experience with Intel Graphic after new fresh install
You have been subscribed to a public bug: Since my new fresh install of Ubuntu 18.04 I can't have a good experience. Use a simple gEdit is impossible because the text area is not showed in a white background but "cloning" everything that were in that screen position curiously it not happen with Leafpad editor. But occur with Gnome-claculator. My LibreOffice can't show their buttons in any toolbar. I've tried to install the oibaf PPA (sudo add-apt-repository ppa:oibaf /graphics-drivers) expcting some improve but nothing change. Unhappily. Some years ago I have this same experience in Ubuntu 16.04 but it was over (I don't know how) and even after a dist-upgrade to 18.04 it is OK, but now I had to to new install and the bug is here. Unhappily. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolb ox,decor,grid,move,resize,mousepoll,regex,snap,gno mecompat,place,imgpng,vpswitch,animation,wall,work arounds,fade,session,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 22:17:53 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,bailer,detection,composite,opengl,compiztoolb ox,decor,grid,move,resize,mousepoll,regex,snap,gno mecompat,place,imgpng,vpswitch,animation,wall,work arounds,fade,session,expo,ezoom,unityshell] GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-09-01 (183 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H87M-HD3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-45-generic root=UUID=3c502856-3b66-4815-8747-59e0fce0d335 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnH87M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H87M-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1902261830.d54e54~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1903030730.cb4e3e~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1903030730.cb4e3e~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git1902111932.15697e~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1903011933.6afed3~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git1901290732.ec2b45~oibaf~b ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- Horrible video experience with Intel Graphic after new fresh install https://bugs.launchpad.net/bugs/1818456 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
Uploaded in bionic by desktop team. Thanks. -- 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/1817738 Title: Can't change virtual terminal when auto-login is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818246] Re: update-notifier's notification is huge due to large icon
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1818246 Title: update-notifier's notification is huge due to large icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818246] Re: update-notifier's notification is huge due to large icon
** Tags added: disco ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1818246 Title: update-notifier's notification is huge due to large icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818246/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
Thanks for clearing up that misconception, Daniel (at least for me; I thought there was at least a sizable team employed by Canonical). I'll be happy to run these versions and do some testing. I'll looking forward to 19.04/19.10, so I'll see how they are in their current state and report any bugs I find. On Mon, Mar 4, 2019, 7:30 PM Daniel van Vugt, wrote: > Short of predicting the future, I think the best answer is that more > keen Ubuntu users should test the next version of Ubuntu before its > release. That way we can discuss/prioritize/fix accessibility issues > before they get released to the wider world. > > You can always get a test build of the next Ubuntu version here: > http://cdimages.ubuntu.com/daily-live/current/ > > There's a common misconception that Canonical has some big development > team that will do all the development and testing but that's not true. > We rely heavily on community users to help make Ubuntu possible. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1767648 > > Title: > Top bar and shell dialogs are not displayed properly when zoom is > enabled > > Status in Mutter: > Fix Released > Status in mutter package in Ubuntu: > Fix Released > Status in mutter source package in Bionic: > Fix Committed > Status in mutter source package in Cosmic: > Fix Released > > Bug description: > [Impact] > > When zoom is enabled, the top bar and some shell dialogs (wireless > network selection, shutdown dialog, etc.) are not displayed properly. > (See the attached screenshots.) > > [Test Case] > > 1. Enable Zoom in Setting > Universal Access > 2. (Optional) Set zoom factor to around 3 (or higher) > 3. Look at the top bar. You will notice that all texts and icons are now > gone. If you move your cursor to the right of the top bar, and then click > on the status menu, you will see that only a portion of the menu is shown. > 4. For the shell dialogs, go to the Settings app. In the Wifi section, > choose one of the secured network available. You will see that the password > dialog is not displayed in its entirety. > > [Regression Potential] > > Low. The affected code is only used in rendering shell panels and > popup menus at the moment. So any potential regression (like the > original bug) would be noticed in those places only, and not beyond. > Furthermore, the upstream fix has been tested regularly for 8 months > already. > > [Other Info] > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gnome-shell 3.28.1-0ubuntu2 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CasperVersion: 1.394 > CurrentDesktop: ubuntu:GNOME > Date: Sat Apr 28 12:54:24 2018 > DisplayManager: gdm3 > GsettingsChanges: >b'org.gnome.desktop.interface' b'gtk-im-module' > b"'gtk-im-context-simple'" >b'org.gnome.desktop.interface' b'cursor-size' b'96' > LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=C.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions > -- 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/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750197] Re: App grid animation causes heavy CPU spikes and dropped frames in Wayland & Xorg
Fix released as part of... gnome-shell (3.30.2-0ubuntu1.18.10.1) cosmic; urgency=medium [ Iain Lane ] * New upstream release 3.30.2 (LP: #1813350) [ Marco Trevisan (Treviño) ] * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/ibusManager-Don-t-pass-undefined-callback-to-ibus.patch: - Fix missing icon in keyboard indicator (LP: #1812266) -- Iain Lane Fri, 25 Jan 2019 19:04:17 + ** Changed in: gnome-shell (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1750197 Title: App grid animation causes heavy CPU spikes and dropped frames in Wayland & Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1808226] Re: Rotated screen is blank in Wayland sessions [Failed to set CRTC mode 1600x1200: No space left on device]
This bug is closed. If you experience any further/different issues then please open new bugs for those. -- 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/1808226 Title: Rotated screen is blank in Wayland sessions [Failed to set CRTC mode 1600x1200: No space left on device] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update
This bug is closed. Please open a new bug if you have any problems. -- 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/1779476 Title: Ubuntu 18.04: gdm3 does not switch to graphics after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1779476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
Pedro, That's enough for me, thanks. This bug is now closed. If anyone experiences any more issues at all then please open a new bug by running: ubuntu-bug gnome-shell And if anyone did want to test 19.04 then you can find it here: http://cdimages.ubuntu.com/daily-live/current/ But if you do find any problems with 19.04 then please open new bugs for those. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
Short of predicting the future, I think the best answer is that more keen Ubuntu users should test the next version of Ubuntu before its release. That way we can discuss/prioritize/fix accessibility issues before they get released to the wider world. You can always get a test build of the next Ubuntu version here: http://cdimages.ubuntu.com/daily-live/current/ There's a common misconception that Canonical has some big development team that will do all the development and testing but that's not true. We rely heavily on community users to help make Ubuntu possible. -- 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/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818584] [NEW] I can not to open my data from USB in Nautilus by non-system applications
Public bug reported: So I has inserted the USB Drive. Then open Nautilus. I tried to open the document from my USB Drive in other program such as WPS Office. But i noticed the error. Also I tried to sent my file from USB Drive to Telegram, but I has got an error. To choose the directory of file I use the integrated in the Ubuntu Nautilus. So I think that there is system bug. Because I didn`t see such error in the stable releases of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 5 02:29:44 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(650, 514)' InstallationDate: Installed on 2019-03-04 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1818584 Title: I can not to open my data from USB in Nautilus by non-system applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1818584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816205] Re: [disco-proposed] When using the Gedit icons they disappear from the desktop
** Summary changed: - When using the Gedit icons they disappear from the desktop + [disco-proposed] When using the Gedit icons they disappear from the desktop -- 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/1816205 Title: [disco-proposed] When using the Gedit icons they disappear from the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
Note: Desktop team kindly offered to update the vcs and do the upload in
bionic on my behalf.
Thanks !
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
- 4) sudo chvt 4 ## chvt will hang here.
+ 4) Print active VT
+ $ sudo fgconsole
+
+ Without the fix, it will be "1". # BAD
+ With the fix, it will be "2". # GOOD
+
+ 5) sudo chvt 4 ## chvt will hang here.
Verification can be made from a 2nd terminal, run :
$ cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never happens.
[Potential regression]
Low.
Current gdm3 run autologin display on tty1. tty1 is really meant for the
login screen. This commit changes autologin to not use the initial vt.
If one do chvt 1, once in tty1 it will hangs again and one won't be able
to switch it. tty1 is really the problem here, so by forcing the
autologin to not use tty1 we improve the current behaviour where we
can't switch VTs at all when autologin is enabled.
The tty1 behaviour will still need (normal behaviour or not ???) to be
investigated, but not mandatory required for the sake of this SRU IMHO.
I suspect systemd-logind to be the reason of the tty1 behaviour:
# ps
root 1350 1 0 Mar03 ?00:00:03 /lib/systemd/systemd-logind
#lsof
systemd-l 1350 root 24u CHR4,1
0t0 45 /dev/tty1
But I haven't dig much in it for now.
So the fix will works as long as one doesn't do run on tty1.
Exactly like when autologin isn't enable.
* From a machine with autologin enable:
/etc/gdm3/customer.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin = user1
$ sudo fgconsole
1
* From a machine with autologin disable:
/etc/gdm3/customer.conf
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
$ sudo fgconsole
2
[Other information]
* Upstream fix:
https://github.com/GNOME/gdm/commit/39fb4ff6
$ git describe --contains 39fb4ff6
3.30.1~2^2~3
$ rmadision gdm3
==> gdm3 | 3.28.3-0ubuntu18.04.4 | bionic-updates | ...
gdm3 | 3.30.1-1ubuntu5 | cosmic | ...
gdm3 | 3.30.1-1ubuntu5 | disco| ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-security | ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-updates | ...
gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed | ...
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mprotect(0x7f5059e9, 4096, PROT_READ) = 0
munmap(0x7f5059e7d000, 74655) = 0
brk(NULL) = 0x561e1843
brk(0x561e18451000) = 0x561e18451000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644,
[Bug 1818575] [NEW] Messages and some LOGS Application errors
Public bug reported: Hello guys In show applications / utilities / logs, we find the LOGS application. When you open the screen it is not possible to resize it. It is larger than the screen configuration. It does not maximize the screen after it is open. I think it should be another novelty of Ubuntu Disco 19.04. In it is contained all logs of errors by demand being: Application log messages, Important, All, Applications, System, Security, and Hardware. I do not know if this function is automatically sending the error messages to the Ubuntu Bug. In this case, I am sending the attachment with the information of my machine with the error messages. Note: It was not possible to send by ubuntu-bug -w, as an error message appears for this application, see attached image. Thank you in advance for your attention. Thank you ** Olá Pessoal Em mostrar aplicativos/utilitários/logs, encontramos o aplicativo LOGS. Ao abrir a tela não é possivel redimensiona-la. Está maior que a configuração da tela. Não maximiza a tela apos estar aberta. Creio que deva ser mais uma novidade do Ubuntu Disco 19.04. Nela está contido todos os logs de erros por demanda sendo: Mensagens de registro de aplicativos, Importante, Todos, Aplicativos, Sistema, Segurança e Hardware. Desconheço se esta função está enviando automaticamente as mensagens de erro para o Ubuntu Bug. Neste caso, estou enviando o anexo com as informações da minha maquina com as mensagens de erro. Obs. Não foi possivel enviar pelo ubuntu-bug -w, pois aparece mensagem de erro para este aplicativo, vide imagem em anexo. Desde já agradeço pela atenção de sempre. Obrigado ** Affects: gnome-logs (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Error message when using ubuntu-bug -w in the LOGS application" https://bugs.launchpad.net/bugs/1818575/+attachment/5243482/+files/Captura%20de%20tela%20de%202019-03-04%2019-21-00.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-logs in Ubuntu. https://bugs.launchpad.net/bugs/1818575 Title: Messages and some LOGS Application errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-logs/+bug/1818575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
I have a laptop that exhibits this behavior. The switching of the ttys will hang about 95% of the time (1 in 20). With this test package, it now works 100% of the time as long as I don't switch to tty1. I tested it 5 times in a row with a reboot between each. I can Ctrl+Alt+F# without any issue. If I run "sudo chvt 1", it will not switch out of that tty again until I reboot my laptop again. Using 2 through 12 all work and switch the display to that tty. Thanks, Chris Newcomer -- 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/1817738 Title: Can't change virtual terminal when auto-login is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
4) sudo chvt 4 ## chvt will hang here.
Verification can be made from a 2nd terminal, run :
$ cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never happens.
[Potential regression]
Low.
Current gdm3 run autologin display on tty1. tty1 is really meant for the
login screen. This commit changes autologin to not use the initial vt.
If one do chvt 1, once in tty1 it will hangs again and one won't be able
to switch it. tty1 is really the problem here, so by forcing the
- autologin to not use tty1 we workaround the issue.
+ autologin to not use tty1 we improve the current behaviour where we
+ can't switch VTs at all when autologin is enabled.
The tty1 behaviour will still need (normal behaviour or not ???) to be
investigated, but not mandatory required for the sake of this SRU IMHO.
I suspect systemd-logind to be the reason of the tty1 behaviour:
# ps
root 1350 1 0 Mar03 ?00:00:03 /lib/systemd/systemd-logind
#lsof
systemd-l 1350 root 24u CHR4,1
0t0 45 /dev/tty1
But I haven't dig much in it for now.
- So the fix will works as long as one doesn't do "chvt 1", which is
- better than right now where autologin in gdm by default uses tty1 and
- prevent any kind of vt switch.
+ So the fix will works as long as one doesn't do run on tty1.
Exactly like when autologin isn't enable.
* From a machine with autologin enable:
/etc/gdm3/customer.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin = user1
$ sudo fgconsole
1
* From a machine with autologin disable:
/etc/gdm3/customer.conf
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
$ sudo fgconsole
2
[Other information]
* Upstream fix:
https://github.com/GNOME/gdm/commit/39fb4ff6
$ git describe --contains 39fb4ff6
3.30.1~2^2~3
$ rmadision gdm3
==> gdm3 | 3.28.3-0ubuntu18.04.4 | bionic-updates | ...
gdm3 | 3.30.1-1ubuntu5 | cosmic | ...
gdm3 | 3.30.1-1ubuntu5 | disco| ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-security | ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-updates | ...
gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed | ...
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mprotect(0x7f5059e9, 4096, PROT_READ) = 0
munmap(0x7f5059e7d000, 74655) = 0
brk(NULL) = 0x561e1843
brk(0x561e18451000) = 0x561e18451000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
mmap(NULL, 10281936,
[Bug 1818348] Re: When window title bar controls are on left, close window button is cut off in title bar of Disks application
Reported at https://gitlab.gnome.org/GNOME/gnome-disk- utility/issues/124. Launchpad won't let me link to that external bu report, says it doesn't recognize it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1818348 Title: When window title bar controls are on left, close window button is cut off in title bar of Disks application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1818348/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1801757] Re: all app indicators disappear
@valeryan-24 that sounds like the same problem as the one I reported. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1801757 Title: all app indicators disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1801757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
- 2.2) autologin run on tty1
- $ sudo fgconsole
- 1
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
4) sudo chvt 4 ## chvt will hang here.
Verification can be made from a 2nd terminal, run :
$ cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never happens.
- A system which runs on tty1 is not able to switch VT. This may or may not be
a kernel issue or else. The tty1 will require some investigation, to see if
it's a normal behaviour or not ... but can be treated as a separate bug.
[Potential regression]
Low.
Current gdm3 run autologin display on tty1. tty1 is really meant for the
login screen. This commit changes autologin to not use the initial vt.
- But if one do chvt 1, once the system runs on tty1 it will hangs again
- and one won't be able to switch it. tty1 is really the problem here, so
- by forcing the autologin to not use tty1 we workaround the issue.
+ If one do chvt 1, once in tty1 it will hangs again and one won't be able
+ to switch it. tty1 is really the problem here, so by forcing the
+ autologin to not use tty1 we workaround the issue.
The tty1 behaviour will still need (normal behaviour or not ???) to be
- investigated, but not mandatory required for the sake of this SRU IMHO
- and can be treated as a separate bug.
+ investigated, but not mandatory required for the sake of this SRU IMHO.
+
+ I suspect systemd-logind to be the reason of the tty1 behaviour:
+
+ # ps
+ root 1350 1 0 Mar03 ?00:00:03 /lib/systemd/systemd-logind
+
+ #lsof
+ systemd-l 1350 root 24u CHR4,1
0t0 45 /dev/tty1
+
+ But I haven't dig much in it for now.
So the fix will works as long as one doesn't do "chvt 1", which is
better than right now where autologin in gdm by default uses tty1 and
prevent any kind of vt switch.
Exactly like when autologin isn't enable.
* From a machine with autologin enable:
/etc/gdm3/customer.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin = user1
$ sudo fgconsole
1
* From a machine with autologin disable:
/etc/gdm3/customer.conf
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
$ sudo fgconsole
2
[Other information]
* Upstream fix:
https://github.com/GNOME/gdm/commit/39fb4ff6
$ git describe --contains 39fb4ff6
3.30.1~2^2~3
$ rmadision gdm3
==> gdm3 | 3.28.3-0ubuntu18.04.4 | bionic-updates | ...
gdm3 | 3.30.1-1ubuntu5 | cosmic | ...
gdm3 | 3.30.1-1ubuntu5 | disco| ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-security | ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-updates | ...
gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed | ...
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
+ 2.2) autologin run on tty1
+ $ sudo fgconsole
+ 1
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
4) sudo chvt 4 ## chvt will hang here.
Verification can be made from a 2nd terminal, run :
$ cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never happens.
+ A system which runs on tty1 is not able to switch VT. This may or may not be
a kernel issue or else. The tty1 will require some investigation, but as a
separate bug.
[Potential regression]
Low.
Current gdm3 run autologin display on tty1. tty1 is really meant for the
login screen. This commit changes autologin to not use the initial vt.
But if one do chvt 1, once the system runs on tty1 it will hangs again
and one won't be able to switch it. tty1 is really the problem here, so
by forcing the autologin to not use tty1 we workaround the issue.
The tty1 behaviour will still need (normal behaviour or not ???) to be
- investigated, but not mandatory required for the sake of this SRU IMHO.
+ investigated, but not mandatory required for the sake of this SRU IMHO
+ and can be treated as a separate bug.
So the fix will works as long as one doesn't do "chvt 1", which is
better than right now where autologin in gdm by default uses tty1 and
prevent any kind of vt switch.
Exactly like when autologin isn't enable.
* From a machine with autologin enable:
/etc/gdm3/customer.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin = user1
$ sudo fgconsole
1
* From a machine with autologin disable:
/etc/gdm3/customer.conf
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
$ sudo fgconsole
2
[Other information]
* Upstream fix:
https://github.com/GNOME/gdm/commit/39fb4ff6
$ git describe --contains 39fb4ff6
3.30.1~2^2~3
$ rmadision gdm3
==> gdm3 | 3.28.3-0ubuntu18.04.4 | bionic-updates | ...
gdm3 | 3.30.1-1ubuntu5 | cosmic | ...
gdm3 | 3.30.1-1ubuntu5 | disco| ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-security | ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-updates | ...
gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed | ...
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mprotect(0x7f5059e9, 4096, PROT_READ) = 0
munmap(0x7f5059e7d000, 74655) = 0
brk(NULL) = 0x561e1843
brk(0x561e18451000) = 0x561e18451000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400
[Bug 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell
Fix proposed upstream: https://gitlab.gnome.org/GNOME/mutter/merge_requests/474 -- 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/1817546 Title: Changing the volume (with the mouse wheel over icon) locks up gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
4) sudo chvt 4 ## chvt will hang here.
Verification can be made from a 2nd terminal, run :
$ cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never happens.
[Potential regression]
Low.
Current gdm3 run autologin display on tty1. tty1 is really meant for the
login screen. This commit changes autologin to not use the initial vt.
- If one do chvt 1, once in tty1 it will hangs again and one won't be able
- to switch it. tty1 is really the problem here, so by forcing the
- autologin to not use tty1 we workaround the issue.
+ But if one do chvt 1, once the system runs on tty1 it will hangs again
+ and one won't be able to switch it. tty1 is really the problem here, so
+ by forcing the autologin to not use tty1 we workaround the issue.
The tty1 behaviour will still need (normal behaviour or not ???) to be
investigated, but not mandatory required for the sake of this SRU IMHO.
So the fix will works as long as one doesn't do "chvt 1", which is
better than right now where autologin in gdm by default uses tty1 and
prevent any kind of vt switch.
Exactly like when autologin isn't enable.
* From a machine with autologin enable:
/etc/gdm3/customer.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin = user1
$ sudo fgconsole
1
* From a machine with autologin disable:
/etc/gdm3/customer.conf
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
$ sudo fgconsole
2
[Other information]
* Upstream fix:
https://github.com/GNOME/gdm/commit/39fb4ff6
$ git describe --contains 39fb4ff6
3.30.1~2^2~3
$ rmadision gdm3
==> gdm3 | 3.28.3-0ubuntu18.04.4 | bionic-updates | ...
gdm3 | 3.30.1-1ubuntu5 | cosmic | ...
gdm3 | 3.30.1-1ubuntu5 | disco| ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-security | ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-updates | ...
gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed | ...
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mprotect(0x7f5059e9, 4096, PROT_READ) = 0
munmap(0x7f5059e7d000, 74655) = 0
brk(NULL) = 0x561e1843
brk(0x561e18451000) = 0x561e18451000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD,
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
4) sudo chvt 4 ## chvt will hang here.
Verification can be made from a 2nd terminal, run :
$ cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never happens.
[Potential regression]
Low.
- Current gdm3 run autologin display on tty1 . tty1 is really meant for
- the login screen. This commit changes autologin to not use the initial
- vt.
+ Current gdm3 run autologin display on tty1. tty1 is really meant for the
login screen. This commit changes autologin to not use the initial vt.
+
+ If one do chvt 1, once in tty1 it will hangs again and one won't be able to
switch it. tty1 is really the problem here, so by forcing the autologin to not
use tty1 we workaround the issue.
+
+ The tty1 behaviour will still need IMHO to be investigated, but not
+ required for the sake of this SRU IMHO.
+
+ So the fix will works as long as one doesn't do "chvt 1", which is
+ better than right now where gmd autologin by default uses tty1 and
+ prevent any kind of vt switch.
Exactly like when autologin isn't enable.
- From a machine with autologin disable:
+ * From a machine with autologin enable:
+
+ /etc/gdm3/customer.conf
+ # Enabling automatic login
+ AutomaticLoginEnable = true
+ AutomaticLogin = user1
+
+ $ sudo fgconsole
+ 1
+
+ * From a machine with autologin disable:
/etc/gdm3/customer.conf
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
$ sudo fgconsole
2
+
[Other information]
* Upstream fix:
https://github.com/GNOME/gdm/commit/39fb4ff6
$ git describe --contains 39fb4ff6
3.30.1~2^2~3
$ rmadision gdm3
==> gdm3 | 3.28.3-0ubuntu18.04.4 | bionic-updates | ...
gdm3 | 3.30.1-1ubuntu5 | cosmic | ...
gdm3 | 3.30.1-1ubuntu5 | disco| ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-security | ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-updates | ...
gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed | ...
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mprotect(0x7f5059e9, 4096, PROT_READ) = 0
munmap(0x7f5059e7d000, 74655) = 0
brk(NULL) = 0x561e1843
brk(0x561e18451000) = 0x561e18451000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
4) sudo chvt 4 ## chvt will hang here.
- 5) From a 2nd terminal, run :
- 5.1) cat /proc/$(pidof chvt)/stack
-
+ Verification can be made from a 2nd terminal, run :
+ $ cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never happens.
[Potential regression]
Low.
Current gdm3 run autologin display on tty1 . tty1 is really meant for
the login screen. This commit changes autologin to not use the initial
vt.
Exactly like when autologin isn't enable.
From a machine with autologin disable:
/etc/gdm3/customer.conf
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
- $ sudo fgconsole
+ $ sudo fgconsole
2
[Other information]
* Upstream fix:
https://github.com/GNOME/gdm/commit/39fb4ff6
$ git describe --contains 39fb4ff6
3.30.1~2^2~3
$ rmadision gdm3
==> gdm3 | 3.28.3-0ubuntu18.04.4 | bionic-updates | ...
gdm3 | 3.30.1-1ubuntu5 | cosmic | ...
gdm3 | 3.30.1-1ubuntu5 | disco| ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-security | ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-updates | ...
gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed | ...
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mprotect(0x7f5059e9, 4096, PROT_READ) = 0
munmap(0x7f5059e7d000, 74655) = 0
brk(NULL) = 0x561e1843
brk(0x561e18451000) = 0x561e18451000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
4) sudo chvt 4 ## chvt will hang here.
5) From a 2nd terminal, run :
5.1) cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never happens.
[Potential regression]
+
+ Low.
+
+ Current gdm3 run autologin display on tty1 . tty1 is really meant for
+ the login screen. This commit changes autologin to not use the initial
+ vt.
[Other information]
* Upstream fix:
https://github.com/GNOME/gdm/commit/39fb4ff6
$ git describe --contains 39fb4ff6
3.30.1~2^2~3
$ rmadision gdm3
==> gdm3 | 3.28.3-0ubuntu18.04.4 | bionic-updates | ...
gdm3 | 3.30.1-1ubuntu5 | cosmic | ...
gdm3 | 3.30.1-1ubuntu5 | disco| ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-security | ...
gdm3 | 3.30.1-1ubuntu5.1 | cosmic-updates | ...
gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed | ...
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mprotect(0x7f5059e9, 4096, PROT_READ) = 0
munmap(0x7f5059e7d000, 74655) = 0
brk(NULL) = 0x561e1843
brk(0x561e18451000) = 0x561e18451000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
Enable debuglogs doesn't provide additional details.
As soon as auto-login is turned off, chvt is back to normal.
The above has been reproduced on Ubuntu:
- Ubuntu Bionic w/ gdm3 3.28.3 & kbd 2.0.4
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
- 2.1) Modify /etc/gdm3/custom.conf
+ 2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
- AutomaticLoginEnable = true
- AutomaticLogin =
+ AutomaticLoginEnable = true
+ AutomaticLogin =
- 3) Restart gdm or reboot
+ 3) Reboot your system and make sure AutoLogin works by not requesting
+ password before opening the session.
4) sudo chvt 4 ## chvt will hang here.
5) From a 2nd terminal, run :
- 5.1) cat /proc/$(pidof chvt)/stack
+ 5.1) cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
It's basically waiting for the VT to be activated, but it never happens.
[Potential regression]
[Other information]
[Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mprotect(0x7f5059e9, 4096, PROT_READ) = 0
munmap(0x7f5059e7d000, 74655) = 0
brk(NULL) = 0x561e1843
brk(0x561e18451000) = 0x561e18451000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
Enable debuglogs doesn't provide additional details.
As soon as auto-login is turned off, chvt is back to normal.
The above has been reproduced on Ubuntu:
- Ubuntu Bionic w/ gdm3 3.28.3 & kbd 2.0.4
- Ubuntu disco w/ gdm3 3.30.1 & kbd 2.0.4
** Description changed:
[Impact]
When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
preventing from changing foreground virtual terminal.
[Test case]
1) Install Bionic/18.04LTS Desktop
2) Enable AutomaticLogin
2.1) Modify /etc/gdm3/custom.conf
# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin =
3) Reboot your system and make sure AutoLogin works by not requesting
password before opening the session.
4) sudo chvt 4 ## chvt will hang here.
5) From a 2nd terminal, run :
5.1) cat /proc/$(pidof chvt)/stack
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
I was able to reproduce the bug, and this upstream fix[1] look promising. On my test machine, using a test package containing this patch on top of current gdm3 bionic, chvt doesn't hang anymore, and work as expected. I'd would like more feedback before I proceed with an SRU. [1] - 39fb4ff6 manager: don't run autologin display on tty1 - Eric -- 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/1817738 Title: Can't change virtual terminal when auto-login is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795121] Re: 18.10: Indicator icons not shown in the panel
This same for me , dropbox missing and redshift app icons. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1795121 Title: 18.10: Indicator icons not shown in the panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1795121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Description changed:
+ [Impact]
+
+ When AutomaticLogin is enable in gdm3. The "chvt" command hangs forever,
+ preventing from changing foreground virtual terminal.
+
+ [Test case]
+
+ 1) Install Bionic/18.04LTS Desktop
+
+ 2) Enable AutomaticLogin
+ 2.1) Modify /etc/gdm3/custom.conf
+ # Enabling automatic login
+ AutomaticLoginEnable = true
+ AutomaticLogin =
+
+ 3) Restart gdm or reboot
+
+ 4) sudo chvt 4 ## chvt will hang here.
+
+ 5) From a 2nd terminal, run :
+ 5.1) cat /proc/$(pidof chvt)/stack
+
+ [<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
+ [<0>] vt_waitactive+0x80/0xd0
+ [<0>] vt_ioctl+0xd26/0x1140
+ [<0>] tty_ioctl+0xf6/0x8c0
+ [<0>] do_vfs_ioctl+0xa8/0x630
+ [<0>] SyS_ioctl+0x79/0x90
+ [<0>] do_syscall_64+0x73/0x130
+ [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
+ [<0>] 0x
+
+ It's basically waiting for the VT to be activated, but it never happens.
+
+ [Potential regression]
+
+ [Other information]
+
+ [Original Description]
sudo strace chvt 4
execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
brk(NULL) = 0x561e1843
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5059e7b000
mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5059878000
mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
close(3) = 0
arch_prctl(ARCH_SET_FS, 0x7f5059e7c500) = 0
mprotect(0x7f5059c5f000, 16384, PROT_READ) = 0
mprotect(0x561e17e87000, 4096, PROT_READ) = 0
mprotect(0x7f5059e9, 4096, PROT_READ) = 0
munmap(0x7f5059e7d000, 74655) = 0
brk(NULL) = 0x561e1843
brk(0x561e18451000) = 0x561e18451000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10281936, ...}) = 0
mmap(NULL, 10281936, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5058ea9000
close(3) = 0
openat(AT_FDCWD, "/proc/self/fd/0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = -1 ENOTTY (Inappropriate ioctl for
device)
close(3) = 0
openat(AT_FDCWD, "/dev/tty0", O_RDWR) = 3
ioctl(3, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(3, KDGKBTYPE, 0x7ffdcdb0efa7) = 0
ioctl(3, VT_ACTIVATE, 0x4) = 0
ioctl(3, VT_WAITACTIVE, 0x4
VT_ACTIVATE will cause a switch to VT number.
VT_WAITACTIVE will sleep/wait until the specified VT has been activated.
$ sudo cat /proc/$(pidof chvt)/stack
[<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
[<0>] vt_waitactive+0x80/0xd0
[<0>] vt_ioctl+0xd26/0x1140
[<0>] tty_ioctl+0xf6/0x8c0
[<0>] do_vfs_ioctl+0xa8/0x630
[<0>] SyS_ioctl+0x79/0x90
[<0>] do_syscall_64+0x73/0x130
[<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[<0>] 0x
Enable debuglogs doesn't provide additional details.
As soon as auto-login is turned off, chvt is back to normal.
The above has been reproduced on Ubuntu:
- Ubuntu Bionic w/ gdm3 3.28.3 & kbd 2.0.4
- Ubuntu disco w/ gdm3 3.30.1 & kbd 2.0.4
--
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/1817738
Title:
Can't change virtual terminal when auto-login is enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817738/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Changed in: gdm3 (Ubuntu Bionic) Status: New => In Progress ** Changed in: gdm3 (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: gdm3 (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1817738 Title: Can't change virtual terminal when auto-login is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1817738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell
** Changed in: gnome-shell (Ubuntu Disco) Assignee: Marco Trevisan (Treviño) (3v1n0) => Andrea Azzarone (azzar1) -- 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/1817546 Title: Changing the volume (with the mouse wheel over icon) locks up gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
This bug was fixed in the package gnome-shell - 3.30.2-0ubuntu1.18.10.1 --- gnome-shell (3.30.2-0ubuntu1.18.10.1) cosmic; urgency=medium [ Iain Lane ] * New upstream release 3.30.2 (LP: #1813350) [ Marco Trevisan (Treviño) ] * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/ibusManager-Don-t-pass-undefined-callback-to-ibus.patch: - Fix missing icon in keyboard indicator (LP: #1812266) -- Iain Lane Fri, 25 Jan 2019 19:04:17 + ** Changed in: gnome-shell (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812266] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813350] Re: [SRU] 3.30.2
This bug was fixed in the package gnome-shell - 3.30.2-0ubuntu1.18.10.1 --- gnome-shell (3.30.2-0ubuntu1.18.10.1) cosmic; urgency=medium [ Iain Lane ] * New upstream release 3.30.2 (LP: #1813350) [ Marco Trevisan (Treviño) ] * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/ibusManager-Don-t-pass-undefined-callback-to-ibus.patch: - Fix missing icon in keyboard indicator (LP: #1812266) -- Iain Lane Fri, 25 Jan 2019 19:04:17 + ** Changed in: gnome-shell (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1813350 Title: [SRU] 3.30.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813350/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813350] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1813350 Title: [SRU] 3.30.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813350/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818540] Re: /usr/lib/gnome-settings-daemon/gsd-color:8:__libc_do_syscall:__libc_signal_restore_set:__GI_raise:__aeabi_ldiv0:gcm_session_device_reset_gamma
That has 3 reports ever, all on 18.04 and armhf, probably a real issue with color manager on that platform but I wouldn't say it's important enough that we care at this point ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Won't Fix -- 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/1818540 Title: /usr/lib/gnome-settings-daemon/gsd- color:8:__libc_do_syscall:__libc_signal_restore_set:__GI_raise:__aeabi_ldiv0:gcm_session_device_reset_gamma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1818540/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818540] [NEW] /usr/lib/gnome-settings-daemon/gsd-color:8:__libc_do_syscall:__libc_signal_restore_set:__GI_raise:__aeabi_ldiv0:gcm_session_device_reset_gamma
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 3.28.1-0ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/d6440dcc36a44df198391fa4420d6d1ab434f0d5 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Low Status: Won't Fix ** Tags: bionic -- 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/1818540 Title: /usr/lib/gnome-settings-daemon/gsd- color:8:__libc_do_syscall:__libc_signal_restore_set:__GI_raise:__aeabi_ldiv0:gcm_session_device_reset_gamma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1818540/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817020] Re: Touching and dragging an icon on the dock blocks input to other apps
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => In Progress ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Disco) Importance: High Assignee: Andrea Azzarone (azzar1) Status: In Progress ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Cosmic) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Bionic) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1817020 Title: Touching and dragging an icon on the dock blocks input to other apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1817020/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818517] Re: "Network Login" browser does not remember cookies
Thank you for your bug report. What do you call "cookie" exactly in that context? You would like the system to auto validate the portals you already visited without showing anything? That's probably something more for the backend side, also worth reporting upstream who probably has more an opinion about that https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues Other platforms don't do that either, do they? (e.g android). Unsure if that would be legal to 'bypass' the portal, the user is supposed to give his explicit consent that he's using the service ** Package changed: gnome-shell (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (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/1818517 Title: "Network Login" browser does not remember cookies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818517] [NEW] "Network Login" browser does not remember cookies
Public bug reported: This is with respect to the gnome-shell-portal-helper, part of the gnome-shell package, which opens its own browser window to prompt for a wifi hotspot login. It all works fine except one little papercut: Could it remember cookies? So when I go back to the same hotspot most days I don't have to click OK to accept cookies every time before I can actually click to go online. It's possible I suppose they don't all use cookies. The hotspot in question is a BT wifi hotspot, so probably quite common in GB anyway. Desired behaviour, hate to say, is like Windows: It actually remembered my choice from before and just logged me in right away. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 4 14:05:46 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (173 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (49 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco package-from-proposed 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/1818517 Title: "Network Login" browser does not remember cookies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818422] Re: Totem: DBus reports wrong .desktop file name
upstream merged the fix ** Changed in: totem (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1818422 Title: Totem: DBus reports wrong .desktop file name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1818422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818422] Re: Totem: DBus reports wrong .desktop file name
Thank you for your bug report, indeed that's still an issue in the current codebase, I proposed a fix upstream now https://gitlab.gnome.org/GNOME/totem/merge_requests/82/ ** Changed in: totem (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1818422 Title: Totem: DBus reports wrong .desktop file name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1818422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818348] Re: When window title bar controls are on left, close window button is cut off in title bar of Disks application
Thank you for your bug report. That's probably because the buttons box is then 'docked' to the sidebar and the buttons don't fully fit in that width. That's an upstream issue, ideally to report to them on https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1818348 Title: When window title bar controls are on left, close window button is cut off in title bar of Disks application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1818348/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818422] Re: Totem: DBus reports wrong .desktop file name
** Changed in: totem (Ubuntu) Importance: Undecided => Low ** Changed in: totem (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1818422 Title: Totem: DBus reports wrong .desktop file name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1818422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797734] Re: slow calculator startup
This is a problem on 18.10 Cosmic Cuttlefish, as well. Embarrassingly slow for a simple application like this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816205] Re: When using the Gedit icons they disappear from the desktop
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => New -- 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/1816205 Title: When using the Gedit icons they disappear from the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+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
No, it's not fixed in any Ubuntu version yet. The first part of the work just landed upstream and for wayland sessions only, that should be in the incoming Ubuntu Disco version first and unsure it's going to be something that is possible to SRU since it involves quite some refactoring. -- 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 1818315] Re: Can't install applications: "E: could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)"
Right, it's likely that the system was busy doing a refresh of the indexes or even installing security upgrades in background, those situations are not reflected nicely in the graphical session (and the gnome-software warning is not really nice either) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1818315 Title: Can't install applications: "E: could not get lock /var/lib/dpkg/lock- frontend - open (11: Resource temporarily unavailable)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1818315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818472] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: nautilus (Ubuntu) Importance: Medium => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1818472 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1818472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
