[Desktop-packages] [Bug 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing
Same issue here, when setting Focus Follow Mouse, but with Xorg. I have a terminal and an editor opened. My mouse is over the terminal. I Alt+Tab to the editor, it changes focus to the editor and immediately focused back on the terminal -- effectively Alt+Tab is no longer working. Ubuntu 22.04.2 LTS. I do have two mouses plugged in -- in case this makes any difference, but when this happens I'm not touching them. -- 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/1969602 Title: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+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 2018175] [NEW] [Zenbook UP6502ZD_Q539ZD, Realtek ALC294, Speaker, Internal] No sound at all
Public bug reported: headphone jack works speakers don't work Tried some fixes I found in the ubuntu forums to no avail ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 29 22:40:09 2023 InstallationDate: Installed on 2023-04-21 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_AlsaPlaybackTestStderr: F a i l u r e t o s u s p e n d : N o s u c h e n t i t y Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Zenbook UP6502ZD_Q539ZD, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UP6502ZD.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UP6502ZD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUP6502ZD.305:bd06/30/2022:br5.25:svnASUSTeKCOMPUTERINC.:pnZenbookUP6502ZD_Q539ZD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUP6502ZD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook Flip dmi.product.name: Zenbook UP6502ZD_Q539ZD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-04-29T21:55:59.760443 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2018175 Title: [Zenbook UP6502ZD_Q539ZD, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: headphone jack works speakers don't work Tried some fixes I found in the ubuntu forums to no avail ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 29 22:40:09 2023 InstallationDate: Installed on 2023-04-21 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_AlsaPlaybackTestStderr: F a i l u r e t o s u s p e n d : N o s u c h e n t i t y Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Zenbook UP6502ZD_Q539ZD, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UP6502ZD.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UP6502ZD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31
[Desktop-packages] [Bug 1891623] Re: LO segfaults in one test on armhf when built with GCC 10
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- 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/1891623 Title: LO segfaults in one test on armhf when built with GCC 10 Status in gcc-10 package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: Expired Status in gcc-10 source package in Groovy: Invalid Status in libreoffice source package in Groovy: Won't Fix Status in gcc-10 source package in Hirsute: Won't Fix Status in libreoffice source package in Hirsute: Won't Fix Status in gcc-10 source package in Impish: Invalid Status in libreoffice source package in Impish: Won't Fix Bug description: I don't think we've had a successful build of Libreoffce on armhf in Ubuntu since gcc-10, it always eventually segfaults after 24 hours or so /<>/toolkit/source/controls/tkscrollbar.cxx: In member function ‘virtual void toolkit::UnoScrollBarControl::adjustmentValueChanged(const com::sun::star::awt::AdjustmentEvent&)’: /<>/toolkit/source/controls/tkscrollbar.cxx:175:5: internal compiler error: Segmentation fault 175 | } | ^ Please submit a full bug report, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623/+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 2017463] Re: chromium 111 and 112 have the wrong architecture in the user agent
** Description changed:
Using chromium browser on ubuntu bionic (the apt version), the wrong
user agent is present in chromium 111 and 112. When testing the arm64
build, the user agent is expected to contain the string aarch64 however
it contains the string x86_64. I am not aware if i386 and armhf builds
are also affected by this or not. This was not an issue in chromium 110
- builds, they had the correct user agent.
+ builds, they had the correct user agent. I am assuming this is likely an
+ issue with chromium source and not packaging in particular.
- There is YouTube bug to go alongside this as well. In chromium 110+, YouTube
is blocking higher than 480p content on Linux unless the user agent is x86_64.
Here is the YouTube debug info from chromium 110 (using the default user agent
which correctly has aarch64).
- ```
- Mozilla/5.0 (X11; Linux aarch64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/110.0.0.0 Safari/537.36
- ```
+ On the other hand, using x86_64 fixes a bug that youtube has on aarch64
+ user agent, where it thinks it's a Hisense TV and limits max resolution
+ to 480p since chromium 110+. playback debug info from youtube to show
+ that:
+
```
{
"ns": "yt",
"el": "detailpage",
"cpn": "HFfQQ5-Ud1Xq31GM",
"ver": 2,
"cmt": "0",
"fmt": "247",
"fs": "0",
"rt": "3.724",
"euri": "",
"lact": 3,
"cl": "525275539",
"mos": 0,
"state": "49",
"volume": 100,
"cbrand": "hisense",
"cbr": "Chrome",
"cbrver": "110.0.0.0",
"c": "WEB",
"cver": "2.20230421.01.00",
"cplayer": "UNIPLAYER",
"cmodel": "65a67gevs",
"cos": "X11",
"cplatform": "TV",
"hl": "en_US",
"cr": "US",
"len": "41920.021",
"fexp":
"23776346,23983296,23986022,24004644,24007246,24080738,24135310,24169501,24219381,24255163,24406084,24415864,24416291,24433679,24437577,24439361,24449113,24462372,24468691,24499792,24516157,24532854,24539776,24550457,24556606,39323074",
"feature": "g-high-rec",
"afmt": "251",
"muted": "0",
"docid": "HA7emw-FIjs",
"ei": "welFZNqxGPik0_wPjtWe6A4",
"plid": "AAX6C8oUWaU74VL5",
"referrer": "https://www.youtube.com/;,
"sdetail": "p:/",
"sourceid": "y",
"of": "xjLV454MDgULLBhO4MUTig",
"vm":
"CAQQARgBOjJBTE03ZXZMUmtPVHNLMHhveDl3MHZNWDhrcW9jY0tuYVVCMnB5LUxwdzNfNW9pSUEtd2JTQVBta0tESV85bzU2Nlg2VmdHV2VRY09NOWxsZ284RUdLelRtTVdVZGxmZXJLanZOOGlWX1g0eGFiSUJOMUlGc0JjM1RwMzJGeHpGdElTdmhaVmNoAQ",
"vct": "0.000",
"vd": "41920.021",
"vpl": "",
"vbu": "0.000-7.000",
"vpa": "0",
"vsk": "0",
"ven": "0",
"vpr": "1",
"vrs": "1",
"vns": "2",
"vec": "null",
"vemsg": "",
"vvol": "1",
"vdom": "1",
"vsrc": "1",
"vw": "693",
"vh": "390",
"lct": "0.000",
"lsk": false,
"lmf": false,
"lbw": "152435.812",
"lhd": "1.635",
"lst": "0.000",
"laa":
"itag_251_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_0_range_78167-212166_time_0.0-8.2_off_0_len_134000",
"lva":
"itag_247_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_0_range_130036-287966_time_0.0-7.0_off_0_len_157931_end_1",
"lar":
"itag_251_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_1_range_241354-432255_time_10.0-19.9_off_0_len_190902",
"lvr":
"itag_247_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_2_range_412688-502401_time_14.0-18.3_off_0_len_89714",
"laq": "220089",
"lvq": "214435",
"lab": "0.000-8.461",
"lvb": "0.000-7.000",
"ismb": 1329,
"leader": 1,
"relative_loudness": "-2.590",
"optimal_format": "720p",
"user_qual": 720,
"release_version": "youtube.player.web_20230418_00_RC00",
"debug_videoId": "HA7emw-FIjs",
"0sz": "false",
"op": "",
"yof": "false",
"dis": "",
"gpu":
"ANGLE_(NVIDIA_Corporation,_NVIDIA_Tegra_X1_(nvgpu)/integrated,_OpenGL_4.5.0)",
"debug_playbackQuality": "hd720",
"debug_date": "Sun Apr 23 2023 22:30:34 GMT-0400 (Eastern Daylight Time)"
}
```
-
- YouTube is reporting back that this is some random branded TV. Changing
- the user agent to x86_64 is a hack that allows for higher resolutions to
- be played back and the output from debug info is "normal" again.
-
- If you have contacts at Google that would be great if the second issue
- could be fixed at YouTube.
--
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/2017463
Title:
chromium 111 and 112 have the wrong architecture in the user agent
Status in chromium-browser package in Ubuntu:
New
Bug description:
Using chromium browser on ubuntu bionic (the apt version), the wrong
user agent is present in chromium 111 and 112. When testing the arm64
build, the user agent is expected to contain the string aarch64
however it contains the string x86_64. I am
[Desktop-packages] [Bug 2017463] Re: chromium 111 and 112 have the wrong architecture in the user agent
** Description changed:
Using chromium browser on ubuntu bionic (the apt version), the wrong
user agent is present in chromium 111 and 112. When testing the arm64
build, the user agent should contain the string aarch64 however it
contains the string x86_64. Many websites use the user agent to provide
download links for the correct architecture that the system is running
and this incorrect user agent will interfere with that process. I am not
aware if i386 and armhf builds are also affected by this or not. This
was not an issue in chromium 110 builds, they had the correct user
agent.
There is YouTube bug to go alongside this as well. In chromium 110+, YouTube
is blocking higher than 480p content on Linux unless the user agent is x86_64.
Here is the YouTube debug info from chromium 110 (using the default user agent
which correctly has aarch64).
```
Mozilla/5.0 (X11; Linux aarch64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/110.0.0.0 Safari/537.36
```
```
{
"ns": "yt",
"el": "detailpage",
"cpn": "HFfQQ5-Ud1Xq31GM",
"ver": 2,
"cmt": "0",
"fmt": "247",
"fs": "0",
"rt": "3.724",
"euri": "",
"lact": 3,
"cl": "525275539",
"mos": 0,
"state": "49",
"volume": 100,
"cbrand": "hisense",
"cbr": "Chrome",
"cbrver": "110.0.0.0",
"c": "WEB",
"cver": "2.20230421.01.00",
"cplayer": "UNIPLAYER",
"cmodel": "65a67gevs",
"cos": "X11",
"cplatform": "TV",
"hl": "en_US",
"cr": "US",
"len": "41920.021",
"fexp":
"23776346,23983296,23986022,24004644,24007246,24080738,24135310,24169501,24219381,24255163,24406084,24415864,24416291,24433679,24437577,24439361,24449113,24462372,24468691,24499792,24516157,24532854,24539776,24550457,24556606,39323074",
"feature": "g-high-rec",
"afmt": "251",
"muted": "0",
"docid": "HA7emw-FIjs",
"ei": "welFZNqxGPik0_wPjtWe6A4",
"plid": "AAX6C8oUWaU74VL5",
"referrer": "https://www.youtube.com/;,
"sdetail": "p:/",
"sourceid": "y",
"of": "xjLV454MDgULLBhO4MUTig",
"vm":
"CAQQARgBOjJBTE03ZXZMUmtPVHNLMHhveDl3MHZNWDhrcW9jY0tuYVVCMnB5LUxwdzNfNW9pSUEtd2JTQVBta0tESV85bzU2Nlg2VmdHV2VRY09NOWxsZ284RUdLelRtTVdVZGxmZXJLanZOOGlWX1g0eGFiSUJOMUlGc0JjM1RwMzJGeHpGdElTdmhaVmNoAQ",
"vct": "0.000",
"vd": "41920.021",
"vpl": "",
"vbu": "0.000-7.000",
"vpa": "0",
"vsk": "0",
"ven": "0",
"vpr": "1",
"vrs": "1",
"vns": "2",
"vec": "null",
"vemsg": "",
"vvol": "1",
"vdom": "1",
"vsrc": "1",
"vw": "693",
"vh": "390",
"lct": "0.000",
"lsk": false,
"lmf": false,
"lbw": "152435.812",
"lhd": "1.635",
"lst": "0.000",
"laa":
"itag_251_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_0_range_78167-212166_time_0.0-8.2_off_0_len_134000",
"lva":
"itag_247_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_0_range_130036-287966_time_0.0-7.0_off_0_len_157931_end_1",
"lar":
"itag_251_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_1_range_241354-432255_time_10.0-19.9_off_0_len_190902",
"lvr":
"itag_247_type_3_src_getRequestInfoForRange_segsrc_getRequestInfoForRange_seg_2_range_412688-502401_time_14.0-18.3_off_0_len_89714",
"laq": "220089",
"lvq": "214435",
"lab": "0.000-8.461",
"lvb": "0.000-7.000",
"ismb": 1329,
"leader": 1,
"relative_loudness": "-2.590",
"optimal_format": "720p",
"user_qual": 720,
"release_version": "youtube.player.web_20230418_00_RC00",
"debug_videoId": "HA7emw-FIjs",
"0sz": "false",
"op": "",
"yof": "false",
"dis": "",
"gpu":
"ANGLE_(NVIDIA_Corporation,_NVIDIA_Tegra_X1_(nvgpu)/integrated,_OpenGL_4.5.0)",
"debug_playbackQuality": "hd720",
"debug_date": "Sun Apr 23 2023 22:30:34 GMT-0400 (Eastern Daylight Time)"
}
```
YouTube is reporting back that this is some random branded TV. Changing
the user agent to x86_64 is a hack that allows for higher resolutions to
be played back and the output from debug info is "normal" again.
- I would like for this to be corrected at YouTube as well as in chromium-
- browser debs.
+ If you have contacts at Google that would be great if the second issue
+ could be fixed at YouTube.
** Description changed:
Using chromium browser on ubuntu bionic (the apt version), the wrong
user agent is present in chromium 111 and 112. When testing the arm64
- build, the user agent should contain the string aarch64 however it
- contains the string x86_64. Many websites use the user agent to provide
- download links for the correct architecture that the system is running
- and this incorrect user agent will interfere with that process. I am not
- aware if i386 and armhf builds are also affected by this or not. This
- was not an issue in chromium 110 builds, they had the correct user
- agent.
+ build, the user agent is expected to contain the string aarch64
[Desktop-packages] [Bug 2018163] [NEW] Ctrl+click no longer allows multiple files to be selected in the file upload window after upgrade to Lunar
Public bug reported: When uploading a file anywhere, using ctrl+click allows you to select more than one file at a time to upload several things in one go. After upgrading to Lunar, this no longer works. Shift+click still works for uploading multiple consecutive files in a list, but if they are needed in a certain order or not sitting one after another, you can no longer select them all by holding ctrl. It's only letting me select one file at a time. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 15:42:41 2023 ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome InstallationDate: Installed on 2022-07-09 (294 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-04-26 (3 days ago) ** Affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2018163 Title: Ctrl+click no longer allows multiple files to be selected in the file upload window after upgrade to Lunar Status in xdg-desktop-portal-gnome package in Ubuntu: New Bug description: When uploading a file anywhere, using ctrl+click allows you to select more than one file at a time to upload several things in one go. After upgrading to Lunar, this no longer works. Shift+click still works for uploading multiple consecutive files in a list, but if they are needed in a certain order or not sitting one after another, you can no longer select them all by holding ctrl. It's only letting me select one file at a time. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 15:42:41 2023 ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome InstallationDate: Installed on 2022-07-09 (294 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-04-26 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2018163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017677] Re: Unable to drag window by title bar
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 If you toggle maximised state with Super+Up or move left or right with Super+Left or Super+Right the window gets focused and dragging works again until you click inside a window again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2017677 Title: Unable to drag window by title bar Status in xorg package in Ubuntu: New Bug description: >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 Intermittent - more often than not this works fine. However, sometimes unable to move window by left-click & drag on the title bar. Not sure what exact conditions are, maybe when alt-tabbing to a different window or when moving onto a different monitor. Upgraded to 23.04 late yesterday and it's happened about 4 times so far today.When it doesn't work - the dragged window just stays still, but relocating the mouse to lower on the window (say the menu bar) resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 15:48:44 2023 DistUpgraded: 2023-04-24 20:50:34,905 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:1413] InstallationDate: Installed on 2021-12-13 (498 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Entroware Apollo ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=943b6cc2-9015-4dda-8079-67ac161950f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/26/2018 dmi.bios.release: 5.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02E dmi.board.asset.tag: Tag 12345 dmi.board.name: Apollo dmi.board.vendor: Entroware dmi.board.version: EL02R5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Entroware dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02E:bd03/26/2018:br5.2:efr5.2:svnEntroware:pnApollo:pvrEL02R5:rvnEntroware:rnApollo:rvrEL02R5:cvnEntroware:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Apollo dmi.product.sku: Not Applicable dmi.product.version: EL02R5 dmi.sys.vendor: Entroware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017677] Re: Unable to drag window by title bar
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 I had been using 23.04 for over a month since the beta. This only started happening on my PC today. What happened? This is incredibly annoying :/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2017677 Title: Unable to drag window by title bar Status in xorg package in Ubuntu: New Bug description: >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 Intermittent - more often than not this works fine. However, sometimes unable to move window by left-click & drag on the title bar. Not sure what exact conditions are, maybe when alt-tabbing to a different window or when moving onto a different monitor. Upgraded to 23.04 late yesterday and it's happened about 4 times so far today.When it doesn't work - the dragged window just stays still, but relocating the mouse to lower on the window (say the menu bar) resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 15:48:44 2023 DistUpgraded: 2023-04-24 20:50:34,905 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:1413] InstallationDate: Installed on 2021-12-13 (498 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Entroware Apollo ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=943b6cc2-9015-4dda-8079-67ac161950f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/26/2018 dmi.bios.release: 5.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02E dmi.board.asset.tag: Tag 12345 dmi.board.name: Apollo dmi.board.vendor: Entroware dmi.board.version: EL02R5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Entroware dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02E:bd03/26/2018:br5.2:efr5.2:svnEntroware:pnApollo:pvrEL02R5:rvnEntroware:rnApollo:rvrEL02R5:cvnEntroware:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Apollo dmi.product.sku: Not Applicable dmi.product.version: EL02R5 dmi.sys.vendor: Entroware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018160] [NEW] gnome-shell crashes when top right panel touched on touchscreen
Public bug reported: Version: ubuntu 23.04 Package: gnome-shell: Installed: 44.0-2ubuntu3 Candidate: 44.0-2ubuntu3 Version table: *** 44.0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status What I expected: I expected the wifi/bluetooth/dark... menu (in the upper right hand corner) to popup when I touched it on my touchscreen (clicking with a mouse or touchpad works fine, touchscreen press does not). This works as intended on Ubuntu 22.04.2 LTS. What happened: The menu popped up as intended, but 2 seconds later it disappeared, along with the top gnome shell panel (presumably it crashed). A few seconds later the gnome panel restores but without the menu. Running applications (such as firefox) don't seem to be affected. Running on an Asus Vivobook 14 (touchscreen). Tried using both safe mode and proprietary graphic mode with same result. Earlier versions of gnome seem to work fine. Same problem happens in Fedora too. Willing to do additional testing. Really wanna get this working. Thanks ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.480 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 18:06:49 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:13d2] LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP470EA_TP470EA ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset layerfs-path=minimal.standard.live.squashfs --- quiet splash SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TP470EA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP470EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP470EA.311:bd07/22/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP470EA_TP470EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP470EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP470EA_TP470EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash lunar ubuntu ** Attachment added: "The panel when opened properly" https://bugs.launchpad.net/bugs/2018160/+attachment/5669663/+files/Screenshot%20from%202023-04-29%2018-31-58.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2018160 Title: gnome-shell crashes when top right panel touched on touchscreen Status in xorg package in Ubuntu: New Bug description: Version: ubuntu 23.04 Package: gnome-shell: Installed: 44.0-2ubuntu3 Candidate: 44.0-2ubuntu3 Version table: *** 44.0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status What I expected: I expected the wifi/bluetooth/dark... menu (in the upper right hand corner) to popup when I touched it on my touchscreen (clicking with a mouse or touchpad works fine, touchscreen press does not). This works as intended on Ubuntu 22.04.2 LTS. What happened: The menu popped up as intended, but 2 seconds later it disappeared, along with the top gnome shell panel (presumably it crashed). A few seconds later the gnome panel restores but without the menu. Running applications
[Desktop-packages] [Bug 2018158] [NEW] [Multi Monitor] Built-in screen gets enabled changing the entire layout after resuming from the lockscreen
Public bug reported: Hello, first of all I am not entirely sure where to report this To explain the issue briefly, I have an ASUS TUF F15 laptop and two external monitors connected each to the HDMI and USB-C port with the laptop lid opened but the built-in screen disabled, what happens on the resume from the lock screen (after a couple of minutes, when all the screens go off), the layout gets messed up because the built in screen gets re-enabled automatically, the HDMI screen remains correctly on, but the USB-C screen gets disabled. I may have a clue on why this happens, I have an NVIDIA optimus setup where the Intel iGPU runs the USB-C monitor and the built-in monitor, the HDMI gets managed from the dedicated NVIDIA card so nothing changes here, and somwhow the builtin screen gets disabled then enabled when resuming the system, resulting in GNOME switching to it automatically as you have plugged in a new screen No matter how many times you force the screen disabling it, it will happen again. The workaround is to just to keep closed the laptop lid, of course, but since you can't power it on without the power button is a bit difficult. So I'd just like to keep it open. Another workaround I found is to unload the asus_nb_wmi and asus_wmi kernel modules as I thought they could be the issue, since they manage this specific platform, but as I said before I am not sure what to expect here, is it the intended behavior from GNOME? I mean, it's like someone plugs in some screens then the output gets enabled automatically but that's not the case of course, but the asus_wmi module may do some weird things. What you expected to happen: Resuming from the lock screen with all the screen layout in place What happened instead: Built-in screen enables itself, USB-C monitor gets disabled, HDMI monitor remains the same, the entire screen layout gets changed Workaround: Keeping the laptop lid closed or disabling asus_wmi and asus_nb_wmi kernel modules System affected: Ubuntu: 23.04 Lunar Lobster, tried also Ubuntu 22.04 and a custom flavor (PopOS 22.04) Don't mind the custom kernel, I tried different releases, including: Kernel: 6.2.0-20-generic Custom 6.2.13 and 6.3.0 kernels gnome-shell version: GNOME Shell 44.0 Info: inxi -F System: Host: haru-nb Kernel: 6.3.0-x64v4-xanmod1 arch: x86_64 bits: 64 Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: ASUSTeK product: ASUS TUF Dash F15 FX516PM_FX516PM v: 1.0 serial: Mobo: ASUSTeK model: FX516PM v: 1.0 serial: UEFI: American Megatrends LLC. v: FX516PM.329 date: 02/01/2023 Battery: ID-1: BAT0 charge: 64.0 Wh (98.9%) condition: 64.7/76.0 Wh (85.1%) volts: 15.8 min: 15.8 CPU: Info: quad core model: 11th Gen Intel Core i7-11370H bits: 64 type: MT MCP cache: L2: 5 MiB Speed (MHz): avg: 3001 min/max: 400/4800 cores: 1: 2068 2: 2607 3: 1718 4: 2707 5: 4300 6: 4284 7: 4312 8: 2018 Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: nvidia v: 530.41.03 Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.8 driver: X: loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa dri: iris gpu: i915,nvidia,nvidia-nvswitch resolution: 1: 2560x1440 2: 1920x1080~60Hz 3: N/A API: OpenGL v: 4.6 Mesa 23.0.2 renderer: Mesa Intel Xe Graphics (TGL GT2) Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel Device-2: NVIDIA GA106 High Definition Audio driver: snd_hda_intel Device-3: Thesycon System & Consulting GmbH DX3 Pro type: USB driver: snd-usb-audio Device-4: Logitech Blue Snowball type: USB driver: hid-generic,snd-usb-audio,usbhid Sound API: ALSA v: k6.3.0-x64v4-xanmod1 running: yes Sound Server-1: PipeWire v: 0.3.65 running: yes Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi IF: wlo1 state: up mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eno2 state: down mac: Device-3: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152 IF: enx00e04c6928d4 state: down mac: IF-ID-1: virbr0 state: down mac: Bluetooth: Device-1: Intel AX201 Bluetooth type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: bt-v: 3.0 RAID: Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd Drives: Local Storage: total: 8.65 TiB used: 3.51 TiB (40.6%) ID-1: /dev/nvme0n1 vendor: Crucial model: CT4000P3SSD8 size: 3.64 TiB ID-2: /dev/nvme1n1 vendor: SK Hynix model: HFM512GD3JX013N size: 476.94 GiB ID-3: /dev/sda type: USB vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB ID-4: /dev/sdb type: USB vendor: Toshiba model: External USB 3.0 size: 931.51 GiB Partition: ID-1: / size: 198.66 GiB used: 133.69 GiB (67.3%) fs: ext4 dev: /dev/nvme1n1p5 ID-2: /boot/efi size: 298.8 MiB used: 91.1 MiB (30.5%) fs: vfat dev:
[Desktop-packages] [Bug 2018152] [NEW] apt update fails for libsndfile after upgrade to Ubuntu 23.04
Public bug reported: After upgrade from Ubuntu 22.10 to 23.04 libsndfile fails with triggers ci file contains unknown directive 'activate-noawaiT' (mind the capital 'T') Solution: Edit /var/lib/dpkg/info/libsndfile1\:i386.triggers and replace the uppercase 'T' by a lowercase 't'. ** Affects: libsndfile (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/2018152 Title: apt update fails for libsndfile after upgrade to Ubuntu 23.04 Status in libsndfile package in Ubuntu: New Bug description: After upgrade from Ubuntu 22.10 to 23.04 libsndfile fails with triggers ci file contains unknown directive 'activate-noawaiT' (mind the capital 'T') Solution: Edit /var/lib/dpkg/info/libsndfile1\:i386.triggers and replace the uppercase 'T' by a lowercase 't'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/2018152/+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 2011606] Re: Black screen at 1st firefox start
Still a black screen on 1st start in Ubuntu 23.04 firefox 112.0.2 -- 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/2011606 Title: Black screen at 1st firefox start Status in firefox package in Ubuntu: Incomplete Bug description: Firefox snap 110.0.1 on Ubuntu 23.04 First start of firefox gives a black screen. Quit and restart FF starts fine. See these messages in journal: Mar 14 16:08:03 corrado-n5-ll-0224 systemd-udevd[445]: video4linux: Process '/usr/lib/snapd/snap-device-helper add snap_firefox_firefox /class/video4linux 0:0' failed with exit code 1. Mar 14 16:08:03 corrado-n5-ll-0224 systemd-udevd[445]: video4linux: Process '/usr/lib/snapd/snap-device-helper add snap_firefox_geckodriver /class/video4linux 0:0' failed with exit code 1. attaching journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2011606/+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 1987979]
So I had a look and I'm a bit lost on the packaging differences and how it interacts with snap to hack that. Do you have some PPA or something else with an uptodate deb of `speech-dispatcher` to build a snap? -- 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/1987979 Title: [snap] Firefox Narrator stopped working after upgrade from 20.04 to 22.04 Status in Mozilla Firefox: New Status in firefox package in Ubuntu: In Progress Bug description: I just noticed that the narrator feature, which reads articles out load with TTS in Firefox reading view stopped working after upgrading to 22.04. Another user reported the same problem on ask Ubuntu: https://askubuntu.com/questions/1418391/no-tts-voices-on- firefox-v102-0-after-upgrading-to-ubuntu-22-04-lts Also, if you have no clue what this is about: https://askubuntu.com/questions/953509/how-can-i-change-the-voice- used-by-firefox-reader-view-narrator-in-ubuntu --- 1) $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) Firefox is a snap now, but I guess for the feature to work it needs to detect TTS which is packaged as deb. $ snap list firefox Name Version Rev Tracking Publisher Notes firefox 104.0-3 1749 latest/stable mozilla✓ - $ apt-cache policy espeak speech-dispatcher-espeak-ng firefox espeak: Installed: 1.48.15+dfsg-3 Candidate: 1.48.15+dfsg-3 Version table: *** 1.48.15+dfsg-3 500 500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status speech-dispatcher-espeak-ng: Installed: 0.11.1-1ubuntu1 Candidate: 0.11.1-1ubuntu1 Version table: *** 0.11.1-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.11.1-1 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages firefox: Installed: (none) Candidate: 1:1snap1-0ubuntu2 Version table: 1:1snap1-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) open a website, enter reader mode, click the icon with sound waves and hear the text being read with TTS 4) the icon is missing --- Edit: I tested Firefox Flatpak and it is also affected, my best guess is that Firefox is not at fault. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017677] Re: Unable to drag window by title bar
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 ** This bug has been marked a duplicate of bug 2013216 Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2017677 Title: Unable to drag window by title bar Status in xorg package in Ubuntu: New Bug description: >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 Intermittent - more often than not this works fine. However, sometimes unable to move window by left-click & drag on the title bar. Not sure what exact conditions are, maybe when alt-tabbing to a different window or when moving onto a different monitor. Upgraded to 23.04 late yesterday and it's happened about 4 times so far today.When it doesn't work - the dragged window just stays still, but relocating the mouse to lower on the window (say the menu bar) resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 15:48:44 2023 DistUpgraded: 2023-04-24 20:50:34,905 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:1413] InstallationDate: Installed on 2021-12-13 (498 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Entroware Apollo ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=943b6cc2-9015-4dda-8079-67ac161950f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/26/2018 dmi.bios.release: 5.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02E dmi.board.asset.tag: Tag 12345 dmi.board.name: Apollo dmi.board.vendor: Entroware dmi.board.version: EL02R5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Entroware dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02E:bd03/26/2018:br5.2:efr5.2:svnEntroware:pnApollo:pvrEL02R5:rvnEntroware:rnApollo:rvrEL02R5:cvnEntroware:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Apollo dmi.product.sku: Not Applicable dmi.product.version: EL02R5 dmi.sys.vendor: Entroware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
Has this been fixed in 22.04 LTS ? I'd like to use that version of Ubuntu at my work place where color printing is needed… -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color Status in CUPS: New Status in atril package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Status in okular package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+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 2011404] Re: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire
just in case it might help someone else: I solved the problem for me by installing pulseaudio first (sudo apt -y install pulseaudio) afterwards the installation of vanilla-gnome-desktop went without any problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2011404 Title: vanilla-gnome-desktop depends on pulseaudio which conflicts with pipewire Status in pipewire package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in ubuntu-gnome-meta package in Ubuntu: Confirmed Bug description: Package vanilla-gnome-desktop 0.97 depends on pulseaudio which conflicts with pipewire-alsa and pipewire-audio which in turn are required for upgrading gnome to version 43. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2011404/+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 2018134] [NEW] [XMG PRO (E23), Realtek ALC1220, Speaker, Internal] No sound at all on either built in speakers, headphones or HDMI audio. Multiple reinstalls of alsa and others
Public bug reported: In settings when selecting the built in audio the levels are moving and it thinks it's outputting sound, but nothing. Same results when using headphones or as a troubleshooting I attempted to use the hdmi audio out as well. Already tried reinstalling alsa and pulseaudio, to no effect. When running lspci -v | grep -A7 -i "audio" I get the following audio devices. 00:1f.3 Audio device: Intel Corporation Device 7a50 (rev 11) Subsystem: CLEVO/KAPOK Computer Device d702 Flags: bus master, fast devsel, latency 32, IRQ 204, IOMMU group 14 Memory at 620313 (64-bit, non-prefetchable) [size=16K] Memory at 620300 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 01:00.1 Audio device: NVIDIA Corporation Device 22bd (rev a1) Subsystem: NVIDIA Corporation Device Physical Slot: 1 Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 15 Memory at 7400 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrik 3084 F pulseaudio /dev/snd/controlC1: patrik 3084 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 11:07:13 2023 InstallationDate: Installed on 2023-04-27 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrik 3084 F pulseaudio /dev/snd/controlC1: patrik 3084 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [XMG PRO (E23), Realtek ALC1220, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2023 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08RTR1 dmi.board.asset.tag: Tag 12345 dmi.board.name: PD5x_7xSNC_SND_SNE dmi.board.vendor: NB01 dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SchenkerTechnologiesGmbH dmi.chassis.version: N/A dmi.ec.firmware.release: 7.4 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08RTR1:bd04/12/2023:br7.8:efr7.4:svnSchenkerTechnologiesGmbH:pnXMGPRO(E23):pvrNotApplicable:rvnNB01:rnPD5x_7xSNC_SND_SNE:rvrNotApplicable:cvnSchenkerTechnologiesGmbH:ct10:cvrN/A:skuXPR15E23/XPR17E23: dmi.product.name: XMG PRO (E23) dmi.product.sku: XPR15E23 / XPR17E23 dmi.product.version: Not Applicable dmi.sys.vendor: SchenkerTechnologiesGmbH ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2018134 Title: [XMG PRO (E23), Realtek ALC1220, Speaker, Internal] No sound at all on either built in speakers, headphones or HDMI audio. Multiple reinstalls of alsa and others, speaker levels in settings are moving yet no sound created Status in alsa-driver package in Ubuntu: New Bug description: In settings when selecting the built in audio the levels are moving and it thinks it's outputting sound, but nothing. Same results when using headphones or as a troubleshooting I attempted to use the hdmi audio out as well. Already tried reinstalling alsa and pulseaudio, to no effect. When running lspci -v | grep -A7 -i "audio" I get the following audio devices. 00:1f.3 Audio device: Intel Corporation Device 7a50 (rev 11) Subsystem: CLEVO/KAPOK Computer Device d702 Flags: bus master, fast devsel, latency 32, IRQ 204, IOMMU group 14 Memory at 620313 (64-bit, non-prefetchable) [size=16K] Memory at 620300 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 01:00.1 Audio device: NVIDIA Corporation Device 22bd (rev a1) Subsystem: NVIDIA Corporation Device Physical Slot: 1 Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 15 Memory at 7400 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
[Desktop-packages] [Bug 2018133] [NEW] touchpad suddenly stopped working in 22.04
Public bug reported: I upgraded to Ubuntu 22.04 and after a week or two of usage, my laptop touchpad has stopped working suddenly. I have tried changing the kernels (I tried 6 or 7 different kernels) but it is not resolving the issue. Touchpad does not show in /proc/bus/input/devices. Laptop: Lenovo YOGA 520-14IKB Description: Ubuntu 22.04.2 LTS Release: 22.04 xserver-xorg-input-libinput: Installed: 1.2.1-1 Candidate: 1.2.1-1 Version table: *** 1.2.1-1 500 500 http://in.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-input-libinput 1.2.1-1 Uname: Linux 6.3.0-060300-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 14:30:16 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu InstallationDate: Installed on 2023-03-24 (35 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 81C8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-060300-generic root=UUID=b42be5cf-69f9-4a86-8689-67e955802248 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 2.50 dmi.bios.vendor: LENOVO dmi.bios.version: 4QCN50WW(V2.14) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 520-14IKB dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnLENOVO:bvr4QCN50WW(V2.14):bd05/14/2019:br2.50:efr2.50:svnLENOVO:pn81C8:pvrLenovoYOGA520-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct31:cvrLenovoYOGA520-14IKB:skuLENOVO_MT_81C8_BU_idea_FM_YOGA520-14IKB: dmi.product.family: YOGA 520-14IKB dmi.product.name: 81C8 dmi.product.sku: LENOVO_MT_81C8_BU_idea_FM_YOGA 520-14IKB dmi.product.version: Lenovo YOGA 520-14IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ubuntu ** Attachment added: "devices" https://bugs.launchpad.net/bugs/2018133/+attachment/5669562/+files/devices -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/2018133 Title: touchpad suddenly stopped working in 22.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I upgraded to Ubuntu 22.04 and after a week or two of usage, my laptop touchpad has stopped working suddenly. I have tried changing the kernels (I tried 6 or 7 different kernels) but it is not resolving the issue. Touchpad does not show in /proc/bus/input/devices. Laptop: Lenovo YOGA 520-14IKB Description: Ubuntu 22.04.2 LTS Release: 22.04 xserver-xorg-input-libinput: Installed: 1.2.1-1 Candidate: 1.2.1-1 Version table: *** 1.2.1-1 500 500 http://in.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-input-libinput 1.2.1-1 Uname: Linux 6.3.0-060300-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 14:30:16 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu InstallationDate: Installed on 2023-03-24 (35 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 81C8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-060300-generic root=UUID=b42be5cf-69f9-4a86-8689-67e955802248 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release:
[Desktop-packages] [Bug 2018132] [NEW] wifi connection lost on firefox crash
Public bug reported: firefox snap occasionally crashes, ie shown a black screen on startup. lately, when it crashes, nm-applet disappears from the tray without disconnecting from the router. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 11:13:03 2023 InstallationDate: Installed on 2023-04-24 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp src 192.168.1.3 metric 600 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.3 metric 600 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connected full full /org/freedesktop/NetworkManager/Devices/2 Forthnet-4jPPK eb56363e-28c9-432a-864b-cebcedbfdacf /org/freedesktop/NetworkManager/ActiveConnection/2 loloopback connected (externally) unknown unknown /org/freedesktop/NetworkManager/Devices/1 lo ccbf9b80-8294-485c-bc1c-3050ad48b3d9 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlo1 wifi-p2p disconnectednone none /org/freedesktop/NetworkManager/Devices/3 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 connected started full enabled enabled enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2018132 Title: wifi connection lost on firefox crash Status in network-manager package in Ubuntu: New Bug description: firefox snap occasionally crashes, ie shown a black screen on startup. lately, when it crashes, nm-applet disappears from the tray without disconnecting from the router. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager 1.42.4-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 11:13:03 2023 InstallationDate: Installed on 2023-04-24 (4 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp src 192.168.1.3 metric 600 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.3 metric 600 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connected full full /org/freedesktop/NetworkManager/Devices/2 Forthnet-4jPPK eb56363e-28c9-432a-864b-cebcedbfdacf /org/freedesktop/NetworkManager/ActiveConnection/2 loloopback connected (externally) unknown unknown /org/freedesktop/NetworkManager/Devices/1 lo ccbf9b80-8294-485c-bc1c-3050ad48b3d9 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlo1 wifi-p2p disconnectednone none /org/freedesktop/NetworkManager/Devices/3 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.42.4 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2018132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 2017976] Re: [SRU] libreoffice 7.5.3 for lunar
** Description changed: [Impact] * LibreOffice 7.5.3 is in its third bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.3_release * Version 7.5.2 is currently released in lunar. For a list of fixed bugs compared to 7.5.2 see the list of bugs fixed in the release candidates of 7.5.3 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1277/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. - Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14726196/+listing-archive-extra + Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/14726196/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230428_091914_c1745@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230428_145808_db4a8@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230428_112634_ff879@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230428_092959_ffca8@/log.gz * [riscv64] not available - * [s390x] ... + * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230428_214513_ee240@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. -- 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/2017976 Title: [SRU] libreoffice 7.5.3 for lunar Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Lunar: New Status in libreoffice source package in Mantic: New Bug description: [Impact] * LibreOffice 7.5.3 is in its third bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.3_release * Version 7.5.2 is currently released in lunar. For a list of fixed bugs compared to 7.5.2 see the list of bugs fixed in the release candidates of 7.5.3 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1277/ * More information about the upstream QA testing can be found here: * Automated tests
