[Bug 1878252] [NEW] Unable to boot to desktop with Matrox G200eR2 (Dell Poweredge R420)
Public bug reported: After successfully installing Ubuntu 20.04 using UEFI with ZFS on my Poweredge R420, it booted to a purple/black screen with a mouse cursor. The mouse was not responsive and I could not use the system. I was able to boot to the grub menu and use nomodeset on the boot options, which did allow the system to boot successfully. The system's gui hangs with "quiet splash", but does boot with "nomodeset". When on the black screen with a mouse cursor, I was able to ssh into the system, so it is booting and running--it is the GUI, mouse, and keyboard that are unresponsive. hardware is Dell Poweredge R420, 64GB ram, 2 x Xeon E5-2430L V2. Graphics is Matrox G200eR2 (which is the integrated video adapter). I get the exact same behavior described here: https://askubuntu.com/questions/1231887/20-04-lts-boot-hang-matrox-g200ew-after-successful-install The Xorg log file is attached. I also ran the commands "sudo service gdm3 stop" and "sudo service gdm3 start". The log from the start operation are also attached. ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Xorg.1.log" https://bugs.launchpad.net/bugs/1878252/+attachment/5370496/+files/Xorg.1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878252 Title: Unable to boot to desktop with Matrox G200eR2 (Dell Poweredge R420) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1878252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878252] Re: Unable to boot to desktop with Matrox G200eR2 (Dell Poweredge R420)
Syslog output from "sudo service gdm3 start" ** Attachment added: "startingGdm3.log" https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1878252/+attachment/5370497/+files/startingGdm3.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878252 Title: Unable to boot to desktop with Matrox G200eR2 (Dell Poweredge R420) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1878252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874524] Re: ZFS installation fails with; Failed to add #4 partition: Numerical result out of range
I can confirm that I get the same error, switched to UEFI, and the problem went away. See my bugreport here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875084 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874524 Title: ZFS installation fails with; Failed to add #4 partition: Numerical result out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1874524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875084] Re: zfs installation fails with : Failed to add #4 partition: Numerical result out of range
I switched to UEFI (from BIOS), and it fixed the issue. I am using 4TB HDD's and I was not aware that BIOS had a max limit of 2 TB HDD. It would be very nice if there was a descriptive error message in this case--it was not easy to find the root cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875084 Title: zfs installation fails with : Failed to add #4 partition: Numerical result out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874524] Re: ZFS installation fails with; Failed to add #4 partition: Numerical result out of range
It would be very nice if there was a descriptive error message in this case--it was not easy to find the root cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874524 Title: ZFS installation fails with; Failed to add #4 partition: Numerical result out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1874524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877708] Re: i want to update my software
*** This bug is a duplicate of bug 1611737 *** https://bugs.launchpad.net/bugs/1611737 To clarify: if you want to upgrade to to 18.04, I'm afraid you'll need to remove ROS Kinetic first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1877708 Title: i want to update my software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877708] Re: i want to update my software
*** This bug is a duplicate of bug 1611737 *** https://bugs.launchpad.net/bugs/1611737 The problem here is that you have ROS Kinetic installed, which only supports Ubuntu 16.04: it doesn't support the upgrade. We're working on a nicer error for exactly this situation. ** This bug has been marked a duplicate of bug 1611737 Can't upgrade from a release if ros packages are installed from ROS servers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1877708 Title: i want to update my software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877708/+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 1875084] Re: zfs installation fails with : Failed to add #4 partition: Numerical result out of range
** Description changed: I selected an install with ZFS to erase what's currently on the drives. Using a Dell Poweredge R420 with a H710 PERC and it crashed before installing anything. + + This issue reproduces 100% of the time that I take the above steps. It + is not intermittent, and I am not able to install on my machine with + ZFS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 16:01:08 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - LANGUAGE=en_US.UTF-8 - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - LC_NUMERIC=C.UTF-8 + LANGUAGE=en_US.UTF-8 + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875084 Title: zfs installation fails with : Failed to add #4 partition: Numerical result out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875084/+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 spicevmc,id=charredir0,name=usbr
[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 1875086] [NEW] Crashed on a clean install after selecting timezone
Public bug reported: Duplicate of 1875084, but I couldn't figure out a way to link these files to that bug. The crash happened when I attempted it again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 Date: Sat Apr 25 16:06:14 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875086 Title: Crashed on a clean install after selecting timezone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875084] [NEW] Crashed on a clean install after selecting timezone
Public bug reported: I selected an install with ZFS to erase what's currently on the drives. Using a Dell Poweredge R420 with a H710 PERC and it crashed before installing anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 16:01:08 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875084 Title: Crashed on a clean install after selecting timezone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611737] Re: Can't upgrade from a release if ros packages are installed from ROS servers
> This makes some upgrades technically not possible since there could not be packages in the ROS repositories available for the new distribution in an upgrade process. For example, there is no a single ROS Release that support 14.04 and 16.04. I can not see a safe/straightforward upgrade path. Jose hit this on the head. This is explicitly not supported by ROS. The problem is, Ubuntu doesn't really have a way of knowing that. I think the best solution to this issue is a nice error message from the upgrader. We can detect that ROS is installed, mention that an upgrade isn't supported, and suggest removing the ROS distro before proceeding. That said, I'm not familiar with the upgrader. Is there supported way we could hook such logic in? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611737 Title: Can't upgrade from a release if ros packages are installed from ROS servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611737/+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 1868024] [NEW] Auto-size doesn't render correctly
Public bug reported: When running the following: $ dialog --infobox "Hello" 0 0 The resulting dialog does not render correctly - the outside borders don't match with the text. This worked in Ubuntu 16.04. Please note that this is tested inside Docker, but I believe it should still work correctly. ** Affects: dialog (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/1868024 Title: Auto-size doesn't render correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1868024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835686] Re: pip3 list --outdated returns HTTP 404 error
>From https://github.com/pypa/pip/issues/6428 this is more the fault of pip >then ubuntu as the version of pip on Ubuntu 19.10 will throw this error when >running --outdated in any pip package is installed from a local file. This is fixed in later versions of pip https://github.com/pypa/pip/pull/6367 and might be back-ported but I would recommend: * Not worrying about system pip and only install pip packages on ubuntu via --user because the system is maintaining it's own pip packages and messing with them may break apt upgrade * Wait till upstream pip is updated on ubuntu * This is also avoided in pipenv virtualenvs: pipenv run pip list --outdated ** Bug watch added: github.com/pypa/pip/issues #6428 https://github.com/pypa/pip/issues/6428 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835686 Title: pip3 list --outdated returns HTTP 404 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1835686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
The easiest way I found to reproduce was to monkey patch the python paramiko library. I've attached a short script which can be used to test a host. It requires either python-paramiko or python3-paramiko to run. ** Attachment added: "test_bug_1863930.py" https://bugs.launchpad.net/ubuntu/bionic/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854413] Re: Backlight adjustments shows OSD but does not change anything on Samsung OLED panel
I haven't had a chance to try these out and I'm not sure how to track these changes through the various repositories and branches but for the record there are some other commits in drm/i915 that are claimed to fix the issue. I'll report back when I get a chance to patch these into 5.3.0-40-generic (which, as a side note, fixes the black screen after resuming from suspend issue on the P1 Gen 2). fde7266fb2f6 drm/i915: Fix eDP DPCD aux max backlight calculations 79946723092b drm/i915: Assume 100% brightness when not in DPCD control mode 662884a9ad99 drm/i915: Fix DPCD register order in intel_dp_aux_enable_backlight() 9ac7d53d70a2 drm/i915: Auto detect DPCD backlight support by default d2a4bb6f8bc8 drm/i915: Don't use VBT for detecting DPCD backlight controls --- https://gitlab.freedesktop.org/drm/intel/issues/510#note_387666 https://github.com/torvalds/linux/commit/fde7266fb2f6fff2a7fe861474bf198ef0f2449f https://github.com/torvalds/linux/commit/79946723092bde318ff11b3e57a02ba13a30b17e https://github.com/torvalds/linux/commit/662884a9ad992240b8169624aae1b0cc273edc30 https://github.com/torvalds/linux/commit/9ac7d53d70a2b4f43360e3aa0f14a2514339328f https://github.com/torvalds/linux/commit/d2a4bb6f8bc8cf2d788adf7e59b5b52fe3ac -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854413 Title: Backlight adjustments shows OSD but does not change anything on Samsung OLED panel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1854413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854177] Re: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2
Looks good in 5.3.0-40-generic. As always, thanks for the help here and in general. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854177 Title: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854177/+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
[Bug 1863930] [NEW] SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
Public bug reported: SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Patch added: "protocol_major_version_mismatch_regression.patch" https://bugs.launchpad.net/bugs/1863930/+attachment/5329542/+files/protocol_major_version_mismatch_regression.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
Given snap's many poor design choices, I was delighted to find that $ sudo apt autoremove --purge snapd had no disadvantages for me, and I recommend it highly to anyone who is able to avoid snap in their ecosystem. In addition to solving this home directory issue, it eliminates some of snap's other intentional clutter, such as bloating `df` and `cat /proc/partitions` with garbage. Regarding unnecessary comments, I'm glad to see people standing up for themselves. Since the devteam's choices don't respect us, I think we have every right to return the favor. It seems to me that after 4 years, continuing to annoy them is one of the few options available to those who can't avoid snap altogether. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+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.
This issue impacts the experience with Ubuntu significantly. Android, Windows, and OS X all sound much better with a Bluetooth headset when on calls, playing games, or listening to music while using the headset microphone. -- 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855615] Re: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS
Had a panic moment when it appeared my i1pro meter had stopped working. It seems I had not used it since upgrading to 18.04.LTS when I started having problems with this issue. As I plugged the unit in gnome-control- center opens at the device colour profile page. When I open a terminal and try to use chartread I get: Read Target Test Chart, Version 2.0.0 Author: Graeme W. Gill, licensed under the AGPL Version 3 usage: chartread [-options] outfile -v Verbose mode -c listno Set communication port from the following list (default 1) ** No ports found ** etc or with chartread -D I get: Read Target Test Chart, Version 2.0.0 Author: Graeme W. Gill, licensed under the AGPL Version 3 usage: chartread [-options] outfile -v Verbose mode -c listno Set communication port from the following list (default 1) Argyll 'V2.0.0' Build 'Linux 64 bit' System 'Linux #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 4.15.0-72-generic x86_64' usb_check_and_add: failed to open '/dev/bus/usb/004/025' ** No ports found ** As a last resort I uninstalled gnome-control-center with synaptic and the device (after unplug and plug in) is available again to chartread -D : Read Target Test Chart, Version 2.0.0 Author: Graeme W. Gill, licensed under the AGPL Version 3 usage: chartread [-options] outfile -v Verbose mode -c listno Set communication port from the following list (default 1) 1 = '/dev/bus/usb/004/008 (GretagMacbeth i1 Pro)' I re-installed and it's back to no-go. It's as though gnome-control-center is grabbing the device and not allowing access even when the window is closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855615 Title: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855615] Re: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS
Had a panic moment when it appeared my i1pro meter had stopped working. It seems I had not used it since upgrading to 18.04.LTS when I started having problems with this issue. As I plugged the unit in gnome-control- center opens at the device colour profile page. When I open a terminal and try to use chartread I get: Read Target Test Chart, Version 2.0.0 Author: Graeme W. Gill, licensed under the AGPL Version 3 usage: chartread [-options] outfile -v Verbose mode -c listno Set communication port from the following list (default 1) ** No ports found ** etc or with chartread -D I get: Read Target Test Chart, Version 2.0.0 Author: Graeme W. Gill, licensed under the AGPL Version 3 usage: chartread [-options] outfile -v Verbose mode -c listno Set communication port from the following list (default 1) Argyll 'V2.0.0' Build 'Linux 64 bit' System 'Linux #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 4.15.0-72-generic x86_64' usb_check_and_add: failed to open '/dev/bus/usb/004/025' ** No ports found ** As a last resort I uninstalled gnome-control-center with synaptic and the device is available again to chartread -D : Read Target Test Chart, Version 2.0.0 Author: Graeme W. Gill, licensed under the AGPL Version 3 usage: chartread [-options] outfile -v Verbose mode -c listno Set communication port from the following list (default 1) 1 = '/dev/bus/usb/004/008 (GretagMacbeth i1 Pro)' I re-installed and it's back to no-go. It's as though gnome-control-center is grabbing the device and not allowing access even when the window is closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855615 Title: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855615] Re: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS
Ok, so I was looking for an option like that but could not find it in any documentation. Just to add I was printing .ps targets from Argyll's targen / printarg / chartread / colprof workflow with: lp target.ps I did some more test prints and have attached the results again. The -o cm-calibration=1 option does seem to turn off calibration from "Device Colour Profiles" but the "color correction setting" in CUPS still has an effect on print output, quite noticeable on a couple of targets which go from orange to purple. I am going to create two profiles from targets printed with the -o cm- calibration=1 option with: a). Device Colour Profiles cms ON and a profile loaded, but Cups colour correction set to High Accuracy. b). Device Colour Profiles cms ON and a profile loaded, but Cups colour correction set to Uncorrected. Hopefully I will then be able to asses the best way forward. ** Attachment added: "printer output and screenshots" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855615/+attachment/5312322/+files/printer%20output%20pictures%202.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855615 Title: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855615] [NEW] Device colour profiles - on / off button not working Ubuntu 18.04.3LTS
Public bug reported: I've been trying to calibrate my printer in Ubuntu 18.04.3LTS with gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.5 Candidate: 1:3.28.2-0ubuntu0.18.04.5 Version table: *** 1:3.28.2-0ubuntu0.18.04.5 500 The least documented part of printer profiling is printing the target. Every guide says turn off printer profile calibration, but no-one tells you how. Through trial, error and a lot of paper and ink it seems to me as though the on / off button next to the printer description does nothing. If the user deletes all existing profiles the field reads Not calibrated and no button is displayed, though on a reboot this changes to a button showing colour management (CMS) on and two default profiles are displayed (default RGB and default grey) with RGB selected. The output of these two states is identical. If the setting is default RGB profile with no others loaded, then changing Cups in a browser to Colour Correction: uncorrected refreshes the state to Not Calibrated, though this is the only time I could force this. Setting Cups to Colour Correction: high accuracy does result in an altered output from the printer. I am guessing this is no colour profiling being applied. However if Cups Colour Correction: uncorrected is set, and a profile is loaded in Device Colour Profiles the output from the printer is the same whether or not the CMS on /off button is pressed. I think this is the result of the profile applied by Device Colour Profiles in either case. Similarly, using Cups Colour Correction: High Accuracy and a profile loaded in Device Colour Profiles, the printer output is the same whether or not the CMS on /off button is pressed, though the output is different from the preceding example. I presume this is the result of two colour transformations being carried out. The attached images of my printer output should hopefully help explain this situation. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "A series of jpgs showing the process" https://bugs.launchpad.net/bugs/1855615/+attachment/5310861/+files/printer%20output%20pictures.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855615 Title: Device colour profiles - on / off button not working Ubuntu 18.04.3LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854413] Re: Backlight adjustments shows OSD but does not change anything on Samsung OLED panel
** Bug watch added: Linux Kernel Bug Tracker #205699 https://bugzilla.kernel.org/show_bug.cgi?id=205699 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=205699 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854413 Title: Backlight adjustments shows OSD but does not change anything on Samsung OLED panel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1854413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854177] Re: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2
Looks good in master-next. I just noticed 5.3.0-24 was out and it exhibits the black screen. But, if I am reading it correctly 5.3.0-24 was tagged 3 weeks ago. I'll keep an eye out for the next one. Unless you meant something other than the linux-image-5.3.0-xx-generic package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854177 Title: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854413] [NEW] Backlight adjustments shows OSD but does not change anything on Samsung OLED panel
Public bug reported: When running Ubuntu with linux-image-5.3.0-23-generic, mainline 5.3.13, or latest 5.4+ my Lenovo ThinkPad P1 Gen 2 with a Samsung OLED panel is unable to change the backlight brightness. The buttons trigger the on- screen display and move the bar but the actual display brightness does not change. With the kernel option i915.enable_dpcd_backlight=1 it does make the backlight change but erratically. For example moving through the range you get stuff like off, medium bright, dim, bright, medium, off. This does work in Ubuntu linux-image-4.15.0-1059-oem. It seems the following commits in particular make the difference. UBUNTU: SAUCE: i915: intel_dp_aux_backlight: Fix max backlight calculations https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/eoan/commit/?h=oem&id=ff39163c455f31005e2709a2006a7605b3d8a05f UBUNTU: SAUCE: drm/i915: customize DPCD brightness control for specific panel https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/eoan/commit/?h=oem&id=cf7286b44a6e27967f5ed134c4492dd17bde118a It has been explained to me that these OEM changes are unlikely to be directly ported into -generic images but it seems relevant to document the issue. I ported the above commits to the latest linux mainline kernel and am running that (other than while reporting this issue). This was in part because >= 5.3.12 fixes another issue with this hardware where the screen remains black after a resume (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854177). I have filed https://bugzilla.kernel.org/show_bug.cgi?id=205699. https://github.com/altendky/linux/commit/395eb4b85f6a0f85061c0598247727de0d9316f6 https://github.com/altendky/linux/commit/c2dc38e6aadf3d979bea83e382a1b119574df7af Built with: git clean -fdx && cp /boot/config-5.3.0-23-generic .config && yes '' | make oldconfig && make clean && make -j `getconf _NPROCESSORS_ONLN` deb- pkg LOCALVERSION=-altendky-backlight Note that the use of DEVICE_ID_ANY is likely bad and the correct ID for this panel should be identified. I wanted to first confirm it worked before bothering to figure out which ID was needed there and how to get it. I have naively ported these patches. While I have done embedded C for years and some hardware design... I am not familiar with Linux kernel development nor any details of controlling this hardware. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: altendky 1381 F pulseaudio CurrentDesktop: KDE Date: Thu Nov 28 21:24:12 2019 InstallationDate: Installed on 2019-11-26 (2 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/lvm_group-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET40W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET40W(1.27):bd10/17/2019:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854413 Title: Backlight adjustments shows OSD but does not change anything on Samsung OLED panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854177] [NEW] Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2
Public bug reported: Present testing has focused on closing the laptop lid and reopening it. The laptop suspends as expected and resumes as expected (existing ssh sessions start working again) except that the display remains black and calls such as `xset -display :0 dpms force on` hang. The screen remains blank sSometimes for a few minutes, sometimes for many. In the example log it was 10 minutes and a few seconds before the display turned back on. One time trying to capture a log of the recovery I gave up after 70 minutes. While the display is black `/var/log/Xorg.0.log` repeats the following lines once per second. [ 119.384] (WW) modeset(0): hotplug event: connector 86's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails... [ 119.386] (II) modeset(0): EDID vendor "SDC", prod id 16705 [ 119.386] (II) modeset(0): Printing DDC gathered Modelines: [ 119.386] (II) modeset(0): Modeline "3840x2160"x0.0 545.12 3840 3888 3920 4160 2160 2164 2168 2184 +hsync -vsync (131.0 kHz eP) This stops when the display turns on and no other messages are logged. The journalctl log has a much longer repeated sequence of messages. I haven't confirmed exact matching of the whole repeated block but here's a snippet reporting a failure. Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Max Voltage Swing reached Nov 27 00:02:32 p1 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:86:eDP-1] Link Training failed at link rate = 54, lane count = 4 When the display turned back on I instead get the following success message. Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] clock recovery OK Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS3 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_start_link_train [i915]] Channel EQ done. DP Training successful I tested the mainline .deb package for 5.3.13 and it did not exhibit this issue. When I open the laptop lid after suspending by closing it the cursor reliably displays within about 1 second and the lock screen is shown within about another second. I further checked versions and the last mainline .deb to exhibit the issue is 5.3.11. 5.3.12 works well. Looking at the changelog for 5.3.12 showed the following two commits referencing i915 (don't let me mislead you here of course, just trying to provide as much info as possible). The first one strikes me as relevant but I haven't applied that patch to the Ubuntu 5.3.0-23 kernel and built it for testing. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f216a8507153578efc309c821528a6b81628cd2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed77d88752aea56b33731aee42e7146379b90769 ProblemType: Bug Dis
[Bug 1854177] Re: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2
** Attachment added: "xorg-2019-11-26T23_56_26-05_00.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854177/+attachment/5308164/+files/xorg-2019-11-26T23_56_26-05_00.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854177 Title: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 752542] Re: ACPI DSDT info
Lenovo ThinkPad P1 Gen 2 (20QT as opposed to 20QU) https://www.lenovo.com/us/en/laptops/thinkpad/thinkpad-p/P1-Gen-2/p/22WS2WPP102 ** Attachment added: "LENOVO-20QTCTO1WW.tar.gz" https://bugs.launchpad.net/lpbugreporter/+bug/752542/+attachment/5307983/+files/LENOVO-20QTCTO1WW.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752542 Title: ACPI DSDT info To manage notifications about this bug go to: https://bugs.launchpad.net/bumblebee/+bug/752542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817595] Re: [SRU] urdfdom-headers and urdfdom should not use locale dependent parsing for floating point numbers
Thanks for testing, Simon! > I was not able to find any fields where I could set "verification- done-bionic" Right under the bug description you'll see a set of tags that you can edit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817595 Title: [SRU] urdfdom-headers and urdfdom should not use locale dependent parsing for floating point numbers To manage notifications about this bug go to: https://bugs.launchpad.net/urdfdom-headers/+bug/1817595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847975] Re: extension does not start, sometime when starting crashes gnome-shell
** Changed in: gnome-shell-extension-show-ip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847975 Title: extension does not start, sometime when starting crashes gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-show-ip/+bug/1847975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817595] Re: [SRU] urdfdom-headers and urdfdom should not use locale dependent parsing for floating point numbers
This patch is complex enough to make folks a little uncomfortable with the SRU. Beyond Julian's suggestions (thanks Julian), Jose, are you willing to commit to thoroughly testing this and resolving any autopkgtest regressions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817595 Title: [SRU] urdfdom-headers and urdfdom should not use locale dependent parsing for floating point numbers To manage notifications about this bug go to: https://bugs.launchpad.net/urdfdom-headers/+bug/1817595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883159] Re: Binary crash, searching for non-existent DLL.
This has been fixed in 1.3.3 ** Changed in: liquidsoap (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883159 Title: Binary crash, searching for non-existent DLL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liquidsoap/+bug/883159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891054] Re: liquidsoap cannot decode mp3 & ogg
This has been fixed in 1.3.3 ** Changed in: liquidsoap (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891054 Title: liquidsoap cannot decode mp3 & ogg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liquidsoap/+bug/891054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404657] Re: installing liquidsoap opus plugin breaks liquidsoap vorbis plugin
Fixed in 1.3.7 ** Changed in: liquidsoap (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404657 Title: installing liquidsoap opus plugin breaks liquidsoap vorbis plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liquidsoap/+bug/1404657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481994] Re: ml2c_lc now undefined in dllgettextStub.so due to gcc 5
Fixed in 0.3.5-2 uploaded to Debian 15 Aug 2015 ** Changed in: ocaml-gettext (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481994 Title: ml2c_lc now undefined in dllgettextStub.so due to gcc 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocaml-gettext/+bug/1481994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838970] [NEW] Sync camomile 1.0.1-4 (universe) from Debian unstable (main)
Public bug reported: Please sync camomile 1.0.1-4 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * No-change rebuild for ocaml ABI changes. * Stick to the 0.8.5 version, because 1.0.1 ftbfs and breaks ocaml-gettext. * No-change rebuild for ocaml ABI changes. * Stick to the 0.8.5 version, because 1.0.1 ftbfs and breaks ocaml-gettext. * Rebuild against new OCAML ABIs. * Rebuild against new OCAML ABIs. * Rebuild against new OCAML ABIs. Camomile has been fixed and no longer FTBFS. It no longer breaks ocaml-gettext Changelog entries since current eoan version 0.8.5-1ubuntu1: camomile (1.0.1-4) unstable; urgency=low * Rebuild for source-only upload * Update maintainer email -- Kyle Robbertze Sun, 14 Jul 2019 07:03:04 +0200 camomile (1.0.1-3) unstable; urgency=medium * Remove build path in compiled artifacts (Closes: #922271) -- Kyle Robbertze Fri, 15 Feb 2019 08:21:51 +0200 camomile (1.0.1-2) unstable; urgency=medium * Use dune package instead of jbuilder * Remove broken symlinks (Closes: #919837) * Drop zh__PINYIN locale (Closes: #918562, #918563) * Install files in the correct location (Closes: #919658) * Bump Standards-Version to 4.3.0 (no change) -- Kyle Robbertze Tue, 29 Jan 2019 12:28:38 +0200 camomile (1.0.1-1) unstable; urgency=medium * New upstream version 1.0.1 * Add new uploader (Closes: #717786) * Bump Standards-Version (changed VCS-* to use salsa) * Move copyright to machine readable format * Update watch file to correctly find new releases * Bump dependency versions * Update Portuguese translation (Closes: #758118), thanks to Américo Monteiro * Add German manuall translations (Closes: #865968), thanks to Chris Leick * Drop stale patches * Restructured installed files to reflect new upstream structure * Move to debhelper from CDBS -- Kyle Robbertze Sat, 10 Nov 2018 20:25:20 +0200 ** Affects: camomile (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/1838970 Title: Sync camomile 1.0.1-4 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camomile/+bug/1838970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838829] [NEW] At first the touchpad worked, but after a few days of using my usb mouse, it stopped working entirely
Public bug reported: none ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-25-generic 4.18.0-25.26~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 2 16:34:59 2019 InstallationDate: Installed on 2019-07-29 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838829 Title: At first the touchpad worked, but after a few days of using my usb mouse, it stopped working entirely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1838829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
Just finished taking this for a spin, both on armhf (to ensure it now
works) and amd64 (to smoke test for no regressions).
Here is an up-to-date amd64 using 1.4~rc1-1build2:
$ cat << EOF >> test.py
> #!/usr/bin/env python3
>
> import pygraphviz
>
> graph = pygraphviz.AGraph()
> graph.add_node('foo')
> graph.add_node('bar')
> graph.add_edge('foo', 'bar')
> print('success!')
> EOF
$ chmod a+x test.py
$ ./test.py
success!
After installing 1.4~rc1-1build2.1 the results are unchanged-- it continues
working:
$ sudo apt install python3-pygraphviz/bionic-proposed
Setting up python3-pygraphviz (1.4~rc1-1build2.1) ...
$ ./test.py
success!
Now, here is an up-to-date armhf using 1.4~rc1-1build2:
$ cat << EOF >> test.py
> #!/usr/bin/env python3
>
> import pygraphviz
>
> graph = pygraphviz.AGraph()
> graph.add_node('foo')
> graph.add_node('bar')
> graph.add_edge('foo', 'bar')
> print('success!')
> EOF
$ chmod a+x test.py
$ ./test.py
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1561, in
__new__
nh = gv.agnode(graph.handle, n.encode(graph.encoding), _Action.find)
KeyError: 'agnode: no key'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./test.py", line 8, in
graph.add_edge('foo', 'bar')
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 478, in
add_edge
e = Edge(self, eh=eh)
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1625, in
__new__
s = Node(graph, nh=source)
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1563, in
__new__
raise KeyError("Node %s not in graph." % n)
KeyError: 'Node None not in graph.'
Broken, as mentioned in the bug report. Now with 1.4~rc1-1build2.1:
$ sudo apt install python3-pygraphviz/bionic-proposed
Setting up python3-pygraphviz (1.4~rc1-1build2.1) ...
$ ./test.py
success!
Fixed! Marking verification done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834379
Title:
armhf Bionic python3-pygraphviz package errors for simple use case
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
I've confirmed that this issue is only present in Bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
** Changed in: python-pygraphviz (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
** Changed in: python-pygraphviz (Ubuntu Disco) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
** Changed in: python-pygraphviz (Ubuntu Cosmic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
** Changed in: python-pygraphviz (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
** Description changed:
[Impact]
python3-pygraphviz does not work for even simple use cases on armhf
Bionic. See error output in Test Case section from adding an edge to a
graph.
This package is currently being used as a dependency of ROS2, which is
now including armhf as a target platform. The functionality that depends
on this package fails to run.
Conclusion from below testing is that the current package is somehow
corrupted.
A no-change rebuild in ppa:emersonknapp/ppa works properly on armhf.
[Test Case]
Using the following test file, and running python3 test.py, the program
raises an error. However program exits with no output as expected on
x86_64 and aarch64
```
# test.py
#!/usr/bin/env python3
import pygraphviz
graph = pygraphviz.AGraph()
graph.add_node('foo')
graph.add_node('bar')
graph.add_edge('foo', 'bar')
```
Error seen
```
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1561, in
__new__
nh = gv.agnode(graph.handle, n.encode(graph.encoding), _Action.find)
KeyError: 'agnode: no key'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "test.py", line 8, in
graph.add_edge('foo', 'bar')
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 478, in
add_edge
e = Edge(self, eh=eh)
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1625, in
__new__
s = Node(graph, nh=source)
File "/usr/lib/python3/dist-packages/pygraphviz/agraph.py", line 1563, in
__new__
raise KeyError("Node %s not in graph." % n)
KeyError: 'Node None not in graph.'
```
-
[Regression Potential]
- This package doesn't currently seem to work at all, so I don't see how
- it could get worse.
+ This is a no-change rebuild, regression potential is very low.
[Other Info]
If I upgrade to 1.5 via pip after installing the apt dependency
libgraphviz-dev, this same snippet works on all of these platforms.
It also works if I install pygraphviz 1.4rc1 from pip. Also, it seems to
work with the debian package python3-pygraphviz 1.4 from cosmic. As far
as I can tell, there are no differences between the cosmic and the
bionic packages, other than it was rebuilt for Python 3.7.
Here's a summary:
Bionic1.4~rc1 Debian Broken
Cosmic1.4~rc1 Debian Works
Disco 1.5 Debian Works
Bionic1.4~rc1 pip Works
Bionic1.5 pip Works
And one more data point; if I pull down the debian sources (apt-get
source python3-pygraphviz ; apt-get build-dep python3-pygraphviz), build
with no modifications (debuild -uc -us), and then install (dpkg -i
python3-pygraphviz_1.4~rc1-1build2_armhf.deb), it works just fine.
From all of this, I can only conclude that the Ubuntu Bionic armhf
debian package is somehow corrupt. Perhaps a rebuild of the package
would solve the problem.
-
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python3-pygraphviz 1.4~rc1-1build2
ProcVersionSignature: Ubuntu 4.15.0-1041.43-aws 4.15.18
Uname: Linux 4.15.0-1041-aws aarch64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: armhf
Date: Wed Jun 26 22:23:47 2019
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: python-pygraphviz
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834379
Title:
armhf Bionic python3-pygraphviz package errors for simple use case
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834379] Re: armhf Bionic python3-pygraphviz package errors for simple use case
Can you try getting a no-change rebuild in a PPA? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834379 Title: armhf Bionic python3-pygraphviz package errors for simple use case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygraphviz/+bug/1834379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828464] Re: Show-IP extension makes shell crash on startup
What is the output of the following? journalctl /usr/bin/gnome-shell -f Start it before installing the extension and let it run until after the crash. ** Changed in: gnome-shell-extension-show-ip (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828464 Title: Show-IP extension makes shell crash on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-show-ip/+bug/1828464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019222] Re: camlimages does not handle any external format (PNG, JPEG, ...) in Precise
This has been fixed with the upload of 1:4.2.6 to Debian ** Changed in: camlimages (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019222 Title: camlimages does not handle any external format (PNG, JPEG, ...) in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camlimages/+bug/1019222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1513194] Re: h5dump crashes with flag passed after input file
This has been fixed upstream in hdf5-1.8.17: https://portal.hdfgroup.org/display/support/HDF5+1.8.17 with: https://bitbucket.hdfgroup.org/projects/HDFFV/repos/hdf5/commits/a1617b7cdbe14173fcf690b4627059fa4528c19b ** Changed in: hdf5 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513194 Title: h5dump crashes with flag passed after input file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdf5/+bug/1513194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824921] [NEW] package linux-firmware 1.175.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 2
Public bug reported: System is a new build. Right off the lastest ISO. Updates were applied. There were issues applying updates. This system does have a mobile i7 and a Geforce 960m 4GB edition. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-firmware 1.175.3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Thu Apr 11 20:06:27 2019 Dependencies: Df: Dmesg: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2019-04-11 (4 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: linux-firmware Title: package linux-firmware 1.175.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824921 Title: package linux-firmware 1.175.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1824921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
On my system, I found that the immediate cause of those messages was running apcupsd, with the default configuration of trying to talk over a serial cable, but without a UPS connected to it. Even if it was otherwise configured for USB, I also had to remove the "DEVICE /dev/ttyS0" line to fix the IRQ errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood of do_IRQ: No irq for vector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797557] Re: Bionic updates break upgrade (apt remove libc6-armhf-cross first)
I had the exact same symptoms as sboylan above, and brute-force fixed this issue by running sudo dpkg -P --force-depends libc6-armel-cross libc6-armhf-cross libc6 -dev-armel-cross libc6-dev-armhf-cross libasan2-armhf-cross libatomic1 -armhf-cross libgcc1-armhf-cross libgomp1-armhf-cross libstdc++-4.8-dev- armhf-cross libstdc++-5-dev-armhf-cross libstdc++6-armhf-cross libubsan0 -armhf-cross then running sudo apt --fix-broken install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797557 Title: Bionic updates break upgrade (apt remove libc6-armhf-cross first) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain-base/+bug/1797557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795292] Re: ELAN469D touch pad not working
Hey everyone. I was directed here from askubuntu. Having the same issue. No wifi or touchpad. Although I updated to the latest BIOS through windows before making the switch to ubuntu. Before looking around, I was able to update to kernel v5.0.4-50004 (using ethernet to usb converter). and still no touchpad or wifi. Have there been any updates reguarding getting at least the touchpad working without having to compile 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/1795292 Title: ELAN469D touch pad not working To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816004] Re: GLVND: AARCH64 : Fix address passed to clear cache
I just tagged a 1.1.1 release for libglvnd with the AARCH64 and PPC64LE fixes: https://github.com/NVIDIA/libglvnd/releases/tag/v1.1.1 If you're switching from 1.0.0, note that the dispatch table order changed between v1.0.0 and v1.1.0, so you'll need matching builds of libGLdispatch.so, libOpenGL.so, libGL.so, and the libGLES*.so libraries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816004 Title: GLVND: AARCH64 : Fix address passed to clear cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+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 /usr/lib/x86_64-linux-gnu/l
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 1662137] Re: 16.04 recovery shell works only for two minutes
*** This bug is a duplicate of bug 1636503 *** https://bugs.launchpad.net/bugs/1636503 This is still happening for me in 18.04.1 LTS. Can anyone else confirm the bug is still present? I'm not sure if I just did a botched update that didn't replace the systemd package or if the bug is back. Another oddity that I'm experiencing is the text cursor going to the left of "ubuntu login:" or "kyle@ubuntu:~$" after a similar duration as the recovery bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662137 Title: 16.04 recovery shell works only for two minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1662137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662137] Re: 16.04 recovery shell works only for two minutes
*** This bug is a duplicate of bug 1636503 *** https://bugs.launchpad.net/bugs/1636503 ** This bug has been marked a duplicate of bug 1636503 recovery mode gets borked after some time out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662137 Title: 16.04 recovery shell works only for two minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1662137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 639608] Re: manual duplex printing missing
I've actually gotten rid of both that printer and that laptop since then so I'm afraid I can't help! Sorry! Anne On Sat 29 Sep 2018 at 18:01, gf <639...@bugs.launchpad.net> wrote: > Hello Ann and Carsten, > Thank you for reporting this bug and describing a problem with > system-config-printer. You made this bug report in 2010 and Ubuntu has > been updated since then. > > Could you confirm that this is no longer a problem and that we can close > the bug report? > If it is still a problem, are you still interested in finding a solution > to this bug? > If you are, could you let us know, and in the current version, run the > following (only once): > apport-collect BUGNUMBER > and upload the updated logs and and any other logs that are relevant for > this particular issue. > > Thank you again for helping make Ubuntu better. > G > [Ubuntu Bug Squad volunteer triager] > > ** Changed in: gtk (Ubuntu) >Status: New => Incomplete > > ** Changed in: system-config-printer (Ubuntu) >Status: New => Incomplete > > ** Changed in: hplip (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/639608 > > Title: > manual duplex printing missing > > Status in gtk package in Ubuntu: > Incomplete > Status in hplip package in Ubuntu: > Incomplete > Status in system-config-printer package in Ubuntu: > Incomplete > > Bug description: > Binary package hint: hplip > > I have problem with 'manual duplex' printing on my HP CP1514n in Ubuntu. > In 10.04 I select the double sided print option (print long edge). Print > is now simplex printing, which is wrong. > In 10.10beta there is a new option checkbox : Duplexer installed. > Because I don't have a duplexer attached to my printer, I deselect this > option. But then I cannot select double sided printing any more. > What to do? > I want first to print the even pages, then I want to place the printed > stack (even pages) in the printer tray. > When I at last acknowledge with the OK printer button, the printer shall > print the odd pages in the correct order on the opposite side of the even > pages. > This works perfectly in Windows. Ubuntu (Linux) must have the same > functionality! > I believe a lot of people have the same problem! > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gtk/+bug/639608/+subscriptions > -- Sent from my iPhone -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/639608 Title: manual duplex printing missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk/+bug/639608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738164] Re: [snap] U2F doesn't work with yubikey
jdstrand, I've added those rules, and the denials go away, but I'm afraid it still doesn't work. There doesn't seem to be any denials, but it's like chrome just doesn't see it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738164 Title: [snap] U2F doesn't work with yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791814] Re: The core snap was renamed to system in the 2.35 release
Customer says: "... using the `snapd` golang API, but that just calls
`GET /v2/interfaces`"
And:
Can someone please verify, for certain, the internal name for the core snap has
changed to `system`. I am seeing this when using the snapd API to request
information about available connections. Example from the API output:
```{Snap:system Name:bluetooth-control Interface:bluetooth-control Attrs:map[]
Apps:[]```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791814
Title:
The core snap was renamed to system in the 2.35 release
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1791814/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786910] Re: Latest patch breaks command line 'restart all'
For those of you using Chef with Ubuntu, the following worked for us as part of our deploy recipes: package 'Install Monit 1:5.16-2' do package_name 'monit' version '1:5.16-2' options '--allow-downgrades' end -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786910 Title: Latest patch breaks command line 'restart all' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1786910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786910] Re: Latest patch breaks command line 'restart all'
Is there any update to this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786910 Title: Latest patch breaks command line 'restart all' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1786910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786910] Re: Latest patch breaks command line 'restart all'
** Description changed: Running 'monit restart all' on command line was working yesterday 13.8.2018 but after latest security patch was installed it gives an error 'Invalid action “action=restart”' Ubuntu 16.04.4 LTS monit: - Installed: 1:5.16-2ubuntu0.1 + Installed: 1:5.16-2ubuntu0.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786910 Title: Latest patch breaks command line 'restart all' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1786910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782285] Re: Add missing libGLESv1_CM.so to Bionic
The actual release tag (plus tarball and release notes) is here: https://github.com/NVIDIA/libglvnd/releases/tag/v1.1.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782285 Title: Add missing libGLESv1_CM.so to Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782285] Re: Add missing libGLESv1_CM.so to Bionic
The other libglvnd libraries would already cause a conflict with nvidia-340, wouldn't they? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782285 Title: Add missing libGLESv1_CM.so to Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780039] Re: Khronos CTS failure on Bionic due to missing change in libegl1
Liblgnvd has a new 1.1.0 point release, which includes that fix (as well as an assortment of others). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780039 Title: Khronos CTS failure on Bionic due to missing change in libegl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1780039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782285] Re: Add missing libGLESv1_CM.so to Bionic
Also, while GLESv1 is the fixed-pipeline stuff, libGLESv1_CM.so just provides a set of forwarder functions. Libglvnd forwards those calls to a vendor library based on the current context, so it's up to the vendor library what to do with them. If a vendor doesn't provide a function to forward to, then libglvnd sends the function to an error or no-op stub (the same way it would handle calling a function without a current context at all). For something like GLESv1, if a vendor library doesnt't support it, then it would just return NULL from its eglCreateConext or glXCreateContextAttribsARB implementation. At that point, the vendor library doesn't need to implement any of the GLESv1 functions -- trying to call a GLESv1 function without a current GLESv1 context is an application error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782285 Title: Add missing libGLESv1_CM.so to Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782285] Re: Add missing libGLESv1_CM.so to Bionic
Just because Mesa doesn't provide GLESv1 doesn't mean other vendor libraries can't. It certainly isn't any reason to prohibit GLESv1 support if a vendor library would otherwise be able to support it. Conversely, having the full set of libglvnd libraries (including libGLESv1_CM.so) doesn't require vendors to support every flavor of OpenGL. If you remove libGLESv1_CM.so, then any driver that does support GLESv1 would have to install its own copy of that library. Two drivers that support GLESv1 would then end up overwriting each other or playing symlink games to switch between them. The whole point of libglvnd is to avoid that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782285 Title: Add missing libGLESv1_CM.so to Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1782285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
I've encountered this bug on the past TWO kernel updates of my Xubuntu 16.04.4 (now .5) system that uses an Nvidia card. Initially I found that falling back to the previous kernel was a satisfactory workaround. This morning, I tried using the "Additional drivers" system setting to change from the Nvidia driver to the noveau driver -- and that has worked perfectly so far. This might be a possible recommended solution. I had originally switched from noveau to the proprietary driver because noveau didn't work properly, but that was several years ago and it has obviously gotten much metter! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
s/metter/better/!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779760] Re: Aptly 1.2.0 tries to use incompatible GPG2
1.3.0 is available in Cosmic, but Bionic still has 1.2.0. Therefore, the bug is still not fixed in Bionic (which is a long-term support release.) What is the solution for people who use Bionic and would rather stick with LTS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779760 Title: Aptly 1.2.0 tries to use incompatible GPG2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptly/+bug/1779760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780821] [NEW] package libc-bin 2.27-3ubuntu1 failed to install/upgrade: instalado libc-bin paquete post-installation guión el subproceso devolvió un error con estado de salida 139
Public bug reported: Failed when trying to install OBS Studio: sudo add-apt-repository ppa:obsproject/obs-studio sudo apt-get install obs-studio ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libc-bin 2.27-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libfdk-aac1:amd64: Install libqt5x11extras5:amd64: Install obs-studio:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jul 9 12:03:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 ErrorMessage: instalado libc-bin paquete post-installation guión el subproceso devolvió un error con estado de salida 139 InstallationDate: Installed on 2016-11-15 (601 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: glibc Title: package libc-bin 2.27-3ubuntu1 failed to install/upgrade: instalado libc-bin paquete post-installation guión el subproceso devolvió un error con estado de salida 139 UpgradeStatus: Upgraded to bionic on 2018-05-06 (64 days ago) ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780821 Title: package libc-bin 2.27-3ubuntu1 failed to install/upgrade: instalado libc-bin paquete post-installation guión el subproceso devolvió un error con estado de salida 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1780821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779760] [NEW] Aptly 1.2.0 tries to use incompatible GPG2
Public bug reported: Because Ubuntu Bionic ships with GPG2 as "gpg", Aptly tries to use this instead of "gpg1". However, the command line options for GPG2 are different from GPG1, and Aptly hasn't yet been fully ported to GPG2. The only version they currently officially support is GPG1. In addition, Aptly's "internal" PGP implementation doesn't seem to properly support subkeys (which we are using), so that won't work for us as a workaround. This was fixed as of upstream pull request #734. It makes sure "gpg" is the correct version, and if not, it falls back to "gpg1". The simplest fix for this issue would be to backport these commits. ** Affects: aptly (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/1779760 Title: Aptly 1.2.0 tries to use incompatible GPG2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptly/+bug/1779760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768855] Re: ufraw-batch in bionic segfault
I'm hitting this in 18.04 as well, trying to use ufraw-batch for my .CR2 thumbnails. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to lensfun in Ubuntu. https://bugs.launchpad.net/bugs/1768855 Title: ufraw-batch in bionic segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lensfun/+bug/1768855/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-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 1743439] Re: Lubuntu installer crashes when choosing LVM encrypted disk
I grabbed the release installer and ran some tests this morning. It appears bug 1638420 has been fixed. Because of that, I was not able to make bug 1743439 happen. I'm not sure 1743439 was actually corrected, but since we can no longer reproduce the issue, I think we can mark 1743439 closed. -Kyle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743439 Title: Lubuntu installer crashes when choosing LVM encrypted disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1743439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743439] Re: Lubuntu installer crashes when choosing LVM encrypted disk
It was suggested that this bug is a duplicate of 1638420 https://bugs.launchpad.net/bugs/1638420 but it is not. The bug 1638420 still exists in the 18.04 installer the last time I checked. It is because of bug 1638420 that we end up using the < Back button, and change the Installation Type. That is when the installer crashes (bug 1743439). 1638420 is about the installer missing required components for LVM encrypted disk. 1743439 is about the installer crashing when you change the Installation Type. Again the video demonstrates this: https://www.youtube.com/embed/htFL03ZEY7c Fixing bug 1638420 may mitigate 1743439 because users will not fail the encrypted install and require them to go back and switch the Installation Type, but they are separate issues. -Kyle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743439 Title: Lubuntu installer crashes when choosing LVM encrypted disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1743439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743439] Re: Lubuntu installer crashes when choosing LVM encrypted disk
** This bug is no longer a duplicate of bug 1638420 LVM install with Lubuntu fails due to missing lvm2 package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743439 Title: Lubuntu installer crashes when choosing LVM encrypted disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1743439/+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 1663247] Re: Conflicts even if organize is used when both parts are built in the same run
*** This bug is a duplicate of bug 1628098 *** https://bugs.launchpad.net/bugs/1628098 ** This bug has been marked a duplicate of bug 1628098 organize needs to run after build in stage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1663247 Title: Conflicts even if organize is used when both parts are built in the same run To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1663247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769016] [NEW] nsswitch.conf doesn't specify 'resolve' to support systemd-resolved
Public bug reported: After upgrading from Ubuntu 16.04 to 18.04, my openconnect vpn connection stopped working. The problem appeared to be related to DNS resolution. After some digging, I discovered that the vpnc-script hook executed by openconnect was adding my VPN DNS servers to /etc/resolv.conf, which systemd-resolve --status was reporting as part of the global config instead of being associated with my VPN interface (tun0). This appeared to break all VPN and non-VPN traffic in my configuration. I found that vpnc-script needed to find 'resolve' in /etc/nsswitch.conf in order to correctly configure the VPN DNS servers with systemd- resolved instead of prepending them to /etc/resolv.conf. http://git.infradead.org/users/dwmw2/vpnc- scripts.git/commitdiff/62e86babac9f734ba031a547501cbe8e5940d83b Adding 'resolve' to the 'hosts:' line in my /etc/nsswitch.conf allowed normal traffic flow. It seems like if 18.04 defaults to using systemd-resolve for DNS resolutions, then the default nsswitch.conf configuration should also declare 'resolve' in the 'hosts:' line, which does not appear to be the case. This would have allowed my VPN connection to continue working successfully after the upgrade. $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 $ dpkg -l libc-bin openconnect systemd vpnc-scripts Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-=-==-=- ii libc-bin 2.27-3ubuntu1 amd64 GNU C Library: Binaries ii openconnect 7.08-3 amd64 open client for Cisco AnyConnect VPN ii systemd 237-3ubuntu10 amd64 system and service manager ii vpnc-scripts 0.1~git20171005-1 all Network configuration scripts for VPNC and OpenConnect ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: openconnect systemd-resolve vpnc-script -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769016 Title: nsswitch.conf doesn't specify 'resolve' to support systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1769016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768388] [NEW] "Open Tilix Here" still in context menu after uninstalling Tilix
Public bug reported: On Ubuntu Budgie there is an option in the context menu in GNOME Files to "Open Tilix Here" which will open that directory in the Tilix terminal emulator. However, after uninstalling Tilix the option still appears but now does nothing (since its trying to open a program that doesn't exist on the system anymore). There should be a check somewhere to verify that Tilix is actually installed before showing the option. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue May 1 22:07:57 2018 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2018-05-01 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Package changed: gnome-terminal (Ubuntu) => budgie-desktop (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768388 Title: "Open Tilix Here" still in context menu after uninstalling Tilix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1768388/+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 1747714] Re: network manager snap service name regression
I see nplan 0.32~16.04.4 in core currently in edge: 16-2.32.5+git694.b490763 Not easy to figure out which revision of core contains a particular version of a particular deb, since I can't find core build manifests FWIW -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747714 Title: network manager snap service name regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1747714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993298] Re: Please make NetworkManager-controlled dnsmasq respect /etc/hosts
I found a solution on stackoverflow thanks to @kbenoit there. https://askubuntu.com/questions/117899/configure-networkmanagers- dnsmasq-to-use-etc-hosts This is not really a bug at all. You just have to configure stuff under /etc/NetworkManager/dnsmasq.d instead, e.g., # echo "addn-hosts=/etc/hosts" > /etc/NetworkManager/dnsmasq.d/hosts.conf # service network-manager restart I will point out the following statement from the networkmanager.conf man page ON THE GNOME WEBSITE (not on the ubuntu 16.04 man page): It is possible to pass custom options to the dnsmasq instance by adding them to files in the "/etc/NetworkManager/dnsmasq.d/" directory. Add any options you want. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993298 Title: Please make NetworkManager-controlled dnsmasq respect /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/993298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747714] Re: network manager snap service name regression
When can we expect this to land in Core on stable? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747714 Title: network manager snap service name regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1747714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
@tyhicks I can also confirm that the issue appears to be resolved with linux- image-4.13.0-38-generic_4.13.0-38.43+lp1759920.1 Below is the requested information. $ uname -a Linux mercury 4.13.0-38-generic #43+lp1759920.1 SMP Tue Apr 3 22:59:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 4.13.0-38.43+lp1759920.1-generic 4.13.16 $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=5dd1c110-663e-4cf0-9a63-45815590a186 ro quiet splash vt.handoff=7 $ dmesg -t | grep -i microcode microcode: microcode updated early to revision 0x84, date = 2018-01-21 microcode: sig=0x906e9, pf=0x20, revision=0x84 microcode: Microcode Update Driver: v2.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)
@tyhicks I can confirm that adding 'apparmor=0' to the kernal boot parameters resolved the issue on an effected system. This was tested on 4.13.0-37-generic, with intel microcode 3.20180312.0 I will proceed with testing kernel: need linux- image-4.13.0-38-generic_4.13.0-38.43+lp1759920.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
