[Desktop-packages] [Bug 1864543] Re: Wrong disk capacity displayed in "About" pane
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1864543 Title: Wrong disk capacity displayed in "About" pane Status in gnome-control-center package in Ubuntu: Confirmed Bug description: The About pane in the Settings says "Disk Capacity 1TB", but my disk is actually 512GB. This might be related: https://bugs.launchpad.net/ubuntu- gnome/+bug/1311558 Version info below. $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt policy gnome-control-center gnome-control-center: Installed: 1:3.35.91-0ubuntu1 Candidate: 1:3.35.91-0ubuntu1 Version table: *** 1:3.35.91-0ubuntu1 500 500 mirror://mirrors.ubuntu.com/mirrors.txt focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1864543/+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 1908348] Re: Disk capacity in "about" section of the gnome-control-panel
See also bug 1864543. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1908348 Title: Disk capacity in "about" section of the gnome-control-panel Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Disk capacity in "about" section of the gnome-control-panel always shows internal computer disk space available but not the disk where Ubuntu is executed. I am executing Ubuntu from and external drive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 16 06:35:52 2020 InstallationDate: Installed on 2020-10-26 (50 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908348/+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 1908348] Re: Disk capacity in "about" section of the gnome-control-panel
It seems to be the sum of all disk capacities. If that's not what you see then please: 1. Tell us how much it reports for you. 2. Run: lsblk > blk.txt and attach the resulting text file here. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1908348 Title: Disk capacity in "about" section of the gnome-control-panel Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Disk capacity in "about" section of the gnome-control-panel always shows internal computer disk space available but not the disk where Ubuntu is executed. I am executing Ubuntu from and external drive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 16 06:35:52 2020 InstallationDate: Installed on 2020-10-26 (50 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908348/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
The same always happens to me when the system does not register key- strokes from my Apple bluetooth keyboard after a system restart. Keyboard appears as connected in the bluetooth setting, but no keystrokes come through. syslog fills with these errors. Setup: MS bluetooth mouse and Apple Wireless Keyboard A1016. -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
/** pin_reg |= DB_TYPE_REMOVE_GLITCH << DB_CNTRL_OFF; */ did not work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO ---
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) Patch #179 no longer works with kernel 5.10.1, because pinctrl-amd.c has already been patched with the current kernel version and GLITCH has been changed. My touchpad MSFT0001: 00 04F3: 3140 still worked up to 5.10-rc7 with #179. This is th new code for GLITCH: - raw_spin_lock_irqsave(&gpio_dev->lock, flags); pin_reg = readl(gpio_dev->base + offset * 4); if (debounce) { pin_reg |= DB_TYPE_REMOVE_GLITCH << DB_CNTRL_OFF; pin_reg &= ~DB_TMR_OUT_MASK; - Do you have any idea what needs to be changed to make it work again? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB16121
[Desktop-packages] [Bug 1869734] Re: openjade segfaults on all arch
There was a fix suggested on https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=975242 and I tried that. It works great. I've let the Debian postgresql-maintainer know and there might be an NMU that would then allow to make this package a sync again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openjade in Ubuntu. https://bugs.launchpad.net/bugs/1869734 Title: openjade segfaults on all arch Status in openjade package in Ubuntu: Triaged Status in pgpool2 package in Ubuntu: New Status in openjade package in Debian: Unknown Bug description: cpaelzer: fun, openjade segfaulting on focal/arm64 I beg your pardon for my ignorance of the ecosystem, but how is this related to postgresql-apt for doc generation? cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc generation on focal/arm64 everything else (other archs, other dists) is fine https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console Myon: only on arm64? only there, yes ./configure && make -C doc/src/sgml all should reproduce it clone and build this branch ? https://github.com/postgres/postgres/tree/REL9_5_STABLE the crash is in /usr/lib/libostyle.so.1 from libostyle1c2 here it is segfault I have this now http://paste.debian.net/1136839/ https://paste.ubuntu.com/p/CfzrfWkqzs/ well I wanted to get -O0 to see more int he debugger my build worked as well now the -O0 openjade installed doesn't segfault oh so like my -O0 then so maybe we should just always -O0 openjade then? TBH who cares about optimization in that But its usage is mostly build time and not runtime maybe -O0 on arm64 only I'm rebulding -O2 again to recheck if that really is it and then -O1 to check the in between it might "just" need a rebuild -O2 re-build segfault -O1 (for completeness) rebuild ... seems to hang? probably not really relevant agreed, but I want to rebuild -O0 again just to see it builds and then works -O0 on arm64 really seems to be a good choice I can try if rebuilding makes it fail on sid cpaelzer: recompiling openjade in arm64/sid doesn't make it segfault so it seems this needs a focal-only fix cpaelzer: the openjade segfault is also present in pgpool2, so not just in ancient PostgreSQL :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1908348] [NEW] Disk capacity in "about" section of the gnome-control-panel
Public bug reported: Disk capacity in "about" section of the gnome-control-panel always shows internal computer disk space available but not the disk where Ubuntu is executed. I am executing Ubuntu from and external drive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 16 06:35:52 2020 InstallationDate: Installed on 2020-10-26 (50 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1908348 Title: Disk capacity in "about" section of the gnome-control-panel Status in gnome-control-center package in Ubuntu: New Bug description: Disk capacity in "about" section of the gnome-control-panel always shows internal computer disk space available but not the disk where Ubuntu is executed. I am executing Ubuntu from and external drive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 16 06:35:52 2020 InstallationDate: Installed on 2020-10-26 (50 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908348/+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 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions
This bug was fixed in the package mutter - 3.38.2-1ubuntu1 --- mutter (3.38.2-1ubuntu1) hirsute; urgency=medium * Merge with debian, containing new upstream release (LP: #1908158): - Apply input device settings on hotplug / reconnect and resume (LP: #1899206) * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch: - Refreshed as per upstream changes mutter (3.38.2-1) unstable; urgency=medium * Team upload * New upstream release - Don't crash during screencasting if cursor is not available - Don't crash if a kernel bug results in appearing to have multiple builtin panels - Log warnings instead of crashing if user-defined keymap is misconfigured - Don't forget we have a touchscreen if a non-touchscreen input device is connected - Log warnings instead of crashing if invalid barriers are created - Otherwise functionally equivalent to 3.38.1-4 * Drop patches cherry-picked from upstream or applied upstream * d/gbp.conf: Use upstream 3.38.x branch. Version 40~alpha was already released, so it's misleading to say that 3.38.x is the latest. * Standards-Version: 4.5.1 (no changes required) * d/rules: Don't run tests if built with nocheck option * Upload to unstable mutter (3.38.1-4) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-50-gc70610c43 - If cursor theme is missing, draw a grey semi-transparent square instead of crashing - Allow primary GPU to be overridden with a udev rule - Fix fullscreen toggle for some applications (Closes: #975453) - Only schedule frame drawing for each surface (window) according to one stage view (monitor) - Fix size hints for client-side-decorated windows - Avoid adding input devices too soon - Performance optimizations - Do not disable the X Security extension if Xwayland was built with it * Don't depend on transitional libgdk-pixbuf2.0-dev * Explicitly build-depend on gdk-pixbuf. Previously it was pulled in by some other dependency (presumably gnome-desktop3 and gtk), but mutter's build system checks for it, so we should build-depend on it here too. * d/p/clutter-frame-clock-Schedule-a-frame-at-least-once-per-se.patch: Add proposed patch to ensure frame clock does not stop (Closes: #974172) mutter (3.38.1-3) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-33-g067af969c - Prevent a use-after-free on (virtual) device removal - Prevent crash on startup caused by dispatching libinput events too early - If Wayland subsurfaces have circular relationships, disconnect the client instead of crashing - When resizing terminals interactively, don't offset the position - Fix broken timestamp behaviour if X11 timestamps overflow - Fix a memory leak - Ensure clock is updated when going from fullscreen app to overview - Fix artifacts around GNOME Shell magnifier cursor - Fix monitor tiling on X11 - Configure input devices correctly in X11 (LP: #1899206, LP: #1899509) - Avoid spurious warnings in log - Event does not have a stage: discarding - assertion 'CLUTTER_IS_STAGE (stage)' failed - Make sure build fails if Xwayland -initfd is requested but not available (not relevant in Debian, we don't request this yet) - Update translations: pt * d/p/backend-Don-t-pull-generated-headers-indirectly.patch: Add a patch from upstream git master to fix parallel builds -- Marco Trevisan (Treviño) Tue, 15 Dec 2020 01:20:01 +0100 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- 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/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Bug description: I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized
[Desktop-packages] [Bug 1899509] Re: Mouse/touchpad settings not applied on hotplug/reconnect/resume
*** This bug is a duplicate of bug 1899206 *** https://bugs.launchpad.net/bugs/1899206 This bug was fixed in the package mutter - 3.38.2-1ubuntu1 --- mutter (3.38.2-1ubuntu1) hirsute; urgency=medium * Merge with debian, containing new upstream release (LP: #1908158): - Apply input device settings on hotplug / reconnect and resume (LP: #1899206) * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch: - Refreshed as per upstream changes mutter (3.38.2-1) unstable; urgency=medium * Team upload * New upstream release - Don't crash during screencasting if cursor is not available - Don't crash if a kernel bug results in appearing to have multiple builtin panels - Log warnings instead of crashing if user-defined keymap is misconfigured - Don't forget we have a touchscreen if a non-touchscreen input device is connected - Log warnings instead of crashing if invalid barriers are created - Otherwise functionally equivalent to 3.38.1-4 * Drop patches cherry-picked from upstream or applied upstream * d/gbp.conf: Use upstream 3.38.x branch. Version 40~alpha was already released, so it's misleading to say that 3.38.x is the latest. * Standards-Version: 4.5.1 (no changes required) * d/rules: Don't run tests if built with nocheck option * Upload to unstable mutter (3.38.1-4) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-50-gc70610c43 - If cursor theme is missing, draw a grey semi-transparent square instead of crashing - Allow primary GPU to be overridden with a udev rule - Fix fullscreen toggle for some applications (Closes: #975453) - Only schedule frame drawing for each surface (window) according to one stage view (monitor) - Fix size hints for client-side-decorated windows - Avoid adding input devices too soon - Performance optimizations - Do not disable the X Security extension if Xwayland was built with it * Don't depend on transitional libgdk-pixbuf2.0-dev * Explicitly build-depend on gdk-pixbuf. Previously it was pulled in by some other dependency (presumably gnome-desktop3 and gtk), but mutter's build system checks for it, so we should build-depend on it here too. * d/p/clutter-frame-clock-Schedule-a-frame-at-least-once-per-se.patch: Add proposed patch to ensure frame clock does not stop (Closes: #974172) mutter (3.38.1-3) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-33-g067af969c - Prevent a use-after-free on (virtual) device removal - Prevent crash on startup caused by dispatching libinput events too early - If Wayland subsurfaces have circular relationships, disconnect the client instead of crashing - When resizing terminals interactively, don't offset the position - Fix broken timestamp behaviour if X11 timestamps overflow - Fix a memory leak - Ensure clock is updated when going from fullscreen app to overview - Fix artifacts around GNOME Shell magnifier cursor - Fix monitor tiling on X11 - Configure input devices correctly in X11 (LP: #1899206, LP: #1899509) - Avoid spurious warnings in log - Event does not have a stage: discarding - assertion 'CLUTTER_IS_STAGE (stage)' failed - Make sure build fails if Xwayland -initfd is requested but not available (not relevant in Debian, we don't request this yet) - Update translations: pt * d/p/backend-Don-t-pull-generated-headers-indirectly.patch: Add a patch from upstream git master to fix parallel builds -- Marco Trevisan (Treviño) Tue, 15 Dec 2020 01:20:01 +0100 ** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1899509 Title: Mouse/touchpad settings not applied on hotplug/reconnect/resume Status in gnome-control-center: Unknown Status in GNOME Settings Daemon: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Bug description: When I plug in a touchpad via USB, my chosen scrolling and speed settings are not applied, unless I adjust them again in the settings UI. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1899509/+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 1908158] Re: Update to 3.38.2
This bug was fixed in the package mutter - 3.38.2-1ubuntu1 --- mutter (3.38.2-1ubuntu1) hirsute; urgency=medium * Merge with debian, containing new upstream release (LP: #1908158): - Apply input device settings on hotplug / reconnect and resume (LP: #1899206) * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch: - Refreshed as per upstream changes mutter (3.38.2-1) unstable; urgency=medium * Team upload * New upstream release - Don't crash during screencasting if cursor is not available - Don't crash if a kernel bug results in appearing to have multiple builtin panels - Log warnings instead of crashing if user-defined keymap is misconfigured - Don't forget we have a touchscreen if a non-touchscreen input device is connected - Log warnings instead of crashing if invalid barriers are created - Otherwise functionally equivalent to 3.38.1-4 * Drop patches cherry-picked from upstream or applied upstream * d/gbp.conf: Use upstream 3.38.x branch. Version 40~alpha was already released, so it's misleading to say that 3.38.x is the latest. * Standards-Version: 4.5.1 (no changes required) * d/rules: Don't run tests if built with nocheck option * Upload to unstable mutter (3.38.1-4) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-50-gc70610c43 - If cursor theme is missing, draw a grey semi-transparent square instead of crashing - Allow primary GPU to be overridden with a udev rule - Fix fullscreen toggle for some applications (Closes: #975453) - Only schedule frame drawing for each surface (window) according to one stage view (monitor) - Fix size hints for client-side-decorated windows - Avoid adding input devices too soon - Performance optimizations - Do not disable the X Security extension if Xwayland was built with it * Don't depend on transitional libgdk-pixbuf2.0-dev * Explicitly build-depend on gdk-pixbuf. Previously it was pulled in by some other dependency (presumably gnome-desktop3 and gtk), but mutter's build system checks for it, so we should build-depend on it here too. * d/p/clutter-frame-clock-Schedule-a-frame-at-least-once-per-se.patch: Add proposed patch to ensure frame clock does not stop (Closes: #974172) mutter (3.38.1-3) experimental; urgency=medium * Team upload * Update to upstream gnome-3-38 branch, commit 3.38.1-33-g067af969c - Prevent a use-after-free on (virtual) device removal - Prevent crash on startup caused by dispatching libinput events too early - If Wayland subsurfaces have circular relationships, disconnect the client instead of crashing - When resizing terminals interactively, don't offset the position - Fix broken timestamp behaviour if X11 timestamps overflow - Fix a memory leak - Ensure clock is updated when going from fullscreen app to overview - Fix artifacts around GNOME Shell magnifier cursor - Fix monitor tiling on X11 - Configure input devices correctly in X11 (LP: #1899206, LP: #1899509) - Avoid spurious warnings in log - Event does not have a stage: discarding - assertion 'CLUTTER_IS_STAGE (stage)' failed - Make sure build fails if Xwayland -initfd is requested but not available (not relevant in Debian, we don't request this yet) - Update translations: pt * d/p/backend-Don-t-pull-generated-headers-indirectly.patch: Add a patch from upstream git master to fix parallel builds -- Marco Trevisan (Treviño) Tue, 15 Dec 2020 01:20:01 +0100 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1908158 Title: Update to 3.38.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Groovy: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on background painting, input devices settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1908158/+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 1908345] Re: package texlive-plain-generic (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/1908345 Title: package texlive-plain-generic (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive- doc/fonts/fontname/8a.html', which is also in package texlive-generic- recommended 2015.20160320-1 Status in texlive-extra package in Ubuntu: New Bug description: pls check ProblemType: Package DistroRelease: Ubuntu 20.04 Package: texlive-plain-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 15 16:13:48 2020 DuplicateSignature: package:texlive-plain-generic:(not installed) Unpacking texlive-plain-generic (2019.202000218-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BWgLqN/119-texlive-plain-generic_2019.202000218-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in package texlive-generic-recommended 2015.20160320-1 ErrorMessage: trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in package texlive-generic-recommended 2015.20160320-1 InstallationDate: Installed on 2020-12-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: texlive-extra Title: package texlive-plain-generic (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in package texlive-generic-recommended 2015.20160320-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1908345/+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 1908345] [NEW] package texlive-plain-generic (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also i
Public bug reported: pls check ProblemType: Package DistroRelease: Ubuntu 20.04 Package: texlive-plain-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 15 16:13:48 2020 DuplicateSignature: package:texlive-plain-generic:(not installed) Unpacking texlive-plain-generic (2019.202000218-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BWgLqN/119-texlive-plain-generic_2019.202000218-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in package texlive-generic-recommended 2015.20160320-1 ErrorMessage: trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in package texlive-generic-recommended 2015.20160320-1 InstallationDate: Installed on 2020-12-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: texlive-extra Title: package texlive-plain-generic (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in package texlive-generic-recommended 2015.20160320-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-extra (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-extra in Ubuntu. https://bugs.launchpad.net/bugs/1908345 Title: package texlive-plain-generic (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive- doc/fonts/fontname/8a.html', which is also in package texlive-generic- recommended 2015.20160320-1 Status in texlive-extra package in Ubuntu: New Bug description: pls check ProblemType: Package DistroRelease: Ubuntu 20.04 Package: texlive-plain-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 15 16:13:48 2020 DuplicateSignature: package:texlive-plain-generic:(not installed) Unpacking texlive-plain-generic (2019.202000218-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BWgLqN/119-texlive-plain-generic_2019.202000218-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in package texlive-generic-recommended 2015.20160320-1 ErrorMessage: trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in package texlive-generic-recommended 2015.20160320-1 InstallationDate: Installed on 2020-12-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: texlive-extra Title: package texlive-plain-generic (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/fonts/fontname/8a.html', which is also in package texlive-generic-recommended 2015.20160320-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1908345/+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 1908341] Re: /usr/bin/gnome-shell:11:get_application_proxy:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #1962 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1962 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1962 Importance: Unknown Status: Unknown ** Summary changed: - /usr/bin/gnome-shell:11:get_application_proxy:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now + gnome-shell crashed with SIGSEGV in get_application_proxy() from g_task_return_now() from g_task_return() from init_second_async_cb() from g_task_return_now() ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Tags removed: 19.04-2019.4 artful cosmic disco eoan kylin-17.10 kylin-19.10 wily yakkety zesty ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- 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/1908341 Title: gnome-shell crashed with SIGSEGV in get_application_proxy() from g_task_return_now() from g_task_return() from init_second_async_cb() from g_task_return_now() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.1-1ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/1614f6f99fae747f6d3291c5cdbc46a816cc5025 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908341/+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 1908341] [NEW] gnome-shell crashed with SIGSEGV in get_application_proxy() from g_task_return_now() from g_task_return() from init_second_async_cb() from g_task_return_now()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.1-1ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/1614f6f99fae747f6d3291c5cdbc46a816cc5025 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-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Medium Status: Confirmed ** Tags: bionic focal groovy xenial -- 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/1908341 Title: gnome-shell crashed with SIGSEGV in get_application_proxy() from g_task_return_now() from g_task_return() from init_second_async_cb() from g_task_return_now() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.1-1ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/1614f6f99fae747f6d3291c5cdbc46a816cc5025 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908341/+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 1907870] Re: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9
That sounds like a different bug. The cause of this bug appears to be related to your HDMI monitor not having a current mode set. Although it does list a 'preferred' mode. That much is clear in the xrandr output. Failing to set a current mode is most likely a bug in 'libmutter'. -- 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/1907870 Title: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9 Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00
[Desktop-packages] [Bug 1907870] Re: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9
I read about a bug similar to this affecting mutter 3.34,but said that they can see the poi ter in the second screen. In this case my monitor falls in no-signal after a few seconds of trying to get the correct mode. (pls, sorry for my English) Regards JM -- 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/1907870 Title: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9 Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55
[Desktop-packages] [Bug 1908314] Re: Flicking screen on intel card
I'm guessing this would be bug 1896091, but to be sure please attach a photo or video of the problem. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908314 Title: Flicking screen on intel card Status in Ubuntu: Incomplete Bug description: Flicking screen on intel card ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 22:46:01 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a0] InstallationDate: Installed on 2020-12-10 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude 7480 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=UUID=2d2eba82-dddc-469c-8508-b0cc7269226b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2020 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd07/26/2020:br1.19:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1908314/+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 1908273] Re: Software stopped working
The only relevant error I can see is a crash in your graphics driver is affecting some Python app: [681600.192682] python3.8[1480136]: segfault at 24 ip 7fbbd34a3c14 sp 7ffc3c62aef0 error 6 in iris_dri.so[7fbbd2a72000+d49000] [681600.192702] Code: 2b 7e 30 01 c7 81 ff ff ff 00 00 0f 87 9d 17 00 00 48 01 c8 48 89 46 38 48 85 c9 0f 84 10 06 00 00 83 ea 01 81 ca 00 00 09 78 <89> 11 48 8d 51 04 45 85 ff 74 76 41 8d 47 ff 48 8d 4c c1 0c 0f 1f Please try: 1. Launching the affected apps from a Terminal window then copy and paste any errors you see here. 2. Check for crash reports using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908273 Title: Software stopped working Status in mesa package in Ubuntu: Incomplete Bug description: After update to Ubuntu 20.04.1 LTS some of my software stopped working, all of it is visualization software: VMD, Discovery Studio, PyMOL, Gmolden, Avogadro. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 14:41:52 2020 DistUpgraded: 2020-11-21 20:16:19,197 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Wykonanie procesu potomnego „./xorg_fix_proprietary.py” (Nie ma takiego pliku ani katalogu) się nie powiodło (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8537] InstallationDate: Installed on 2020-05-20 (208 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-21 (23 days ago) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8537 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD0097RK4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G6 dmi.product.sku: 5PQ09EA#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908273/+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 1907870] Re: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9
I think this is probably a bug in 'mutter'. Less likely a bug in 'gnome- control-center' or 'xorg-server'. ** Summary changed: - Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 + HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9 ** No longer affects: linux (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags added: multimonitor -- 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/1907870 Title: HDMI monitor detected but black screen (has a preferred mode but no current mode) with Intel UHD graphics on kernel 5.9 Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 5
[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)
It's likely this freeze was actually a crash, and that crash might have been fixed already under a different guise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Focal: Incomplete Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, clicking on an app folder and clicking on the blank area freezes gnome shell and it makes the session completely unusable and non recoverable. How to reproduce: 1- Click 9 dots on bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Click on an app folder to open it. 3- Click on the blank area outside of the opened folder dialog. 4- Gnome shell gets freezes and never come back from this state, on both wayland session and x11 session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:00:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1872268/+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 1908265] Re: bad heating
I can't see any explanation for such a problem in the attached files. Please run 'top' in a Terminal window and tell us what processes are using the most CPU. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908265 Title: bad heating Status in Ubuntu: Incomplete Bug description: i had dell pre-installed ubuntu, but i had erase it. now i am facing heating issues ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 17:59:23 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08c8] InstallationDate: Installed on 2020-12-11 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Bus 001 Device 002: ID 27c6:5301 Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-124-generic root=UUID=4f0e25d7-2cd2-474f-9088-9df1ffccd1ce ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0H40C6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:svnDellInc.:pnVostro3480:pvr:rvnDellInc.:rn0H40C6:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3480 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1908265/+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 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
The crash appears to be relatively rare globally: 20.04: 602 times 20.10: 52 times I hope I was wrong thinking that this might be caused by the desktop- icons extension. Please start by uninstalling all extensions except those three that are shipped with Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 Status in gjs: Unknown Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215 --- A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[2
[Desktop-packages] [Bug 1906600] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444031/+files/acpidump.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-
[Desktop-packages] [Bug 1906600] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444027/+files/ProcModules.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device
[Desktop-packages] [Bug 1906600] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444026/+files/ProcInterrupts.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820]
[Desktop-packages] [Bug 1906600] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444024/+files/ProcCpuinfoMinimal.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [160687534
[Desktop-packages] [Bug 1906600] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444025/+files/ProcEnviron.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device
[Desktop-packages] [Bug 1906600] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444023/+files/ProcCpuinfo.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device
[Desktop-packages] [Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
You can also try disabling the 'Desktop Icons' extension in the 'Extensions' app. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 Status in gjs: Unknown Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215 --- A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modes
[Desktop-packages] [Bug 1906600] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444030/+files/WifiSyslog.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (
[Desktop-packages] [Bug 1906600] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444029/+files/UdevDb.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-dev-w
[Desktop-packages] [Bug 1906600] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444028/+files/PulseList.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2
[Desktop-packages] [Bug 1906600] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444022/+files/Lsusb-v.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-de
[Desktop-packages] [Bug 1906600] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444021/+files/Lsusb-t.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-de
[Desktop-packages] [Bug 1906600] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444020/+files/Lsusb.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-dev-wlo
[Desktop-packages] [Bug 1906600] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444014/+files/AlsaInfo.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-
[Desktop-packages] [Bug 1906600] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444019/+files/Lspci-vt.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-
[Desktop-packages] [Bug 1906600] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444018/+files/Lspci.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-dev-wlo
[Desktop-packages] [Bug 1906600] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444017/+files/IwConfig.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-
[Desktop-packages] [Bug 1906600] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444016/+files/CurrentDmesg.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] devi
[Desktop-packages] [Bug 1906600] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1906600/+attachment/5444015/+files/CRDA.txt -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: Confirmed Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-dev-wlo1)
[Desktop-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
If I have done this correctly, and that is truly questionable, I just installed one of the generic kernels from https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.10-rc6/amd64/ then restarted the PC and was connected for 8 - 10 minutes, but then the connection dropped again. I had installed: linux- modules-5.10.0-051000rc6-generic_5.10.0-051000rc6.202011291930_amd64.deb. Here is what it shows I am running: bryan@bryan-HP-Notebook:~$ uname -r 5.4.0-58-generic I will run the apport again to upload immediately after posting this message. As always, I thank you for your help. Cheers! ** Description changed: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:1
[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)
I don't know why, but when I installed Gnome tweak, Gnome tweak tool, Gnome shell extensions, the problem disappeared -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Focal: Incomplete Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, clicking on an app folder and clicking on the blank area freezes gnome shell and it makes the session completely unusable and non recoverable. How to reproduce: 1- Click 9 dots on bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Click on an app folder to open it. 3- Click on the blank area outside of the opened folder dialog. 4- Gnome shell gets freezes and never come back from this state, on both wayland session and x11 session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:00:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1872268/+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 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal
We don't maintain those extensions directly. Really it's up to the authors of the extensions to keep them up to date upstream. And in the Ubuntu archive it's up to anyone interested to update them, using the SRU process: https://wiki.ubuntu.com/StableReleaseUpdates -- 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/1903764 Title: [SRU] Update gnome-shell to 3.36.7 in Focal Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Focal: Fix Committed Bug description: [Impact] This is the current GNOME 3.36.x stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix potential stack overflow in libcroco [Michael; !1404] * Fix system action search regressions [Florian; #3169] * Fix week number alignment when using font-scaling [Joonas; !1415] * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, !1451, #2230, !1423] Contributors: Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, Bastien Nocera, Daniel van Vugt Translators: Marek Černocký [cs] 3.36.6 == * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071] * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420] Contributors: Sebastian Keller, Zephaniah E. Loss-Cutler-Hull Translators: Goran Vidović [hr], Balázs Úr [hu] 3.36.5 == * Fix extension updates when many extensions are installed [Jeremias; !1363] * Fix missing icons in on-screen keyboard [Emre; #2631, #3007] * Fix delay when showing calendar events [Sebastian; #2992] * Fix app picker regressions on small displays [Sebastian; #2234, !1375, !1378] * Fix top bar navigation when NumLock is active [Olivier; #550] * Delay login animation until wallpaper has loaded [Michael; #734996] * Revert changes that caused mispositioning in overview in multi-monitor setups [Robert; #2971] * Reset auth prompt on login screen on VT switch before fade in [Ray; #2997] * Fix stuck grab when destroying open popup menu [Florian; #3022] * Misc. bug fixes and cleanups [Florian, Carlos, Andre, Jonas; !1357, !1371, !1381, #3037, #3005, !1386, !1390] Contributors: Michael Catanzaro, Jonas Dreßler, Olivier Fourdan, Carlos Garnacho, Sebastian Keller, Robert Mader, Andre Moreira Magalhaes, Florian Müllner, Jeremias Ortega, Ray Strode, Emre Uyguroglu Translators: Boyuan Yang [zh_CN], Rafael Fontenelle [pt_BR] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. The verification is going to include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [Regression potential] There have been fixes in various places: system actions search in different languages, alignment of week numbers in calendar menu, lock screen, scaling of app icons on Hi-dpi displays, extension updates, missing icons in OSK and showing calendar events in calendar menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 19:40:03 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-26 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835706] Re: Extensions don't load in gnome-shell 3.36 (Ubuntu 20.04)
** Summary changed: - Extensions don't load in gnome-shell 3.34/3.36 (Ubuntu 19.10-20.04) + Extensions don't load in gnome-shell 3.36 (Ubuntu 20.04) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.36 (Ubuntu 20.04) Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-weather package in Ubuntu: Confirmed Bug description: Some extensions don't load in gnome-shell 3.34/3.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896334] Re: SRU 3.36.6
It seems bug 1903764 is tracking 3.36.7 now. And the changelog in proposed mentions this bug in the update to 3.36.6 that precedes it. But really they're both the same update now -- to 3.36.7. ** Summary changed: - SRU 3.36.6/3.36.7 + SRU 3.36.6 -- 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/1896334 Title: SRU 3.36.6 Status in gnome-shell package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in yaru-theme source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6 Since the theme side of the project in ubuntu is shipped via Yaru theme, that project is included in the SRU. The changes involving yaru here are ONLY gnome-shell upstream changes applied to the Yaru sources, as per this we can consider them also part of the GNOME release. In fact: - Ubuntu's GNOME shell uses a Yaru theme based on upstream gnome-shell This theme basically takes the shell's data/ directory, applies some diffs and generates a gresource file out of it, that it's then loaded on startup (in place of the upstream one). - GNOME Shell applied some fixes to the theme (se its data/ directory diffs) - In order to get those fixes in Ubuntu main session we have to sync the upstream changes applied to such dir to yaru's src/gnome-shell path - You can easily compare the diffs applied there to match the ones happening in its upstream counterpart. The yaru-theme's `gnome-shell/upstream` directory is just for documentation and to allow three way merges when updating to new versions of gnome-shell, and it is not used for generating the final packages at all [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in popup-grab handling, gdm view fixes, lockscreen display changes in some hw, extensions updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+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 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
** Attachment added: "grep . /sys/class/drm/*/modes > drmmodes.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907870/+attachment/5444004/+files/drmmodes.txt -- 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/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0
[Desktop-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
** Attachment added: "Xrandr with Wayland output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907870/+attachment/5444003/+files/xrandrv.txt -- 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/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 7
[Desktop-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
Just in case... same cable and same external monitor works perfect on my HP Omen 15 with Nvidia GTX1060 and Ubuntu 20.04 -- 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/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-1 disco
[Desktop-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
Using Wayland didn't solve the problem, even worst... it makes the desktop more unstable. -- 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/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-1 disconnected (normal left inverted r
[Desktop-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
** Attachment added: "Xrandr with Xorg output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907870/+attachment/5444002/+files/xrandrv_xorg.txt -- 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/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94
[Desktop-packages] [Bug 1908312] Re: [Echo-NHH, playback] fails after a while (stutter)
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1908312 Title: [Echo-NHH, playback] fails after a while (stutter) Status in alsa-driver package in Ubuntu: New Bug description: Bluetooth playback suffers from intermittent stutters. Happens on multiple bluetooth speakers (I tested it).Apparently this is a known problem because there is a whole thread about it on Reddit, which seems a bit ridiculous this has been an issue for 9 or 10 years and hasn't been resolved yet because bluetooth speakers are so common now. Playback improved somewhat when auto-mute is disabled via alsmixer (but ONLY when the system is active. If screensaver engages to shut down the screens, the stutters begin shortly thereafter.Prior to disabling auto-mute, the system would intermittently stutter regardless of whether screen saver/power saver modes were active. Am using Ubuntu 20.10 (had the same issue under the prior version of ubuntu too). Software center version is 3.38.1. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j 1726 F pulseaudio /dev/snd/controlC1: j 1726 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 15:35:16 2020 InstallationDate: Installed on 2020-05-21 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Echo-NHH Symptom_Type: Sound works for a while, then breaks Title: [Echo-NHH, playback] fails after a while UpgradeStatus: Upgraded to groovy on 2020-10-28 (48 days ago) dmi.bios.date: 01/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1908312/+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 1908312] [NEW] [Echo-NHH, playback] fails after a while (stutter)
You have been subscribed to a public bug: Bluetooth playback suffers from intermittent stutters. Happens on multiple bluetooth speakers (I tested it).Apparently this is a known problem because there is a whole thread about it on Reddit, which seems a bit ridiculous this has been an issue for 9 or 10 years and hasn't been resolved yet because bluetooth speakers are so common now. Playback improved somewhat when auto-mute is disabled via alsmixer (but ONLY when the system is active. If screensaver engages to shut down the screens, the stutters begin shortly thereafter.Prior to disabling auto-mute, the system would intermittently stutter regardless of whether screen saver/power saver modes were active. Am using Ubuntu 20.10 (had the same issue under the prior version of ubuntu too). Software center version is 3.38.1. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j 1726 F pulseaudio /dev/snd/controlC1: j 1726 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 15:35:16 2020 InstallationDate: Installed on 2020-05-21 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Echo-NHH Symptom_Type: Sound works for a while, then breaks Title: [Echo-NHH, playback] fails after a while UpgradeStatus: Upgraded to groovy on 2020-10-28 (48 days ago) dmi.bios.date: 01/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd01/11/2013:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- [Echo-NHH, playback] fails after a while (stutter) https://bugs.launchpad.net/bugs/1908312 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- 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 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
Are there any known regressions/issues from this fix? The actual crash seems to be fixed but there still seems to be some confusion between the laptop display and external monitors, the internal display is active when the lid is closed, and suspend with lid closed messes up the desktop/monitor "fullscreen" size. I'm using a Razer Blade 15 with 3 external monitors. If I boot the laptop with the lid closed, "Screen Display" settings shows the laptop display is active, and it's possible to drag a window off the screen to where the laptop display is supposed to be (but lid is closed, it's off). If I then suspend and resume, the screen sizing gets messed up - hitting F11 to fullscreen a window on the 2nd monitor results in it expanding to fill 2 monitors instead of 1. However, if I open the laptop lid, and suspend with the lid open, then F11 fullscreen correctly fills 1 monitor as it should. Ubuntu 20.04 LTS has the problem. Ubuntu 20.10 works ok (lid closed on boot=no active laptop display, after suspend F11 still works) -- 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/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Groovy: Fix Released Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1881197] Update Released
The verification of the Stable Release Update for gnome-system-monitor has completed successfully and the package is now being 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 Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. Status in Gnome System Monitor: Unknown Status in gnome-system-monitor package in Ubuntu: Fix Released Status in gnome-system-monitor source package in Focal: Fix Released Bug description: [Impact] * gnome-system-monitor 3.36.1 is the latest minor update in the 3.36 series * it fixes one bug (https://gitlab.gnome.org/GNOME/gnome-system- monitor/-/issues/142), and includes translation updates for a few languages, but these won't impact the package in Ubuntu because it uses the gnome language packs [Test Case] * In gnome-system-monitor's preferences window, in the resources tab, set the update interval to 0.5 seconds * Open the resources tab and watch the network traffic graph while generating incoming and outgoing traffic (for example by running speedtest-cli) * Expected result: outgoing and incoming traffic on the graph is consistent with the actual traffic * Actual result without the bugfix in 3.36.1: the graph shows null outgoing and incoming traffic, even though the totals seem to be updated in the labels below the graph [Where problems could occur] * Given the one and only code change in this update is a one-liner that adds a cast to double (https://gitlab.gnome.org/GNOME/gnome- system-monitor/-/commit/3e916c4ee21cede8465e9378fa07e9a71a472c2f), regression potential seems fairly limited. Looking at the code in more details, the change is in a function that is used only to draw the network traffic graph, it's not common code used to draw other graphs. So verifying that the bug is indeed fixed should be enough to be confident there are no regressions. Testing should be carried out with various values for the update interval, both integers and non- integers. * As mentioned in the impact section, this update includes translation updates, but those shouldn't apply because translations for gnome-system-monitor are shipped externally as part of the language-pack-gnome-*-base packages [Original description] 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) gnome-system-monitor: Instalado: 3.36.0-1 Candidato: 3.36.0-1 Tabela de versão: *** 3.36.0-1 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1 500 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) There should be a graph drawn with the info about my network usage, as well as number on the download/upload speeds. 4) Pretty much nothing happens. It calculates how much data I've downloaded/uploaded since the OS was booted, but that's it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 17:51:55 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2019-12-06 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1881197/+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 1881197] Re: No network usage info presented, always 0 bytes/s.
This bug was fixed in the package gnome-system-monitor - 3.36.1-0ubuntu0.20.04.1 --- gnome-system-monitor (3.36.1-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1881197) * debian/control{,.in}: require meson >= 0.50 -- Olivier Tilloy Mon, 07 Dec 2020 15:48:25 +0100 ** Changed in: gnome-system-monitor (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. Status in Gnome System Monitor: Unknown Status in gnome-system-monitor package in Ubuntu: Fix Released Status in gnome-system-monitor source package in Focal: Fix Released Bug description: [Impact] * gnome-system-monitor 3.36.1 is the latest minor update in the 3.36 series * it fixes one bug (https://gitlab.gnome.org/GNOME/gnome-system- monitor/-/issues/142), and includes translation updates for a few languages, but these won't impact the package in Ubuntu because it uses the gnome language packs [Test Case] * In gnome-system-monitor's preferences window, in the resources tab, set the update interval to 0.5 seconds * Open the resources tab and watch the network traffic graph while generating incoming and outgoing traffic (for example by running speedtest-cli) * Expected result: outgoing and incoming traffic on the graph is consistent with the actual traffic * Actual result without the bugfix in 3.36.1: the graph shows null outgoing and incoming traffic, even though the totals seem to be updated in the labels below the graph [Where problems could occur] * Given the one and only code change in this update is a one-liner that adds a cast to double (https://gitlab.gnome.org/GNOME/gnome- system-monitor/-/commit/3e916c4ee21cede8465e9378fa07e9a71a472c2f), regression potential seems fairly limited. Looking at the code in more details, the change is in a function that is used only to draw the network traffic graph, it's not common code used to draw other graphs. So verifying that the bug is indeed fixed should be enough to be confident there are no regressions. Testing should be carried out with various values for the update interval, both integers and non- integers. * As mentioned in the impact section, this update includes translation updates, but those shouldn't apply because translations for gnome-system-monitor are shipped externally as part of the language-pack-gnome-*-base packages [Original description] 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) gnome-system-monitor: Instalado: 3.36.0-1 Candidato: 3.36.0-1 Tabela de versão: *** 3.36.0-1 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1 500 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) There should be a graph drawn with the info about my network usage, as well as number on the download/upload speeds. 4) Pretty much nothing happens. It calculates how much data I've downloaded/uploaded since the OS was booted, but that's it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 17:51:55 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2019-12-06 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1881197/+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 1875717] Re: Opening file from Samba share results in Document in Use
So clearly the problem here is with Thunar and PCManFM-Qt, at least something about how they handle the Samba connection that makes LibreOffice (and only LibreOffice, apparently) unhappy. So I have three thoughts: 1. Connect to the Samba share manually. This way we're not relying on the logic in the file manager to do the mounting. Assuming this works correctly for all file managers, then we can safely put the blame on the file managers themselves even though there must be something about LibreOffice that makes it particular. https://help.ubuntu.com/community/Samba/SambaClientGuide#Connecting_using_CIFS 2. Run the file manager on the command line and see if it spits anything out. I know with PCManFM-Qt, it also handles desktop management, so there's a daemon running. You can find that and kill it and then run `pcmanfm-qt --profile=lxqt 2>&1`. I'm less intimately familiar with Thunar so I'll leave it as an exercise to the reader to figure that out. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+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 1908314] [NEW] Flicking screen on intel card
Public bug reported: Flicking screen on intel card ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 22:46:01 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a0] InstallationDate: Installed on 2020-12-10 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude 7480 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=UUID=2d2eba82-dddc-469c-8508-b0cc7269226b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2020 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd07/26/2020:br1.19:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908314 Title: Flicking screen on intel card Status in xorg package in Ubuntu: New Bug description: Flicking screen on intel card ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 22:46:01 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a0] InstallationDate: Installed on 2020-12-10 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude 7480 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=UUID=2d2eba82-dddc-469c-8508-b0cc7269226b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2020 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd07/26/2020:br1.19:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1908314/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : des
[Desktop-packages] [Bug 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal
The gse list contains some extensions that have already been broken since Focal release in April 2020. Theses are the ones that I know: gnome-shell-extension-weather → LP: #1873661, LP: #1835706 gnome-shell-extension-onboard → got removed in Debian on 2020-01-09 because of incompatibility with recent versions of gnome-shell (https://tracker.debian.org/news/1092762/accepted-onboard-141-5-source- into-unstable/) gnome-shell-extension-multi-monitors → LP: #1873789 gnome-shell-extension-gsconnect(-browsers) → very broken, only supports GNOME 3.30, Ubuntu-specific, hasn't been updated since 2019-01-08 -- 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/1903764 Title: [SRU] Update gnome-shell to 3.36.7 in Focal Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Focal: Fix Committed Bug description: [Impact] This is the current GNOME 3.36.x stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix potential stack overflow in libcroco [Michael; !1404] * Fix system action search regressions [Florian; #3169] * Fix week number alignment when using font-scaling [Joonas; !1415] * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, !1451, #2230, !1423] Contributors: Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, Bastien Nocera, Daniel van Vugt Translators: Marek Černocký [cs] 3.36.6 == * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071] * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420] Contributors: Sebastian Keller, Zephaniah E. Loss-Cutler-Hull Translators: Goran Vidović [hr], Balázs Úr [hu] 3.36.5 == * Fix extension updates when many extensions are installed [Jeremias; !1363] * Fix missing icons in on-screen keyboard [Emre; #2631, #3007] * Fix delay when showing calendar events [Sebastian; #2992] * Fix app picker regressions on small displays [Sebastian; #2234, !1375, !1378] * Fix top bar navigation when NumLock is active [Olivier; #550] * Delay login animation until wallpaper has loaded [Michael; #734996] * Revert changes that caused mispositioning in overview in multi-monitor setups [Robert; #2971] * Reset auth prompt on login screen on VT switch before fade in [Ray; #2997] * Fix stuck grab when destroying open popup menu [Florian; #3022] * Misc. bug fixes and cleanups [Florian, Carlos, Andre, Jonas; !1357, !1371, !1381, #3037, #3005, !1386, !1390] Contributors: Michael Catanzaro, Jonas Dreßler, Olivier Fourdan, Carlos Garnacho, Sebastian Keller, Robert Mader, Andre Moreira Magalhaes, Florian Müllner, Jeremias Ortega, Ray Strode, Emre Uyguroglu Translators: Boyuan Yang [zh_CN], Rafael Fontenelle [pt_BR] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. The verification is going to include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [Regression potential] There have been fixes in various places: system actions search in different languages, alignment of week numbers in calendar menu, lock screen, scaling of app icons on Hi-dpi displays, extension updates, missing icons in OSK and showing calendar events in calendar menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 19:40:03 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-26 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903764/+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 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
Thanks, unsure what's the issue, it might be worth reporting upstream on https://bugzilla.mozilla.org There are issues discussed on https://bugzilla.mozilla.org/show_bug.cgi?id=1590474 but it sounds a bit different Did you try the deb of 78 or an older version? Could you also give some details on how to trigger the warning, is there a public website where an account could be created for testing? ** Bug watch added: Mozilla Bugzilla #1590474 https://bugzilla.mozilla.org/show_bug.cgi?id=1590474 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+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 1881200] Re: onboard defaults to tablet mode
** Package changed: onboard (Ubuntu) => onboard -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1881200 Title: onboard defaults to tablet mode Status in Onboard: New Bug description: I am using onboard on arch Linux with i3 on a convertible laptop. I have "Auto-show when editing text" enabled as well as "Auto-show only in tablet mode". The acpid service is enabled with systemd and works properly. onboard is started when logging in through "exec --no- startup-id onboard" within the i3 configs. When first started, onboard automatically assumes it is in tablet mode and will auto-show the keyboard when editing text. Once the computer is flipped into tablet mode and flipped back into laptop mode, onboard doesn't automatically show, which is the expected behavior. I assume this is because onboard doesn't receive an initial acpid message telling it it is starting in laptop mode, so it assumes tablet mode initially. Having a setting to specify whether to start in tablet or laptop mode could fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1881200/+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 1860653] Re: onboard cannot be moved under wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: onboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1860653 Title: onboard cannot be moved under wayland Status in onboard package in Ubuntu: Confirmed Bug description: When shifting from Xorg to wayland, I can no longer move the whole keyboard with tap&hold&shift on the 4arrows icon, as I could before. This is a pity as the magnification feature in wayland is great for a tablet. kubuntu 18.04, plasma 5.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1860653/+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 1902801] Re: Encrypted attachments cannot be opened or saved as decrypted files
https://bugs.launchpad.net/ubuntu/+source/thunderbird/1:78.6.0+build1-0ubuntu1 ** Changed in: thunderbird (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1902801 Title: Encrypted attachments cannot be opened or saved as decrypted files Status in thunderbird package in Ubuntu: Fix Released Status in Arch Linux: Fix Released Bug description: I have been using enigmail in thunderbird until I upgraded Ubuntu and with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1 As enigmail is now integrated in thunderbird, I have gone through the painful upgrade process (it does not allow to look into passwordmanager for the pasphrase of the gpg keys it wants to import by blocking all other windows), and decryption of emails now works. But when looking at a decrypted email, fully being able to read the text content, when I want to use the Menu option "Decrypt and Open" by right clicking on an attachment (pdf in this case), nothing happens. What I expect to happen: The pdf file being shown to me in the pdf viewer. Or some error being displayed, or maybe I am asked for my gpg passphrase again for additional security. When trying the option "Decrypt and save as", next I can select a folder and filename, (the pdf name without .gpg) and chose "save" - but when looking into that folder, there is no decrypted file. (I tried this plenty of time, I am sure its not there, and I did this action before the upgrade many times successfully). What I would expect: the attached file without the .gpg suffix (the filename proposed when opening the dialog, which I did not change) in the selected directory. $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy thunderbird thunderbird: Installed: 1:78.3.2+build1-0ubuntu1 Candidate: 1:78.3.2+build1-0ubuntu1 Version table: *** 1:78.3.2+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1902801/+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 1907470] Re: Thunderbird latest/stable snap's release note shows 'Daily build' instead
seems it was due to an invalid configure key in the distributor ini, should be fixed in edge with the next build ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1907470 Title: Thunderbird latest/stable snap's release note shows 'Daily build' instead Status in thunderbird package in Ubuntu: Fix Committed Bug description: Hello there! Under Ubuntu 20.04, with Thunderbird installed using snap (latest/stable: 78.5.1 2020-12-02), the release note shows up as `daily build` with a tab navigating to https://start.thunderbird.net /en-US/daily/?uri=/thunderbird/releasenotes/&locale=en- US&version=78.5.1&channel=release-cck- ubuntu&os=Linux&buildid=20201130232704 The expected behavior is that the release note should show up as Thunderbird stable build. I have asked in the snapcraft forum and one member have also confirmed this issue (https://forum.snapcraft.io/t/question-regarding-the- thunderbird-snap-latest-stable-release-note/21496). Thank you for your help and hope you have a great day! Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1907470/+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 1894006] Re: firefox crashes with MOZ_ENABLE_WAYLAND=1 when apparmor profile is enforced
This bug was fixed in the package firefox - 84.0+build3-0ubuntu0.20.04.1 --- firefox (84.0+build3-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (84.0+build3) -- Olivier Tilloy Mon, 14 Dec 2020 09:52:38 +0100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1894006 Title: firefox crashes with MOZ_ENABLE_WAYLAND=1 when apparmor profile is enforced Status in firefox package in Ubuntu: Fix Released Bug description: Recently I decided to try running firefox 80 directly via Wayland, instead of via X11. It crashed. (I haven't tried any previous versions.) I found the following in /var/log/audit/audit.log: type=AVC msg=audit(1599023168.948:3997869): apparmor="DENIED" operation="mknod" profile="firefox" name="/dev/shm/wayland.mozilla.ipc.0" pid=1042373 comm="Compositor" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 I added the following to /etc/apparmor.d/local/usr.bin.firefox: /dev/shm/wayland.mozilla.* rw, reloaded the profile: sudo apparmor_parser -r < /etc/apparmor.d/usr.bin.firefox and now it works. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 4497 F pulseaudio /dev/snd/controlC0: paul 4497 F pulseaudio BuildID: 20200818235255 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: GNOME DefaultProfileIncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2011-11-06 (3223 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) KernLog: NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 zfs zunicode zavl icp zcommon znvpair Package: firefox 80.0+build2-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=617752e9-3054-4928-881c-0e0651a839b0 ro splash quiet ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile2PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile2 - LastVersion=80.0/20200818235255 Profile1 - LastVersion=78.0.2/20200708170202 (Out of date) Profile0 (Default) - LastVersion=80.0/20200818235255 (In use) RunningIncompatibleAddons: True Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-25 (190 days ago) UserGroups: adm admin cdrom dialout docker libvirt lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M1AKT35A dmi.board.name: 3111 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258011708158 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1AKT35A:bd03/21/2018:svnLENOVO:pn10MRCTO1WW:pvrThinkCentreM710q:rvnLENOVO:rn3111:rvrSDK0J40700WIN3258011708158:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710q dmi.product.name: 10MRCTO1WW dmi.product.sku: LENOVO_MT_10MR_BU_LENOVO_FM_ThinkCentre M710q dmi.product.version: ThinkCentre M710q dmi.sys.vendor: LENOVO modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1894006/+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 1894006] Re: firefox crashes with MOZ_ENABLE_WAYLAND=1 when apparmor profile is enforced
This bug was fixed in the package firefox - 84.0+build3-0ubuntu0.20.10.1 --- firefox (84.0+build3-0ubuntu0.20.10.1) groovy; urgency=medium * New upstream release (84.0+build3) -- Olivier Tilloy Mon, 14 Dec 2020 09:54:22 +0100 ** Changed in: firefox (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: firefox (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1894006 Title: firefox crashes with MOZ_ENABLE_WAYLAND=1 when apparmor profile is enforced Status in firefox package in Ubuntu: Fix Released Bug description: Recently I decided to try running firefox 80 directly via Wayland, instead of via X11. It crashed. (I haven't tried any previous versions.) I found the following in /var/log/audit/audit.log: type=AVC msg=audit(1599023168.948:3997869): apparmor="DENIED" operation="mknod" profile="firefox" name="/dev/shm/wayland.mozilla.ipc.0" pid=1042373 comm="Compositor" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 I added the following to /etc/apparmor.d/local/usr.bin.firefox: /dev/shm/wayland.mozilla.* rw, reloaded the profile: sudo apparmor_parser -r < /etc/apparmor.d/usr.bin.firefox and now it works. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 4497 F pulseaudio /dev/snd/controlC0: paul 4497 F pulseaudio BuildID: 20200818235255 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: GNOME DefaultProfileIncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2011-11-06 (3223 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) KernLog: NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 zfs zunicode zavl icp zcommon znvpair Package: firefox 80.0+build2-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=617752e9-3054-4928-881c-0e0651a839b0 ro splash quiet ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd} Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile2PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile2 - LastVersion=80.0/20200818235255 Profile1 - LastVersion=78.0.2/20200708170202 (Out of date) Profile0 (Default) - LastVersion=80.0/20200818235255 (In use) RunningIncompatibleAddons: True Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-25 (190 days ago) UserGroups: adm admin cdrom dialout docker libvirt lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M1AKT35A dmi.board.name: 3111 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258011708158 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1AKT35A:bd03/21/2018:svnLENOVO:pn10MRCTO1WW:pvrThinkCentreM710q:rvnLENOVO:rn3111:rvrSDK0J40700WIN3258011708158:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710q dmi.product.name: 10MRCTO1WW dmi.product.sku: LENOVO_MT_10MR_BU_LENOVO_FM_ThinkCentre M710q dmi.product.version: ThinkCentre M710q dmi.sys.vendor: LENOVO modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1894006/+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 1907470] Re: Thunderbird latest/stable snap's release note shows 'Daily build' instead
There are discussions upstream about similar issues, example https://bugzilla.mozilla.org/show_bug.cgi?id=1637349 which suggests it could be due to a channel configuration but we don't set anything special... ** Bug watch added: Mozilla Bugzilla #1637349 https://bugzilla.mozilla.org/show_bug.cgi?id=1637349 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1907470 Title: Thunderbird latest/stable snap's release note shows 'Daily build' instead Status in thunderbird package in Ubuntu: Confirmed Bug description: Hello there! Under Ubuntu 20.04, with Thunderbird installed using snap (latest/stable: 78.5.1 2020-12-02), the release note shows up as `daily build` with a tab navigating to https://start.thunderbird.net /en-US/daily/?uri=/thunderbird/releasenotes/&locale=en- US&version=78.5.1&channel=release-cck- ubuntu&os=Linux&buildid=20201130232704 The expected behavior is that the release note should show up as Thunderbird stable build. I have asked in the snapcraft forum and one member have also confirmed this issue (https://forum.snapcraft.io/t/question-regarding-the- thunderbird-snap-latest-stable-release-note/21496). Thank you for your help and hope you have a great day! Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1907470/+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 1908284] Re: [snap] chromium headless crashes in revision 1424
I should have specified that I'm experiencing the error on Ubuntu Server. I just tested on my laptop running Ubuntu Desktop and it works fine. I also found that on my headless Ubuntu Servers if you install the ubuntu-desktop metapackage before you install the chromium snap, everything will work fine then too. However, if you install the chromium snap before you install the ubuntu-desktop metapackage it will still be broken even after the ubuntu-desktop metapackage is done installing. I'd still reckon that this is a regression though, because chromium snap revision 1421 was working fine in headless mode on a standard install of Ubuntu Server without the need to install any other packages first. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1908284 Title: [snap] chromium headless crashes in revision 1424 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+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 1908299] [NEW] Selecting area to grab puts gnome-screenshot into a 100% CPU busy loop
Public bug reported: Save dialog never appears. I have used gnome-screenshot many times daily for years. This started happening yesterday. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 15:05:15 2020 InstallationDate: Installed on 2018-05-05 (955 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to focal on 2020-07-27 (141 days ago) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1908299 Title: Selecting area to grab puts gnome-screenshot into a 100% CPU busy loop Status in gnome-screenshot package in Ubuntu: New Bug description: Save dialog never appears. I have used gnome-screenshot many times daily for years. This started happening yesterday. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screenshot 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 15:05:15 2020 InstallationDate: Installed on 2018-05-05 (955 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to focal on 2020-07-27 (141 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1908299/+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 1899262] Update Released
The verification of the Stable Release Update for wpa has completed successfully and the package is now being 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 Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Bionic: Fix Released Bug description: * Impact One of the distro patch is incorrect and create issues when trying to query dbus properties * Test Case $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface shouldn't error out (the /1 reflect the interface number and could be a different value, check with d-feet if needed) * Regression potential The fixes is in the dbus interface, check that communication with desktop clients (indicator, applet, settings) still works correctly, returning expected informations on the signal, etc - dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties
This bug was fixed in the package wpa - 2:2.6-15ubuntu2.6 --- wpa (2:2.6-15ubuntu2.6) bionic; urgency=medium * debian/patches/fix-dbus-getall-request.patch: - update to a fixed version of the patch to not error out when not in AP mode, thanks Michael Nazzareno Trimarchi (lp: #1899262) -- Sebastien Bacher Wed, 11 Nov 2020 10:50:58 +0100 ** Changed in: wpa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Bionic: Fix Released Bug description: * Impact One of the distro patch is incorrect and create issues when trying to query dbus properties * Test Case $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface shouldn't error out (the /1 reflect the interface number and could be a different value, check with d-feet if needed) * Regression potential The fixes is in the dbus interface, check that communication with desktop clients (indicator, applet, settings) still works correctly, returning expected informations on the signal, etc - dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1908010] Re: [upstream] Thunderbird filters doesn't handle base64 encoded message
** Changed in: thunderbird (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1908010 Title: [upstream] Thunderbird filters doesn't handle base64 encoded message Status in thunderbird package in Ubuntu: New Bug description: User is able to define e-mail filters in Thunderbird. This can cover multiple fields like From:, To:, Subject: and Content . Using Content option allows a way to provide string which will be matched against e-mail content. Although this doesn't work when message is base64 encoded - this format is properly displayed by Thunderbird but it seems filters came to early and match user provided clear text against encoded text in e-mail. I confirmed this by defining filter with base64 fragment as desired string but this is not an option for more dynamic messages - adding one space before clear text string will change entrie string due to how base64 encode work so it needs to fully decode e-mail and then apply filters ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:68.10.0+build1-0ubuntu0.18.04.1 Uname: Linux 5.10.0-051000rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 BuildID: 20200629235513 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 02:19:49 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2015-05-08 (2046 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.10.0/20200629235513 (In use) SourcePackage: thunderbird UpgradeStatus: Upgraded to bionic on 2018-08-26 (840 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1908010/+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 1873638] Re: Titlebar buttons incorrectly placed when set to appear on the left
it's confirmed but low priority, it's cosmetic and not impacting the default layout -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873638 Title: Titlebar buttons incorrectly placed when set to appear on the left Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Unexpected button location on settings. Check image as screenshot attachment. Gnome Tweaks -> move the Titlebar buttons from Right to Left. Buttons should be paced on the extreme left -> for gnome-control- center they are centrally placed. OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question how be how to reproduce? To switch button on the left side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
The audio simply disappeared, because the sound card, when the voltage was reduced, reset, causing the kernel to recognize it as card 0 or card 1, different from the settings. Then the sound was gone. After testing the input source, the voltage of 3.3 V and 5 V was below normal (around 3.28 V and 5.08 V) causing the card to not work properly. After repairing the power supply, the voltage of 3.3 V and 5 V is around 3.32 V and 5.13 V. On the outside, the power supply appears to be of good quality, but inside it has few output capacitors. ** Changed in: alsa-driver (Ubuntu) Status: New => Opinion ** Changed in: alsa-driver (Ubuntu) Status: Opinion => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1
[Desktop-packages] [Bug 1908293] Re: "extract here" doesn't work
** No longer affects: file-roller (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1908293 Title: "extract here" doesn't work Status in pcmanfm-qt package in Ubuntu: New Bug description: In PCManFM-Qt, when I right click on archived files (zip) and choose "Extract here" to uncompress the file in the current folder, nothing happens, the file is not uncompressed at all. But if I use "Extract to", everything works like usual. When I use PCManFM-Qt as superuser (root), "Extract here" works fine. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1908293/+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 1908293] Re: "extract here" doesn't work
It seems the same problem reported in 2012 at https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1069611 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1908293 Title: "extract here" doesn't work Status in file-roller package in Ubuntu: New Status in pcmanfm-qt package in Ubuntu: New Bug description: In PCManFM-Qt, when I right click on archived files (zip) and choose "Extract here" to uncompress the file in the current folder, nothing happens, the file is not uncompressed at all. But if I use "Extract to", everything works like usual. When I use PCManFM-Qt as superuser (root), "Extract here" works fine. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1908293/+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 1873638] Re: Titlebar buttons incorrectly placed when set to appear on the left
The issue is not present in Fedora, it's Ubuntu specific. Will this nug get any attention? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873638 Title: Titlebar buttons incorrectly placed when set to appear on the left Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Unexpected button location on settings. Check image as screenshot attachment. Gnome Tweaks -> move the Titlebar buttons from Right to Left. Buttons should be paced on the extreme left -> for gnome-control- center they are centrally placed. OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question how be how to reproduce? To switch button on the left side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+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 1908293] [NEW] "extract here" doesn't work
Public bug reported: In PCManFM-Qt, when I right click on archived files (zip) and choose "Extract here" to uncompress the file in the current folder, nothing happens, the file is not uncompressed at all. But if I use "Extract to", everything works like usual. When I use PCManFM-Qt as superuser (root), "Extract here" works fine. Description:Ubuntu 20.04.1 LTS Release:20.04 ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Affects: pcmanfm-qt (Ubuntu) Importance: Undecided Status: New ** Tags: lubuntu ** Also affects: pcmanfm-qt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1908293 Title: "extract here" doesn't work Status in file-roller package in Ubuntu: New Status in pcmanfm-qt package in Ubuntu: New Bug description: In PCManFM-Qt, when I right click on archived files (zip) and choose "Extract here" to uncompress the file in the current folder, nothing happens, the file is not uncompressed at all. But if I use "Extract to", everything works like usual. When I use PCManFM-Qt as superuser (root), "Extract here" works fine. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1908293/+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 1905623] Re: df: /run/user/1000/doc: Operation not permitted
This bug was fixed in the package coreutils - 8.32-4ubuntu2 --- coreutils (8.32-4ubuntu2) hirsute; urgency=medium * d/p/treat-devtmpfs-and-squashfs-as-dummy-filesystems.patch: - Extend default filesystem exlusion to fuse.portal (LP: #1905623) -- Julian Andres Klode Sat, 05 Dec 2020 21:55:44 +0100 ** Changed in: coreutils (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in coreutils package in Ubuntu: Fix Released Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+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 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus
This bug was fixed in the package ibus - 1.5.23-2 --- ibus (1.5.23-2) unstable; urgency=medium * Team upload * debian/patches/Warn-deprecated-IBus-XKB-engines-w-dialog.patch: - Show a warning dialog when a deprecated engine name from ibus < 1.5.23 is configured (LP: #1901789). * Bump Standards-Version to 4.5.1 -- Gunnar Hjalmarsson Mon, 14 Dec 2020 13:09:45 +0100 ** Changed in: ibus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1901789 Title: Release upgrade 20.04 -> 20.10 removed input method from ibus Status in ibus: New Status in ibus package in Ubuntu: Fix Released Bug description: What happened: === I'm using iBus as input "method" with - Japanese (Anthy) // primary - German set up. I upgraded from ubuntu 20.04 to 20.10. EXPECTED: No changes regarding input. ACTUAL: German input method was removed lsb_release -rd === Description: Ubuntu 20.10 Release: 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Oct 28 11:10:04 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1901789/+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 1797002] Re: Bluetooth audio skips while the settings dialog is open
Hello, Thank you for looking at this issue. If source code propagate downstream, then I think it would be a good idea to come up with a system that propagates bug reports upstream. If that effort is underway I will consider registering on arbitrary other bug trackers in the meantime as a stopgap solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: Bluetooth audio skips while the settings dialog is open Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1873638] Re: Titlebar buttons incorrectly placed when set to appear on the left
I can confirm it for Ubuntu 20.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873638 Title: Titlebar buttons incorrectly placed when set to appear on the left Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Unexpected button location on settings. Check image as screenshot attachment. Gnome Tweaks -> move the Titlebar buttons from Right to Left. Buttons should be paced on the extreme left -> for gnome-control- center they are centrally placed. OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question how be how to reproduce? To switch button on the left side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+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 1908284] Re: [snap] chromium headless crashes in revision 1424
I set up a new VM running Ubuntu 20.04 just to rule out any issue with my original system. On my original system, when the chromium snap was updated to 1424 headless chromium started crashing. On that same system, I reverted back to 1421 and things are working again. So, 1424 doesn't work on either my original system, or the new VPS I set up. 1421 works on my original system, but I can't roll back to 1421 on the new VM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1908284 Title: [snap] chromium headless crashes in revision 1424 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+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 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
I have the same bug ** Attachment added: "snap-store.png" https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+attachment/5443882/+files/snap-store.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+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 1908284] Re: [snap] chromium headless crashes in revision 1424
Just tested with revision 1424 in a clean and up-to-date focal amd64 VM, and headless chromium works, I can inspect the page being loaded using devtools in a separate chromium instance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1908284 Title: [snap] chromium headless crashes in revision 1424 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+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 1908284] Re: chromium headless crashes in snap 1424
So if I understand correctly, revision 1421 works on one system, and revision 1424 doesn't work on a different system. It would be useful to test either 1424 on the first system, or 1421 or the other system, to confirm the regression, and rule out a system-specific issue. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Summary changed: - chromium headless crashes in snap 1424 + [snap] chromium headless crashes in revision 1424 ** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1908284 Title: [snap] chromium headless crashes in revision 1424 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+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 1908284] Re: chromium headless crashes in snap 1424
So if I understand correctly, revision 1421 works on one system, and revision 1424 doesn't work on a different system. It would be useful to test either 1424 on the first system, or 1421 or the other system, to confirm the regression, and rule out a system-specific issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1908284 Title: [snap] chromium headless crashes in revision 1424 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+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 1908161] Re: Update to 3.38.2
** Also affects: gnome-shell-extensions (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell-extensions (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell-extensions (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extensions (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: gnome-shell (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: gnome-shell-extensions (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: gnome-shell (Ubuntu Groovy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extensions (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: gnome-shell-extensions (Ubuntu Groovy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell-extensions (Ubuntu Groovy) Status: New => In Progress -- 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/1908161 Title: Update to 3.38.2 Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell-extensions package in Ubuntu: Fix Released Status in gnome-shell source package in Groovy: Fix Committed Status in gnome-shell-extensions source package in Groovy: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Screenshots handling has changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908161/+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 1908284] [NEW] chromium headless crashes in snap 1424
Public bug reported: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1908284 Title: chromium headless crashes in snap 1424 Status in chromium-browser package in Ubuntu: New Bug description: I'm running Ubuntu 20.04 and it looks like the current stable version of the Chromium snap has an issue running headless: ``` tjcravey@chromium:~$ chromium --headless --remote-debugging-port=9222 https://chromium.org [0100/00.240635:ERROR:zygote_linux.cc(607)] Zygote could not fork: process_type gpu-process numfds 3 child_pid -1 [0100/00.240882:ERROR:zygote_linux.cc(639)] write: Broken pipe (32) Trace/breakpoint trap (core dumped) ``` ``` tjcravey@chromium:~$ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: today at 15:33 UTC channels: latest/stable:87.0.4280.88 2020-12-10 (1424) 124MB - latest/candidate: 87.0.4280.88 2020-12-10 (1424) 124MB - latest/beta: 88.0.4324.41 2020-12-15 (1441) 144MB - latest/edge: 89.0.4350.4 2020-12-11 (1434) 257MB - installed: 87.0.4280.88(1424) 124MB - ``` I was able to revert back to snap 1421 on a different system and that command works fine there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908284/+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 1886592] Re: Add support for VMware Horizon SSO to gnome-shell
Hello Matthew, or anyone else affected, Accepted gnome-shell into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.36.7-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1886592 Title: Add support for VMware Horizon SSO to gnome-shell Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Eoan: Won't Fix Status in gnome-shell source package in Focal: Fix Committed Status in gnome-shell source package in Groovy: Fix Released Bug description: [Impact] VMware Horizon is a VDI product that runs atop of VMware's normal virtualisation stack, and it supports SSO authentication for login. In the past, the VMware Horizon agent has been pretty buggy, and requires SSO patches to be present to function, otherwise it breaks and causes entire outages for anyone trying to use the VDI. To solve this, VMware had been custom compiling their own libgnome- shell.so libraries with their SSO patches, which are based on oVirt's SSO implementation. When you install VMware Horizon agent to the instance, it overwrites Ubuntu's libgnome-shell.so with their custom compiled one. VMware don't keep their custom compiled libgnome-shell.so library up to date, so bugs that have already been fixed still live on in their library. Also, when Ubuntu updates our gnome-shell packages, it overwrites the custom libgnome-shell.so library, which then causes the Horizon agent to break, and causes outages for anyone using the VDI, which have to be solved by manually copying the custom library back. This situation is untenable for VMware Horizon users, so I have asked VMware to upstream their SSO patches. After a long painful process, they have landed in gnome-shell master. This SRU will significantly improve the quality of life for VMware Horizon users, and will remove the need for VMware to distribute custom libraries. [Testcase] You need an instance that runs on VMware Horizon, and the Horizon agent needs to be installed and running. Ideally, SSO authentication should be enabled to test all features, but it is not necessary to partially test. Test packages are available in this ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf247978-test If you install the test package in a VMware Horizon VDI, the instance should come up cleanly after reboot and function properly, especially with SSO login. The instance should be able to function without custom libgnome- shell.so libraries provided by VMware. [Regression Potential] The code refactors the oVirt SSO implementation into a more generalised interface, which other virtualisation platforms can use. oVirt has been transitioned to this interface as part of the refactoring, which means that any if the new oVirt SSO implementation is broken, it could break users running in oVirt. VMware's patches also use the new generalised interface, which is much simpler than before, and it has been tested internally by VMware. There was a very long review process with upstream GNOME, which ironed out all of their concerns. I have been reviewing the code along the way, and I am confident that it will not cause any regressions. If a regression did occur, then it would break SSO functionality only. [Other Information] Upstream Issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1983 Upstream merge-request: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/915 Commits: commit 809f820cd4a4eebb120ab5dde3f1985d35bcb540 Author: yun341
[Desktop-packages] [Bug 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal
Hello Amr, or anyone else affected, Accepted gnome-shell into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.36.7-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903764 Title: [SRU] Update gnome-shell to 3.36.7 in Focal Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Focal: Fix Committed Bug description: [Impact] This is the current GNOME 3.36.x stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix potential stack overflow in libcroco [Michael; !1404] * Fix system action search regressions [Florian; #3169] * Fix week number alignment when using font-scaling [Joonas; !1415] * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, !1451, #2230, !1423] Contributors: Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, Bastien Nocera, Daniel van Vugt Translators: Marek Černocký [cs] 3.36.6 == * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071] * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420] Contributors: Sebastian Keller, Zephaniah E. Loss-Cutler-Hull Translators: Goran Vidović [hr], Balázs Úr [hu] 3.36.5 == * Fix extension updates when many extensions are installed [Jeremias; !1363] * Fix missing icons in on-screen keyboard [Emre; #2631, #3007] * Fix delay when showing calendar events [Sebastian; #2992] * Fix app picker regressions on small displays [Sebastian; #2234, !1375, !1378] * Fix top bar navigation when NumLock is active [Olivier; #550] * Delay login animation until wallpaper has loaded [Michael; #734996] * Revert changes that caused mispositioning in overview in multi-monitor setups [Robert; #2971] * Reset auth prompt on login screen on VT switch before fade in [Ray; #2997] * Fix stuck grab when destroying open popup menu [Florian; #3022] * Misc. bug fixes and cleanups [Florian, Carlos, Andre, Jonas; !1357, !1371, !1381, #3037, #3005, !1386, !1390] Contributors: Michael Catanzaro, Jonas Dreßler, Olivier Fourdan, Carlos Garnacho, Sebastian Keller, Robert Mader, Andre Moreira Magalhaes, Florian Müllner, Jeremias Ortega, Ray Strode, Emre Uyguroglu Translators: Boyuan Yang [zh_CN], Rafael Fontenelle [pt_BR] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. The verification is going to include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [Regression potential] There have been fixes in various places: system actions search in different languages, alignment of week numbers in calendar menu, lock screen, scaling of app icons on Hi-dpi displays, extension updates, missing icons in OSK and showing calendar events in calendar menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 19:40:03 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-26 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-25
[Desktop-packages] [Bug 1896334] Re: SRU 3.36.6/3.36.7
Hello Marco, or anyone else affected, Accepted gnome-shell into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.36.7-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1896334 Title: SRU 3.36.6/3.36.7 Status in gnome-shell package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in yaru-theme source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6 Since the theme side of the project in ubuntu is shipped via Yaru theme, that project is included in the SRU. The changes involving yaru here are ONLY gnome-shell upstream changes applied to the Yaru sources, as per this we can consider them also part of the GNOME release. In fact: - Ubuntu's GNOME shell uses a Yaru theme based on upstream gnome-shell This theme basically takes the shell's data/ directory, applies some diffs and generates a gresource file out of it, that it's then loaded on startup (in place of the upstream one). - GNOME Shell applied some fixes to the theme (se its data/ directory diffs) - In order to get those fixes in Ubuntu main session we have to sync the upstream changes applied to such dir to yaru's src/gnome-shell path - You can easily compare the diffs applied there to match the ones happening in its upstream counterpart. The yaru-theme's `gnome-shell/upstream` directory is just for documentation and to allow three way merges when updating to new versions of gnome-shell, and it is not used for generating the final packages at all [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in popup-grab handling, gdm view fixes, lockscreen display changes in some hw, extensions updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+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 1908187] Re: Taking a screenshot during a game may lead to crash
Hello Marco, or anyone else affected, Accepted gnome-shell into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.36.7-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1908187 Title: Taking a screenshot during a game may lead to crash Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Focal: Fix Committed Bug description: [ Impact ] A screenshot of the Left 4 Dead 2 or Garry's Mod window causes the gnome-shell to terminate the user's session. [ Test case ] - Launch a game (Left 4 Dead 2 or Garry's Mod) - Open GNOME Screenshot app - Set "Window" in Capture Area menu and "Delay in Seconds" to 2-3 seconds - Alt-tab (or switch by Super key) to an open game - GNOME Screenshot app terminates the user session with an error "something went wrong". [ Regression potential ] No screenshot may be taken when requested To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908187/+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 1908161] Re: Update to 3.38.2
** Description changed: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working + Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions + https://launchpadlibrarian.net/511426552/gse + [ Regression potential ] Screenshots handling has changed -- 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/1908161 Title: Update to 3.38.2 Status in gnome-shell package in Ubuntu: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Screenshots handling has changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908161/+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 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
Looking at the Error Console was the right idea, thanks. Here's the error that is caught when clicking the "Confirm Security Exception" button: Exception { name: "NS_ERROR_FAILURE", message: "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.port]", result: 2147500037, filename: "chrome://pippki/content/exceptionDialog.js", lineNumber: 156, columnNumber: 0, data: null, stack: "getURI@chrome://pippki/content/exceptionDialog.js:156:7\naddException@chrome://pippki/content/exceptionDialog.js:386:13\n_fireButtonEvent@chrome://global/content/elements/dialog.js:487:19\n_doButtonCommand@chrome://global/content/elements/dialog.js:466:29\n_handleButtonCommand@chrome://global/content/elements/dialog.js:460:19\nInformUserOfCertError@chrome://messenger/content/mailWindow.js:685:10\nOnStopRunningUrl@chrome://messenger/content/mailWindowOverlay.js:2938:30\n", location: XPCWrappedNative_NoHelper } The previous -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+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 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal
gnome shell extensions to be tested with the SRU ** Attachment added: "gse" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903764/+attachment/5443879/+files/gse ** Attachment removed: "gse" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903764/+attachment/5443878/+files/gse ** Description changed: [Impact] This is the current GNOME 3.36.x stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix potential stack overflow in libcroco [Michael; !1404] * Fix system action search regressions [Florian; #3169] * Fix week number alignment when using font-scaling [Joonas; !1415] * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, !1451, #2230, !1423] Contributors: Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, Bastien Nocera, Daniel van Vugt Translators: Marek Černocký [cs] 3.36.6 == * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071] * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420] Contributors: Sebastian Keller, Zephaniah E. Loss-Cutler-Hull Translators: Goran Vidović [hr], Balázs Úr [hu] 3.36.5 == * Fix extension updates when many extensions are installed [Jeremias; !1363] * Fix missing icons in on-screen keyboard [Emre; #2631, #3007] * Fix delay when showing calendar events [Sebastian; #2992] * Fix app picker regressions on small displays [Sebastian; #2234, !1375, !1378] * Fix top bar navigation when NumLock is active [Olivier; #550] * Delay login animation until wallpaper has loaded [Michael; #734996] * Revert changes that caused mispositioning in overview in multi-monitor setups [Robert; #2971] * Reset auth prompt on login screen on VT switch before fade in [Ray; #2997] * Fix stuck grab when destroying open popup menu [Florian; #3022] * Misc. bug fixes and cleanups [Florian, Carlos, Andre, Jonas; !1357, !1371, !1381, #3037, #3005, !1386, !1390] Contributors: Michael Catanzaro, Jonas Dreßler, Olivier Fourdan, Carlos Garnacho, Sebastian Keller, Robert Mader, Andre Moreira Magalhaes, Florian Müllner, Jeremias Ortega, Ray Strode, Emre Uyguroglu Translators: Boyuan Yang [zh_CN], Rafael Fontenelle [pt_BR] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. The verification is going to include checking those extensions before and after the update to ensure the SRU isn't creating regressions - https://launchpadlibrarian.net/511426270/gse + https://launchpadlibrarian.net/511426552/gse [Regression potential] There have been fixes in various places: system actions search in different languages, alignment of week numbers in calendar menu, lock screen, scaling of app icons on Hi-dpi displays, extension updates, missing icons in OSK and showing calendar events in calendar menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 19:40:03 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-26 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903764 Title: [SRU] Update gnome-shell to 3.36.7 in Focal Status in gnome-shell package in Ubuntu: Triaged Bug description: [Impact] This is the current GNOME 3.36.x stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix potential stack overflow in libcroco [Michael; !1404] * Fix system action search regressions [Florian; #3169] * Fix week number alignment when using font-scaling [Joonas; !1415] * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, !1451, #2230, !1423] Contributors: Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, Bastien Nocera, Daniel van Vugt Translators: Marek Černocký [cs] 3.36.6 == * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071] * Fix app icon scaling regression on HiDPI displays [Sebasti
[Desktop-packages] [Bug 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal
Detail of the extensions to be tested ** Attachment added: "gse" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903764/+attachment/5443878/+files/gse ** Description changed: [Impact] This is the current GNOME 3.36.x stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix potential stack overflow in libcroco [Michael; !1404] * Fix system action search regressions [Florian; #3169] * Fix week number alignment when using font-scaling [Joonas; !1415] * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, !1451, #2230, !1423] Contributors: Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, Bastien Nocera, Daniel van Vugt Translators: Marek Černocký [cs] 3.36.6 == * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071] * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420] Contributors: Sebastian Keller, Zephaniah E. Loss-Cutler-Hull Translators: Goran Vidović [hr], Balázs Úr [hu] 3.36.5 == * Fix extension updates when many extensions are installed [Jeremias; !1363] * Fix missing icons in on-screen keyboard [Emre; #2631, #3007] * Fix delay when showing calendar events [Sebastian; #2992] * Fix app picker regressions on small displays [Sebastian; #2234, !1375, !1378] * Fix top bar navigation when NumLock is active [Olivier; #550] * Delay login animation until wallpaper has loaded [Michael; #734996] * Revert changes that caused mispositioning in overview in multi-monitor setups [Robert; #2971] * Reset auth prompt on login screen on VT switch before fade in [Ray; #2997] * Fix stuck grab when destroying open popup menu [Florian; #3022] * Misc. bug fixes and cleanups [Florian, Carlos, Andre, Jonas; !1357, !1371, !1381, #3037, #3005, !1386, !1390] Contributors: Michael Catanzaro, Jonas Dreßler, Olivier Fourdan, Carlos Garnacho, Sebastian Keller, Robert Mader, Andre Moreira Magalhaes, Florian Müllner, Jeremias Ortega, Ray Strode, Emre Uyguroglu Translators: Boyuan Yang [zh_CN], Rafael Fontenelle [pt_BR] - [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. + The verification is going to include checking those extensions before and after the update to ensure the SRU isn't creating regressions + https://launchpadlibrarian.net/511426270/gse [Regression potential] There have been fixes in various places: system actions search in different languages, alignment of week numbers in calendar menu, lock screen, scaling of app icons on Hi-dpi displays, extension updates, missing icons in OSK and showing calendar events in calendar menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 19:40:03 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-26 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: gnome-shell (Ubuntu) Importance: Medium => High -- 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/1903764 Title: [SRU] Update gnome-shell to 3.36.7 in Focal Status in gnome-shell package in Ubuntu: Triaged Bug description: [Impact] This is the current GNOME 3.36.x stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix potential stack overflow in libcroco [Michael; !1404] * Fix system action search regressions [Florian; #3169] * Fix week number alignment when using font-scaling [Joonas; !1415] * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, !1451, #2230, !1423] Contributors: Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, Bastien Nocera, Daniel van Vugt Translators: Marek Černocký [cs] 3.36.6 == * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071] * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420]
[Desktop-packages] [Bug 1908273] Re: Software stopped working
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1908273 Title: Software stopped working Status in xorg package in Ubuntu: New Bug description: After update to Ubuntu 20.04.1 LTS some of my software stopped working, all of it is visualization software: VMD, Discovery Studio, PyMOL, Gmolden, Avogadro. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 14:41:52 2020 DistUpgraded: 2020-11-21 20:16:19,197 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Wykonanie procesu potomnego „./xorg_fix_proprietary.py” (Nie ma takiego pliku ani katalogu) się nie powiodło (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8537] InstallationDate: Installed on 2020-05-20 (208 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-21 (23 days ago) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8537 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD0097RK4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G6 dmi.product.sku: 5PQ09EA#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1908273/+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 1908273] [NEW] Software stopped working
You have been subscribed to a public bug: After update to Ubuntu 20.04.1 LTS some of my software stopped working, all of it is visualization software: VMD, Discovery Studio, PyMOL, Gmolden, Avogadro. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 14:41:52 2020 DistUpgraded: 2020-11-21 20:16:19,197 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Wykonanie procesu potomnego „./xorg_fix_proprietary.py” (Nie ma takiego pliku ani katalogu) się nie powiodło (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8537] InstallationDate: Installed on 2020-05-20 (208 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 440 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-11-21 (23 days ago) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8537 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD0097RK4 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 440 G6 dmi.product.sku: 5PQ09EA#AKD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Software stopped working https://bugs.launchpad.net/bugs/1908273 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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