[Desktop-packages] [Bug 1686623] Re: Gnome terminal window shrink on exit focus with wayland
I'm seeing this bug with Ubuntu 22.04.1 LTS. Windowing System: Wayland Graphics: AMD Renoir I'm using the default theme. -- 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/1686623 Title: Gnome terminal window shrink on exit focus with wayland Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Gnome terminal window shrink each time the window is unfocused. It only happen with Wayland. Workaround: Maximize the terminal window. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 27 14:10:17 2017 EcryptfsInUse: Yes SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-03-28 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1686623/+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 2003996] [NEW] /usr/bin/software-properties-gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:http
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003996 Title: /usr/bin/software-properties- gtk:TimeoutError:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status:readinto:recv_into:read Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/032c1f3f3d9b9b05e5087f7e37a05a3d0d40e699 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003996/+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 2003406] Re: imap and smtp to outlook.office365.com over oauth2 problem
In case you install thunderbird thru snap, you can upgrade to beta
sudo snap refresh thunderbird --channel=latest/beta
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2003406
Title:
imap and smtp to outlook.office365.com over oauth2 problem
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Good morning,
Since yesterday january 18 2023 Thunderbird cannot connect to my
company email anymore, both imap and smtp. Mail server for imap is
outlook.office365.com, port 993, SSL/TLS, OAuth2. For smtp:
smtp.office365.com port 587, STARTTLS, OAuth2.
On january 17 and before, all was working well with the same settings.
Thunderbird version is 102.7.0 (64-bit) on an up-to-date Ubuntu 22.10.
When I start TB from a terminal, I get this:
```
[ImapModuleLoader] Using nsImapService.cpp
[NntpModuleLoader] Using NntpService.jsm
[Pop3ModuleLoader] Using Pop3Service.jsm
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[calBackendLoader] Using Thunderbird's ical.js backend
console.debug: "Successfully loaded OpenPGP library librnp.so version
0.16.2+git20220922.298ad98b.MZLA from /usr/lib/thunderbird/librnp.so"
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0
unprotected)"
console.debug: "Successfully loaded optional OpenPGP library libgpgme.so.11
from system's standard library locations"
console.debug: "gpgme version: 1.17.1"
console.warn: services.settings: Failed to load last_modified.json:
TypeError: NetworkError when attempting to fetch resource.
console.debug: "Trying to load /usr/lib/thunderbird/libotr.so"
console.debug: "Trying to load libotr.so from system's standard library
locations"
console.debug: "Trying to load libotr.so.5 from system's standard library
locations"
console.debug: "Trying to load libotr.so from system's standard library
locations"
console.log: (new Error("Cannot load required OTR library",
"resource:///modules/OTRLib.jsm", 109))
JavaScript error: resource:///modules/OAuth2.jsm, line 168:
NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001
(NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name]
JavaScript error: resource:///modules/OAuth2.jsm, line 168:
NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001
(NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name]
JavaScript error: resource:///modules/OAuth2.jsm, line 168:
NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001
(NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name]
```
That last bit (to me) seems to indicate a client side (TB) issue. If
anybody knows or can make a fix, that would be great, I much prefer TB
to the MS web interface.
Best,
Joolz.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2003406/+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 1425000] Re: Cannot set right monitor as primary in dual monitor configuration
For workaround, I created a tool to move window to the specified monitor. https://github.com/stzdzyhs/mwtm Hope it useful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1425000 Title: Cannot set right monitor as primary in dual monitor configuration Status in unity-control-center package in Ubuntu: Won't Fix Status in unity-settings-daemon package in Ubuntu: Won't Fix Status in xfwm4 package in Ubuntu: Invalid Bug description: Unity always considers the left monitor as the default/primary one when in a dual-monitor configuration. By this I mean that: - Desktop icons appear only on the left monitor - An opened app (eg libreoffice writer) is opened on the left screen, even if I launch it via the launcher on the right monitor The current configuration can be seen at http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png The .config/monitors.xml file is shown below. Notice that the HDMI display (green in the photo) is set asyes. Nevertheless, this seems to be ignored - the behaviour is the one mentioned above (desktop icons on the left and writer opening on the left) . no GSM 0x4b7a 0xb13b 1440 900 60 0 0 normal no no no GSM 0x5a26 0x0008976f 1920 1080 60 1440 0 normal no no yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1425000/+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 1850081] Re: Folder pane text overflows
** Changed in: thunderbird Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850081 Title: Folder pane text overflows Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Confirmed Bug description: After upgrading to Kubuntu 19.10 I noticed the text in the folder pane overflows which hides the unread count, it appears as if the text is behind the scrollbar. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: rowan 2237 F pulseaudio /dev/snd/controlC0: rowan 2237 F pulseaudio BuildID: 20191010144232 Channel: Unavailable CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-11-19 (343 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-6abdd954-b5ad-4d9d-a828-9824b0180710 Package: thunderbird 1:68.1.2+build1-0ubuntu1 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 PrefSources: prefs.js ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use) RunningIncompatibleAddons: False Tags: eoan Themes: extensions.sqlite corrupt or missing Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 187.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr187.0.0.0.0:bd07/22/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850081/+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 1888942] Re: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click
** Changed in: firefox Status: Confirmed => Invalid -- 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/1888942 Title: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Invalid Bug description: Hi, if I click in an url in firefox, the whole url ist marked, i.e. highlighted. If I now use a click on the mousewheel to paste the content of the clipboard into another software, I discover that the url wasn't copied into the clipboard - the previous content ist filled in. That's confusing to me. I would expect: If I can mark an url in Firefox with a single mouse-click, which looks like a marking with a triple click, then it should be copied also in the clipboard. That would be a consisting behavior. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 78.0.2+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 1453 F pulseaudio /dev/snd/controlC1: matthias 1453 F pulseaudio /dev/snd/pcmC1D0c: matthias 1453 F...m pulseaudio /dev/snd/pcmC1D0p: matthias 1453 F...m pulseaudio BuildID: 20200708170202 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:44:27 2020 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:730 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2020-04-24 (92 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 600 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=74.0.1/20200403064753 (Out of date) Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET53W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS06G0J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90GJVAH dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS06G0J dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1888942/+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 1850081]
It's gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850081 Title: Folder pane text overflows Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Confirmed Bug description: After upgrading to Kubuntu 19.10 I noticed the text in the folder pane overflows which hides the unread count, it appears as if the text is behind the scrollbar. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: rowan 2237 F pulseaudio /dev/snd/controlC0: rowan 2237 F pulseaudio BuildID: 20191010144232 Channel: Unavailable CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-11-19 (343 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-6abdd954-b5ad-4d9d-a828-9824b0180710 Package: thunderbird 1:68.1.2+build1-0ubuntu1 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 PrefSources: prefs.js ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use) RunningIncompatibleAddons: False Tags: eoan Themes: extensions.sqlite corrupt or missing Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 187.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr187.0.0.0.0:bd07/22/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850081/+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 1850081]
Is this going to be gone in 111? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850081 Title: Folder pane text overflows Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Confirmed Bug description: After upgrading to Kubuntu 19.10 I noticed the text in the folder pane overflows which hides the unread count, it appears as if the text is behind the scrollbar. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: rowan 2237 F pulseaudio /dev/snd/controlC0: rowan 2237 F pulseaudio BuildID: 20191010144232 Channel: Unavailable CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-11-19 (343 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-6abdd954-b5ad-4d9d-a828-9824b0180710 Package: thunderbird 1:68.1.2+build1-0ubuntu1 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 PrefSources: prefs.js ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Profiles: Profile0 (Default) - LastVersion=68.1.2/20191010144232 (In use) RunningIncompatibleAddons: False Tags: eoan Themes: extensions.sqlite corrupt or missing Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 187.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr187.0.0.0.0:bd07/22/2019:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850081/+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 1888942]
Fixing the dep here should allow selection which will handle the use cases here *** This bug has been marked as a duplicate of bug 1633203 *** -- 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/1888942 Title: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Invalid Bug description: Hi, if I click in an url in firefox, the whole url ist marked, i.e. highlighted. If I now use a click on the mousewheel to paste the content of the clipboard into another software, I discover that the url wasn't copied into the clipboard - the previous content ist filled in. That's confusing to me. I would expect: If I can mark an url in Firefox with a single mouse-click, which looks like a marking with a triple click, then it should be copied also in the clipboard. That would be a consisting behavior. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 78.0.2+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 1453 F pulseaudio /dev/snd/controlC1: matthias 1453 F pulseaudio /dev/snd/pcmC1D0c: matthias 1453 F...m pulseaudio /dev/snd/pcmC1D0p: matthias 1453 F...m pulseaudio BuildID: 20200708170202 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:44:27 2020 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:730 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2020-04-24 (92 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 600 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=74.0.1/20200403064753 (Out of date) Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET53W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS06G0J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90GJVAH dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS06G0J dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1888942/+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 1993191] Re: apport hook that collects snap's information is outdated
This bug was fixed in the package chromium-browser -
1:85.0.4183.83-0ubuntu3
---
chromium-browser (1:85.0.4183.83-0ubuntu3) lunar; urgency=medium
[ Olivier Tilloy ]
* debian/apport/chromium-browser.py: update the apport hook to collect
up-to-date information from the chromium snap (LP: #1993191)
-- Nathan Pratta Teodosio Mon, 17 Oct
2022 18:53:30 +0200
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1993191
Title:
apport hook that collects snap's information is outdated
Status in chromium-browser package in Ubuntu:
Fix Released
Status in chromium-browser source package in Focal:
In Progress
Status in chromium-browser source package in Jammy:
In Progress
Status in chromium-browser source package in Kinetic:
In Progress
Bug description:
Impact
--
The Apport hook of the Chromium browser is outdated. It collects
information about core18, but the snap uses core20.
Moreover, it does not collect information about other interface
providers.
Test plan
-
1. Install the current chromium-browser.
2. Generate a report with
apport-bug --save /tmp/c1 chromium-browser
3. Install chromium-browser from proposed.
4. Generate another report with
apport-bug --save /tmp/c2 chromium-browser
Note: If the package was built and generated locally, you will need
APPORT_DISABLE_DISTRO_CHECK=1 in the environment.
5. Compare the files. The meaningful differences should be in the
Snap.Info. sections, namely:
- Snap.Info.core18 -> Snap.Info.core20
- {None} -> Snap.Info.cups
- {None} -> Snap.Info.gnome-3-38-2004
Differences should not be observed in Snap.Info.{chromium,core,gtk-
common-themes}.
Regression potential
Being Apport a bug reporting program, an incorrect parsing of the
SNAP_META file could lead to insertion of unwanted information in the
report or to suppress the insertion of information about the relevant
interfaces.
Original report
---
See https://bazaar.launchpad.net/~chromium-team/chromium-
browser/groovy-stable/view/head:/debian/apport/chromium-
browser.py#L59.
It collects information about core18, but the chromium snap was
rebased on core20 almost a year ago.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
Regarding NGINX, PCRE2 support is now available in NGINX nginx 1.21.5+ so there was support as of December 24th 2021 and later. Which means that NGINX 1.22+ supports PCRE2. This could be marked as Triaged *for 23.04 and later* once NGINX is merged in from Debian upstream, if someone can put a few cycles to build/test. Refer to https://trac.nginx.org/nginx/changeset/0b5f12d5c531be630a4aae644686be83cfed3267/nginx and the "fixed" Trac bug https://trac.nginx.org/nginx/ticket/720 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: In Progress Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Fix Released Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Fix Released Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Status in postfix package in Debian: Fix Released Status in zsh package in Debian: Confirmed Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
> non-nVidia hardware The above is a Dell Latitude 3160 Pentium-powered Chromebook-class educational laptop. Built-in screen. Problem occurs when booting from USB stick and choosing 'Try Ubuntu' (or 'Try Ubuntu Budgie'), with 22.04.1-LTS (Jammy). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
> We aren't considering the issue as rls target at this point, it's on a limited set of hardware and the nvidia drivers don't have the issue and can we used instead This behavior is also occurring on non-nVidia hardware: $ dmesg |egrep '(CPU|fb|i915)' |grep -v '0x[0-9a-f]*fb[0-9a-f]*' [0.057997] smpboot: Allowing 4 CPUs, 0 hotplug CPUs [0.058224] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1 [0.175649] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.218117] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=4. [0.239261] CPU0: Thermal monitoring enabled (TM1) [0.239261] MDS: Mitigation: Clear CPU buffers [0.239261] smpboot: CPU0: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz (family: 0x6, model: 0x4c, stepping: 0x3) [0.239261] smp: Bringing up secondary CPUs ... [0.239261] node #0, CPUs: #1 #2 #3 [0.247844] smp: Brought up 1 node, 4 CPUs [0.413818] pci :00:02.0: BAR 2: assigned to efifb [0.795846] fbcon: Taking over console [0.989716] ledtrig-cpu: registered to indicate activity on CPUs [0.989957] efifb: probing for efifb [0.990013] efifb: showing boot graphics [0.992809] efifb: framebuffer at 0x8000, using 4128k, total 4128k [0.992823] efifb: mode is 1366x768x32, linelength=5504, pages=1 [0.992826] efifb: scrolling: redraw [0.992827] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [0.998870] fb0: EFI VGA frame buffer device [2.931834] i915 :00:02.0: vgaarb: deactivate vga console [3.002852] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 [3.104714] fbcon: i915drmfb (fb0) is primary device [4.548010] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device [ 20.618832] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) $ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
It seems like this has stalled again and I don't understand why. Patches were posted about 1 month ago and they got some testing feedback within 2 days of availability. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: New Status in gstreamer1.0 package in Ubuntu: New Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: New Status in gstreamer1.0 source package in Jammy: New Status in pipewire source package in Jammy: Confirmed Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 783794]
Dear Georgy Angelov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/783794 Title: [Upstream] Black text converted to white opening pptx Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Binary package hint: libreoffice 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.3.3-1ubuntu1 Candidate: 1:3.3.3-1ubuntu1 Version table: *** 1:3.3.3-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Impress via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/783794/+attachment/2131821/+files/EDC%20Presentation%281%29.pptx -O info.pptx && loimpress -nologo info.pptx is the black text on white background for slide 2 looks as it does in PowerPoint. 4) What happens instead is the black text is converted to white. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Mon May 16 22:45:50 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/783794/+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 1999884] Re: gdm-smartcard not passing successful authentication to desktop at system logon
Can you try to see what you get with pamtester, by using pamtester -v gdm-smartcard $USER authenticate Also try with: pamtester -v gdm-smartcard "" authenticate ** Also affects: sssd (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Changed in: sssd (Ubuntu) Importance: Undecided => High ** Changed in: sssd (Ubuntu) Status: New => Triaged ** Changed in: gdm3 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1999884 Title: gdm-smartcard not passing successful authentication to desktop at system logon Status in gdm3 package in Ubuntu: Triaged Status in sssd package in Ubuntu: Triaged Bug description: For information I've repeated this entire process on RHEL8 and it works there, it also was working upon last test on Ubuntu 20.04 Releases: 22.04 LTS and 22.10 Package Version (for reporting purposes): 43.0-1ubuntu1 Background: System has been configured with sssd, krb5 and pkinit. All of these packages confirm a successful connection to the Active Directory Domain Controller. I have a YubiKey which has a CA generated certificate on it (with all required uses/capabilities including sign) and this is working fine on other systems. Expected Behavior: Insert YubiKey before boot. At the logon window press enter on the Username field. Select the certificate, enter PIN when prompted. Authenticate to desktop. What is happening: Insert YubiKey before boot. At the logon window press enter on the Username field. Select the certificate, enter PIN when prompted. Returns to Username field and does not log in. Other: This is a clean install of 22.10 updated to 16 Dec 2022. I also tried the same thing with 22.04 LTS just in case. I have enabled level 6 logging on SSSD and can confirm that side of the entire process is fine. I can also log on with a password and do a kinit and get a valid kerberos ticket. With some systematic tests, I managed to pinpoint the login is failing after gdm-smartcard reports a successful login: Dec 16 10:25:43 ubu-vm-2022 gdm-smartcard]: gkr-pam: stashed password to try later in open session Dec 16 10:26:22 ubu-vm-2022 gdm-smartcard]: pam_sss(gdm-smartcard:auth): authentication success; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=b...@authenticate.me.uk I did not have this problem on 20.04. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gdm3 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 16 11:43:25 2022 InstallationDate: Installed on 2022-12-16 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1999884/+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 2003976] [NEW] 22.04.1 LTS is incredably SLOW!
Public bug reported: I have been happily using at least the last 10 releases of Ubuntu. I am careful to upgrade to LTS versions. I upgraded to 22.04 a few weeks ago and have failed in researching the web for a solution. My system has lots of memory and disk and the CPU is not busy. I have not been able to locate the bottleneck, I wish I had a tool that would show where the CPU is idling. Surely there is an easy fix! Thanks, Carl ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 13:42:34 2023 DisplayManager: gdm3 InstallationDate: Installed on 2017-11-01 (1912 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2023-01-22 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2003976 Title: 22.04.1 LTS is incredably SLOW! Status in gnome-shell package in Ubuntu: New Bug description: I have been happily using at least the last 10 releases of Ubuntu. I am careful to upgrade to LTS versions. I upgraded to 22.04 a few weeks ago and have failed in researching the web for a solution. My system has lots of memory and disk and the CPU is not busy. I have not been able to locate the bottleneck, I wish I had a tool that would show where the CPU is idling. Surely there is an easy fix! Thanks, Carl ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 13:42:34 2023 DisplayManager: gdm3 InstallationDate: Installed on 2017-11-01 (1912 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2023-01-22 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003976/+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 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
I have the same issue with ubuntu 22.10 on Acer swift 5 when the resolution is 1920x1200. The jitter/shutter happens on the lower end of the screen. If I lower the resolution, everything gets back to normal. Also, this behavior takes place no matter what tool I use to move the mouse -> touch pad or Microsoft mouse. Kind regards, Ciprian -- 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/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions Status in gnome-shell package in Ubuntu: Incomplete Bug description: Mouse lag on fresh install of ubuntu 22.04 LTS (wayland). This problem didn't occur in previous version of ubuntu based on xorg. Specifically, frequent mouse lag when I turn on the pc, when I unlock the pc or when heavy operations are done on it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-13 (50 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-56-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/+source/gnome-shell/+bug/1982560/+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 1993191] Re: apport hook that collects snap's information is outdated
Uploaded to Lunar, currently in the SRU queue for Kinetic, Jammy, and
Focal. Unsubscribing sponsors.
Thanks for your contributions!
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
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/1993191
Title:
apport hook that collects snap's information is outdated
Status in chromium-browser package in Ubuntu:
Fix Committed
Status in chromium-browser source package in Focal:
In Progress
Status in chromium-browser source package in Jammy:
In Progress
Status in chromium-browser source package in Kinetic:
In Progress
Bug description:
Impact
--
The Apport hook of the Chromium browser is outdated. It collects
information about core18, but the snap uses core20.
Moreover, it does not collect information about other interface
providers.
Test plan
-
1. Install the current chromium-browser.
2. Generate a report with
apport-bug --save /tmp/c1 chromium-browser
3. Install chromium-browser from proposed.
4. Generate another report with
apport-bug --save /tmp/c2 chromium-browser
Note: If the package was built and generated locally, you will need
APPORT_DISABLE_DISTRO_CHECK=1 in the environment.
5. Compare the files. The meaningful differences should be in the
Snap.Info. sections, namely:
- Snap.Info.core18 -> Snap.Info.core20
- {None} -> Snap.Info.cups
- {None} -> Snap.Info.gnome-3-38-2004
Differences should not be observed in Snap.Info.{chromium,core,gtk-
common-themes}.
Regression potential
Being Apport a bug reporting program, an incorrect parsing of the
SNAP_META file could lead to insertion of unwanted information in the
report or to suppress the insertion of information about the relevant
interfaces.
Original report
---
See https://bazaar.launchpad.net/~chromium-team/chromium-
browser/groovy-stable/view/head:/debian/apport/chromium-
browser.py#L59.
It collects information about core18, but the chromium snap was
rebased on core20 almost a year ago.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 2003962] Re: [snap] Chromium update makes system unresponsive, black screen
> linux: custom kernel 6.0.7 with squashfs bug hotfix Snaps are sensitive to kernel changes. Sorry, we cannot help if you use a custom one. :| > ( but it's been crashing during snap updates since at least the 5.x ) Do let us know if you are able to reproduce the issue on Focal supported kernels. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2003962 Title: [snap] Chromium update makes system unresponsive, black screen Status in chromium-browser package in Ubuntu: Incomplete Bug description: Every day for the past few days I've been getting notification 'pending update of chromium snap (n) days left'. I noticed earlier that chromium seems to crash my system when it updates(at least it warns now so i can know it's doing it) - as in when i come back to log in after the update, to xorg/gnome, the caps lock doesn't turn on when pressed, and there's nothing but a black screen - ie the system is completely unresponsive. tried hitting magic Sysrq+i to no avail. Had to hard reboot the system with the power button. system was working just fine last night at 1030pm, so whatever happened had to be after then is what did it: I just got another one saying 13 days left. from kern.log Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change from 0 to 303936 Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400 audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575 comm="apparmor_parser" Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400 audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1586575 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400 audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.hook.configure" pid=1586580 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400 audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" pid=1586577 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400 audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" pid=1586579 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400 audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromedriver" pid=1586578 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400 audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400 audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400 audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cancel" pid=1586584 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400 audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.accept" pid=1586583 comm="apparmor_parser" nothing in syslog from 2:38am ubuntu 20.04 linux: custom kernel 6.0.7 with squashfs bug hotfix ( but it's been crashing during snap updates since at least the 5.x ) root@eva1:/var/log# apt-cache policy chromium-browser chromium-browser: Installed: 80.0.3987.163-0ubuntu1 Candidate: 80.0.3987.163-0ubuntu1 Version table: *** 80.0.3987.163-0ubuntu1 500 500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status actual version post update: Version 109.0.5414.74 (Official Build) snap (64-bit) which is different than the last time I saw it ( 103.0.5060.134 ) so it's clearly updating itself, which supports the idea that the snap is updating during the crash but it would be nice to not hard lock my whole desktop system every 2 weeks. ProblemType: Bug DistroRelease:
[Desktop-packages] [Bug 2003962] Re: [snap] Chromium update makes system unresponsive, black screen
** Summary changed: - chromium snap update makes system unresponsive, black screen + [snap] Chromium update makes system unresponsive, black screen -- 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/2003962 Title: [snap] Chromium update makes system unresponsive, black screen Status in chromium-browser package in Ubuntu: New Bug description: Every day for the past few days I've been getting notification 'pending update of chromium snap (n) days left'. I noticed earlier that chromium seems to crash my system when it updates(at least it warns now so i can know it's doing it) - as in when i come back to log in after the update, to xorg/gnome, the caps lock doesn't turn on when pressed, and there's nothing but a black screen - ie the system is completely unresponsive. tried hitting magic Sysrq+i to no avail. Had to hard reboot the system with the power button. system was working just fine last night at 1030pm, so whatever happened had to be after then is what did it: I just got another one saying 13 days left. from kern.log Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change from 0 to 303936 Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400 audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575 comm="apparmor_parser" Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400 audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1586575 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400 audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.hook.configure" pid=1586580 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400 audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" pid=1586577 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400 audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" pid=1586579 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400 audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromedriver" pid=1586578 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400 audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400 audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400 audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cancel" pid=1586584 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400 audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.accept" pid=1586583 comm="apparmor_parser" nothing in syslog from 2:38am ubuntu 20.04 linux: custom kernel 6.0.7 with squashfs bug hotfix ( but it's been crashing during snap updates since at least the 5.x ) root@eva1:/var/log# apt-cache policy chromium-browser chromium-browser: Installed: 80.0.3987.163-0ubuntu1 Candidate: 80.0.3987.163-0ubuntu1 Version table: *** 80.0.3987.163-0ubuntu1 500 500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status actual version post update: Version 109.0.5414.74 (Official Build) snap (64-bit) which is different than the last time I saw it ( 103.0.5060.134 ) so it's clearly updating itself, which supports the idea that the snap is updating during the crash but it would be nice to not hard lock my whole desktop system every 2 weeks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 09:44:00 2023 InstallationDate:
[Desktop-packages] [Bug 2000849] Re: [snap] Request: open (and close) stable/ubuntu-23.04 track
I opened and closed stable/ubuntu-23.04. ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Released -- 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/2000849 Title: [snap] Request: open (and close) stable/ubuntu-23.04 track Status in chromium-browser package in Ubuntu: Fix Released Bug description: Hi Chromium Maintainers! In an effort to revive Edubuntu [1], we (the Edubuntu Team, which consists of my wife and I so far) wish to seed both Firefox and Chromium. This is because Chromium will be better supported in the classroom for collaboration on Google Docs and other web-based applications. This was brought to our attention recently in the Discourse discussion [2]. We discussed it amongst ourselves and decided this was probably a good idea. However, once we're approved for official flavor status and have .iso images building daily, in order to seed Chromium, it will need a stable/ubuntu-yy.mm track opened and closed just like the Firefox team does it now. There is no immediate rush on this, but I figured the sooner I brought this issue forward the better. [1] https://discourse.ubuntu.com/t/announcing-edubuntu-revival/32929 [2] https://discourse.ubuntu.com/t/announcing-edubuntu-revival/32929/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000849/+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 2000849] Re: [snap] Request: open (and close) stable/ubuntu-23.04 track
https://forum.snapcraft.io/t/track-request-open-and-close-stable- ubuntu-23-04 ** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- 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/2000849 Title: [snap] Request: open (and close) stable/ubuntu-23.04 track Status in chromium-browser package in Ubuntu: In Progress Bug description: Hi Chromium Maintainers! In an effort to revive Edubuntu [1], we (the Edubuntu Team, which consists of my wife and I so far) wish to seed both Firefox and Chromium. This is because Chromium will be better supported in the classroom for collaboration on Google Docs and other web-based applications. This was brought to our attention recently in the Discourse discussion [2]. We discussed it amongst ourselves and decided this was probably a good idea. However, once we're approved for official flavor status and have .iso images building daily, in order to seed Chromium, it will need a stable/ubuntu-yy.mm track opened and closed just like the Firefox team does it now. There is no immediate rush on this, but I figured the sooner I brought this issue forward the better. [1] https://discourse.ubuntu.com/t/announcing-edubuntu-revival/32929 [2] https://discourse.ubuntu.com/t/announcing-edubuntu-revival/32929/13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2000849/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()
** Also affects: apport (Ubuntu Lunar) Importance: High Status: Invalid ** Also affects: gtk+3.0 (Ubuntu Lunar) Importance: High Status: Triaged ** Tags removed: rls-kk-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value() Status in apport package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in apport source package in Focal: Invalid Status in gtk+3.0 source package in Focal: Triaged Status in apport source package in Lunar: Invalid Status in gtk+3.0 source package in Lunar: Triaged Bug description: Steps to reproduce -- 1. Use GNOME with GNOME shell 2. killall -11 gnome-shell Suspicious Apport log: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Error tracker - https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22 Stack trace --- Python: ``` File "apport-gtk", line 703, in app = GTKUserInterface(sys.argv) File "apport-gtk", line 68, in GTKUserInterface.__init__ self.widgets.add_from_file( os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui") ) ``` StacktraceTop: _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319 gtk_css_value_icon_theme_compute (icon_theme=, property_id=, provider=, style=, parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84 gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at ../../../../gtk/gtkcssstaticstyle.c:237 _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, provider=provider@entry=0x0, style=style@entry=0x1e7c320, parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122 gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at ../../../../gtk/gtkcssstaticstyle.c:195 Original report --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()
** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Triaged ** Changed in: apport (Ubuntu) Status: Triaged => Invalid ** Changed in: apport (Ubuntu Focal) Status: Triaged => Invalid ** Changed in: gtk+3.0 (Ubuntu Focal) Status: Confirmed => Triaged ** Changed in: gtk+3.0 (Ubuntu Focal) Importance: Undecided => High ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value() Status in apport package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in apport source package in Focal: Invalid Status in gtk+3.0 source package in Focal: Triaged Status in apport source package in Lunar: Invalid Status in gtk+3.0 source package in Lunar: Triaged Bug description: Steps to reproduce -- 1. Use GNOME with GNOME shell 2. killall -11 gnome-shell Suspicious Apport log: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Error tracker - https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5 https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22 Stack trace --- Python: ``` File "apport-gtk", line 703, in app = GTKUserInterface(sys.argv) File "apport-gtk", line 68, in GTKUserInterface.__init__ self.widgets.add_from_file( os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui") ) ``` StacktraceTop: _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319 gtk_css_value_icon_theme_compute (icon_theme=, property_id=, provider=, style=, parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84 gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at ../../../../gtk/gtkcssstaticstyle.c:237 _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, provider=provider@entry=0x0, style=style@entry=0x1e7c320, parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122 gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at ../../../../gtk/gtkcssstaticstyle.c:195 Original report --- Session suddenly stopped and came back to login screen, all opened windows lost. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: apport-gtk 2.20.11-0ubuntu7 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 16:20:13 2019 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2018-06-16 (443 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 SegvAnalysis: Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax PC (0x7f532548f8c4) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 2001922] Re: Xorg crash
I've got a new crash after installing the xorg-core-dbgsym, the backtrace looks the same though. What else can I provide, other than reinstalling the whole machine? That's something I'd really like to avoid if possible [60.469] (EE) [60.469] (EE) Backtrace: [60.472] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5625c4342719] [60.473] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f129d1d3520] [60.473] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x258) [0x5625c41d7298] [60.473] (EE) 3: /usr/lib/xorg/Xorg (ProcSendEvent+0x848) [0x5625c41df688] [60.473] (EE) 4: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1e43) [0x5625c42b88b3] [60.474] (EE) 5: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x5625c42e2e7c] [60.474] (EE) 6: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x5625c42dbf51] [60.474] (EE) 7: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x5625c42dc14e] [60.474] (EE) 8: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x5625c433bc90] [60.474] (EE) 9: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x5625c433bf18] [60.474] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5625c41cc267] [60.475] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5625c41d0534] [60.475] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f129d1bad90] [60.476] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f129d1bae40] [60.476] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5625c41b9605] [60.476] (EE) [60.476] (EE) Segmentation fault at address 0x7fffbdcbf000 [60.476] (EE) Fatal server error: [60.476] (EE) Caught signal 11 (Segmentation fault). Server aborting -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2001922 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: My Ubuntu 22.04.1 LTS installation crashes, but I was not able to figure out how to reproducibly trigger the crash. The last time it happened was with firefox and zoom running, the display suddenly went black and after a few seconds the X login screen appeared, my session gone. There are files in /var/crash/ -rw-r--r-- 1 root whoopsie0 Jan 5 14:09 _usr_lib_xorg_Xorg.0.upload -rw-r- 1 root whoopsie 12792518 Jan 5 14:09 _usr_lib_xorg_Xorg.0.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:09 _usr_lib_xorg_Xorg.0.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _usr_bin_xfsettingsd.1000.upload -rw-r- 1 petr whoopsie 516897 Jan 5 14:13 _usr_bin_xfsettingsd.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _usr_bin_xfsettingsd.1000.uploaded -rw-r--r-- 1 petr whoopsie0 Jan 5 14:13 _opt_zoom_zoom.1000.upload -rw-r- 1 petr whoopsie 46590288 Jan 5 14:13 _opt_zoom_zoom.1000.crash -rw--- 1 whoopsie whoopsie 37 Jan 5 14:13 _opt_zoom_zoom.1000.uploaded and .xsession-errors.old ends with (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 0x649, atom "_NET_WM_STATE_STAYS_ON_TOP") (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0 Exiting due to channel error. Failed to parse arguments: Cannot open display: :0.0 Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open display. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0 (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Failed to parse arguments: Cannot open display: :0.0 Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Invalid MIT-MAGIC-COOKIE-1 keyxset: unable to open display ":0.0" Is it safe and useful to upload the files from /var/crash/? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop:
[Desktop-packages] [Bug 2003962] Re: chromium snap update makes system unresponsive, black screen
root@eva1:/var/log# apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://muug.ca/mirror/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Mesa Intel® HD Graphics 630 (KBL GT2) gnome 3.36.1 -- 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/2003962 Title: chromium snap update makes system unresponsive, black screen Status in chromium-browser package in Ubuntu: New Bug description: Every day for the past few days I've been getting notification 'pending update of chromium snap (n) days left'. I noticed earlier that chromium seems to crash my system when it updates(at least it warns now so i can know it's doing it) - as in when i come back to log in after the update, to xorg/gnome, the caps lock doesn't turn on when pressed, and there's nothing but a black screen - ie the system is completely unresponsive. tried hitting magic Sysrq+i to no avail. Had to hard reboot the system with the power button. system was working just fine last night at 1030pm, so whatever happened had to be after then is what did it: I just got another one saying 13 days left. from kern.log Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change from 0 to 303936 Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400 audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575 comm="apparmor_parser" Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400 audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1586575 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400 audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.hook.configure" pid=1586580 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400 audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" pid=1586577 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400 audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" pid=1586579 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400 audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromedriver" pid=1586578 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400 audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400 audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400 audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cancel" pid=1586584 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400 audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.accept" pid=1586583 comm="apparmor_parser" nothing in syslog from 2:38am ubuntu 20.04 linux: custom kernel 6.0.7 with squashfs bug hotfix ( but it's been crashing during snap updates since at least the 5.x ) root@eva1:/var/log# apt-cache policy chromium-browser chromium-browser: Installed: 80.0.3987.163-0ubuntu1 Candidate: 80.0.3987.163-0ubuntu1 Version table: *** 80.0.3987.163-0ubuntu1 500 500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status actual version post update: Version 109.0.5414.74 (Official Build) snap (64-bit) which is different than the last time I saw it ( 103.0.5060.134 ) so it's clearly updating itself, which supports the idea that the snap is updating during the crash but it would be nice to not hard lock my whole desktop system every 2 weeks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion:
[Desktop-packages] [Bug 2003962] Re: chromium snap update makes system unresponsive, black screen
themusicgod1@eva1:~$ snap changes ID Status Spawn Ready Summary 228 Donetoday at 02:38 CST today at 02:38 CST Auto-refresh snap "chromium" also supports that the update happened, and that the system was doing at least something until 2:38:44am when the last kern.log entry was found video driver: intel: root@eva1:/var/log# lsmod | grep vid video 61440 1 i915 backlight 24576 4 video,drm_display_helper,i915,drm -- 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/2003962 Title: chromium snap update makes system unresponsive, black screen Status in chromium-browser package in Ubuntu: New Bug description: Every day for the past few days I've been getting notification 'pending update of chromium snap (n) days left'. I noticed earlier that chromium seems to crash my system when it updates(at least it warns now so i can know it's doing it) - as in when i come back to log in after the update, to xorg/gnome, the caps lock doesn't turn on when pressed, and there's nothing but a black screen - ie the system is completely unresponsive. tried hitting magic Sysrq+i to no avail. Had to hard reboot the system with the power button. system was working just fine last night at 1030pm, so whatever happened had to be after then is what did it: I just got another one saying 13 days left. from kern.log Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change from 0 to 303936 Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400 audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575 comm="apparmor_parser" Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400 audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1586575 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400 audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.hook.configure" pid=1586580 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400 audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" pid=1586577 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400 audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" pid=1586579 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400 audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromedriver" pid=1586578 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400 audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400 audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400 audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cancel" pid=1586584 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400 audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.accept" pid=1586583 comm="apparmor_parser" nothing in syslog from 2:38am ubuntu 20.04 linux: custom kernel 6.0.7 with squashfs bug hotfix ( but it's been crashing during snap updates since at least the 5.x ) root@eva1:/var/log# apt-cache policy chromium-browser chromium-browser: Installed: 80.0.3987.163-0ubuntu1 Candidate: 80.0.3987.163-0ubuntu1 Version table: *** 80.0.3987.163-0ubuntu1 500 500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status actual version post update: Version 109.0.5414.74 (Official Build) snap (64-bit) which is different than the last time I saw it ( 103.0.5060.134 ) so it's clearly updating itself, which supports the idea that the snap is updating during the crash but it would be nice
[Desktop-packages] [Bug 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
This is a problem even at the desktop level. With the gnome desktop font set to the default 'Ubuntu 11' if I use an app (gImageReader in my case, see also https://github.com/manisandro/gImageReader/issues/613) to write certain decomposed characters (e.g. \u0069\u0300), they are not properly combined on the screen. This is a bad user experience. I've switched to 'DejaVu Sans 11' as a workaround, as it seems to handle everything correctly so far. However, the related DejaVu Sans Mono Book still messes this up (e.g. in gnome-terminal and gedit), but on different combined characters. So for monospace needs I've found FreeMono to cover the most ground (pkg: fonts-freefont-ttf). Try this, while switching between the default gnome-terminal font (Ubuntu Mono?) and DejaVu Sans Mono Book: $ echo -e '\u0069\u0300\u0020\u0254\u0327' ì ɔ̧ The ì renders correctly while the open o + cedilla doesn't, both here and with the terminal font set to DejaVu Sans Mono Book, but if you switch to the default font in the terminal the open o + cedilla renders correctly while the ì renders with both the dot and the grave accent on top of each other, rather than the dot disappearing like it should. I would guess that the related font definitions (Ubuntu Regular/Mono, DejaVu Sans Mono, possibly others) are simply incomplete when it comes to these less common character combinations. font-manager has been very helpful for side-by-side comparisons of sample text in multiple fonts. ** Bug watch added: github.com/manisandro/gImageReader/issues #613 https://github.com/manisandro/gImageReader/issues/613 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-hack package in Ubuntu: Incomplete Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: Confirmed Status in fonts-tlwg package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Confirmed Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: Confirmed Status in ttf-bitstream-vera package in Ubuntu: Won't Fix Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 1850282] Re: snap cannot be run while being upgraded − no user feedback
newer versions seem to at least warn the user that an upgrade is coming and to not have chromium open during the upgrade -- 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/1850282 Title: snap cannot be run while being upgraded − no user feedback Status in snapd: In Progress Status in chromium-browser package in Ubuntu: New Status in snapd package in Ubuntu: Confirmed Bug description: I've just upgraded to Ubuntu 19.10 with the new snap version of Chromium a week or two ago On starting my system today, I found that Chromium had disappeared from the launcher and wasn't even in the apps list. using the command 'chromium' didn't work either, giving me the message that chromium wasn't installed. "You can install it using snap install chromium". Then when I try to install it, I get the message "chromium is already installed". After about 10 minutes of digging around, I discovered that the chromium snap was disabled. I couldn't enable it because it was being refreshed. Come on! this is unacceptable behaviour for any tool but especially a browser which must be one of the most heavily used applications on Ubuntu. This will really hit the reputation of ubuntu with any user who has to take maybe more than 10 minutes to discover the problem, or may never discover it - Chromium may just mysteriously reappear some time later. Desired behaviour: Never disappear. Allow refresh to happen under the covers, transparently (as it used to with apt). Minimally acceptable behaviour: never disappear, but display a message "chromium is being refreshed. Please try later". $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: stable channels: stable:78.0.3904.70 2019-10-29 (920) 160MB - candidate: 78.0.3904.70 2019-10-29 (920) 160MB - beta: 78.0.3904.70 2019-10-22 (907) 165MB - edge: 79.0.3941.4 2019-10-21 (905) 159MB - installed: 78.0.3904.70(917) 167MB disabled To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1850282/+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 2003962] [NEW] chromium snap update makes system unresponsive, black screen
Public bug reported: Every day for the past few days I've been getting notification 'pending update of chromium snap (n) days left'. I noticed earlier that chromium seems to crash my system when it updates(at least it warns now so i can know it's doing it) - as in when i come back to log in after the update, to xorg/gnome, the caps lock doesn't turn on when pressed, and there's nothing but a black screen - ie the system is completely unresponsive. tried hitting magic Sysrq+i to no avail. Had to hard reboot the system with the power button. system was working just fine last night at 1030pm, so whatever happened had to be after then is what did it: I just got another one saying 13 days left. from kern.log Jan 26 02:38:38 eva kernel: [2487580.958314] loop20: detected capacity change from 0 to 303936 Jan 26 02:38:42 eva kernel: [2487585.064103] audit: type=1400 audit(1674722322.852:26188): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine" pid=1586575 comm="apparmor_parser" Jan 26 02:38:42 eva kernel: [2487585.064110] audit: type=1400 audit(1674722322.852:26189): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/snapd/17950/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1586575 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.240118] audit: type=1400 audit(1674722323.028:26190): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.hook.configure" pid=1586580 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487585.933271] audit: type=1400 audit(1674722323.721:26191): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.chromium" pid=1586577 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.166852] audit: type=1400 audit(1674722323.955:26192): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromium" pid=1586579 comm="apparmor_parser" Jan 26 02:38:43 eva kernel: [2487586.192853] audit: type=1400 audit(1674722323.981:26193): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.chromium.chromedriver" pid=1586578 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.321626] audit: type=1400 audit(1674722324.110:26194): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.cups" pid=1586582 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330187] audit: type=1400 audit(1674722324.118:26195): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cups-browsed" pid=1586585 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.330708] audit: type=1400 audit(1674722324.119:26196): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.cancel" pid=1586584 comm="apparmor_parser" Jan 26 02:38:44 eva kernel: [2487586.336931] audit: type=1400 audit(1674722324.125:26197): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap.cups.accept" pid=1586583 comm="apparmor_parser" nothing in syslog from 2:38am ubuntu 20.04 linux: custom kernel 6.0.7 with squashfs bug hotfix ( but it's been crashing during snap updates since at least the 5.x ) root@eva1:/var/log# apt-cache policy chromium-browser chromium-browser: Installed: 80.0.3987.163-0ubuntu1 Candidate: 80.0.3987.163-0ubuntu1 Version table: *** 80.0.3987.163-0ubuntu1 500 500 http://muug.ca/mirror/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status actual version post update: Version 109.0.5414.74 (Official Build) snap (64-bit) which is different than the last time I saw it ( 103.0.5060.134 ) so it's clearly updating itself, which supports the idea that the snap is updating during the crash but it would be nice to not hard lock my whole desktop system every 2 weeks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 09:44:00 2023 InstallationDate: Installed on 2017-04-18 (2108 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 109.0.5414.74 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2020-04-25 (1005 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal snap -- You received this bug notification because you are a member of Desktop Packages, which is
[Desktop-packages] [Bug 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fonts-ubuntu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-hack package in Ubuntu: Incomplete Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: Confirmed Status in fonts-tlwg package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Confirmed Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: Confirmed Status in ttf-bitstream-vera package in Ubuntu: Won't Fix Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: oxygen-fonts (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-hack package in Ubuntu: Incomplete Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: Confirmed Status in fonts-tlwg package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Confirmed Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: Confirmed Status in ttf-bitstream-vera package in Ubuntu: Won't Fix Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fonts-tlwg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-hack package in Ubuntu: Incomplete Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: Confirmed Status in fonts-tlwg package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Confirmed Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: Confirmed Status in ttf-bitstream-vera package in Ubuntu: Won't Fix Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fonts-noto (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-hack package in Ubuntu: Incomplete Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: Confirmed Status in fonts-tlwg package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Confirmed Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: Confirmed Status in ttf-bitstream-vera package in Ubuntu: Won't Fix Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 2002290] Re: Poor Arabic rendering in VTE
This bug was fixed in the package gnome-terminal - 3.46.7-1ubuntu2 --- gnome-terminal (3.46.7-1ubuntu2) lunar; urgency=medium * Use DejaVu as system font if LANG is Arabic (LP: #2002290) -- Gunnar Hjalmarsson Wed, 25 Jan 2023 20:14:38 +0100 ** Changed in: gnome-terminal (Ubuntu) Status: Fix Committed => Fix Released -- 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/2002290 Title: Poor Arabic rendering in VTE Status in gnome-terminal package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: New Bug description: VTE has a number of issues when it comes to rendering Arabic letters in the terminal, which could affect a number of languages (Arabic, Urdu, Persian... etc). Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed with spaces between its letters, making readability hard and sometimes not possible. Sometimes the letters are crushed together very closely making reading impossible too. Bug 2: If a non-Arabic text and an Arabic text are displayed together in the same line, then the entire line will be missed up and you won't be able to understand what is being said. Both of these bugs can be seen from the image I attached. I reported both of these bugs together because it's unlikely they can be fixed separately, probably they are related to each other. Problem can be seen in any VTE-based terminal. Here I am using GNOME Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu version and in any terminal version as well (it has been there since forever). I reported the bug here instead of upstream because that's what they said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs, but this bug is not related to Ubuntu only; it happens on all Linux distributions. Happy to provide any information you need, or any do tests or experiments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+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 2003889] Re: Please merge wpa 2.10-10 from Debian
This bug was fixed in the package wpa - 2:2.10-10ubuntu1 --- wpa (2:2.10-10ubuntu1) lunar; urgency=medium * Merge with Debian (LP: #2003889). Remaining changes: - debian/patches/lower_security_level_for_tls_1.patch: set the OpenSSL security level to 0 if that is the only option to continue the TLS negotiation, i.e., when TLS 1.0/1.1 are still allowed in wpa_supplicant default configuration and OpenSSL 3.0 with the constraint on MD5-SHA1 use. Patch proposed by Jouni Malinen on the upstream mailinglist (lp: #1958267) wpa (2:2.10-10) unstable; urgency=medium * Configure wpa_supplicant.service to create control sockets owned by group netdev (Closes: #1012844) -- Nathan Pratta Teodosio Wed, 25 Jan 2023 13:24:16 -0300 ** Changed in: wpa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/2003889 Title: Please merge wpa 2.10-10 from Debian Status in wpa package in Ubuntu: Fix Released Bug description: I built it successfully in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/2003889/+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 2003957] Re: Appearance set to dark but menus are the default
** Attachment added: "Screenshot from 2023-01-26 16-56-25.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003957/+attachment/5643605/+files/Screenshot%20from%202023-01-26%2016-56-25.png -- 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/2003957 Title: Appearance set to dark but menus are the default Status in gnome-shell package in Ubuntu: New Bug description: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003957/+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 2003957] [NEW] Appearance set to dark but menus are the default
Public bug reported: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Attachment added: "Screenshot from 2023-01-26 16-56-39.png" https://bugs.launchpad.net/bugs/2003957/+attachment/5643600/+files/Screenshot%20from%202023-01-26%2016-56-39.png -- 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/2003957 Title: Appearance set to dark but menus are the default Status in gnome-shell package in Ubuntu: New Bug description: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003957/+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 1999336] Re: New bugfix release 22.2.5
Tested locally on Intel Alder Lake and AMD W5700, works fine ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1999336 Title: New bugfix release 22.2.5 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Kinetic: Fix Committed Bug description: [Impact] Update Mesa to the latest bugfix release of the 22.2.x series for kinetic, and backport it to jammy for 22.04.2 image. diffstat: 177 files changed, 2100 insertions(+), 617 deletions(-) 191 commits [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1999336/+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 2003956] [NEW] package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1
Public bug reported: The upgrade from 20.04 to 22.04 failed which caused by can not upgrade firefox. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 109.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patten11134 F pulseaudio BuildID: 20230112150232 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Jan 26 21:17:07 2023 ErrorMessage: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-07-30 (1276 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 172.16.228.0/24 dev vmnet1 proto kernel scope link src 172.16.228.1 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600 192.168.142.0/24 dev vmnet8 proto kernel scope link src 192.168.142.1 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to jammy on 2023-01-26 (0 days ago) dmi.bios.date: 03/21/2022 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd03/21/2022:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn0JKGD4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2003956 Title: package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 Status in firefox package in Ubuntu: New Bug description: The upgrade from 20.04 to 22.04 failed which caused by can not upgrade firefox. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 109.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patten11134 F pulseaudio BuildID: 20230112150232 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Jan 26 21:17:07 2023 ErrorMessage: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-07-30 (1276 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 172.16.228.0/24 dev vmnet1 proto kernel scope link src 172.16.228.1 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600 192.168.142.0/24 dev vmnet8 proto kernel scope link src 192.168.142.1 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: 新的 firefox 软件包 pre-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to jammy on 2023-01-26 (0 days ago) dmi.bios.date: 03/21/2022 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0JKGD4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10
[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Changed in: postfix (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: In Progress Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Fix Released Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Fix Released Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Status in postfix package in Debian: Fix Released Status in zsh package in Debian: Confirmed Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1993191] Re: apport hook that collects snap's information is outdated
I already prepared the SRU but didn't involve the SRU team yet as the
fix is not release in Lunar yet.
--
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/1993191
Title:
apport hook that collects snap's information is outdated
Status in chromium-browser package in Ubuntu:
In Progress
Status in chromium-browser source package in Focal:
In Progress
Status in chromium-browser source package in Jammy:
In Progress
Status in chromium-browser source package in Kinetic:
In Progress
Bug description:
Impact
--
The Apport hook of the Chromium browser is outdated. It collects
information about core18, but the snap uses core20.
Moreover, it does not collect information about other interface
providers.
Test plan
-
1. Install the current chromium-browser.
2. Generate a report with
apport-bug --save /tmp/c1 chromium-browser
3. Install chromium-browser from proposed.
4. Generate another report with
apport-bug --save /tmp/c2 chromium-browser
Note: If the package was built and generated locally, you will need
APPORT_DISABLE_DISTRO_CHECK=1 in the environment.
5. Compare the files. The meaningful differences should be in the
Snap.Info. sections, namely:
- Snap.Info.core18 -> Snap.Info.core20
- {None} -> Snap.Info.cups
- {None} -> Snap.Info.gnome-3-38-2004
Differences should not be observed in Snap.Info.{chromium,core,gtk-
common-themes}.
Regression potential
Being Apport a bug reporting program, an incorrect parsing of the
SNAP_META file could lead to insertion of unwanted information in the
report or to suppress the insertion of information about the relevant
interfaces.
Original report
---
See https://bazaar.launchpad.net/~chromium-team/chromium-
browser/groovy-stable/view/head:/debian/apport/chromium-
browser.py#L59.
It collects information about core18, but the chromium snap was
rebased on core20 almost a year ago.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 1993191] Re: apport hook that collects snap's information is outdated
** Description changed:
+
+ Impact
+ --
+
+ The Apport hook of the Chromium browser is outdated. It collects
+ information about core18, but the snap uses core20.
+
+ Moreover, it does not collect information about other interface
+ providers.
+
+ Test plan
+ -
+
+ 1. Install the current chromium-browser.
+
+ 2. Generate a report with
+
+ apport-bug --save /tmp/c1 chromium-browser
+
+ 3. Install chromium-browser from proposed.
+
+ 4. Generate another report with
+
+ apport-bug --save /tmp/c2 chromium-browser
+
+ Note: If the package was built and generated locally, you will need
+ APPORT_DISABLE_DISTRO_CHECK=1 in the environment.
+
+ 5. Compare the files. The meaningful differences should be in the
+ Snap.Info. sections, namely:
+
+ - Snap.Info.core18 -> Snap.Info.core20
+ - {None} -> Snap.Info.cups
+ - {None} -> Snap.Info.gnome-3-38-2004
+
+ Differences should not be observed in Snap.Info.{chromium,core,gtk-
+ common-themes}.
+
+ Regression potential
+
+
+ Being Apport a bug reporting program, an incorrect parsing of the
+ SNAP_META file could lead to insertion of unwanted information in the
+ report or to suppress the insertion of information about the relevant
+ interfaces.
+
+
+ Original report
+ ---
+
See https://bazaar.launchpad.net/~chromium-team/chromium-browser/groovy-
stable/view/head:/debian/apport/chromium-browser.py#L59.
It collects information about core18, but the chromium snap was rebased
on core20 almost a year ago.
--
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/1993191
Title:
apport hook that collects snap's information is outdated
Status in chromium-browser package in Ubuntu:
In Progress
Status in chromium-browser source package in Focal:
In Progress
Status in chromium-browser source package in Jammy:
In Progress
Status in chromium-browser source package in Kinetic:
In Progress
Bug description:
Impact
--
The Apport hook of the Chromium browser is outdated. It collects
information about core18, but the snap uses core20.
Moreover, it does not collect information about other interface
providers.
Test plan
-
1. Install the current chromium-browser.
2. Generate a report with
apport-bug --save /tmp/c1 chromium-browser
3. Install chromium-browser from proposed.
4. Generate another report with
apport-bug --save /tmp/c2 chromium-browser
Note: If the package was built and generated locally, you will need
APPORT_DISABLE_DISTRO_CHECK=1 in the environment.
5. Compare the files. The meaningful differences should be in the
Snap.Info. sections, namely:
- Snap.Info.core18 -> Snap.Info.core20
- {None} -> Snap.Info.cups
- {None} -> Snap.Info.gnome-3-38-2004
Differences should not be observed in Snap.Info.{chromium,core,gtk-
common-themes}.
Regression potential
Being Apport a bug reporting program, an incorrect parsing of the
SNAP_META file could lead to insertion of unwanted information in the
report or to suppress the insertion of information about the relevant
interfaces.
Original report
---
See https://bazaar.launchpad.net/~chromium-team/chromium-
browser/groovy-stable/view/head:/debian/apport/chromium-
browser.py#L59.
It collects information about core18, but the chromium snap was
rebased on core20 almost a year ago.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Bug watch added: Debian Bug tracker #88 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88 ** Also affects: postfix (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: In Progress Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Fix Released Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Fix Released Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Status in postfix package in Debian: Unknown Status in zsh package in Debian: Confirmed Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1993191] Re: apport hook that collects snap's information is outdated
** Patch added: "lunar.diff" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+attachment/5643551/+files/lunar.diff -- 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/1993191 Title: apport hook that collects snap's information is outdated Status in chromium-browser package in Ubuntu: In Progress Status in chromium-browser source package in Focal: In Progress Status in chromium-browser source package in Jammy: In Progress Status in chromium-browser source package in Kinetic: In Progress Bug description: See https://bazaar.launchpad.net/~chromium-team/chromium- browser/groovy-stable/view/head:/debian/apport/chromium- browser.py#L59. It collects information about core18, but the chromium snap was rebased on core20 almost a year ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 1993191] Re: apport hook that collects snap's information is outdated
** Changed in: chromium-browser (Ubuntu) Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio) ** Changed in: chromium-browser (Ubuntu Kinetic) Assignee: Olivier Tilloy (osomon) => Nathan Teodosio (nteodosio) ** Changed in: chromium-browser (Ubuntu Focal) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: chromium-browser (Ubuntu Jammy) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- 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/1993191 Title: apport hook that collects snap's information is outdated Status in chromium-browser package in Ubuntu: In Progress Status in chromium-browser source package in Focal: In Progress Status in chromium-browser source package in Jammy: In Progress Status in chromium-browser source package in Kinetic: In Progress Bug description: See https://bazaar.launchpad.net/~chromium-team/chromium- browser/groovy-stable/view/head:/debian/apport/chromium- browser.py#L59. It collects information about core18, but the chromium snap was rebased on core20 almost a year ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993191/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one
This bug was fixed in the package software-properties - 0.96.24.32.20 --- software-properties (0.96.24.32.20) bionic; urgency=medium * softwareproperties/gtk/DialogUaAttach.py: fix an incomplete backport of recent changes, fix an exception raised when opening the attach dialog (lp: #2003527) software-properties (0.96.24.32.19) bionic; urgency=medium * Replace Livepatch integration with Ubuntu Pro (lp: #2003527) -- Sebastien Bacher Wed, 25 Jan 2023 18:50:56 +0100 ** Changed in: software-properties (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003527 Title: Replace the Livepatch tab by an Ubuntu Pro one Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact We want desktop integration with Ubuntu Pro, that will also replace the custom registration code we had for Livepatch which is integrated with the new service * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - until the service is in production to try the magic workflow, edit /etc/ubuntu-advantage/uaclient.conf to set contract_url: https://contracts.staging.canonical.com then 'ua refresh config') and use the non staging for token registration - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch' The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one
This bug was fixed in the package software-properties - 0.99.9.10 --- software-properties (0.99.9.10) focal; urgency=medium * Replace Livepatch integration with Ubuntu Pro (lp: #2003527) -- Sebastien Bacher Fri, 20 Jan 2023 13:34:21 +0100 ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003527 Title: Replace the Livepatch tab by an Ubuntu Pro one Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact We want desktop integration with Ubuntu Pro, that will also replace the custom registration code we had for Livepatch which is integrated with the new service * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - until the service is in production to try the magic workflow, edit /etc/ubuntu-advantage/uaclient.conf to set contract_url: https://contracts.staging.canonical.com then 'ua refresh config') and use the non staging for token registration - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch' The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003527] Re: Replace the Livepatch tab by an Ubuntu Pro one
This bug was fixed in the package software-properties - 0.99.22.5 --- software-properties (0.99.22.5) jammy; urgency=medium * Replace Livepatch integration with Ubuntu Pro (lp: #2003527) -- Sebastien Bacher Fri, 20 Jan 2023 11:58:10 +0100 ** Changed in: software-properties (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003527 Title: Replace the Livepatch tab by an Ubuntu Pro one Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Released Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: * Impact We want desktop integration with Ubuntu Pro, that will also replace the custom registration code we had for Livepatch which is integrated with the new service * Test case - ensure that the machine isn't attached to ubuntu pro (otherwise the screen would not be displayed) and is online $ pro status and `$ pro detach` if needed - until the service is in production to try the magic workflow, edit /etc/ubuntu-advantage/uaclient.conf to set contract_url: https://contracts.staging.canonical.com then 'ua refresh config') and use the non staging for token registration - $ software-properties-gtk -> the list of tabs should include an 'Ubuntu Pro' one and no 'Livepatch' The Ubuntu Pro tab should state 'This machine is not covered by an Ubuntu Pro subscription', display a 'Enable Ubuntu Pro' button and have other controls inactive - click 'Enable Ubuntu Pro' -> A dialog 'Enable Ubuntu Pro' opens -> the first option 'Enter code on ubuntu.com/pro/attach' is selected -> a pincode is displayed under the option - go to http//ubuntu.com/pro/attach and enter the pincode -> after some seconds the software-properties UI should update and display a green mark and 'Valid token' label on the right of the pincode - click 'Confirm' -> you should get an authentification prompt - enter your password -> a spinner starts animating instead of the 'Valid token' label -> once the attachment job is done the dialog is autoclosed -> the UI should now state 'Ubuntu Pro support is enabled', under Security 'ESM Infra', 'ESM Apps' and 'Kernel Livepatch' should be displayed an enabled (or without 'ESM Apps' if you don't have the current ubuntu-advantage-tools) - check that the '$ pro status' output matches the UI one - try enabling/disable options -> verify that the 'pro status' change accordingly - Click 'Disable Ubuntu Pro' -> you get asked for confirmation and password -> confirm that the UI is back to the original state and that 'pro status' confirm the system isn't attached to Ubuntu Pro anymore - Go through the testcase again but selecting the 'Or add token manually' option, the steps should be similar * Regression Potential There could be problems in the UI The new service could be not working as expected Strings are new and currently have no translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003527/+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 2003894] Re: package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 during
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/2003894 Title: package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 during ubuntu focal to jammy upgrade Status in firefox package in Ubuntu: Confirmed Bug description: During the upgrade from Ubuntu Focal to Ubuntu Jammy, the automatic installer for the firefox package which installs the snap package for firefox crashed and this is the bug report it asked me to submit. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 109.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-136.153-generic 5.4.218 Uname: Linux 5.4.0-136-generic x86_64 AddonCompatCheckDisabled: False AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-136-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' BuildID: 20230112150232 Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown Channel: Unavailable Date: Wed Jan 25 11:49:32 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown IpRoute: default via 10.91.23.1 dev eth0 proto dhcp src 10.91.23.253 metric 100 10.91.23.0/24 dev eth0 proto kernel scope link src 10.91.23.253 metric 100 10.91.23.1 dev eth0 proto dhcp scope link src 10.91.23.253 metric 100 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown NoProfiles: True Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 109.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-01-25 (0 days ago) dmi.bios.date: 12/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: X399 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/04/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399Taichi:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2003894/+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 1938152]
t -- 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/1938152 Title: Printing output gets truncated on 90.0.0 and 90.0.1 Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: There is a bug in 90.0.0 and 90.0.1 that truncates output while printing due to a scaling issue. It was fixed in 90.0.2 as it chopped off content on most websites. Package should be updated to include the fixes of 90.0.2 as this is affecting many users. There is no work around other then downgrading back to 89. More info can be found here: https://bugzilla.mozilla.org/show_bug.cgi?id=1720621 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1938152/+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
