[Desktop-packages] [Bug 1947257] Re: Partial profile loss on upgrade from 21.04 to 21.10
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1947257 Title: Partial profile loss on upgrade from 21.04 to 21.10 Status in firefox package in Ubuntu: Expired Bug description: In the upgrade from 21.04 to 21.10 I noticed it had updated firefox. When restarting some of my profile was kept (themes, addons, etc) but I've noticed my primary window of 50+ tabs was lost. It opened 3 other windows correctly. I tried to find it via "recently closed tabs/windows" but it's not showing up. I have also confirmed there are no duplicate profiles. Silly me assumed it was done correctly and when the upgrade process offered to remove old packages I did so I can't seem to retrieve the old profile. Additional information: lsb_release -rd: Description: Ubuntu 21.10 Release: 21.10 snap package information: snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-21.10 refresh-date: today at 09:00 AEST channels: latest/stable:93.0-1 2021-10-08 (631) 157MB - latest/candidate: 93.0-1 2021-09-28 (631) 157MB - latest/beta: 94.0b5-1 2021-10-13 (650) 157MB - latest/edge: ↑ esr/stable: 78.15.0esr-1 2021-10-04 (637) 148MB - esr/candidate:91.2.0esr-1 2021-09-29 (634) 160MB - esr/beta: ↑ esr/edge: ↑ installed: 93.0-1 (631) 157MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947257/+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 1946434] Re: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3
** Changed in: oem-priority Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946434 Title: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3 Status in OEM Priority Project: Invalid Status in nvidia-prime package in Ubuntu: Invalid Status in nvidia-prime source package in Focal: In Progress Status in nvidia-prime source package in Hirsute: In Progress Bug description: [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946434/+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 1946440] Re: SRU: enable RTD3 only on laptops
** Changed in: oem-priority Status: New => Invalid -- 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/1946440 Title: SRU: enable RTD3 only on laptops Status in OEM Priority Project: Invalid Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946440/+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 1955505] [NEW] Wrong context menu font is displayed when using vte 0.66.2-1
Public bug reported: Expected behaviour: Font should display as expected. Actual behaviour: A monospace font is displayed instead. Steps to reproduce the behaviour: 1. Install Ubuntu MATE 22.04 LTS 2. Launch mate-terminal 3. Do right mouse click to get context menu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mate-terminal 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Dec 21 23:49:21 2021 InstallationDate: Installed on 2021-12-21 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211221) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-desktop Importance: Unknown Status: Unknown ** Affects: mate-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: vte2.91 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "monospaced menu in MATE Terminal" https://bugs.launchpad.net/bugs/1955505/+attachment/5548976/+files/mate-terminal-monospaced-menu.png ** Bug watch added: github.com/mate-desktop/mate-terminal/issues #407 https://github.com/mate-desktop/mate-terminal/issues/407 ** Also affects: mate-desktop via https://github.com/mate-desktop/mate-terminal/issues/407 Importance: Unknown Status: Unknown ** Also affects: vte2.91 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1955505 Title: Wrong context menu font is displayed when using vte 0.66.2-1 Status in MATE Desktop: Unknown Status in mate-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: Expected behaviour: Font should display as expected. Actual behaviour: A monospace font is displayed instead. Steps to reproduce the behaviour: 1. Install Ubuntu MATE 22.04 LTS 2. Launch mate-terminal 3. Do right mouse click to get context menu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mate-terminal 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Dec 21 23:49:21 2021 InstallationDate: Installed on 2021-12-21 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211221) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1955505/+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 1955500] Re: firefox crashes often
I have as extensions: Feedbro GNOME Shell Integration (courtesy of ubuntu) Stylus uBlock Origin -- 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/1955500 Title: firefox crashes often Status in firefox package in Ubuntu: New Bug description: Recently (since ~2021-12-15) firefox has been crashing a lot, often daily. There's no obvious pattern that I can see. Most recent crash logs: Dec 21 12:37:51 cerberus firefox.desktop[755990]: Sandbox: Unexpected EOF, op 0 flags 0200 path /proc/755990/cgroup Dec 21 12:37:51 cerberus firefox.desktop[756121]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755809]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755990]: Exiting due to channel error. ... Dec 21 12:37:51 cerberus firefox.desktop[745228]: [GFX1-]: Receive IPC close with reason=AbnormalShutdown Dec 21 12:37:51 cerberus firefox.desktop[744870]: Exiting due to channel error. ... Previous crash: Dec 20 12:56:53 cerberus kernel: traps: GeckoMain[613052] trap int3 ip:7fa351cc1295 sp:7fff6ba7eea0 error:0 in libglib-2.> Dec 20 12:56:53 cerberus gnome-shell[722119]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[722386]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[615970]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[717612]: Exiting due to channel error. ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 95.0.1+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jlquinn2641 F pulseaudio /dev/snd/controlC0: jlquinn2641 F pulseaudio /dev/snd/controlC2: jlquinn2641 F pulseaudio /dev/snd/controlC1: jlquinn2641 F pulseaudio BuildID: 20211215221728 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Dec 21 13:17:24 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-05-29 (570 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.1.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.10 metric 100 MostRecentCrashID: bp-6d5c31fc-1b33-459b-bfab-9d3b20211216 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=54.0/20170612122310 (Out of date) Profile0 (Default) - LastVersion=95.0.1/20211215221728 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-11-04 (412 days ago) dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.sku: 083615D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro mtime.conffile..etc.apport.crashdb.conf: 2021-06-21T20:18:54.448530 To manage notifications about
[Desktop-packages] [Bug 1955500] [NEW] firefox crashes often
Public bug reported: Recently (since ~2021-12-15) firefox has been crashing a lot, often daily. There's no obvious pattern that I can see. Most recent crash logs: Dec 21 12:37:51 cerberus firefox.desktop[755990]: Sandbox: Unexpected EOF, op 0 flags 0200 path /proc/755990/cgroup Dec 21 12:37:51 cerberus firefox.desktop[756121]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755809]: Exiting due to channel error. Dec 21 12:37:51 cerberus firefox.desktop[755990]: Exiting due to channel error. ... Dec 21 12:37:51 cerberus firefox.desktop[745228]: [GFX1-]: Receive IPC close with reason=AbnormalShutdown Dec 21 12:37:51 cerberus firefox.desktop[744870]: Exiting due to channel error. ... Previous crash: Dec 20 12:56:53 cerberus kernel: traps: GeckoMain[613052] trap int3 ip:7fa351cc1295 sp:7fff6ba7eea0 error:0 in libglib-2.> Dec 20 12:56:53 cerberus gnome-shell[722119]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[722386]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[615970]: Exiting due to channel error. Dec 20 12:56:53 cerberus gnome-shell[717612]: Exiting due to channel error. ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 95.0.1+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: jlquinn2641 F pulseaudio /dev/snd/controlC0: jlquinn2641 F pulseaudio /dev/snd/controlC2: jlquinn2641 F pulseaudio /dev/snd/controlC1: jlquinn2641 F pulseaudio BuildID: 20211215221728 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Dec 21 13:17:24 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-05-29 (570 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.1.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.10 metric 100 MostRecentCrashID: bp-6d5c31fc-1b33-459b-bfab-9d3b20211216 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=54.0/20170612122310 (Out of date) Profile0 (Default) - LastVersion=95.0.1/20211215221728 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-11-04 (412 days ago) dmi.bios.date: 12/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd12/16/2019:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.sku: 083615D9 dmi.product.version: 123456789 dmi.sys.vendor: Supermicro mtime.conffile..etc.apport.crashdb.conf: 2021-06-21T20:18:54.448530 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1955500 Title: firefox crashes often Status in firefox package in Ubuntu: New Bug description: Recently (since ~2021-12-15) firefox has been crashing a lot, often daily. There's no obvious pattern that I can see. Most recent crash logs: Dec 21 12:37:51 cerberus
[Desktop-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1926256 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+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 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1922276 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output Status in MATE Desktop: New Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu MATE 21.04 installed (or use Live session) 2. Launch MATE Terminal 3. Enable infinite history (Edit - Profile Preferences - Scrolling, Scrollback - Unlimited) 4. Execute command with long output such as `journalctl | cat` 5. Select Edit - Select All (or press ++), then Edit - Copy (or press ++) 6. Open Pluma text editor and paste just copied terminal output Expected results: * whole terminal output is copied - staring by `user@host:~$ journalctl | cat` and ending by `user@host:~$` Actual results: * only last 15 lines were copied (depends on terminal size) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 1 17:35:47 2021 LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1922276/+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 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1947420 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1947420 Title: Buggish interface @ workstation panels previews when using dual portrait Status in MATE Desktop: New Status in Ubuntu MATE: Confirmed Status in libwnck3 package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Confirmed Bug description: ...Freshly upgraded to 21.10 using the same OS that I used to open most of my previous video glitches ever... Using 2x monitor in portrait mode, the preview panel/widget(?) located at the bottom right side shows 2 things wrong: 1. The "Workspace 1" preview is very elongated when compared to not only all of it's previous incarnations (from 14.04 to 21.10) but also has an inconsistent size when compared to it's neighbouring "Workspace 2". Expectation: both 1 and 2 should be sized identically. 2. When hovering the mouse cursor on "Workspace 2" only it's left portion will highlight. Expectation: both monitors of "2" should highlight See enclosed picture. To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1947420/+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 1955326] Re: Ubuntu 20.04 freezes on nvidia nvidia-340 -
** Package changed: ubuntu => nvidia-graphics-drivers-340 (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1955326 Title: Ubuntu 20.04 freezes on nvidia nvidia-340 - Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Just upgraded to Ubuntu 20 from 18. After splash screen cursor blinks and nothing happens. So boot into recovery mode. From what I read on stackoverflow etc this is related to Nvidia driver. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.3 LTS Release: 20.04 ubuntu-drivers devices == /sys/devices/pci:00/:00:03.0/:02:00.0 == modalias : pci:v10DEd06E4sv1043sd830Cbc03sc00i00 vendor : NVIDIA Corporation model: G98 [GeForce 8400 GS Rev. 2] driver : nvidia-340 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin dmesg | grep -i nvidia [6.755975] audit: type=1400 audit(1639843935.149:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=340 comm="apparmor_parser" [6.756075] audit: type=1400 audit(1639843935.149:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=340 comm="apparmor_parser" [7.147366] nvidia: loading out-of-tree module taints kernel. [7.147373] nvidia: module license 'NVIDIA' taints kernel. [7.153255] nvidia: module verification failed: signature and/or required key missing - tainting kernel [7.193816] nvidia :02:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [7.194410] [drm] Initialized nvidia-drm 0.0.0 20150116 for :02:00.0 on minor 0 [7.194420] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [7.240070] nvidia_uvm: Loaded the UVM driver, major device number 241 [7.349712] caller os_map_kernel_space+0x6d/0xb0 [nvidia] mapping multiple BARs [7.389714] caller os_map_kernel_space+0x6d/0xb0 [nvidia] mapping multiple BARs [ 66.369188] caller os_map_kernel_space+0x6d/0xb0 [nvidia] mapping multiple BARs dpkg -l | grep nvidia ii nvidia-340 340.108-0ubuntu5.20.04.2 amd64NVIDIA binary driver - version 340.108 ii nvidia-opencl-icd-340 340.108-0ubuntu5.20.04.2 amd64NVIDIA OpenCL ICD rc nvidia-settings440.82-0ubuntu0.18.04.1 amd64Tool for configuring the NVIDIA graphics driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1955326/+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 1955326] [NEW] Ubuntu 20.04 freezes on nvidia nvidia-340 -
You have been subscribed to a public bug: Just upgraded to Ubuntu 20 from 18. After splash screen cursor blinks and nothing happens. So boot into recovery mode. From what I read on stackoverflow etc this is related to Nvidia driver. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 ubuntu-drivers devices == /sys/devices/pci:00/:00:03.0/:02:00.0 == modalias : pci:v10DEd06E4sv1043sd830Cbc03sc00i00 vendor : NVIDIA Corporation model: G98 [GeForce 8400 GS Rev. 2] driver : nvidia-340 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin dmesg | grep -i nvidia [6.755975] audit: type=1400 audit(1639843935.149:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=340 comm="apparmor_parser" [6.756075] audit: type=1400 audit(1639843935.149:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=340 comm="apparmor_parser" [7.147366] nvidia: loading out-of-tree module taints kernel. [7.147373] nvidia: module license 'NVIDIA' taints kernel. [7.153255] nvidia: module verification failed: signature and/or required key missing - tainting kernel [7.193816] nvidia :02:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [7.194410] [drm] Initialized nvidia-drm 0.0.0 20150116 for :02:00.0 on minor 0 [7.194420] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 [7.240070] nvidia_uvm: Loaded the UVM driver, major device number 241 [7.349712] caller os_map_kernel_space+0x6d/0xb0 [nvidia] mapping multiple BARs [7.389714] caller os_map_kernel_space+0x6d/0xb0 [nvidia] mapping multiple BARs [ 66.369188] caller os_map_kernel_space+0x6d/0xb0 [nvidia] mapping multiple BARs dpkg -l | grep nvidia ii nvidia-340 340.108-0ubuntu5.20.04.2 amd64NVIDIA binary driver - version 340.108 ii nvidia-opencl-icd-340 340.108-0ubuntu5.20.04.2 amd64NVIDIA OpenCL ICD rc nvidia-settings440.82-0ubuntu0.18.04.1 amd64Tool for configuring the NVIDIA graphics driver ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 20.04 freezes on nvidia nvidia-340 - https://bugs.launchpad.net/bugs/1955326 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. -- 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 1946987] Re: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
** Summary changed: - Nvidia 340 Xorg driver is installed but not loaded after OS upgrade + Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. If I use Budgie Desktop instead of Xfce as desktop environment, it will automatically log out to the LightDM login screen, if I first try to start that Budgie session and then the HDMI output is used as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1946987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1946987] Re: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
** Description changed: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and xrand does not even list the connector. When using nouveau, HDMI is listed but it shows as disconnected. WORKAROUND when using nvidia driver: Log out of session. Then lightdm screen shows on both monitors. And if I then log in to a session, the extrernal monitor works there, too. + + If I use Budgie Desktop instead of Xfce as desktop environment, it will + automatically log out to the LightDM login screen, if I first try to + start that Budgie session and then the HDMI output is used as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Oct 13 16:27:00 2021 DistUpgraded: 2021-10-13 15:24:05,135 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2019-05-08 (888 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=dd272475-45e5-4fca-b9ab-1b1f3f3015bd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-10-13 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1946987 Title: Regression: Nvidia 340 Xorg driver is installed but not loaded after OS upgrade Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I tried both nouveau and nvidia-340 drivers. It used to work at least by the latter one in Xubuntu 18.04, even with HWE kernel When using the nvidia-340 driver: $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1200, current 1920 x 1200, maximum 1920 x 1200 default connected 1920x1200+0+0 0mm x 0mm 1920x1200 77.00* A device is connected in HDMI and
[Desktop-packages] [Bug 1955461] Re: ibus-x11 crashed with SIGSEGV in __pthread_kill_implementation()
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1955461/+attachment/5548856/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1955461 Title: ibus-x11 crashed with SIGSEGV in __pthread_kill_implementation() Status in ibus package in Ubuntu: New Bug description: Nothing observed ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: ibus 1.5.25-3 Uname: Linux 5.15.7-051507-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 21 07:30:13 2021 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2021-12-10 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211209) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon SegvAnalysis: Segfault happened at: 0x7f615926644c <__run_exit_handlers+108>: mov 0x10(%r15,%rdx,1),%rcx PC (0x7f615926644c) ok source "0x10(%r15,%rdx,1)" (0x1041bf32f0b920) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=15, threadid=140056065796736) at pthread_kill.c:44 __pthread_kill_internal (signo=15, threadid=140056065796736) at pthread_kill.c:80 __GI___pthread_kill (threadid=140056065796736, signo=signo@entry=15) at pthread_kill.c:91 __GI_raise (sig=15) at ../sysdeps/posix/raise.c:26 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-x11 crashed with SIGSEGV in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1955461/+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 1955483] Re: dhcp4 (wlp1s0): could not get netmask from lease
** Description changed: + I get this on n-m 1.30.0-1ubuntu3 (hirsuite) and 1.32.12-0ubuntu1 + (impish). It's been reported and fixed upstream. Any chance of getting + an update to the impish package with the fix? + Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (wlp1s0): supplicant interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: WPA: Key negotiation completed with 00:19:88:4d:03:b3 [PTK=CCMP GTK=TKIP] Dec 21 06:23:54 t495 kernel: [ 787.299157] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 00:19:88:4d:03:b3 completed [id=0 id_str=] Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-53 noise= txrate=1000 Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): supplicant interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "VesperXB-Arawa" Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9699] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9703] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9707] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Dec 21 06:23:54 t495 avahi-daemon[984]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::86b7:7a02:8867:b893. Dec 21 06:23:54 t495 avahi-daemon[984]: New relevant interface wlp1s0.IPv6 for mDNS. Dec 21 06:23:54 t495 avahi-daemon[984]: Registering new address record for fe80::86b7:7a02:8867:b893 on wlp1s0.*. Dec 21 06:23:55 t495 NetworkManager[989]: [1640089435.0002] dhcp4 (wlp1s0): could not get netmask from lease Dec 21 06:23:55 t495 NetworkManager[989]: [1640089435.0003] dhcp4 (wlp1s0): state changed unknown -> fail ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #848 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/848 ** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/848 Importance: Unknown Status: Unknown -- 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/1955483 Title: dhcp4 (wlp1s0): could not get netmask from lease Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: I get this on n-m 1.30.0-1ubuntu3 (hirsuite) and 1.32.12-0ubuntu1 (impish). It's been reported and fixed upstream. Any chance of getting an update to the impish package with the fix? Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (wlp1s0): supplicant interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: WPA: Key negotiation completed with 00:19:88:4d:03:b3 [PTK=CCMP GTK=TKIP] Dec 21 06:23:54 t495 kernel: [ 787.299157] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 00:19:88:4d:03:b3 completed [id=0 id_str=] Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-53 noise= txrate=1000 Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): supplicant interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "VesperXB-Arawa" Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9699] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9703] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9707] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Dec 21 06:23:54 t495 avahi-daemon[984]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::86b7:7a02:8867:b893. Dec 21 06:23:54 t495 avahi-daemon[984]: New relevant interface
[Desktop-packages] [Bug 1955483] [NEW] dhcp4 (wlp1s0): could not get netmask from lease
Public bug reported: I get this on n-m 1.30.0-1ubuntu3 (hirsuite) and 1.32.12-0ubuntu1 (impish). It's been reported and fixed upstream. Any chance of getting an update to the impish package with the fix? Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (wlp1s0): supplicant interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: WPA: Key negotiation completed with 00:19:88:4d:03:b3 [PTK=CCMP GTK=TKIP] Dec 21 06:23:54 t495 kernel: [ 787.299157] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 00:19:88:4d:03:b3 completed [id=0 id_str=] Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-53 noise= txrate=1000 Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): supplicant interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "VesperXB-Arawa" Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9699] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9703] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9707] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Dec 21 06:23:54 t495 avahi-daemon[984]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::86b7:7a02:8867:b893. Dec 21 06:23:54 t495 avahi-daemon[984]: New relevant interface wlp1s0.IPv6 for mDNS. Dec 21 06:23:54 t495 avahi-daemon[984]: Registering new address record for fe80::86b7:7a02:8867:b893 on wlp1s0.*. Dec 21 06:23:55 t495 NetworkManager[989]: [1640089435.0002] dhcp4 (wlp1s0): could not get netmask from lease Dec 21 06:23:55 t495 NetworkManager[989]: [1640089435.0003] dhcp4 (wlp1s0): state changed unknown -> fail ** Affects: network-manager Importance: Unknown Status: Unknown ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1955483 Title: dhcp4 (wlp1s0): could not get netmask from lease Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: I get this on n-m 1.30.0-1ubuntu3 (hirsuite) and 1.32.12-0ubuntu1 (impish). It's been reported and fixed upstream. Any chance of getting an update to the impish package with the fix? Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (wlp1s0): supplicant interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9548] device (p2p-dev-wlp1s0): supplicant management interface state: associating -> 4way_handshake Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: WPA: Key negotiation completed with 00:19:88:4d:03:b3 [PTK=CCMP GTK=TKIP] Dec 21 06:23:54 t495 kernel: [ 787.299157] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-CONNECTED - Connection to 00:19:88:4d:03:b3 completed [id=0 id_str=] Dec 21 06:23:54 t495 wpa_supplicant[1024]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-53 noise= txrate=1000 Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): supplicant interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9698] device (wlp1s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "VesperXB-Arawa" Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9699] device (p2p-dev-wlp1s0): supplicant management interface state: 4way_handshake -> completed Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9703] device (wlp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Dec 21 06:23:54 t495 NetworkManager[989]: [1640089434.9707] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) Dec 21 06:23:54 t495 avahi-daemon[984]: Joining mDNS multicast group on interface wlp1s0.IPv6 with address fe80::86b7:7a02:8867:b893. Dec 21 06:23:54 t495 avahi-daemon[984]: New relevant interface wlp1s0.IPv6 for mDNS. Dec 21 06:23:54 t495 avahi-daemon[984]: Registering new address record for fe80::86b7:7a02:8867:b893 on wlp1s0.*. Dec 21 06:23:55 t495 NetworkManager[989]: [1640089435.0002]
[Desktop-packages] [Bug 1955475] Re: Sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main)
This bug was fixed in the package libayatana-indicator - 0.9.0-1 Sponsored for fossfreedom (fossfreedom) --- libayatana-indicator (0.9.0-1) unstable; urgency=medium * New upstream release. * debian/patches: + Drop all previous patches. All shipped upstream. + Add 0001_src-CMakeLists.txt-indicator.symbols-Don-t-export-pr.patch. Don't export private symbols. * debian/: + Adjust to upstream build system switch (autotools -> CMake). * debian/control: + Bump Standards-Version: to 4.6.0. No changes needed. + Add missing dev:pkg dependency to libayatana-indicator3-dev: libayatana-ido3-dev (>= 0.8.0). + Enforce usage of version 0.9.0 of the Ayatana IDO library. * debian/copyright: + Update auto-generated copyright.in reference file. + Update copyright attributions. * debian/watch: + Use format version 4. * debian/rules: + Install NEWS file as upstream ChangeLog. * debian/upstream/metadata: + Update points of contact, put UBports Foundation in Donation: field. -- Mike Gabriel Thu, 18 Nov 2021 13:35:28 +0100 ** Changed in: libayatana-indicator (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libayatana-indicator in Ubuntu. https://bugs.launchpad.net/bugs/1955475 Title: Sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main) Status in libayatana-indicator package in Ubuntu: Fix Released Bug description: Please sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Correctly restore +x permissions on the .install for dh_exec I've done a test build of the debian package and installed the resulting .deb installs just fine. Upstream has dropped the need for lomiri-app-launch as a dependency in ubuntu In addition the v0.9.0 of the package ensures alignment with the v0.9.0 series of the other ayatana packages that have already migrated to ubuntu. Changelog entries since current jammy version 0.8.4-4ubuntu2: libayatana-indicator (0.9.0-1) unstable; urgency=medium * New upstream release. * debian/patches: + Drop all previous patches. All shipped upstream. + Add 0001_src-CMakeLists.txt-indicator.symbols-Don-t-export-pr.patch. Don't export private symbols. * debian/: + Adjust to upstream build system switch (autotools -> CMake). * debian/control: + Bump Standards-Version: to 4.6.0. No changes needed. + Add missing dev:pkg dependency to libayatana-indicator3-dev: libayatana-ido3-dev (>= 0.8.0). + Enforce usage of version 0.9.0 of the Ayatana IDO library. * debian/copyright: + Update auto-generated copyright.in reference file. + Update copyright attributions. * debian/watch: + Use format version 4. * debian/rules: + Install NEWS file as upstream ChangeLog. * debian/upstream/metadata: + Update points of contact, put UBports Foundation in Donation: field. -- Mike Gabriel Thu, 18 Nov 2021 13:35:28 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-indicator/+bug/1955475/+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 1955475] [NEW] Sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main)
Public bug reported: Please sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Correctly restore +x permissions on the .install for dh_exec I've done a test build of the debian package and installed the resulting .deb installs just fine. Upstream has dropped the need for lomiri-app-launch as a dependency in ubuntu In addition the v0.9.0 of the package ensures alignment with the v0.9.0 series of the other ayatana packages that have already migrated to ubuntu. Changelog entries since current jammy version 0.8.4-4ubuntu2: libayatana-indicator (0.9.0-1) unstable; urgency=medium * New upstream release. * debian/patches: + Drop all previous patches. All shipped upstream. + Add 0001_src-CMakeLists.txt-indicator.symbols-Don-t-export-pr.patch. Don't export private symbols. * debian/: + Adjust to upstream build system switch (autotools -> CMake). * debian/control: + Bump Standards-Version: to 4.6.0. No changes needed. + Add missing dev:pkg dependency to libayatana-indicator3-dev: libayatana-ido3-dev (>= 0.8.0). + Enforce usage of version 0.9.0 of the Ayatana IDO library. * debian/copyright: + Update auto-generated copyright.in reference file. + Update copyright attributions. * debian/watch: + Use format version 4. * debian/rules: + Install NEWS file as upstream ChangeLog. * debian/upstream/metadata: + Update points of contact, put UBports Foundation in Donation: field. -- Mike Gabriel Thu, 18 Nov 2021 13:35:28 +0100 ** Affects: libayatana-indicator (Ubuntu) Importance: Wishlist Status: New ** Changed in: libayatana-indicator (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libayatana-indicator in Ubuntu. https://bugs.launchpad.net/bugs/1955475 Title: Sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main) Status in libayatana-indicator package in Ubuntu: New Bug description: Please sync libayatana-indicator 0.9.0-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Correctly restore +x permissions on the .install for dh_exec I've done a test build of the debian package and installed the resulting .deb installs just fine. Upstream has dropped the need for lomiri-app-launch as a dependency in ubuntu In addition the v0.9.0 of the package ensures alignment with the v0.9.0 series of the other ayatana packages that have already migrated to ubuntu. Changelog entries since current jammy version 0.8.4-4ubuntu2: libayatana-indicator (0.9.0-1) unstable; urgency=medium * New upstream release. * debian/patches: + Drop all previous patches. All shipped upstream. + Add 0001_src-CMakeLists.txt-indicator.symbols-Don-t-export-pr.patch. Don't export private symbols. * debian/: + Adjust to upstream build system switch (autotools -> CMake). * debian/control: + Bump Standards-Version: to 4.6.0. No changes needed. + Add missing dev:pkg dependency to libayatana-indicator3-dev: libayatana-ido3-dev (>= 0.8.0). + Enforce usage of version 0.9.0 of the Ayatana IDO library. * debian/copyright: + Update auto-generated copyright.in reference file. + Update copyright attributions. * debian/watch: + Use format version 4. * debian/rules: + Install NEWS file as upstream ChangeLog. * debian/upstream/metadata: + Update points of contact, put UBports Foundation in Donation: field. -- Mike Gabriel Thu, 18 Nov 2021 13:35:28 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libayatana-indicator/+bug/1955475/+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 1955434] Re: Driverless printing detection does not work
OK, I rebooted the printer and the printer was autodiscovered again. Those cups apparmor denies don't appear to stop discovery ... so they are noise on the journal log ... minor. I will mark this as invalid. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid ** Changed in: apparmor (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1955434 Title: Driverless printing detection does not work Status in apparmor package in Ubuntu: Invalid Status in cups package in Ubuntu: Invalid Bug description: 20 Dec 2021 fresh just installed ubuntu budgie jammy daily My network HP Photosmart printer is not detected. In fact the only printer found via gnome settings is CUPS-BRF-PRINTER This is a regression since both 20.04.3 and 21.10 both find the same printer on the network automatically. journal -ae | grep cups shows apparmor issues dad@dad-MacBookPro:~$ journalctl -ae | grep cups Dec 20 23:42:40 dad-MacBookPro audit[711]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12 capname="net_admin" Dec 20 23:42:40 dad-MacBookPro kernel: audit: type=1400 audit(1640043760.707:41): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12 capname="net_admin" Dec 20 23:42:48 dad-MacBookPro audit[834]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23 capname="sys_nice" Dec 20 23:42:48 dad-MacBookPro kernel: audit: type=1400 audit(1640043768.971:42): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23 capname="sys_nice" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.3.3op2-7ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Dec 20 23:44:41 2021 InstallationDate: Installed on 2021-12-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211220) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Apple Inc. MacBookPro9,2 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=69ee9609-7759-4141-a4ce-e89f3cb9e31a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1955434/+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 1955434] Re: Driverless printing detection does not work
Jammy has not had any changes to the apparmor packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1955434 Title: Driverless printing detection does not work Status in apparmor package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: 20 Dec 2021 fresh just installed ubuntu budgie jammy daily My network HP Photosmart printer is not detected. In fact the only printer found via gnome settings is CUPS-BRF-PRINTER This is a regression since both 20.04.3 and 21.10 both find the same printer on the network automatically. journal -ae | grep cups shows apparmor issues dad@dad-MacBookPro:~$ journalctl -ae | grep cups Dec 20 23:42:40 dad-MacBookPro audit[711]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12 capname="net_admin" Dec 20 23:42:40 dad-MacBookPro kernel: audit: type=1400 audit(1640043760.707:41): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=711 comm="cupsd" capability=12 capname="net_admin" Dec 20 23:42:48 dad-MacBookPro audit[834]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23 capname="sys_nice" Dec 20 23:42:48 dad-MacBookPro kernel: audit: type=1400 audit(1640043768.971:42): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=834 comm="cups-browsed" capability=23 capname="sys_nice" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.3.3op2-7ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Dec 20 23:44:41 2021 InstallationDate: Installed on 2021-12-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211220) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Apple Inc. MacBookPro9,2 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=69ee9609-7759-4141-a4ce-e89f3cb9e31a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP91.88Z.00D9.B00.1802021100 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1955434/+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
