[Desktop-packages] [Bug 1627524] Re: package libwebkit2gtk-4.0-37:armhf 2.12.5-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

[Luís Cunha dos Reis Infante da Câmara]

** Changed in: webkit2gtk (Ubuntu)
   Status: Invalid => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1627524

Title:
  package libwebkit2gtk-4.0-37:armhf 2.12.5-0ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in webkit2gtk package in Ubuntu:
  Incomplete

Bug description:
  while doing apt-get update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libwebkit2gtk-4.0-37:armhf 2.12.5-0ubuntu0.16.04.1
  Uname: Linux 4.4.19-v7+ armv7l
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libwebkit2gtk-4.0-37: Configure
   NULL: ConfigurePending
  Architecture: armhf
  Date: Sun Sep 25 18:12:43 2016
  DpkgTerminalLog:
   dpkg: error processing package libwebkit2gtk-4.0-37:armhf (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: webkit2gtk
  Title: package libwebkit2gtk-4.0-37:armhf 2.12.5-0ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1627524/+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 1627524] Re: package libwebkit2gtk-4.0-37:armhf 2.12.5-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

[Chris Guiver]

Thank you for reporting this bug to Ubuntu.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1627524

Title:
  package libwebkit2gtk-4.0-37:armhf 2.12.5-0ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in webkit2gtk package in Ubuntu:
  Incomplete

Bug description:
  while doing apt-get update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libwebkit2gtk-4.0-37:armhf 2.12.5-0ubuntu0.16.04.1
  Uname: Linux 4.4.19-v7+ armv7l
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libwebkit2gtk-4.0-37: Configure
   NULL: ConfigurePending
  Architecture: armhf
  Date: Sun Sep 25 18:12:43 2016
  DpkgTerminalLog:
   dpkg: error processing package libwebkit2gtk-4.0-37:armhf (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: webkit2gtk
  Title: package libwebkit2gtk-4.0-37:armhf 2.12.5-0ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1627524/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1976204] Re: Screen freeze if a 4K monitor is added to a 4K laptop while DING is active

[Daniel van Vugt]

The bug doesn't happen if I build mutter/gnome-shell from git. The bug
still doesn't happen if I build the Ubuntu 42.1 tags (jammy) from salsa,
with all Ubuntu patches.

Using the jammy release binaries the bug still occurs consistently. I am
not getting any results from gjs_dumpstack anymore (like above), but
earlier in the day I did get:

  == Stack trace for context 0x56139f48b4a0 ==
  gnome-shell[10091]: #0   7ffc53926a00 I   
resource:///org/gnome/shell/ui/windowManager.js:314 (2b03e27293d0 @ 78)
  gnome-shell[10091]: #1   7ffc53926a50 I   self-hosted:1181 (2e95f68b0a10 @ 
454)

So actually that's the same as Marco mentioned in comment #13.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1976204

Title:
  Screen freeze if a 4K monitor is added to a 4K laptop while DING is
  active

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  [Summary]
  The system will run into freeze if I connect the external monitor through 
DP/HDMI with dongle DA310 or Docking WD19TB

  [Steps to reproduce]
  1. Attact DA310 or WD19TB to DUT
  2. Cold Boot into OS
  3. Plug the DP/HDMI cable to DA310 or WD19TB
  4. Check the external monitor has signal
  5. Click keyboard or move mouse to check system can work well

  [Expected result]
  System won't be freeze with external monitor.

  [Actual result]
  Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse
  don't work during the screen freeze.
  It can be recovered after unplug the external monitor sometime.

  [gnome-shell stack trace]
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]:   ubuntu : TTY=pts/2 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
opened for user root(uid=0) by ubuntu(uid=1001)
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
closed for user root
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.

  This system is using OLED (3456x2160) panel, and I can't reproduce this issue 
on FHD panel.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-17 (75 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  Package: gnome-shell 42.1-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  RelatedPackageVersions: 

[Desktop-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

[Marian Rainer-Harbach]

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

-- 
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/1958267

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Fix Committed
Status in wpa package in Debian:
  New

Bug description:
  * Impact
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  * Test case
  try to connect to a TLS <= 1.1 access point

  * Regression potential
  the patch lowers the security level in some situation for compatibility, it 
shouldn't prevent connecting to newer hardware, still try to connect to 
different type of wifi with different security levels

  ---

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults

[Launchpad Bug Tracker]

** Branch linked: lp:~chromium-team/chromium-browser/bionic-dev

-- 
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/1978989

Title:
  FTBFS on armhf since version 102: the final link step segfaults

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Example build log:

  [51110/51110] LINK ./chrome
  FAILED: chrome 
  python3 "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- 
../../../../../usr/bin/clang++-10 
-Wl,--version-script=../../build/linux/chrome.map -Wl,--build-id=sha1 -fPIC 
-Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now --target=arm-linux-gnueabihf 
-no-canonical-prefixes -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-z,defs 
-Wl,--as-needed -nostdlib++ -pie -Wl,--disable-new-dtags -Wl,-rpath=\$ORIGIN -o 
"./chrome" -Wl,--start-group @"./chrome.rsp" ./libffmpeg.so -Wl,--end-group  
-ldl -lpthread -lrt -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lnss3 
-lnssutil3 -lsmime3 -lplds4 -lplc4 -lnspr4 -latk-1.0 -latk-bridge-2.0 -lcups 
-lgio-2.0 -ldbus-1 -latomic -lresolv -lexpat -luuid -ldrm -lxcb -lxkbcommon 
-lX11 -lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgbm 
-lwayland-client -lpangocairo-1.0 -lpango-1.0 -lcairo -lasound -lXi -lpci 
-latspi -lxshmfence
  clang++-10: error: unable to execute command: Segmentation fault (core dumped)
  clang++-10: error: linker command failed due to signal (use -v to see 
invocation)
  ninja: build stopped: subcommand failed.

  This is observed for the deb package builds targeting bionic (built
  with clang 10), on armhf only (other architectures build fine).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+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 1978989] Re: FTBFS on armhf since version 102: the final link step segfaults

[Olivier Tilloy]

The packages for chromium-browser 103.0.5060.53-0ubuntu0.18.04.1
successfully built on all architectures (including armhf) at the first
attempt in ppa:chromium-team/beta, so it looks like the patch is enough
to work around the problem.

** 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/1978989

Title:
  FTBFS on armhf since version 102: the final link step segfaults

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Example build log:

  [51110/51110] LINK ./chrome
  FAILED: chrome 
  python3 "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" -- 
../../../../../usr/bin/clang++-10 
-Wl,--version-script=../../build/linux/chrome.map -Wl,--build-id=sha1 -fPIC 
-Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now --target=arm-linux-gnueabihf 
-no-canonical-prefixes -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-z,defs 
-Wl,--as-needed -nostdlib++ -pie -Wl,--disable-new-dtags -Wl,-rpath=\$ORIGIN -o 
"./chrome" -Wl,--start-group @"./chrome.rsp" ./libffmpeg.so -Wl,--end-group  
-ldl -lpthread -lrt -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lglib-2.0 -lnss3 
-lnssutil3 -lsmime3 -lplds4 -lplc4 -lnspr4 -latk-1.0 -latk-bridge-2.0 -lcups 
-lgio-2.0 -ldbus-1 -latomic -lresolv -lexpat -luuid -ldrm -lxcb -lxkbcommon 
-lX11 -lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgbm 
-lwayland-client -lpangocairo-1.0 -lpango-1.0 -lcairo -lasound -lXi -lpci 
-latspi -lxshmfence
  clang++-10: error: unable to execute command: Segmentation fault (core dumped)
  clang++-10: error: linker command failed due to signal (use -v to see 
invocation)
  ninja: build stopped: subcommand failed.

  This is observed for the deb package builds targeting bionic (built
  with clang 10), on armhf only (other architectures build fine).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1978989/+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 1979098] Re: detached ua key and and attached back, now on extensive security maintenance until 31/12/9999

[Sebastien Bacher]

Thank you for your bug report. The information displayed there is indeed
incorrect, it is using the value returned by

$ ua status --format=json

so reassing to this component

** Package changed: software-properties (Ubuntu) => ubuntu-advantage-
tools (Ubuntu)

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => Confirmed

-- 
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/1979098

Title:
  detached ua key and and attached back, now on extensive security
  maintenance until 31/12/

Status in ubuntu-advantage-tools package in Ubuntu:
  Confirmed

Bug description:
  I have detached Ubuntu Advantage key and attached again, to make
  livepatch work. When I realized the updates tab changed to Extensive
  Security Maintenance until 31/12/ (essentially until Y10K)

  I tried re-opening the app, didn't work. Restarted the PC, didn't
  work. A partial upgrade, didn't work. I have a screenshot, it has been
  attached.

  Ubuntu Release: 22.04
  Version of software-properties-gtk: 0.99.22.2
  What I expected to happen: Livepatch working again, on the free subscription 
of LTS until 2027.
  What happened instead: Somehow got support until 31/12/ (again, Y10K.)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.22.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 17 19:03:59 2022
  InstallationDate: Installed on 2022-06-14 (2 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1979098/+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 1979175] Re: Gnome screensaver always overrides xscreensaver in xdg-screensaver

[Stuart Langridge]

Agreed that this is about the built-in screensaver, but I don't really
know what the best vocabulary is here; feel free to edit the bug title
if it's clearer.

As far as I can tell, there is no way to tell Gnome to stop owning the
d-bus screensaver names. (The answer is not to make everyone who needs
to inhibit the screensaver change yet again to do things another way, of
course.)

I use xscreensaver because it's cool; I would like the fun screensavers,
not just blankness, and I'd like the most up-to-date ones because there
are new ones.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1979175

Title:
  Gnome screensaver always overrides xscreensaver in xdg-screensaver

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  /usr/bin/xdg-screensaver checks for various different screensavers
  with lines like this:

  # Consider "xscreensaver" a separate DE
  xscreensaver-command -version 2> /dev/null | grep XScreenSaver > /dev/null && 
DE="xscreensaver"
  # Consider "gnome-screensaver" a separate DE
  dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.GetNameOwner string:org.gnome.ScreenSaver > /dev/null 2>&1 
&& DE="gnome_screensaver"

  However, gnome-shell always owns that org.gnome.ScreenSaver name on
  the bus and that cannot be prevented, even if gnome-screensaver is
  disabled. What this means is that if you install xscreensaver on a
  default Ubuntu installation and then disable gnome-screensaver, xdg-
  screensaver will still treat the running screensaver as being gnome-
  screensaver.

  When Firefox plays videos, it regularly calls "xdg-screensaver reset"
  to inhibit the screensaver, which is correct behaviour. However,
  because of the above bug, this call doesn't actually work because
  gnome-screensaver can't be told to stop owning its name on the bus. So
  what this means in practice is that on Ubuntu, if you install
  xscreensaver, then the screensaver will come on even while videos are
  playing in Firefox, and that's not supposed to happen.

  Proposed fix: move the xscreensaver check in xdg-screensaver to
  *after* the check for gnome-screensaver, so that if xscreensaver is
  present then it takes priority. This is likely to be correct because
  xscreensaver isn't present by default, so it being installed at all
  indicates some desire on the user's part to have it running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xdg-utils 1.1.3-2ubuntu1.20.04.2 [modified: usr/bin/xdg-screensaver]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 20 07:20:51 2022
  InstallationDate: Installed on 2020-06-20 (729 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1979175/+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 1978547] Re: nautilus crash on search

[Sebastien Bacher]

those error match bug #1726129 but could you maybe try to follow
https://wiki.ubuntu.com/Backtrace and get a stacktrace using gdb?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1978547

Title:
  nautilus crash on search

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 LTS (updated from 21.10)
  nautilus 1.42.1.1-0ubuntu
  15.15.0-37-generic
  flatpak installed
  Type=x11

  
  Expected to happen:
  1. open nautilus
  2. type anything in search box in any folder (remote or not, empty or not)
  3. nautilus do the search.

  What happens:
  1. open nautilus
  2. type anything in search box in any folder (remote or not, empty or not)
  3. nautilus crashes and prompt to end the process

  What I've tested:
  1. sudo apt install --reinstall nautilus
  2. rm ~/.config/nautilus
  none worked

  Strange result:
  sometimes (same search, same folder) it doesn't crash. After waiting about 
1min (!) doing nothing, the search results appear. After this happy long time, 
if I try other searches without closing the window, they work as expected.

  I would have posted this a week earlier, but then the strange result
  first came out. So I thought that I could figure it out, but I
  couldn't. Before that I didn't realize how important the search box
  was. Now I have installed nemo as I was waiting nautilus to be fixed.
  If I could test anything that it could help, I would love to help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978547/+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 1922884] Re: transmission-gtk segfault (core dumped)

[Sebastien Bacher]

** Changed in: transmission (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1922884

Title:
  transmission-gtk segfault (core dumped)

Status in transmission package in Ubuntu:
  Invalid

Bug description:
  Unable to launch transmission-gtk application, segfault.
  Ubuntu 21.04 up-to-date.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: transmission-gtk 3.00-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  7 09:47:02 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: transmission
  UpgradeStatus: Upgraded to hirsute on 2020-06-09 (301 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1922884/+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 1969315] Re: text in torrent info tabs change after opening it to gibberish

[Sebastien Bacher]

** Changed in: transmission (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1969315

Title:
  text in torrent info tabs change after opening it to gibberish

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  on transmission-gtk

  after opening the torrent's properties panel, the text at first it's showing 
ok, buy on mouse hover it changes to random text
  worked fine on 21.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 17 19:28:03 2022
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1969315/+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 1979143] Re: Segmentation fault after UI elements misplaced

[Sebastien Bacher]

*** This bug is a duplicate of bug 1969315 ***
https://bugs.launchpad.net/bugs/1969315

** This bug has been marked a duplicate of bug 1969315
   text in torrent info tabs change after opening it to gibberish

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1979143

Title:
  Segmentation fault after UI elements misplaced

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  Not sure how it started and what causes it, but now every time I open the 
properties window of a torrent, some UI labels would be misplaced (i.e. text 
appears in the wrong places in the UI).
  After a few minutes of these UI issues, transmission crashes with 
Segmentation fault.

  Running it from the terminal shows a lot of GTK error messages, e.g.:

  Gtk-CRITICAL **: 00:22:03.053: gtk_label_set_text: assertion
  'GTK_IS_LABEL (label)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 20 00:46:02 2022
  InstallationDate: Installed on 2021-03-10 (466 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (51 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1979143/+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 1979175] Re: Gnome screensaver always overrides xscreensaver in xdg-screensaver

[Sebastien Bacher]

Thank you for the bug report. Reversing the order of the check is
probably not right though, it would mean that on a machine with several
desktop environments installed, including one maybe using xscreensaver,
then 'default' GNOME sessions would stop using the right cmd.

Is using xscreensaver under GNOME really something users are doing, if
so it would be interesting to know why.

The right fix to handle those configurations would probably be to check
the gsettings key configuration, assuming that's how the GNOME
screensaver has been disabled.

** Changed in: xdg-utils (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1979175

Title:
  Gnome screensaver always overrides xscreensaver in xdg-screensaver

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  /usr/bin/xdg-screensaver checks for various different screensavers
  with lines like this:

  # Consider "xscreensaver" a separate DE
  xscreensaver-command -version 2> /dev/null | grep XScreenSaver > /dev/null && 
DE="xscreensaver"
  # Consider "gnome-screensaver" a separate DE
  dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.GetNameOwner string:org.gnome.ScreenSaver > /dev/null 2>&1 
&& DE="gnome_screensaver"

  However, gnome-shell always owns that org.gnome.ScreenSaver name on
  the bus and that cannot be prevented, even if gnome-screensaver is
  disabled. What this means is that if you install xscreensaver on a
  default Ubuntu installation and then disable gnome-screensaver, xdg-
  screensaver will still treat the running screensaver as being gnome-
  screensaver.

  When Firefox plays videos, it regularly calls "xdg-screensaver reset"
  to inhibit the screensaver, which is correct behaviour. However,
  because of the above bug, this call doesn't actually work because
  gnome-screensaver can't be told to stop owning its name on the bus. So
  what this means in practice is that on Ubuntu, if you install
  xscreensaver, then the screensaver will come on even while videos are
  playing in Firefox, and that's not supposed to happen.

  Proposed fix: move the xscreensaver check in xdg-screensaver to
  *after* the check for gnome-screensaver, so that if xscreensaver is
  present then it takes priority. This is likely to be correct because
  xscreensaver isn't present by default, so it being installed at all
  indicates some desire on the user's part to have it running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xdg-utils 1.1.3-2ubuntu1.20.04.2 [modified: usr/bin/xdg-screensaver]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 20 07:20:51 2022
  InstallationDate: Installed on 2020-06-20 (729 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1979175/+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 1979175] Re: Gnome screensaver always overrides xscreensaver in xdg-screensaver

[Sebastien Bacher]

Oh, also the use of 'gnome-screensaver' in the bug description is a bit
confusing since that's the name of the old standalone screensaver, which
is still available in the archive and separate deb binary. It is not the
built-in-GNOME screensaver, which the description seems to be referring
to?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1979175

Title:
  Gnome screensaver always overrides xscreensaver in xdg-screensaver

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  /usr/bin/xdg-screensaver checks for various different screensavers
  with lines like this:

  # Consider "xscreensaver" a separate DE
  xscreensaver-command -version 2> /dev/null | grep XScreenSaver > /dev/null && 
DE="xscreensaver"
  # Consider "gnome-screensaver" a separate DE
  dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.GetNameOwner string:org.gnome.ScreenSaver > /dev/null 2>&1 
&& DE="gnome_screensaver"

  However, gnome-shell always owns that org.gnome.ScreenSaver name on
  the bus and that cannot be prevented, even if gnome-screensaver is
  disabled. What this means is that if you install xscreensaver on a
  default Ubuntu installation and then disable gnome-screensaver, xdg-
  screensaver will still treat the running screensaver as being gnome-
  screensaver.

  When Firefox plays videos, it regularly calls "xdg-screensaver reset"
  to inhibit the screensaver, which is correct behaviour. However,
  because of the above bug, this call doesn't actually work because
  gnome-screensaver can't be told to stop owning its name on the bus. So
  what this means in practice is that on Ubuntu, if you install
  xscreensaver, then the screensaver will come on even while videos are
  playing in Firefox, and that's not supposed to happen.

  Proposed fix: move the xscreensaver check in xdg-screensaver to
  *after* the check for gnome-screensaver, so that if xscreensaver is
  present then it takes priority. This is likely to be correct because
  xscreensaver isn't present by default, so it being installed at all
  indicates some desire on the user's part to have it running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xdg-utils 1.1.3-2ubuntu1.20.04.2 [modified: usr/bin/xdg-screensaver]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 20 07:20:51 2022
  InstallationDate: Installed on 2020-06-20 (729 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: xdg-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1979175/+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 1970386] Re: Remmina toolbar does not hide in RDP session

[Sebastien Bacher]

There is a similar bug upstream on
https://gitlab.com/Remmina/Remmina/-/issues/2710

could you try if you get the issue also if you do?
$ GTK_THEME=Adwaita remmina

** Bug watch added: gitlab.com/Remmina/Remmina/-/issues #2710
   https://gitlab.com/Remmina/Remmina/-/issues/2710

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/1970386

Title:
  Remmina toolbar does not hide in RDP session

Status in remmina package in Ubuntu:
  New

Bug description:
  Remmina's toolbar does not autohide anymore when in fullscreen RDP
  session. I have to interact with the toolbar before it hides again.
  Normal behavior under Ubuntu 20.04 was that the toolbar automatically
  hides when there's no longer a mouseover event.

  OS: Ubuntu 22.04 LTS
  Package version: remmina 1.4.25+dfsg-1

  What I expect to happen: Remmina toolbar hides automatically when
  there is no mouseover event.

  What happened instead: Remmina toolbar does not hide and is displayed
  over my other applications.

  If there's anything I can do the help, please let me know!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1970386/+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 1969140] Re: Window minimize animation flickers and appears in the wrong place in Xorg sessions

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2317
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2317

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2317
   Importance: Unknown
   Status: Unknown

-- 
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/1969140

Title:
  Window minimize animation flickers and appears in the wrong place in
  Xorg sessions

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Graphical glitches appears while minimizing or maximizing apps in x11
  session randomly, screencast below

  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
  Date: Thu Apr 14 17:07:49 2022
  DisplayManager: gdm3
  GsettingsChanges:

  InstallationDate: Installed on 2022-04-12 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1969140/+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 1960590] Re: gnome-shell crashed with SIGSEGV in cogl_gl_framebuffer_bind() from _cogl_driver_gl_flush_framebuffer_state() from cogl_context_flush_framebuffer_state() from cogl

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2316
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2316

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2316
   Importance: Unknown
   Status: Unknown

-- 
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/1960590

Title:
  gnome-shell crashed with SIGSEGV in cogl_gl_framebuffer_bind() from
  _cogl_driver_gl_flush_framebuffer_state() from
  cogl_context_flush_framebuffer_state() from cogl_framebuffer_clear4f()
  from clutter_layer_node_pre_draw()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
41.3-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4f89714feb56bfeca16dbf20580cd82c75a2d6d1 
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/mutter/+bug/1960590/+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 1979118] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")

[Daniel van Vugt]

Crashing in getenv with a valid parameter like this should not be
possible so I think some heap corruption must have occurred before the
crash.

-- 
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/1979118

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/dea417d91da22f2d4de0980b3be8d98be8f8c100

  ---

  Just started, only firefox-trunk active

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.21.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Jun 18 15:41:24 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2022-05-14 (34 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 42.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f6ea4325c1d <__GI_getenv+173>:  cmp
(%r12),%bp
   PC (0x7f6ea4325c1d) ok
   source "(%r12)" (0xfca16778d75cc123) not located in a known VMA region 
(needed readable region)!
   destination "%bp" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_getenv (name=0x7f6ea355531e "NTCONFIG_SYSROOT") at ./stdlib/getenv.c:84
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   FcConfigBuildFonts () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1979118/+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 1979118] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")

[Daniel van Vugt]

Tracking in
https://errors.ubuntu.com/problem/dea417d91da22f2d4de0980b3be8d98be8f8c100

** Summary changed:

- gnome-shell crashed with SIGSEGV in __GI_getenv()
+ gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

** Tags added: jammy

** Description changed:

+ https://errors.ubuntu.com/problem/dea417d91da22f2d4de0980b3be8d98be8f8c100
+ 
+ ---
+ 
  Just started, only firefox-trunk active
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.21.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Jun 18 15:41:24 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
-  
+ 
  InstallationDate: Installed on 2022-05-14 (34 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 42.2-1ubuntu1
  SegvAnalysis:
-  Segfault happened at: 0x7f6ea4325c1d <__GI_getenv+173>:  cmp
(%r12),%bp
-  PC (0x7f6ea4325c1d) ok
-  source "(%r12)" (0xfca16778d75cc123) not located in a known VMA region 
(needed readable region)!
-  destination "%bp" ok
-  Stack memory exhausted (SP below stack segment)
+  Segfault happened at: 0x7f6ea4325c1d <__GI_getenv+173>:  cmp
(%r12),%bp
+  PC (0x7f6ea4325c1d) ok
+  source "(%r12)" (0xfca16778d75cc123) not located in a known VMA region 
(needed readable region)!
+  destination "%bp" ok
+  Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  __GI_getenv (name=0x7f6ea355531e "NTCONFIG_SYSROOT") at ./stdlib/getenv.c:84
-  ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
-  ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
-  FcConfigBuildFonts () from /lib/x86_64-linux-gnu/libfontconfig.so.1
-  ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
+  __GI_getenv (name=0x7f6ea355531e "NTCONFIG_SYSROOT") at ./stdlib/getenv.c:84
+  ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
+  ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
+  FcConfigBuildFonts () from /lib/x86_64-linux-gnu/libfontconfig.so.1
+  ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

-- 
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/1979118

Title:
  gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/dea417d91da22f2d4de0980b3be8d98be8f8c100

  ---

  Just started, only firefox-trunk active

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 42.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.21.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Jun 18 15:41:24 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2022-05-14 (34 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 42.2-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f6ea4325c1d <__GI_getenv+173>:  cmp
(%r12),%bp
   PC (0x7f6ea4325c1d) ok
   source "(%r12)" (0xfca16778d75cc123) not located in a known VMA region 
(needed readable region)!
   destination "%bp" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_getenv (name=0x7f6ea355531e "NTCONFIG_SYSROOT") at ./stdlib/getenv.c:84
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   FcConfigBuildFonts () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1979118/+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 1979181] Re: /usr/bin/gnome-shell:11:__GI_getenv:IA__FcConfigGetSysRoot:IA__FcConfigGetSysRoot:IA__FcDirCacheCreateUUID:IA__FcDirCacheRead

[Daniel van Vugt]

*** This bug is a duplicate of bug 1979118 ***
https://bugs.launchpad.net/bugs/1979118

** This bug has been marked a duplicate of bug 1979118
   gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")

-- 
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/1979181

Title:
  /usr/bin/gnome-
  
shell:11:__GI_getenv:IA__FcConfigGetSysRoot:IA__FcConfigGetSysRoot:IA__FcDirCacheCreateUUID:IA__FcDirCacheRead

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.1-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/dea417d91da22f2d4de0980b3be8d98be8f8c100 
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/gnome-shell/+bug/1979181/+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 1971126] Re: unable to click on application search results

[Daniel van Vugt]

Please check to see if Ubuntu Dock's auto-hide feature is the cause of
this bug (like in bug 1979096).

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/1971126

Title:
  unable to click on application search results

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When searching for applications under the Activities section,
  application results appear but cannot be clicked on to start them.
  Attempting to use the arrow keys to navigate between the results also
  doesn't work. However, if the enter key is pressed, the first result
  will load. Other types of results can be clicked on to open them, such
  as folder results in Files. This appears to be a regression from
  previous versions.

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  gnome-shell:
Installed: 42.0-2ubuntu1
Candidate: 42.0-2ubuntu1
Version table:
   *** 42.0-2ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  2 07:57:00 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-02-28 (62 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971126/+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 1979181] [NEW] /usr/bin/gnome-shell:11:__GI_getenv:IA__FcConfigGetSysRoot:IA__FcConfigGetSysRoot:IA__FcDirCacheCreateUUID:IA__FcDirCacheRead

[errors.ubuntu.com bug bridge]

*** This bug is a duplicate of bug 1979118 ***
https://bugs.launchpad.net/bugs/1979118

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.1-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/dea417d91da22f2d4de0980b3be8d98be8f8c100 
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: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: jammy

-- 
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/1979181

Title:
  /usr/bin/gnome-
  
shell:11:__GI_getenv:IA__FcConfigGetSysRoot:IA__FcConfigGetSysRoot:IA__FcDirCacheCreateUUID:IA__FcDirCacheRead

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.1-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/dea417d91da22f2d4de0980b3be8d98be8f8c100 
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/gnome-shell/+bug/1979181/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled

[Daniel van Vugt]

** Summary changed:

- X.org or Gnome-shell
+ gnome-shell search can't launch apps if dock auto-hide is enabled

** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1979096

Title:
  gnome-shell search can't launch apps if dock auto-hide is enabled

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  The problem happens, when I enable the dock to hide automatically.
  With this enabled, it is not possible to run the programs through the
  search. But when disabled, it is possible to search and run the
  programs. Here's the video of the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 17 18:21:45 2022
  DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed
   v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388]
  InstallationDate: Installed on 2021-04-15 (428 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago)
  dmi.bios.date: 03/04/2017
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX/BR
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
  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/gnome-shell/+bug/1979096/+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 1970386] Re: Remmina toolbar does not hide in RDP session

[jonju]

I can confirm this.
This should be fixed as you can hardly work:
Ubuntu 22.04 -> Remmina 1.4.25 (git n/a)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/1970386

Title:
  Remmina toolbar does not hide in RDP session

Status in remmina package in Ubuntu:
  New

Bug description:
  Remmina's toolbar does not autohide anymore when in fullscreen RDP
  session. I have to interact with the toolbar before it hides again.
  Normal behavior under Ubuntu 20.04 was that the toolbar automatically
  hides when there's no longer a mouseover event.

  OS: Ubuntu 22.04 LTS
  Package version: remmina 1.4.25+dfsg-1

  What I expect to happen: Remmina toolbar hides automatically when
  there is no mouseover event.

  What happened instead: Remmina toolbar does not hide and is displayed
  over my other applications.

  If there's anything I can do the help, please let me know!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1970386/+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 1979166] Re: hostapd not compiled with 802.11ax support

[tduffy83]

** Package changed: wpa (Ubuntu) => hostapd (Ubuntu)

-- 
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/1979166

Title:
  hostapd not compiled with 802.11ax support

Status in hostapd package in Ubuntu:
  New

Bug description:
  setting ieee80211ax=1 in the hostapd.conf results in a unknown
  configuration error.  802.11ax is supported in V2.10 of hostap, so
  it's likely that the make config flag is not set properly to enable
  this.  Need to update CONFIG_IEEE80211AX=y and recompile.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hostapd/+bug/1979166/+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 1979175] [NEW] Gnome screensaver always overrides xscreensaver in xdg-screensaver

[Stuart Langridge]

Public bug reported:

/usr/bin/xdg-screensaver checks for various different screensavers with
lines like this:

# Consider "xscreensaver" a separate DE
xscreensaver-command -version 2> /dev/null | grep XScreenSaver > /dev/null && 
DE="xscreensaver"
# Consider "gnome-screensaver" a separate DE
dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.GetNameOwner string:org.gnome.ScreenSaver > /dev/null 2>&1 
&& DE="gnome_screensaver"

However, gnome-shell always owns that org.gnome.ScreenSaver name on the
bus and that cannot be prevented, even if gnome-screensaver is disabled.
What this means is that if you install xscreensaver on a default Ubuntu
installation and then disable gnome-screensaver, xdg-screensaver will
still treat the running screensaver as being gnome-screensaver.

When Firefox plays videos, it regularly calls "xdg-screensaver reset" to
inhibit the screensaver, which is correct behaviour. However, because of
the above bug, this call doesn't actually work because gnome-screensaver
can't be told to stop owning its name on the bus. So what this means in
practice is that on Ubuntu, if you install xscreensaver, then the
screensaver will come on even while videos are playing in Firefox, and
that's not supposed to happen.

Proposed fix: move the xscreensaver check in xdg-screensaver to *after*
the check for gnome-screensaver, so that if xscreensaver is present then
it takes priority. This is likely to be correct because xscreensaver
isn't present by default, so it being installed at all indicates some
desire on the user's part to have it running.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xdg-utils 1.1.3-2ubuntu1.20.04.2 [modified: usr/bin/xdg-screensaver]
ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 20 07:20:51 2022
InstallationDate: Installed on 2020-06-20 (729 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: xdg-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xdg-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1979175

Title:
  Gnome screensaver always overrides xscreensaver in xdg-screensaver

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  /usr/bin/xdg-screensaver checks for various different screensavers
  with lines like this:

  # Consider "xscreensaver" a separate DE
  xscreensaver-command -version 2> /dev/null | grep XScreenSaver > /dev/null && 
DE="xscreensaver"
  # Consider "gnome-screensaver" a separate DE
  dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.GetNameOwner string:org.gnome.ScreenSaver > /dev/null 2>&1 
&& DE="gnome_screensaver"

  However, gnome-shell always owns that org.gnome.ScreenSaver name on
  the bus and that cannot be prevented, even if gnome-screensaver is
  disabled. What this means is that if you install xscreensaver on a
  default Ubuntu installation and then disable gnome-screensaver, xdg-
  screensaver will still treat the running screensaver as being gnome-
  screensaver.

  When Firefox plays videos, it regularly calls "xdg-screensaver reset"
  to inhibit the screensaver, which is correct behaviour. However,
  because of the above bug, this call doesn't actually work because
  gnome-screensaver can't be told to stop owning its name on the bus. So
  what this means in practice is that on Ubuntu, if you install
  xscreensaver, then the screensaver will come on even while videos are
  playing in Firefox, and that's not supposed to happen.

  Proposed fix: move the xscreensaver check in xdg-screensaver to
  *after* the check for gnome-screensaver, so that if xscreensaver is
  present then it takes priority. This is likely to be correct because
  xscreensaver isn't present by default, so it being installed at all
  indicates some desire on the user's part to have it running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xdg-utils 1.1.3-2ubuntu1.20.04.2 [modified: usr/bin/xdg-screensaver]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 20 07:20:51 2022
  InstallationDate: Installed on 2020-06-20 (729 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  

[Desktop-packages] [Bug 1965518] Re: [USB-Audio - USB Audio, recording] Recording problem

[Arwinnd]

Issue exists also on Ubuntu 22.04 last time when I was checking. I think
it was around this month.

-- 
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/1965518

Title:
  [USB-Audio - USB Audio, recording] Recording problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio
  Realtek ALC4080 is not recording audio. What I did found out, that the
  bar which indicates that something is recording is going up, when I
  play some sound on ubuntu, so input "thinks" it is output I think.

  If raport is somehow saying I was not using that mic at the moment,
  that is because I was using other card which I need to buy, for mic to
  temporarly work. I rechecked it before sending report, and yes, that
  original from MBO audio input is still not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity
  Date: Fri Mar 18 10:39:26 2022
  InstallationDate: Installed on 2022-03-12 (5 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed
  Symptom_Card: USB Audio - USB Audio
  Symptom_Type: None of the above
  Title: [USB-Audio - USB Audio, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D31
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965518/+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 1965518] Re: [USB-Audio - USB Audio, recording] Recording problem

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

-- 
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/1965518

Title:
  [USB-Audio - USB Audio, recording] Recording problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio
  Realtek ALC4080 is not recording audio. What I did found out, that the
  bar which indicates that something is recording is going up, when I
  play some sound on ubuntu, so input "thinks" it is output I think.

  If raport is somehow saying I was not using that mic at the moment,
  that is because I was using other card which I need to buy, for mic to
  temporarly work. I rechecked it before sending report, and yes, that
  original from MBO audio input is still not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity
  Date: Fri Mar 18 10:39:26 2022
  InstallationDate: Installed on 2022-03-12 (5 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed
  Symptom_Card: USB Audio - USB Audio
  Symptom_Type: None of the above
  Title: [USB-Audio - USB Audio, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D31
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965518/+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