[Bug 1897454] Re: [snap] Chromium has Wayland support disabled
It feels pretty sluggish to use. Not sure if it's a packaging issue or chromium issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897454 Title: [snap] Chromium has Wayland support disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897454] Re: [snap] Chromium has Wayland support disabled
It works for me on 102.0.5005.40 (latest/beta channel) but with the following GPU error messages: ``` [2005781:2005781:0506/130903.210912:ERROR:gpu_init.cc(481)] Passthrough is not supported, GL is egl, ANGLE is WARNING: Kernel has no file descriptor comparison support: Operation not permitted [2005575:2005810:0506/130906.160463:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration. ``` And thousands of ``` [2008866:20:0506/131316.160676:ERROR:client_native_pixmap_dmabuf.cc(227)] Failed to mmap dmabuf: Permission denied (13) ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897454 Title: [snap] Chromium has Wayland support disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
I upgraded the following to 3.44.0-1ubuntu1 from jammy-proposed: evolution evolution-common evolution-plugin-bogofilter evolution-plugin- pstimport evolution-plugins libevolution I can also confirm I can compose messages and replies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
Ubuntu 22.04 Evolution 3.44.0-1 Sway 1.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969584] Re: Evolution does not allow editing email content on Wayland
Same issue. Screenshot attached is a reply to an email. Blank window happens with: * HTML * Plain text Workaround: switch to any of the Markdown options when composing a message. ** Attachment added: "2022-04-20T09:36:05,423753999+01:00.png" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+attachment/5581622/+files/2022-04-20T09%3A36%3A05%2C423753999+01%3A00.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969584 Title: Evolution does not allow editing email content on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1969584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
Added `gnome-control-center` to affected - GNOME online accounts requires a web browsing session to auth into some services. ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
`WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution` works around the issue for me on a Sway wayland session and running evolution in native wayland mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
** Attachment added: "eglinfo" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+attachment/5572891/+files/eglinfo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
I get the same from es2_info and eglinfo ** Attachment added: "es2_info" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+attachment/5572890/+files/es2_info -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
The tooltip comes from hovering with the mouse pointer over an (invisible) link on the email. Not sure why the pointer wasn't captured. ** Attachment added: "2022-03-25T10:58:57,801723903+00:00.png" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+attachment/5572867/+files/2022-03-25T10%3A58%3A57%2C801723903+00%3A00.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
** Attachment removed: "Screenshot of evolution showing no message contents" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+attachment/5572860/+files/2022-03-25T10%3A58%3A57%2C801723903+00%3A00.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] [NEW] [jammy regression] Evolution does not display message content anymore
Public bug reported: Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy third-party-packages wayland-session ** Attachment added: "Screenshot of evolution showing no message contents" https://bugs.launchpad.net/bugs/1966418/+attachment/5572860/+files/2022-03-25T10%3A58%3A57%2C801723903+00%3A00.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964025] Re: Do not support OpenSSL 3
This currently breaks Vagrant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964025 Title: Do not support OpenSSL 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-bcrypt-pbkdf/+bug/1964025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840560] Re: "error: can't find command hwmatch" during grub
I can confirm 2.04-1ubuntu26.15 from focal-proposed fixes it. Thank you Lukasz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840560 Title: "error: can't find command hwmatch" during grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1840560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965750] [NEW] [jammy regression] No sound from onboard audio (playback / record)
Public bug reported: After updates I applied last friday, my onboard audio has ceased to function. No audio comes out the laptop speakers and no audio goes in the internal microphone (built in audio). If I connect my bluetooth headset (Bose NC700) the audio works, but only ever in mono. I cannot switch to the A2DP sink, it stays on HPF mono. I tried switching from pulseaudio to pipewire and pipewire-pulse, and I kind of made it work - the bluetooth headset works correctly, and the onboard audio works again after switching default inputs and outputs a number of times. I just want to stress my laptop's audio has worked fine for years in all versions of ubuntu including Jammy, but only up until Friday Jan the 18th 2022. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Mon Mar 21 11:48:25 2022 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to jammy on 2022-03-01 (20 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965750 Title: [jammy regression] No sound from onboard audio (playback / record) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
I can confirm "20220314.gitcd01f857-0ubuntu2" from proposed fixes the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897454] Re: [snap] Chromium has Wayland support disabled
Forgot to add. Chromium is from the edge channel, at version 101.0.4919.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897454 Title: [snap] Chromium has Wayland support disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897454] Re: [snap] Chromium has Wayland support disabled
It still fails to start (sway 1.7): ~ chromium --enable-features=UseOzonePlatform --ozone-platform=wayland [278662:278662:0310/100635.924517:ERROR:wayland_connection.cc(209)] Failed to connect to Wayland display [278662:278662:0310/100635.924552:ERROR:ozone_platform_wayland.cc(226)] Failed to initialize Wayland platform [278662:278662:0310/100635.924557:ERROR:env.cc(225)] The platform failed to initialize. Exiting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897454 Title: [snap] Chromium has Wayland support disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63
Thank you, I was plagued by this issue on my Bose NC700 cans. In my case bluetoothd isn't crashing btw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962542 Title: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1962542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958022] Re: fish integration broken in focal
*** This bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 Issue also present in Impish. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958022 Title: fish integration broken in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1958022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I haven't got any pulseaudio updates on 21.04, to which version of ubuntu was the fix released to? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
That would be for 21.10 at this point yes? I wonder, how close/far is Ubuntu to swap PA for Pipewire? After next lts? I do believe this particular issue is not present on current Pipewire. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916309] Re: Cannot upgrade to 20.10 from 20.04
Turns out, when you select "normal" you must not use the -d flag. My mistake. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916309 Title: Cannot upgrade to 20.10 from 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1916309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916309] [NEW] Cannot upgrade to 20.10 from 20.04
Public bug reported: I'm trying to upgrade to 20.10 from 20.04 to no avail: ``` root@luis-XPS-15-9560 /h/luis# DEBUG_UPDATE_MANAGER=1 do-release-upgrade -d Checking for a new Ubuntu release MetaRelease.__init__() useDevel=True useProposed=False /etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release /etc/update-manager/meta-release: https://changelogs.ubuntu.com/meta-release-lts /etc/update-manager/meta-release: -development /etc/update-manager/meta-release: -proposed metarelease-uri: https://changelogs.ubuntu.com/meta-release-development MetaRelease.download() have self.metarelease_information MetaRelease.parse() current dist name: 'focal' found distro name: 'groovy' found distro name: 'hirsute' current dist not found in meta-release file Upgrades to the development release are only available from the latest supported release. ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal ``` /etc/update-manager/release-upgrades has: ``` [DEFAULT] Prompt=normal ``` /var/lib/update-manager/meta-release has entries for focal, groovy and hirsute: https://paste.ubuntu.com/p/dRkW8ZG5Df/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: sway Date: Fri Feb 19 23:45:03 2021 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2021-01-11T10:06:24.732377 mtime.conffile..etc.update-manager.release-upgrades: 2021-02-19T23:33:06.852046 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916309 Title: Cannot upgrade to 20.10 from 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1916309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916309] Re: Cannot upgrade to 20.10 from 20.04
Curiously the URL on the debug for the release upgrader does not have focal in it: https://changelogs.ubuntu.com/meta-release-development Dist: groovy Name: Groovy Gorilla Version: 20.10 Date: Thu, 22 October 2020 20:22:00 UTC Supported: 1 Description: This is the 20.10 release Release-File: http://archive.ubuntu.com/ubuntu/dists/groovy-updates/Release ReleaseNotes: http://archive.ubuntu.com/ubuntu/dists/groovy-updates/main/dist-upgrader-all/current/ReleaseAnnouncement ReleaseNotesHtml: http://archive.ubuntu.com/ubuntu/dists/groovy-updates/main/dist-upgrader-all/current/ReleaseAnnouncement.html UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/groovy-updates/main/dist-upgrader-all/current/groovy.tar.gz UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/groovy-updates/main/dist-upgrader-all/current/groovy.tar.gz.gpg Dist: hirsute Name: Hirsute Hippo Version: 21.04 Date: Thu, 22 April 2021 21:04:00 UTC Supported: 1 Description: This is the 21.04 release Release-File: http://archive.ubuntu.com/ubuntu/dists/hirsute/Release ReleaseNotes: http://archive.ubuntu.com/ubuntu/dists/hirsute/main/dist-upgrader-all/current/DevelReleaseAnnouncement ReleaseNotesHtml: http://archive.ubuntu.com/ubuntu/dists/hirsute/main/dist-upgrader-all/current/DevelReleaseAnnouncement.html UpgradeTool: http://archive.ubuntu.com/ubuntu/dists/hirsute/main/dist-upgrader-all/current/hirsute.tar.gz UpgradeToolSignature: http://archive.ubuntu.com/ubuntu/dists/hirsute/main/dist-upgrader-all/current/hirsute.tar.gz.gpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916309 Title: Cannot upgrade to 20.10 from 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1916309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
Fix will come with network-manager-gnome 1.20.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
I managed to get Campbell's patch to hide unmanaged devices upstreamed: https://gitlab.gnome.org/GNOME/network-manager- applet/-/merge_requests/93 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899233] Re: post login - no apps launched - virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1: virtualbox kernel module failed to build
I have tested the updated in proposed and it works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899233 Title: post login - no apps launched - virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1: virtualbox kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1899233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910559] Re: GDM3: Black screen with blinking cursor
Roger that, thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910559] Re: GDM3: Black screen with blinking cursor
The error you posted got me thinking and I did a reinstall of libnma0 and gir1.2-nm-1.0 and now the problem went away. Somehow, something on these got foobared. I never had any networkmanager issues though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910559] Re: GDM3: Black screen with blinking cursor
Thank you Daniel. None of the 3 ways to get ahold of a crash report worked unfortunately. There's nothing on /var/crash even after applying the workaround (Adding 'Crash' to the problem_types list on crashdb) and https://errors.ubuntu.com/user/5955c0a85343a54d5d779518dadcd4e278745d94628b423987bea5979d44b1d2b9ed23756ac91f32035088000d8d2ae868a6c9b99b7aff70d4febf3d6df571d2 as you can see is empty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910559] Re: GDM3: Black screen with blinking cursor
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559/+attachment/5450607/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910559] Re: GDM3: Black screen with blinking cursor
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559/+attachment/5450606/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910559] Re: GDM3: Black screen with blinking cursor
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559/+attachment/5450605/+files/prevjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908717] Re: Black screen with blinking cursor
Thank you Daniel. I needed oibaf's updates to get ahold of Mesa <=20.2 and libgnvd <=1.3.2 in order to successfully compile wlroots and sway from sources. Now that hwe has come out with the updates I needed I ppa-purged oibaf, but the issue remains. I have re-opened this on https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908717 Title: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910559] Re: GDM3: Black screen with blinking cursor
I have temporarily switched to lightdm, which works fine. Recording of the issue: https://www.youtube.com/watch?v=6VaizT4uC8w=youtu.be -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910559] [NEW] GDM3: Black screen with blinking cursor
Public bug reported: About a month ago, GDM ceased to work. I opened another issue here https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717 but due to me using oibaf's ppa it was considered prudent to discard that issue and re-open after I removed the ppa and restored Ubuntu's dist packages. Upon boot, gdm goes to a black screen with a cursor. This screen flickers to show the underlying tty and on each flicker the cursor position resets to the bottom right. It will do this a number of times until GDM dies and I'm left on a tty. I can start my window manager (sway) without issue from the console still and everything functions normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: sway Date: Thu Jan 7 15:55:43 2021 SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1910559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908717] Re: Black screen with blinking cursor
If I leave GDM3 like that for a while (around 30 secs or so) it will eventually terminate and drop to the underlying tty. Conversely, lightdm is working correctly. I can use that for the time being. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908717 Title: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908717] Re: Black screen with blinking cursor
Just to point out I have power-cycled my laptop in case a reboot wasn't cutting it. Also, I can switch TTY no problem, that's how I'm starting the window manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908717 Title: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908717] [NEW] Black screen with blinking cursor
Public bug reported: For some reason, since today GDM has ceased to work. No updates came through as last time I installed any updates was a week ago. Upon boot, gdm goes to a black screen with a cursor. This screen flickers to show the underlying tty and on each flicker the cursor position resets. I can start my window manager (sway) without issue from the console still and everything functions normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: sway Date: Fri Dec 18 13:44:09 2020 SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908717 Title: Black screen with blinking cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802533] Re: [MIR] pipewire
Thank you Liz. There are no installable packages on your PPA though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802533 Title: [MIR] pipewire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1802533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel]
I realised what an idiotic question that was as I submitted the form. Please disregard -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel]
Excellent stuff that is. Just to clarify, will this come in the default 5.4.0 kernel for Ubuntu 20.04.1 or the hwe kernel as the link to the fix suggests? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads
I had to do a clean-reinstall of 20.04 as there were other issues (my brother scan not working among others) that were deal breakers to me. I noticed the 5.8.0 kernel is available for install via the metapackage linux-generic-hwe-20.04-edge (installs linux-image-5.8.0-25-generic and related packages) To cut a long story short, the error occurs in focal with the groovy kernel as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads
So it looks like focal will inherit this problem when HWE starts rolling out. ** Summary changed: - Cannot boot with thunderbolt dock connected before kernel loads + Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901578] Re: Cannot remove snap package ubuntu 20.10
After adding a second user... ~ sudo snap remove slack error: cannot perform the following tasks: - Save data of snap "slack" in automatic snapshot set #5 (user: lookup userid 1002: no such file or directory) I did have a third user for testing out other things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901578 Title: Cannot remove snap package ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session
Problem remains in 20.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: Links triggered within most snap apps open in a separate browser session To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1835024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901578] Re: Cannot remove snap package ubuntu 20.10
After adding some random third user, snap removal works again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901578 Title: Cannot remove snap package ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901578] Re: Cannot remove snap package ubuntu 20.10
I'm seeing the same problem after a clean install of 20.10 over a pre- existing home folder. ~ sudo snap remove slack error: cannot perform the following tasks: - Save data of snap "slack" in automatic snapshot set #4 (user: lookup userid 1001: no such file or directory) ~ id 1001 id: ‘1001’: no such user: No such file or directory There used to be a user 1001 in my system before I reinstalled (just not mine, some other I use to try out other desktop environments). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901578 Title: Cannot remove snap package ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads
After going through a lot of kernels from the mainline PPA I've concluded the same, issue happens with kernel 5.7+. To complicate matters, if there's any output at all on the screen before the dell logo screen with the LUKS password entry is supposed to come back, it will work regardless of the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901215] [NEW] Cannot boot with thunderbolt dock connected before kernel loads
Public bug reported: Dell XPS 9650 with a TB16 thunderbolt dock. 2 external displays through the dock (HDMI and VGA). My system uses graphical boot via plymouth. Dell logo remains on screen while ubuntu loads into gdm3 (when it is booting normally). I'm using LUKS. This is a regression from focal and kernel 5.4. If I boot the laptop with the thunderbolt dock connected, the system will get past the Dell logo, go to a black screen and remain there. The screen is powered up as I can see some light on the edges. It won't boot up or respond to any keys. After force-shutdown via power key long press, on the next boot the grub menu will appear. The system will boot normally then (with the dock still connected). If I boot the system with the dock disconnected, it will correctly go into disk encryption password prompt. If at that point I connect the dock and wait without entering the password, the system will correctly set up the dock: the displays lit up and the mouse and keyboard plugged into it become active. The system boots normally. I'm trying to bisect in which kernel version this happened. I'll put results in a comment. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.25.30 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: luis 3332 F pulseaudio /dev/snd/controlC0: luis 3332 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 23 16:27:30 2020 InstallationDate: Installed on 2019-08-17 (432 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=/dev/mapper/vglinux-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-09 (13 days ago) dmi.bios.date: 11/17/2019 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:br1.18:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879580] Re: Screencast interface missing
I can confirm this is a problem in 20.10 as well. Pipewire 0.3 is available but apps (eg Chromium via snap and Chrome via deb) cannot acquire outputs to share with the error Claudio pasted above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
There's an update to grub coming, so anybody who's modified the grub scripts are going to hit the issue again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877727] Re: Nvidia dGPU active despite prime-select set to Intel card
More info: * ubuntu-driver install did not install nvidia-dkms-440 (had to be installed by hand) * Upon boot, /sys/bus/pci/devices/:01:00.0/power/control is set to `auto`, but the GPU is powered on. Setting it to `on` then to `auto` again powers down the GPU. * This temporary fix above survives suspend/resume -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877727] Re: Nvidia dGPU active despite prime-select set to Intel card
I'm on a Dell XPS 9560, i7-7700HQ, GP107M (GTX 1050 mobile). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877727] Re: Nvidia dGPU active despite prime-select set to Intel card
The path to this issue for me is different. I installed this laptop originally with 19.04 and nvidia-435 (possibly post installation?) and all was well upon upgrade to 19.10 and later on to 20.04. Upgrading to 20.04 kept the nvidia-435 driver and this bug did not manifest. Today I upgraded the driver to nvidia-440 via `ubuntu-driver install` and the issue started happening - the gpu is still powered up even though I rebooted into intel. I switched back and forth using `prime- select`. I tried reverting back to nvidia-435 to no avail. I can apply the "fix" via powertop (it does `echo 'auto' > '/sys/bus/pci/devices/:01:00.0/power/control';`) and I can confirm this shuts down the GPU properly and cuts power usage dramatically, until next boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
A workaround, if you really need auto-login, is to install lightdm (at this point still choose gdm3), enable auto-login via gnome settings, then switch to lightdm (sudo dpkg-reconfigure gdm3). Not sure why it autologins but it does. Can't lock the gnome session however as not using gdm anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: [SRU] vagrant spits out ruby deprecation warnings on every call
Same as Lothar here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: [SRU] vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887362] Re: CPU can't reach full speed after resuming from sleep
Dmesg above has such a faulty resume. Laptop went to sleep `Jul 12 19:56:05` and awoke to a faulty cpu state at `Jul 13 09:17:14` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887362 Title: CPU can't reach full speed after resuming from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887362] [NEW] CPU can't reach full speed after resuming from sleep
Public bug reported: This happens very sporadically after upgrading to 20.04 (not an issue before focal). Sometimes, after resuming from sleep, the CPU won't go over 1.23GHz. It will scale up and down between this and the min speed (800MHz) but go no higher. Putting the laptop to sleep and resuming brings it back to normal. I can't find a reliable way of reproducing it as it seems to happen at random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.40.43 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luis 1013521 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: sway Date: Mon Jul 13 09:27:33 2020 InstallationDate: Installed on 2019-08-17 (330 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a0 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vglinux-root 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: Upgraded to focal on 2020-03-31 (103 days ago) dmi.bios.date: 05/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.2 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887362 Title: CPU can't reach full speed after resuming from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871637] Re: [flicker free boot] boot image disappears for a second before LUKS prompt
*** This bug is a duplicate of bug 1836858 *** https://bugs.launchpad.net/bugs/1836858 Thank you Daniel, I'll follow the other bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871637 Title: [flicker free boot] boot image disappears for a second before LUKS prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: [SRU] vagrant spits out ruby deprecation warnings on every call
You can manually download it from here https://launchpad.net/~lucaskanashiro/+archive/ubuntu/focal-vagrant- sru/+packages if you don't want to add the PPA nor wait for proper release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: [SRU] vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730460] Re: Very poor multi-monitor performance in Wayland sessions
:O -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730460 Title: Very poor multi-monitor performance in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1730460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: [SRU] vagrant spits out ruby deprecation warnings on every call
I can confirm I see none of the warnings I mentioned earlier with 2.2.6 +dfsg-2ubuntu3~ppa1 or any new ones either. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: [SRU] vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard
You can manually select the output to use from gnome-settings until the fix lands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876065 Title: After unplug headphones and plug them again no sound can be heard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840560] Re: "error: can't find command hwmatch" during grub
Any reason the (failed) call to hwmatch is important? Ubuntu has worked fine for quite some time now without it, so perhaps it can be removed altogether from grub? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840560 Title: "error: can't find command hwmatch" during grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1840560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: [SRU] vagrant spits out ruby deprecation warnings on every call
Thank you for the work. Patches seem not quite complete as you mentioned: ## ~ vagrant provision ==> default: Running provisioner: shell... default: Running: inline script /usr/share/rubygems-integration/all/gems/vagrant-2.2.6/plugins/provisioners/shell/provisioner.rb:56: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call (eval):1: warning: The called method `detail' is defined here [...] ## ~ vagrant up (or reload) Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'ubuntu/bionic64' version '20200317.0.0' is up to date... [...] ==> default: Forwarding ports... /usr/share/rubygems-integration/all/gems/vagrant-2.2.6/plugins/providers/virtualbox/action/forward_ports.rb:50: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call /usr/share/rubygems-integration/all/gems/i18n-1.8.2/lib/i18n.rb:195: warning: The called method `t' is defined here ## -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: [SRU] vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: [SRU] vagrant spits out ruby deprecation warnings on every call
Looks like it's been added to the deb repo within the last hour or so, I did another apt update and got another 3 packages to upgrade including vagrant. Will report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: [SRU] vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: [SRU] vagrant spits out ruby deprecation warnings on every call
This one is different. Do a vagrant up from destroy, then ctrl+c straight away ~ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'ubuntu/focal64'... ^C==> default: Waiting for cleanup before exiting... /usr/share/rubygems-integration/all/gems/vagrant-2.2.6/bin/vagrant:200: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: [SRU] vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871685] Re: [SRU] vagrant spits out ruby deprecation warnings on every call
I might be doing something wrong, but focal-proposed isn't bringing in 2.2.6+dfsg-2ubuntu2 and the launchpad link above only contains the package sources and ubuntu build files. Am I too soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871685 Title: [SRU] vagrant spits out ruby deprecation warnings on every call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871637] Re: [flicker free boot] boot image disappears for a second before LUKS prompt
Uploaded the plymouth log and corresponding dmesg above. There's been a change to the boot process after adding `plymouth:debug`. Now, it briefly (less than 200ms I reckon) shows the boot log before going back to the dell / ubuntu / crypto password prompt stage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871637 Title: [flicker free boot] boot image disappears for a second before LUKS prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871637] Re: [flicker free boot] boot image disappears for a second before LUKS prompt
dmesg with `quiet splash drm.debug=0x4 log_buf_len=10M plymouth:debug` boot ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+attachment/5350319/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871637 Title: [flicker free boot] boot image disappears for a second before LUKS prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871637] Re: [flicker free boot] boot image disappears for a second before LUKS prompt
plymouth debug log with `quiet splash drm.debug=0x4 log_buf_len=10M plymouth:debug` boot ** Attachment added: "plymouth-debug.log" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+attachment/5350318/+files/plymouth-debug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871637 Title: [flicker free boot] boot image disappears for a second before LUKS prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871637] Re: [flicker free boot] boot image disappears for a second before LUKS prompt
Attached dmesg with drm.debug=0x4 log_buf_len=10M boot options ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+attachment/5350130/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871637 Title: [flicker free boot] boot image disappears for a second before LUKS prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871637] [NEW] [flicker free boot] boot image disappears for a second before LUKS prompt
Public bug reported: The display goes black at some point after BIOS boot and LUKS prompt, where original boot image is restored alongside Ubuntu's boot bits. Best shown in a video: https://www.youtube.com/watch?v=YUtlE6YkFuk Dell XPS 9560 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: Unity Date: Wed Apr 8 14:17:01 2020 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 15 9560 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vglinux-root ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vglinux-root ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: Upgraded to focal on 2020-03-31 (7 days ago) dmi.bios.date: 11/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871637 Title: [flicker free boot] boot image disappears for a second before LUKS prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871637] Re: [flicker free boot] boot image disappears for a second before LUKS prompt
journalctl -b 0 ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+attachment/5349632/+files/journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871637 Title: [flicker free boot] boot image disappears for a second before LUKS prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840560] [NEW] "error: can't find command hwmatch" during grub
Public bug reported:
Upon disabling my grub menu using grub-customizer, I've noticed that
just before the system boots and goes into the crypto password prompt
the following error message appears on the display:
```
error: can't find command hwmatch
```
Looks like this command is referenced from /boot/grub/grub/cfg
```
if hwmatch ${prefix}/gfxblacklist.txt 3; then
```
However, the mod doesn't exist on grub's mod folder:
```
~ ls -la /boot/grub/x86_64-efi/*.mod|wc -l
269
~ ls -la /boot/grub/x86_64-efi/hw*
fish: No matches for wildcard “/boot/grub/x86_64-efi/hw*”
```
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 18 00:22:41 2019
InstallationDate: Installed on 2019-08-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug disco wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840560
Title:
"error: can't find command hwmatch" during grub
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1840560/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825187] [NEW] Terminator does not register some keyboard shortcuts
Public bug reported: The version of terminator bundled with Disco seems unable to respond to certain shortcuts. I have mapped ctrl+shift+arrowleft and ctrl+shift+arrowdown to split terminal vertically and horizontally, respectively. The keybindings section of terminator correctly registers setting the shortcut, but the terminals don't split. The default shortcuts however work, if restored. Terminator offer a nightly build in a PPA for cosmic than when installed manually in Disco fixes the problem and now terminator works normally. This package has two extra requirements: gir1.2-gconf-2.0 and python- gobject. Installing these then using the disco version doesn't work either. Their PPA is at https://launchpad.net/~gnome-terminator/+archive/ubuntu /nightly-gtk3, and the version is for cosmic. The version number is the same (1.91-1 in disco and 1.91.0 in their ppa). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: terminator 1.91-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 17 14:44:44 2019 PackageArchitecture: all SourcePackage: terminator UpgradeStatus: Upgraded to disco on 2019-04-17 (0 days ago) ** Affects: terminator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825187 Title: Terminator does not register some keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1825187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
Indeed disabling sysrq seems to fix the problem, but this has worked for donkey's ages so what exactly changed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776113] Re: Laptop does not suspend when lid is closed
All gnome sessions above are on X btw, not Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776113 Title: Laptop does not suspend when lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1776113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776113] Re: Laptop does not suspend when lid is closed
Commenting out the line HandleLidSwitch=suspend restores normal behaviour. Since I didn't change it to begin with, I gather an update did this judging by how its last modified date was the same day suspend-on-lidclose stopped working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776113 Title: Laptop does not suspend when lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1776113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776113] Re: Laptop does not suspend when lid is closed
I've been experiencing the same problem since friday on a Dell XPS 9560 laptop on Bionic. I created a different user account to test and laptop doesn't suspend, but if I switch that user to a Mate Desktop session it works fine. These are the relevant lines on my logind.conf file: ~ cat /etc/systemd/logind.conf |grep -i lid HandleLidSwitch=ignore #HandleLidSwitchDocked=ignore #LidSwitchIgnoreInhibited=yes Curiously, I can see this config file was changed last (presumably due to an update?) just last friday june the 8th, which is perhaps too much of a coincidence: /etc/systemd ~ ll total 36K -rw-r--r-- 1 root root 1.1K Apr 2 20:25 journald.conf -rw-r--r-- 1 root root 1017 Jun 8 13:33 logind.conf drwxr-xr-x 2 root root 4.0K Oct 4 2017 network -rw-r--r-- 1 root root 601 Apr 12 12:12 resolved.conf drwxr-xr-x 21 root root 4.0K Jun 11 08:18 system -rw-r--r-- 1 root root 1.7K Apr 2 20:25 system.conf -rw-r--r-- 1 root root 604 Apr 2 20:25 timesyncd.conf drwxr-xr-x 3 root root 4.0K May 10 15:52 user -rw-r--r-- 1 root root 1.2K Jul 12 2017 user.conf This happens on: * Ubuntu gnome session * Vanilla gnome session * Unity 7 session Suspend on lid closed works correctly on * Mate session I do not mix DE's on the same user, always create a new one to use with it to avoid home folder pollution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776113 Title: Laptop does not suspend when lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1776113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763350] Re: Evolution 3.28.1-1 doesn't do replies or forwards correctly
Either you'll get notified by update-notifier and see what updates are coming in there, or you update via apt and will be listed there too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763350 Title: Evolution 3.28.1-1 doesn't do replies or forwards correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1763350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763419] [NEW] [Regression] Reply / forward neither quoting nor inlining original email
Public bug reported: After today's (2018-04-12) update of Evolution, whenever I reply or forward an email, the original email is neither quoted nor inlined as per Composer Preferences. The version of evolution available in bionic until yesterday (2018-04-11) didn't have this problem. I'm using evolution via gnome online accounts on google mail accounts. Happens on email received on all accounts. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 12 16:24:00 2018 InstallationDate: Installed on 2017-11-30 (132 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-04-09 (2 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Summary changed: - Reply / forward not quoting or inlining or attaching original email + [Regression] Reply / forward not quoting or inlining or attaching original email ** Description changed: After today's (2018-04-12) update of Evolution, whenever I reply or forward an email, the original email is neither quote nor inlined as per - preferences. + Composer Preferences. The version of evolution available in bionic until yesterday (2018-04-11) didn't have this problem. I'm using evolution via gnome online accounts on google mail accounts. Happens on email received on all accounts. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 12 16:24:00 2018 InstallationDate: Installed on 2017-11-30 (132 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-04-09 (2 days ago) ** Summary changed: - [Regression] Reply / forward not quoting or inlining or attaching original email + [Regression] Reply / forward neither quoting nor inlining original email ** Description changed: After today's (2018-04-12) update of Evolution, whenever I reply or - forward an email, the original email is neither quote nor inlined as per - Composer Preferences. + forward an email, the original email is neither quoted nor inlined as + per Composer Preferences. The version of evolution available in bionic until yesterday (2018-04-11) didn't have this problem. I'm using evolution via gnome online accounts on google mail accounts. Happens on email received on all accounts. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Apr 12 16:24:00 2018 InstallationDate: Installed on 2017-11-30 (132 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-04-09 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763419 Title: [Regression] Reply / forward neither quoting nor inlining original email To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1763419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754394] Re: Very dark chromium interface and pages when hardware acceleration is enabled
Well, I'll be absolutely damned. I created a new user and initially started in gnome wayland. This issue wasn't present on xwayland. I then reset the user, and logged into gnome xorg. No problem in there either. I reset the user and logged into Unity 7. Problem wasn't there. Initially. To cut a long story short, this happens on Unity 7 when the launcher has been configured to show on a monitor that's not the primary (eg built in desktop display). Steps to reproduce: * Connect a second screen * Log into unity * Configure a dark theme (not totally black) - arc-dark is very good as when the glitch happens you can really tell the difference * Open chromium - looks normal and themed. * Close chromium * Open the display tool, set the launcher placement on the secondary monitor * Open chromium - you'll see it looks way darker now This is at least on my setup. I can reproduce this as well on my main account. I'll try on a different laptop I have at home. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754394 Title: Very dark chromium interface and pages when hardware acceleration is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754394] Re: Very dark chromium interface and pages when hardware acceleration is enabled
Also I'm observing the same thing when opening photos (eg the screenshots above) with Gnome Image Viewer 3.26. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754394 Title: Very dark chromium interface and pages when hardware acceleration is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754394] Re: Very dark chromium interface and pages when hardware acceleration is enabled
** Attachment added: "chromium-no-hw-accel.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754394/+attachment/5073173/+files/chromium-no-hw-accel.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754394 Title: Very dark chromium interface and pages when hardware acceleration is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754394] [NEW] Very dark chromium interface and pages when hardware acceleration is enabled
Public bug reported: I switched back to FF when Quantum came out, this is why I hadn't realised this until today that I had to use hangouts in Chromium. For some reason, it's like gamma for the Chromium windows is dialled almost all the way down when hardware acceleration is enabled. Please see screenshots. The "chromium-no-hw-accel.png" screenshot shows the same colours as Firefox and Qupzilla. I've since tried on other browsers using chromium to the same effect: * Google Chrome 65.0.3325.146 * Opera 51.0.2830.55 * Chromium 64.0.3282.167-0ubuntu0.17.10.1 (as per bug report). This happens on intel HD630 graphics. I have a bumblebee/bbswitch set up but it seems unable to boot Chromium at all with HW on. I haven't been able however to see the same stuff on Electron apps though (VS Code and Slack). My setup: * XPS 9560 * Bumblebee / bbswitch set up * i7-7700HQ / Intel HD630 * Ubuntu 17.10 * Unity 7 * Kernel 4.13.0-36-generic ~ cat /usr/share/X11/xorg.conf.d/20-intel.conf Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" Option "DRI" "3" EndSection ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 64.0.3282.167-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAQrG2gVVZUMB8VAQMONR546rsEoVlVnigNUFSlSwBxT4GA0cABAQEBAQEBAQEBAjqAGHE4LUBYLEUAEyshAAAe/wBOUlBQNTE3VTBUVlUK/ABERUxMIFAyNDExSAog/QA4TB5TEQAKICAgICAgABQ= modes: 1920x1080 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBNEHYUADEaAQSlIxN4DmYap1Q0vCULS1cBAQEBAQEBAQEBAQEBAQEBTdAAoPBwPoAwIDUAWsIQAAAY/gBZMlhORIBMUTE1NkQxAAACQQMoABIAAAsBCiAgAAY= modes: 3840x2160 Date: Thu Mar 8 16:08:08 2018 Desktop-Session: 'unity' '/etc/xdg/xdg-unity:/etc/xdg/xdg-unity:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings' '/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share/:/usr/share/unity:/usr/share/unity:/home/luis/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2017-11-30 (97 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Load-Avg-1min: 0.34 Load-Processes-Running-Percent: 0.1% MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=979f134e-10a9-41ac-86cb-67c1e8295aaf ro quiet splash acpi_rev_override=5 pci=nommconf vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754394 Title: Very dark chromium interface and pages when hardware acceleration is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754394] Re: Very dark chromium interface and pages when hardware acceleration is enabled
** Attachment added: "chromium-yes-hw-accel.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754394/+attachment/5073172/+files/chromium-yes-hw-accel.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754394 Title: Very dark chromium interface and pages when hardware acceleration is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1754394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722708] Re: Crash when setting laptop display resolution
I have the same problem. I can set my laptop display to FHD down from 4K to match my external monitor, but as soon as I click on "scale 100%" button the apply button disappears and I get "Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitor scales must be identical" on the console. A workaround that works in the meantime is to use arandr, arrange your screens, and apply any changes - this will reset scale back to 1 and gnome display control panel works again. Arandr bottom snap can make both displays overlap, bear that in mind if you get the gnome panel repeated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722708 Title: Crash when setting laptop display resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733557] Re: Login screen showing Authentication Failed Switch to greeter...
I'm seeing this also upon 17.10 upgrade in unity / lightdm / unity greeter. It doesn't happen 100% of the time, typically takes some time time to manifest (I only ever suspend my laptop from monday to friday), but once it starts happening, it always happens until I shut down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failed Switch to greeter... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1733557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730460] Re: Framerate drops when moving windows across physical displays
Roger that Daniel. I can confirm it doesn't happen on X. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730460 Title: Framerate drops when moving windows across physical displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730460] Re: Framerate drops when moving windows across physical displays
This was happening on gnome-shell, not unity. The report says unity I gather because the crashes got so bad I had to switch back. I feel it might be tied up to the dynamic transparency stuff on either the top panel, or the dock. I opened another bug about the crashes here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1735127 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730460 Title: Framerate drops when moving windows across physical displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)
This workaround works for me, but years of muscle memory... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732612 Title: Alt+Printscreen not working (doesn't generate keypress event) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
Same issue on Dell XPS 15 9560: [0.004000] ACPI: Core revision 20170531 [0.004000] ACPI: Overriding _REV return value to 5 [0.038137] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170531/dswload-210) [0.038142] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170531/psobject-252) [0.038181] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp11) while loading table (20170531/tbxfload-228) [0.041005] ACPI Error: 1 table load failures, 12 successful (20170531/tbxfload-246) Linux luis-XPS-15-9560 4.13.0-21-generic #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584407 Title: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
I haven't noticed any adverse effects yet, but the laptop is relatively new and I'm not yet 100% familiar with its nooks and crannies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584407 Title: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355209] Re: The Evolution plugin for Mail Notification doesn't work/exist
Same here, the issue seems to be: ~ evolution (evolution:24146): module-plugin-lib-WARNING **: can't load plugin '/usr/lib/evolution/plugins/liborg-jylefort-mail-notification.so': /usr/lib/evolution/plugins/liborg-jylefort-mail-notification.so: undefined symbol: camel_message_info_uid (evolution:24146): module-plugin-lib-WARNING **: Cannot resolve symbol 'org_jylefort_mail_notification_folder_changed' in plugin '/usr/lib/evolution/plugins/liborg-jylefort-mail-notification.so' (not exported?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/355209 Title: The Evolution plugin for Mail Notification doesn't work/exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mail-notification/+bug/355209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
Thank you, would be great to have this backported into 17.10 as this is causing me occasional login issues with the set of extensions I have installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
