[Bug 2070392] [NEW] 24.04 Update not working on odroid
Public bug reported: Upgrade does not work because changes could not be calculated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:125:1568112:2024-06-25 18:04:49.593404246 +0200:2024-06-25 18:04:49.161393021 +0200:/var/crash/_usr_libexec_polkitd.0.crash Date: Tue Jun 25 18:03:43 2024 InstallationDate: Installed on 2020-07-15 (1440 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-06-25 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: Error checking for authorization org.freedesktop.policykit.exec: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying mtime.conffile..etc.update-manager.release-upgrades: 2022-07-08T22:58:29.289659 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070392 Title: 24.04 Update not working on odroid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2070392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882216] Re: [bochs_drm] Booting gets stuck with corrupt graphics
I don't wan't to advertise but just to give an impression what virtual hardware we are talking about: https://contabo.com/?show=vps Both VPS are the SSD models. The interesting thing is that the problems started with Ubuntu 20.04. - I already used gnome on Ubuntu 18.04. Now I installed ubuntu-desktop and as far as I can remember I used gnome- desktop with 18.04. - basically both should use the same base if I'm not wrong. So the problem is not that big because XRDP is working and also X2GO. The VNC direct connection to GUI is my last option if everything else is not working. After Upgrade I also hat some problems with missing mouuse and keyboard in GUI. I used apt install xserver-xorg-input-evdev which solved this problem. Due to the several graphic modes which are tested at boot I thought maybe that this testing takes to long or something like this. But up to know I found no way to skip this resolution / graphic modes testing. If I use startx this process is much shorter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882216 Title: [bochs_drm] Booting gets stuck with corrupt graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882216] Re: [bochs_drm] Booting gets stuck with corrupt graphics
Thanks. I think I have tried both before but just to be sure I changed both settings and rebooted. Now the screen is not bluish with blue lines anymore it is black and I can switch to shell. So that's more or less like on VPS2 but without purple look. After that I returned to #WaylandEnable=false and the result after reboot is also the black screen. Seems to remove nomodeset is making the minimal difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882216 Title: [bochs_drm] Booting gets stuck with corrupt graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights
Ah, that makes much sense. If you are having problems you could help yourself. ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882102 Title: [vmwgfx] Gnome Desktop only starting with root rights To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882216] [NEW] Xorg freeze
Public bug reported: When booting on a VPS connected via VNC at first the text messages via boot are displayed. Then the resolution changes several times (VNC size changes) and after a lot of resolution changes it gets stuck in a corrupd graphic design. The cursor is still blinking but alt+Fx does also not work. Using sudo service gdm3 stop and sudo startx is working. Due to the fact that the VNC console is completely frozen and this is hosted at a provider I have to use a separate putty session to stop gdm and starting a new gui session which is then displayed in the VNC. This problem does not exist with Ubuntu 18.04 LTS. It does not matter if I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to 20.04 LTS. On a second VPS the problem is similar but not the same. The second one does not get totally frozen. There is still no GUI when booting but it ends up in a purple uniform screen even the text mode is purple (the first VPS ends up a blueish screen with blue vertical lines). On the second VPS it is possible to switch to shell (purple style) and executing the abovementioned commands directly without a second putty session. But the behavior is basically similar for both VPS. When using sudo reboot the second VPS displays text again and the first only some graphic trash. So basically they have both the same behavior but on the first the graphics are totally destroyed even text is not working anymore. The Funny thing is that startx is still working but after clothng the startx session the graphic trash is shown again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jun 5 10:39:59 2020 DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882216 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights
You are using multi user target because you like to or also having some kind of problems? If I use (which means removing the if else) exec /usr/libexec/gnome-session-binary --systemd "$@" the result is the same. Still the same message for missing permission. And with exec /usr/libexec/gnome-session-binary --builtin "$@" the result is identical. I thought maybe it's good to sort out this error first and if there are no problems without starting GUI without root rights than maybe a second bug report for boot to gui. But I can also open another bug report now. I'm not sure if this bugs / problems are connected in any way or not. With 18.04 I did not have this kind of errors on both machines. The funny thing is: On my Raspberry Pi 4b it is working from start (ok, this is a special distribution for special hardware so it should run). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882102 Title: [vmwgfx] Gnome Desktop only starting with root rights To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights
To be clear - I have not found an edit option: -stop service gdm3 -start service gdm3 +sudo service gdm3 stop +sudo service gdm3 start This will not result in something visible in the VNC. sudo startx does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882102 Title: [vmwgfx] Gnome Desktop only starting with root rights To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights
Can you log in normally from the login screen? Is it only an issue with 'startx'? No, if I try to boot directly to GUI the resolution changes several times (I can see that via VNC which is available at boot time for the VPS because the VNC size is changing several times) and then get's stuck. This happens on two different VPS. I have upgraded from 18.04 LTS. But this error is not connected to the update. I also tried to use a fresh install and the result was the same. Which means there is no login screen on both machines. If it get's stuck the beavior is different on both VPS even if I copy everything except /sys /run /proc (which means the same installation is used) one VPS gets stuck in a purple screen and it is possible to change to command line via Alt+F. The other one ends up in a blueish screen with lines and a blinking cursor but this one is totally stuck. I added two screenshots of that. Sometimes I see the desktop for a part of a socond between the resolution changes. I also tried to set a fixed resolution but was not sucessfull because the switching is still happening. If I stop the gdm serrvice startx with root is possible afterwards. IT took me a while to realize this because at first I thought I should focus on the GUI boot problem. I now switched both VPS to multi user target insted of graphical boot. If I use stop service gdm3 and start service gdm3 the result is the same like described above. XRDP combined with remote desktop is also only working via root login. Also please run: ls -l /usr/libexec/gnome-session-binary ls -l /usr/libexec/gnome-session-binary -rwxr-xr-x 1 root root 334664 Mar 26 13:22 /usr/libexec/gnome-session-binary On tests with xrdp I also saw some other errors in syslog which are more detailed as the gnome session permission error which does not seem to be the root cause: May 27 18:34:59 systemd[587724]: at-spi-dbus-bus.service: Failed to execute command: Permission denied May 27 18:34:59 systemd[587724]: at-spi-dbus-bus.service: Failed at step EXEC spawning /usr/libexec/at-spi-bus-launcher: Permission denied May 27 18:34:59 systemd[1678]: at-spi-dbus-bus.service: Main process exited, code=exited, status=203/EXEC I have seen some oher useers with this kind of problem which switched off at-spi-dbus-bus.service. I tried that and ended up with. That's where I stopped trying and switched at-spi-dbus-bus.service to start agein like before. Which means I'm now on standard settings after upgrade again: dbus-daemon[642845]: [session uid=0 pid=642843] Activating service name='org.freedesktop.systemd1' requested by ':1.20' (uid=0 pid=642800 comm="/usr/libexec/gnome-session-binary --builtin " label="unconfined") May 27 19:49:30 dbus-daemon[642845]: [session uid=0 pid=642843] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 May 27 19:49:30 org.gtk.vfs.Daemon[642897]: A connection to the bus can't be made May 27 19:49:30 gnome-control-c[646635]: gnome-control-center-search-provider: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0. May 27 19:49:30 seahorse[643522]: seahorse: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0. May 27 19:49:30 org.gnome.Chara[646649]: org.gnome.Characters.BackgroundService: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0. May 27 19:49:30 gnome-calendar[643523]: gnome-calendar: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0. May 27 19:49:30 systemd[1]: root-.cache-gvfs.mount: Succeeded. May 27 19:49:30 systemd[225333]: root-.cache-gvfs.mount: Succeeded. May 27 19:49:30 org.gnome.Shell.CalendarServer[643029]: gnome-shell-calendar-server[643029]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting May 27 19:49:30 systemd[1678]: root-.cache-gvfs.mount: Succeeded. May 27 19:49:30 systemd[1679]: root-.cache-gvfs.mount: Succeeded. May 27 19:49:30 org.gtk.vfs.Daemon[643591]: A connection to the bus can't be made May 27 19:49:30 org.gtk.vfs.Daemon[643694]: A connection to the bus can't be made -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882102 Title: [vmwgfx] Gnome Desktop only starting with root rights To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882102] [NEW] Gnome Desktop only starting with root rights
Public bug reported: All files in home folder are owned by the user. startx is only working with root rights. xinit: connection to X server lost/usr/bin/gnome-session: 29: exec: /usr/libexec/gnome-session-binary: Permission denied ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Jun 4 16:25:19 2020 DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=UUID=f8fcb1ae-51b1-4ab2-b79d-66cf34ad77d9 ro nomodeset rootflags=subvol=ROOT SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-04-26 (38 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882102 Title: Gnome Desktop only starting with root rights To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
