[Desktop-packages] [Bug 2047262] Re: Firefox stopped inhibiting screensaver on video playback

2024-02-02 Thread Eugene San
** Summary changed:

- Firefox stops inhibiting screensaver after opening/un-suspending two or more 
tabs with video playback
+ Firefox stopped inhibiting screensaver on video playback

** Description changed:

+ Update (02/2024):
+ With Firefox 122 on Ubuntu-Mate 23.10, screensaver/powermanager inhibition is 
completely broken even with Mozilla's .deb package.
+ 
  After a fresh start of firefox, screen saver is blocked properly when
  playing video but after opening/un-suspending a few tabs with video,
  inhibition stops working.
  
  I was unable to come up with reproducible scenario but after a few hours
  of browsing it usually stops working. Restarting firefox fixes the
  problem.
  
  The bug first appeared around August and affects both .deb and snap
  packages.
  
  Tested on Ubuntu-Mate 22.04.3, Xorg, both Pulseaudio and Pipewire (if that's 
relevant).
  I don't see any relevant msgs in xsession-errors or system logs.

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

Title:
  Firefox stopped inhibiting screensaver on video playback

Status in firefox package in Ubuntu:
  New

Bug description:
  Update (02/2024):
  With Firefox 122 on Ubuntu-Mate 23.10, screensaver/powermanager inhibition is 
completely broken even with Mozilla's .deb package.

  After a fresh start of firefox, screen saver is blocked properly when
  playing video but after opening/un-suspending a few tabs with video,
  inhibition stops working.

  I was unable to come up with reproducible scenario but after a few
  hours of browsing it usually stops working. Restarting firefox fixes
  the problem.

  The bug first appeared around August and affects both .deb and snap
  packages.

  Tested on Ubuntu-Mate 22.04.3, Xorg, both Pulseaudio and Pipewire (if that's 
relevant).
  I don't see any relevant msgs in xsession-errors or system logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2047262/+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 2052343] [NEW] Native Messaging is not working with Snap version of Chromium

2024-02-02 Thread Eugene San
Public bug reported:

Native Messaging is not working with Snap version of Chromium.

Snap Firefox, Native Firefox and Native Chrome, work fine.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Native Messaging is not working with Snap version of Chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Native Messaging is not working with Snap version of Chromium.

  Snap Firefox, Native Firefox and Native Chrome, work fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2052343/+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 2052339] Re: Pipewire-alsa fails to expose output sound devices

2024-02-02 Thread Yotam Benshalom
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3830
   https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3830

** Also affects: pipewire via
   https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3830
   Importance: Unknown
   Status: Unknown

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

Title:
  Pipewire-alsa fails to expose output sound devices

Status in PipeWire:
  Unknown
Status in pipewire package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04.

  Since the update to pipewire-alsa 1.02, FTL: Faster than Light stopped
  playing audio. It reports:

  Starting audio library...
  Failed to open sound device

  This seems to be an upstream issue: 
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3830
  This issue is resolved upstream in pipewire-alsa 1.03, so I hope that the 
ubuntu package is updated soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pipewire-alsa 1.0.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  3 01:59:01 2024
  InstallationDate: Installed on 2022-01-31 (732 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to noble on 2024-01-19 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pipewire/+bug/2052339/+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 2052339] [NEW] Pipewire-alsa fails to expose output sound devices

2024-02-02 Thread Yotam Benshalom
Public bug reported:

Ubuntu 24.04.

Since the update to pipewire-alsa 1.02, FTL: Faster than Light stopped
playing audio. It reports:

Starting audio library...
Failed to open sound device

This seems to be an upstream issue: 
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3830
This issue is resolved upstream in pipewire-alsa 1.03, so I hope that the 
ubuntu package is updated soon.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: pipewire-alsa 1.0.2-1ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb  3 01:59:01 2024
InstallationDate: Installed on 2022-01-31 (732 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
SourcePackage: pipewire
UpgradeStatus: Upgraded to noble on 2024-01-19 (15 days ago)

** Affects: pipewire
 Importance: Unknown
 Status: Unknown

** Affects: pipewire (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

** Summary changed:

- Pipewire-alssa fails to expose output sound devices
+ Pipewire-alsa fails to expose output sound devices

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

Title:
  Pipewire-alsa fails to expose output sound devices

Status in PipeWire:
  Unknown
Status in pipewire package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04.

  Since the update to pipewire-alsa 1.02, FTL: Faster than Light stopped
  playing audio. It reports:

  Starting audio library...
  Failed to open sound device

  This seems to be an upstream issue: 
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3830
  This issue is resolved upstream in pipewire-alsa 1.03, so I hope that the 
ubuntu package is updated soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: pipewire-alsa 1.0.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  3 01:59:01 2024
  InstallationDate: Installed on 2022-01-31 (732 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to noble on 2024-01-19 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pipewire/+bug/2052339/+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 2050033] Re: gettext: msgfmt --java2 does not support Java 21

2024-02-02 Thread Launchpad Bug Tracker
This bug was fixed in the package gettext - 0.21-14ubuntu1

---
gettext (0.21-14ubuntu1) noble; urgency=medium

  * Update patches to support Java 21 (LP: #2050033):
- d/p/12-in-language-java-avoid-stack-overflow.patch: cherry-pick upstream
  patch to resolve Java 21 FTBFS.
- d/p/07-java-17-support.patch: add Java versions, set release level 8.

 -- Vladimir Petko   Mon, 22 Jan 2024
13:33:17 +1300

** Changed in: gettext (Ubuntu)
   Status: New => Fix Released

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

Title:
  gettext: msgfmt --java2 does not support Java 21

Status in gettext package in Ubuntu:
  Fix Released
Status in gettext package in Debian:
  New

Bug description:
  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --

  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---

  It appears that gettext package does not support Java 21.

  Note: gettext 0.22.4 refactors Java support. This delta can be safely
  dropped after a new upstream release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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 1729433]

2024-02-02 Thread Jeff Fortin Tam
I forgot to mention: the behavior observed in my comment #58 above is
consistent across the apps, i.e. on my end it behaves the same in Draw
like it does in Calc or Writer; I don't get minuscule windows on
demaximizing, but the window size restoration is still a coin toss
between "what it was" and "what is the width and height of the maximized
window".

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 1793124]

2024-02-02 Thread Grifoni-david
I ended up here looking for a solution to the problem of scrolling by cells in 
Libreoffice Calc, but I see that it is a long-standing issue. It seems 
incredible to me that in such a long time this has not been resolved.
I agree that a scroll-by-pixel option would solve the problem of large cells 
and make navigation smoother.

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+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 1729433]

2024-02-02 Thread Jeff Fortin Tam
It partially works for me in version 24.2 from Flathub, on Wayland GNOME
45 / Fedora 39.

What works: it doesn't become minuscule.

What doesn't work optimally: it seems the maximization state is maybe
not saved independently from width/height, because sometimes when you
unmaximize it, either...

* It unmaximizes to the previous window width/height (correct behavior), or;
* It unmaximizes to the "maximized window's width/height" (incorrect behavior)

See this demonstration video showing both situations with LibreOffice Calc 24.2:
https://youtu.be/dv8gb1GljzU

Further reference that might help as inspiration for implementation,
i.e. how it works in GNOME apps at least:
https://developer.gnome.org/documentation/tutorials/save-state.html (you
can see there that the maximization state is saved independently from
width/height, but also you need to infer that width/height shouldn't get
saved while in maximized state, only in windowed state)

---

Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Flatpak
Calc: threaded

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 1988754]

2024-02-02 Thread Libreoffice-commits
Matt K committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/05889c7fd814187aec3d88c056ece0cc33736868

tdf#149499 Prevent crash upon inserting page break and undoing

It will be available in 24.8.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  libreoffice writer crashes when edit the page break

Status in LibreOffice:
  In Progress
Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
  I have tried also using LibreOffice from ppa and it still crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+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 2052324] [NEW] Gnome not possible run from wsl

2024-02-02 Thread Tero Nevalainen
Public bug reported:

there is error xorg.conf (EE) no screens found(EE)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDmesg:
 Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
 ** (process:4174): WARNING **: 20:44:25.586: Unable to register authentication 
agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication 
agent already exists for the given subject
 Error registering local authentication agent: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent 
already exists for the given subject
Date: Fri Feb  2 20:44:11 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 
Lspci-vt:
 -+-[a214:00]---00.0  Red Hat, Inc. Virtio console
  \-[:00]-
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 480M
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: initrd=\initrd.img WSL_ROOT_INIT=1 panic=-1 nr_cpus=4 
bonding.max_bonds=0 dummy.numdummies=0 fb_tunnels=none console=hvc0 debug 
pty.legacy_count=0
ProcModules:
 
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
 Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with 
exit code 127: 
 ** (process:4187): WARNING **: 20:44:25.696: Unable to register authentication 
agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication 
agent already exists for the given subject
 Error registering local authentication agent: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent 
already exists for the given subject
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  Gnome not possible run from wsl

Status in xorg package in Ubuntu:
  New

Bug description:
  there is error xorg.conf (EE) no screens found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  Uname: Linux 5.15.133.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
   ** (process:4174): WARNING **: 20:44:25.586: Unable to register 
authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An 
authentication agent already exists for the given subject
   Error registering local authentication agent: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent 
already exists for the given subject
  Date: Fri Feb  2 20:44:11 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  Lspci-vt:
   -+-[a214:00]---00.0  Red Hat, Inc. Virtio console
\-[:00]-
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=vhci_hcd/8p, 480M
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: initrd=\initrd.img WSL_ROOT_INIT=1 panic=-1 nr_cpus=4 
bonding.max_bonds=0 dummy.numdummies=0 fb_tunnels=none console=hvc0 debug 
pty.legacy_count=0
  ProcModules:
   
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: 
   ** (process:4187): WARNING **: 20:44:25.696: Unable to register 
authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An

[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-02-02 Thread John Johansen
We have found that allowing the user namespace creation, and then
denying capabilities is in general handled much better by KDE. The the
case of the plasmashell and the browswer widget denying the creation of
the user namespace would cause a crash with a SIGTRAP backtrace, where
allowing the creation of the userns and then denying capabilities within
the user namespace would result in the browser widget falling back to a
sandbox that didn't use user namespaces, not ideal but better than a
crash. To make sure the widget was using the full sandbox we gave it a
profile (see QtWebEngineProcess in /etc/apparmor.d/plasmashell).

The apparmor package is adding a base set of profiles, including one for
the plasmashell and the unprivileged_userns profile.

We are willing to carry profiles in the apparmor package but are also
happy for other packages to carry them. Generally speaking, having the
profile carried in the package means its easier for the package
maintainer to update the profile, if that is something the package
maintainer is willing to do.

We are more than willing to take in profiles and patches to profiles, or
allow a maintainer to claim some profiles and move them out of the
apparmor package. What ever is best for the maintainer.

AppArmor does have a second set of profiles that are not installed by
default in the apparmor-profiles package. These profiles once installed
are not enabled by default but must be selectively enabled by the user.
If you are looking for a broader set of profiles as a base to start from
there is also the apparmor.d project
https://github.com/roddhjav/apparmor.d. They aren't tuned for ubuntu but
they can be a good starting point if a profile is needed.


Note: the current apparmor package doesn't allow you to specify the userns 
transition in policy. A new version of the apparmor package is coming that will 
allow it.

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akregator package in Ubuntu:
  Confirmed
Status in angelfish package in Ubuntu:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Confirmed
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Confirmed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Confirmed
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kiwix package in Ubuntu:
  Confirmed
Status in konqueror package in Ubuntu:
  Confirmed
Status in kontact package in Ubuntu:
  Confirmed
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Confirmed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2047737] Re: Nautilus crashes when opening folders that contain files with js or json extensions

2024-02-02 Thread Paul Peregud
/var/crash$ sudo cat _usr_bin_nautilus.1000.uploaded 
07f47ab6-c1bc-11ee-9cd1-fa163ec44ecd

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

Title:
  Nautilus crashes when opening folders that contain files with js or
  json extensions

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After attempting to open a folder that contains js or json files the app 
crashes.
  when testing from terminal I get a segmentation fault and no other error info.
  even enabling G_MESSAGES_DEBUG=all did not provide additional info.
  removing nautilus extensions, resetting xdg-mime for js/json, and disabling 
nautilus features (search, file count, etc ...) did not fix the problem either.

  additional info
  $ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:42.6-0ubuntu1
Candidate: 1:42.6-0ubuntu1
Version table:
   *** 1:42.6-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:42.2-0ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:42.0-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.6-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 14:50:09 2023
  InstallationDate: Installed on 2023-02-14 (319 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu3.1
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047737/+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 2047737] Re: Nautilus crashes when opening folders that contain files with js or json extensions

2024-02-02 Thread Paul Peregud
On my machine crash will occur if nautilus opens a directory containing
a .json file (haven't experimented with .js) which is not empty. Files
with trivial body, such as '""' or '"{}"' do trigger segfault. Empty
(zero sized) .json files does not trigger segfault.

```
segfault at 7fed30041ff8 ip 7fed50109bad sp 7fed30042000 error 6 in 
libgio-2.0.so.0.7200.4[7fed5000+111000] likely on CPU 6 (core 2, socket 0)
```

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

Title:
  Nautilus crashes when opening folders that contain files with js or
  json extensions

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After attempting to open a folder that contains js or json files the app 
crashes.
  when testing from terminal I get a segmentation fault and no other error info.
  even enabling G_MESSAGES_DEBUG=all did not provide additional info.
  removing nautilus extensions, resetting xdg-mime for js/json, and disabling 
nautilus features (search, file count, etc ...) did not fix the problem either.

  additional info
  $ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:42.6-0ubuntu1
Candidate: 1:42.6-0ubuntu1
Version table:
   *** 1:42.6-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:42.2-0ubuntu2.1 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:42.0-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.6-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 14:50:09 2023
  InstallationDate: Installed on 2023-02-14 (319 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu3.1
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047737/+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 2052307] Re: ALSA error: snd_pcm_open failed: Operation not supported.

2024-02-02 Thread Cliff Carson
Switching to VLC to play the same radio stream works as expected.

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

Title:
  ALSA error: snd_pcm_open failed: Operation not supported.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Getting the following error trying to play a radio stream in
  Audacious.

  ERROR ../src/libaudgui/util.cc:328 [audgui_simple_message]: ALSA
  error: snd_pcm_open failed: Operation not supported.

  This occurred after the daily update on 2/2/24.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:cliff  2336 F pipewire
   /dev/snd/controlC0:  cliff  2341 F wireplumber
   /dev/snd/controlC1:  cliff  2341 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  2 08:53:34 2024
  InstallationDate: Installed on 2023-12-02 (62 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2052307/+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 2052307] [NEW] ALSA error: snd_pcm_open failed: Operation not supported.

2024-02-02 Thread Cliff Carson
Public bug reported:

Getting the following error trying to play a radio stream in Audacious.

ERROR ../src/libaudgui/util.cc:328 [audgui_simple_message]: ALSA error:
snd_pcm_open failed: Operation not supported.

This occurred after the daily update on 2/2/24.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:cliff  2336 F pipewire
 /dev/snd/controlC0:  cliff  2341 F wireplumber
 /dev/snd/controlC1:  cliff  2341 F wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  2 08:53:34 2024
InstallationDate: Installed on 2023-12-02 (62 days ago)
InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2018
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3503
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

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

Title:
  ALSA error: snd_pcm_open failed: Operation not supported.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Getting the following error trying to play a radio stream in
  Audacious.

  ERROR ../src/libaudgui/util.cc:328 [audgui_simple_message]: ALSA
  error: snd_pcm_open failed: Operation not supported.

  This occurred after the daily update on 2/2/24.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:cliff  2336 F pipewire
   /dev/snd/controlC0:  cliff  2341 F wireplumber
   /dev/snd/controlC1:  cliff  2341 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  2 08:53:34 2024
  InstallationDate: Installed on 2023-12-02 (62 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2052307/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-02-02 Thread Scarlett Gately Moore
I have tested the above packages and created a profile for kontact
locally and kontact no longer crashes hooray. I am still sorting out
what I need to do here for the kde packages ( returning after a long
time gone ) Is there a package I need to add new profiles or is someone
else adding the new profiles? SO for my newbness.

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akregator package in Ubuntu:
  Confirmed
Status in angelfish package in Ubuntu:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Confirmed
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Confirmed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Confirmed
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kiwix package in Ubuntu:
  Confirmed
Status in konqueror package in Ubuntu:
  Confirmed
Status in kontact package in Ubuntu:
  Confirmed
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Confirmed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2052296] [NEW] The ability to copy/paste in the terminal was crashed.

2024-02-02 Thread Mikhail Medvedev
Public bug reported:

The ability to copy/paste in the terminal via c /
c if the national keyboard toggle is set as 
is broken again. The defect appeared after upgrading to xserver-xorg-
core/jammy 2:21.1.4-2ubuntu1.7~22.04.8ppa10 amd64

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  The ability to copy/paste in the terminal was crashed.

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The ability to copy/paste in the terminal via c /
  c if the national keyboard toggle is set as 
  is broken again. The defect appeared after upgrading to xserver-xorg-
  core/jammy 2:21.1.4-2ubuntu1.7~22.04.8ppa10 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2052296/+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 2052138] [NEW] After screen turns off and you turn it back on, weird corruption

2024-02-02 Thread George Salukvadze
Public bug reported:

When the laptop main screen turns off due to inactivity and then you
turn it back on, there is a weird corruption.

Restart helps.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
 GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  2 10:14:53 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[10de:24dc] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] 
[17aa:3a58]
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev c4) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:3a58]
InstallationDate: Installed on 2024-01-12 (21 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=9943bf1f-3749-4bb4-89b5-33eeb86f8afc ro quiet splash 
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN60WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K17763 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.60
dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN60WW:bd03/07/2023:br1.60:efr1.60:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
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 corruption mantic ubuntu

** Attachment added: "20240202_101543.mp4"
   
https://bugs.launchpad.net/bugs/2052138/+attachment/5744272/+files/20240202_101543.mp4

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

Title:
  After screen turns off and you turn it back on, weird corruption

Status in xorg package in Ubuntu:
  New

Bug description:
  When the laptop main screen turns off due to inactivity and then you
  turn it back on, there is a weird corruption.

  Restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 
15:37:48 UTC 2023
   GCC version:
  ApportVersion