[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
I said my initial piece and recommendation here: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2046470/comments/2 It carries through here... This was brought up as a recommendation in Launchpad (here in this bug report) back in 2019, In that bug report, I questioned why this had been ignored, and not discussed much since then. It didn't go away, and it was discussed as it should have been. I was embarrassed that it had been that way for 4 years. Since then: By then Debian had already removed it from being installed as a default. Ubuntu kept it. even after that bug report... RedHat had removed it from being default installed. SUSE, is a special case, where they kept it for their Enterprise Server Lineup... Because they have different tuning settings for them, versus their desktops and other product images. But then on page 16 of their Performance Analysis, Tuning and Tools Guide (https://documentation.suse.com/sbp/server-linux/pdf/SBP-performance-tuning_en.pdf), that chapter starts out with this quote: >>> A correct IRQ configuration – above all in multi-core architecture and >>> multi-thread >>> applications– can have a profound impact on throughput and latency >>> performance ...and further says that the first step to get there is to disable irqbalance (where they give the instructions to disable the service) and how to go through irq configuration from there. Applications vendors, which we have in our repo's, such as Vlave Steam and CpuFrq, currently recommend removing irqbalance, if installed. RE: https://github.com/ValveSoftware/Proton/issues/3243 http://konkor.github.io/cpufreq/faq/ Additional to the blog article linked to in the last comment above, I found this blog (https://blogs.oracle.com/linux/post/irqbalance-design-and-internals), that goes into how it makes decisions in load balancing and is best summed up in it's conclusion: >>> This article described the internals of the irqbalance daemon. The >>> information provided >>> here can be used to debug and better understand load balance decisions >>> taken by irqbalance. The question I have is, if Ubuntu is Debian Branch, and we long ago went from having different kernels for desktop & server in ubuntu-base, but do have ubuntu-server packages and ubuntu-desktop packages, where things could be different, why is this still a broad sweep as a default install? I am happy that this is getting discussed properly now so that we can relook at this ad what it means to us today. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 2042979] Re: Noble spice-vdagent crash crashes xorg
Note that KVM machine / OS templates, currently, only go to Ubuntu 23.10, which this one is set to. If I set them to VGA, instead of QXL, it doesn't seem to happen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/2042979 Title: Noble spice-vdagent crash crashes xorg Status in spice-vdagent package in Ubuntu: New Bug description: This is on 'debian release' upgraded from Mantic to Noble, which I keep persistent to test the Noble Upgrades from day-to-day. Intermittent crashes, which results in the desktops crashing and returning back to the GDM3 graphical login. I am not sure if, since a VM, and Spice, if it is a KVM host problem, or if a Noble problem. The host is 22.04.3: >>> kvm --version QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15) Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers virsh -c qemu:///system version --daemon Compiled against library: libvirt 8.0.0 Using library: libvirt 8.0.0 Using API: QEMU 8.0.0 Running hypervisor: QEMU 6.2.0 Running against daemon: 8.0.0 >>> Attaching crash report below ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: spice-vdagent 0.22.1-3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 12:25:52 2023 InstallationDate: Installed on 2023-10-25 (13 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2042979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042979] Re: Noble spice-vdagent crash crashes xorg
** Attachment added: "_usr_lib_xorg_Xorg.1000.crash" https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2042979/+attachment/5717051/+files/_usr_lib_xorg_Xorg.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/2042979 Title: Noble spice-vdagent crash crashes xorg Status in spice-vdagent package in Ubuntu: New Bug description: This is on 'debian release' upgraded from Mantic to Noble, which I keep persistent to test the Noble Upgrades from day-to-day. Intermittent crashes, which results in the desktops crashing and returning back to the GDM3 graphical login. I am not sure if, since a VM, and Spice, if it is a KVM host problem, or if a Noble problem. The host is 22.04.3: >>> kvm --version QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15) Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers virsh -c qemu:///system version --daemon Compiled against library: libvirt 8.0.0 Using library: libvirt 8.0.0 Using API: QEMU 8.0.0 Running hypervisor: QEMU 6.2.0 Running against daemon: 8.0.0 >>> Attaching crash report below ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: spice-vdagent 0.22.1-3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 12:25:52 2023 InstallationDate: Installed on 2023-10-25 (13 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2042979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042979] [NEW] Noble spice-vdagent crash crashes xorg
Public bug reported: This is on 'debian release' upgraded from Mantic to Noble, which I keep persistent to test the Noble Upgrades from day-to-day. Intermittent crashes, which results in the desktops crashing and returning back to the GDM3 graphical login. I am not sure if, since a VM, and Spice, if it is a KVM host problem, or if a Noble problem. The host is 22.04.3: >>> kvm --version QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15) Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers virsh -c qemu:///system version --daemon Compiled against library: libvirt 8.0.0 Using library: libvirt 8.0.0 Using API: QEMU 8.0.0 Running hypervisor: QEMU 6.2.0 Running against daemon: 8.0.0 >>> Attaching crash report below ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: spice-vdagent 0.22.1-3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 12:25:52 2023 InstallationDate: Installed on 2023-10-25 (13 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: spice-vdagent (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages ** Attachment added: "_usr_bin_spice-vdagent.1000.crash" https://bugs.launchpad.net/bugs/2042979/+attachment/5717048/+files/_usr_bin_spice-vdagent.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/2042979 Title: Noble spice-vdagent crash crashes xorg Status in spice-vdagent package in Ubuntu: New Bug description: This is on 'debian release' upgraded from Mantic to Noble, which I keep persistent to test the Noble Upgrades from day-to-day. Intermittent crashes, which results in the desktops crashing and returning back to the GDM3 graphical login. I am not sure if, since a VM, and Spice, if it is a KVM host problem, or if a Noble problem. The host is 22.04.3: >>> kvm --version QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15) Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers virsh -c qemu:///system version --daemon Compiled against library: libvirt 8.0.0 Using library: libvirt 8.0.0 Using API: QEMU 8.0.0 Running hypervisor: QEMU 6.2.0 Running against daemon: 8.0.0 >>> Attaching crash report below ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: spice-vdagent 0.22.1-3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 12:25:52 2023 InstallationDate: Installed on 2023-10-25 (13 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/2042979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041328] Re: gnome-session crash on Kubuntu 23.10
Agreed. I think the resulting gnome-session crash was just a side-affect of something else, not the underlying issue itself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2041328 Title: gnome-session crash on Kubuntu 23.10 Status in gnome-session package in Ubuntu: Invalid Bug description: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install UbI had been at the Issue section of Canonical's github for ubuntu-desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install Ubuntu Reboot Apply updates Reboot Install gnome-sessions & LightDM Reboot Do some tests (T2-a) Install kubuntu-desktop Do more tests (T2-b) Should basically be the same right? Basically the same packages. Just a difference in the order they were installed, and the image they were installed from.. VM#1 crashes on gnome-session (will manually upload crash report, as apport failed while submitting) Test was just to log out and select a session type from LightDM, so see if it went to a desktop. If it locked up, I toggled over to vtty4 to issue: 'sudo killall lightdm' , to get back to the graphical login In test T1-a, logged out, the only Gnome mode that would go to a desktop without locking up the machine was Gnome on Wayland. Standard Name of "Gnome" is repeated/duplicated, even though there is only one desktop file for it in /usr/share/xsessions... There seems to be another But there is another gnome.desktop file somewhere, as I could edit the Name in that file to isolate if there was actually 2 files in the search path. At this time, both options of "GNOME" failed, and GNOME on xorg failed. * The GNOME desktop file that is located elsewhere is in /usr/share/wayland-sessions/... In test T1-b, only the .desktop file located in /usr/share/xsessions does not work... The duplicated GNOME entry located at /usr/share/wayland-sessions/gnome.desktop works. Just installing ubuntu-desktop corrected a lot of problems that gnome-session had, when installed without that, but some issues with gnome-session remain. Test T2-1 & T2-b, all sessions worked. Crash report is from after Test T1-b, in a Gnome session. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-session 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Oct 26 10:15:38 2023 InstallationDate: Installed on 2023-10-26 (1 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2041328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041328] Re: gnome-session crash on Kubuntu 23.10
Even with GDM3... The problem seems to be the foundation somewhere, as this one was installed originally as Kubuntu from the Kubuntu 23.10 installer ISO. The second on that was the comaparison was originally installed from the Ubuntu 23.10.1 Installer ISO. This test originally was spurned from three users telling that htey were gettig core 1 of their CPU's pegged at 100% when installed with the Kubuntu iso, but had no trouble at all installing with the Ubuntu iso, then adding the Kubuntu Desktop to it... Ohter Kubuntu users were having locking problems, if installed from the Kubuntu iso... The idea was brought up to try other desktops to see if there was a locking problem with those desktop installed on a Kubuntu foundation, with parallel tests of being installed from the Ubuntu iso as the comparison... I could not replicate that CPU problem, nor the system locking up, but I did find this. This test case #1 randomly crashes back to the Login Manager, no matter which DM is set to the Default... Even If I set GDM3, and/or SDDM as the DM. Like I said above, installing ubuntu-desktop on top of that, actually sorted out a lot of the initial problems it was having. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2041328 Title: gnome-session crash on Kubuntu 23.10 Status in gnome-session package in Ubuntu: Incomplete Bug description: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install UbI had been at the Issue section of Canonical's github for ubuntu-desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install Ubuntu Reboot Apply updates Reboot Install gnome-sessions & LightDM Reboot Do some tests (T2-a) Install kubuntu-desktop Do more tests (T2-b) Should basically be the same right? Basically the same packages. Just a difference in the order they were installed, and the image they were installed from.. VM#1 crashes on gnome-session (will manually upload crash report, as apport failed while submitting) Test was just to log out and select a session type from LightDM, so see if it went to a desktop. If it locked up, I toggled over to vtty4 to issue: 'sudo killall lightdm' , to get back to the graphical login In test T1-a, logged out, the only Gnome mode that would go to a desktop without locking up the machine was Gnome on Wayland. Standard Name of "Gnome" is repeated/duplicated, even though there is only one desktop file for it in /usr/share/xsessions... There seems to be another But there is another gnome.desktop file somewhere, as I could edit the Name in that file to isolate if there was actually 2 files in the search path. At this time, both options of "GNOME" failed, and GNOME on xorg failed. * The GNOME desktop file that is located elsewhere is in /usr/share/wayland-sessions/... In test T1-b, only the .desktop file located in /usr/share/xsessions does not work... The duplicated GNOME entry located at /usr/share/wayland-sessions/gnome.desktop works. Just installing ubuntu-desktop corrected a lot of problems that gnome-session had, when installed without that, but some issues with gnome-session remain. Test T2-1 & T2-b, all sessions worked. Crash report is from after Test T1-b, in a Gnome session. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-session 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Oct 26 10:15:38 2023 InstallationDate: Installed on 2023-10-26
[Desktop-packages] [Bug 2041328] Re: gnome-session crash on Kubuntu 23.10
I have been using LightDM as my DE with Gnome3 since it cam out. Gnome3 Works fine with LightDM through 23.10. That is just personal choice. GDM3 is still there. It is installed by default along with gnome- sessions, because it is the default. Do not get distracted. I can confirm that Tests T2-a are with LightDM as the DE and there are no errors at all. If I switch it t GDM3, still same errors. I cannot test it easily with SDDM, as there is no DE chooser, so has to be done other ways. ### Marked as "incomplete"? What else do you need? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2041328 Title: gnome-session crash on Kubuntu 23.10 Status in gnome-session package in Ubuntu: Incomplete Bug description: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install UbI had been at the Issue section of Canonical's github for ubuntu-desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install Ubuntu Reboot Apply updates Reboot Install gnome-sessions & LightDM Reboot Do some tests (T2-a) Install kubuntu-desktop Do more tests (T2-b) Should basically be the same right? Basically the same packages. Just a difference in the order they were installed, and the image they were installed from.. VM#1 crashes on gnome-session (will manually upload crash report, as apport failed while submitting) Test was just to log out and select a session type from LightDM, so see if it went to a desktop. If it locked up, I toggled over to vtty4 to issue: 'sudo killall lightdm' , to get back to the graphical login In test T1-a, logged out, the only Gnome mode that would go to a desktop without locking up the machine was Gnome on Wayland. Standard Name of "Gnome" is repeated/duplicated, even though there is only one desktop file for it in /usr/share/xsessions... There seems to be another But there is another gnome.desktop file somewhere, as I could edit the Name in that file to isolate if there was actually 2 files in the search path. At this time, both options of "GNOME" failed, and GNOME on xorg failed. * The GNOME desktop file that is located elsewhere is in /usr/share/wayland-sessions/... In test T1-b, only the .desktop file located in /usr/share/xsessions does not work... The duplicated GNOME entry located at /usr/share/wayland-sessions/gnome.desktop works. Just installing ubuntu-desktop corrected a lot of problems that gnome-session had, when installed without that, but some issues with gnome-session remain. Test T2-1 & T2-b, all sessions worked. Crash report is from after Test T1-b, in a Gnome session. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-session 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Oct 26 10:15:38 2023 InstallationDate: Installed on 2023-10-26 (1 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2041328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041328] Re: gnome-session crash on Kubuntu 23.10
_user_libexec-usbprotection.1000.upload is also present but is 0 bytes, so can not be uploaded. ** Attachment added: "_usr_libexec_gsd-usb-protection.1000.uploaded" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2041328/+attachment/5713580/+files/_usr_libexec_gsd-usb-protection.1000.uploaded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2041328 Title: gnome-session crash on Kubuntu 23.10 Status in gnome-session package in Ubuntu: New Bug description: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install UbI had been at the Issue section of Canonical's github for ubuntu-desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install Ubuntu Reboot Apply updates Reboot Install gnome-sessions & LightDM Reboot Do some tests (T2-a) Install kubuntu-desktop Do more tests (T2-b) Should basically be the same right? Basically the same packages. Just a difference in the order they were installed, and the image they were installed from.. VM#1 crashes on gnome-session (will manually upload crash report, as apport failed while submitting) Test was just to log out and select a session type from LightDM, so see if it went to a desktop. If it locked up, I toggled over to vtty4 to issue: 'sudo killall lightdm' , to get back to the graphical login In test T1-a, logged out, the only Gnome mode that would go to a desktop without locking up the machine was Gnome on Wayland. Standard Name of "Gnome" is repeated/duplicated, even though there is only one desktop file for it in /usr/share/xsessions... There seems to be another But there is another gnome.desktop file somewhere, as I could edit the Name in that file to isolate if there was actually 2 files in the search path. At this time, both options of "GNOME" failed, and GNOME on xorg failed. * The GNOME desktop file that is located elsewhere is in /usr/share/wayland-sessions/... In test T1-b, only the .desktop file located in /usr/share/xsessions does not work... The duplicated GNOME entry located at /usr/share/wayland-sessions/gnome.desktop works. Just installing ubuntu-desktop corrected a lot of problems that gnome-session had, when installed without that, but some issues with gnome-session remain. Test T2-1 & T2-b, all sessions worked. Crash report is from after Test T1-b, in a Gnome session. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-session 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Oct 26 10:15:38 2023 InstallationDate: Installed on 2023-10-26 (1 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2041328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041328] Re: gnome-session crash on Kubuntu 23.10
So the tests in T2a were all good and it remains good. The VM that started out as Kubuntu has issues. They have the same packages present. The order they were installed is different. ** Description changed: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install UbI had been at the Issue section of Canonical's github for ubuntu-desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install Ubuntu Reboot Apply updates Reboot Install gnome-sessions & LightDM Reboot Do some tests (T2-a) Install kubuntu-desktop Do more tests (T2-b) Should basically be the same right? Basically the same packages. Just a difference in the order they were installed, and the image they were installed from.. VM#1 crashes on gnome-session (will manually upload crash report, as apport failed while submitting) Test was just to log out and select a session type from LightDM, so see if it went to a desktop. If it locked up, I toggled over to vtty4 to issue: 'sudo killall lightdm' , to get back to the graphical login - In test T1-a, logged out, only Gnome mode that would go to a desktop without locking up the machine was Gnome on Wayland. Standard Name of "Gnome" is repeated/duplicated, even though there is only one desktop file for it in /usr/share/xsessions... - But there is another gnome.desktop file somewhere, as I could edit the Name in that file to isolate if there was actually 2 files in the search path. At this time, both options of "GNOME" failes, and GNOME on xorg failed. + In test T1-a, logged out, the only Gnome mode that would go to a desktop + without locking up the machine was Gnome on Wayland. Standard Name of + "Gnome" is repeated/duplicated, even though there is only one desktop + file for it in /usr/share/xsessions... There seems to be another - In test T1-b, only the .desktop file located in /usr/shar/xsessions does - not work... The dulicated GNOME entry located at unknown location works. + But there is another gnome.desktop file somewhere, as I could edit the + Name in that file to isolate if there was actually 2 files in the search + path. At this time, both options of "GNOME" failed, and GNOME on xorg + failed. + + * The GNOME desktop file that is located elsewhere is in + /usr/share/wayland-sessions/... + + In test T1-b, only the .desktop file located in /usr/share/xsessions + does not work... The duplicated GNOME entry located at + /usr/share/wayland-sessions/gnome.desktop works. Just installing ubuntu- + desktop corrected a lot of problems that gnome-session had, when + installed without that, but some issues with gnome-session remain. Test T2-1 & T2-b, all sessions worked. Crash report is from after Test T1-b, in a Gnome session. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-session 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Oct 26 10:15:38 2023 InstallationDate: Installed on 2023-10-26 (1 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2041328 Title: gnome-session crash on Kubuntu 23.10 Status in gnome-session package in Ubuntu: New Bug description: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue
[Desktop-packages] [Bug 2041328] Re: gnome-session crash on Kubuntu 23.10
** Attachment added: "_usr_lib_xorg_Xorg.0.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2041328/+attachment/5713579/+files/_usr_lib_xorg_Xorg.0.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2041328 Title: gnome-session crash on Kubuntu 23.10 Status in gnome-session package in Ubuntu: New Bug description: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install UbI had been at the Issue section of Canonical's github for ubuntu-desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install Ubuntu Reboot Apply updates Reboot Install gnome-sessions & LightDM Reboot Do some tests (T2-a) Install kubuntu-desktop Do more tests (T2-b) Should basically be the same right? Basically the same packages. Just a difference in the order they were installed, and the image they were installed from.. VM#1 crashes on gnome-session (will manually upload crash report, as apport failed while submitting) Test was just to log out and select a session type from LightDM, so see if it went to a desktop. If it locked up, I toggled over to vtty4 to issue: 'sudo killall lightdm' , to get back to the graphical login In test T1-a, logged out, the only Gnome mode that would go to a desktop without locking up the machine was Gnome on Wayland. Standard Name of "Gnome" is repeated/duplicated, even though there is only one desktop file for it in /usr/share/xsessions... There seems to be another But there is another gnome.desktop file somewhere, as I could edit the Name in that file to isolate if there was actually 2 files in the search path. At this time, both options of "GNOME" failed, and GNOME on xorg failed. * The GNOME desktop file that is located elsewhere is in /usr/share/wayland-sessions/... In test T1-b, only the .desktop file located in /usr/share/xsessions does not work... The duplicated GNOME entry located at /usr/share/wayland-sessions/gnome.desktop works. Just installing ubuntu-desktop corrected a lot of problems that gnome-session had, when installed without that, but some issues with gnome-session remain. Test T2-1 & T2-b, all sessions worked. Crash report is from after Test T1-b, in a Gnome session. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-session 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Oct 26 10:15:38 2023 InstallationDate: Installed on 2023-10-26 (1 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2041328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041328] Re: gnome-session crash on Kubuntu 23.10
Attached Crash report files. ** Attachment added: "_usr_libexec_gsd-usb-protection.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2041328/+attachment/5713578/+files/_usr_libexec_gsd-usb-protection.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2041328 Title: gnome-session crash on Kubuntu 23.10 Status in gnome-session package in Ubuntu: New Bug description: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install UbI had been at the Issue section of Canonical's github for ubuntu-desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install Ubuntu Reboot Apply updates Reboot Install gnome-sessions & LightDM Reboot Do some tests (T2-a) Install kubuntu-desktop Do more tests (T2-b) Should basically be the same right? Basically the same packages. Just a difference in the order they were installed, and the image they were installed from.. VM#1 crashes on gnome-session (will manually upload crash report, as apport failed while submitting) Test was just to log out and select a session type from LightDM, so see if it went to a desktop. If it locked up, I toggled over to vtty4 to issue: 'sudo killall lightdm' , to get back to the graphical login In test T1-a, logged out, the only Gnome mode that would go to a desktop without locking up the machine was Gnome on Wayland. Standard Name of "Gnome" is repeated/duplicated, even though there is only one desktop file for it in /usr/share/xsessions... There seems to be another But there is another gnome.desktop file somewhere, as I could edit the Name in that file to isolate if there was actually 2 files in the search path. At this time, both options of "GNOME" failed, and GNOME on xorg failed. * The GNOME desktop file that is located elsewhere is in /usr/share/wayland-sessions/... In test T1-b, only the .desktop file located in /usr/share/xsessions does not work... The duplicated GNOME entry located at /usr/share/wayland-sessions/gnome.desktop works. Just installing ubuntu-desktop corrected a lot of problems that gnome-session had, when installed without that, but some issues with gnome-session remain. Test T2-1 & T2-b, all sessions worked. Crash report is from after Test T1-b, in a Gnome session. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-session 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Oct 26 10:15:38 2023 InstallationDate: Installed on 2023-10-26 (1 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2041328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2041328] [NEW] gnome-session crash on Kubuntu 23.10
Public bug reported: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install UbI had been at the Issue section of Canonical's github for ubuntu-desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install Ubuntu Reboot Apply updates Reboot Install gnome-sessions & LightDM Reboot Do some tests (T2-a) Install kubuntu-desktop Do more tests (T2-b) Should basically be the same right? Basically the same packages. Just a difference in the order they were installed, and the image they were installed from.. VM#1 crashes on gnome-session (will manually upload crash report, as apport failed while submitting) Test was just to log out and select a session type from LightDM, so see if it went to a desktop. If it locked up, I toggled over to vtty4 to issue: 'sudo killall lightdm' , to get back to the graphical login In test T1-a, logged out, only Gnome mode that would go to a desktop without locking up the machine was Gnome on Wayland. Standard Name of "Gnome" is repeated/duplicated, even though there is only one desktop file for it in /usr/share/xsessions... But there is another gnome.desktop file somewhere, as I could edit the Name in that file to isolate if there was actually 2 files in the search path. At this time, both options of "GNOME" failes, and GNOME on xorg failed. In test T1-b, only the .desktop file located in /usr/shar/xsessions does not work... The dulicated GNOME entry located at unknown location works. Test T2-1 & T2-b, all sessions worked. Crash report is from after Test T1-b, in a Gnome session. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-session 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Oct 26 10:15:38 2023 InstallationDate: Installed on 2023-10-26 (1 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2041328 Title: gnome-session crash on Kubuntu 23.10 Status in gnome-session package in Ubuntu: New Bug description: I had been at the Issue section of Canonical's github for ubuntu- desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install gnome-session, LightDm Reboot Do some tests (T1-a) Install ubuntu-desktop... Do more tests (T1-b) Create another VM (VM#2) Install UbI had been at the Issue section of Canonical's github for ubuntu-desktop-installer's issue section and felt compelled to answer some user's questions about their problems. (Long story that I won't dwell on) * There was an interesting trend there with Kubuntu user issues. One Kubuntu user mentioned something that sparked my interest... It was enough to prompt me to download the latest ISO image for it to investigate on my own. Here is the repeatable steps to recreate it: Create a VM (VM#1) Install Kubuntu. Reboot Apply updates Reboot Install
[Desktop-packages] [Bug 2039592] Re: no connection via SIM card
I had been helping this user on Ubuntu Forums: https://ubuntuforums.org/showthread.php?t=2491572 "English" is not this user's primary language, so let me help him explain this here. This worked for him in 20.04. It is not working since he upgraded to 22.04. For some unknown reason, lshw -C Network is not producing expected results on that device, so not a lot of human-friendly readable information is being shown. His system sees his WWAN card as you can see in his attached WifiSyslog.txt: жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: new high-speed USB device number 4 using xhci_hcd жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: New USB device found, idVendor=03f0, idProduct=521d, bcdDevice= 0.01 жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: New USB device strings: Mfr=5, Product=4, SerialNumber=0 жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: Product: HP hs3110 HSPA+ Mobile Broadband Device жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: Manufacturer: Hewlett-Packard What isn't showing up there in that log, is anything about a driver being attached to that device. In the attached RfKill.txt, that device does not even show up in the list. But his syslogs say this: Code:13:26:44 NetworkManager: [1696760804.3166] audit: op="radio-control" arg="wwan-enabledn" pid=2374 uid=1000 result="success" 13:26:44 NetworkManager: [1696760804.3166] audit: op="radio-control" arg="wwan-enabledn" pid=2374 uid=1000 result="success" 13:26:44 NetworkManager: [1696760804.3159] manager: rfkill: WWAN hardware radio set enabled 12:37:51 NetworkManager: [1696757871.8350] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file 12:37:51 NetworkManager: [1696757871.8190] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) 12:37:51 NetworkManager: [1696757871.8124] manager[0x55e016153040]: rfkill: WWAN hardware radio set disabled So rfkill is seeing it and addressing it, the NNWwanFactory module is being loaded, but the device is not being left as enabled... That is what I know about it. Is anyone going to triage this soon? It has been 5 days now... When I refer a user to file a bug report, it's because I have faith that when I do, it's the correct thing to do for the improvement of Ubuntu, that something is wrong, it is not working as expected, that can possibly be corrected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2039592 Title: no connection via SIM card Status in network-manager package in Ubuntu: New Bug description: Ubuntu 22.04 I can’t connect to the Internet via a SIM card. I can see how the Measurement Manager is being developed and the plugin is installed.. I'll add a module: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) manager: rfkill: WWAN is jammed with radio; I'll become a file. the driver does not load!!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 19:40:10 2023 InstallationDate: Installed on 2023-10-03 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) IpRoute: default via 192.168.43.63 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.43.0/24 dev wlo1 proto kernel scope link src 192.168.43.83 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 ONEPLUS_A5000_co_aptsvo 174d782e-8952-4921-b779-adbd0266fe27 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full
[Desktop-packages] [Bug 2039592] Re: no connection via SIM card
I had been helping this user on Ubuntu Forums: https://ubuntuforums.org/showthread.php?t=2491572 "English" is not this user's primary language, so let me help him explain this here. This worked for him in 20.04. It is not working since he upgraded to 22.04. For some unknown reason, lshw -C Network is not producing expected results on that device, so not a lot of human-friendly readable information is being shown. His system sees his WWAN card as you can see in his attached WifiSyslog.txt: жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: new high-speed USB device number 4 using xhci_hcd жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: New USB device found, idVendor=03f0, idProduct=521d, bcdDevice= 0.01 жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: New USB device strings: Mfr=5, Product=4, SerialNumber=0 жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: Product: HP hs3110 HSPA+ Mobile Broadband Device жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: Manufacturer: Hewlett-Packard What isn't showing up there in that log, is anything about a driver being attached to that device. In the attached RfKill.txt, that device does not even show up in the list. But his syslogs say this: Code:13:26:44 NetworkManager: [1696760804.3166] audit: op="radio-control" arg="wwan-enabledn" pid=2374 uid=1000 result="success" 13:26:44 NetworkManager: [1696760804.3166] audit: op="radio-control" arg="wwan-enabledn" pid=2374 uid=1000 result="success" 13:26:44 NetworkManager: [1696760804.3159] manager: rfkill: WWAN hardware radio set enabled 12:37:51 NetworkManager: [1696757871.8350] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file 12:37:51 NetworkManager: [1696757871.8190] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) 12:37:51 NetworkManager: [1696757871.8124] manager[0x55e016153040]: rfkill: WWAN hardware radio set disabled So rfkill is seeing it and addressing it, the NNWwanFactory module is being loaded, but the device is not being left as enabled... That is what I know about it. Is anyone going to triage this soon? It has been 5 days now... When I refer a user to file a bug report, it's because I have faith that when I do, it's the correct thing to do for the improvement of Ubuntu, that something is wrong, it is not working as expected, that can possibly be corrected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2039592 Title: no connection via SIM card Status in network-manager package in Ubuntu: New Bug description: Ubuntu 22.04 I can’t connect to the Internet via a SIM card. I can see how the Measurement Manager is being developed and the plugin is installed.. I'll add a module: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) manager: rfkill: WWAN is jammed with radio; I'll become a file. the driver does not load!!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 19:40:10 2023 InstallationDate: Installed on 2023-10-03 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) IpRoute: default via 192.168.43.63 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.43.0/24 dev wlo1 proto kernel scope link src 192.168.43.83 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 ONEPLUS_A5000_co_aptsvo 174d782e-8952-4921-b779-adbd0266fe27 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full
[Desktop-packages] [Bug 2038857] Re: Mantic Daily Text Editor Crashed Xorg
Note: When I was looking for changed/modified files, that was related
to:
https://answers.launchpad.net/ubuntu/+source/subiquity/+question/708132,
which is still unanswered...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2038857
Title:
Mantic Daily Text Editor Crashed Xorg
Status in xorg package in Ubuntu:
New
Bug description:
In testing Mantic Daily ISO. Dl'ed today and updated to current git in
installer. After selecting "Erase All and Install Ubuntu: Experimental
ZFS > Next... Jumped out to system and started gnome-terminal.
Created file of all modified files within the last 5 minutes. Opened
Text Editor > Open... Text editor could not see any recent files and
had no way to navigate to folders... Selected menu in top bar of
editor... Scree when blank, then to lock-screen.
On getting back through lockscreen, ubuntu-desktop-installer
restarted. Went to "try". apport said that Xorg had crashed.
On choosing report bug, apport crashed. Submitted report via 'ubuntu-
bug'.
Here we are.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 9 17:58:20 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-6.2
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.2
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
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/+source/xorg/+bug/2038857/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2038857] [NEW] Mantic Daily Text Editor Crashed Xorg
Public bug reported:
In testing Mantic Daily ISO. Dl'ed today and updated to current git in
installer. After selecting "Erase All and Install Ubuntu: Experimental
ZFS > Next... Jumped out to system and started gnome-terminal.
Created file of all modified files within the last 5 minutes. Opened
Text Editor > Open... Text editor could not see any recent files and had
no way to navigate to folders... Selected menu in top bar of editor...
Scree when blank, then to lock-screen.
On getting back through lockscreen, ubuntu-desktop-installer restarted.
Went to "try". apport said that Xorg had crashed.
On choosing report bug, apport crashed. Submitted report via 'ubuntu-
bug'.
Here we are.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 9 17:58:20 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-6.2
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.2
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
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 mantic ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2038857
Title:
Mantic Daily Text Editor Crashed Xorg
Status in xorg package in Ubuntu:
New
Bug description:
In testing Mantic Daily ISO. Dl'ed today and updated to current git in
installer. After selecting "Erase All and Install Ubuntu: Experimental
ZFS > Next... Jumped out to system and started gnome-terminal.
Created file of all modified files within the last 5 minutes. Opened
Text Editor > Open... Text editor could not see any recent files and
had no way to navigate to folders... Selected menu in top bar of
editor... Scree when blank, then to lock-screen.
On getting back through lockscreen, ubuntu-desktop-installer
restarted. Went to "try". apport said that Xorg had crashed.
On choosing report bug, apport crashed. Submitted report via 'ubuntu-
bug'.
Here we are.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir
[Desktop-packages] [Bug 2028438] Re: gnome-control-center crash with assertion failure: cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button)
Even if I remove/purge it,and install fresh... On start, it is stuck at the same point and error... It is affected by this upstream Gnome bug: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1504 Upon seeing that it is affected by setting the power profile to performance... I did this: Code: mafoelffen@Mikes-ThinkPad-T520:~$ powerprofilesctl get performance mafoelffen@Mikes-ThinkPad-T520:~$ powerprofilesctl set balanced mafoelffen@Mikes-ThinkPad-T520:~$ powerprofilesctl get balanced After that, gnome-control-center was unlocked and worked... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash with assertion failure: cc-power- panel.c:1122:performance_profile_set_active: assertion failed: (button) Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Suddenly today, while doing a backup (rsync) system started going to sleep... I know I had my setting set to not suspend, never to go to screensaver. Went to ope "Settings"... Settings loaded fine (then). Selected "Power". Settings crashed, and opened Bug Report dialog, but on "Send", that also crashed. "Settings" can no longer open at all. Starts to load, at least by the status in the upper bar of screen, then goes away. In 'top', I can see it running while it is trying to start (as gnome-control-center)... Then goes away. Have tried to re- install it, same problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Jul 22 12:28:06 2023 InstallationDate: Installed on 2021-09-23 (667 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-08-17 (339 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2028438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028438] Re: gnome-control-center crash
Stuck on power panel: mafoelffen@Mikes-ThinkPad-T520:~$ gnome-control-center network (gnome-control-center:122922): cc-power-profile-row-CRITICAL **: 01:37:57.530: cc_power_profile_row_get_radio_button: assertion 'CC_IS_POWER_PROFILE_ROW (self)' failed ** power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) Bail out! power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) Aborted (core dumped) mafoelffen@Mikes-ThinkPad-T520:~$ gnome-control-center -v display (gnome-control-center:123168): cc-power-profile-row-CRITICAL **: 01:39:37.164: cc_power_profile_row_get_radio_button: assertion 'CC_IS_POWER_PROFILE_ROW (self)' failed ** power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) Bail out! power-cc-panel:ERROR:../panels/power/cc-power-panel.c:1122:performance_profile_set_active: assertion failed: (button) Aborted (core dumped) *** END OUTPUT *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Suddenly today, while doing a backup (rsync) system started going to sleep... I know I had my setting set to not suspend, never to go to screensaver. Went to ope "Settings"... Settings loaded fine (then). Selected "Power". Settings crashed, and opened Bug Report dialog, but on "Send", that also crashed. "Settings" can no longer open at all. Starts to load, at least by the status in the upper bar of screen, then goes away. In 'top', I can see it running while it is trying to start (as gnome-control-center)... Then goes away. Have tried to re- install it, same problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Jul 22 12:28:06 2023 InstallationDate: Installed on 2021-09-23 (667 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-08-17 (339 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028438] Re: gnome-control-center crash
Further. When this originally happened, this was while checking a strange occurrence of the laptop going into hibernation... When all settings in the BIOS is set to not go to sleep... And everything in dconf set not to go to sleep. I don't know if this is related, but... It is still going to sleep. And Settings will not start. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash Status in gnome-control-center package in Ubuntu: New Bug description: Suddenly today, while doing a backup (rsync) system started going to sleep... I know I had my setting set to not suspend, never to go to screensaver. Went to ope "Settings"... Settings loaded fine (then). Selected "Power". Settings crashed, and opened Bug Report dialog, but on "Send", that also crashed. "Settings" can no longer open at all. Starts to load, at least by the status in the upper bar of screen, then goes away. In 'top', I can see it running while it is trying to start (as gnome-control-center)... Then goes away. Have tried to re- install it, same problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Jul 22 12:28:06 2023 InstallationDate: Installed on 2021-09-23 (667 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-08-17 (339 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028438] Re: gnome-control-center crash
Errors log from journalctl and syslog attached ** Attachment added: "errors.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028438/+attachment/5687909/+files/errors.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash Status in gnome-control-center package in Ubuntu: New Bug description: Suddenly today, while doing a backup (rsync) system started going to sleep... I know I had my setting set to not suspend, never to go to screensaver. Went to ope "Settings"... Settings loaded fine (then). Selected "Power". Settings crashed, and opened Bug Report dialog, but on "Send", that also crashed. "Settings" can no longer open at all. Starts to load, at least by the status in the upper bar of screen, then goes away. In 'top', I can see it running while it is trying to start (as gnome-control-center)... Then goes away. Have tried to re- install it, same problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Jul 22 12:28:06 2023 InstallationDate: Installed on 2021-09-23 (667 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-08-17 (339 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028438] [NEW] gnome-control-center crash
Public bug reported: Suddenly today, while doing a backup (rsync) system started going to sleep... I know I had my setting set to not suspend, never to go to screensaver. Went to ope "Settings"... Settings loaded fine (then). Selected "Power". Settings crashed, and opened Bug Report dialog, but on "Send", that also crashed. "Settings" can no longer open at all. Starts to load, at least by the status in the upper bar of screen, then goes away. In 'top', I can see it running while it is trying to start (as gnome-control-center)... Then goes away. Have tried to re-install it, same problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Jul 22 12:28:06 2023 InstallationDate: Installed on 2021-09-23 (667 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-08-17 (339 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2028438 Title: gnome-control-center crash Status in gnome-control-center package in Ubuntu: New Bug description: Suddenly today, while doing a backup (rsync) system started going to sleep... I know I had my setting set to not suspend, never to go to screensaver. Went to ope "Settings"... Settings loaded fine (then). Selected "Power". Settings crashed, and opened Bug Report dialog, but on "Send", that also crashed. "Settings" can no longer open at all. Starts to load, at least by the status in the upper bar of screen, then goes away. In 'top', I can see it running while it is trying to start (as gnome-control-center)... Then goes away. Have tried to re- install it, same problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Jul 22 12:28:06 2023 InstallationDate: Installed on 2021-09-23 (667 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-08-17 (339 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2008420] Re: '/usr/share/applications/default.list' content outdated
Found that this is a symlink to, so the concerned file is actually "/etc/gnome/defaults.list". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2008420 Title: '/usr/share/applications/default.list' content outdated Status in nautilus package in Ubuntu: New Bug description: For Ubuntu 22.10 and 23.04, the contents of file /usr/share/applcations/default.list has file associations for audio file set as 'rhythmbox.desktop' as the application startup file to associate files to... That file was updated and changed names to 'org.gnome.Rhythmbox3.desktop'... File '/usr/share/applications/defaults.list' needs to be updated to reflect that change. I know that the system that file belongs to, is underlying to nautilus, but I was unsure on what to file this issue against. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 13:08:55 2023 GsettingsChanges: InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2008420] Re: '/usr/share/applications/default.list' content outdated
Here is the concerned file: ** Attachment added: "defaults.list" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008420/+attachment/5649647/+files/defaults.list -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2008420 Title: '/usr/share/applications/default.list' content outdated Status in nautilus package in Ubuntu: New Bug description: For Ubuntu 22.10 and 23.04, the contents of file /usr/share/applcations/default.list has file associations for audio file set as 'rhythmbox.desktop' as the application startup file to associate files to... That file was updated and changed names to 'org.gnome.Rhythmbox3.desktop'... File '/usr/share/applications/defaults.list' needs to be updated to reflect that change. I know that the system that file belongs to, is underlying to nautilus, but I was unsure on what to file this issue against. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 13:08:55 2023 GsettingsChanges: InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2008420] [NEW] '/usr/share/applications/default.list' content outdated
Public bug reported: For Ubuntu 22.10 and 23.04, the contents of file /usr/share/applcations/default.list has file associations for audio file set as 'rhythmbox.desktop' as the application startup file to associate files to... That file was updated and changed names to 'org.gnome.Rhythmbox3.desktop'... File '/usr/share/applications/defaults.list' needs to be updated to reflect that change. I know that the system that file belongs to, is underlying to nautilus, but I was unsure on what to file this issue against. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 13:08:55 2023 GsettingsChanges: InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2008420 Title: '/usr/share/applications/default.list' content outdated Status in nautilus package in Ubuntu: New Bug description: For Ubuntu 22.10 and 23.04, the contents of file /usr/share/applcations/default.list has file associations for audio file set as 'rhythmbox.desktop' as the application startup file to associate files to... That file was updated and changed names to 'org.gnome.Rhythmbox3.desktop'... File '/usr/share/applications/defaults.list' needs to be updated to reflect that change. I know that the system that file belongs to, is underlying to nautilus, but I was unsure on what to file this issue against. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 13:08:55 2023 GsettingsChanges: InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000447] [NEW] Startup Splash dialog (usplash) no dialog for LVM encrytion unlock
Public bug reported: dm-crypt graphical unlock dialog does not appear. Screen is just black, as if the machine is hung, BUT... If you or to show the boot messages, the dm-crypt unlock text console message is there, with one asterist ccorred already from the key the user pressed to get there... So you have to backspace before entering in the passphrase. Alternately, if you assume it "IS" there... You can just enter in the passphrase and for it to continue... ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth 22.02.122-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 25 16:49:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2022-12-26 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221225) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-21-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-21-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.2 dmi.sys.vendor: QEMU ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar uec-images wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2000447 Title: Startup Splash dialog (usplash) no dialog for LVM encrytion unlock Status in plymouth package in Ubuntu: New Bug description: dm-crypt graphical unlock dialog does not appear. Screen is just black, as if the machine is hung, BUT... If you or to show the boot messages, the dm-crypt unlock text console message is there, with one asterist ccorred already from the key the user pressed to get there... So you have to backspace before entering in the passphrase. Alternately, if you assume it "IS" there... You can just enter in the passphrase and for it to continue... ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth 22.02.122-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 25 16:49:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2022-12-26 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221225) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-21-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-21-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth:
[Desktop-packages] [Bug 1998124] [NEW] Nautilus- broken link from "Find New Applications"
Public bug reported: (On 23.04 Daily build) If you are creating a .desktop on the desktop... or in Nautilus... and right-click use: Open With Other Application > Find New Applications... It errors out and locks up everything. The error displayed says that it can't find 'gnome-software'. It gets multiple error popups that do not go away. You have to reboot to get out of it. Another user can recreate the error, but can cancel out of it. Dev thread: https://ubuntuforums.org/showthread.php?t=2481316 If I install 'gnome-software', it continues on normally... I want to file a bug to report it and get that resolved, but unsure what package to file it against. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 28 08:20:07 2022 GsettingsChanges: InstallationDate: Installed on 2022-11-28 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221128) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1998124 Title: Nautilus- broken link from "Find New Applications" Status in nautilus package in Ubuntu: New Bug description: (On 23.04 Daily build) If you are creating a .desktop on the desktop... or in Nautilus... and right-click use: Open With Other Application > Find New Applications... It errors out and locks up everything. The error displayed says that it can't find 'gnome- software'. It gets multiple error popups that do not go away. You have to reboot to get out of it. Another user can recreate the error, but can cancel out of it. Dev thread: https://ubuntuforums.org/showthread.php?t=2481316 If I install 'gnome-software', it continues on normally... I want to file a bug to report it and get that resolved, but unsure what package to file it against. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 28 08:20:07 2022 GsettingsChanges: InstallationDate: Installed on 2022-11-28 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221128) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1998124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1375511] Re: XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great
This was my usual install script (attached). Notice the comments at the minimum install of the XServer Core. Used to install and work fine --withoutrecommends. Now I have to remove that flag from it... and let it install full. There most be another dependency there somewhere now. (not sure yet where.) But removed my X install (remove from the last line going backwards) and re-installed with this updated script... and it works fine now. -- Closed? ** Attachment added: minimalx.sh https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mach64/+bug/1375511/+attachment/4221988/+files/minimalx.sh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-mach64 in Ubuntu. https://bugs.launchpad.net/bugs/1375511 Title: XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great Status in “xserver-xorg-video-mach64” package in Ubuntu: New Bug description: System is now Server 14.04, with a minimal X install (openbox, etc...) and package xserver-xorg-video-mach64 was installed and is the newest version. I just upgraded that server from 12.04LTS Server. Before the upgrade, it had worked fine using startx to boot an instance of X for doing maintenance. Did a release upgrade (today) to 14.04 and it's now broke. XLog has that same exact message. Diving into it right now to check it out (see why it broke). Other users on the forum are also having this problem: http://ubuntuforums.org/showthread.php?t=2241397p=13132193 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-mach64 6.9.4-1build1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 Date: Mon Sep 29 16:26:16 2014 InstallationDate: Installed on 2013-04-05 (542 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release i386 (20130214) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-mach64 UpgradeStatus: Upgraded to trusty on 2014-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mach64/+bug/1375511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1375511] [NEW] XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great
Public bug reported: System is now Server 14.04, with a minimal X install (openbox, etc...) and package xserver-xorg-video-mach64 was installed and is the newest version. I just upgraded that server from 12.04LTS Server. Before the upgrade, it had worked fine using startx to boot an instance of X for doing maintenance. Did a release upgrade (today) to 14.04 and it's now broke. XLog has that same exact message. Diving into it right now to check it out (see why it broke). Other users on the forum are also having this problem: http://ubuntuforums.org/showthread.php?t=2241397p=13132193 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-mach64 6.9.4-1build1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 Date: Mon Sep 29 16:26:16 2014 InstallationDate: Installed on 2013-04-05 (542 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release i386 (20130214) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-mach64 UpgradeStatus: Upgraded to trusty on 2014-09-29 (0 days ago) ** Affects: xserver-xorg-video-mach64 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-mach64 in Ubuntu. https://bugs.launchpad.net/bugs/1375511 Title: XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great Status in “xserver-xorg-video-mach64” package in Ubuntu: New Bug description: System is now Server 14.04, with a minimal X install (openbox, etc...) and package xserver-xorg-video-mach64 was installed and is the newest version. I just upgraded that server from 12.04LTS Server. Before the upgrade, it had worked fine using startx to boot an instance of X for doing maintenance. Did a release upgrade (today) to 14.04 and it's now broke. XLog has that same exact message. Diving into it right now to check it out (see why it broke). Other users on the forum are also having this problem: http://ubuntuforums.org/showthread.php?t=2241397p=13132193 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-mach64 6.9.4-1build1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 Date: Mon Sep 29 16:26:16 2014 InstallationDate: Installed on 2013-04-05 (542 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release i386 (20130214) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-mach64 UpgradeStatus: Upgraded to trusty on 2014-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mach64/+bug/1375511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1375511] Re: XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great
Remember that without xserver coming up, if you want info, back traces or logs, that it will be from the command line from that server. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-mach64 in Ubuntu. https://bugs.launchpad.net/bugs/1375511 Title: XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great Status in “xserver-xorg-video-mach64” package in Ubuntu: New Bug description: System is now Server 14.04, with a minimal X install (openbox, etc...) and package xserver-xorg-video-mach64 was installed and is the newest version. I just upgraded that server from 12.04LTS Server. Before the upgrade, it had worked fine using startx to boot an instance of X for doing maintenance. Did a release upgrade (today) to 14.04 and it's now broke. XLog has that same exact message. Diving into it right now to check it out (see why it broke). Other users on the forum are also having this problem: http://ubuntuforums.org/showthread.php?t=2241397p=13132193 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-mach64 6.9.4-1build1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 Date: Mon Sep 29 16:26:16 2014 InstallationDate: Installed on 2013-04-05 (542 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release i386 (20130214) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-mach64 UpgradeStatus: Upgraded to trusty on 2014-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mach64/+bug/1375511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1375511] Re: XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great
xorg.0.log file from that server: ** Attachment added: xorg.0.log file https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mach64/+bug/1375511/+attachment/4219766/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-mach64 in Ubuntu. https://bugs.launchpad.net/bugs/1375511 Title: XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great Status in “xserver-xorg-video-mach64” package in Ubuntu: New Bug description: System is now Server 14.04, with a minimal X install (openbox, etc...) and package xserver-xorg-video-mach64 was installed and is the newest version. I just upgraded that server from 12.04LTS Server. Before the upgrade, it had worked fine using startx to boot an instance of X for doing maintenance. Did a release upgrade (today) to 14.04 and it's now broke. XLog has that same exact message. Diving into it right now to check it out (see why it broke). Other users on the forum are also having this problem: http://ubuntuforums.org/showthread.php?t=2241397p=13132193 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-mach64 6.9.4-1build1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 Date: Mon Sep 29 16:26:16 2014 InstallationDate: Installed on 2013-04-05 (542 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release i386 (20130214) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-mach64 UpgradeStatus: Upgraded to trusty on 2014-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mach64/+bug/1375511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1375511] Re: XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great
From lspci: 00:03.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rage XL PCI [1002:4752] (rev 27) (prog-if 00 [VGA controller]) Subsystem: Compaq Computer Corporation Proliant Rage XL [0e11:001e] Flags: bus master, stepping, medium devsel, latency 64 Memory at f600 (32-bit, non-prefetchable) [size=16M] I/O ports at 2400 [size=256] Memory at f5ff (32-bit, non-prefetchable) [size=4K] [virtual] Expansion ROM at 8000 [disabled] [size=128K] Capabilities: access denied -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-mach64 in Ubuntu. https://bugs.launchpad.net/bugs/1375511 Title: XServer modprobe: FATAL: Module mach64 not found. 14.04.1. 12.04 worked great Status in “xserver-xorg-video-mach64” package in Ubuntu: New Bug description: System is now Server 14.04, with a minimal X install (openbox, etc...) and package xserver-xorg-video-mach64 was installed and is the newest version. I just upgraded that server from 12.04LTS Server. Before the upgrade, it had worked fine using startx to boot an instance of X for doing maintenance. Did a release upgrade (today) to 14.04 and it's now broke. XLog has that same exact message. Diving into it right now to check it out (see why it broke). Other users on the forum are also having this problem: http://ubuntuforums.org/showthread.php?t=2241397p=13132193 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-mach64 6.9.4-1build1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 Date: Mon Sep 29 16:26:16 2014 InstallationDate: Installed on 2013-04-05 (542 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release i386 (20130214) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-mach64 UpgradeStatus: Upgraded to trusty on 2014-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mach64/+bug/1375511/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351639] Re: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.331.38', which
This is still a problem on one of mine (my main box that I also use for the console for my servers). This box has been running 14.04 and nvidia-current (331.38) since it's realease. Only reason was going to 331.xx update was that I run Gnome 3 and for some reason 331.xx boink's any resolutions but low-res in Gnome 3 Native, but fine in all other desktop modes (Gnome or Unity). But anyways 331.xx to 331.xx Update crashes the install from inside Additional drivers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1351639 Title: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu /libnvidia-opencl.so.331.38', which is also in package nvidia-opencl- icd-331 331.38-0ubuntu7.1 Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Bug description: installing proprietary driver ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-opencl-icd-331-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Fri Aug 1 23:49:06 2014 DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not installed):trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.331.38', which is also in package nvidia-opencl-icd-331 331.38-0ubuntu7.1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.331.38', which is also in package nvidia-opencl-icd-331 331.38-0ubuntu7.1 InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: nvidia-graphics-drivers-331-updates Title: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.331.38', which is also in package nvidia-opencl-icd-331 331.38-0ubuntu7.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1351639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1351639] Re: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.331.38', which
If you want to hear the kicker on that(?): I just did a check of my install packages on that box... And nvidia-331-updates NVIDIA binary driver - version 331.38 (ver 7.1) says it's installed. So it did instal,l but somewhere/somehow set off an error report as a crash? If you know me from helping users over the years with XServer and the Linux graphics layer, you know I am not a new, nor normal user. But this an interesting quark. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1351639 Title: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu /libnvidia-opencl.so.331.38', which is also in package nvidia-opencl- icd-331 331.38-0ubuntu7.1 Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Bug description: installing proprietary driver ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-opencl-icd-331-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Fri Aug 1 23:49:06 2014 DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not installed):trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.331.38', which is also in package nvidia-opencl-icd-331 331.38-0ubuntu7.1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.331.38', which is also in package nvidia-opencl-icd-331 331.38-0ubuntu7.1 InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: nvidia-graphics-drivers-331-updates Title: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.331.38', which is also in package nvidia-opencl-icd-331 331.38-0ubuntu7.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1351639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174034] [NEW] gedit not closing, exiting or minimizing.
Public bug reported: (Gnome Fallback) Since upgrade to 13.04- Gedit not exiting from the x decoration or minimizing from the _ decoration. Selecting X will minimze the app. Fill menu will close doc's and exit. Right click on lower taskbar close will quit app... But GTK window taskbar X will not quit. Selecting the lower taskbar, will minimize app. All other desktop app's seem to work normally. ??? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Apr 28 12:03:15 2013 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2013-01-26 (92 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to raring on 2013-04-26 (1 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1174034 Title: gedit not closing, exiting or minimizing. Status in “gedit” package in Ubuntu: New Bug description: (Gnome Fallback) Since upgrade to 13.04- Gedit not exiting from the x decoration or minimizing from the _ decoration. Selecting X will minimze the app. Fill menu will close doc's and exit. Right click on lower taskbar close will quit app... But GTK window taskbar X will not quit. Selecting the lower taskbar, will minimize app. All other desktop app's seem to work normally. ??? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Apr 28 12:03:15 2013 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2013-01-26 (92 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to raring on 2013-04-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1174034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174034] Re: gedit not closing, exiting or minimizing.
One other note- If I select the _ decoration on the gtk.Window, the whole top bar on that window grey's out losing focus... and act's if it is unresponsive. If I then select the app from the lower taskbar, then it regains focus and starts working normally (all working correctly)... until closed and restarted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1174034 Title: gedit not closing, exiting or minimizing. Status in “gedit” package in Ubuntu: New Bug description: (Gnome Fallback) Since upgrade to 13.04- Gedit not exiting from the x decoration or minimizing from the _ decoration. Selecting X will minimze the app. Fill menu will close doc's and exit. Right click on lower taskbar close will quit app... But GTK window taskbar X will not quit. Selecting the lower taskbar, will minimize app. All other desktop app's seem to work normally. ??? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Apr 28 12:03:15 2013 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2013-01-26 (92 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to raring on 2013-04-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1174034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174034] Re: gedit not closing, exiting or minimizing.
I am mistaken in that this error also includes nautilus. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1174034 Title: gedit not closing, exiting or minimizing. Status in “gedit” package in Ubuntu: New Bug description: (Gnome Fallback) Since upgrade to 13.04- Gedit not exiting from the x decoration or minimizing from the _ decoration. Selecting X will minimze the app. Fill menu will close doc's and exit. Right click on lower taskbar close will quit app... But GTK window taskbar X will not quit. Selecting the lower taskbar, will minimize app. All other desktop app's seem to work normally. ??? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Apr 28 12:03:15 2013 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2013-01-26 (92 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to raring on 2013-04-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1174034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174034] Re: gedit not closing, exiting or minimizing.
Working fine in Unity and Gnome3... Problem just in Gnome Fallback. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1174034 Title: gedit not closing, exiting or minimizing. Status in “gedit” package in Ubuntu: New Bug description: (Gnome Fallback) Since upgrade to 13.04- Gedit not exiting from the x decoration or minimizing from the _ decoration. Selecting X will minimze the app. Fill menu will close doc's and exit. Right click on lower taskbar close will quit app... But GTK window taskbar X will not quit. Selecting the lower taskbar, will minimize app. All other desktop app's seem to work normally. ??? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Apr 28 12:03:15 2013 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2013-01-26 (92 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to raring on 2013-04-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1174034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 907311] Re: Not exiting properly? An instance of Brasero is already running, exiting
I am one of those duplicates joining this bug as directed, because someone pointed my bug report as a duplicate to this one. Of note- I have a work-around. I noticed that after I run Brasero and exit, the process is still running. That is why it is not starting a new instance of Brasero. So my fix is to bring up a terminal session cntrlaltT... Type in: pidof Brasero It will return the process ID of four digits long. For example: 8573. If the returned process ID where 8573, then you would type in: kill 8573 to end that process. Once that process is killed, Brasero will run again. Note that this is a work-around. You have to kill the process manually, because brasero is not really exiting gracefully. In fact since it still has a process ID, itis really not exiting... Therefore the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/907311 Title: Not exiting properly? An instance of Brasero is already running, exiting Status in “brasero” package in Ubuntu: Confirmed Status in “brasero” package in Arch Linux: New Bug description: After successfully burning an ISO file (by clicking on it in nautilus) I am unable to burn any more. Double-clicking ISO files has no effect. Running brasero from the launcher does nothing. If I open a terminal to run brasero, I get: $ brasero ** (brasero:4117): WARNING **: An instance of Brasero is already running, exiting The only solution is to $ killall brasero (Edit to add: there is no icon in the dock(?) indicating that brasero is running, and alt-tab does not show it, so I can't switch to it). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brasero 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic-pae 3.0.9 Uname: Linux 3.0.0-14-generic-pae i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Wed Dec 21 12:14:15 2011 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: Upgraded to oneiric on 2011-10-14 (67 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/907311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1145286] [NEW] Brasero runs once then fails
Public bug reported: On a fresh system boot, Brasero runs well. After burning ISO to disk and closing application, Brasero will try to start (Starting Brasero), then just go away. Have to reboot to get it going again. Seem's like Brasero is not exiting gracefully, so cannot restart. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: brasero 3.4.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 13:32:31 2013 InstallationDate: Installed on 2013-01-26 (37 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: Upgraded to quantal on 2013-02-23 (9 days ago) ** Affects: brasero (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1145286 Title: Brasero runs once then fails Status in “brasero” package in Ubuntu: New Bug description: On a fresh system boot, Brasero runs well. After burning ISO to disk and closing application, Brasero will try to start (Starting Brasero), then just go away. Have to reboot to get it going again. Seem's like Brasero is not exiting gracefully, so cannot restart. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: brasero 3.4.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 13:32:31 2013 InstallationDate: Installed on 2013-01-26 (37 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: Upgraded to quantal on 2013-02-23 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1145286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1145286] Re: Brasero runs once then fails
I've been using Ubuntu since 8.04LTS... And I've been testing U+1 for 4-5 years on other boxes and servers here, but this is on my main everyday box (no U+1 dev). I cleaned things up on this one and did a fresh re-Install 37 days ago. It did this in v12.04 also (7 days ago upgraded this box to v12.10 ). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1145286 Title: Brasero runs once then fails Status in “brasero” package in Ubuntu: New Bug description: On a fresh system boot, Brasero runs well. After burning ISO to disk and closing application, Brasero will try to start (Starting Brasero), then just go away. Have to reboot to get it going again. Seem's like Brasero is not exiting gracefully, so cannot restart. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: brasero 3.4.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 13:32:31 2013 InstallationDate: Installed on 2013-01-26 (37 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: Upgraded to quantal on 2013-02-23 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1145286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1145286] Re: Brasero runs once then fails
//*** ~$ brasero -g --brasero-media-debug log 21 ~$ cat log ** (brasero:7386): WARNING **: An instance of Brasero is already running, exiting ~$ pidof brasero 2585 :~$ kill 2585 ***// ...and it works again without a reboot. But the new instance also stays loaded after exit. This may be a duplicate of bug #972962... But that bug was on v12.04 n commandline. This is on v12.10 and both commandline and through GUI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1145286 Title: Brasero runs once then fails Status in “brasero” package in Ubuntu: New Bug description: On a fresh system boot, Brasero runs well. After burning ISO to disk and closing application, Brasero will try to start (Starting Brasero), then just go away. Have to reboot to get it going again. Seem's like Brasero is not exiting gracefully, so cannot restart. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: brasero 3.4.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Mar 4 13:32:31 2013 InstallationDate: Installed on 2013-01-26 (37 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brasero UpgradeStatus: Upgraded to quantal on 2013-02-23 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1145286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
