[Bug 1900055] [NEW] Window position is off when resolution set to 300 percent
Public bug reported: On my laptop with the resolution at 300 percent, software update shows just off center of the screen. If the window is maximized it will re- center, but then if you click install it will appear to freeze and will become unresponsive until the installation process has finished. Once it has finished installing, the window does not properly re-draw itself (see attachment--notice no borders around the dialog box). See attachment for example. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: update-manager 1:20.10.1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 16:04:41 2020 InstallationDate: Installed on 2020-07-04 (103 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session ** Attachment added: "UpdateBug.png" https://bugs.launchpad.net/bugs/1900055/+attachment/5422708/+files/UpdateBug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900055 Title: Window position is off when resolution set to 300 percent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1900055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875487] Re: VirtualBox & Gnome Boxes unload to load on 20.04 AMD
I wiped the machine and did a clean install, which seems to have resolved the issue. You can close this as I'm unable to replicate it. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875487 Title: VirtualBox & Gnome Boxes unload to load on 20.04 AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1875487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886224] Re: zsys error when installing or upgrading from apt
I wiped the drive and reinstalled, which fixed the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886224 Title: zsys error when installing or upgrading from apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1886224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886224] [NEW] zsys error when installing or upgrading from apt
Public bug reported: Any time I run apt, I get the following error: Errors were encountered while processing: zsys ZSys is adding automatic system snapshot to GRUB menu ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 13:00:13 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash --- InstallationDate: Installed on 2020-03-07 (117 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886224 Title: zsys error when installing or upgrading from apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1886224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884437] Re: Windows are resized and reordered upon resume from lock or suspend
It's still doing it with the same process ID. I switched DP cables-- perhaps it's a bad port on the board or display... I'll look into it further. Thanks for your assistance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884437 Title: Windows are resized and reordered upon resume from lock or suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1884437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884437] [NEW] Windows are resized and reordered upon resume from lock or suspend
Public bug reported: After a resume from a lock/suspend, windows sizes are changed, fonts are incorrect sizes (until mouse over), and windows have moved from the secondary monitor to the primary monitor. This happens every time the displays have been off (from a suspend or lock screen). AMD graphics with dual 4K displays. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 07:46:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: asus-wmi-sensors, b6c25d2, 5.4.0-21-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-33-generic, x86_64: installed asus-wmi-sensors, b6c25d2, 5.4.0-37-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1462:3680] InstallationDate: Installed on 2020-03-07 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_xbqp91@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_xbqp91 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884437 Title: Windows are resized and reordered upon resume from lock or suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1884437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen
This happens to me as well. I too have two monitors, and sometimes the menu is even on the wrong monitor. Oddly enough, if I click off then right-click again (right away), the menu appears correctly. It's almost as if it is triggered by not being invoked after x amount of time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780790 Title: Menus, tooltips and dropdowns are often misplaced on screen To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1780790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875487] Re: VirtualBox & Gnome Boxes unload to load on 20.04 AMD
VirtualBox
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up
correctly. Please reinstall virtualbox-dkms package and load the kernel
module by executing
'modprobe vboxdrv'
as root.
If your system has EFI Secure Boot enabled you may also need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can
load them. Please see your Linux system's documentation for more
information.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The
support driver is not installed. On linux, open returned ENOENT.
Failed to open a session for the virtual machine Windows10.
The virtual machine 'Windows10' has terminated unexpectedly during
startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875487
Title:
VirtualBox & Gnome Boxes unload to load on 20.04 AMD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1875487/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875487] Re: VirtualBox & Gnome Boxes unload to load on 20.04 AMD
Here's the log from Gnome Boxes:
Broker URL: qemu+unix:///session
Domain: win10
UUID: b2debae5-e519-4492-b60d-cb4b9edc9400
Persistent: yes
Cpu time: 0
Memory: 6341970 KiB
Max memory: 32861316 KiB
CPUs: 16
State: GVIR_DOMAIN_STATE_SHUTOFF
Domain config:
win10
b2debae5-e519-4492-b60d-cb4b9edc9400
Microsoft Windows 10
https://wiki.gnome.org/Apps/Boxes;>
installed
http://microsoft.com/win/10:9
http://libosinfo.org/xmlns/libvirt/domain/1.0;>
http://microsoft.com/win/10"/>
6341970
6341970
16
hvm
destroy
restart
destroy
/usr/bin/qemu-system-x86_64
QEMU log:
2020-03-22 16:50:09.270+: starting up libvirt version: 6.0.0, package:
0ubuntu5 (Christian Ehrhardt Tue, 10 Mar
2020 08:58:04 +0100), qemu version: 4.2.0Debian 1:4.2-3ubuntu3, kernel:
5.4.0-18-generic, hostname: Tower
LC_ALL=C \
/usr/bin/qemu-system-x86_64 \
-name guest=win10,debug-threads=on \
-S \
-machine pc-q35-4.2,accel=kvm,usb=off,dump-guest-core=off \
-cpu host \
-m 6194 \
-overcommit mem-lock=off \
-smp 16,sockets=1,cores=8,threads=2 \
-uuid b2debae5-e519-4492-b60d-cb4b9edc9400 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=28,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-reboot \
-global ICH9-LPC.disable_s3=1 \
-global ICH9-LPC.disable_s4=1 \
-boot menu=on,strict=on \
-device
pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2
\
-device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \
-device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \
-device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
-device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x1d.0x7 \
-device
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x1d
\
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x1d.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x1d.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \
-device usb-ccid,id=ccid0,bus=usb.0,port=1 \
-blockdev
'{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"qcow2","file":"libvirt-3-storage","backing":null}'
\
-device
virtio-blk-pci,scsi=off,bus=pci.3,addr=0x0,drive=libvirt-3-format,id=virtio-disk0,bootindex=2,write-cache=on
\
-blockdev
'{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}'
\
-device ide-cd,bus=ide.2,drive=libvirt-2-format,id=sata0-0-2,bootindex=1 \
-blockdev
'{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}'
\
-device ide-cd,bus=ide.3,drive=libvirt-1-format,id=sata0-0-3 \
-netdev user,id=hostnet0 \
-device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:01:7e:68,bus=pci.1,addr=0x0
\
-chardev spicevmc,id=charsmartcard0,name=smartcard \
-device ccid-card-passthru,chardev=charsmartcard0,id=smartcard0,bus=ccid0.0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev spicevmc,id=charchannel0,name=vdagent \
-device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
\
-chardev spiceport,id=charchannel1,name=org.spice-space.webdav.0 \
-device
virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.spice-space.webdav.0
\
-device usb-tablet,id=input0,bus=usb.0,port=2 \
-spice port=0,disable-ticketing,image-compression=off,seamless-migration=on \
-device
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1
\
-device ich9-intel-hda,id=sound0,bus=pcie.0,addr=0x1b \
-device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 \
-chardev
[Bug 1875487] [NEW] VirtualBox & Gnome Boxes unload to load on 20.04 AMD
Public bug reported: Since 20.04, I am unable to use virtualization on AMD. The kernel module fails to load. Virtualization is turned on in the bios, yet the computer is acting as if it were not. AMD Ryzen 7 3700x. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virtualbox-qt 6.1.6-dfsg-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 14:24:31 2020 ExecutablePath: /usr/lib/virtualbox/VirtualBox InstallationDate: Installed on 2020-03-07 (51 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - VirtualBox & Gnome Boxes unload to load on 20.04 AMD 20.04 + VirtualBox & Gnome Boxes unload to load on 20.04 AMD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875487 Title: VirtualBox & Gnome Boxes unload to load on 20.04 AMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1875487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868896] Re: Minimized windows reappear when closing the overview
Thanks for your quick response on this! So awesome! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868896 Title: Minimized windows reappear when closing the overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868896] Re: 20.04 items won't stay minimized with MS Teams Open
I thought it had something to do with Teams being open, but this doesn't appear to be the case. ** Description changed: I just ran all of the updates for 20.04 on two machines, and both machines experience the same issue. Items do not appear to stay "minimized". For instance, you can minimize Thunderbird, and it appears to re-maximize itself. However, you cannot click on anything in the maximized window, but you can re-minimize it (that button does work), then click the dock to bring it back out and it functions properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 18:11:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Dell Iris Plus Graphics G7 [1028:096d] + Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Dell Iris Plus Graphics G7 [1028:096d] InstallationDate: Installed on 2020-03-11 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311) MachineType: Dell Inc. XPS 13 9300 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/usr/bin/zsh + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vp1gr9@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vp1gr9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.6 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.6:bd01/17/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Summary changed: - 20.04 items won't stay minimized with MS Teams Open + 20.04 items won't stay minimized -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868896 Title: 20.04 items won't stay minimized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868896] Re: 20.04 items won't stay minimized
Oddly enough, it seems to only happen when Microsoft Teams is open. I just noticed that it wasn't happening, but the moment I open Teams, it started to happen again. Note: MS Teams is NOT the program that won't stay minimized--it is any program. ** Summary changed: - 20.04 items won't stay minimized + 20.04 items won't stay minimized with MS Teams Open -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868896 Title: 20.04 items won't stay minimized with MS Teams Open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868896] [NEW] 20.04 items won't stay minimized with MS Teams Open
Public bug reported: I just ran all of the updates for 20.04 on two machines, and both machines experience the same issue. Items do not appear to stay "minimized". For instance, you can minimize Thunderbird, and it appears to re-maximize itself. However, you cannot click on anything in the maximized window, but you can re-minimize it (that button does work), then click the dock to bring it back out and it functions properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 18:11:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G7 [1028:096d] InstallationDate: Installed on 2020-03-11 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311) MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vp1gr9@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vp1gr9 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.6 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.6:bd01/17/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible single-occurrence ubuntu 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/1868896 Title: 20.04 items won't stay minimized with MS Teams Open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1868896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic
Same here on a XPS 13 7390, 5.4.0-14-generic also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858844 Title: [Dell XPS 15 9575] Screen brightness stopped working with linux- image-5.4.0-9-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from
Mine does EVERYTHING EXACTLY as you just mentioned. Sent from my iPhone > On Jan 4, 2019, at 3:25 AM, Benjamin Schmid <1748...@bugs.launchpad.net> > wrote: > > @vanvugt Seeing this VERY regularly in cosmic, too. Just came back here > to re-check the status of this long-term annoying issue. > > The fact is, that gnome shell provides me a VERY poor UX experience: > > Logged out for the session more than 10mins? Type your password and go > get take a coffee, because it literally takes 1-2 minutes until the > session finally crashes and restarts. Before my PC it literally > unusable. Sometimes I also switch to the login screen and re-login into > my running session to somehow provoke the crash to get it usable. > > Ah – and by the way: On some occassions lockscreen does not work and > expose the clickable (!) left sidebar. In this case I only can unlock > via the login-screen way to crash the session. > > Also commonly in normal operation the left sidebar looks strangely > sized. Then I need to type "r" to restart the shell to resume normal > operation. > > Feels really like an old, nearly dying device … > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1755163). > https://bugs.launchpad.net/bugs/1748450 > > Title: > gnome-shell crashed with SIGTRAP in _g_log_abort() from > g_log_default_handler() from default_log_handler(message="Connection > to xwayland lost") from g_logv() from g_log() from > > Status in gnome-shell package in Ubuntu: > Invalid > Status in mutter package in Ubuntu: > Fix Released > Status in gnome-shell source package in Bionic: > Invalid > Status in mutter source package in Bionic: > Fix Released > > Bug description: > [Impact] > > * Xwayland is failing frequently (not crashing), which triggers a > crash in gnome-shell because gnome-shell doesn't know how to survive > after Xwayland has reset itself. > > * The frequent gnome-shell crashes create frequent problem reports and > annoying dialogs for users, after they log in to an apparently working > gnome-shell. > > * This affects Xorg sessions too, because the gdm login screen itself > is a Wayland session. And Xorg users will see the problem dialog after > they have logged into a Xorg session. > > * The fix simply converts the crash into a silent exit (as decided by > Gnome upstream). This avoids the mountain of crash reports and > annoying error dialogs at least. It does not fix the root causes that > remain in Xwayland, but this is considered acceptable because there > really isn't a bug in gnome-shell here other than it doesn't know how > to survive without a connection to Xwayland. > > * For users of Xorg sessions, like bionic default, this is a full fix > as Xorg users will never get an Xwayland instance after logging in. > And hence the Xwayland bugs are irrelevant. > > [Test Case] > > * Just install bionic, use it lightly and reboot a few times. > > * Observe crash files are left in /var/crash and problem report > dialogs after logging in. > > [Regression Potential] > > Medium. The fix does not really change the structure of the existing > error handling, only changes it from a core dump into a silent exit. > For Xorg users this should be invisible as the affected login screen > restarts automatically. > > [Other Info] > > This is a whole class of gnome-shell crash which includes bug 1505409, bug > 1748450 and bug 1556601. All three should be considered the same crash for > the sake of this SRU. Just don't mark them as duplicates of each other > because they are all still collecting duplicates of their own. > > - > > *** This is a duplicate of bug 1505409, but is being kept separate so > as to automatically collect duplicate reports since the stacktrace > signature has changed recently. Any resolution and discussion should > occur in bug 1505409. *** > > See also: > https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 > > ProblemType: Crash > DistroRelease: Ubuntu 18.04 > Package: gnome-shell 3.26.2-0ubuntu2 > ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 > Uname: Linux 4.13.0-33-generic x86_64 > ApportVersion: 2.20.8-0ubuntu8 > Architecture: amd64 > CurrentDesktop: GNOME-Greeter:GNOME > Date: Thu Feb 8 23:50:23 2018 > DisplayManager: gdm3 > ExecutablePath: /usr/bin/gnome-shell > GsettingsChanges: > > InstallationDate: Installed on 2016-03-21 (690 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) > ProcCmdline: /usr/bin/gnome-shell > ProcEnviron: > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/false > Signal: 5 > SourcePackage: gnome-shell > StacktraceTop: > () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 > _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 > _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 > XPending () at
Re: [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I didn’t need to remove GDM3, but installing LightDM (and switching to it) fixed it for me. Well, I should say it was a workaround, anyway... > On Oct 24, 2018, at 11:56 PM, ccdisle wrote: > > Uncommenting "WaylandEnable=false " worked. > > Removing gdm3 did not work, I just got redirected to a tty3 login shell. > > Thanks again > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1752053 > > Title: > nvidia-390 fails to boot graphical display > > Status in mesa package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-390 package in Ubuntu: > Fix Released > Status in xserver-xorg-video-nouveau package in Ubuntu: > Invalid > > Bug description: > I'm using Bionic with the new 4.15 kernel. I've been using the > nvidia-384 driver with no problem for a while. Today I issued "sudo > apt-get upgrade" and I was prompted to upgrade the nvidia driver to > the nvidia-390. After installing the driver and rebooting, I was only > able to boot in to the tty terminal. The graphical display failed to > boot. I have had similar problems with nvidia driver version 390 with > Arch Linux and with Open Suse Tumbleweed. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773113] Re: nvidia-390 does not show GUI
390 is completely useless for me 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/1773113 Title: nvidia-390 does not show GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
I upgraded from 17.10 to 18.04. It wouldn't log in, but through ssh I purged the nvidia drivers, installed 396 through the PPA, rebooted, and it came up and worked. It is a tower with GTX 1060. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
I hear Pop!_OS 18.04 doesn't have this issue. I'm unfortunately about to give up on Ubuntu and give that a try. Some word of reassurance from the Ubuntu team here would be nice. Where they marked this as fixed, I'm not hopeful of a fix--at least anytime soon. If anyone has found a true and simple workaround, please let us know! Otherwise, I think my hardware will require me to look somewhere else... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
At the top of this page it says "Fix Released". Does anyone know to to get them to change the status to an open bug and re-evaluate it? It's clearly not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
Hopeful this bug was fixed (as it improperly states above), I did a fresh install on my machine with an Nvidia 1060. It will boot, then go to a black screen on login, etc. I tried what people mentioned above, but was not able to get a stable working system. I went back to 17.10 and have not had any issues since. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
I had to wipe my system from an image I had made last week. I went through everything mentioned above--I was able to get video back, but as soon as I'd try logging in my UI would hang. I'd have to reboot from SSH. Everything is working now--I'm going to hold off running any upgrades for a few days though in hopes they fix the bug. Running GTX 1060. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
