[Touch-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
** Attachment added: "boot messages with plymouth debugging messages" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5352286/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. In recovery mood, I can log in. With no external monitors attached, it works. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
** Summary changed: - booting with splash hangs when external monitors are connected (pure intel laptop) + booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) ** Description changed: + I think this is a problem with the splash boot loader. This problem is + not reproduced if using nosplash. - I think this is a problem with the splash boot loader. + I have installed 20.04 to this laptop. Thinkpad T480, i7, intel + graphics. - I have installed 20.04 to this laptop. Clean install, not an upgrade. + Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. - I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. + I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. + In recovery mood, I can log in. - I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. + + With no external monitors attached, it works. + + I am used to having such problems with Nvidia graphics is involved, but + this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed - tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed + tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo UHD Graphics 620 [17aa:225d] + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are
Re: [Touch-packages] [Bug 1869024] Re: add support for DynamicUser feature of systemd
On 2020-04-10 1:16 p.m., Jamie Strandboge wrote: > The abstraction is meant to cover the client, not systemd internal > specifics. A client simply accessing that DBus API won't need it and a > client simply accessing those sockets won't need it. It very well might > be that a profiled application is using some *ctl command from systemd > that would need it, but in that case said command would need to be added > to the policy and the boot-id could be added at that time. I don't know as squid, named and samba (to name a few) generate many denials trying to read /proc/sys/kernel/random/boot_id. None of those are explicitly trying to use the DynamicUser feature. Could it be just a side effect of how nsswitch.conf is setup by default? $ grep systemd /etc/nsswitch.conf passwd: files systemd group: files systemd Maybe you'd prefer this to be reported/discussed in a separated LP? Regards, Simon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1869024 Title: add support for DynamicUser feature of systemd Status in snapd: In Progress Status in apparmor package in Ubuntu: Fix Released Bug description: systemd offers to create dynamic (and semi-stable) users for services. This causes many services using Apparmor profiles to trigger those denials (even when they don't use the DynamicUser feature): audit: type=1107 audit(1585076282.591:30): pid=621 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/systemd1" interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" mask="send" name="org.freedesktop.systemd1" pid=709 label="/usr/sbin/squid" peer_pid=1 peer_label="unconfined" And more recently with systemd 245 this also get shown: audit: type=1400 audit(1585139000.628:39): apparmor="DENIED" operation="open" profile="/usr/sbin/squid" name="/run/systemd/userdb/" pid=769 comm="squid" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Additional information: # lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 # uname -a Linux foo.example.com 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # apt-cache policy apparmor squid apparmor: Installed: 2.13.3-7ubuntu2 Candidate: 2.13.3-7ubuntu2 Version table: *** 2.13.3-7ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status squid: Installed: 4.10-1ubuntu1 Candidate: 4.10-1ubuntu1 Version table: *** 4.10-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1869024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872256] [NEW] Unable to play DVD disc / The playback of this move requires a DVD source plugin which is not installed.
Public bug reported: I am unable to play DVD discs. Followed the usual Ubuntu process, but the issue persists. Nothing aforementioned in https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044 helps. Ubuntu 20.04 beta. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgstreamer1.0-0 1.16.2-2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 02:09:35 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2020-04-06 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872256 Title: Unable to play DVD disc / The playback of this move requires a DVD source plugin which is not installed. Status in gstreamer1.0 package in Ubuntu: New Bug description: I am unable to play DVD discs. Followed the usual Ubuntu process, but the issue persists. Nothing aforementioned in https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044 helps. Ubuntu 20.04 beta. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgstreamer1.0-0 1.16.2-2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 02:09:35 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2020-04-06 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1872256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel laptop)
** Summary changed: - booting with splash hangs when external monitors are connected + booting with splash hangs when external monitors are connected (pure intel laptop) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870585] Re: Not cleaning /var/tmp by default
** Tags added: sosreport sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1870585 Title: Not cleaning /var/tmp by default Status in systemd package in Ubuntu: New Bug description: 1) 20.04 2) 245.2-1ubuntu2 3) I expect /var/tmp to be cleaned up in some way. 4) It's commented out per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773313 In sosreport was comparing the difference between /tmp (Ubuntu/Debian) and /var/tmp (RH) and determined that as long as /var/tmp gets cleaned on a regular basis we would prefer /var/tmp. The bug that appears to have prompted the disabling was fixed a long time ago, can we have this 30d delete re-enabled by default? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870585/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870850] Re: Multi-line paste broken between kitty and nano 4.8 [focal]
This bug was fixed in the package nano - 4.8-1ubuntu1 --- nano (4.8-1ubuntu1) focal; urgency=medium * Thanks Benno Schulenberg for providing the info and patches * debian/patches/git_justify_segfault.patch: - backprot an upstream fix to avoid a segfault when justifying empty lines (lp: #1866820) * debian/patches/git_newline_paste.patch: - backport an upstream fix for pasting new lines via kitty (lp: #1870850) -- Sebastien Bacher Fri, 10 Apr 2020 16:12:30 +0200 ** Changed in: nano (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1870850 Title: Multi-line paste broken between kitty and nano 4.8 [focal] Status in nano package in Ubuntu: Fix Released Bug description: Ubuntu 20.04 Focal beta (as of 2020-04-04) nano 4.8-1 What I expect to happen: multi-line paste into nano via kitty pastes multiple lines. What happens instead: pasted multi-line text is one line with no line breaks. There is a bit of a spat between the developers of kitty (gnome- terminal:kitty::screen:tmux, basically) and nano about how to do multi-line pasting. See e.g.: * https://savannah.gnu.org/bugs/?58010 * https://lists.gnu.org/archive/html/nano-devel/2020-03/msg5.html * https://github.com/kovidgoyal/kitty/issues/994 Without taking sides, the facts are: * With the current versions in focal (kitty 0.15.0 and nano 4.8), pasting multi-line will result in newlines being eaten. * nano 4.9 introduces a fix (commit 481529e8650d105c3280def764e4917af0cabb49) which brings the newline handling more in line with other terminal-aware programs (treating raw \n as line break). Peripherally, nano 4.8 introduced new bracketed paste mode support. This makes a read of the kitty github issue above harder, since the issue being reported here is about an incompatibility in bracketed paste mode between kitty and nano, not pre-bracketed ^J handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1870850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866820] Re: crash in nano-4.8 when typing ^6 ^J [patch]
This bug was fixed in the package nano - 4.8-1ubuntu1 --- nano (4.8-1ubuntu1) focal; urgency=medium * Thanks Benno Schulenberg for providing the info and patches * debian/patches/git_justify_segfault.patch: - backprot an upstream fix to avoid a segfault when justifying empty lines (lp: #1866820) * debian/patches/git_newline_paste.patch: - backport an upstream fix for pasting new lines via kitty (lp: #1870850) -- Sebastien Bacher Fri, 10 Apr 2020 16:12:30 +0200 ** Changed in: nano (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1866820 Title: crash in nano-4.8 when typing ^6 ^J [patch] Status in nano package in Ubuntu: Fix Released Bug description: Nanos since version 4.0 contain a silly oversight: when the user tries to justify an empty region (with ^6 ^J, or similar), nano crashes. Attached upstream patch fixes the problem. Please apply to Focal before it is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1866820/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872241] Re: evolution-addressbook-factory crashed with signal 5 in g_thread_new()
*** This bug is a duplicate of bug 1858320 *** https://bugs.launchpad.net/bugs/1858320 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1858320, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872241/+attachment/5352162/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352164/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352168/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352169/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352170/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352171/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352172/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1858320 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872241 Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new() Status in evolution-data-server package in Ubuntu: New Bug description: it was crashing in the background, without me actively doing anything with the addressbook ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 16:27:54 2020 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory InstallationDate: Installed on 2017-10-13 (911 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory Signal: 5 SourcePackage: evolution-data-server StacktraceTop: g_thread_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 e_data_factory_spawn_subprocess_backend () at /usr/lib/x86_64-linux-gnu/libebackend-1.2.so.10 () at /usr/lib/x86_64-linux-gnu/libedata-book-1.2.so.25 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872242] [NEW] HDA Intel PCH on samsung laptop: Headphones not working, speakers are ok
Public bug reported: Speakers in my samsung laptop are ok, but headphones don't work (no sound). Using Ubuntu 18.04 defaults. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr1936 F pulseaudio /dev/snd/controlC0: sartojr1936 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:47:32 2020 InstallationDate: Installed on 2020-01-14 (88 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1377 F pulseaudio sartojr1936 F pulseaudio /dev/snd/controlC0: gdm1377 F pulseaudio sartojr1936 F pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [760XBE, Realtek ALC256, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P02REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - Speakers in my samsung laptop are ok, but hearphones are muted. Using + Speakers in my samsung laptop are ok, but headphones are muted. Using Ubuntu 18.04 defaults. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: sartojr1936 F pulseaudio - /dev/snd/controlC0: sartojr1936 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: sartojr1936 F pulseaudio + /dev/snd/controlC0: sartojr1936 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:47:32 2020 InstallationDate: Installed on 2020-01-14 (88 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: - LANGUAGE=pt_BR:pt:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pt_BR.UTF-8 - SHELL=/bin/bash + LANGUAGE=pt_BR:pt:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pt_BR.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: gdm1377 F pulseaudio - sartojr1936 F pulseaudio - /dev/snd/controlC0: gdm1377 F pulseaudio - sartojr1936 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: gdm1377 F pulseaudio + sartojr1936 F pulseaudio + /dev/snd/controlC0: gdm1377 F pulseaudio + sartojr1936 F pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [760XBE, Realtek ALC256, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
[Touch-packages] [Bug 1862566] Re: Corrupt sound played
Thanks for responding, Daniel. I missed your response. Unfortunately the issue is rare enough that I can't rely on reproducing it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1862566 Title: Corrupt sound played Status in pulseaudio package in Ubuntu: Expired Bug description: Every once in a while, I get sort of static-y sound with a degree of echo. This affects all sounds - within browser, using `play` from the terminal, etc. I can solve it by restarting pulseaudio. However, when I do that, I no longer get the terminal beep. Ubuntu 18.04 It's not common, and I can't find anything wrong in the system log. To restart, I killed the process: /usr/bin/pulseaudio --start --log-target=syslog It restarts itself, and audio generally seems to be working now. However, I now see in the system log things like: Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: ". Reason: Missing track ID in msid attribute. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed to create native session description. Type: "offer" SDP: "v=0\r\no=- 4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 0.0.0.0\r\nb=AS:30\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:7Ejs\r\na=ice-pwd:938XM9CAOZEbY2uhDpuFrizo\r\na=ice-options:trickle\r\na=fingerprint:sha-256 23:5D:00:AF:7B:28:BA:7D:02:92:4E:00:66:5F:B3:C1:C4:F2:BD:66:2B:10:03:74:93:B5:F1:9E:61:45:A3:15\r\na=setup:actpass\r\na=mid:0\r\na=sendrecv\r\na=msid: \r\na=rtcp-mux\r\na=rtpmap:119 google-data/9\r\na=ssrc:4203958806 cname:1yXiouHPsVbMJDst\r\na=ssrc:4203958806 msid:- \r\na=ssrc:4203958806 mslabel:-\r\na=ssrc:4203958806 label:\r\n" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 Uname: Linux 4.15.0-87-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 22:02:47 2020 InstallationDate: Installed on 2016-05-30 (1350 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-09-17 (511 days ago) dmi.bios.date: 01/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1862566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872235] [NEW] package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127
Public bug reported: When doing a distro-upgrade from Ubuntu 16.04 to 18.04 shared-mime-info broke the whole process throwing errors about libicu60, which was installed as new in the upgrade process. While the system was broken, I forced a reinstall of libicu60 (apt install --reinstall libicu60) which then allowed shared-mime-info to be installable. As this interrupted the distro upgrade process, I have rolled back to a backup before the upgrade took place, so this system is not in the same state as when the issue happened. I am not able to provide further debug assistance here. I've performed many upgrades from 16.04 to 18.04 and have only seen this issue happen once so far. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shared-mime-info 1.9-2 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sat Apr 11 13:33:07 2020 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2016-03-14 (1489 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: shared-mime-info Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2020-04-11 (0 days ago) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1872235 Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127 Status in shared-mime-info package in Ubuntu: New Bug description: When doing a distro-upgrade from Ubuntu 16.04 to 18.04 shared-mime- info broke the whole process throwing errors about libicu60, which was installed as new in the upgrade process. While the system was broken, I forced a reinstall of libicu60 (apt install --reinstall libicu60) which then allowed shared-mime-info to be installable. As this interrupted the distro upgrade process, I have rolled back to a backup before the upgrade took place, so this system is not in the same state as when the issue happened. I am not able to provide further debug assistance here. I've performed many upgrades from 16.04 to 18.04 and have only seen this issue happen once so far. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shared-mime-info 1.9-2 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sat Apr 11 13:33:07 2020 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2016-03-14 (1489 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: shared-mime-info Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2020-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1872235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
** Changed in: libxml2 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1869814 Title: ubuntu-docs build failure - possible solution Status in libxml2: New Status in libxml2 package in Ubuntu: Fix Committed Status in ubuntu-docs package in Ubuntu: Fix Released Bug description: ubuntu-docs failed to build during the second Focal Fossa test rebuild: https://launchpad.net/ubuntu/+archive/test- rebuild-20200327-focal/+build/18982738 It was itstool which failed to generate the localized zh_CN pages. If dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But excluding the Chinese pages is apparently not an acceptable solution. The itstool package in focal {build-,}depends on python3. I built itstool in a PPA with python2 instead, and in that PPA ubuntu-docs built fine without modifications: https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages So the root cause seems to lie neither in ubuntu-docs nor itstool. I would suspect that python3-libxml2 is buggy, but since itstool was built against python2 in eoan, it's hard to tell if it's a regression. Would building itstool against python2 be an acceptable workaround in focal? To manage notifications about this bug go to: https://bugs.launchpad.net/libxml2/+bug/1869814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872222] [NEW] [WH-CH700N, playback] fails after a while
Public bug reported: Whether I'm watching something, or doing something else whilst listening to playback, the playback stops and starts intermittently. Only happens on Bluetooth, not on Aux. CPU/RAM usage not high when issue occurs. As well as this, my bluetooth driver is not supported out of the box, so had to download 3rd party firmware file. Firmware file from here: https://github.com/winterheart/broadcom-bt-firmware Was the only solution that worked, possibly defective? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1395 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 19:18:26 2020 InstallationDate: Installed on 2020-04-10 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: WH-CH700N Symptom_PulseAudioLog: Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:56:08 tom-Laptop systemd[803]: pulseaudio.service: Succeeded. Apr 11 18:56:18 tom-Laptop systemd[803]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [WH-CH700N, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.50:bd10/08/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTUE-04L00VEN:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.sku: INVALID dmi.product.version: PSKTUE-04L00VEN dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/187 Title: [WH-CH700N, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Whether I'm watching something, or doing something else whilst listening to playback, the playback stops and starts intermittently. Only happens on Bluetooth, not on Aux. CPU/RAM usage not high when issue occurs. As well as this, my bluetooth driver is not supported out of the box, so had to download 3rd party firmware file. Firmware file from here: https://github.com/winterheart/broadcom-bt-firmware Was the only solution that worked, possibly defective? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1395 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 19:18:26 2020 InstallationDate: Installed on 2020-04-10 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: WH-CH700N Symptom_PulseAudioLog: Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:56:08 tom-Laptop systemd[803]: pulseaudio.service: Succeeded. Apr 11 18:56:18 tom-Laptop systemd[803]:
[Touch-packages] [Bug 1872224] [NEW] [Satellite L300, Realtek ALC268, Mic, Internal] Sound is distorted
Public bug reported: Hi My internal mic does not work properly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: petardemirev 1217 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 21:28:21 2020 InstallationDate: Installed on 2020-02-16 (55 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Вграден звук - HDA Intel Symptom_Jack: Mic, Internal Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [Satellite L300, Realtek ALC268, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd12/09/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLBGE-00T009G3:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite L300 dmi.product.sku: Montevina_Fab dmi.product.version: PSLBGE-00T009G3 dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1872224 Title: [Satellite L300, Realtek ALC268, Mic, Internal] Sound is distorted Status in alsa-driver package in Ubuntu: New Bug description: Hi My internal mic does not work properly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: petardemirev 1217 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 21:28:21 2020 InstallationDate: Installed on 2020-02-16 (55 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Вграден звук - HDA Intel Symptom_Jack: Mic, Internal Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [Satellite L300, Realtek ALC268, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd12/09/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLBGE-00T009G3:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite L300 dmi.product.sku: Montevina_Fab dmi.product.version: PSLBGE-00T009G3 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1872224/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872071] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872071 Title: ibus-x11 crashed with SIGSEGV in __GI___poll() Status in ibus package in Ubuntu: Confirmed Bug description: This happened at start up after software updater requested a restart.I attached unattended-upgrades.log unattended-upgrades-dpkg.log dpkg.log to show what packages were installed before the restart. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 07:16:32 2020 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-03-14 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f6b2b2919f6 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx PC (0x7f6b2b2919f6) ok source "0x10(%rax)" (0x1042f359537650) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __GI___poll (fds=0x7f6af80067e0, nfds=3, timeout=1766) at ../sysdeps/unix/sysv/linux/poll.c:29 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () Title: ibus-x11 crashed with SIGSEGV in __GI___poll() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872071/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872217] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()
*** This bug is a duplicate of bug 1872071 *** https://bugs.launchpad.net/bugs/1872071 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1872071, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872217/+attachment/5351993/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5351995/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5351998/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5351999/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5352000/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5352001/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5352002/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1872071 ibus-x11 crashed with SIGSEGV in __GI___poll() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872217 Title: ibus-x11 crashed with SIGSEGV in __GI___poll() Status in ibus package in Ubuntu: New Bug description: Problema constantes de Ibus ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 11 14:10:03 2020 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon ProcEnviron: LANG=es_VE.UTF-8 LANGUAGE=es_VE:es PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fc97abc69f6 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx PC (0x7fc97abc69f6) ok source "0x10(%rax)" (0xb143e205ad8c0) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __GI___poll (fds=0x55f25e1ac530, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () Title: ibus-x11 crashed with SIGSEGV in __GI___poll() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio
I haven't had this problem for some time now. Maybe there was an update that fixed it? However sometimes the sound volume controller in the top right corner is no associated with sound device being used. I mean when I change the volume or mute it nothing happens because it controls some other device not the one being used. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1860930 Title: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB headphones. When the headphones are plugged in during boot the internal speakers won't work. There is only crackling sound coming from them. It doesn't help in I unplug the headphones. There is no problem if they are not plugged in during boot. I'm using Ubuntu 19.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:26:35 2020 InstallationDate: Installed on 2019-12-19 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX531GXR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX531GXR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus S dmi.product.name: Zephyrus S GX531GXR_GX531GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872215] [NEW] There should be a GUI option to install non-security packages too
Public bug reported: The Software & Updates program lacks the option for the user to allow Ubuntu to automatically install non-security packages. It only supports security packages. I know Unattended-upgrades supports automatic upgrading of other packages but it might be too complicated for new users. There should be an easier way. Consider that Windows also deals with software updates "unattended" by default. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Attachment added: "windowsxp-update.png" https://bugs.launchpad.net/bugs/1872215/+attachment/5351985/+files/windowsxp-update.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1872215 Title: There should be a GUI option to install non-security packages too Status in unattended-upgrades package in Ubuntu: New Bug description: The Software & Updates program lacks the option for the user to allow Ubuntu to automatically install non-security packages. It only supports security packages. I know Unattended-upgrades supports automatic upgrading of other packages but it might be too complicated for new users. There should be an easier way. Consider that Windows also deals with software updates "unattended" by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1872215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
sync'd. please close this bug once libxml2 has been accepted https://launchpad.net/ubuntu/focal/+queue?queue_state=1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1869814 Title: ubuntu-docs build failure - possible solution Status in libxml2: New Status in libxml2 package in Ubuntu: In Progress Status in ubuntu-docs package in Ubuntu: Fix Released Bug description: ubuntu-docs failed to build during the second Focal Fossa test rebuild: https://launchpad.net/ubuntu/+archive/test- rebuild-20200327-focal/+build/18982738 It was itstool which failed to generate the localized zh_CN pages. If dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But excluding the Chinese pages is apparently not an acceptable solution. The itstool package in focal {build-,}depends on python3. I built itstool in a PPA with python2 instead, and in that PPA ubuntu-docs built fine without modifications: https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages So the root cause seems to lie neither in ubuntu-docs nor itstool. I would suspect that python3-libxml2 is buggy, but since itstool was built against python2 in eoan, it's hard to tell if it's a regression. Would building itstool against python2 be an acceptable workaround in focal? To manage notifications about this bug go to: https://bugs.launchpad.net/libxml2/+bug/1869814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872209] [NEW] syntax error message in f-string doesn't report line number
Public bug reported: I accidentally came across this annoying 'feature' or more likely, bug. The following code f"...foo ... {**kwargs} ..." produces a very basic syntax error message with no line number in the source file: File "", line 1 (**kwargs) ^ SyntaxError: invalid syntax This is the error message I would expect from the interpreter, but not when running a python script. A demo script is as follows: ''' f-string bug demonstration ''' def main(*args, **kwargs): print(f"main() called with *args={*args}, **kwargs={**kwargs}") With a longer python file, it is hard to find the offending line. Should the line number be displayed in the error message? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: python3 3.7.5-1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 17:08:35 2020 SourcePackage: python3-defaults UpgradeStatus: Upgraded to eoan on 2019-10-23 (170 days ago) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1872209 Title: syntax error message in f-string doesn't report line number Status in python3-defaults package in Ubuntu: New Bug description: I accidentally came across this annoying 'feature' or more likely, bug. The following code f"...foo ... {**kwargs} ..." produces a very basic syntax error message with no line number in the source file: File "", line 1 (**kwargs) ^ SyntaxError: invalid syntax This is the error message I would expect from the interpreter, but not when running a python script. A demo script is as follows: ''' f-string bug demonstration ''' def main(*args, **kwargs): print(f"main() called with *args={*args}, **kwargs={**kwargs}") With a longer python file, it is hard to find the offending line. Should the line number be displayed in the error message? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: python3 3.7.5-1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 17:08:35 2020 SourcePackage: python3-defaults UpgradeStatus: Upgraded to eoan on 2019-10-23 (170 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1872209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872198] Re: perte pave numerique
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872198 Title: perte pave numerique Status in xorg package in Ubuntu: New Bug description: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases
Thank you. FWIW, the man page also needs to be updated then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: New Bug description: Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872198] [NEW] perte pave numerique
You have been subscribed to a public bug: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- perte pave numerique https://bugs.launchpad.net/bugs/1872198 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases
glob actually needs to come back to some extend (* only), but otherwise yes, read the NEWS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: New Bug description: Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases
You mean, this feature is removed from apt? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: New Bug description: Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872200] Re: apt does not accept globs and regexes in some cases
Hmm seems I missed disabling that in apt list, good catch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: New Bug description: Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Same problem with Samsung Galaxy Book Flex 930QCG. The Samsung Galaxy Chromebook and Galaxy Book Flex look very similar, the sound chip should be the same, the Chromebook is open source and also uses the Linux kernel, can we refer to the Chromebook code? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color
[Touch-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298
Same problem with Samsung Galaxy Book Flex 930QCG. The Samsung Galaxy Chromebook and Galaxy Book Flex look very similar, the sound chip should be the same, the Chromebook is open source and also uses the Linux kernel, can we refer to the Chromebook code? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834566 Title: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Unable to get system speakers working running 19.04. At max volume, sound is barely perceptible through headphones. Pavucontrol shows sounds is present, but no amount of adjustments makes a difference. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 3355 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 28 00:44:13 2019 InstallationDate: Installed on 2019-06-05 (22 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AHK.029.190425.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP930MBE-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: Notebook 9 Series dmi.product.name: 930MBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK dmi.product.version: P02AHK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1085976] Re: Documentation has "FIXME" items that are unfixed
** Changed in: gtk+3.0 (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1085976 Title: Documentation has "FIXME" items that are unfixed Status in GTK+: Expired Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk+3.0 package in Debian: Fix Released Bug description: The Ubuntu package libgtk-3-doc supplies the items of interest... In the directory /usr/share/doc/libgtk-3-doc/gtk3 there are 3 files that contain FIXME content In that directory: # grep FIXME * GtkApplication.html:FIXME: MISSING XINCLUDE CONTENT GtkBuilder.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html: FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT # I am just starting with GTK+ and Glade, so having this instead of the first code sample in the gtk-getting-started page is a show-stopper. I suggest it's as urgent as documentation bugs get. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgtk-3-doc 3.4.2-0ubuntu0.5 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Mon Dec 3 05:59:17 2012 Dependencies: InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True PackageArchitecture: all SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1085976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872200] [NEW] apt does not accept globs and regexes in some cases
Public bug reported: Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1872200 Title: apt does not accept globs and regexes in some cases Status in apt package in Ubuntu: New Bug description: Observed with Ubuntu 20.04 Beta. apt remove 'mypackage*' does not remove all installed packages starting with “mypackage”. Instead: $ sudo apt remove 'mypackage*' Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package mypackage* However: $ sudo apt list --installed 'mypackage*' Listing... Done mypackage-data-v1/focal,focal,now 0.3.2-5build1 all [installed,automatic] mypackage1/focal,now 0.3.2-5build1 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1872200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871997] Re: The primary display will cause black screen when external 4K monitor is configured to flipped
** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871997/+attachment/5351890/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1871997 Title: The primary display will cause black screen when external 4K monitor is configured to flipped Status in xorg package in Ubuntu: Incomplete Bug description: The primary (built-in) display will cause black screen when external 4K monitor is configured to flipped Steps to reproduce: 1. plug 4K monitor via HDMI 2. open gnome-control-center 3. select Displays -> Orientation -> Landscape (flipped) 4. apply 5. black screen on built-in displays The primary display can be recovered if HDMI cable is re-plugged again. Machine: Dell XPS 13 9380 (Intel Coffee Lake) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:24:13 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-07 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. XPS 13 9380 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=60712c21-4620-4018-821e-afb9a77f9ec8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.10.2 dmi.board.name: 0SSY11 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.10.2:bd01/15/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0SSY11:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF 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.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872104] Re: Lenovo x230 fails to get into login mode after reboot - just purple screen or sometimes login w fprint and same purple screen
*** This bug is a duplicate of bug 1240336 *** https://bugs.launchpad.net/bugs/1240336 ** This bug has been marked a duplicate of bug 1240336 After release upgrade, the user loses permissions for several basic actions in the system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1872104 Title: Lenovo x230 fails to get into login mode after reboot - just purple screen or sometimes login w fprint and same purple screen Status in shadow package in Ubuntu: New Bug description: "Fresh" install, /home kept, via "Other " on install from usb Powering off gets me into sleep mode, power button configured to only on/off. More on/off gets real shut down. I have to go through safe mode, and have not found what gets it working. Last time I did all, and had to reboot again, because of same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: login 1:4.8.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 17:48:48 2020 InstallationDate: Installed on 2019-01-14 (451 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
My privileges in custom group is in att screenshot I think I got the same bug years ago, and checked about this on a MacBookPro 13" 2011, and the same appeared about the groups, but I had no login problems!? Same usb-stick with (maybe an newer zsynk? still within the same day 20.04) Now I know why my wifi was buggy on the Mac, after screen was black. I'll check on my dell xps m1530 and check about groups/privileges. That one is more like clean install. ** Attachment added: "privileges" https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/+attachment/5351889/+files/Screenshot%20from%202020-04-11%2014-51-59.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxdm package in Ubuntu: Triaged Status in policykit-desktop-privileges package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
I experienced this 10. april and made a bugreport about login, #1872104. I lost my adm privileges and "was put" to a custom group, att screenshot ** Attachment added: "custom group" https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/+attachment/5351888/+files/Screenshot%20from%202020-04-11%2014-53-05.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxdm package in Ubuntu: Triaged Status in policykit-desktop-privileges package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872104] Re: Lenovo x230 fails to get into login mode after reboot - just purple screen or sometimes login w fprint and same purple screen
This is a duplicate of bug #1240336 I resolved it by installing gnome-system-tools and changed my status of group from "custom" to "admin" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1872104 Title: Lenovo x230 fails to get into login mode after reboot - just purple screen or sometimes login w fprint and same purple screen Status in shadow package in Ubuntu: New Bug description: "Fresh" install, /home kept, via "Other " on install from usb Powering off gets me into sleep mode, power button configured to only on/off. More on/off gets real shut down. I have to go through safe mode, and have not found what gets it working. Last time I did all, and had to reboot again, because of same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: login 1:4.8.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 17:48:48 2020 InstallationDate: Installed on 2019-01-14 (451 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832057] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
*** This bug is a duplicate of bug 1829401 *** https://bugs.launchpad.net/bugs/1829401 While having software and updates open, I added a PPA from terminal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1832057 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow Status in software-properties package in Ubuntu: Confirmed Bug description: Falló actualización de repositorios ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.4 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 21:32:02 2019 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2019-06-02 (5 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 75497475 ProcEnviron: LANGUAGE=es_SV:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_SV.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '75497475'] PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow UpgradeStatus: Upgraded to eoan on 2019-06-02 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1832057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I'm HP Spectre x360 Linux amanah 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [*] Laptop speakers work [ ] HDMI output does not work [ ] Internal microphone does not work [*] External microphone works -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]
New error log: Apr 10 22:11:47 xxx dhcpd[3765]: Server starting service. Apr 10 22:11:47 xxx dhcpd[3765]: failover peer dhcp-failover: peer moves from normal to communications-interrupted Apr 10 22:11:47 xxx dhcpd[3765]: failover peer dhcp-failover: I move from startup to normal Apr 10 22:11:47 xxx dhcpd[3765]: balancing pool 561b77e547d0 192.168.1.0/24 total 60 free 27 backup 33 lts 3 max-own (+/-)6 Apr 10 22:11:47 xxx dhcpd[3765]: balanced pool 561b77e547d0 192.168.1.0/24 total 60 free 27 backup 33 lts 3 max-misbal 9 Apr 10 22:11:47 xxx dhcpd[3765]: failover peer dhcp-failover: peer moves from communications-interrupted to normal Apr 10 22:11:47 xxx dhcpd[3765]: failover peer dhcp-failover: Both servers normal Apr 10 22:11:47 xxx sh[3765]: ../../../../lib/isc/unix/socket.c:4359: fatal error: select() failed: Bad file descriptor Apr 10 22:11:47 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 22:11:47 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872106 Title: isc-dhcp-server crashing constantly [Ubuntu 20.04] Status in isc-dhcp package in Ubuntu: Confirmed Bug description: isc-dhcp-server crashing constantly (sometimes within seconds or minutes, sometimes within hours) with the following error messages: Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service. Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ?? Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ?? Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ?? Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ?? Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ?? Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 927828] Re: sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed.
** Changed in: sudo (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/927828 Title: sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed. Status in sudo: Unknown Status in libpam-mount package in Ubuntu: Invalid Status in sudo package in Ubuntu: Fix Released Status in libpam-mount source package in Precise: Invalid Status in sudo source package in Precise: Fix Released Status in sudo package in Debian: Fix Released Bug description: Stable Release Update request [Impact] Pluggable Authentication Module (PAM) pam_open_session() is not called by sudo when a timestamp is still valid (currently 15 minutes) leading to unexpected behaviour and (sometimes hidden) failures of PAM session modules. The issue will affect *all* PAMs although it is revealed by libpam-mount through this assert() causing an Abort. Due to significant code refactoring to support a plug-in architecture upstream between the Oneiric (1.7.4p6) and Precise (1.8.3p1) versions of sudo a hidden bug in sudo's use of the PAM library has been revealed by systems that have libpam-mount installed. This is only installed as a reverse dependency of sadms or else manually to support auto-mounting of user encfs volumes. The issue will affect *all* PAMs. [Development Fix] I reported the bug to upstream sudo and Rob Miller (upstream author) promptly investigated and published a patch against upstream's development tip and the imminent 1.8.5 release candidate. The patch fixes the issue for upstream. [Stable Fix] Backporting the upstream fix required moving patch hunks around to different files to account for the changes since Precise's 1.8.3p1. Although transformed, the patch doesn't add or remove any additional logic - it just accounts for variable name-changes and code that had moved to alternate functions. The patch is on my linked bzr branch. [Test Case] 1. Install libpam-mount 2. Repeatedly run sudo within the default 15 minute timestamp caching window sudo apt-get install libpam-mount sudo echo TEST sudo echo TEST sudo echo TEST [Regression Potential] No regression potential. Returns functional behaviour to that expected by PAMs . --- Original Report --- When running sudo it executes properly the first time during a session but, after credentials are cached, further attempts result in an error: sciri@Rico:~$ sudo id [sudo] password for sciri: uid=0(root) gid=0(root) groups=0(root) sciri@Rico:~$ sudo id uid=0(root) gid=0(root) groups=0(root) sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed. Aborted ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libpam-mount 2.10-2 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 Uname: Linux 3.2.0-14-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CheckboxSubmission: 15c9c9b122c9273f52b28c9a5df794ac CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b Date: Mon Feb 6 14:21:24 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110901) SourcePackage: libpam-mount UpgradeStatus: Upgraded to precise on 2012-02-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/927828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Attachment added: "journalctl -b-1 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5351782/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872176] [NEW] [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 When I'm using certain applications, mostly games, the sound starts breaking randomly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rohan 2393 F pulseaudio /dev/snd/pcmC0D7p: rohan 2393 F...m pulseaudio /dev/snd/controlC1: rohan 2393 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 14:17:58 2020 InstallationDate: Installed on 2018-04-19 (722 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: Apr 11 14:04:57 rohan-work dbus-daemon[884]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 14:04:58 rohan-work dbus-daemon[884]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 14:05:05 rohan-work systemd[1913]: pulseaudio.service: Succeeded. Apr 11 14:05:15 rohan-work systemd[1913]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while UpgradeStatus: Upgraded to focal on 2020-04-02 (8 days ago) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.GR dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M PRO-VD PLUS (MS-7B38) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.GR:bd12/02/2019:svnMicro-StarInternationalCo.,Ltd:pnMS-7B38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VDPLUS(MS-7B38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B38 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1872176 Title: [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 When I'm using certain applications, mostly games, the sound starts breaking randomly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rohan 2393 F pulseaudio /dev/snd/pcmC0D7p: rohan 2393 F...m pulseaudio /dev/snd/controlC1: rohan 2393 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 14:17:58 2020 InstallationDate: Installed on 2018-04-19 (722 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: Apr 11 14:04:57 rohan-work dbus-daemon[884]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 14:04:58 rohan-work dbus-daemon[884]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11
[Touch-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Attachment added: "journalctl -b0 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5351769/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872164] Re: qhd (joined) via hdmi 1.4 not working
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872164 Title: qhd (joined) via hdmi 1.4 not working Status in xorg package in Ubuntu: New Bug description: bought a shiny new QHD screen and connected via hdmi it works in single screen mode and in mirror setup but joining/extending does not. it just stays black. don't know how to troubleshoot besides journal model is Philips 272B8Q resolution 2560 x 1440 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Apr 11 08:18:36 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.3.0-45-generic, x86_64: installed nvidia, 435.21, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0819] Subsystem: Dell GM108M [GeForce MX130] [1028:0819] InstallationDate: Installed on 2020-03-30 (11 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude 5591 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=68c5a16c-e29b-4e94-b10c-a14954bc07f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872164/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872164] [NEW] qhd (joined) via hdmi 1.4 not working
You have been subscribed to a public bug: bought a shiny new QHD screen and connected via hdmi it works in single screen mode and in mirror setup but joining/extending does not. it just stays black. don't know how to troubleshoot besides journal model is Philips 272B8Q resolution 2560 x 1440 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Apr 11 08:18:36 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.3.0-45-generic, x86_64: installed nvidia, 435.21, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0819] Subsystem: Dell GM108M [GeForce MX130] [1028:0819] InstallationDate: Installed on 2020-03-30 (11 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude 5591 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=68c5a16c-e29b-4e94-b10c-a14954bc07f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan performance ubuntu -- qhd (joined) via hdmi 1.4 not working https://bugs.launchpad.net/bugs/1872164 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872159] [NEW] booting with splash hangs when external monitors are connected
You have been subscribed to a public bug: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-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: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- booting with splash hangs when external monitors are connected https://bugs.launchpad.net/bugs/1872159 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used
It also prefers configured key files over smart cards, causing similar issues. Luckily there is a work around for that by adding /dev/null as an identify file in the config, but that's super ugly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1872145 Title: explicit key offered after all agent keys, auth can fail before explicit key used Status in openssh package in Ubuntu: New Bug description: A user creates an ssh key and specifies it on the cmdline with 'ssh -i new_key user@host'. The connection fails with the message "Too many authentication failures" displayed to the user. This would lead the user to believe that they failed to put the public portion of the new key on the destination and it will probably be hard for the average user to debug this. The root of this issue is that the user has a number of keys in ~/.ssh/ registered with their ssh agent. The ssh command is offering each of these keys from the agent to the remote system before trying the explicit key from the command line. There are enough agent keys to reach the failure limit (usually 5 keys) with the remote before they get to the explicit key. The solution today for the user is to head down into the ssh_config man page to find '-o IdentitiesOnly=yes' to skip the agent keys and only use the specified key. But they're unlikely to do this because '-i' in the ssh man page doesn't suggest this and they'd only look for this if they actually understood the root cause of the problem, which is a bit cruel. We should consider changing the order of the keys offered to the remote to use explicit keys first followed by agent keys. It would seem to me that this would honor the users intent of explicitly specifying a key to use. The current order makes this difficult for anyone fielding a user's authentication failure report as they must double check that ssh managed to actually try the key the user specified before it raised an error message about authentication failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp