[Desktop-packages] [Bug 2017841] [NEW] Firefox drag/drop url onto desktop crashes ubuntu login session
Public bug reported: Situation - while browsing I want to save page's url to desktop (likely any folder). I drag the url (by padlock icon in the address bar) onto my desktop folder to save shortcut to the page (for later view, to share it etc). The ubuntu user session (Wayland) will lock up and crash (bringing me back to user login screen) the moment I move the mouse (dragging the url) to FF windows boundary. Sometimes I'll get as far hovering over open desktop area but it'll crash withing seconds from me starting the task. No shortcut is saved to the desktop. FireFox can't restore session when launched again after login to system (I tried even restarting the pc before attempts at launching FF again). All you get is black/blank FF window and spinning cursor. Initially, the only way to get FF working again appeared to be to kill open FF window, switch to in private mode - this one will start fine and the next time FF would start normally. The session from before the crash would be gone though, really annoying for anyone with multiple open tabs. I'm quite certain that this was the reason why I'd given up on FF snap in 22.04 (normal/legacy install did not have the problem) but the same (?) problem on 23.04 forced me to have a closer look at what's going on, recovery options and to sing up/report the bug. What I've also noticed is that if following the crash I'd open in private FF windows 1st (instead of trying to open normal browser session only to have to terminate the browser showing blank window) and only then start normal FF session, FF would restore my tabs from before the crash. This is of little use now that I have to figure how to go back to my old session (I'll backtrack it somehow but this is pita). I'm tempted to pull the plug on snap FF again and move back to less fancy but more resilient setup (and with greater functionality). Btw, the same crash can be triggered when doing drag and drop from bookmark or history manager in FF. Chromium snap install does not crash the login/Wayland session but url drag and drop attempt just does nothing anyway, no file is left on the desktop. Quite a basic functionality that works from any browser on Windows or macOS, seems like a great omission. An unfortunate choice if limited interactivity with user's own file system was just inherent to snap packaged software. I understand security but it's personal computer desktop environment 1st. I'm not sure of any security impact but this surely does not look good and is definitely a risk of data/work lost (luckily I did not have whole lot of open windows besides terminal). ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2017841 Title: Firefox drag/drop url onto desktop crashes ubuntu login session Status in firefox package in Ubuntu: New Bug description: Situation - while browsing I want to save page's url to desktop (likely any folder). I drag the url (by padlock icon in the address bar) onto my desktop folder to save shortcut to the page (for later view, to share it etc). The ubuntu user session (Wayland) will lock up and crash (bringing me back to user login screen) the moment I move the mouse (dragging the url) to FF windows boundary. Sometimes I'll get as far hovering over open desktop area but it'll crash withing seconds from me starting the task. No shortcut is saved to the desktop. FireFox can't restore session when launched again after login to system (I tried even restarting the pc before attempts at launching FF again). All you get is black/blank FF window and spinning cursor. Initially, the only way to get FF working again appeared to be to kill open FF window, switch to in private mode - this one will start fine and the next time FF would start normally. The session from before the crash would be gone though, really annoying for anyone with multiple open tabs. I'm quite certain that this was the reason why I'd given up on FF snap in 22.04 (normal/legacy install did not have the problem) but the same (?) problem on 23.04 forced me to have a closer look at what's going on, recovery options and to sing up/report the bug. What I've also noticed is that if following the crash I'd open in private FF windows 1st (instead of trying to open normal browser session only to have to terminate the browser showing blank window) and only then start normal FF session, FF would restore my tabs from before the crash. This is of little use now that I have to figure how to go back to my old session (I'll backtrack it somehow but this is pita). I'm tempted to pull the plug on snap FF again and move back to less fancy but more resilient setup (and with greater functionality). Btw, the same crash can be triggered when doing drag and drop from bookmark or history
[Desktop-packages] [Bug 2017832] [NEW] No audio/sound after fresh 23.4 install, only dummy audio
Public bug reported: Did a fresh install of 23.4 and there is no working audio. Sound settings only show a "dummy output" audio device. If I plug headphones into the headphone jack, then a device shows up in sound settings: "Headphones - Tiger Lake-LP Smart Sound Technology Audio Controller". Then, if I try "test" and try to test the speakers, I hear nothing. If I open firefox and play a youtube video: 1. If I have headphones plugged in, I hear the audio over the internal speaker, not the headphones. 2. If I do not have the headphones plugged in, I hear nothing (dummy ouput in sound settings). Pipwire appears to be running: steve@steve-chromebook:~$ systemctl --user | grep wire pipewire-pulse.service loaded active running PipeWire PulseAudio pipewire.service loaded active running PipeWire Multimedia Service wireplumber.service loaded active running Multimedia Service Session Manager pipewire-pulse.socket loaded active running PipeWire PulseAudio pipewire.socket loaded active running PipeWire Multimedia System Socket Intel sound drivers appear to be running: $ lsmod | grep snd | grep intel snd_soc_intel_hda_dsp_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_maxim_common20480 1 snd_soc_sof_rt5682 snd_soc_intel_sof_realtek_common24576 1 snd_soc_sof_rt5682 snd_sof_pci_intel_tgl16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel57344 1 snd_sof_intel_hda_common snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 311296 6 snd_soc_sof_rt5682,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_intel_sof_realtek_common,snd_sof_probes,snd_sof_intel_hda snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common snd_hda_ext_core 36864 4 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_soc_acpi_intel_match77824 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common soundwire_bus 110592 5 regmap_sdw,soundwire_intel,soundwire_generic_allocation,soundwire_cadence,snd_soc_max98373_sdw snd_hda_intel 61440 0 snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg snd_soc_core 417792 16 snd_soc_max98373,snd_soc_sof_rt5682,snd_soc_rt5682,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_intel_sof_realtek_common,snd_soc_hdac_hda,snd_soc_max98373_i2c,snd_soc_intel_sof_maxim_common,snd_soc_max98373_sdw,snd_sof_probes,snd_soc_dmic,snd_soc_rt5682s,snd_soc_rt5682_i2c snd_hda_codec 204800 5 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_intel_hda_dsp_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_hda_core 139264 9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_soc_intel_hda_dsp_common,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_sof_intel_hda snd_pcm 192512 18 snd_hda_codec_hdmi,snd_hda_intel,snd_soc_sof_rt5682,snd_soc_rt5682,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_intel_sof_realtek_common,snd_soc_max98373_i2c,snd_soc_core,snd_sof_utils,snd_soc_max98373_sdw,snd_hda_core,snd_soc_rt5682s,snd_pcm_dmaengine snd 135168 18 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_soc_sof_rt5682,snd_hda_codec,snd_sof,snd_timer,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Alsa info is here: http://alsa-project.org/db/?f=ea6f792b4f92dd965494ec53df480554c50c4456 This info shows some errors in dmesg, but I have no idea if they are expected or indicate a problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 1388 F wireplumber /dev/snd/seq:steve 1385 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 20:33:57 2023 InstallationDate: Installed on 2023-04-27 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64
[Desktop-packages] [Bug 2017780] Re: gdm was failing to start for me, because smarcard.desktop was missing
I'm sorry, but that's not a legit action: removing a required component is not the way to handle this case. smart card login can be disabled "properly" by using gsettings sudo -u gdm env DCONF_PROFILE=gdm settings set \ org.gnome.login-screen enable-smartcard-authentication false Or use https://github.com/realmazharhussain/gdm-settings See more on https://wiki.archlinux.org/title/GDM for further details on dconf settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2017780 Title: gdm was failing to start for me, because smarcard.desktop was missing Status in gdm3 package in Ubuntu: Won't Fix Status in gnome-settings-daemon package in Ubuntu: Won't Fix Bug description: gdm was failing to start for me, because smarcard.desktop was missing I use yubikey for gpg & ssh, and not for "smartcard authentication". I tried hard to not have any smartcard login on my gdm screen. I removed /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop which i think is an allowed action. I installed updates, gdm didn't start anymore because Smartcard.desktop is required to start settion and was unable to start it without it. Doing sudo apt install --reinstall -o Dpkg::Options::=--force-confmiss gnome-settings-daemon ressurected ability to start gdm But also ressurected Smartcard.desktop. How do I disable gdm to not attempt smartcard logins, when my system a) is not enrolled to use or trust any smarcards via pam or anything b) it is a yubikey with gpg certs c) i want gdm to still show and allow login with locally configured user despite smartcard plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2017780/+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 2017780] Re: gdm was failing to start for me, because smarcard.desktop was missing
** Changed in: gdm3 (Ubuntu) Status: Triaged => Won't Fix ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2017780 Title: gdm was failing to start for me, because smarcard.desktop was missing Status in gdm3 package in Ubuntu: Won't Fix Status in gnome-settings-daemon package in Ubuntu: Won't Fix Bug description: gdm was failing to start for me, because smarcard.desktop was missing I use yubikey for gpg & ssh, and not for "smartcard authentication". I tried hard to not have any smartcard login on my gdm screen. I removed /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop which i think is an allowed action. I installed updates, gdm didn't start anymore because Smartcard.desktop is required to start settion and was unable to start it without it. Doing sudo apt install --reinstall -o Dpkg::Options::=--force-confmiss gnome-settings-daemon ressurected ability to start gdm But also ressurected Smartcard.desktop. How do I disable gdm to not attempt smartcard logins, when my system a) is not enrolled to use or trust any smarcards via pam or anything b) it is a yubikey with gpg certs c) i want gdm to still show and allow login with locally configured user despite smartcard plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2017780/+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 2013542] Re: [lunar] windows size/position is not saved for some apps
I experience this with Discord and the Heroic Games Launcher. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2013542 Title: [lunar] windows size/position is not saved for some apps Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, Lunar up to date, Ubuntu session, Wayland or X11 1) open Synaptic not in full screen 2) change window size to full screen 3) close Synaptic 4) open Synaptic 5) its window is not maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013542/+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 2017819] [NEW] Many broken symlinks and a few empty directories.
Public bug reported: Broken symlinks- ./Humanity/apps/24/catfish.svg ./Humanity/apps/24/x-system-software-sources.svg ./Humanity/apps/24/panel-searchtool.svg ./Humanity/apps/24/pk-package-sources.svg ./Humanity/apps/24/xfce4-appfinder.svg ./Humanity/apps/24/gpk-repo.svg ./Humanity/apps/24/edit-urpm-sources.svg ./Humanity/apps/24/gnome-searchtool.svg ./Humanity/apps/48/catfish.svg ./Humanity/apps/48/x-system-software-sources.svg ./Humanity/apps/48/panel-searchtool.svg ./Humanity/apps/48/pk-package-sources.svg ./Humanity/apps/48/xfce4-appfinder.svg ./Humanity/apps/48/gpk-repo.svg ./Humanity/apps/48/edit-urpm-sources.svg ./Humanity/apps/48/gnome-searchtool.svg ./Humanity/status/48/aptdaemon-update-cache.svg ./Humanity/stock/24/stock_zoom-page.svg ./Humanity/stock/22/stock_zoom-page.svg ./Humanity/stock/48/stock_zoom-page.svg Empty directories- ./Humanity-Dark/places/32 ./Humanity-Dark/actions/24 ./Humanity-Dark/actions/22 ** Affects: humanity Importance: Undecided Status: New ** Affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal humanity icons jammy kinetic lunar mantic ubuntu ** Also affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/2017819 Title: Many broken symlinks and a few empty directories. Status in Humanity: New Status in humanity-icon-theme package in Ubuntu: New Bug description: Broken symlinks- ./Humanity/apps/24/catfish.svg ./Humanity/apps/24/x-system-software-sources.svg ./Humanity/apps/24/panel-searchtool.svg ./Humanity/apps/24/pk-package-sources.svg ./Humanity/apps/24/xfce4-appfinder.svg ./Humanity/apps/24/gpk-repo.svg ./Humanity/apps/24/edit-urpm-sources.svg ./Humanity/apps/24/gnome-searchtool.svg ./Humanity/apps/48/catfish.svg ./Humanity/apps/48/x-system-software-sources.svg ./Humanity/apps/48/panel-searchtool.svg ./Humanity/apps/48/pk-package-sources.svg ./Humanity/apps/48/xfce4-appfinder.svg ./Humanity/apps/48/gpk-repo.svg ./Humanity/apps/48/edit-urpm-sources.svg ./Humanity/apps/48/gnome-searchtool.svg ./Humanity/status/48/aptdaemon-update-cache.svg ./Humanity/stock/24/stock_zoom-page.svg ./Humanity/stock/22/stock_zoom-page.svg ./Humanity/stock/48/stock_zoom-page.svg Empty directories- ./Humanity-Dark/places/32 ./Humanity-Dark/actions/24 ./Humanity-Dark/actions/22 To manage notifications about this bug go to: https://bugs.launchpad.net/humanity/+bug/2017819/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
** Tags removed: sts-sponsor ** Tags added: se-sponsor-halves -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in gvfs package in Ubuntu: New Status in tracker-miners package in Ubuntu: Fix Released Status in gvfs source package in Bionic: Confirmed Status in tracker-miners source package in Bionic: Won't Fix Status in gvfs source package in Focal: Confirmed Status in tracker-miners source package in Focal: In Progress Status in gvfs source package in Jammy: Confirmed Status in tracker-miners source package in Jammy: In Progress Status in gvfs source package in Kinetic: Confirmed Status in tracker-miners source package in Kinetic: In Progress Status in gvfs source package in Lunar: Confirmed Status in tracker-miners source package in Lunar: Fix Released Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 Focal requires four additional patches to solve the issue, namely: commit 8065985c8d818414a36fe151862afdf42c5eda8a Author:
[Desktop-packages] [Bug 2017573] Re: Font hinting broken on Plasma 23.04
@mrvanes: Picking the appropriate affected package is sometimes a trial and error exercise. This bug is an example of that. Possibly plasma-desktop isn't the right package. But OTOH that's where we see the issue, i.e. the refusal to honor the font hinting value. And by picking plasma-desktop, the Kubuntu developers will see this bug. In the end we may conclude that it should be reported upstream. But which upstream? Well, my belief is that the Kubuntu devs have the best insight in that respect. I have played a little more with my Kubuntu 23.04 installation. While it apparently recognizes fontconfig's setting with respect to hinting, I can confirm that the setting is not honored when rendering. Since it's a VM, sending screenshots is a bit tricky, so I won't do that. I think you already have provided sufficient evidence which supports the existence of an issue. @Dmitriy: Since you haven't opposed my reply to you, I dropped gnome- desktop as an affected package. If you experience font rendering issues in Ubuntu/GNOME, please file a separate bug about that. ** No longer affects: gnome-desktop (Ubuntu) ** Changed in: plasma-desktop (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2017573 Title: Font hinting broken on Plasma 23.04 Status in plasma-desktop package in Ubuntu: Confirmed Bug description: Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting for all non-commercial fonts seems broken. I used to have decent if not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only fonts that still hint correctly are Microsoft's Verdana and Tahoma etc. Not sure whether the devide is exactly along this line, but it stands out. Tried regenerating font cache (fc-cache -rv) but that didn't help. Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.3.0 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Notebook Product Name: N141CU System Version: Not Applicable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/2017573/+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 1268556] Re: 8086:1502 [Fujitsu D3076-S1x] Ethernet disconnecting at boot and later
** Changed in: network-manager (Ubuntu) Status: New => Fix Released -- 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/1268556 Title: 8086:1502 [Fujitsu D3076-S1x] Ethernet disconnecting at boot and later Status in network-manager package in Ubuntu: Fix Released Bug description: Fresh install XUbuntu 12.04. After boot network interface is down. After unplugging and plugging back network cable, network is up and running again. Later (randomly) it may go off again. Again, unplugging and plugging back network cable helps. Ethernet card is onboard Intel. Mainboard: FUJITSU D3076-S1 Same problem happens with onboard ethernet with Intel mainboard DH61BE. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-58-generic 3.2.0-58.88 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1641 F xfce4-volumed user 1718 F pulseaudio /dev/snd/controlC0: user 1641 F xfce4-volumed user 1718 F pulseaudio CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfb22 irq 50' Mixer name : 'Conexant CX20642' Components : 'HDA:14f150a2,173411b0,00100100' Controls : 19 Simple ctrls : 9 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfb08 irq 17' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,10de094a,00100100' Controls : 12 Simple ctrls : 2 Date: Mon Jan 13 12:02:04 2014 HibernationDevice: RESUME=UUID=324bb3ce-d9ee-4142-a94d-1382ec436191 InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130822) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. MachineType: FUJITSU D3076-S1 MarkForUpload: True ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-58-generic root=UUID=2d4ccd09-d6c3-47ee-80ad-14977144d770 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.2.0-58-generic N/A linux-backports-modules-3.2.0-58-generic N/A linux-firmware1.79.9 RfKill: SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2012 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.4.0 R1.12.0 for D3076-S1x dmi.board.name: D3076-S1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3076-S1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.4.0R1.12.0forD3076-S1x:bd09/20/2012:svnFUJITSU:pnD3076-S1:pvr:rvnFUJITSU:rnD3076-S1:rvrS26361-D3076-S1:cvnFUJITSU:ct6:cvr: dmi.product.name: D3076-S1 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1268556/+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 2017804] [NEW] "Don't show this message again" button has no effect
Public bug reported: Since my upgrade to Ubuntu 23.04 I get annoying popups I've never seen before, especially when waking the computer from suspend, telling me e.g. that my connection to the WiFi network was lost or restored. Although these popups have a "Don't show this message again" button, that button seems to have no effect and I can't figure out how to stop the dialogs from appearing. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 26 13:26:32 2023 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-10 (1932 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp4s0 proto dhcp src 192.168.1.202 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.202 metric 600 SourcePackage: network-manager UpgradeStatus: Upgraded to lunar on 2023-04-21 (5 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-10-21T17:11:24 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 connected started full enabled enabled enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "example of the dialog I'm seeing" https://bugs.launchpad.net/bugs/2017804/+attachment/5668966/+files/Screenshot%20from%202023-04-25%2009-01-03.png -- 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/2017804 Title: "Don't show this message again" button has no effect Status in network-manager package in Ubuntu: New Bug description: Since my upgrade to Ubuntu 23.04 I get annoying popups I've never seen before, especially when waking the computer from suspend, telling me e.g. that my connection to the WiFi network was lost or restored. Although these popups have a "Don't show this message again" button, that button seems to have no effect and I can't figure out how to stop the dialogs from appearing. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 26 13:26:32 2023 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-01-10 (1932 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp4s0 proto dhcp src 192.168.1.202 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.202 metric 600 SourcePackage: network-manager UpgradeStatus: Upgraded to lunar on 2023-04-21 (5 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-10-21T17:11:24 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2017804/+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 2017333] Re: Some Area in Top right corner of the screen is not clickable.
Yes, the problem was Anydesk. Thank you for the tip. Have followed the above mentioned step, and now I'm able to access that area. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Incomplete => Opinion ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2017333 Title: Some Area in Top right corner of the screen is not clickable. Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: https://www.reddit.com/r/Ubuntu/comments/12tyiwf/top_right_area_is_not_clickable_in_ubuntu_2304_i/ This link contains the visual representation and more details about the bug. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 12:10:32 2023 DistUpgraded: 2023-04-21 16:05:44,447 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81ec] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ec] InstallationDate: Installed on 2022-04-01 (385 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 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/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: HP HP Notebook ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=358a40b6-0ed5-4812-8281-fbd535f676fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 12/17/2019 dmi.bios.release: 15.48 dmi.bios.vendor: Insyde dmi.bios.version: F.48 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.61 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 61.61 dmi.modalias: dmi:bvnInsyde:bvrF.48:bd12/17/2019:br15.48:efr61.61:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.61:cvnHP:ct10:cvrChassisVersion:skuW6T44PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: W6T44PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2017333/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
The attachment "mysuperpatch.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in ubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 1993900] Re: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse
@ermshiperete Yes. And the *same* problem here in Ubuntu 23.04 (Xorg) too... -- 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/1993900 Title: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse Status in gnome-control-center package in Ubuntu: Confirmed Bug description: As far as I remember, this problem was not present in the previous versions of Ubuntu (Xorg): After selecting "Switch input sources individually for each window" at the "GNOME Settings" / "Keyboard / Input source switching" section, the keyboard layout can be changed for each window using the keyboard shortcut (Windows Key+Space), however when the selection is attempted using the mouse, nothing is changed and the current layout stays as is. The problem is that I can use the keyboard shortcut on a local machine; however, I have to use the mouse for a remote desktop, since the key combination is captured by the local machine in this case. Wayland seems to work OK in this respect. Ref: https://askubuntu.com/questions/1436720/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Oct 22 19:02:15 2022 InstallationDate: Installed on 2019-03-08 (1324 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-29 (176 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993900/+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 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1025.26~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 (5.19.0-1025.26~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1993900] Re: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1993900 Title: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse Status in gnome-control-center package in Ubuntu: Confirmed Bug description: As far as I remember, this problem was not present in the previous versions of Ubuntu (Xorg): After selecting "Switch input sources individually for each window" at the "GNOME Settings" / "Keyboard / Input source switching" section, the keyboard layout can be changed for each window using the keyboard shortcut (Windows Key+Space), however when the selection is attempted using the mouse, nothing is changed and the current layout stays as is. The problem is that I can use the keyboard shortcut on a local machine; however, I have to use the mouse for a remote desktop, since the key combination is captured by the local machine in this case. Wayland seems to work OK in this respect. Ref: https://askubuntu.com/questions/1436720/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Oct 22 19:02:15 2022 InstallationDate: Installed on 2019-03-08 (1324 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-29 (176 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993900/+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 1993900] Re: "Switch input sources individually for each window" does not work when a keyboard layout is selected using the mouse
I see the same behavior in Ubuntu 22.10 when running X11 ("Ubuntu on
Xorg"). I don't see this bug with Wayland.
--
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/1993900
Title:
"Switch input sources individually for each window" does not work when
a keyboard layout is selected using the mouse
Status in gnome-control-center package in Ubuntu:
Confirmed
Bug description:
As far as I remember, this problem was not present in the previous
versions of Ubuntu (Xorg):
After selecting "Switch input sources individually for each window" at
the "GNOME Settings" / "Keyboard / Input source switching" section,
the keyboard layout can be changed for each window using the keyboard
shortcut (Windows Key+Space), however when the selection is attempted
using the mouse, nothing is changed and the current layout stays as
is.
The problem is that I can use the keyboard shortcut on a local
machine; however, I have to use the mouse for a remote desktop, since
the key combination is captured by the local machine in this case.
Wayland seems to work OK in this respect.
Ref: https://askubuntu.com/questions/1436720/
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Oct 22 19:02:15 2022
InstallationDate: Installed on 2019-03-08 (1324 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to jammy on 2022-04-29 (176 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993900/+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 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1026.29~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 (5.19.0-1026.29~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1036.40~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 (5.15.0-1036.40~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2017794] [NEW] selecting text problem when app runs full screen
Public bug reported: When Text editor runs full screen, it is not possible to select (with the mouse) the portion of text which is in the bottom of the screen. When app doesn't run full screen, the behavior goes back to normal : selecting text while moving pointer in the bottom of the window makes text move up, so that the text selection extends. Precision : Ubuntu 23.04, Gnome 44, some Gnome extensions installed but not the one that creates a taskbar at the bottom of the screen ; interface configured with nothing at the bottom of the screen ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-text-editor selection text -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2017794 Title: selecting text problem when app runs full screen Status in gnome-text-editor package in Ubuntu: New Bug description: When Text editor runs full screen, it is not possible to select (with the mouse) the portion of text which is in the bottom of the screen. When app doesn't run full screen, the behavior goes back to normal : selecting text while moving pointer in the bottom of the window makes text move up, so that the text selection extends. Precision : Ubuntu 23.04, Gnome 44, some Gnome extensions installed but not the one that creates a taskbar at the bottom of the screen ; interface configured with nothing at the bottom of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2017794/+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 2017333] Re: Some Area in Top right corner of the screen is not clickable.
I opened a bug for gnome-shell-extension-appindicator on Github https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/438 ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #438 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/438 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2017333 Title: Some Area in Top right corner of the screen is not clickable. Status in gnome-shell-extension-appindicator package in Ubuntu: Incomplete Bug description: https://www.reddit.com/r/Ubuntu/comments/12tyiwf/top_right_area_is_not_clickable_in_ubuntu_2304_i/ This link contains the visual representation and more details about the bug. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 12:10:32 2023 DistUpgraded: 2023-04-21 16:05:44,447 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81ec] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ec] InstallationDate: Installed on 2022-04-01 (385 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 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/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: HP HP Notebook ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=358a40b6-0ed5-4812-8281-fbd535f676fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 12/17/2019 dmi.bios.release: 15.48 dmi.bios.vendor: Insyde dmi.bios.version: F.48 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.61 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 61.61 dmi.modalias: dmi:bvnInsyde:bvrF.48:bd12/17/2019:br15.48:efr61.61:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.61:cvnHP:ct10:cvrChassisVersion:skuW6T44PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: W6T44PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2017333/+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 2016395] Re: control-center sound using audio devices without consent
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged -- 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/2016395 Title: control-center sound using audio devices without consent Status in gnome-control-center package in Ubuntu: Triaged Bug description: (Reporting for blind user ken) gnome-control-center sound is forcing the selection of an input device you do not have consent to use.The only option listed is CM108 microphone. None is not an option; it needs to be. Motherboard audio is also missing. Just because an audio device exists does not mean you have consent to use it for desktop audio purposes. NONE must always be an option. Audio output device also lacks none, though in this case it isn't causing an issue because there is another audio output device. However, using this audio output device without permission is a federal crime. Unauthorized radio transmissions are not allowed. Reproduce: * * Plug in digirig mobile which contains a USB hub, CM108 audio, and CP210 serial and ham radio rig interface circuitry. * Enable pipewire as described here: https://gist.github.com/the-spyke/2de98b22ff4f978ebf0650c90e82027e?permalink_comment_id=4116017 * Open control-center sound. * Try to set output device to none. Ubuntu 22.04.2 LTS Linux ken-OptiPlex-760 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux This is by no means the only audio device that is not yours to use indiscriminately. There are many uses for audio devices that are not for user interaction. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.6 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 15 18:17:39 2023 InstallationDate: Installed on 2018-05-05 (1806 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-12-05 (131 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2016395/+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 2017333] Re: Some Area in Top right corner of the screen is not clickable.
I experience this bug in Wayland and XORG. If I hover over the "ghost" area I get mouse pointer hints for two of my tray-applications: anydesk and Zoiper desktop. If I disable the Appindicator shell extension the problem is gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2017333 Title: Some Area in Top right corner of the screen is not clickable. Status in gnome-shell-extension-appindicator package in Ubuntu: Incomplete Bug description: https://www.reddit.com/r/Ubuntu/comments/12tyiwf/top_right_area_is_not_clickable_in_ubuntu_2304_i/ This link contains the visual representation and more details about the bug. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 12:10:32 2023 DistUpgraded: 2023-04-21 16:05:44,447 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81ec] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ec] InstallationDate: Installed on 2022-04-01 (385 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio 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/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: HP HP Notebook ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=358a40b6-0ed5-4812-8281-fbd535f676fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 12/17/2019 dmi.bios.release: 15.48 dmi.bios.vendor: Insyde dmi.bios.version: F.48 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.61 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 61.61 dmi.modalias: dmi:bvnInsyde:bvrF.48:bd12/17/2019:br15.48:efr61.61:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.61:cvnHP:ct10:cvrChassisVersion:skuW6T44PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: W6T44PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2017333/+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 2017780] Re: gdm was failing to start for me, because smarcard.desktop was missing
** Changed in: gdm3 (Ubuntu) Importance: Undecided => Critical ** Changed in: gdm3 (Ubuntu) Status: New => Triaged ** Tags added: jammy regression-update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2017780 Title: gdm was failing to start for me, because smarcard.desktop was missing Status in gdm3 package in Ubuntu: Triaged Status in gnome-settings-daemon package in Ubuntu: New Bug description: gdm was failing to start for me, because smarcard.desktop was missing I use yubikey for gpg & ssh, and not for "smartcard authentication". I tried hard to not have any smartcard login on my gdm screen. I removed /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop which i think is an allowed action. I installed updates, gdm didn't start anymore because Smartcard.desktop is required to start settion and was unable to start it without it. Doing sudo apt install --reinstall -o Dpkg::Options::=--force-confmiss gnome-settings-daemon ressurected ability to start gdm But also ressurected Smartcard.desktop. How do I disable gdm to not attempt smartcard logins, when my system a) is not enrolled to use or trust any smarcards via pam or anything b) it is a yubikey with gpg certs c) i want gdm to still show and allow login with locally configured user despite smartcard plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2017780/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions
** Patch added: "mysuperpatch.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5668944/+files/mysuperpatch.debdiff -- 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/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in ubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 2017786] [NEW] update script in ubuntu-meta not handling germinate or specified versions
Public bug reported: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- 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/2017786 Title: update script in ubuntu-meta not handling germinate or specified versions Status in ubuntu-meta package in Ubuntu: New Bug description: update script handled debootstrap and devscripts, does not handle germinate. also doesn't handle potential specified versions in the package directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 2016315] Re: mouse and touchpad panel: assets have black background
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2016315 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please attach a screenshot of what you are seeing. What is the output of this command? gsettings get org.gnome.desktop.interface gtk-theme -- 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/2016315 Title: mouse and touchpad panel: assets have black background Status in gnome-control-center package in Ubuntu: New Bug description: The assets used in mouse and touchpad panel have black background that is not present in upstream assets. Perhaps this is caused during improper rendering of assets from the script used for changing colors ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2016315/+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 2017498] Re: crashes trying to open the mouse screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2017498 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/2017498 Title: crashes trying to open the mouse screen Status in gnome-control-center package in Ubuntu: Confirmed Bug description: gnome-control-center crashes on ubuntu 23.04 when trying to open the mouse screen Steps to reproduce: 1. In GNOME Settings, navigate to the mouse screen. The control center crashes (i.e., the window closes instead of showing the mouse screen). 2. Start GNOME Settings again, e.g., using GNOME Shell or by running the following command from the terminal: `gnome-control-center`. The main window does not show. Instead, the commandline output prints an error message as follows: Commandline output: ``` gnome-control-center --verbose 21:10:51.6276 GStreamer-Play[32248]: ERROR: GtkGstPlay: 'playbin' element not found, please check your setup [1]32248 trace trap (core dumped) gnome-control-center --verbose ``` More observations: Note, this happens reproducably. I just recently upgraded to ubuntu 23.04, which means I am running GNOME 44. I am now unable to start the gnome-control-center. It happens in wayland and xorg sessions. I am using an intel x86 laptop, a lenovo thinkpad x1 carbon. Workaround: The following workaround allows to start gnome-control- center again, but does not allow to access the mouse panel. In dconf editor, reset `org/gnome/control-center/last-panel'. The control center will then open successfully. I think this indicates that the mouse panel causes gnome-control-center to crash. Upstream ticket over at GNOME's gitlab project: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2459 Upstream analysis by Felipe Borges, maintainer of the upstream project: > The issue seems to be about Ubuntu packaging not including the needed dependencies for the GtkPicture videos we now show in the Mouse panel. > Could you please file this issue downstream in the Ubuntu bug tracker? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017498/+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 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.15/5.15.0-1038.45~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.15 (5.15.0-1038.45~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-azure-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2017780] [NEW] gdm was failing to start for me, because smarcard.desktop was missing
Public bug reported: gdm was failing to start for me, because smarcard.desktop was missing I use yubikey for gpg & ssh, and not for "smartcard authentication". I tried hard to not have any smartcard login on my gdm screen. I removed /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop which i think is an allowed action. I installed updates, gdm didn't start anymore because Smartcard.desktop is required to start settion and was unable to start it without it. Doing sudo apt install --reinstall -o Dpkg::Options::=--force-confmiss gnome-settings-daemon ressurected ability to start gdm But also ressurected Smartcard.desktop. How do I disable gdm to not attempt smartcard logins, when my system a) is not enrolled to use or trust any smarcards via pam or anything b) it is a yubikey with gpg certs c) i want gdm to still show and allow login with locally configured user despite smartcard plugged in ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2017780 Title: gdm was failing to start for me, because smarcard.desktop was missing Status in gdm3 package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: gdm was failing to start for me, because smarcard.desktop was missing I use yubikey for gpg & ssh, and not for "smartcard authentication". I tried hard to not have any smartcard login on my gdm screen. I removed /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop which i think is an allowed action. I installed updates, gdm didn't start anymore because Smartcard.desktop is required to start settion and was unable to start it without it. Doing sudo apt install --reinstall -o Dpkg::Options::=--force-confmiss gnome-settings-daemon ressurected ability to start gdm But also ressurected Smartcard.desktop. How do I disable gdm to not attempt smartcard logins, when my system a) is not enrolled to use or trust any smarcards via pam or anything b) it is a yubikey with gpg certs c) i want gdm to still show and allow login with locally configured user despite smartcard plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2017780/+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 2016925] Re: Firefox window is visually corrupted after upgrading to Ubuntu 23.04
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2016925 Title: Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+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 2017777] [NEW] hplip
Public bug reported: 1. The release of Ubuntu you are using, via? $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 2. The version of the package you are using, via? $ apt-cache policy hplip hplip: Installed: 3.22.10+dfsg0-1 Candidate: 3.22.10+dfsg0-1 Version table: *** 3.22.10+dfsg0-1 500 500 http://au.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3. What you expected to happen? I expected it to run. 4. What happened instead? this error $ hp-toolbox HP Linux Imaging and Printing System (ver. 3.22.10) HP Device Manager ver. 15.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. QSocketNotifier: Can only be used with threads started with QThread Traceback (most recent call last): File "/usr/bin/hp-toolbox", line 280, in toolbox = ui.DevMgr5(__version__, device_uri, None) ^^ File "/usr/share/hplip/ui5/devmgr5.py", line 238, in __init__ core = CoreInstall(MODE_CHECK) ^^^ File "/usr/share/hplip/installer/core_install.py", line 240, in __init__ self.passwordObj = password.Password(ui_mode) ^^ File "/usr/share/hplip/base/password.py", line 94, in __init__ self.__readAuthType() # self.__authType ^ File "/usr/share/hplip/base/password.py", line 119, in __readAuthType distro_name = get_distro_std_name(os_name) ^^^ NameError: name 'get_distro_std_name' is not defined. Did you mean: 'get_distro_name'? I fixed the bug like this: sudo gvim -p /usr/share/hplip/base/password.py 119#distro_name = get_distro_std_name(os_name) 120distro_name = get_distro_name() I commented out 119 and inserted 120 in it's place then it ran fine. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: hplip 3.22.10+dfsg0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 22:07:57 2023 InstallationDate: Installed on 2023-04-21 (5 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lpstat: device for Brother_HL_2130_series_killashandra: implicitclass://Brother_HL_2130_series_killashandra/ device for HP_OfficeJet_8010: hp:/net/HP_OfficeJet_8010_series?ip=192.168.188.17 device for HP_OfficeJet_8010_killashandra: implicitclass://HP_OfficeJet_8010_killashandra/ device for HP_OfficeJet_8010_series_97968B: implicitclass://HP_OfficeJet_8010_series_97968B/ device for PDF_killashandra: implicitclass://PDF_killashandra/ MachineType: Gigabyte Technology Co., Ltd. X570 UD Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL_2130_series_killashandra.ppd', '/etc/cups/ppd/HP_OfficeJet_8010_series_97968B.ppd', '/etc/cups/ppd/PDF_killashandra.ppd', '/etc/cups/ppd/HP_OfficeJet_8010.ppd', '/etc/cups/ppd/HP_OfficeJet_8010_killashandra.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL_2130_series_killashandra.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010_series_97968B.ppd: Permission denied grep: /etc/cups/ppd/PDF_killashandra.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010_killashandra.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=cc914b12-8999-4260-99ce-6db6d4662c7f ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20:bd07/07/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: hplip (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 hplip in Ubuntu. https://bugs.launchpad.net/bugs/201 Title: hplip
[Desktop-packages] [Bug 2017777] Re: hplip
Note I fixed the bug like this I fixed the bug like this: sudo gvim -p /usr/share/hplip/base/password.py 119 #distro_name = get_distro_std_name(os_name) 120 distro_name = get_distro_name() I commented out 119 and inserted 120 in it's place -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/201 Title: hplip Status in hplip package in Ubuntu: New Bug description: 1. The release of Ubuntu you are using, via? $ lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 2. The version of the package you are using, via? $ apt-cache policy hplip hplip: Installed: 3.22.10+dfsg0-1 Candidate: 3.22.10+dfsg0-1 Version table: *** 3.22.10+dfsg0-1 500 500 http://au.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3. What you expected to happen? I expected it to run. 4. What happened instead? this error $ hp-toolbox HP Linux Imaging and Printing System (ver. 3.22.10) HP Device Manager ver. 15.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. QSocketNotifier: Can only be used with threads started with QThread Traceback (most recent call last): File "/usr/bin/hp-toolbox", line 280, in toolbox = ui.DevMgr5(__version__, device_uri, None) ^^ File "/usr/share/hplip/ui5/devmgr5.py", line 238, in __init__ core = CoreInstall(MODE_CHECK) ^^^ File "/usr/share/hplip/installer/core_install.py", line 240, in __init__ self.passwordObj = password.Password(ui_mode) ^^ File "/usr/share/hplip/base/password.py", line 94, in __init__ self.__readAuthType() # self.__authType ^ File "/usr/share/hplip/base/password.py", line 119, in __readAuthType distro_name = get_distro_std_name(os_name) ^^^ NameError: name 'get_distro_std_name' is not defined. Did you mean: 'get_distro_name'? I fixed the bug like this: sudo gvim -p /usr/share/hplip/base/password.py 119#distro_name = get_distro_std_name(os_name) 120distro_name = get_distro_name() I commented out 119 and inserted 120 in it's place then it ran fine. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: hplip 3.22.10+dfsg0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 22:07:57 2023 InstallationDate: Installed on 2023-04-21 (5 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lpstat: device for Brother_HL_2130_series_killashandra: implicitclass://Brother_HL_2130_series_killashandra/ device for HP_OfficeJet_8010: hp:/net/HP_OfficeJet_8010_series?ip=192.168.188.17 device for HP_OfficeJet_8010_killashandra: implicitclass://HP_OfficeJet_8010_killashandra/ device for HP_OfficeJet_8010_series_97968B: implicitclass://HP_OfficeJet_8010_series_97968B/ device for PDF_killashandra: implicitclass://PDF_killashandra/ MachineType: Gigabyte Technology Co., Ltd. X570 UD Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL_2130_series_killashandra.ppd', '/etc/cups/ppd/HP_OfficeJet_8010_series_97968B.ppd', '/etc/cups/ppd/PDF_killashandra.ppd', '/etc/cups/ppd/HP_OfficeJet_8010.ppd', '/etc/cups/ppd/HP_OfficeJet_8010_killashandra.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL_2130_series_killashandra.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010_series_97968B.ppd: Permission denied grep: /etc/cups/ppd/PDF_killashandra.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010_killashandra.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=cc914b12-8999-4260-99ce-6db6d4662c7f ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Desktop-packages] [Bug 2017770] [NEW] "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else
Public bug reported: Enter code on ubuntu.com/pro/attach is not a clickable url. however ubuntu.com/pro and "register new account" are. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2023-04-26 12-05-00.png" https://bugs.launchpad.net/bugs/2017770/+attachment/5668913/+files/Screenshot%20from%202023-04-26%2012-05-00.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2017770 Title: "Enter code on ubuntu.com/pro/attach" is not clickable URL like everything else Status in software-properties package in Ubuntu: New Bug description: Enter code on ubuntu.com/pro/attach is not a clickable url. however ubuntu.com/pro and "register new account" are. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2017770/+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 2014111] Re: Mouse pointing focus issues
I have found the cause! I have noticed AnyDesk opens when I click around its icon in notification area (actually far below it). Just tried uninstalling it -- the issue solved! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2014111 Title: Mouse pointing focus issues Status in firefox package in Ubuntu: New Bug description: When I hover over Firefox UI elements, it seems like there is a little shift, so it is sometimes hard/impossible to click some elements. E.g. New tab button inaccessible as all. Reproducible only when window is maximized, and only in one of two monitors connected. --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2017-10-07 (2013 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) NonfreeKernelModules: nvidia_modeset nvidia ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Snap: firefox 112.0-2 (latest/stable) SnapChanges: ID Стан Запуск Готово Підсумок 992 Done 2023-04-12T03:08:40+03:00 2023-04-12T03:09:34+03:00 Автоматично перечитати snap-пакунок "firefox" Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2017-10-07 (2013 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) NonfreeKernelModules: nvidia_modeset nvidia ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Snap: firefox 112.0-2 (latest/stable) SnapChanges: ID Стан Запуск Готово Підсумок 992 Done 2023-04-12T03:08:40+03:00 2023-04-12T03:09:34+03:00 Автоматично перечитати snap-пакунок "firefox" Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2017-10-07 (2013 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) NonfreeKernelModules: nvidia_modeset nvidia ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Snap: firefox 112.0-2 (latest/stable) SnapChanges: ID Стан Запуск Готово Підсумок 992 Done 2023-04-12T03:08:40+03:00 2023-04-12T03:09:34+03:00 Автоматично перечитати snap-пакунок "firefox" Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-03-31 (12 days ago) UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2014111/+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 2017762] Re: GLX apps fail to run in X2Go remote desktop
** Also affects: mesa (Debian) Importance: Undecided Status: New ** Also affects: mesa (Fedora) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017762 Title: GLX apps fail to run in X2Go remote desktop Status in mesa package in Ubuntu: New Status in mesa package in Debian: New Status in mesa package in Fedora: New Bug description: GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on Ubuntu LTS 20.04 USER@COMPUTER:~$ glxgears X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 32 Current serial number in output stream: 32 USER@COMPUTER:~$ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 Manually downgrading to mesa-21.x from the Ubuntu 20.04 repository solves the problem: sudo apt purge libgl1-amber-dri sudo dpkg -i \ libegl-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgbm1_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglapi-mesa_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglx-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libxatracker2_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-va-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vdpau-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vulkan-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb sudo apt-mark hold \ libegl-mesa0 \ libgl1-mesa-dri \ libglapi-mesa \ libglx-mesa0 \ mesa-va-drivers \ mesa-vdpau-drivers \ mesa-vulkan-drivers \ libgbm1 \ libxatracker2 There's also a discussion about this on the X2Go user list, but no solution so far (just the workaround to downgrade to mesa 21.x): https://lists.x2go.org/pipermail/x2go-user/2022-June/006825.html Similar problems on Ubuntu 23.-04 with mesa 23.x, although there the error message is different. Tested on several computers with connections from different Linux, Windows and Mac clients. All show the same behaviour: no go with mesa-22.x on Ubuntu-22.04. Success with downgraded mesa. How to replicate: - install ubuntu 22.04 on real hardware or on a VM (tested with QEMU/virt-manager) - apt-get install x2goserver-xsession mesa-utils - make X2Go connection from another client to new install - run 'glxinfo' -> GLX error - downgrade mesa to v. 21.x -> no GLX error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.108.03 Thu Oct 20 05:10:45 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 26 10:41:42 2023 DistUpgraded: 2022-05-12 16:08:31,041 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.108.03, 5.19.0-38-generic, x86_64: installed nvidia/510.108.03, 5.19.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204GL [Quadro M4000] [10de:13f1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204GL [Quadro M4000] [10de:1153] InstallationDate: Installed on 2017-03-24 (2223 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision WorkStation 690 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=a6888b05-975d-4ffe-9cf1-a37038661267 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-05-12 (348 days ago)
[Desktop-packages] [Bug 2017762] [NEW] GLX apps fail to run in X2Go remote desktop
Public bug reported: GLX apps fail to run on Ubuntu LTS 22.04. They used to run fine on Ubuntu LTS 20.04 USER@COMPUTER:~$ glxgears X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 32 Current serial number in output stream: 32 USER@COMPUTER:~$ glxinfo name of display: :50.0 X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply) Serial number of failed request: 27 Current serial number in output stream: 27 Manually downgrading to mesa-21.x from the Ubuntu 20.04 repository solves the problem: sudo apt purge libgl1-amber-dri sudo dpkg -i \ libegl-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgbm1_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglapi-mesa_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libglx-mesa0_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ libxatracker2_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-va-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vdpau-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb \ mesa-vulkan-drivers_21.2.6-0ubuntu0.1~20.04.2_amd64.deb sudo apt-mark hold \ libegl-mesa0 \ libgl1-mesa-dri \ libglapi-mesa \ libglx-mesa0 \ mesa-va-drivers \ mesa-vdpau-drivers \ mesa-vulkan-drivers \ libgbm1 \ libxatracker2 There's also a discussion about this on the X2Go user list, but no solution so far (just the workaround to downgrade to mesa 21.x): https://lists.x2go.org/pipermail/x2go-user/2022-June/006825.html Similar problems on Ubuntu 23.-04 with mesa 23.x, although there the error message is different. Tested on several computers with connections from different Linux, Windows and Mac clients. All show the same behaviour: no go with mesa-22.x on Ubuntu-22.04. Success with downgraded mesa. How to replicate: - install ubuntu 22.04 on real hardware or on a VM (tested with QEMU/virt-manager) - apt-get install x2goserver-xsession mesa-utils - make X2Go connection from another client to new install - run 'glxinfo' -> GLX error - downgrade mesa to v. 21.x -> no GLX error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.108.03 Thu Oct 20 05:10:45 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 26 10:41:42 2023 DistUpgraded: 2022-05-12 16:08:31,041 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/510.108.03, 5.19.0-38-generic, x86_64: installed nvidia/510.108.03, 5.19.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204GL [Quadro M4000] [10de:13f1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204GL [Quadro M4000] [10de:1153] InstallationDate: Installed on 2017-03-24 (2223 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision WorkStation 690 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=a6888b05-975d-4ffe-9cf1-a37038661267 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-05-12 (348 days ago) dmi.bios.date: 04/25/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MY171 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/25/2008:svnDellInc.:pnPrecisionWorkStation690:pvr:rvnDellInc.:rn0MY171:rvrA01:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation 690 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 2017756] [NEW] Pipewire-pulse consuming huge amounts of memory
Public bug reported: I noticed my RAM usage was high. pipewire-pulse is the highest user of RAM on my system. The system has been up for four days. I have used all manner of audio applications in that time, including Slack huddle, Zoom, mpv, VLC and Microsoft Edge (YouTube, Netflix) and Kdenlive. alan@ziggy:~$ pactl stat Currently in use: 7865827 blocks containing 2.1 GiB bytes total. Allocated during whole lifetime: 42983702 blocks containing 3.6 GiB bytes total. Sample cache size: 275.2 KiB alan@ziggy:~$ sudo python3 bin/ps_mem.py | tail 207.7 MiB + 419.6 MiB = 627.2 MiB gnome-shell 227.3 MiB + 455.3 MiB = 682.7 MiB syncthing (2) 385.4 MiB + 855.8 MiB = 1.2 GiB slack (8) 409.5 MiB + 928.5 MiB = 1.3 GiB Discord (8) 4.2 GiB + 8.9 GiB = 13.1 GiB msedge [updated] (45) 14.1 GiB + 28.2 GiB = 42.3 GiB pipewire-pulse - 62.7 GiB = ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire-pulse 0.3.65-3 Uname: Linux 6.2.2-060202-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 10:24:47 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (263 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: pipewire UpgradeStatus: Upgraded to lunar on 2023-01-02 (113 days ago) ** Affects: pipewire Importance: Unknown Status: Unknown ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "Screenshot from 2023-04-26 10-32-36.png" https://bugs.launchpad.net/bugs/2017756/+attachment/5668843/+files/Screenshot%20from%202023-04-26%2010-32-36.png ** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #1840 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1840 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1840 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2017756 Title: Pipewire-pulse consuming huge amounts of memory Status in PipeWire: Unknown Status in pipewire package in Ubuntu: New Bug description: I noticed my RAM usage was high. pipewire-pulse is the highest user of RAM on my system. The system has been up for four days. I have used all manner of audio applications in that time, including Slack huddle, Zoom, mpv, VLC and Microsoft Edge (YouTube, Netflix) and Kdenlive. alan@ziggy:~$ pactl stat Currently in use: 7865827 blocks containing 2.1 GiB bytes total. Allocated during whole lifetime: 42983702 blocks containing 3.6 GiB bytes total. Sample cache size: 275.2 KiB alan@ziggy:~$ sudo python3 bin/ps_mem.py | tail 207.7 MiB + 419.6 MiB = 627.2 MiB gnome-shell 227.3 MiB + 455.3 MiB = 682.7 MiB syncthing (2) 385.4 MiB + 855.8 MiB = 1.2 GiB slack (8) 409.5 MiB + 928.5 MiB = 1.3 GiB Discord (8) 4.2 GiB + 8.9 GiB = 13.1 GiB msedge [updated] (45) 14.1 GiB + 28.2 GiB = 42.3 GiB pipewire-pulse - 62.7 GiB = ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire-pulse 0.3.65-3 Uname: Linux 6.2.2-060202-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 10:24:47 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (263 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: pipewire UpgradeStatus: Upgraded to lunar on 2023-01-02 (113 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2017756/+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 2017677] Re: Unable to drag window by title bar
This bug doesn't just affect window movement (dragging), it also fails to properly select the window, so that it doesn't become the foreground window -- 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/2017677 Title: Unable to drag window by title bar Status in xorg package in Ubuntu: New Bug description: >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 Intermittent - more often than not this works fine. However, sometimes unable to move window by left-click & drag on the title bar. Not sure what exact conditions are, maybe when alt-tabbing to a different window or when moving onto a different monitor. Upgraded to 23.04 late yesterday and it's happened about 4 times so far today.When it doesn't work - the dragged window just stays still, but relocating the mouse to lower on the window (say the menu bar) resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 15:48:44 2023 DistUpgraded: 2023-04-24 20:50:34,905 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:1413] InstallationDate: Installed on 2021-12-13 (498 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Entroware Apollo ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=943b6cc2-9015-4dda-8079-67ac161950f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/26/2018 dmi.bios.release: 5.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02E dmi.board.asset.tag: Tag 12345 dmi.board.name: Apollo dmi.board.vendor: Entroware dmi.board.version: EL02R5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Entroware dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02E:bd03/26/2018:br5.2:efr5.2:svnEntroware:pnApollo:pvrEL02R5:rvnEntroware:rnApollo:rvrEL02R5:cvnEntroware:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Apollo dmi.product.sku: Not Applicable dmi.product.version: EL02R5 dmi.sys.vendor: Entroware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017677/+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 2017734] Re: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017734 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2017734/+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 2017734] [NEW] package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017734 Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned Status in gdk-pixbuf package in Ubuntu: New Bug description: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: gdk-pixbuf Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2017734/+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 2017735] [NEW] package rygel 0.42.1-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: rygel 0.42.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: rygel Title: package rygel 0.42.1-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) ** Affects: rygel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rygel in Ubuntu. https://bugs.launchpad.net/bugs/2017735 Title: package rygel 0.42.1-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in rygel package in Ubuntu: New Bug description: Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: rygel 0.42.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 26 08:57:37 2023 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2023-01-24 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: rygel Title: package rygel 0.42.1-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rygel/+bug/2017735/+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 2017722] Re: Update to 112.0.2
Package Information: https://launchpad.net/ubuntu/+source/firefox/112.0.2+build1-0ubuntu0.20.04.1 https://launchpad.net/ubuntu/+source/firefox/112.0.2+build1-0ubuntu0.18.04.1 ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2017722 Title: Update to 112.0.2 Status in firefox package in Ubuntu: Fix Released Bug description: https://www.mozilla.org/en-US/firefox/112.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2017722/+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
