[Desktop-packages] [Bug 2030963] Re: Window/app switcher highlights hard to see
For anyone who's struggled to use the task switcher since 22.04 and until this is finally fixed, a reasonably painless workaround is available: https://askubuntu.com/a/1492396/145568 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2030963 Title: Window/app switcher highlights hard to see Status in GNOME Shell: New Status in Yaru Theme: New Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Bug description: In 22.04's default theme, it's almost impossible for me to make out which app or window is the currently selected one in the window switcher (alt-tab) or the application switcher (super-tab). The "highlighted" item is just a slightly different shade of grey. I mean, I can make it out if I squint at it, but ... that just isn't a *highlight*. This is a use where Ubuntu Orange shines, too. :-( "Ok, boomer, you're blind. I can see that just fine". Fair enough. Are you under thirty and (thus still) have 20:20 vision, by any chance? The point is, it isn't good UI design either way. What's worse, the high contrast accessibility setting doesn't touch any of it, and that is definitely a bug. == EDIT: Rearranged the submission so that the bit this bug is meant to be primarily about is on top. The below bits are preserved so that the discussion still makes sense. Similarly, the active workspace in the workspace overview (?) does get an orange frame, but it's very thin, much too thin to see unless you look closely. Again, that's not a highlight. A highlight is supposed to pop out. In comparison, the highlighting for the current tab in Terminal is ok- ish. I'd *prefer* for the entire tab to become orange, or to become a lighter colour in addition to the orange bar, but it's usable. (I could go on. For example, windows' title bars are now white vs the iconic Ubuntu Brown, which makes it hard to tell where the title bar is vs the window contents. Many applications also have buttons in the title bar now. It's no longer possible to just grab a window and move it on auto-pilot ... If the title bar can't be a different colour any more, at least separate it with a thick line or something. In any case, 22.04 is a massive regression in terms of visual UI design vs 18.04. Form should follow function, not the other way around.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 10 12:58:31 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (7 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2030963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
@ausbin: `aa-complain` is hardly a "fix": it bypasses AppArmor, which is not optimal, knowing how PDF documents are often used as a malware vector. Admittedly, malware is less likely to be targeted at Linux desktops but still... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04
Running APT evince 42.1-3 on stock Ubuntu 22.04/GNOME 42.0/Wayland. My issue is Evince opening in a tiny window every time it's fired off; this deployment was upgraded from 21.10, which didn't suffer from such issue. I attach below the output from `journalctl -f` while starting up Evince, which clearly shows AppArmor violations. I thus attempted the approach from https://askubuntu.com/a/886011/145568 . When running with `aa-complain evince`, Evince behaves properly; I accepted `aa-logprof`'s suggestion to grant /usr/bin/evince [owner /run/user/1000/at-spi/bus rw,]. Unfortunately as soon as I reinstate `aa-enforce evince`, the tiny window issue re-appears. (Note: at first I Ignored /usr/sbin/cups-browsed [capability sys_nice,] because I thought it was unrelated; I tried to grant it but this still doesn't solve the issue). ** Attachment added: "Evince 42.1-3 AppArmor debugging.txt" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+attachment/5587685/+files/Evince%2042.1-3%20AppArmor%20debugging.txt ** Summary changed: - Evince Document Viewer(42.0) does not remember last page in 22.04 + Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Incomplete Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Incomplete Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970937] Re: USN-5394-1 (libwebkit2gtk-4.0-37) causes regression in Evolution: impossible to compose email
FWIW, I've just upgraded to 22.04 and the version of Evolution bundled with it (3.44.0-1ubuntu1) doesn't suffer from this problem; so it affects 21.10 only. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1970937 Title: USN-5394-1 (libwebkit2gtk-4.0-37) causes regression in Evolution: impossible to compose email Status in webkit2gtk package in Ubuntu: Confirmed Bug description: This morning the security patch USN-5394-1 (https://ubuntu.com/security/notices/USN-5394-1) deployed on my laptop and following a reboot, I can no longer compose emails (or reply to emails) using Evolution (3.40.4-1ubuntu2). The composition window is blank. I'm on 21.10. As a proof of concept, I have rolled back the relevant parts of USN-5394-1 as follows: 1. Restored libwebkit2gtk-4.0.so.37.55.9 and libjavascriptcoregtk-4.0.so.18.19.11 (in /usr/lib/x86_64-linux-gnu) from a ZFS snapshot. 2. Re-established soft-links `libwebkit2gtk-4.0.so.37` and `libjavascriptcoregtk-4.0.so.18` to point to above versions. Does this bug belong somewhere else? If so, please guide me; I've raised it here because of the clear regression impact. I can't really choose between the vulnerabilities in USN-5394-1 and being able to write email... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1970937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970937] [NEW] USN-5394-1 (libwebkit2gtk-4.0-37) causes regression in Evolution: impossible to compose email
Public bug reported: This morning the security patch USN-5394-1 (https://ubuntu.com/security/notices/USN-5394-1) deployed on my laptop and following a reboot, I can no longer compose emails (or reply to emails) using Evolution (3.40.4-1ubuntu2). The composition window is blank. I'm on 21.10. As a proof of concept, I have rolled back the relevant parts of USN-5394-1 as follows: 1. Restored libwebkit2gtk-4.0.so.37.55.9 and libjavascriptcoregtk-4.0.so.18.19.11 (in /usr/lib/x86_64-linux-gnu) from a ZFS snapshot. 2. Re-established soft-links `libwebkit2gtk-4.0.so.37` and `libjavascriptcoregtk-4.0.so.18` to point to above versions. Does this bug belong somewhere else? If so, please guide me; I've raised it here because of the clear regression impact. I can't really choose between the vulnerabilities in USN-5394-1 and being able to write email... ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1970937 Title: USN-5394-1 (libwebkit2gtk-4.0-37) causes regression in Evolution: impossible to compose email Status in webkit2gtk package in Ubuntu: New Bug description: This morning the security patch USN-5394-1 (https://ubuntu.com/security/notices/USN-5394-1) deployed on my laptop and following a reboot, I can no longer compose emails (or reply to emails) using Evolution (3.40.4-1ubuntu2). The composition window is blank. I'm on 21.10. As a proof of concept, I have rolled back the relevant parts of USN-5394-1 as follows: 1. Restored libwebkit2gtk-4.0.so.37.55.9 and libjavascriptcoregtk-4.0.so.18.19.11 (in /usr/lib/x86_64-linux-gnu) from a ZFS snapshot. 2. Re-established soft-links `libwebkit2gtk-4.0.so.37` and `libjavascriptcoregtk-4.0.so.18` to point to above versions. Does this bug belong somewhere else? If so, please guide me; I've raised it here because of the clear regression impact. I can't really choose between the vulnerabilities in USN-5394-1 and being able to write email... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1970937/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872488] [NEW] Task switcher current app highlighting - dark gray on black - v. hard to distinguish
Public bug reported: IMHO the highlighting of the current app on the 20.04 task switcher being dark gray over a black background (see attached screenshot) is nearly impossible to distinguish. This may be suitable for the "dark" theme variant (people working in darkened rooms) but it should be possible to select a "Default" or "Light" variant that makes this a little more easy on the eye. Attempting to adjust this in gnome-control-panel under Appearance-> Window colors has no effect. Using Tweaks, with the "User Themes" extension, under Appearance -> Themes, selecting "Yaru-light" for Applications and "Default" under Shell exhibits the same behaviour. Interestingly, there are only two choices under Shell: Default and Yaru- dark and switching doesn't change anything. Could the issue be that a Yaru-light gnome-shell theme is missing from the package? I'm still unsure whether this is an install issue with my 19.10 upgraded deployment but having cross-checked the package content, I don't think so. My system is fully updated. $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt policy yaru-theme-gnome-shell yaru-theme-gtk yaru-theme-gnome-shell: Installed: 20.04.4 Candidate: 20.04.4 Version table: *** 20.04.4 500 500 http://ch.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status yaru-theme-gtk: Installed: 20.04.4 Candidate: 20.04.4 Version table: *** 20.04.4 500 500 http://ch.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Attachment added: "Task switcher.png" https://bugs.launchpad.net/bugs/1872488/+attachment/5353344/+files/Task%20switcher.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1872488 Title: Task switcher current app highlighting - dark gray on black - v. hard to distinguish Status in yaru-theme package in Ubuntu: New Bug description: IMHO the highlighting of the current app on the 20.04 task switcher being dark gray over a black background (see attached screenshot) is nearly impossible to distinguish. This may be suitable for the "dark" theme variant (people working in darkened rooms) but it should be possible to select a "Default" or "Light" variant that makes this a little more easy on the eye. Attempting to adjust this in gnome-control-panel under Appearance-> Window colors has no effect. Using Tweaks, with the "User Themes" extension, under Appearance -> Themes, selecting "Yaru-light" for Applications and "Default" under Shell exhibits the same behaviour. Interestingly, there are only two choices under Shell: Default and Yaru-dark and switching doesn't change anything. Could the issue be that a Yaru-light gnome-shell theme is missing from the package? I'm still unsure whether this is an install issue with my 19.10 upgraded deployment but having cross-checked the package content, I don't think so. My system is fully updated. $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt policy yaru-theme-gnome-shell yaru-theme-gtk yaru-theme-gnome-shell: Installed: 20.04.4 Candidate: 20.04.4 Version table: *** 20.04.4 500 500 http://ch.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status yaru-theme-gtk: Installed: 20.04.4 Candidate: 20.04.4 Version table: *** 20.04.4 500 500 http://ch.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1872488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842954] Re: AMD GPU hang/crash/black screen after suspend(ing)
Issue definitely also occurs with stock Ubuntu GNOME DE (just did a fresh install on a ThinkPad t495s with "AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx"; up-to-date kernel 5.3.0-26-generic and the issue occurred twice within 12 hours of installing - once upon resuming and the 2nd time just after forcing a reboot due to first issue. I fully understand that complaining here isn't likely to have much effect but it's a real shame that just when AMD finally appears to be taking the Edge over Intel (we *desperately* need the competition IMHO; see the vulnerabilities debacle), the premier Linux desktop distribution falls flat on its face. I also understand that the issue is likely not Debian/Ubuntu specific. That said, I really hope that Canonical sees this bug and sponsors a fix (perhaps in partnership with AMD) at least before 20.04 LTS hits the shelves. Stack trace: Jan 21 08:56:57 t495s kernel: [ 7403.538132] [ cut here ] Jan 21 08:56:57 t495s kernel: [ 7403.538257] WARNING: CPU: 5 PID: 1566 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932 dcn10_verify_allow_pstate_change_high.col d+0xc/0x23d [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.538258] Modules linked in: rfcomm ccm cmac bnep nls_iso8859_1 iwlmvm snd_hda_codec_realtek mac80211 libarc4 snd_hda_codec_generic uvcvideo btusb snd_h da_codec_hdmi btrtl videobuf2_vmalloc btbcm videobuf2_memops snd_seq_midi btintel videobuf2_v4l2 edac_mce_amd videobuf2_common snd_seq_midi_event snd_hda_intel kvm_amd snd_hda_codec video dev bluetooth ccp kvm irqbypass snd_rawmidi snd_hda_core joydev mc serio_raw input_leds iwlwifi snd_hwdep wmi_bmof thinkpad_acpi snd_pcm nvram ecdh_generic k10temp ecc ledtrig_audio snd_s eq snd_pci_acp3x snd_seq_device rtsx_pci_ms snd_timer ipmi_devintf memstick cfg80211 ipmi_msghandler snd ucsi_acpi typec_ucsi typec soundcore mac_hid sch_fq_codel parport_pc ppdev lp parp ort ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid dm_crypt amdgpu crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel amd_iommu_v2 rtsx_pc i_sdmmc gpu_sched i2c_algo_bit ttm drm_kms_helper aes_x86_64 crypto_simd syscopyarea sysfillrect Jan 21 08:56:57 t495s kernel: [ 7403.538286] sysimgblt cryptd glue_helper psmouse fb_sys_fops drm i2c_piix4 nvme rtsx_pci r8169 nvme_core realtek wmi video i2c_scmi Jan 21 08:56:57 t495s kernel: [ 7403.538295] CPU: 5 PID: 1566 Comm: Xorg Tainted: GW 5.3.0-26-generic #28-Ubuntu Jan 21 08:56:57 t495s kernel: [ 7403.538296] Hardware name: LENOVO 20QJCTO1WW/20QJCTO1WW, BIOS R13ET40W(1.14 ) 10/29/2019 Jan 21 08:56:57 t495s kernel: [ 7403.538381] RIP: 0010:dcn10_verify_allow_pstate_change_high.cold+0xc/0x23d [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.538385] Code: 83 c8 ff e9 59 f7 f7 ff 48 c7 c7 08 f1 a2 c0 e8 9d 97 79 f8 0f 0b 83 c8 ff e9 43 f7 f7 ff 48 c7 c7 08 f1 a2 c0 e8 87 97 79 f8 <0f> 0b 80 bb 9f 01 00 00 00 75 05 e9 6a 1e f8 ff 48 8b 83 f8 02 00 Jan 21 08:56:57 t495s kernel: [ 7403.538386] RSP: 0018:9d04820f7710 EFLAGS: 00010246 Jan 21 08:56:57 t495s kernel: [ 7403.538387] RAX: 0024 RBX: 88e30cc8 RCX: 0006 Jan 21 08:56:57 t495s kernel: [ 7403.538388] RDX: RSI: 0082 RDI: 88e31ed57440 Jan 21 08:56:57 t495s kernel: [ 7403.538388] RBP: 9d04820f7720 R08: 0617 R09: 0004 Jan 21 08:56:57 t495s kernel: [ 7403.538389] R10: R11: 0001 R12: 88e30cc8 Jan 21 08:56:57 t495s kernel: [ 7403.538390] R13: 88e1d06701b8 R14: R15: 88e1d1253000 Jan 21 08:56:57 t495s kernel: [ 7403.538391] FS: 7effe0e44a80() GS:88e31ed4() knlGS: Jan 21 08:56:57 t495s kernel: [ 7403.538392] CS: 0010 DS: ES: CR0: 80050033 Jan 21 08:56:57 t495s kernel: [ 7403.538392] CR2: CR3: 00040fbec000 CR4: 003406e0 Jan 21 08:56:57 t495s kernel: [ 7403.538393] Call Trace: Jan 21 08:56:57 t495s kernel: [ 7403.538474] dcn10_pipe_control_lock.part.0+0x76/0x80 [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.538554] dcn10_apply_ctx_for_surface+0x4a8/0x5e0 [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.538634] ? dc_remove_plane_from_context+0x108/0x270 [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.538635] done. Jan 21 08:56:57 t495s kernel: [ 7403.538706] ? dc_rem_all_planes_for_stream+0xc8/0x110 [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.538777] dc_commit_state_no_check+0x387/0x580 [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.538840] ? amdgpu_cgs_read_register+0x14/0x20 [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.538914] dc_commit_state+0x96/0xb0 [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.538987] amdgpu_dm_atomic_commit_tail+0x3bf/0xfb0 [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.539062] ? optc1_get_crtc_scanoutpos+0x69/0xa0 [amdgpu] Jan 21 08:56:57 t495s kernel: [ 7403.539130] ?
[Desktop-packages] [Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'
Hi Daniel, Thanks to the pointer. I now have 3.30.1-2ubuntu1.18.10.2 and it seems the issue is resolved (not sure if this is the new version or the manual fix below, which I applied thanks to your pointer). I'd installed the Pop theme manually (through apt) atop stock 18.10. The slightly unorthodox thing I'd done was a soft-link from /usr/share /gnome-shell/theme/Yaru/gnome-shell.css onto ../gnome-shell.css, which is itself a soft-link to /usr/share/themes/Pop/gnome-shell/gnome- shell.css This would consistent theming of the lock screen, which doesn't appear to obey the control panel setting. Using the soft-links also makes it easier to spot when those files get overwritten by updates. So it looks like the changes introduced in 3.30.1-2ubuntu1.18.10.1 makes it impossible to follow symlinks from /usr/share/gnome-shell/theme/Yaru /gnome-shell.css ? I guess it's perhaps debatable whether the standard gnome-shell package should reference a hardcoded theme (or maybe that's a GNOME limitation?) Anyway, since I've worked around this issue, I guess this bug can be closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css' Status in gnome-shell package in Ubuntu: Incomplete Bug description: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left those alone): Start-Date: 2018-12-19 09:13:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.8821' Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1) End-Date: 2018-12-19 09:13:31 I solved the issue by downgrading the just-updated gnome-shell packages as follows: sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome- shell=3.30.1-2ubuntu1 Having done this, I switched back to the GDM screen and managed to log in as normal. I couldn't find any smoking gun in system logs but please let me know if there's a way to collect any useful debug info. One thing I'm using which differs from stock 18.10 is the System76 "Pop" theme (let me know if you need details). Presumably a theme cannot cause such issues and/or if the new version of gnome-shell is meant to be incompatible with themes other than Yaru, this should be clearly documented. The problematic versions are the "Candidate" shown below: gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status gnome-shell-common: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login)
Hi Daniel, please see attached; apologies for delay. I hope the weird "gnome-session-binary[4266]: CRITICAL: We failed, but the fail whale is dead. Sorry" is a tell-tale sign? Cheers Christian ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+attachment/5224875/+files/prevboot.txt ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login) Status in gnome-shell package in Ubuntu: New Bug description: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left those alone): Start-Date: 2018-12-19 09:13:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.8821' Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1) End-Date: 2018-12-19 09:13:31 I solved the issue by downgrading the just-updated gnome-shell packages as follows: sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome- shell=3.30.1-2ubuntu1 Having done this, I switched back to the GDM screen and managed to log in as normal. I couldn't find any smoking gun in system logs but please let me know if there's a way to collect any useful debug info. One thing I'm using which differs from stock 18.10 is the System76 "Pop" theme (let me know if you need details). Presumably a theme cannot cause such issues and/or if the new version of gnome-shell is meant to be incompatible with themes other than Yaru, this should be clearly documented. The problematic versions are the "Candidate" shown below: gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status gnome-shell-common: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809092] [NEW] gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login)
Public bug reported: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left those alone): Start-Date: 2018-12-19 09:13:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.8821' Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1) End-Date: 2018-12-19 09:13:31 I solved the issue by downgrading the just-updated gnome-shell packages as follows: sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome- shell=3.30.1-2ubuntu1 Having done this, I switched back to the GDM screen and managed to log in as normal. I couldn't find any smoking gun in system logs but please let me know if there's a way to collect any useful debug info. One thing I'm using which differs from stock 18.10 is the System76 "Pop" theme (let me know if you need details). Presumably a theme cannot cause such issues and/or if the new version of gnome-shell is meant to be incompatible with themes other than Yaru, this should be clearly documented. The problematic versions are the "Candidate" shown below: gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status gnome-shell-common: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic regression-update ** Package changed: gnome (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access + gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login) Status in gnome-shell package in Ubuntu: New Bug description: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left those alone): Start-Date: 2018-12-19 09:13:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.8821' Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1) End-Date: 2018-12-19 09:13:31 I solved the issue by downgrading
[Desktop-packages] [Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login)
** Description changed: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left those alone): Start-Date: 2018-12-19 09:13:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.8821' Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1) End-Date: 2018-12-19 09:13:31 I solved the issue by downgrading the just-updated gnome-shell packages as follows: sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome- shell=3.30.1-2ubuntu1 Having done this, I switched back to the GDM screen and managed to log - in as normal. I couldn't find anything useful in system logs but please - let me know if there's a way to collect such info. + in as normal. I couldn't find any smoking gun in system logs but please + let me know if there's a way to collect any useful debug info. One thing I'm using which differs from stock 18.10 is the System76 "Pop" theme (let me know if you need details). Presumably a theme cannot cause such issues and/or if the new version of gnome-shell is meant to be incompatible with themes other than Yaru, this should be clearly documented. The problematic versions are the "Candidate" shown below: gnome-shell: - Installed: 3.30.1-2ubuntu1 - Candidate: 3.30.1-2ubuntu1.18.10.1 - Version table: - 3.30.1-2ubuntu1.18.10.1 500 - 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages - *** 3.30.1-2ubuntu1 500 - 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.30.1-2ubuntu1 + Candidate: 3.30.1-2ubuntu1.18.10.1 + Version table: + 3.30.1-2ubuntu1.18.10.1 500 + 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages + *** 3.30.1-2ubuntu1 500 + 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 100 /var/lib/dpkg/status gnome-shell-common: - Installed: 3.30.1-2ubuntu1 - Candidate: 3.30.1-2ubuntu1.18.10.1 - Version table: - 3.30.1-2ubuntu1.18.10.1 500 - 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages - 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages - *** 3.30.1-2ubuntu1 500 - 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 3.30.1-2ubuntu1 + Candidate: 3.30.1-2ubuntu1.18.10.1 + Version table: + 3.30.1-2ubuntu1.18.10.1 500 + 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages + 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages + *** 3.30.1-2ubuntu1 500 + 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login) Status in gnome-shell package in Ubuntu: New Bug description: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left thos
[Desktop-packages] [Bug 1770322] Re: Xorg crashes after system sleep / wakeup
*** This bug is a duplicate of bug 1769819 *** https://bugs.launchpad.net/bugs/1769819 FWIW, I am experiencing fairly regular X.org crashes at sleep resume with my ThinkPad X1c5 (stock KabyLake Intel HD 620 iGPU) on 18.04 (currently running 4.15.0-36 but has been happening for a while). Never had such issues with 17.10. This may be related to waking up the laptop hooked to my monitor over a USB-C cable after it was previously used un-docked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1770322 Title: Xorg crashes after system sleep / wakeup Status in xorg-server package in Ubuntu: Incomplete Bug description: after putting the system to sleep, and waking it up, Xorg crashes, and I'm lead to a new greeter / login screen. naturally the state of my desktop is lost in this process, and I'm stuck with a new login with no apps running. the error reporter says: Error: [Errno 21] is a directory: '/proc/driver/nvidia/gpus/:01:00.0/' which is indeed true: $ ls /proc/driver/nvidia/gpus/\:01\:00.0/ information registry the same system worked fine with ubuntu 17.10 this is a follow-up filing for bug 1769819, after X server core dumping has been enabled: $ cat /etc/gdm3/custom.conf ... [debug] # Uncomment the line below to turn on debugging # More verbose logs # Additionally lets the X server dump core if it crashes Enable=true ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 10 07:31:41 2018 DistUpgraded: 2018-05-04 09:38:04,874 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.13.0-39-generic, x86_64: installed nvidia, 390.48, 4.15.0-20-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes 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] NVIDIA Corporation GK104 [GeForce GTX 680] [10de:1180] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 680] [3842:3687] InstallationDate: Installed on 2016-04-03 (766 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=e56cb504-229d-4c7a-b16c-b259d05e992b ro noprompt quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-05-04 (5 days ago) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H 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.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 vers
[Desktop-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
Just to clarify above comment from hans005: from what I can read here his problem (#138, #145) was a completely different issue: standby with nvidia GPU. This regression relates to *hibernation* (not mere standby) and AFAIK, has been experienced with a variety of GPUs (included Intel integrated GPUs as in my case) so it's quite likely *not* a condition related to GPU drivers or model in use - although it's common for less run-of-the- mill dGPUs to exacerbate such issues I suppose. I don't believe there are any workarounds to the issue accurately captured by the bug's headline. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Hi @cascagrossa, just to clarify: my impression is that in order to trigger the bug you'll need to suspend somewhere where the WLAN network you want to connect to at resume time isn't available as it's the scan aspect of things that appears to be inhibited. This is evidenced by the fact that he network-mgr UI shows a stale list of WiFi networks when the bug manifests itself; I've don't *think* I've ever had this bug affect me in a stationary suspend/resume scenario. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Also further to #60, I have put the following in mine (Thinkpad X1 Carbon 3) and it does indeed seem to fix the problem so far - been testing over a few days: /lib/systemd/system-sleep/wpasupplicant: post) (sleep 3 ; /sbin/wpa_cli resume) & ;; 16.04.1 fresh install, kernel 4.4.0-59; network-manager 1.2.2-0ubuntu0.16.04.3 Anything shorter than 3 seconds seems to be too fast for that race condition; could this suggest this might be better fixed with a systemd dependency? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Fresh 16.04.1 install on ThinkPad X1 carbon 3 with stock Intel 7265 (802.11abgn) WiFi here; laptop also has a Sierra Wireless EM7345 4G LTE WWAN integrate USB module. Typical scenario: I use the WWAN when out and about, suspend the laptop, come back to office and expect the laptop to re-connect to WiFi. Typically the WWAN reconnects but the network mgr applet shows a stale list of WiFi access points (looks like they're from when I last suspended the laptop). Kern.log has below notices after resume from sleep regarding the WLAN adapter [1] I tried the following (several times in a row) from the above suggestions to restore my connection (in assumed descending order of "invasion"): 1. sudo wpa_cli scan 2. sudo rfkill block wifi; sleep 3; rfkill unblock wifi 3. sudo systemctl restart network-manager.service #3 did it this time but there was definitely a previous occurrence where it didn't help and only a reboot did. Just in case this helps shed some light on this lengthy thread. Would agree that this isn't Ubuntu's finest hour; sorry I cannot be more constructive. [1] ken.log Jan 6 10:31:49 cinamon5u NetworkManager[1270]: [1483695109.4803] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jan 6 10:31:49 cinamon5u kernel: [ 3239.333883] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready Jan 6 10:31:49 cinamon5u kernel: [ 3239.432191] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready Jan 6 10:31:49 cinamon5u NetworkManager[1270]: [1483695109.8678] device (wlp4s0): supplicant interface state: starting -> ready Jan 6 10:31:49 cinamon5u NetworkManager[1270]: [1483695109.8679] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jan 6 10:31:49 cinamon5u kernel: [ 3239.721341] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready Jan 6 10:33:19 cinamon5u NetworkManager[1270]: [1483695199.5763] device (wlp4s0): state change: disconnected -> unavailable (reason 'none') [30 20 0] Jan 6 10:33:23 cinamon5u kernel: [ .131109] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready Jan 6 10:33:23 cinamon5u NetworkManager[1270]: [1483695203.3310] device (wlp4s0): supplicant interface state: starting -> ready Jan 6 10:33:23 cinamon5u NetworkManager[1270]: [1483695203.3311] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jan 6 10:33:23 cinamon5u kernel: [ .175963] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
