[Touch-packages] [Bug 2090805] Re: gdm blank screen

2024-12-17 Thread Paul-Andre Panon
OK, so I kind of messed up in that I did at some point get things working again, but didn't realize it because while I was experimenting and testing/trying to figure things out, I run a dual monitor setup (unequal sizes) and wound up swapping the monitor cable outputs so that when things started wo

[Touch-packages] [Bug 2090805] Re: gdm blank screen

2024-12-10 Thread Paul-Andre Panon
It looks like some parts of gnome were missing. Reinstalled the gnome package and a bunch more packages got re-installed and fixed. Still not working. However, now the only service which stills fail to start and is broken is org.freedeskop.systemd1, which twice tries and fails to startup due to bei

[Touch-packages] [Bug 2090805] Re: gdm blank screen

2024-12-07 Thread Paul-Andre Panon
dbus-run-session gnome-session produced the following results dbus-daemon[22068]: [session uid=0 pid=22068] Activating service name='org.freedesktop.systemd1' requested by ':1.4' (uid=0 pid=22069 comm="/usr/libexec/gnome-session-binary" label="unconfined") dbus-daemon[22068]: [session uid=0 pid=

[Touch-packages] [Bug 2090805] Re: gdm blank screen

2024-12-07 Thread Paul-Andre Panon
Also, systemctl --user status reports a degraded state with 1 failed unit -- 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/2090805 Title: gdm blank screen Status in xorg packa

[Touch-packages] [Bug 2090805] Re: gdm blank screen

2024-12-07 Thread Paul-Andre Panon
Sorry about the duplication between post #4 and #5. I got an error after trying to save #4 and thought I had lost it, so I redid it. -- 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/bu

[Touch-packages] [Bug 2090805] Re: gdm blank screen

2024-12-07 Thread Paul-Andre Panon
** Attachment added: "journalctl -xb output" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2090805/+attachment/5842753/+files/xbjournal.err -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs

[Touch-packages] [Bug 2090805] Re: gdm blank screen

2024-12-07 Thread Paul-Andre Panon
** Attachment added: "journalctl -xb output" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2090805/+attachment/5842752/+files/xbjournal.err -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs

[Touch-packages] [Bug 2090805] Re: gdm blank screen

2024-12-07 Thread Paul-Andre Panon
Trying to run XDG_SESSION_TYP=wayland dus-run-session gnome-session resulted in dbus-daemon[22068]: [session uid=0 pid=22068] Activating service name='org.freedesktop.systemd1' requested by ':1.4' (uid=0 pid=22069 comm="/usr/libexec/gnome-session-binary" label="unconfined") dbus-daemon[22068]

Re: [Touch-packages] [Bug 2090805] Re: gdm blank screen

2024-12-04 Thread Paul-Andre Panon
Thanks for your suggestions. Since I don't have a GUI, sending you a copy of the boot journal and attaching it to this ticket is a bit of a pain and I've been busy with work. A bunch of points: 1. My boot sequence is messed up. I no longer see a grub boot menu so I can choose alternative boot opt

[Touch-packages] [Bug 2017594] Re: package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker

2023-04-25 Thread Paul-Andre Panon
OK, so basically this is due to the usrmerge change, that appears to be driven by Redhat who recommend reinstalls for each new major version. It was adopted by Debian and hence Uyuni and you haven't got a reliable way to apply the merge during the in-place upgrades that you historically supported;

[Touch-packages] [Bug 2017594] Re: package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker

2023-04-24 Thread Paul-Andre Panon
Ah, I now see what you mean by the usrmerge. However I think that just reinforces my comments above. It doesn't make any sense for the installed package file to be installed in /sbin if /sbin is a symlink to /usr/sbin. if /usr/sbin is the canonical directory, and /sbin is an alias/symlink, then the

[Touch-packages] [Bug 2017594] Re: package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker

2023-04-24 Thread Paul-Andre Panon
Actually I just re-read and saw that you indicated /sbin was the symlink, which seems really strange because dpkg -L shows /sbin/apparmor_parser as a file in the apparmor package, but not /usr/sbin. ndco-admin@CARMD-EV-ALBLD7:~$ dpkg -L apparmor /. /etc /etc/apparmor /etc/apparmor/parser.conf /etc

[Touch-packages] [Bug 2017594] Re: package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker

2023-04-24 Thread Paul-Andre Panon
Also ~$ dpkg -S /usr/sbin/apparmor_parser dpkg-query: no path found matching pattern /usr/sbin/apparmor_parser ~$ dpkg -S /sbin/apparmor_parser apparmor: /sbin/apparmor_parser so it seems pretty messed up to me that the package file list would include the symbolic link but not the actual file. Som

[Touch-packages] [Bug 2017594] Re: package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker

2023-04-24 Thread Paul-Andre Panon
The /usr/sbin file not a symlink when it's causing an error. I'm guessing that it's a hard link but that the package upgrade is somehow deleting the /sbin directory entry (because it's the only one listed in the dpkg -L output) and building a new inode for the new file contents, but leaving the /us

[Touch-packages] [Bug 2017594] Re: package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker

2023-04-24 Thread Paul-Andre Panon
That's a good question. I'm not sure of the exact history of these systems, but I'm under the impression that they've gone through dist- upgrades from as least one older LTS and more likely at least 2 (i.e. from 16.04 to 18.04, to 20.04), but that predates my involvement. That said, when I looked a

[Touch-packages] [Bug 2017594] [NEW] package leaves non-updated copy of /usr/sbin/apparmor_parser after update to apparmor-2.13.3-7ubuntu5.2. Orphaned older executable breaks docker

2023-04-24 Thread Paul-Andre Panon
Public bug reported: There appears to be two copies of apparmor_parser installed by previous versions of the apparmor package, in /sbin and /usr/sbin. When updating the apparmor package to apparmor-2.13.3-7ubuntu5.2, only the /sbin/apparmor_parser executable is updated and the /usr/sbin copy is le

[Touch-packages] [Bug 1788060] [NEW] du program crashes on /var/lib

2018-08-20 Thread Paul Andre Panon
Public bug reported: We have an Ubuntu 18 installation using xfs file systems user@hostname:~$ df Filesystem 1K-blocks Used Available Use% Mounted on udev 19896400 1989640 0% /dev tmpfs 404008 848403160 1% /run /dev/sda19754624 308337