[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
This bug was fixed in the package evince - 44.1-1ubuntu1 --- evince (44.1-1ubuntu1) mantic; urgency=medium * Allow evince to spawn browsers distributed as snaps (LP: #1794064) - debian/apparmor-profile: include snap-browsers abstracted profile and allow transitions to them in evince -- Georgia Garcia Mon, 05 Jun 2023 16:35:51 -0300 ** Changed in: evince (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Committed Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: In Progress Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: In Progress Status in evince source package in Lunar: In Progress Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1854976] Re: systemd-resolved doesn't work with "host -l" / AXFR queries
The decision to refuse zone transfer requests was in fact deliberate, as described here: https://github.com/systemd/systemd/commit/b30bf55d5c9942f15f27a641c2c34bbb646ec981. Therefore, I think "Won't Fix" is the appropriate resolution here. ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/1854976 Title: systemd-resolved doesn't work with "host -l" / AXFR queries Status in systemd package in Ubuntu: Won't Fix Bug description: Hello, some time ago network-manager in Ubuntu switched from dnsmasq to systemd-resolved. When network-manager used dnsmasq to handle DNS, one could use "host -l" to list all the hosts in a DNS zone, something like this: $ host -l mydomain.lan mydomain.lan name server mydns.mydomain.lan host1.mydomain.lan has address x.x.x.x host2.mydomain.lan has address x.x.x.x host3.mydomain.lan has address x.x.x.x host4.mydomain.lan has address x.x.x.x [...] That, unfortunately, no longer works since the switch to systemd-resolved, it always fails like this: $ host -l mydomain.lan Host mydomain.lan not found: 4(NOTIMP) ; Transfer failed. And I think that's because systemd-resolved is "filtering" the AXFR queries issued by "host -l" (I checked the network traffic with tcdump and that "NOTIMP" comes from the loopback interface). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1854976/+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 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks
The related upstream issue references a PR that was merged upstream 3 years ago: https://github.com/systemd/systemd/issues/3943#issuecomment-625791141. Based on that, I am marking this Fix Released, but please re-open if this is observed on newer releases. ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- 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/1611945 Title: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks Status in systemd package in Ubuntu: Fix Released Bug description: We have a just-installed Ubuntu 16.04 LTS machine with a number of disks behind port-multiplier eSATA ports, all of them driven by a SiI 3124 controller (sata_sil24 kernel driver). Our machine sees all disks on all channels, however under 16.04 only one disk from each channel shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id and /dev/disk/by-uuid). For our usage this is a severe defect because we rotate disks in and out of the external enclosure and rely on mounting specific slots in the external enclosure through /dev/disk/by-path. This did not happen in Ubuntu 12.04 LTS, the release that this machine was previously running. According to 'udevadm info --export-db' and 'udevadm test-builtin path_id' and so on, systemd's udev stuff is assigning all drives behind the same port the same disk/by-path data (ID_PATH et al). In 'udevadm info /sys/block/sdX', the 'P:' and 'E: DEVPATH=' values show a difference in the target portion of PCI path, eg: P: /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda P: /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:1:0/0:1:0:0/block/sdb However the 'S: disk/by-path', 'E: DEVLINKS=', and 'E: ID_PATH' portions do not. For both devices above, we see: S: disk/by-path/pci-:02:00.0-ata-1 E: ID_PATH=pci-:02:00.0-ata-1 Naturally only one device can have a /dev/disk/by- path/pci-:02:00.0-ata-1 symlink, so instead of four disks per channel in /dev/disk/by-path we see one. Ubuntu release: 16.04 Package versions from 'apt-cache policy udev systemd': udev: Installed: 229-4ubuntu7 systemd: Installed: 229-4ubuntu7 'journalctl -b' reports that during boot systemd does report some 'appeared twice with different sysfs paths' notes, eg: Aug 10 13:34:21 verdandi systemd[1]: dev-disk-by\x2dpath- pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk- by\x2dpath-pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:3:0/0:3:0:0/block/sdd/sdd1 and /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 However it doesn't seem to be reporting this for all port-multiplier drives and their partitions. If it would be useful I can attach full 'udevadm info --export-db' output or the like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1611945/+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 1770082] Re: systemd-networkd not renaming devices on boot
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Released
Status in netplan.io source package in Cosmic:
Fix Released
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Bring down interface : 'ip link set dev ens3 down'
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: myiface3: mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
valid_lft 3575sec preferred_lft 3575sec
inet6 fe80::5054:ff:fede:bdf6/64 scope link
valid_lft forever preferred_lft forever
So names are successfully changed with netplan apply.
This seems to be some udev-related timing or priority
[Touch-packages] [Bug 1872015] Re: resolv.conf symlink is broken
That is the correct setting when the stub-resolver is in use, which is the default in Ubuntu. Without further details I cannot know what was broken at the time. I don't think there is any action to take. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1872015 Title: resolv.conf symlink is broken Status in systemd package in Ubuntu: Invalid Bug description: see description here: https://askubuntu.com/a/1041631/436647 *The Default* $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 39 Apr 26 12:07 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf I deleted this and pointed to the correct file. After rebooting, this solved my issue. And I was even able to switch networks on my laptop and the DNS switched correctly. Of course when on external networks I can't resolve any of my local machines but that is expected. As soon as I switch back to my local network, all the local machines resolve correctly because my router is the DNS. - *The Fix* $ sudo rm -f /etc/resolv.conf $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 32 May 29 08:48 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf $ sudo reboot ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Apr 10 07:04:17 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP ProLiant MicroServer Gen8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=2351ab04-e595-4761-ad9d-d2d5975d1b08 ro maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2014 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ06:bd06/06/2014:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant MicroServer Gen8 dmi.product.sku: 712317-421 dmi.sys.vendor: HP mtime.conffile..etc.systemd.resolved.conf: 2020-04-10T06:39:38.172640 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872015/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: apparmor (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: apparmor (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: apparmor (Ubuntu Lunar) Status: Confirmed => In Progress -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Committed Status in evince package in Ubuntu: Fix Committed Status in apparmor source package in Jammy: In Progress Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: In Progress Status in evince source package in Lunar: In Progress Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 2023436] Re: Icons are showing as no entry signs
thanks for the update, closing since it seems like a local issue rather than a gtk bug ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Invalid -- 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/2023436 Title: Icons are showing as no entry signs Status in gtk+3.0 package in Ubuntu: Invalid Bug description: I have tried looking in various places to see why icons aren't showing properly. Checked loads of log messages. Located the icons on the filesystem but for some reason the icons aren't loading. It is intermittent, for example sometimes the battery symbol shows and sometimes it doesn't. A bigger problem is that sometimes the screen goes black but the laptop is still on, the keyboard is still responding but it's impossible to use. Sometimes this happens a few times in an hour. Sometimes it can be days between using it. This is making my laptop pretty unusable. If there is anything I can do to investigate this further then please shout, happy to run all the commands and provide all the logs. I've attached a screenshot showing the issue in the settings panel but that isn't the only place this is happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 10 10:17:48 2023 DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d] InstallationDate: Installed on 2020-07-31 (1043 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9500 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago) dmi.bios.date: 03/16/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2023436/+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
Re: [Touch-packages] [Bug 2023436] Re: Icons are showing as no entry signs
Correction, I ran: sudo /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders --update-cache. I rebooted and all the icons are loading correctly, thank you! I am also applying the driver change which will hopefully resolve my screen issue. If not I will raise a separate bug. I've been putting up with this annoyance for months, thank you for helping me get rid of this problem! Kind regards, Andrew On Mon, 12 Jun 2023 at 19:57, Andrew Perry wrote: > I did some googling and fixed the gnome control centre issue by running: > sudo /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders > > Lots of other images aren't loading yet but I'll restart and see if that > addresses it > > On Mon, 12 Jun 2023 at 19:37, Andrew Perry wrote: > >> This is the output: >> >> (gnome-control-center:9103): Gtk-WARNING **: 19:35:37.672: Could not load >> a pixbuf from /com/ubuntu/themes/Yaru-dark/3.0/assets/bullet-symbolic.svg. >> This may indicate that pixbuf loaders or the mime database could not be >> found. >> >> On Mon, 12 Jun 2023 at 09:31, Andrew Perry wrote: >> >>> Thanks for the replies, you're right about it being a different bug. >>> Should have known better. Will post the results of the command for this bug >>> tonight. >>> >>> Kind regards, >>> Andrew >>> >>> On Mon, 12 Jun 2023, 08:45 Daniel van Vugt, <2023...@bugs.launchpad.net> >>> wrote: >>> The black screen issue you mention should be discussed elsewhere because each bug should only cover a single topic. But that's likely to be caused by the open source 'nouveau' driver. So please open the 'Additional Drivers' app to install a supported NVIDIA driver to avoid that. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/2023436 Title: Icons are showing as no entry signs Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I have tried looking in various places to see why icons aren't showing properly. Checked loads of log messages. Located the icons on the filesystem but for some reason the icons aren't loading. It is intermittent, for example sometimes the battery symbol shows and sometimes it doesn't. A bigger problem is that sometimes the screen goes black but the laptop is still on, the keyboard is still responding but it's impossible to use. Sometimes this happens a few times in an hour. Sometimes it can be days between using it. This is making my laptop pretty unusable. If there is anything I can do to investigate this further then please shout, happy to run all the commands and provide all the logs. I've attached a screenshot showing the issue in the settings panel but that isn't the only place this is happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 10 10:17:48 2023 DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d] InstallationDate: Installed on 2020-07-31 (1043 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9500 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago) dmi.bios.date: 03/16/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D:
Re: [Touch-packages] [Bug 2023436] Re: Icons are showing as no entry signs
I did some googling and fixed the gnome control centre issue by running: sudo /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders Lots of other images aren't loading yet but I'll restart and see if that addresses it On Mon, 12 Jun 2023 at 19:37, Andrew Perry wrote: > This is the output: > > (gnome-control-center:9103): Gtk-WARNING **: 19:35:37.672: Could not load > a pixbuf from /com/ubuntu/themes/Yaru-dark/3.0/assets/bullet-symbolic.svg. > This may indicate that pixbuf loaders or the mime database could not be > found. > > On Mon, 12 Jun 2023 at 09:31, Andrew Perry wrote: > >> Thanks for the replies, you're right about it being a different bug. >> Should have known better. Will post the results of the command for this bug >> tonight. >> >> Kind regards, >> Andrew >> >> On Mon, 12 Jun 2023, 08:45 Daniel van Vugt, <2023...@bugs.launchpad.net> >> wrote: >> >>> The black screen issue you mention should be discussed elsewhere because >>> each bug should only cover a single topic. But that's likely to be >>> caused by the open source 'nouveau' driver. So please open the >>> 'Additional Drivers' app to install a supported NVIDIA driver to avoid >>> that. >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/2023436 >>> >>> Title: >>> Icons are showing as no entry signs >>> >>> Status in gtk+3.0 package in Ubuntu: >>> Incomplete >>> >>> Bug description: >>> I have tried looking in various places to see why icons aren't showing >>> properly. Checked loads of log messages. Located the icons on the >>> filesystem but for some reason the icons aren't loading. It is >>> intermittent, for example sometimes the battery symbol shows and >>> sometimes it doesn't. >>> >>> A bigger problem is that sometimes the screen goes black but the >>> laptop is still on, the keyboard is still responding but it's >>> impossible to use. Sometimes this happens a few times in an hour. >>> Sometimes it can be days between using it. >>> >>> This is making my laptop pretty unusable. If there is anything I can >>> do to investigate this further then please shout, happy to run all the >>> commands and provide all the logs. I've attached a screenshot showing >>> the issue in the settings panel but that isn't the only place this is >>> happening. >>> >>> ProblemType: Bug >>> DistroRelease: Ubuntu 22.04 >>> Package: xorg 1:7.7+23ubuntu2 >>> ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 >>> Uname: Linux 5.19.0-43-generic x86_64 >>> ApportVersion: 2.20.11-0ubuntu82.5 >>> Architecture: amd64 >>> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >>> CasperMD5CheckResult: unknown >>> CompositorRunning: None >>> CurrentDesktop: ubuntu:GNOME >>> Date: Sat Jun 10 10:17:48 2023 >>> DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed, >>> re-reading >>> DistroCodename: jammy >>> DistroVariant: ubuntu >>> ExtraDebuggingInterest: Yes, including running git bisection searches >>> GraphicsCard: >>>Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) >>> (prog-if 00 [VGA controller]) >>> Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d] >>> Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d] >>> InstallationDate: Installed on 2020-07-31 (1043 days ago) >>> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 >>> (20200423) >>> MachineType: Dell Inc. XPS 15 9500 >>> ProcEnviron: >>>LANGUAGE=en_GB:en >>>PATH=(custom, no user) >>>XDG_RUNTIME_DIR= >>>LANG=en_GB.UTF-8 >>>SHELL=/bin/bash >>> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic >>> root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7 >>> SourcePackage: xorg >>> Symptom: display >>> UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago) >>> dmi.bios.date: 03/16/2023 >>> dmi.bios.release: 1.22 >>> dmi.bios.vendor: Dell Inc. >>> dmi.bios.version: 1.22.0 >>> dmi.board.name: 05XYW7 >>> dmi.board.vendor: Dell Inc. >>> dmi.board.version: A00 >>> dmi.chassis.type: 10 >>> dmi.chassis.vendor: Dell Inc. >>> dmi.modalias: >>> dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: >>> dmi.product.family: XPS >>> dmi.product.name: XPS 15 9500 >>> dmi.product.sku: 097D >>> dmi.sys.vendor: Dell Inc. >>> version.compiz: compiz N/A >>> version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 >>> version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 >>> version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 >>> version.xserver-xorg-core: xserver-xorg-core >>> 2:21.1.4-2ubuntu1.7~22.04.1 >>> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A >>> version.xserver-xorg-video-ati: xserver-xorg-video-ati >>> 1:19.1.0-2ubuntu1 >>>
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu Lunar) Status: Confirmed => In Progress ** Changed in: evince (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: evince (Ubuntu) Assignee: James Henstridge (jamesh) => (unassigned) ** Changed in: evince (Ubuntu Lunar) Importance: Undecided => High -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Fix Committed Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in apparmor source package in Lunar: Confirmed Status in evince source package in Lunar: In Progress Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Also affects: evince (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: evince (Ubuntu Lunar) Status: New => Confirmed ** Changed in: apparmor (Ubuntu Lunar) Status: New => Confirmed -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Confirmed Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in apparmor source package in Lunar: Confirmed Status in evince source package in Lunar: Confirmed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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
Re: [Touch-packages] [Bug 2023436] Re: Icons are showing as no entry signs
This is the output: (gnome-control-center:9103): Gtk-WARNING **: 19:35:37.672: Could not load a pixbuf from /com/ubuntu/themes/Yaru-dark/3.0/assets/bullet-symbolic.svg. This may indicate that pixbuf loaders or the mime database could not be found. On Mon, 12 Jun 2023 at 09:31, Andrew Perry wrote: > Thanks for the replies, you're right about it being a different bug. > Should have known better. Will post the results of the command for this bug > tonight. > > Kind regards, > Andrew > > On Mon, 12 Jun 2023, 08:45 Daniel van Vugt, <2023...@bugs.launchpad.net> > wrote: > >> The black screen issue you mention should be discussed elsewhere because >> each bug should only cover a single topic. But that's likely to be >> caused by the open source 'nouveau' driver. So please open the >> 'Additional Drivers' app to install a supported NVIDIA driver to avoid >> that. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/2023436 >> >> Title: >> Icons are showing as no entry signs >> >> Status in gtk+3.0 package in Ubuntu: >> Incomplete >> >> Bug description: >> I have tried looking in various places to see why icons aren't showing >> properly. Checked loads of log messages. Located the icons on the >> filesystem but for some reason the icons aren't loading. It is >> intermittent, for example sometimes the battery symbol shows and >> sometimes it doesn't. >> >> A bigger problem is that sometimes the screen goes black but the >> laptop is still on, the keyboard is still responding but it's >> impossible to use. Sometimes this happens a few times in an hour. >> Sometimes it can be days between using it. >> >> This is making my laptop pretty unusable. If there is anything I can >> do to investigate this further then please shout, happy to run all the >> commands and provide all the logs. I've attached a screenshot showing >> the issue in the settings panel but that isn't the only place this is >> happening. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 22.04 >> Package: xorg 1:7.7+23ubuntu2 >> ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 >> Uname: Linux 5.19.0-43-generic x86_64 >> ApportVersion: 2.20.11-0ubuntu82.5 >> Architecture: amd64 >> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >> CasperMD5CheckResult: unknown >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Sat Jun 10 10:17:48 2023 >> DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed, >> re-reading >> DistroCodename: jammy >> DistroVariant: ubuntu >> ExtraDebuggingInterest: Yes, including running git bisection searches >> GraphicsCard: >>Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) >> (prog-if 00 [VGA controller]) >> Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d] >> Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d] >> InstallationDate: Installed on 2020-07-31 (1043 days ago) >> InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 >> (20200423) >> MachineType: Dell Inc. XPS 15 9500 >> ProcEnviron: >>LANGUAGE=en_GB:en >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_GB.UTF-8 >>SHELL=/bin/bash >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic >> root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7 >> SourcePackage: xorg >> Symptom: display >> UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago) >> dmi.bios.date: 03/16/2023 >> dmi.bios.release: 1.22 >> dmi.bios.vendor: Dell Inc. >> dmi.bios.version: 1.22.0 >> dmi.board.name: 05XYW7 >> dmi.board.vendor: Dell Inc. >> dmi.board.version: A00 >> dmi.chassis.type: 10 >> dmi.chassis.vendor: Dell Inc. >> dmi.modalias: >> dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: >> dmi.product.family: XPS >> dmi.product.name: XPS 15 9500 >> dmi.product.sku: 097D >> dmi.sys.vendor: Dell Inc. >> version.compiz: compiz N/A >> version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 >> version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 >> version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 >> version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 >> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A >> version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 >> version.xserver-xorg-video-intel: xserver-xorg-video-intel >> 2:2.99.917+git20210115-1 >> version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau >> 1:1.0.17-2build1 >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2023436/+subscriptions >> >> -- You received this bug notification because you are a member of Ubuntu Touch seeded
[Touch-packages] [Bug 1250875] Re: Lightdm sometimes fails to auto login
I confirm the same problem Xubuntu 22.04.1. Ligthdm version: 1.30.0-0ubuntu5 -- 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/1250875 Title: Lightdm sometimes fails to auto login Status in lightdm package in Ubuntu: Confirmed Bug description: Using ubuntu 14.04 and sometimes when I boot into ubuntu lightdm fails to auto login, and I must login manually in the unity greeter. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 Date: Wed Nov 13 14:33:18 2013 InstallationDate: Installed on 2013-10-10 (33 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-11-04 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu) Status: Incomplete => Confirmed ** Changed in: evince (Ubuntu Jammy) Status: Incomplete => Confirmed -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Confirmed Status in apparmor source package in Jammy: Confirmed Status in evince source package in Jammy: Confirmed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 2023580] [NEW] Touchscreen just works with Pen
Public bug reported: I have a Lenovo Yoga 730 and use the "active Pen 2". Everything worked fine with the previous Version of Ubuntu. Since i installed 23.04, i got some Problems. At the beginnig my Pen doesnt worked correctly. I solved this Problem with some Updates. After that i once changed to xorg and then came back to wayland. Nw in both of them, my Touchscreen just works with the Stylus and not with my fingers anymore, which is really annoiing. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 12 20:00:06 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:39fe] InstallationDate: Installed on 2023-05-11 (32 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 81JR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.6-060306-generic root=UUID=5288c76f-982f-4f19-a751-1f28abac1f9f ro quiet splash resume=UUID=e07eea5d-7392-4dd3-bf67-4162e5574848 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 2.21 dmi.bios.vendor: LENOVO dmi.bios.version: 9NCN21WW(V2.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 730-13IWL dmi.ec.firmware.release: 2.21 dmi.modalias: dmi:bvnLENOVO:bvr9NCN21WW(V2.06):bd12/25/2020:br2.21:efr2.21:svnLENOVO:pn81JR:pvrLenovoYOGA730-13IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA730-13IWL:skuLENOVO_MT_81JR_BU_idea_FM_YOGA730-13IWL: dmi.product.family: YOGA 730-13IWL dmi.product.name: 81JR dmi.product.sku: LENOVO_MT_81JR_BU_idea_FM_YOGA 730-13IWL dmi.product.version: Lenovo YOGA 730-13IWL dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu wayland-session -- 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/2023580 Title: Touchscreen just works with Pen Status in xorg package in Ubuntu: New Bug description: I have a Lenovo Yoga 730 and use the "active Pen 2". Everything worked fine with the previous Version of Ubuntu. Since i installed 23.04, i got some Problems. At the beginnig my Pen doesnt worked correctly. I solved this Problem with some Updates. After that i once changed to xorg and then came back to wayland. Nw in both of them, my Touchscreen just works with the Stylus and not with my fingers anymore, which is really annoiing. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.3.6-060306-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 12 20:00:06 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:39fe] InstallationDate: Installed on 2023-05-11 (32 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 81JR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.6-060306-generic root=UUID=5288c76f-982f-4f19-a751-1f28abac1f9f ro quiet splash resume=UUID=e07eea5d-7392-4dd3-bf67-4162e5574848 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 2.21 dmi.bios.vendor: LENOVO dmi.bios.version:
[Touch-packages] [Bug 2020177] Re: Leaking sessions in pam_systemd
Can you please attach logs from a boot where this was seen? If the current boot exhibits this, you can use 0 as the boot id: $ journalctl -u systemd-logind.service -b $boot_id > systemd-logind- logs.txt -- 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/2020177 Title: Leaking sessions in pam_systemd Status in systemd package in Ubuntu: Incomplete Bug description: May 19 12:38:38 s20.wr0.ru sshd[3793128]: pam_systemd(sshd:session): Failed to create session: Maximum number of sessions (8192) reached, refusing further sessions. # loginctl list-sessions|wc -l 8195 # loginctl session-status 302548700 302548700 - topaz (450) Since: Tue 2022-10-18 09:29:02; 7 months 0 days ago Leader: 2637625 Remote: 92.42.15.122 Service: sshd; type tty; class user State: closing Unit: session-302548700.scope # ps axf|wc -l 72 The only way I could figure to fix this is to reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.21 Uname: Linux 4.15.0 x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDmesg: Date: Fri May 19 12:58:47 2023 Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 TERM=xterm-256color PATH=(custom, no user) ProcInterrupts: Error: [Errno 2] No such file or directory: '/proc/interrupts' ProcKernelCmdLine: quiet SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2022-01-26 (478 days ago) acpidump: mtime.conffile..etc.systemd.journald.conf: 2022-08-19T16:13:27.570934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2020177/+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 2020177] Re: Leaking sessions in pam_systemd
Well. I don't see any processes in the OS that would correspond to those sessions. The state of most of them is Closing. systemd also spams a lot about too many sessions. Looks like systemd doesn't close sessions properly. -- 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/2020177 Title: Leaking sessions in pam_systemd Status in systemd package in Ubuntu: Incomplete Bug description: May 19 12:38:38 s20.wr0.ru sshd[3793128]: pam_systemd(sshd:session): Failed to create session: Maximum number of sessions (8192) reached, refusing further sessions. # loginctl list-sessions|wc -l 8195 # loginctl session-status 302548700 302548700 - topaz (450) Since: Tue 2022-10-18 09:29:02; 7 months 0 days ago Leader: 2637625 Remote: 92.42.15.122 Service: sshd; type tty; class user State: closing Unit: session-302548700.scope # ps axf|wc -l 72 The only way I could figure to fix this is to reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.21 Uname: Linux 4.15.0 x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDmesg: Date: Fri May 19 12:58:47 2023 Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 TERM=xterm-256color PATH=(custom, no user) ProcInterrupts: Error: [Errno 2] No such file or directory: '/proc/interrupts' ProcKernelCmdLine: quiet SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2022-01-26 (478 days ago) acpidump: mtime.conffile..etc.systemd.journald.conf: 2022-08-19T16:13:27.570934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2020177/+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 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status
** Tags added: rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1980991 Title: /usr/sbin/on_ac_power incorrectly reporting ac power status Status in powermgmt-base package in Ubuntu: Triaged Status in powermgmt-base source package in Kinetic: Triaged Bug description: Good afternoon, folks. I believe I discovered a bug in the /usr/sbin/on_ac_power script. I have a Dell OptiPlex 5090 host that has an entry in /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe this is the USB-C power delivery port on the front of the chassis. The issue I'm encountering is that /usr/sbin/on_ac_power is exiting with code 1 which states: (1 (false) if not on AC power) when that isn't the case. This looks to be because of the ucsi-source-psy-USBC000:001 entry reporting the "online" status as 0, presumably because nothing is currently connected to that USB-C port. This causes /usr/sbin/on_ac_power to incorrectly report that the machine isn't connected to AC power and causes other utilities like unattended-upgrades to quit when using the default configuration since it believes the machine isn't connected to AC power. There is a workaround with unattended-upgrades where you can specify it to run regardless of if AC power is connected, but as more and more chassis implement power-delivery USB-C ports I foresee this becoming more of an issue. I'm not sure if it's anything to look into, but I figured I would share my findings. Please let me know if you have any questions or if I can provide any additional information, troubleshooting, or testing. Thanks! -Kevin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 2019026] Re: systemd /tmp cleaning is suboptimal
> how would it impact you if it was NOT cleaned at reboot? I just like it. It's easier for me to keep track in my head that "oh, this file in /tmp will only be around until I reboot", as opposed to trying to keep track of the actual age of a file. To be clear, I am not suggesting that my use case is strong argument for keeping the current default (I will happily write an /etc/tmpfiles.d/tmp.conf drop-in to meet my preference if needed). Just pointing out that there might be a range of preferences on the default handling of /tmp. Also, you may have already come across this, but if not, this is the Debian bug that resulted in the current default: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675422. If you think it would be best for most Ubuntu users to change the current default, then we should go with your suggested change. If the motivation is mostly about your schroot use case, then I would suggest either modifying schroot to do what you need, or using /etc/tmpfiles.d/tmp.conf. ** Bug watch added: Debian Bug tracker #675422 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675422 -- 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/2019026 Title: systemd /tmp cleaning is suboptimal Status in systemd package in Ubuntu: New Bug description: Historically on Debian and Ubuntu, before systemd, the default handling of /tmp was to periodically, and at boot, remove all files/directories older than 30 days; and leave other contents alone. With the move to systemd, the "default" (really, hard-coded in /usr/lib/tmpfiles.d/tmp.conf) is to not clean /tmp periodically, but at boot to remove all contents. This is suboptimal for two reasons. By cleaning /tmp *only* at boot, if a system makes heavy use of /tmp and has lots of inodes under it, possibly due to failures of some process to clean up after itself, at boot the system will be unavailable for an unnecessarily long time while these files are removed. By cleaning *all* files under /tmp, this makes a reboot an Event where in-progress files may be unnecessarily lost. While the FHS does not *guarantee* that files under /tmp will persist across boot (because /tmp may be a tmpfs), it also does not *require* that /tmp be cleared on boot. Although data stored in /tmp may be deleted in a site-specific manner, it is recommended that files and directories located in /tmp be deleted whenever the system is booted. FHS added this recommendation on the basis of historical precedent and common practice, but did not make it a requirement because system administration is not within the scope of this standard. I therefore believe the correct value for /usr/lib/tmpfiles.d/tmp.conf to restore past behavior is 'd /tmp 1777 root root 30d'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2019026/+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 2023536] Re: package sysv-rc (not installed) failed to install/upgrade: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62
sysv-rc 2.88dsf-41ubuntu6 is not part of Ubuntu 22.04. It is part of Ubuntu *14*.04, which is 9 years old - old enough that the transitional Replaces: field from init-system-helpers to sysv-rc has been dropped. Installing Ubuntu 14.04 packages on Ubuntu 22.04 is not supported. ** Changed in: sysvinit (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/2023536 Title: package sysv-rc (not installed) failed to install/upgrade: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init- system-helpers 1.62 Status in sysvinit package in Ubuntu: Won't Fix Bug description: when i install vscode. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: sysv-rc (not installed) ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: sysv-rc:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 12 16:15:46 2023 DpkgTerminalLog: Preparing to unpack .../sysv-rc_2.88dsf-41ubuntu6_all.deb ... Unpacking sysv-rc (2.88dsf-41ubuntu6) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/sysv-rc_2.88dsf-41ubuntu6_all.deb (--unpack): trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62 ErrorMessage: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62 InstallationDate: Installed on 2023-05-13 (30 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: sysvinit Title: package sysv-rc (not installed) failed to install/upgrade: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2023536/+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 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate
** Package changed: linux (Ubuntu) => openssl (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: openssl (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Changed in: openssl (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2023545 Title: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate Status in Ubuntu on IBM z Systems: New Status in openssl package in Ubuntu: New Bug description: ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024 Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not tainted 5.15.0-73-generic #80-Ubuntu Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0) Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708 Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:0 PM:0 RI:0 EA:3 Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 02aa3289f9d0 Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 02aa328a4300 Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 02aa03ff Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 03ffae437c22 03ffec2fe000 Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2 lgr%r11,%r2 03ffae11c700: 4700bc0,0 #03ffae11c704: b24f00a0ear%r10,%a0 >03ffae11c708: 58102018l%r1,24(%r2) 03ffae11c70c: ebaa002dsllg%r10,%r10,32 03ffae11c712: b24f00a1ear%r10,%a1 03ffae11c716: 5910a0d0c%r1,208(%r10) 03ffae11c71a: a7840033brc8,03ffae11c780 Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address: Jun 07 13:06:08 SYSTEM kernel: [<03ffae33242c>] 0x3ffae33242c Jun 07 13:06:08 SYSTEM systemd[1]: Started Process Core Dump (PID 2345/UID 0). Jun 07 13:06:08 SYSTEM systemd-coredump[2350]: Process 2344 (openssl) of user 0 dumped core. Found module linux-vdso64.so.1 with build-id: bcfab8ac8dbd44c758c3c5494e2952db16905d2e Found module libica.so.4 with build-id: 0cc5ace50644dfba6d0ecf4f783477cd04a55731 Found module ibmca.so with build-id: 27daaf0ed1857fdad3761c2b3db21020999eee08 Found module ld64.so.1 with build-id: 31d4856f0ba9ea058c91a34f4d684ae0fe01964c Found module libc.so.6 with build-id: 74250317950da91d3345f258cb2dd12d22c3f2e5 Found module libcrypto.so.3 with build-id: a27f20e6cf293f214d459530ce2c0b2b52fdbdb4 Found module libssl.so.3 with build-id: e2c031c3dac06b5ce43bdea022aee7989f78dde4 Found module openssl with build-id: ed0fe325182e99d135ee6b08e6d90a9d1c42af7f Stack trace of thread 2344:
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
What's the status of keepalived in Mantic on this bug?
** Tags added: server-triage-discuss
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Triaged
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Won't Fix
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Fix Released
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
vrrp_mcast_group6 ff02::12 # optional, default ff02::12
enable_traps # enable SNMP traps
}
vrrp_sync_group collection {
group {
[Touch-packages] [Bug 2015355] Update Released
The verification of the Stable Release Update for util-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2015355 Title: Please backport patches for false atari partition detection to Ubuntu 20.04 Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Focal: Fix Released Bug description: [Impact] The partition detection logic in libblkid1 can falsely report the presence of an atari partition. One place where this has a practical impact is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441). [Test Plan] * Create a new qcow2 disk image: $ qemu-img create -f qcow2 test.img 20G * Boot a focal ISO with QEMU/KVM as if installing to test.img: $ qemu-system-x86_64 -enable-kvm -m 4096 -name test -drive file=test.img,format=qcow2 -net nic,model=virtio -net user,hostfwd=tcp::1022-:22 -vga virtio -cdrom ubuntu-20.04.6-desktop- amd64.iso * Using the live environment, format the empty disk. These particular commands were given as a reproducer on the upstream bug report (https://github.com/util-linux/util-linux/issues/1116). $ parted -s /dev/sda -- mklabel msdos $ parted -s /dev/sda -- mkpart primary 0% 10% mkpart primary 10% 30% * Run wipefs on /dev/sda to list partitions. On an affected machine, an atari partition will be listed. On a fixed machine, the incorrect atari listing will be gone. $ wipefs /dev/sda DEVICE OFFSET TYPE UUID LABEL sda0x1fe dos sda0x1d2 atari [Where problems could occur] These patches specifically address the atari prober logic in libblkid. Therefore, if we saw regressions it would be related to detecting atari partitions with libblkid. This would potentially impact tools such as wipefs and blkid, or any other tool that uses libblkid1 for this purpose. [Original Description] There are three patches in util-linux upstream that were released in util-linux 2.37 and prevent false detection of the atari partition table with blkid and wipefs. We see this mostly on LUKS devices initialised via luksFormat reporting there is an atari partition table on the device when it is empty. This causes issues in various places, but one key example for us is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441) RedHat backported these fixes to RHEL 8 under https://bugzilla.redhat.com/show_bug.cgi?id=2060030 and it would be helpful if Ubuntu also backported them to Ubuntu 20.04 which is still running util-linux 2.34 The request is to backport patches based on the https://github.com/util-linux/util-linux/issues/1159 upstream report. Upstream commits to cherry-pick the changes to libblkid/src/partitions/atari.c from: 2cc76d50d7a14bef8e7b07fab11b26c9e49d36a2 282ceadc3a72fc07dd0388b8880fd751490bb87f c70b4f2a5b99876d230b8f4f413c3bb3ee6647f1 # lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.6 LTS Release:20.04 Codename: focal # blkid -V blkid from util-linux 2.34 (libblkid 2.34.0, 14-Jun-2019) # blkid -p -s TYPE -s PTTYPE -o export /dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted DEVNAME=dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted PTTYPE=atari # lsblk ... sdccrypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-3600a09803830474a735d4c63744c4a56crypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2015355/+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 2015355] Re: Please backport patches for false atari partition detection to Ubuntu 20.04
This bug was fixed in the package util-linux - 2.34-0.1ubuntu9.4 --- util-linux (2.34-0.1ubuntu9.4) focal; urgency=medium * Fix false atari partition detection (LP: #2015355): - Backport upstream patches to fix atari partition detection in libblkid: + debian/patches/libblkid-fix-Atari-prober-logic.patch + debian/patches/libblkid-make-Atari-more-robust.patch - Backport upstream patches to fix atari tests: + debian/patches/tests-update-atari-partx-tests.patch + debian/patches/tests-update-atari-blkid-tests.patch + debian/source/include-binaries: Track changes that are not representable in quilt patch. -- Nick Rosbrook Tue, 30 May 2023 11:42:35 -0400 ** Changed in: util-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2015355 Title: Please backport patches for false atari partition detection to Ubuntu 20.04 Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Focal: Fix Released Bug description: [Impact] The partition detection logic in libblkid1 can falsely report the presence of an atari partition. One place where this has a practical impact is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441). [Test Plan] * Create a new qcow2 disk image: $ qemu-img create -f qcow2 test.img 20G * Boot a focal ISO with QEMU/KVM as if installing to test.img: $ qemu-system-x86_64 -enable-kvm -m 4096 -name test -drive file=test.img,format=qcow2 -net nic,model=virtio -net user,hostfwd=tcp::1022-:22 -vga virtio -cdrom ubuntu-20.04.6-desktop- amd64.iso * Using the live environment, format the empty disk. These particular commands were given as a reproducer on the upstream bug report (https://github.com/util-linux/util-linux/issues/1116). $ parted -s /dev/sda -- mklabel msdos $ parted -s /dev/sda -- mkpart primary 0% 10% mkpart primary 10% 30% * Run wipefs on /dev/sda to list partitions. On an affected machine, an atari partition will be listed. On a fixed machine, the incorrect atari listing will be gone. $ wipefs /dev/sda DEVICE OFFSET TYPE UUID LABEL sda0x1fe dos sda0x1d2 atari [Where problems could occur] These patches specifically address the atari prober logic in libblkid. Therefore, if we saw regressions it would be related to detecting atari partitions with libblkid. This would potentially impact tools such as wipefs and blkid, or any other tool that uses libblkid1 for this purpose. [Original Description] There are three patches in util-linux upstream that were released in util-linux 2.37 and prevent false detection of the atari partition table with blkid and wipefs. We see this mostly on LUKS devices initialised via luksFormat reporting there is an atari partition table on the device when it is empty. This causes issues in various places, but one key example for us is in kubernetes where mount-utils will refuse to format the device (https://github.com/kubernetes/mount- utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441) RedHat backported these fixes to RHEL 8 under https://bugzilla.redhat.com/show_bug.cgi?id=2060030 and it would be helpful if Ubuntu also backported them to Ubuntu 20.04 which is still running util-linux 2.34 The request is to backport patches based on the https://github.com/util-linux/util-linux/issues/1159 upstream report. Upstream commits to cherry-pick the changes to libblkid/src/partitions/atari.c from: 2cc76d50d7a14bef8e7b07fab11b26c9e49d36a2 282ceadc3a72fc07dd0388b8880fd751490bb87f c70b4f2a5b99876d230b8f4f413c3bb3ee6647f1 # lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 20.04.6 LTS Release:20.04 Codename: focal # blkid -V blkid from util-linux 2.34 (libblkid 2.34.0, 14-Jun-2019) # blkid -p -s TYPE -s PTTYPE -o export /dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted DEVNAME=dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted PTTYPE=atari # lsblk ... sdccrypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-3600a09803830474a735d4c63744c4a56crypto_LUKS a79d2982-74f2-44c7-bb29-460768ebfe64 `-pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2015355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1991919] Re: libgoogle-glog-dev has unmet dependencies due to libunwind
Any workaround for this? I just tried and this still reproduces. For example, you cannot install both libc++-dev and libgoogle-glog-dev due to this: apt install libc++-dev libgoogle-glog-dev Interestingly, for me this only happens on x86_64. On the arm version of the libgoogle-glog-dev package does not depend on libunwind: ``` $ apt show libgoogle-glog-dev Package: libgoogle-glog-dev Version: 0.5.0+really0.4.0-2 Priority: optional Section: universe/libdevel Source: google-glog Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Laszlo Boszormenyi (GCS) Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 383 kB Depends: libgoogle-glog0v5 (= 0.5.0+really0.4.0-2), libgflags-dev Homepage: https://github.com/google/glog Download-Size: 91.7 kB APT-Manual-Installed: yes APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages Description: library that implements application-level logging. ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to google-glog in Ubuntu. https://bugs.launchpad.net/bugs/1991919 Title: libgoogle-glog-dev has unmet dependencies due to libunwind Status in google-glog package in Ubuntu: Confirmed Status in libunwind package in Ubuntu: Confirmed Bug description: # Error Description Installing `libgoogle-glog-dev` results in an error: ``` $ sudo apt install libgoogle-glog-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libunwind-14-dev : Breaks: libunwind-dev but 1.3.2-2build2 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ``` # Comments I have the packages libc++-14-dev and libc++-dev installed. The package libgoogle-glog-dev dependes on "libunwind-dev | libunwind7-dev". But Package 'libunwind7-dev' has no installation candidate. Package 'libunwind-dev' is incompatible with libc++-14-dev and libc++-dev: ``` $ sudo apt install libunwind-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libc++-14-dev libc++-dev libunwind-14-dev The following NEW packages will be installed: libunwind-dev 0 upgraded, 1 newly installed, 3 to remove and 14 not upgraded. Need to get 0 B/1.882 kB of archives. After this operation, 3.176 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. ``` # Additional information: $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ apt-cache policy libgoogle-glog-dev libgoogle-glog-dev: Installed: (none) Candidate: 0.5.0+really0.4.0-2 Version table: 0.5.0+really0.4.0-2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages $ apt show libgoogle-glog-dev Package: libgoogle-glog-dev Version: 0.5.0+really0.4.0-2 Priority: optional Section: universe/libdevel Source: google-glog Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Laszlo Boszormenyi (GCS) Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 388 kB Depends: libgoogle-glog0v5 (= 0.5.0+really0.4.0-2), libgflags-dev, libunwind-dev | libunwind7-dev Homepage: https://github.com/google/glog Download-Size: 91,9 kB APT-Sources: http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages Description: library that implements application-level logging. This library provides logging APIs based on C++-style streams and various helper macros. . This package contains static and debug libraries and header files for developing applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-glog/+bug/1991919/+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 2017420] Update Released
The verification of the Stable Release Update for libheif has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Invalid Status in gdk-pixbuf package in Ubuntu: Invalid Status in libheif package in Ubuntu: Fix Released Status in eog source package in Lunar: Invalid Status in gdk-pixbuf source package in Lunar: Invalid Status in libheif source package in Lunar: Fix Released Bug description: * Impact The libheif loader is bailing out due to a missing plugin directory which leads to image viewer as eog not being able to open pictures in that format anymore * Testcase Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog * Where problems could occur The package build is using the option to not split the codec in separate plugins but the version of Lunar doesn't handle the missing plugins directory and bails out. The code of the version in mantic has been refactored in a way which fixes this problem. For lunar it's easier to just create the directory. The directory is included in the libheif1 binary but that should not create any conflict, it's a temporary situation for lunar only and even if the soname changed dpkg allows for several deb packages to provide the same directory. -- In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+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 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore
This bug was fixed in the package libheif - 1.14.2-1ubuntu1 --- libheif (1.14.2-1ubuntu1) lunar; urgency=medium * debian/libheif1.dirs: - create the plugins directory, if it's missing the loader is bailing out. Fix opening of heif files in eog (lp: #2017420) -- Sebastien Bacher Thu, 01 Jun 2023 11:31:10 +0200 ** Changed in: libheif (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Invalid Status in gdk-pixbuf package in Ubuntu: Invalid Status in libheif package in Ubuntu: Fix Released Status in eog source package in Lunar: Invalid Status in gdk-pixbuf source package in Lunar: Invalid Status in libheif source package in Lunar: Fix Released Bug description: * Impact The libheif loader is bailing out due to a missing plugin directory which leads to image viewer as eog not being able to open pictures in that format anymore * Testcase Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog * Where problems could occur The package build is using the option to not split the codec in separate plugins but the version of Lunar doesn't handle the missing plugins directory and bails out. The code of the version in mantic has been refactored in a way which fixes this problem. For lunar it's easier to just create the directory. The directory is included in the libheif1 binary but that should not create any conflict, it's a temporary situation for lunar only and even if the soname changed dpkg allows for several deb packages to provide the same directory. -- In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+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
Re: [Touch-packages] [Bug 2023436] Re: Icons are showing as no entry signs
Thanks for the replies, you're right about it being a different bug. Should have known better. Will post the results of the command for this bug tonight. Kind regards, Andrew On Mon, 12 Jun 2023, 08:45 Daniel van Vugt, <2023...@bugs.launchpad.net> wrote: > The black screen issue you mention should be discussed elsewhere because > each bug should only cover a single topic. But that's likely to be > caused by the open source 'nouveau' driver. So please open the > 'Additional Drivers' app to install a supported NVIDIA driver to avoid > that. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2023436 > > Title: > Icons are showing as no entry signs > > Status in gtk+3.0 package in Ubuntu: > Incomplete > > Bug description: > I have tried looking in various places to see why icons aren't showing > properly. Checked loads of log messages. Located the icons on the > filesystem but for some reason the icons aren't loading. It is > intermittent, for example sometimes the battery symbol shows and > sometimes it doesn't. > > A bigger problem is that sometimes the screen goes black but the > laptop is still on, the keyboard is still responding but it's > impossible to use. Sometimes this happens a few times in an hour. > Sometimes it can be days between using it. > > This is making my laptop pretty unusable. If there is anything I can > do to investigate this further then please shout, happy to run all the > commands and provide all the logs. I've attached a screenshot showing > the issue in the settings panel but that isn't the only place this is > happening. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: xorg 1:7.7+23ubuntu2 > ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 > Uname: Linux 5.19.0-43-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.5 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: unknown > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat Jun 10 10:17:48 2023 > DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed, > re-reading > DistroCodename: jammy > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) > (prog-if 00 [VGA controller]) > Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d] > Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d] > InstallationDate: Installed on 2020-07-31 (1043 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: Dell Inc. XPS 15 9500 > ProcEnviron: >LANGUAGE=en_GB:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_GB.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic > root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago) > dmi.bios.date: 03/16/2023 > dmi.bios.release: 1.22 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.22.0 > dmi.board.name: 05XYW7 > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: > dmi.product.family: XPS > dmi.product.name: XPS 15 9500 > dmi.product.sku: 097D > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20210115-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.17-2build1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2023436/+subscriptions > > -- 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/2023436 Title: Icons are showing as no entry signs Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I have tried looking in various places to see why icons aren't showing properly. Checked loads of log messages. Located the icons on the filesystem but for some reason the icons aren't loading. It is intermittent,
[Touch-packages] [Bug 2023536] [NEW] package sysv-rc (not installed) failed to install/upgrade: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62
Public bug reported: when i install vscode. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: sysv-rc (not installed) ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: sysv-rc:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 12 16:15:46 2023 DpkgTerminalLog: Preparing to unpack .../sysv-rc_2.88dsf-41ubuntu6_all.deb ... Unpacking sysv-rc (2.88dsf-41ubuntu6) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/sysv-rc_2.88dsf-41ubuntu6_all.deb (--unpack): trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62 ErrorMessage: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62 InstallationDate: Installed on 2023-05-13 (30 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: sysvinit Title: package sysv-rc (not installed) failed to install/upgrade: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/2023536 Title: package sysv-rc (not installed) failed to install/upgrade: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init- system-helpers 1.62 Status in sysvinit package in Ubuntu: New Bug description: when i install vscode. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: sysv-rc (not installed) ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: sysv-rc:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jun 12 16:15:46 2023 DpkgTerminalLog: Preparing to unpack .../sysv-rc_2.88dsf-41ubuntu6_all.deb ... Unpacking sysv-rc (2.88dsf-41ubuntu6) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/sysv-rc_2.88dsf-41ubuntu6_all.deb (--unpack): trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62 ErrorMessage: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62 InstallationDate: Installed on 2023-05-13 (30 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: sysvinit Title: package sysv-rc (not installed) failed to install/upgrade: trying to overwrite '/usr/sbin/invoke-rc.d', which is also in package init-system-helpers 1.62 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/2023536/+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 2023463] Re: Cannot remove items from side panel
Thanks for the bug report. Please provide a screenshot, photo or video so we can understand better what you are describing. Please also note that Ubuntu 22.10 reaches end of life in a couple of weeks so please upgrade when you can: https://ubuntu.com/download/desktop https://wiki.ubuntu.com/Releases ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2023463 Title: Cannot remove items from side panel Status in Ubuntu: Incomplete Bug description: Only an annoying bug I cannot remove the attached from my menu on the side panel. Other items are removed ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 14:22:20 2023 DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014 DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:100c] InstallationDate: Installed on 2023-02-08 (123 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire F5-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago) dmi.bios.date: 05/25/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18: dmi.product.family: SKL dmi.product.name: Aspire F5-572 dmi.product.sku: Aspire F5-572_100C_1.18 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2023463/+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 2023436] Re: Icons are showing as no entry signs
The black screen issue you mention should be discussed elsewhere because each bug should only cover a single topic. But that's likely to be caused by the open source 'nouveau' driver. So please open the 'Additional Drivers' app to install a supported NVIDIA driver to avoid that. -- 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/2023436 Title: Icons are showing as no entry signs Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I have tried looking in various places to see why icons aren't showing properly. Checked loads of log messages. Located the icons on the filesystem but for some reason the icons aren't loading. It is intermittent, for example sometimes the battery symbol shows and sometimes it doesn't. A bigger problem is that sometimes the screen goes black but the laptop is still on, the keyboard is still responding but it's impossible to use. Sometimes this happens a few times in an hour. Sometimes it can be days between using it. This is making my laptop pretty unusable. If there is anything I can do to investigate this further then please shout, happy to run all the commands and provide all the logs. I've attached a screenshot showing the issue in the settings panel but that isn't the only place this is happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 10 10:17:48 2023 DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d] InstallationDate: Installed on 2020-07-31 (1043 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9500 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago) dmi.bios.date: 03/16/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2023436/+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 2023436] Re: Icons are showing as no entry signs
Thanks for the bug report. Please try running 'gnome-control-center' in a Terminal window. When the bug occurs again, please tell us what text if any has been logged to the Terminal window. ** Package changed: xorg (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete -- 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/2023436 Title: Icons are showing as no entry signs Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I have tried looking in various places to see why icons aren't showing properly. Checked loads of log messages. Located the icons on the filesystem but for some reason the icons aren't loading. It is intermittent, for example sometimes the battery symbol shows and sometimes it doesn't. A bigger problem is that sometimes the screen goes black but the laptop is still on, the keyboard is still responding but it's impossible to use. Sometimes this happens a few times in an hour. Sometimes it can be days between using it. This is making my laptop pretty unusable. If there is anything I can do to investigate this further then please shout, happy to run all the commands and provide all the logs. I've attached a screenshot showing the issue in the settings panel but that isn't the only place this is happening. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 10 10:17:48 2023 DistUpgraded: 2022-10-02 12:38:39,285 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:097d] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:097d] InstallationDate: Installed on 2020-07-31 (1043 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9500 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=7a62b7f7-b519-470b-bcb8-48e870873cc4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-10-02 (250 days ago) dmi.bios.date: 03/16/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 05XYW7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd03/16/2023:br1.22:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2023436/+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 2023401] Re: Upon shutdown, shutdown process doesn't complete and the computer stays on
Thanks for the bug report. Please reproduce the bug again, wait a while and power off the machine. Then turn it on again and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2023401 Title: Upon shutdown, shutdown process doesn't complete and the computer stays on Status in Ubuntu: Incomplete Bug description: When I want to shutdown my computer, very often since last Ubuntu version, the process seems not to go to the end, and the computer never shuts down. I used not to notice it, physically close my laptop and put it back in my bag, then hours later find it very hot and with fans going at full speed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:35:50 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2023401/+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 2023403] Re: Dell XPS-17 trackpad stutters frequently
Thanks for the bug report. Please open a Terminal window and run 'top'. Now wait for the bug to occur again. Does 'top' show any process using high CPU when the stutter is happening? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2023403 Title: Dell XPS-17 trackpad stutters frequently Status in Ubuntu: Incomplete Bug description: Randomly, my trackpad has a lot of trouble detecting movement, for 10 to 20 seconds, until it comes back. Used to happen every day in previous versions, now every 3 days or so. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:43:21 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2023403/+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 2023400] Re: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Bug watch added: Mozilla Bugzilla #1745714 https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 ** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 Importance: Unknown Status: Unknown ** Also affects: thunderbird (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/2023400 Title: Upon clicking Thunderbird e-mail notifications, the e-mail doesn't open until clicking on a second notification Status in Mozilla Thunderbird: Unknown Status in gnome-shell package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: When I receive an e-mail, a notification appears. I click it in order for Thunderbird to open on the correct e-mail. But Thunderbird doesn't open right away, a new notification "'Thunderbird' is ready" appears, which I have to click in order for Thunderbird to open correctly. Related : https://bugzilla.mozilla.org/show_bug.cgi?id=1745714 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 9 16:31:36 2023 DistUpgraded: 2023-04-21 10:53:49,032 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-H GT2 [UHD Graphics] [1028:098f] Subsystem: Dell TU117M [GeForce GTX 1650 Ti Mobile] [1028:098f] InstallationDate: Installed on 2021-04-12 (787 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (49 days ago) dmi.bios.date: 03/14/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd03/14/2023:br1.24:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr:sku098F: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/2023400/+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
