date:20230110

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Confirmed

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

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE 
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3   
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0   

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+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 1999986] Re: ibus-daemon 170% CPU when using Flatpak Endeavour

2023-01-10 Thread DuckDuckWhale

"GNOME on Wayland" shows the same behavior as "Ubuntu on Wayland" after
installing the package.

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

Title:
  ibus-daemon 170% CPU when using Flatpak Endeavour

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  - Install Endeavour from Flatpak: 
https://flathub.org/apps/details/org.gnome.Todo
  - Synchronize a few Google tasks list
  - Attempt to type in the new task bar
  - Observe that `ibus-daemon` uses 170% CPU for half a minute before typing is 
possible

  Ubuntu 22.10 with Gnome, with both English and Chinese input methods
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/186/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections

Hmm.. OK. So I assume those connections would normally (not using the
netplan integration) be created in /run/NetworkManager/system-
connections/...?

So I think we need to find a way to detect NMS_KEYFILE_STORAGE_TYPE_RUN,
or respectively ignore any connections that are not of
NMS_KEYFILE_STORAGE_TYPE_ETC, but that data is not directly available in
the nms-keyfile-writer.c code. So it needs some more digging.

** Tags added: netplan-nm

** Tags removed: netplan-nm
** Tags added: nm-netplan

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

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE 
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3   
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0   

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections

Actually, https://developer-old.gnome.org/NetworkManager/stable/nm-dbus-
types.html#NMSettingsConnectionFlags suggests this could possibly be
avoided, by checking for `!is_external`, too.

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

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE 
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3   
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0   

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+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 1998893] Re: NV reverse prime HDMI has no output

andreas, directx-headers was dropped instead, and that upload rejected,
so the current version in proposed builds and is ready for updates.
sorry for the hassle, this was supposed to be the correct path to follow
all along :)

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

Title:
  NV reverse prime HDMI has no output

Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The X failed to load glamoregl module on Dell's new platforms, the module is 
needed by NV dGPU.

  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading 
/usr/lib/xorg/modules/libglamoregl.so
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: 
vendor="X.Org Foundation"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 
1.21.1.3, module version = 1.0.1
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org 
ANSI C Emulation, version 0.4
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does 
not support the 0xa78b PCI ID.
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to 
try glamor on llvmpipe
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor 
initialization failed

  [Fix]

  The upstream PR added missing ID for the platforms.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/

  After creating the test build to include the PR above, ODM verified
  passed on those platform.

  [Test case]
  Install fixed package on the systems, check that display works.

  [Where things could go wrong]
  Although one commit drops a couple of pci-id's, they were already dropped 
from the jammy kernel for lp1990242

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998893] Update Released

The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  NV reverse prime HDMI has no output

Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The X failed to load glamoregl module on Dell's new platforms, the module is 
needed by NV dGPU.

  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading 
/usr/lib/xorg/modules/libglamoregl.so
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: 
vendor="X.Org Foundation"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 
1.21.1.3, module version = 1.0.1
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org 
ANSI C Emulation, version 0.4
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does 
not support the 0xa78b PCI ID.
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to 
try glamor on llvmpipe
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor 
initialization failed

  [Fix]

  The upstream PR added missing ID for the platforms.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/

  After creating the test build to include the PR above, ODM verified
  passed on those platform.

  [Test case]
  Install fixed package on the systems, check that display works.

  [Where things could go wrong]
  Although one commit drops a couple of pci-id's, they were already dropped 
from the jammy kernel for lp1990242

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1998893] Re: NV reverse prime HDMI has no output

This bug was fixed in the package mesa - 22.0.5-0ubuntu0.3

---
mesa (22.0.5-0ubuntu0.3) jammy; urgency=medium

  * crocus-fix-leak-in-query-code.patch: Drop the patch so the other fix
can get through to updates.

mesa (22.0.5-0ubuntu0.2) jammy; urgency=medium

  * crocus-fix-leak-in-query-code.patch: Fix gnome-shell crashing on
older Intel hw. (LP: #1972977)
  * patches: Update pci-id's for ADL-S/RPL-S. (LP: #1998893)

 -- Timo Aaltonen   Thu, 05 Jan 2023 10:45:40 +0200

** Changed in: mesa (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  NV reverse prime HDMI has no output

Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The X failed to load glamoregl module on Dell's new platforms, the module is 
needed by NV dGPU.

  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) LoadModule: "glamoregl"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Loading 
/usr/lib/xorg/modules/libglamoregl.so
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) Module glamoregl: 
vendor="X.Org Foundation"
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: compiled for 
1.21.1.3, module version = 1.0.1
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: ABI class: X.Org 
ANSI C Emulation, version 0.4
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: MESA: warning: Driver does 
not support the 0xa78b PCI ID.
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): Refusing to 
try glamor on llvmpipe
  十二 05 10:04:55 /usr/libexec/gdm-x-session[1292]: (II) modeset(0): glamor 
initialization failed

  [Fix]

  The upstream PR added missing ID for the platforms.
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16320/
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17569/

  After creating the test build to include the PR above, ODM verified
  passed on those platform.

  [Test case]
  Install fixed package on the systems, check that display works.

  [Where things could go wrong]
  Although one commit drops a couple of pci-id's, they were already dropped 
from the jammy kernel for lp1990242

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998893/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end

This bug was fixed in the package mesa - 22.0.5-0ubuntu0.3

---
mesa (22.0.5-0ubuntu0.3) jammy; urgency=medium

  * crocus-fix-leak-in-query-code.patch: Drop the patch so the other fix
can get through to updates.

mesa (22.0.5-0ubuntu0.2) jammy; urgency=medium

  * crocus-fix-leak-in-query-code.patch: Fix gnome-shell crashing on
older Intel hw. (LP: #1972977)
  * patches: Update pci-id's for ADL-S/RPL-S. (LP: #1998893)

 -- Timo Aaltonen   Thu, 05 Jan 2023 10:45:40 +0200

** Changed in: mesa (Ubuntu Jammy)
   Status: Confirmed => Fix Released

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Triaged

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
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/mesa/+bug/1972977/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end

nope, reopening so that this will be fixed via the kinetic backport

** Changed in: mesa (Ubuntu Jammy)
   Status: Fix Released => Triaged

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Triaged

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
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/mesa/+bug/1972977/+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 1999986] Re: ibus-daemon 170% CPU when using Flatpak Endeavour

2023-01-10 Thread Gunnar Hjalmarsson

** Changed in: ibus (Ubuntu)
   Status: Incomplete => New

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

Title:
  ibus-daemon 170% CPU when using Flatpak Endeavour

Status in ibus package in Ubuntu:
  New

Bug description:
  - Install Endeavour from Flatpak: 
https://flathub.org/apps/details/org.gnome.Todo
  - Synchronize a few Google tasks list
  - Attempt to type in the new task bar
  - Observe that `ibus-daemon` uses 170% CPU for half a minute before typing is 
possible

  Ubuntu 22.10 with Gnome, with both English and Chinese input methods
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/186/+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 2002332] Re: [22.04] Cannot see thumbnail in MTP of PTP mode in Nautilus

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

** Changed in: nautilus (Ubuntu)
   Status: New => Confirmed

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

Title:
  [22.04] Cannot see thumbnail in MTP of PTP mode in Nautilus

Status in libmtp package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Usage of USB to see / copy photos from an Android phone is still
  useful in 2023

  With Ubuntu 22.04 up to date :

  - Connect your Android phone ( Android 10 lineageos here )

  - Choose MTP : open nautilus and browse -> No thumbnail for your pictures 
  - Choose PTP : open nautilus and browse -> No thumbnail for your pictures 
  - Choose PTP : open Shotwell and browse -> Some thumbnails appears

  Without thumbnails , it is almost impossible to choose what to copy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/2002332/+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 2002332] Re: [22.04] Cannot see thumbnail in MTP of PTP mode in Nautilus

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

** Changed in: libmtp (Ubuntu)
   Status: New => Confirmed

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

Title:
  [22.04] Cannot see thumbnail in MTP of PTP mode in Nautilus

Status in libmtp package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Usage of USB to see / copy photos from an Android phone is still
  useful in 2023

  With Ubuntu 22.04 up to date :

  - Connect your Android phone ( Android 10 lineageos here )

  - Choose MTP : open nautilus and browse -> No thumbnail for your pictures 
  - Choose PTP : open nautilus and browse -> No thumbnail for your pictures 
  - Choose PTP : open Shotwell and browse -> Some thumbnails appears

  Without thumbnails , it is almost impossible to choose what to copy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/2002332/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections

2023-01-10 Thread Alfonso Sanchez-Beato

Changing the check as suggested to:

if (!is_volatile && !is_nm_generated && !is_external) {
...

does help and netplan files for tun0 and tun1 are not written anymore.
But, when I create a VPN connection I still have problems.

$ network-manager.nmcli c import type openvpn file 
$ network-manager.nmcli c up 
$ network-manager.nmcli c
NAME  UUID  TYPE  DEVICE 
7b7fd99d-2651-4796-ba50-beda0890aab9  vpn   ens3   
tun0  1d7b454c-4897-4d3d-899a-619165a996bf  tun   tun0   
tun1  f7b9ba1f-496b-4cca-ae79-31db28a64c29  tun   tun1   
tun2  46935370-3662-4aac-b563-877214b48cd8  tun   tun2   
netplan-ens3  bec3d02a-c9e5-3283-92ab-ee43a4246c85  ethernet  ens3   
$ sudo /snap/bin/network-manager.nmcli d
DEVICE  TYPE  STATE   CONNECTION   
tun0tun   connected (externally)  tun0 
tun1tun   connected (externally)  tun1 
tun2tun   connected (externally)  tun2 
ens3ethernet  connected   netplan-ens3 
lo  loopback  unmanaged   --   
$ network-manager.nmcli c down default
$ network-manager.nmcli c 
NAME  UUID  TYPE  DEVICE 
netplan-ens3  bec3d02a-c9e5-3283-92ab-ee43a4246c85  ethernet  ens3   
tun0  8bc8d5b1-6000-4b78-9988-72d2d811bfb7  tun   tun0   
tun1  9d614be8-dac1-44ef-acfd-f9c60005b56f  tun   tun1   
default   7b7fd99d-2651-4796-ba50-beda0890aab9  vpn   -- 
$ ls /etc/netplan/
00-default-nm-renderer.yaml
50-cloud-init.yaml
90-NM-7b7fd99d-2651-4796-ba50-beda0890aab9.yaml
90-NM-46935370-3662-4aac-b563-877214b48cd8

Note that when you create an OpenVPN connection both a normal NM
connection and a new tunnel device (tun2) are created. NM creates a
external device for tun2. The interesting thing here is that the file
for tun2 is written after setting down the connection, and the NM daemon
actually forgets it (until you restart it and reads the netplan file).
Maybe this storing is in a different code path.

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

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE 
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3   
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0   

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections

Thanks for your testing and detailed analysis!

So IIUC the connection works as expected, but only after reloading the
connection profiles; it doesn't show up at the time it is expected,
right?

Does running 'nmcli connection reload' after the connection profile for
the VPN connection (tun2?) got written, make it show up in the NM
daemon?

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

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE 
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3   
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0   

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions


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

[Desktop-packages] [Bug 1999336] Re: New bugfix release 22.2.5

2023-01-10 Thread Boaz Dodin

As per description it looks like this bug is also about backporting to Jammy.
Should Jammy need to be added to the Affects table?

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

Title:
  New bugfix release 22.2.5

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  Update Mesa to the latest bugfix release of the 22.2.x series for
  kinetic, and backport it to jammy for 22.04.2 image.

  diffstat:
  177 files changed, 2100 insertions(+), 617 deletions(-)
  191 commits

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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

[Desktop-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack

2023-01-10 Thread Łukasz Zemczak

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-15 into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-15/1:15.0.6-3~ubuntu0.22.04.2 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: llvm-toolchain-15 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Backport packages for 22.04.2 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-15 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in spirv-headers package in Ubuntu:
  Invalid
Status in spirv-llvm-translator-14 package in Ubuntu:
  Invalid
Status in spirv-llvm-translator-15 package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in libdrm source package in Jammy:
  Fix Committed
Status in llvm-toolchain-15 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  In Progress
Status in spirv-headers source package in Jammy:
  Fix Committed
Status in spirv-llvm-translator-14 source package in Jammy:
  In Progress
Status in spirv-llvm-translator-15 source package in Jammy:
  Fix Committed

Bug description:
  [Impact
  The graphics HWE stack from kinetic needs to be backported for 22.04.2

  directx-headers
  - build-dep of the new Mesa

  libdrm
  - build-dep of the new Mesa

  llvm-15
  - new package in jammy
  - build-dep of the new Mesa

  mesa
  - new major release (22.2.x)
  - new HW support, like AMD RDNA3, Intel DG2

  spirv-headers
  - needed by s-l-t-15

  spirv-llvm-translator-14
  - needed to bootstrap libclc from llvm

  spirv-llvm-translator-15
  - needed for the actual libclc-15 after initial bootstrap

  Bootstrapping plan:
  - s-l-t-14 built from NEW
  - llvm-15 built with s-l-t-14
  - s-l-t-15 built against llvm-15
  - llvm-15 built again with s-l-t-15
  -> mesa ready for building

  [Test case]
  Install the new mesa on various hw, see that everything still works like 
before or better.

  spirv-headers:
  - test reverse-build-deps that they still build
  Reverse-Build-Depends
  * glslang
  * intel-graphics-compiler
  * spirv-llvm-translator-14
  * spirv-llvm-translator-15
  * spirv-tools
  * vkbasalt
  * vkd3d
  * vulkan-validationlayers

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 22.2.x in order to minimize the chance for those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections

2023-01-10 Thread Alfonso Sanchez-Beato

> So IIUC the connection works as expected, but only after reloading the
connection profiles; it doesn't show up at the time it is expected,
right?

Hm, not sure if we mean the same. That two connections (tun2 and
) appear after connecting to the VPN is expected. NM
recognizes tun2 as "external" as it is an auxiliary device/connection
created by the OpenVPN plugin. The problem that is happening is that
that connection is being stored in /etc/netplan/, which should not be
the case.

Note that tun0 and tun1 are slightly different as those are created by
the OpenVPN server also running on the device. The netplan files for
them are not written anymore after changing the patch.

> Does running 'nmcli connection reload' after the connection profile
for the VPN connection (tun2?) got written, make it show up in the NM
daemon?

No, that does not happen. But it happens if I reboot the system. I think
that is because there is some file in /run that prevents this from
happening if just reloading things.

Before rebooting:
$ sudo ls run/NetworkManager/system-connections/ -l
total 20
lrwxrwxrwx 1 root root9 Jan 10 11:22 
891164a5-1fed-42b8-8f6e-903db6396d5e.nmmeta -> /dev/null
-rw--- 1 root root  403 Jan 10 11:24 
netplan-NM-891164a5-1fed-42b8-8f6e-903db6396d5e.nmconnection
-rw--- 1 root root 1248 Jan 10 11:24 
netplan-NM-af486148-2495-48a9-9704-2a1230e97e32.nmconnection
-rw--- 1 root root  131 Jan 10 11:24 netplan-ens3.nmconnection
-rw--- 1 root root  336 Jan 10 09:37 tun0.nmconnection
-rw--- 1 root root  336 Jan 10 09:37 tun1.nmconnection

After rebooting:
$ sudo ls run/NetworkManager/system-connections/ -l
total 20
-rw--- 1 root root  403 Jan 10 11:28 
netplan-NM-891164a5-1fed-42b8-8f6e-903db6396d5e.nmconnection
-rw--- 1 root root 1248 Jan 10 11:28 
netplan-NM-af486148-2495-48a9-9704-2a1230e97e32.nmconnection
-rw--- 1 root root  131 Jan 10 11:28 netplan-ens3.nmconnection
-rw--- 1 root root  336 Jan 10 11:28 tun0.nmconnection
-rw--- 1 root root  336 Jan 10 11:28 tun1.nmconnection

891164a5 was tun2 and af486148 the VPN connection.

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

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE 
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3   
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0   

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+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 1972133] Re: +/- geometry offsets don't work under Wayland

2023-01-10 Thread Geert Uytterhoeven

GNOME-TERMINAL(1) says:

   --geometry=GEOMETRY
   Set the window size as COLSxROWS+X+Y. For example, 80x24 or
   80x24+200+200.

When run under Wayland, only "COLSxROWS" are honoured, "+X+Y" are not.
When run under Xorg, everything works as expected.

I have a script that creates tens of windows and tabs at predefined
positions, which now needs manual repositioning.

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

Title:
  +/- geometry offsets don't work under Wayland

Status in xwayland package in Ubuntu:
  Confirmed

Bug description:
  When using the default wayland-based session in Ubuntu 22.04, trying
  to use +/- to control window placement doesn't work.  E.g. the
  following should give me a gnome-terminal window in the lower-right
  corner of the screen:

gnome-terminal --geometry -0-0

  It does not; instead it stacks it with a window position just slightly
  down from and to the left of the previous window.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xwayland 2:22.1.1-1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  8 18:14:34 2022
  InstallationDate: Installed on 2019-12-23 (867 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: xwayland
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1972133/+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 1972133] Re: +/- geometry offsets don't work under Wayland

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

** Changed in: xwayland (Ubuntu)
   Status: New => Confirmed

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

Title:
  +/- geometry offsets don't work under Wayland

Status in xwayland package in Ubuntu:
  Confirmed

Bug description:
  When using the default wayland-based session in Ubuntu 22.04, trying
  to use +/- to control window placement doesn't work.  E.g. the
  following should give me a gnome-terminal window in the lower-right
  corner of the screen:

gnome-terminal --geometry -0-0

  It does not; instead it stacks it with a window position just slightly
  down from and to the left of the previous window.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xwayland 2:22.1.1-1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  8 18:14:34 2022
  InstallationDate: Installed on 2019-12-23 (867 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: xwayland
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1972133/+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 2002393] [NEW] Speaker Mute and Microphone Mute LED indicators not working on HP Pro x360 435 G9

You have been subscribed to a public bug:

The HP Pro x360 435 G9 has LED indicators built into the F5 key and F8
key to indicate that the Speakers (F5) and Microphone (F8) are muted.
Pressing F5 correctly toggles the output of sound off and on, but the
indicator LED never illuminates. Pressing F8 correctly toggles the
Microphone input on and off, but again the indicator LED never
illuminates.

The expected operation would be that each of the LEDs would be
illuminated when their respective mutes are in effect.


lsb_release -rd:
Description:Ubuntu 22.10
Release:22.10

cat /proc/version_signature:
Ubuntu 5.19.0-26.27-generic 5.19.7

apt-cache policy linux-modules-extra-5.19.0-26-generic 
linux-modules-extra-5.19.0-26-generic:
  Installiert:   5.19.0-26.27
  Installationskandidat: 5.19.0-26.27

grep -i codec /proc/asound/card*/codec*:
/proc/asound/card0/codec#0:Codec: ATI R6xx HDMI
/proc/asound/card1/codec#0:Codec: Realtek ALC236

I've tested the following module options in /etc/modprobe.d/alsa-base.conf 
without success:
options snd-hda-intel model=hp-gpio-led
options snd-hda-intel model=hp-mute-led-mic1
options snd-hda-intel model=hp-mute-led-mic2
options snd-hda-intel model=hp-gpio-led-mic3
options snd-hda-intel model=hp-gpio-mic1
options snd-hda-intel model=hp-line1-mic1
options snd-hda-intel model=hp-gpio4
options snd-hda-intel model=hp-gpio2-hotkey
options snd-hda-intel model=hp-dock-pins
options snd-hda-intel model=hp-dock-gpio-mic

The issue probably needs a quirk to get wiring of the LEDs correct. The
code needed to accomplish for that lies in
/sound/pci/hda/patch_realtek.c

I've tested the following quirks (including modules rebuild) without success:
- SND_PCI_QUIRK(0x103c, 0x89ed, "HP Pro x360 435 13.3 inch G9 Notebook PC",\ 
ALC236_FIXUP_HP_MUTE_LED_MICMUTE_VREF),
- SND_PCI_QUIRK(0x103c, 0x89ed, "HP Pro x360 435 13.3 inch G9 Notebook PC",\ 
ALC236_FIXUP_HP_GPIO_LED),
 
There is a similar bug report, #1948006, for this issue. However, it's 
adressing the same effect on a different model.

I would very much appreciate if somebody could further track down this
issue.

THX,
Carsten

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
Uname: Linux 5.19.0-26-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  carsten1692 F wireplumber
 /dev/snd/controlC1:  carsten1692 F wireplumber
 /dev/snd/seq:carsten1689 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 10 10:24:42 2023
InstallationDate: Installed on 2022-12-25 (15 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/18/2022
dmi.bios.release: 9.0
dmi.bios.vendor: HP
dmi.bios.version: U80 Ver. 01.09.00
dmi.board.name: 89ED
dmi.board.vendor: HP
dmi.board.version: KBC Version 17.47.00
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 23.71
dmi.modalias: 
dmi:bvnHP:bvrU80Ver.01.09.00:bd10/18/2022:br9.0:efr23.71:svnHP:pnHPProx36043513.3inchG9NotebookPC:pvr:rvnHP:rn89ED:rvrKBCVersion17.47.00:cvnHP:ct31:cvr:sku6F262EA#ABD:
dmi.product.family: 103C_5336AN HP Pro x360
dmi.product.name: HP Pro x360 435 13.3 inch G9 Notebook PC
dmi.product.sku: 6F262EA#ABD
dmi.sys.vendor: HP
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-01-05T10:08:37.052394

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


** Tags: amd64 apport-bug kinetic wayland-session
-- 
Speaker Mute and Microphone Mute LED indicators not working on HP Pro x360 435 
G9
https://bugs.launchpad.net/bugs/2002393
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to alsa-driver in Ubuntu.

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

[Desktop-packages] [Bug 2002393] Re: Speaker Mute and Microphone Mute LED indicators not working on HP Pro x360 435 G9

2023-01-10 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  Speaker Mute and Microphone Mute LED indicators not working on HP Pro
  x360 435 G9

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The HP Pro x360 435 G9 has LED indicators built into the F5 key and F8
  key to indicate that the Speakers (F5) and Microphone (F8) are muted.
  Pressing F5 correctly toggles the output of sound off and on, but the
  indicator LED never illuminates. Pressing F8 correctly toggles the
  Microphone input on and off, but again the indicator LED never
  illuminates.

  The expected operation would be that each of the LEDs would be
  illuminated when their respective mutes are in effect.

  
  lsb_release -rd:
  Description:  Ubuntu 22.10
  Release:  22.10

  cat /proc/version_signature:
  Ubuntu 5.19.0-26.27-generic 5.19.7

  apt-cache policy linux-modules-extra-5.19.0-26-generic 
  linux-modules-extra-5.19.0-26-generic:
Installiert:   5.19.0-26.27
Installationskandidat: 5.19.0-26.27

  grep -i codec /proc/asound/card*/codec*:
  /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI
  /proc/asound/card1/codec#0:Codec: Realtek ALC236

  I've tested the following module options in /etc/modprobe.d/alsa-base.conf 
without success:
  options snd-hda-intel model=hp-gpio-led
  options snd-hda-intel model=hp-mute-led-mic1
  options snd-hda-intel model=hp-mute-led-mic2
  options snd-hda-intel model=hp-gpio-led-mic3
  options snd-hda-intel model=hp-gpio-mic1
  options snd-hda-intel model=hp-line1-mic1
  options snd-hda-intel model=hp-gpio4
  options snd-hda-intel model=hp-gpio2-hotkey
  options snd-hda-intel model=hp-dock-pins
  options snd-hda-intel model=hp-dock-gpio-mic

  The issue probably needs a quirk to get wiring of the LEDs correct.
  The code needed to accomplish for that lies in
  /sound/pci/hda/patch_realtek.c

  I've tested the following quirks (including modules rebuild) without success:
  - SND_PCI_QUIRK(0x103c, 0x89ed, "HP Pro x360 435 13.3 inch G9 Notebook PC",\ 
ALC236_FIXUP_HP_MUTE_LED_MICMUTE_VREF),
  - SND_PCI_QUIRK(0x103c, 0x89ed, "HP Pro x360 435 13.3 inch G9 Notebook PC",\ 
ALC236_FIXUP_HP_GPIO_LED),
   
  There is a similar bug report, #1948006, for this issue. However, it's 
adressing the same effect on a different model.

  I would very much appreciate if somebody could further track down this
  issue.

  THX,
  Carsten

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carsten1692 F wireplumber
   /dev/snd/controlC1:  carsten1692 F wireplumber
   /dev/snd/seq:carsten1689 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 10 10:24:42 2023
  InstallationDate: Installed on 2022-12-25 (15 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2022
  dmi.bios.release: 9.0
  dmi.bios.vendor: HP
  dmi.bios.version: U80 Ver. 01.09.00
  dmi.board.name: 89ED
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 17.47.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 23.71
  dmi.modalias: 
dmi:bvnHP:bvrU80Ver.01.09.00:bd10/18/2022:br9.0:efr23.71:svnHP:pnHPProx36043513.3inchG9NotebookPC:pvr:rvnHP:rn89ED:rvrKBCVersion17.47.00:cvnHP:ct31:cvr:sku6F262EA#ABD:
  dmi.product.family: 103C_5336AN HP Pro x360
  dmi.product.name: HP Pro x360 435 13.3 inch G9 Notebook PC
  dmi.product.sku: 6F262EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-01-05T10:08:37.052394

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2002393/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections

2023-01-10 Thread Alfonso Sanchez-Beato

To reproduce the problem, this should be enough:

1. Create a connection to an OpenVPN server
2. Start the connection. The OpenVPN plugin will create a tunnel interface.
3. "nmcli c" should show a tunX connection and the VPN connection. "nmcli d"
should show tunX as a external connection.
4. Disconnect the VPN connection (nmcli c down )
5. A file in /etc/netplan/ for the tunX which should not be there is created

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

Title:
netplan network-manager plugin tries to save temporary connections

Status in netplan:
Triaged
Status in network-manager package in Ubuntu:
Confirmed

Bug description:
When creating an OpenVPN connection, a temporal connection called tunN
is created. For instance, after activating a connection called
vpntest, I have:

NAME UUID TYPE DEVICE
vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3
tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0

tun0 is created/removed after activating/deactivating vpntest and
should not really be saved, but I see netplan adding it in
/etc/netplan. And while doing so the plugin also reports some errors
(I see these when stopping the connection):

Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG:
the profile cannot be stored in keyfile format without becoming unusable:
cannot access file: No such file or directory
Nov 28 16:16:57 ubuntu NetworkManager[11752]:
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920]
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null))
to
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
keyfile writer produces an invalid connection: cannot access file: No such
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+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 1983794] Re: Evolution not deleting autosave files

2023-01-10 Thread Treviño

** Also affects: evolution (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: libcanberra (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** No longer affects: evolution (Ubuntu Jammy)

** Changed in: libcanberra (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libcanberra (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: libcanberra (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: libcanberra (Ubuntu Jammy)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  In Progress
Status in libcanberra source package in Jammy:
  Triaged

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 1998207] Re: netplan network-manager plugin tries to save temporary connections

Thanks! I've added the "!is_external" check to my latest development
patch revision at:
https://github.com/slyon/NetworkManager/commits/netplan-nm-1.40

So this bug report is now mostly about comment #10, where the openvpn
client/plugin is creating a temporary tunX device, which is displayed as
"external" in "nmcli d", but still a Netplan YAML file is created in
/etc/netplan on "nmcli con down ". I can easily reproduce this
issue locally, using Canonical VPN and see tunX connection definitions
piling up in /etc/netplan/ when bringing it up&down a few times in a
row.

This doesn't seem to affect the functionality, though. The VPN is
connection is working when up in each iteration.

** Description changed:

+ *** Note: This bug is mostly about comment #10, now ***
+ 
  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called vpntest,
  I have:
  
- NAME  UUID  TYPE  DEVICE 
- vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3   
- tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0   
+ NAME  UUID  TYPE  DEVICE
+ vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3
+ tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0
  
  tun0 is created/removed after activating/deactivating vpntest and should
  not really be saved, but I see netplan adding it in /etc/netplan. And
  while doing so the plugin also reports some errors (I see these when
  stopping the connection):
  
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

** Changed in: netplan
   Importance: High => Medium

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

Title:
  netplan network-manager plugin tries to save temporary connections

Status in netplan:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  *** Note: This bug is mostly about comment #10, now ***

  When creating an OpenVPN connection, a temporal connection called tunN
  is created. For instance, after activating a connection called
  vpntest, I have:

  NAME  UUID  TYPE  DEVICE
  vpntest   458856e6-8f0f-4dc6-82f2-dd72868252a0  vpn   ens3
  tun0  1eb1dbe8-5678-4818-9adf-fb2dc01ed132  tun   tun0

  tun0 is created/removed after activating/deactivating vpntest and
  should not really be saved, but I see netplan adding it in
  /etc/netplan. And while doing so the plugin also reports some errors
  (I see these when stopping the connection):

  Nov 28 16:16:57 ubuntu NetworkManager[11752]:  [1669652217.2920] BUG: 
the profile cannot be stored in keyfile format without becoming unusable: 
cannot access file: No such file or directory
  Nov 28 16:16:57 ubuntu NetworkManager[11752]: 
((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed
  Nov 28 16:16:57 ubuntu NetworkManager[11752]:   [1669652217.2920] 
keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) 
to 
"/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection":
 keyfile writer produces an invalid connection: cannot access file: No such 
file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1998207/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init

2023-01-10 Thread Treviño

> Why are you setting d->object to NULL in on_object_disposed? By doing
that you are introducing memory leak, no?

Well the point was that I didn't want this to happen when last reference
was removed, but this can't really happen in a sane setup unless
something played some dirty game with the object.

So that's fine, I've handled it as part of fix for #1983794

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

Title:
  gnome-shell crashed with SIGTRAP from error "Can't create a
  GtkStyleContext without a display connection" in
  gtk_style_context_init

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in libcanberra package in Ubuntu:
  Fix Released

Bug description:
  GNOME Shell isn't meant to use GTK at all, but it's repeatedly
  crashing in GTK since the introduction of GNOME 40.

  https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
  https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844
  https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad
  https://errors.ubuntu.com/problem/d69ccaf1379f588b04ecac2a6cc93b9be31100b4

  This seems to be a result of Xwayland crashing and gnome-shell then
  trying to recover (and failing). Although gnome-shell shouldn't be
  using GTK, and Wayland sessions shouldn't be dependent on having an
  X11 server (Xwayland) available. Fixing either of those should resolve
  this.

  WORKAROUND:

  sudo apt remove libcanberra-gtk3-module

  TEST CASE:

  1. Log into a Wayland session.
  2. Open a Terminal.
  3. $ xrandr   # Just to ensure Xwayland starts
  4. $ killall Xwayland

  Expected: gnome-shell still responds.
  Observed: gnome-shell freezes or exits.

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 29 15:11:43 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-10-27 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions


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

[Desktop-packages] [Bug 1999336] Re: New bugfix release 22.2.5

it's changelog doesn't refer to this bug, so there's little point

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

Title:
  New bugfix release 22.2.5

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  Update Mesa to the latest bugfix release of the 22.2.x series for
  kinetic, and backport it to jammy for 22.04.2 image.

  diffstat:
  177 files changed, 2100 insertions(+), 617 deletions(-)
  191 commits

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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

[Desktop-packages] [Bug 2000649] Re: Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from DeliverGrabbedEvent() from ProcessDeviceEvent() from XkbHandleActions()

2023-01-10 Thread andrey

Hi! For now I did the following "trick": I added needed repositories
from the "kinetic" into /etc/source.list and using aptitude installed
all needed dependencies. I've been using it for some time now -- no
crashes so far.

I sincerely hope that Ubuntu 22.04.2 will contain this bug fix, because
this bug being in LTS release is not good at all!

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

Title:
  Xorg crashed with SIGSEGV in FreezeThisEventIfNeededForSyncGrab() from
  DeliverGrabbedEvent() from ProcessDeviceEvent() from
  XkbHandleActions()

Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Occasionally, (I wasn't able to reproduce it) xorg just hangs or
  crashes to the log screen. It happens about every two weeks,
  especially if I don't reboot often (However doesn't matter much, I
  think, because it also happens on "fresh" boot).

  I use bspwm (version from the jammy repository), on Lubuntu 22.04.1
  (fresh install, not upgrade from 22.04, nor 20.04).

  Freezes occur when I switch between desktops, just hangs and that's
  it, no response to the keyboard, however mouse is usually usable and
  screen keeps updating.

  Crashes occur when I switch between windows or desktops (I use
  shortcuts for this), xorg just goes black and prints my shortcut to
  the screen; waits for a few secs and opens login screen.

  I don't know why it is happening, before 22.04 I was using 16.04 never
  had any problems.

  I tried google it, use some intel video card in /etc/X11/xorg.conf.d
  directory, but it makes system unusable at all, just type is super
  slow and I gave up experimenting with different flags ...

  I really hope you can tell me something, because this bug is really
  annoying, especially when I have a lot of windows open and I have to
  open them all again and again. Thank you in advance and have a nice
  day!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Wed Dec 28 23:59:36 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:5062]
  InstallationDate: Installed on 2022-12-24 (3 days ago)
  InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HMS6XX00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2022
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET69W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HMS6XX00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HMS6XX00
  dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2000649/+subscriptions


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

[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE

2023-01-10 Thread Egmont Koblinger

(I am the one who designed [1] and implemented RTL (right-to-left) and
BiDi (bidirectional) text support in VTE.)

The two issues you report here are totally independent.


Re bug 1:

Terminal emulators, by their very nature and their legacy of maybe ~50
years, _have to_ operate in a strict rectangular grid of character
cells. If you try to break out of this grid, you break pretty much
everything.

Sticking to such a grid has quite a few advantages and quite a few
disadvantates. The visual disadvantages are more prominent with scripts
that do connect the letters to each other, such as Arabic.

I'm sure that there's room for improvement in rendering, but it probably
doesn't belong to VTE. Or maybe belongs to the VTE to the extent of
switching to a different font rendering engine (e.g. from freetype to
harfbuzz; there's an upstream bug about it).

However, by the very nature of the grid layout, no rendering engine
could perform magic and end up with a beautiful rendering if it starts
with a font that doesn't have the letters of the desired width.

Long story short: You'll need to find a high quality monospace Arabic
font. Or, in fact, one where the English and the Arabic letters all have
the same width (or somehow merge two such fonts, an English and an
Arabic one, via fontconfig; I'm not at all familiar with how to do
that).

For testing, I happened to use a font where the Arabic text didn't look
anywhere as bad as your screenshot. I probably used "Monospace 9", but I
don't know if this font itself contains Arabic, or if they were
substituted from another font, and if so then which one. Comparing the
layout to the layout of let's say web browsers (which don't have the
fixed with constraint), bearing in mind that I cannot read Arabic, I am
confident to say that the rendering was way better than the one in your
screenshot. At the very least, letters were connected or not connected
exactly as in the browser, and the overall look was also reasonably
close.

So keep finding the right font for you.


Re bug 2:

This one is not about joining or not joining adjacent letters; this one
is about figuring out how to shuffle the order of the character cells to
make sure that words and sentences aren't "sdrawkcab" (backwards).

Pretty much every terminal behaves differently when it comes to RTL or
BiDi text. That is, unfortunately it is literally impossible for an app
to emit RTL or BiDi text and expect to appear correctly in the terminal.
Also, some applications have different requirement from the terminal
than others.

Overly simplified story: Some apps need to emit logical order and expect
the terminal emulator to rearrange the cells. If the terminal doesn't
rearrange, the output will be "nekorb" (broken). Some other apps need to
reorder the cells themselves, and if the terminal also reorders them
then the output will be, again, "nekorb". No matter which approach a
terminal emulator picks (i.e. to rearrange or not to rearrange according
to the BiDi algorithm), one set of the applications has no chance of
implementing RTL. Or, rather, no application could ever implement proper
RTL, because they could not tell which kind of terminal they operate on.
(Fun: I've also come across an app where half of the strings were in
logical order and half were in visual, making it absolutely certain that
no terminal would ever display correctly the entire app.)

The only proper attempt to fix RTL for terminals dated back to ~30 years
earlier, preceding the Unicode BiDi Algorithm, and contained many flaws
(let alone that it's a document with no known implementation). All the
other attempts were much more fundamentally broken (like forcing the
terminal to rearrange the cells, making it literally impossible to
implement e.g. BiDi-aware terminal-based text editors). I elaborate on
this in my BiDi proposal.

I gathered information, studied the subject thoroughly, evaluated
earlier "solutions", and then come up with a proposal that would address
all the issues. This is a ~50 page document, referring to the also quite
enormous Unicode BiDi Algorithm as one of its building blocks. Then I
implemented it in VTE.

It's important to understand that no RTL behavior for terminals could
ever magically fix the output of all the existing utilities (such as
"apt" as seen in your screenshot), it would just be literally impossible
to do that.

My RTL/BiDi proposal makes confirming terminals a _platform_ capable of
properly handling the RTL/BiDi needs of every kind of application. But
as a next step, applications on top of them have to use the provided
features wisely.

So VTE is the first, and perhaps still only (I'm not sure about that)
terminal whose RTL / BiDi capabilities make it possible for all of
"apt", "vim", "tmux" etc. (insert thousands of other apps here) to
implement RTL / BiDi, despite their vastly different needs.

Now it's the applications' turn to use the available RTL / BiDi features
as they require.

(By the way, if you copy the given "a

[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE

2023-01-10 Thread Egmont Koblinger

To be absolutely fair, I have to add this:

One thing, namely the handling of BiDi _control_ characters at the very
beginning of a paragraph (logical line), remains as a TODO item both in
the spec and in VTE's implementation (both of which are really
nontrivial).

I just ran out of motivation and time, so it's probably waiting for
someone else to fix it.

In the unlikely case that "apt"'s given message begins with such a
character, and VTE chopping it off is the reason for the wrong order,
then it's my fault :)

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

Title:
  Poor Arabic rendering in VTE

Status in gnome-terminal package in Ubuntu:
  New
Status in vte package in Ubuntu:
  New

Bug description:
  VTE has a number of issues when it comes to rendering Arabic letters
  in the terminal, which could affect a number of languages (Arabic,
  Urdu, Persian... etc).

  Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed
  with spaces between its letters, making readability hard and sometimes
  not possible. Sometimes the letters are crushed together very closely
  making reading impossible too.

  Bug 2: If a non-Arabic text and an Arabic text are displayed together
  in the same line, then the entire line will be missed up and you won't
  be able to understand what is being said.

  Both of these bugs can be seen from the image I attached.

  I reported both of these bugs together because it's unlikely they can
  be fixed separately, probably they are related to each other.

  Problem can be seen in any VTE-based terminal. Here I am using GNOME
  Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu
  version and in any terminal version as well (it has been there since
  forever).

  I reported the bug here instead of upstream because that's what they
  said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs,
  but this bug is not related to Ubuntu only; it happens on all Linux
  distributions.

  Happy to provide any information you need, or any do tests or
  experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions


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

[Desktop-packages] [Bug 2002415] [NEW] package chromium-browser 108.0.5359.71-0ubuntu0.18.04.5 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error

2023-01-10 Thread mashaal sajid

Public bug reported:

I was updating from 18.04 to 20.04 and I was given the option to do a
partial upgrade and then everything did'nt go well it seems. there's an
issue with chromium and some other packages

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser 108.0.5359.71-0ubuntu0.18.04.5
ProcVersionSignature: Ubuntu 5.4.0-136.153~18.04.1-generic 5.4.218
Uname: Linux 5.4.0-136-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
DRM.card0-DP-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-HDMI-A-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wAJ5XQGAAEaAQSVIhN4CiQQl1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBZBtWd1AAEzAwIDYAWMIQAAAaohdWuVAALTAwIDYAWMIQAAAa/gBGVkdQUIBOVDE1TjQyQQGUABkBCiAgAFQ=
 modes: 1366x768 1366x768
Date: Tue Jan 10 09:11:35 2023
Desktop-Session:
 'None'
 'None'
 'None'
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-osp1-20171027-1
Env:
 'None'
 'None'
ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-10-31 (1531 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
InstalledPlugins:
 
Load-Avg-1min: 1.92
Load-Processes-Running-Percent:   0.1%
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 15-3573
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-136-generic 
root=UUID=8c431716-fe56-47f3-b49f-b7bb6d054608 ro alx.enable_wol=1 
mem_sleep_default=deep quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
SourcePackage: chromium-browser
Title: package chromium-browser 108.0.5359.71-0ubuntu0.18.04.5 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0XT9M4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0XT9M4:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 15-3573
dmi.product.sku: 083E
dmi.product.version: 1.4.0
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.chromium-browser: [deleted]

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


** Tags: amd64 apport-package focal

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

Title:
  package chromium-browser 108.0.5359.71-0ubuntu0.18.04.5 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was updating from 18.04 to 20.04 and I was given the option to do a
  partial upgrade and then everything did'nt go well it seems. there's
  an issue with chromium and some other packages

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 108.0.5359.71-0ubuntu0.18.04.5
  ProcVersionSignature: Ubuntu 5.4.0-136.153~18.04.1-generic 5.4.218
  Uname: Linux 5.4.0-136-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ5XQGAAEaAQSVIhN4CiQQl1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBZBtWd1AAEzAwIDYAWMIQAAAaohdWuVAALTAwIDYAWMIQAAAa/gBGVkdQUIBOVDE1TjQyQQGUABkBCiAgAFQ=
   modes: 1366x768 1366x768
  Date: Tue Jan 10 09:11:35 2023
  Desktop-Session:
   'None'

[Desktop-packages] [Bug 2002414] [NEW] Gnome does not open (appear)

2023-01-10 Thread Yosha872

Public bug reported:

Since latest update, on 2023-01-09 my laptop can not reach Gnome, stuck
on the text boot screen after GRUB. Kernel: 5.19.0-28 (previous
installed was 5.19.0-26). No useful error message displayed.

When doing ALT+CTRL+F2 I can log as user and see (top) that the computer is not 
hang.
When doing CTRL+ALT+TAB, the graphical Ubuntu shutown screen does appear, then 
the computer does reboot.

When booting with 5.19.0-26 I can the same issue, but with more debug
lines on the text boot screen. No useful error message displayed.

OS: ubuntu 22.10.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: plymouth 22.02.122-1ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
Uname: Linux 5.19.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jan 10 16:03:39 2023
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2022-05-03 (251 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam
 Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros 
QCA9377 Bluetooth
 Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575G
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro quiet splash vt.handoff=7
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2017
dmi.bios.release: 0.0
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.32
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 2.30
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32:
dmi.product.family: KBL
dmi.product.name: Aspire E5-575G
dmi.product.sku: Aspire E5-575G_115F_1.32
dmi.product.version: V1.32
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug kinetic

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

Title:
  Gnome does not open (appear)

Status in plymouth package in Ubuntu:
  New

Bug description:
  Since latest update, on 2023-01-09 my laptop can not reach Gnome,
  stuck on the text boot screen after GRUB. Kernel: 5.19.0-28 (previous
  installed was 5.19.0-26). No useful error message displayed.

  When doing ALT+CTRL+F2 I can log as user and see (top) that the computer is 
not hang.
  When doing CTRL+ALT+TAB, the graphical Ubuntu shutown screen does appear, 
then the computer does reboot.

  When booting with 5.19.0-26 I can the same issue, but with more debug
  lines on the text boot screen. No useful error message displayed.

  OS: ubuntu 22.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: plymouth 22.02.122-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  Uname: Linux 5.19.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 10 16:03:39 2023
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2022-05-03 (251 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros 
QCA9377 Bluetooth
   Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575G
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
ro

[Desktop-packages] [Bug 2002415] Re: package chromium-browser 108.0.5359.71-0ubuntu0.18.04.5 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e

2023-01-10 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package chromium-browser 108.0.5359.71-0ubuntu0.18.04.5 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I was updating from 18.04 to 20.04 and I was given the option to do a
  partial upgrade and then everything did'nt go well it seems. there's
  an issue with chromium and some other packages

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 108.0.5359.71-0ubuntu0.18.04.5
  ProcVersionSignature: Ubuntu 5.4.0-136.153~18.04.1-generic 5.4.218
  Uname: Linux 5.4.0-136-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ5XQGAAEaAQSVIhN4CiQQl1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBZBtWd1AAEzAwIDYAWMIQAAAaohdWuVAALTAwIDYAWMIQAAAa/gBGVkdQUIBOVDE1TjQyQQGUABkBCiAgAFQ=
   modes: 1366x768 1366x768
  Date: Tue Jan 10 09:11:35 2023
  Desktop-Session:
   'None'
   'None'
   'None'
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  Env:
   'None'
   'None'
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-10-31 (1531 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  InstalledPlugins:
   
  Load-Avg-1min: 1.92
  Load-Processes-Running-Percent:   0.1%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15-3573
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-136-generic 
root=UUID=8c431716-fe56-47f3-b49f-b7bb6d054608 ro alx.enable_wol=1 
mem_sleep_default=deep quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: chromium-browser
  Title: package chromium-browser 108.0.5359.71-0ubuntu0.18.04.5 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0XT9M4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0XT9M4:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3573
  dmi.product.sku: 083E
  dmi.product.version: 1.4.0
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2002415/+subscriptions


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

[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE

** Attachment added: "gnome terminal with Monospace 9 font.png"

https://bugs.launchpad.net/ubuntu/+source/vte/+bug/2002290/+attachment/5640499/+files/gnome%20terminal%20with%20Monospace%209%20font.png

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

Title:
Poor Arabic rendering in VTE

Status in gnome-terminal package in Ubuntu:
New
Status in vte package in Ubuntu:
New

Bug description:
VTE has a number of issues when it comes to rendering Arabic letters
in the terminal, which could affect a number of languages (Arabic,
Urdu, Persian... etc).

Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed
with spaces between its letters, making readability hard and sometimes
not possible. Sometimes the letters are crushed together very closely
making reading impossible too.

Bug 2: If a non-Arabic text and an Arabic text are displayed together
in the same line, then the entire line will be missed up and you won't
be able to understand what is being said.

Both of these bugs can be seen from the image I attached.

I reported both of these bugs together because it's unlikely they can
be fixed separately, probably they are related to each other.

Problem can be seen in any VTE-based terminal. Here I am using GNOME
Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu
version and in any terminal version as well (it has been there since
forever).

I reported the bug here instead of upstream because that's what they
said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs,
but this bug is not related to Ubuntu only; it happens on all Linux
distributions.

Happy to provide any information you need, or any do tests or
experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions

[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE

** Attachment added: "gnome terminal with Monospace 12.png"

https://bugs.launchpad.net/ubuntu/+source/vte/+bug/2002290/+attachment/5640500/+files/gnome%20terminal%20with%20Monospace%2012.png

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

Title:
Poor Arabic rendering in VTE

Status in gnome-terminal package in Ubuntu:
New
Status in vte package in Ubuntu:
New

Bug description:
VTE has a number of issues when it comes to rendering Arabic letters
in the terminal, which could affect a number of languages (Arabic,
Urdu, Persian... etc).

Bug 2: If a non-Arabic text and an Arabic text are displayed together
in the same line, then the entire line will be missed up and you won't
be able to understand what is being said.

Both of these bugs can be seen from the image I attached.

I reported both of these bugs together because it's unlikely they can
be fixed separately, probably they are related to each other.

Happy to provide any information you need, or any do tests or
experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions

[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE

** Attachment added: "apt output in gnome terminal.png"

https://bugs.launchpad.net/ubuntu/+source/vte/+bug/2002290/+attachment/5640501/+files/apt%20output%20in%20gnome%20terminal.png

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

Title:
Poor Arabic rendering in VTE

Status in gnome-terminal package in Ubuntu:
New
Status in vte package in Ubuntu:
New

Bug description:
VTE has a number of issues when it comes to rendering Arabic letters
in the terminal, which could affect a number of languages (Arabic,
Urdu, Persian... etc).

Bug 2: If a non-Arabic text and an Arabic text are displayed together
in the same line, then the entire line will be missed up and you won't
be able to understand what is being said.

Both of these bugs can be seen from the image I attached.

I reported both of these bugs together because it's unlikely they can
be fixed separately, probably they are related to each other.

Happy to provide any information you need, or any do tests or
experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions

[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE

** Attachment added: "apt output in the browser with RTL.png"

https://bugs.launchpad.net/ubuntu/+source/vte/+bug/2002290/+attachment/5640502/+files/apt%20output%20in%20the%20browser%20with%20RTL.png

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

Title:
Poor Arabic rendering in VTE

Status in gnome-terminal package in Ubuntu:
New
Status in vte package in Ubuntu:
New

Bug description:
VTE has a number of issues when it comes to rendering Arabic letters
in the terminal, which could affect a number of languages (Arabic,
Urdu, Persian... etc).

Bug 2: If a non-Arabic text and an Arabic text are displayed together
in the same line, then the entire line will be missed up and you won't
be able to understand what is being said.

Both of these bugs can be seen from the image I attached.

I reported both of these bugs together because it's unlikely they can
be fixed separately, probably they are related to each other.

Happy to provide any information you need, or any do tests or
experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions

[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE

Hello Egmont.

Thank you for the detailed reply and for fixing my understanding about
these issues. I also highly appreciate your work and help!

I was using the default font in Ubuntu, but when I changed it to
Monospace 9 (or even 12) as you suggested, the spaces issues disappeared
and the text is now indeed very much more readable. I attached
screenshots for Monospace 9 and 12.

I am not sure however, which Monospace font is that? I mean, to which
family? In the terminal settings it just says "Monospace".

So perhaps the first thing we can drive from this to fix bug 1: Use a
different terminal font by default in Ubuntu for GNOME Terminal instead
of the one currently being used (which currently seems to me to be
Ubuntu Mono 12)? Maybe this could be done at least when the system
language is Arabic?

I will test additional possible fonts and see how they would look like.

For bug 2, I did a small test for "apt" output in the terminal and also
in the web browser (attached images) and in Gedit. You can see that both
the RTL webpage and Gedit can display the same output text very much
better than the terminal, the order of the text is changed, and displays
very nicely. Perhaps the only issue is from apt's translation side (they
seem to have left 1 letter untranslated which is the M letter in "MB",
which is giving the uncomfortable look), but aside from that, Gedit and
the web browser can display the same text without issues, unlike in the
GNOME Terminal which changes the order of the text.

So to sum up, if my understanding is correct, are you saying that VTE
actually supports displaying RTL/BiDi correctly, and this is just an
issue in "applications" like apt, tmux, vim... etc, and they need to fix
this issue from their side? I mean, it is an issue in the apps
themselves, and not terminal emulators (like GNOME Terminal), correct?

Thank you so much for your help, and for your work over the years. I am
trying to make a small volunteering team to report all Arabic/RTL
related bugs in Linux and open source software (we have sadly so many,
like tens of them!), and we are gradually starting to report and
investigate any bug.

I would happily test any scenario or experiment to fix any Arabic or
RTL-related bug.

P.S: It sounds like Launchpad does not allow multiple image uploads (or
I didn't find it), so I had to upload images one by one, sorry for that!

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

Title:
  Poor Arabic rendering in VTE

Status in gnome-terminal package in Ubuntu:
  New
Status in vte package in Ubuntu:
  New

Bug description:
  VTE has a number of issues when it comes to rendering Arabic letters
  in the terminal, which could affect a number of languages (Arabic,
  Urdu, Persian... etc).

  Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed
  with spaces between its letters, making readability hard and sometimes
  not possible. Sometimes the letters are crushed together very closely
  making reading impossible too.

  Bug 2: If a non-Arabic text and an Arabic text are displayed together
  in the same line, then the entire line will be missed up and you won't
  be able to understand what is being said.

  Both of these bugs can be seen from the image I attached.

  I reported both of these bugs together because it's unlikely they can
  be fixed separately, probably they are related to each other.

  Problem can be seen in any VTE-based terminal. Here I am using GNOME
  Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu
  version and in any terminal version as well (it has been there since
  forever).

  I reported the bug here instead of upstream because that's what they
  said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs,
  but this bug is not related to Ubuntu only; it happens on all Linux
  distributions.

  Happy to provide any information you need, or any do tests or
  experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions


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

[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE

** Attachment added: "apt output in gedit.png"

https://bugs.launchpad.net/ubuntu/+source/vte/+bug/2002290/+attachment/5640503/+files/apt%20output%20in%20gedit.png

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

Title:
Poor Arabic rendering in VTE

Status in gnome-terminal package in Ubuntu:
New
Status in vte package in Ubuntu:
New

Bug description:
VTE has a number of issues when it comes to rendering Arabic letters
in the terminal, which could affect a number of languages (Arabic,
Urdu, Persian... etc).

Bug 2: If a non-Arabic text and an Arabic text are displayed together
in the same line, then the entire line will be missed up and you won't
be able to understand what is being said.

Both of these bugs can be seen from the image I attached.

I reported both of these bugs together because it's unlikely they can
be fixed separately, probably they are related to each other.

Happy to provide any information you need, or any do tests or
experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions

[Desktop-packages] [Bug 2002290] Re: Poor Arabic rendering in VTE

Also I found the default Monospace used in Ubuntu. It is DejaVu Sans
Mono:

mhsabbagh@ubuntu2204:/$ fc-match monospace
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"

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

Title:
  Poor Arabic rendering in VTE

Status in gnome-terminal package in Ubuntu:
  New
Status in vte package in Ubuntu:
  New

Bug description:
  VTE has a number of issues when it comes to rendering Arabic letters
  in the terminal, which could affect a number of languages (Arabic,
  Urdu, Persian... etc).

  Bug 1: Any Arabic word in any VTE-based terminal is choppily displayed
  with spaces between its letters, making readability hard and sometimes
  not possible. Sometimes the letters are crushed together very closely
  making reading impossible too.

  Bug 2: If a non-Arabic text and an Arabic text are displayed together
  in the same line, then the entire line will be missed up and you won't
  be able to understand what is being said.

  Both of these bugs can be seen from the image I attached.

  I reported both of these bugs together because it's unlikely they can
  be fixed separately, probably they are related to each other.

  Problem can be seen in any VTE-based terminal. Here I am using GNOME
  Terminal 3.44.0 on Ubuntu 22.04, but it can be seen in any Ubuntu
  version and in any terminal version as well (it has been there since
  forever).

  I reported the bug here instead of upstream because that's what they
  said at the page: https://wiki.gnome.org/Apps/Terminal/ReportingBugs,
  but this bug is not related to Ubuntu only; it happens on all Linux
  distributions.

  Happy to provide any information you need, or any do tests or
  experiments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2002290/+subscriptions


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

[Desktop-packages] [Bug 1580123] Re: xrandr --scale (again) confines mouse to native solution

2023-01-10 Thread Danky

The bug is here again. I'm using Ubuntu jammy 22.04 with xserver-xorg
1:7.7+23ubuntu2 and xserver-xorg-core 2:21.1.3-2ubuntu2.5. I think it's
xorg 21.1, it seems there was a version change in xorg.

I have three monitors, two 4k and one old 1280x1024. Some time ago I
used it with scale 2x2 and it was useful for chats, follow logs, etc.

But now the mouse gets confined in a quarter of the screen :(

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

Title:
  xrandr --scale (again) confines mouse to native solution

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This might be a regression where the original issue is:
  https://bugs.launchpad.net/xorg-server/+bug/883319

  It can be easily reproduced by doing something like:

  xrandr --output DP1 --scale 1.25x1.25

  The mouse will be still constrained to the native solution (aka you
  can't move the mouse outside a box of whatever DP1 had as resolution
  before.

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ xrandr --version
  xrandr program version   1.5.0
  Server reports RandR version 1.5

  $ apt-cache policy xserver-xorg-core
  xserver-xorg-core:
Installed: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1580123/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)

2023-01-10 Thread Yosha872

Same issue on Xubuntu 22.04.1 French, the 'file not found' URL is:

file:///usr/share/libreoffice/help/index.html?Target=scalc/.uno%3AHelpIndex&Language=fr&System=UNIX&Version=7.3

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

Title:
  libreoffice help doesn't open in firefox (404 error on
  file:///tmp/lu417531j7po.tmp/NewHelp0.html)

Status in libreoffice package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Committed
Status in libreoffice source package in Jammy:
  Fix Released
Status in snapd source package in Jammy:
  Confirmed

Bug description:
  Ubuntu jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Opened LibreOffice Writer as random apps in QA-test.
  Hit F1 to call help, and all I get is an error

  URL:  file:///tmp/lu417531j7po.tmp/NewHelp0.html

  ---
  File not found

  Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  Firefox opens as a snap; but it isn't accessing the data from
  LibreOffice.

  Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks-
  libreoffice-deb/27537

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 04:46:33 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 2001922] Re: Xorg crash

2023-01-10 Thread pd

This time it crashed almost instantly after logging in. There is a new
id in /var/crash/_usr_lib_xorg_Xorg.0.uploaded

be43a9e0-9103-11ed-9d0c-fa163e993415

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+attachment/5640509/+files/prevboot.txt

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu 22.04.1 LTS installation crashes, but I was not able to
  figure out how to reproducibly trigger the crash. The last time it
  happened was with firefox and zoom running, the display suddenly went
  black and after a few seconds the X login screen appeared, my session
  gone.

  There are files in /var/crash/

  -rw-r--r-- 1 root whoopsie0 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.upload
  -rw-r- 1 root whoopsie 12792518 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.crash
  -rw--- 1 whoopsie whoopsie   37 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.uploaded
  -rw-r--r-- 1 petr whoopsie0 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.upload
  -rw-r- 1 petr whoopsie   516897 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.crash
  -rw--- 1 whoopsie whoopsie   37 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.uploaded
  -rw-r--r-- 1 petr whoopsie0 Jan  5 14:13 
_opt_zoom_zoom.1000.upload
  -rw-r- 1 petr whoopsie 46590288 Jan  5 14:13 _opt_zoom_zoom.1000.crash
  -rw--- 1 whoopsie whoopsie   37 Jan  5 14:13 
_opt_zoom_zoom.1000.uploaded

  
  and .xsession-errors.old ends with

  (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 
0x649, atom "_NET_WM_STATE_STAYS_ON_TOP")
  (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0
  Exiting due to channel error.
  Failed to parse arguments: Cannot open display: :0.0
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open 
display.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0
  (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"

  Is it safe and useful to upload the files from /var/crash/?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Jan  5 14:17:42 2023
  DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:3f96]
  InstallationDate: Installed on 2021-11-07 (424 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20YA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic 
root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago)
  dmi.bios.date: 09/23/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMCN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: ThinkBook 13s G3 ACN
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMCN27WW:bd09/23/2021:br1.27:efr1.19:svnLENOVO:pn20YA:pvrThinkBook13sG3ACN:rvnLENOVO

[Desktop-packages] [Bug 2002432] [NEW] X11 not started during boot, crashed

2023-01-10 Thread Marian Minar

Public bug reported:

After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I
can only boot into recovery mode.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Tue Jan 10 18:45:16 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed
 acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed
 tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed
 tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:501e]
InstallationDate: Installed on 2015-11-17 (2611 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20AV002WXS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset 
dis_ucode_ldr i915.enable_hangcheck=0
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2018
dmi.bios.release: 1.93
dmi.bios.vendor: LENOVO
dmi.bios.version: J4ET93WW(1.93)
dmi.board.asset.tag: Not Available
dmi.board.name: 20AV002WXS
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540:
dmi.product.family: ThinkPad L540
dmi.product.name: 20AV002WXS
dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540
dmi.product.version: ThinkPad L540
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
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
xserver.bootTime: Tue Jan 10 18:24:35 2023
xserver.configfile: /root/xorg.conf.new
xserver.devices:
 
xserver.errors: Server terminated with error (2). Closing log file.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:21.1.3-2ubuntu2.5

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

Title:
  X11 not started during boot, crashed

Status in xorg package in Ubuntu:
  New

Bug description:
  After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I
  can only boot into recovery mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 10 18:45:16 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed
   acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:501e]
  InstallationDate: Installed on 2015-11-17 (2611 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20AV002WXS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset 
dis_ucode_ldr i915.enable_hangcheck=0
  SourcePackage: xorg
  U

[Desktop-packages] [Bug 2002415] Re: package chromium-browser 108.0.5359.71-0ubuntu0.18.04.5 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e

2023-01-10 Thread Nathan Teodosio

>From DpkgTerminalLog.txt:

--->
(Get 
https://api.snapcraft.io/api/v1/snaps/download/jZLfBRzf1cYlYysIjD2bwSzNtngY0qit_1535.snap:
 dial tcp: lookup api.snapcraft.io on 127.0.0.53:53: read udp 
127.0.0.1:59253->127.0.0.53:53: i/o timeout)
<---

Looks like a temporary outage of snapcraft.io, and I think this isn't
the first report whose cause was that, so probably a more explanatory
error message would be helpful.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Triaged

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  package chromium-browser 108.0.5359.71-0ubuntu0.18.04.5 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  I was updating from 18.04 to 20.04 and I was given the option to do a
  partial upgrade and then everything did'nt go well it seems. there's
  an issue with chromium and some other packages

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 108.0.5359.71-0ubuntu0.18.04.5
  ProcVersionSignature: Ubuntu 5.4.0-136.153~18.04.1-generic 5.4.218
  Uname: Linux 5.4.0-136-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ5XQGAAEaAQSVIhN4CiQQl1lUjiceUFQBAQEBAQEBAQEBAQEBAQEBZBtWd1AAEzAwIDYAWMIQAAAaohdWuVAALTAwIDYAWMIQAAAa/gBGVkdQUIBOVDE1TjQyQQGUABkBCiAgAFQ=
   modes: 1366x768 1366x768
  Date: Tue Jan 10 09:11:35 2023
  Desktop-Session:
   'None'
   'None'
   'None'
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  Env:
   'None'
   'None'
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-10-31 (1531 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  InstalledPlugins:
   
  Load-Avg-1min: 1.92
  Load-Processes-Running-Percent:   0.1%
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15-3573
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-136-generic 
root=UUID=8c431716-fe56-47f3-b49f-b7bb6d054608 ro alx.enable_wol=1 
mem_sleep_default=deep quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: chromium-browser
  Title: package chromium-browser 108.0.5359.71-0ubuntu0.18.04.5 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0XT9M4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0XT9M4:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3573
  dmi.product.sku: 083E
  dmi.product.version: 1.4.0
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2002415/+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 1996148] Re: pipewire update to 0.3.48-1ubuntu2 resulted in regressions

This bug was fixed in the package pipewire - 0.3.48-1ubuntu3

---
pipewire (0.3.48-1ubuntu3) jammy; urgency=medium

  * Revert the previous change to resolve a regression with screencasting.
Extra fixes are available upstream but figuring out the details will
take longer (lp: #1996148)

 -- Sebastien Bacher   Wed, 09 Nov 2022 12:12:45
+0100

** Changed in: pipewire (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  pipewire update to  0.3.48-1ubuntu2 resulted in regressions

Status in pipewire package in Ubuntu:
  Invalid
Status in pipewire source package in Jammy:
  Fix Released

Bug description:
  The SRU in bug 1985057 resulted in regression reports, including bug
  1987631, currently marked as duplicates bug 1993912 and bug 1995358,
  and possibly bug 1994928. It's clear that we need to revert, but I
  don't want the metadata to close all of those regression bugs since it
  isn't clear that they will definitely be resolved with the revert. So
  this is a meta-bug to track the revert itself, to ensure that the
  original bug remains open after the revert lands. I will change Seb's
  upload to refer to this bug instead. Hopefully this is the most
  helpful arrangement to keep bug statuses and tooling clean and
  accurate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1996148/+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 1996067] Re: [SRU] Enable support for Antelope Cloud Archive

This bug was fixed in the package software-properties - 0.99.22.4

---
software-properties (0.99.22.4) jammy; urgency=medium

  * cloudarchive: Enable support for the Antelope Ubuntu Cloud Archive on
22.04 (LP: #1996067).

 -- Corey Bryant   Wed, 09 Nov 2022 09:29:26
-0500

** Changed in: software-properties (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
   [SRU] Enable support for Antelope Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:antelope
 cloud-archive:antelope-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the antelope cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:antelope
  sudo add-apt-repository cloud-archive:antelope-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1996067/+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 2002451] [NEW] Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1

2023-01-10 Thread Till Kamppeter

Public bug reported:

I have released the second generation of cups-filters some weeks ago:

https://openprinting.github.io/cups-filters-Second-Generation-First-
Beta-Release/

It is an architecture change needed for the transition into the New
Architecture of printing, where we will go all-IPP and classic CUPS
printer drivers/filters and PPD files will get replaced by Printer
Applications (emulations of driverless IPP printers).

To get a smooth transition and to fade out the PPD file support code and
its need to get maintained, I have split the upstream source package
cups-filters into libcupsfilters, libppd, cups-filters, braille-printer-
app, and cups-browsed. This especially allows to use the library
libcupsfilters in Printer Applications without pulling in the PPD file
support code in libppd.

The Debian/Ubuntu packages will also be based on the the 5 source
packages libcupsfilters, libppd, cups-filters, braille-printer-app, and
cups-browsed and not come from a single cups-filters source package any
more.

For testing this and also solving the problem that there is a package
named libppd in Debian which got abandoned 20 years ago (bug #2000411) I
decided to put all the new packages, of the 2nd generation of cups-
filters and also new packages depending on these, into a PPA:

https://launchpad.net/~till-kamppeter/+archive/ubuntu/new-arch-
dev/+packages

On one of these uploads, the one of the cups-filters package, I
accidentally uploaded directly to lunar and not to the PPA and it got
accepted into lunar-proposed.

It will not migrate to the release, as it FTBFS due to its build
dependencies libcupsfilters (>= 2~) and libppd (>= 2~) not being in
lunar.

I want to ask you with this bug report to remove/reject this accidental
upload, so that in the time being until everything with the 2nd-gen
cups-filters is solved, I can upload cups-filters 1.x packages again.

** Affects: cups-filters (Ubuntu)
 Importance: High
 Status: New

** Changed in: cups-filters (Ubuntu)
   Importance: Undecided => High

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

Title:
  Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1

Status in cups-filters package in Ubuntu:
  New

Bug description:
  I have released the second generation of cups-filters some weeks ago:

  https://openprinting.github.io/cups-filters-Second-Generation-First-
  Beta-Release/

  It is an architecture change needed for the transition into the New
  Architecture of printing, where we will go all-IPP and classic CUPS
  printer drivers/filters and PPD files will get replaced by Printer
  Applications (emulations of driverless IPP printers).

  To get a smooth transition and to fade out the PPD file support code
  and its need to get maintained, I have split the upstream source
  package cups-filters into libcupsfilters, libppd, cups-filters,
  braille-printer-app, and cups-browsed. This especially allows to use
  the library libcupsfilters in Printer Applications without pulling in
  the PPD file support code in libppd.

  The Debian/Ubuntu packages will also be based on the the 5 source
  packages libcupsfilters, libppd, cups-filters, braille-printer-app,
  and cups-browsed and not come from a single cups-filters source
  package any more.

  For testing this and also solving the problem that there is a package
  named libppd in Debian which got abandoned 20 years ago (bug #2000411)
  I decided to put all the new packages, of the 2nd generation of cups-
  filters and also new packages depending on these, into a PPA:

  https://launchpad.net/~till-kamppeter/+archive/ubuntu/new-arch-
  dev/+packages

  On one of these uploads, the one of the cups-filters package, I
  accidentally uploaded directly to lunar and not to the PPA and it got
  accepted into lunar-proposed.

  It will not migrate to the release, as it FTBFS due to its build
  dependencies libcupsfilters (>= 2~) and libppd (>= 2~) not being in
  lunar.

  I want to ask you with this bug report to remove/reject this
  accidental upload, so that in the time being until everything with the
  2nd-gen cups-filters is solved, I can upload cups-filters 1.x packages
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002451/+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 2002453] [NEW] wayland external monitor turned off for second user

2023-01-10 Thread Johannes Timm

Public bug reported:

Im using Gonome-Wayland for the login screen and user sessions on my
hybrid (Intel+Nvidia) laptop.

When Im in the login screen all monitors are turned on (and display the
mouse). The first user that logs in and starts its Wayland session can
use all screens. This session is left running and the swithc user
functionality is used to log into the other account. Here only the
Laptop screen (intel) works, the external screen turns off (no signal).
Within the login screen all screens work.

Im using the multiuser capabilities to distinguish between my "work" and
"personal" user profile.

Its intended that both users and the login screen may use all screens at
all times. Theoretically each user may have their personal set of
devices using advanced features of loginctl.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 10 23:57:02 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-07-16 (178 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  wayland external monitor turned off for second user

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Im using Gonome-Wayland for the login screen and user sessions on my
  hybrid (Intel+Nvidia) laptop.

  When Im in the login screen all monitors are turned on (and display
  the mouse). The first user that logs in and starts its Wayland session
  can use all screens. This session is left running and the swithc user
  functionality is used to log into the other account. Here only the
  Laptop screen (intel) works, the external screen turns off (no
  signal). Within the login screen all screens work.

  Im using the multiuser capabilities to distinguish between my "work"
  and "personal" user profile.

  Its intended that both users and the login screen may use all screens
  at all times. Theoretically each user may have their personal set of
  devices using advanced features of loginctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 10 23:57:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-07-16 (178 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2002453/+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 2002456] [NEW] Random window repaints missing if happen together with title change

2023-01-10 Thread Fenix Elfmz

Public bug reported:

System: Ubuntu 22.04.1 LTS
Hardware: VmWare on i7 3770 configured with 4 CPUs, but wild users from field 
reported same issue on different hardware.
Option 1: User logged in locally through Ubuntu on XOrg option in login screen.
Option 2: User logged in remotely via xrdp protocol that uses XOrg.

Problem manifested as sporadic missing repaints of application. Debugging shows 
that missing repaints happen in case window title text changed just before 
window image repainting.
Was able to create minimalistic X11 test application that on each keypress: 
changes titlebar to random string and (immediately) paints some string inside. 
From time to time titlebar changed but content inside is not painted, although 
according to debug prints expose events arrived correctly all the time. However 
if in such situation try to move window by grabbing its titlebar using mouse 
(sometimes its enough just to move mouse over) - then content gets updated to 
correct one and (according to debug printouts) this happens without getting 
expose events by application. 

Attached: source code of demo application and will try to attach also video 
recording of demonstration.
Note that bug highly depends on timings (likely its a race condition somewhere 
in XWayland or Window Manager and there is loop in code attenuated for highest 
reproduction rate on my system. On other systems it may need adjustements.

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

** Attachment added: "Minimal reproduction application"
   
https://bugs.launchpad.net/bugs/2002456/+attachment/5640552/+files/x11app.tar.gz

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

Title:
  Random window repaints missing if happen together with title change

Status in xwayland package in Ubuntu:
  New

Bug description:
  System: Ubuntu 22.04.1 LTS
  Hardware: VmWare on i7 3770 configured with 4 CPUs, but wild users from field 
reported same issue on different hardware.
  Option 1: User logged in locally through Ubuntu on XOrg option in login 
screen.
  Option 2: User logged in remotely via xrdp protocol that uses XOrg.

  Problem manifested as sporadic missing repaints of application. Debugging 
shows that missing repaints happen in case window title text changed just 
before window image repainting.
  Was able to create minimalistic X11 test application that on each keypress: 
changes titlebar to random string and (immediately) paints some string inside. 
From time to time titlebar changed but content inside is not painted, although 
according to debug prints expose events arrived correctly all the time. However 
if in such situation try to move window by grabbing its titlebar using mouse 
(sometimes its enough just to move mouse over) - then content gets updated to 
correct one and (according to debug printouts) this happens without getting 
expose events by application. 

  Attached: source code of demo application and will try to attach also video 
recording of demonstration.
  Note that bug highly depends on timings (likely its a race condition 
somewhere in XWayland or Window Manager and there is loop in code attenuated 
for highest reproduction rate on my system. On other systems it may need 
adjustements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2002456/+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 2002451] Re: Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1

2023-01-10 Thread Steve Langasek

Removing packages from lunar-proposed:
cups-filters 2.0~b2-0ubuntu1 in lunar
Comment: Wrong upload target
1 package successfully removed.


** Changed in: cups-filters (Ubuntu)
   Status: New => Fix Released

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

Title:
  Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  I have released the second generation of cups-filters some weeks ago:

  https://openprinting.github.io/cups-filters-Second-Generation-First-
  Beta-Release/

  It is an architecture change needed for the transition into the New
  Architecture of printing, where we will go all-IPP and classic CUPS
  printer drivers/filters and PPD files will get replaced by Printer
  Applications (emulations of driverless IPP printers).

  To get a smooth transition and to fade out the PPD file support code
  and its need to get maintained, I have split the upstream source
  package cups-filters into libcupsfilters, libppd, cups-filters,
  braille-printer-app, and cups-browsed. This especially allows to use
  the library libcupsfilters in Printer Applications without pulling in
  the PPD file support code in libppd.

  The Debian/Ubuntu packages will also be based on the the 5 source
  packages libcupsfilters, libppd, cups-filters, braille-printer-app,
  and cups-browsed and not come from a single cups-filters source
  package any more.

  For testing this and also solving the problem that there is a package
  named libppd in Debian which got abandoned 20 years ago (bug #2000411)
  I decided to put all the new packages, of the 2nd generation of cups-
  filters and also new packages depending on these, into a PPA:

  https://launchpad.net/~till-kamppeter/+archive/ubuntu/new-arch-
  dev/+packages

  On one of these uploads, the one of the cups-filters package, I
  accidentally uploaded directly to lunar and not to the PPA and it got
  accepted into lunar-proposed.

  It will not migrate to the release, as it FTBFS due to its build
  dependencies libcupsfilters (>= 2~) and libppd (>= 2~) not being in
  lunar.

  I want to ask you with this bug report to remove/reject this
  accidental upload, so that in the time being until everything with the
  2nd-gen cups-filters is solved, I can upload cups-filters 1.x packages
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002451/+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 2002456] Re: Random window repaints missing if happen together with title change

2023-01-10 Thread Fenix Elfmz

Here is video record of reproduction... Hope it will upload//

** Attachment added: "Recording of reproduction using this app"

https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2002456/+attachment/5640553/+files/Screencast%202023-01-11%2002%3A28%3A35.mp4

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

Title:
Random window repaints missing if happen together with title change

Status in xwayland package in Ubuntu:
New

Bug description:
System: Ubuntu 22.04.1 LTS
Hardware: VmWare on i7 3770 configured with 4 CPUs, but wild users from field
reported same issue on different hardware.
Option 1: User logged in locally through Ubuntu on XOrg option in login
screen.
Option 2: User logged in remotely via xrdp protocol that uses XOrg.

Problem manifested as sporadic missing repaints of application. Debugging
shows that missing repaints happen in case window title text changed just
before window image repainting.
Was able to create minimalistic X11 test application that on each keypress:
changes titlebar to random string and (immediately) paints some string inside.
From time to time titlebar changed but content inside is not painted, although
according to debug prints expose events arrived correctly all the time. However
if in such situation try to move window by grabbing its titlebar using mouse
(sometimes its enough just to move mouse over) - then content gets updated to
correct one and (according to debug printouts) this happens without getting
expose events by application.

Attached: source code of demo application and will try to attach also video
recording of demonstration.
Note that bug highly depends on timings (likely its a race condition
somewhere in XWayland or Window Manager and there is loop in code attenuated
for highest reproduction rate on my system. On other systems it may need
adjustements.

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

[Desktop-packages] [Bug 1010683] Re: ATI Resume from Suspend leads into black screen (VGA_Switcheroo)

2023-01-10 Thread Bug Watch Updater

** Changed in: xserver-xorg-driver-ati
   Status: Unknown => Fix Released

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

Title:
  ATI Resume from Suspend leads into black screen (VGA_Switcheroo)

Status in Linux:
  Confirmed
Status in xserver-xorg-driver-ati:
  Fix Released
Status in xserver-xorg-video-ati package in Ubuntu:
  Incomplete

Bug description:
  I have a HP Touchsmart 2 (tm2).
  This Notebook has 2 Graphiccars: Intel (DIS) and ATI (IGD):
  # lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Core Processor 
Integrated Graphics Controller (rev 02)
  01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI 
Manhattan [Mobility Radeon HD 5400 Series]

  If i use the Intel-Graphiccard, everything works well, i can suspend and 
resume as often as i'd like.
  Edit: As soon as I switched (switch to ATI and back to Intel, the below 
problem happens on Intel-GPU too).
  If i use the ATI-Graphiccard i can suspend (wich takes a longer time than 
with the Intel one) however I can't resume. I get a blank/black screen and 
can't change brightness. Plus I can't switch to any tty.

  I've tried this instructions to find an error: 
https://wiki.ubuntu.com/DebuggingKernelSuspend
  but it dosn't seem to bring relevant informations (however, I'll add the 
dmesg.txt to this bugreport)

  PS: to switch between graphiccards, I use "vga_switcheroo" and i have
  "vanilla"-ubuntu, no third party software.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.1.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.317
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Fri Jun  8 20:54:43 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1486]
   Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 
Series] [1002:68e0] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company TouchSmart tm2-2050er discrete GPU 
(Mobility Radeon HD 5450) [103c:1486]
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2)
  MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed 
boot=casper  quiet splash -- persistent BOOT_IMAGE=/casper/vmlinuz
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1486
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.1A
  dmi.chassis.asset.tag: CNU0250216
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd07/30/2010:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr048920252A2000122:rvnHewlett-Packard:rn1486:rvr83.1A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP TouchSmart tm2 Notebook PC
  dmi.product.version: 048920252A2000122
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.7.8-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20120322+ab7291d-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1010683/+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.ne

[Desktop-packages] [Bug 2002451] Re: Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1

2023-01-10 Thread Till Kamppeter

@vorlon, thank you very much!

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

Title:
  Accidentally uploaded: cups-filters 2.0~b2-0ubuntu1

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  I have released the second generation of cups-filters some weeks ago:

  https://openprinting.github.io/cups-filters-Second-Generation-First-
  Beta-Release/

  It is an architecture change needed for the transition into the New
  Architecture of printing, where we will go all-IPP and classic CUPS
  printer drivers/filters and PPD files will get replaced by Printer
  Applications (emulations of driverless IPP printers).

  To get a smooth transition and to fade out the PPD file support code
  and its need to get maintained, I have split the upstream source
  package cups-filters into libcupsfilters, libppd, cups-filters,
  braille-printer-app, and cups-browsed. This especially allows to use
  the library libcupsfilters in Printer Applications without pulling in
  the PPD file support code in libppd.

  The Debian/Ubuntu packages will also be based on the the 5 source
  packages libcupsfilters, libppd, cups-filters, braille-printer-app,
  and cups-browsed and not come from a single cups-filters source
  package any more.

  For testing this and also solving the problem that there is a package
  named libppd in Debian which got abandoned 20 years ago (bug #2000411)
  I decided to put all the new packages, of the 2nd generation of cups-
  filters and also new packages depending on these, into a PPA:

  https://launchpad.net/~till-kamppeter/+archive/ubuntu/new-arch-
  dev/+packages

  On one of these uploads, the one of the cups-filters package, I
  accidentally uploaded directly to lunar and not to the PPA and it got
  accepted into lunar-proposed.

  It will not migrate to the release, as it FTBFS due to its build
  dependencies libcupsfilters (>= 2~) and libppd (>= 2~) not being in
  lunar.

  I want to ask you with this bug report to remove/reject this
  accidental upload, so that in the time being until everything with the
  2nd-gen cups-filters is solved, I can upload cups-filters 1.x packages
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2002451/+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 424044]

2023-01-10 Thread Qa-admin-q

Dear Yury,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  [Upstream] Math Object formula changed causing resize saving .odt to
  .doc

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Triaged
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org-writer

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.3.3-1ubuntu2
Candidate: 1:3.3.3-1ubuntu2
Version table:
   *** 1:3.3.3-1ubuntu2 0
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/424044/+attachment/2287815/+files/example.odt
  && lowriter -nologo example.odt

  save to .doc and open the .doc it looks the same as the .odt.

  4) What happens instead is the embedded Math equation is resized. The
  Math equation changes from:

  size 21{ Prod cSub { size 14{ ital "k="1} } cSup { size 14{N} } {p rSub {size 
14 {k}
  }^{size 14 n_{size 10 k} } } }

  in the .odt to:

  size 12{ Prod cSub { size 8{ ital "k="1} } cSup { size 8{N} } {p rSub
  { size 8{k} } rSup { size 8{n rSub {k} } } } } {}

  in .doc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/424044/+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 2001922] Re: Xorg crash

Thanks. Unfortunately that doesn't contain the Xorg log that it should.
I don't know if that's because this is Xubuntu or because this is an
upgrade from 21.10 to 22.04.

On that note, you're also using an old kernel 5.13 which should have
upgraded to at least 5.15. But the old kernel is *probably* not the
cause of this bug.

Can you find where your current Xorg log files are (containing the
crash)?

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu 22.04.1 LTS installation crashes, but I was not able to
  figure out how to reproducibly trigger the crash. The last time it
  happened was with firefox and zoom running, the display suddenly went
  black and after a few seconds the X login screen appeared, my session
  gone.

  There are files in /var/crash/

  -rw-r--r-- 1 root whoopsie0 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.upload
  -rw-r- 1 root whoopsie 12792518 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.crash
  -rw--- 1 whoopsie whoopsie   37 Jan  5 14:09 
_usr_lib_xorg_Xorg.0.uploaded
  -rw-r--r-- 1 petr whoopsie0 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.upload
  -rw-r- 1 petr whoopsie   516897 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.crash
  -rw--- 1 whoopsie whoopsie   37 Jan  5 14:13 
_usr_bin_xfsettingsd.1000.uploaded
  -rw-r--r-- 1 petr whoopsie0 Jan  5 14:13 
_opt_zoom_zoom.1000.upload
  -rw-r- 1 petr whoopsie 46590288 Jan  5 14:13 _opt_zoom_zoom.1000.crash
  -rw--- 1 whoopsie whoopsie   37 Jan  5 14:13 
_opt_zoom_zoom.1000.uploaded

  
  and .xsession-errors.old ends with

  (xfwm4:8122): xfwm4-WARNING **: 14:11:00.736: unmanaged net_wm_state (window 
0x649, atom "_NET_WM_STATE_STAYS_ON_TOP")
  (xfwm4:10847): Gtk-WARNING **: 14:13:01.216: cannot open display: :0.0
  Exiting due to channel error.
  Failed to parse arguments: Cannot open display: :0.0
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  (xfsettingsd:10849): xfsettingsd-ERROR **: 14:13:01.239: Unable to open 
display.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  (xfwm4:10854): Gtk-WARNING **: 14:13:01.244: cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  (xfwm4:10860): Gtk-WARNING **: 14:13:01.264: cannot open display: :0.0
  (xfwm4:10863): Gtk-WARNING **: 14:13:01.280: cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  (xfwm4:10865): Gtk-WARNING **: 14:13:01.293: cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  Failed to parse arguments: Cannot open display: :0.0
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"
  Invalid MIT-MAGIC-COOKIE-1 keyxset:  unable to open display ":0.0"

  Is it safe and useful to upload the files from /var/crash/?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Jan  5 14:17:42 2023
  DistUpgraded: 2022-12-25 11:03:07,557 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.13.0-35-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Cezanne [17aa:3f96]
  InstallationDate: Installed on 2021-11-07 (424 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20YA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic 
root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to jammy on 2022-12-25 (11 days ago)
  dmi.bios.date: 09/23/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMCN27WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: ThinkBook 13s G3 ACN
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dm

[Desktop-packages] [Bug 1800555] Re: Computer slow. Error reports appear.

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Computer slow. Error reports appear.

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Computer slow. Error reports appear. Says system is running on low
  graphics sometimes. Makes me log in most of the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   [[0;32m  OK  [0m] Stopped WPA supplicant.
   [[0;32m  OK  [0m] Started Show Plymouth Boot Screen.
Starting Hold until boot process finishes up...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 29 17:37:27 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1]
  InstallationDate: Installed on 2016-09-11 (778 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard p6710f
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic 
root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.07
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CE0480TV4
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6710f
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 29 17:32:25 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800555/+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 1790519] Re: package xserver-common 2:1.18.4-0ubuntu0.8 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package xserver-common 2:1.18.4-0ubuntu0.8 failed to install/upgrade:
  problemi con le dipendenze - lasciato non configurato

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  pc blocked and needs hard power off or reboot more than two times.
  Every time I power on pc I see messages with "There is a problem..."

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xserver-common 2:1.18.4-0ubuntu0.8
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep  3 20:08:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: problemi con le dipendenze - lasciato non configurato
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] 
[1002:94c3] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV610 [Radeon HD 2400 
PRO] [174b:e370]
  MachineType: CdcPointSpa MS-7255
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=0ce495b0-d61b-494b-bde1-68981ac3b3ca ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: xorg-server
  Title: package xserver-common 2:1.18.4-0ubuntu0.8 failed to install/upgrade: 
problemi con le dipendenze - lasciato non configurato
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V5.6C
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7255
  dmi.board.vendor: Micro-Star
  dmi.board.version: 2.0
  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.:bvrV5.6C:bd11/15/2007:svnCdcPointSpa:pnMS-7255:pvr2.0:rvnMicro-Star:rnMS-7255:rvr2.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7255
  dmi.product.version: 2.0
  dmi.sys.vendor: CdcPointSpa
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Sep  3 20:07:34 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSleep Button KEYBOARD, id 8
   inputMicrosoft Microsoft Wheel Mouse Optical® MOUSE, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1790519/+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 1762336] Re: when viewing ads in youtube, the screen lock is turned on

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  when viewing ads in youtube, the screen lock is turned on

Status in firefox package in Ubuntu:
  Expired

Bug description:
  1. Expect that video playback will be continuous throughout the entire video. 
  2. It turned out that when advertising in the video is enabled lock screen. 
This prevents you from watching the video. 
  3. I open the browser, I start video on youtube after long viewing 
advertising video hosting is started and with it the screen lock is started.

  ---

  1. Ожидаю что режим просмотра видео будет непрерывен на протяжении всего 
видео. 
  2. Оказалось что при появлении рекламы в видео включается блокировка экрана. 
Это мешает просмотру видео. 
  3. Открываю браузер, запускаю видео на youtube после длительного просмотра 
запускается реклама видеохостинга и с ней запускается блокировка экрана.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 59.0.2+build1-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   alexandr   1788 F...m pulseaudio
   /dev/snd/controlC0:  alexandr   1788 F pulseaudio
  BuildID: 20180404120016
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Mon Apr  9 13:24:47 2018
  ExecutablePath: /usr/lib/firefox/firefox
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-02-01 (66 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.0.1 dev wlp4s0  proto static  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s0  proto kernel  scope link  src 192.168.0.14  
metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=59.0.2/20180404120016 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.17
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571G
  dmi.board.vendor: Acer
  dmi.board.version: V2.17
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.17
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.17:bd02/27/2013:svnAcer:pnAspireV5-571G:pvrV2.17:rvnAcer:rnAspireV5-571G:rvrV2.17:cvnAcer:ct9:cvrV2.17:
  dmi.product.family: Aspire V5-571G
  dmi.product.name: Aspire V5-571G
  dmi.product.version: V2.17
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1762336/+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 1631643] Re: 1920x1080 HDMI output is corrupted in 16.04

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  1920x1080 HDMI output is corrupted in 16.04

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Ever since upgrading to 16.04 from 14.04 on my Lenovo x230 the HDMI
  output to a Benq W1070 is corrupted if run at 1920x1080 (native
  resolution). At 1280x720 the display looks fine. Looking at similar
  reports for other graphics cards it seems similar to cases when the
  frequency is too low. I've tested that the projector still works fine
  with the same cable and another computer. I've attached a photo of the
  kind of corruption that shows up on screen. It's mostly green/magenta
  pixels sprinkled across the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Oct  8 19:38:39 2016
  DistUpgraded: 2016-08-07 01:11:54,340 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  InstallationDate: Installed on 2014-05-03 (889 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 23252QG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=UUID=9018e190-86bb-4fbf-a348-d47ea769640f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-08-07 (62 days ago)
  dmi.bios.date: 05/24/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET31WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23252QG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET31WW(1.11):bd05/24/2012:svnLENOVO:pn23252QG:pvrThinkPadX230:rvnLENOVO:rn23252QG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23252QG
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Oct  5 10:26:16 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1631643/+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 1692149] Re: Firefox thinks w3.css is a domain

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Firefox thinks w3.css is a domain

Status in firefox package in Ubuntu:
  Expired

Bug description:
  When I type in w3.css in the url bar it gives this:
  https://s9.postimg.org/4f15c6ndb/Screenshot_from_2017-05-19_21-28-10.png

  Even though I should not be doing searches in the url bar I'm
  accustomed to chrome's omnibox

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 53.0.2+build1-0ubuntu0.17.04.2
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   alexios2049 F...m pulseaudio
   /dev/snd/controlC0:  alexios2049 F pulseaudio
  BuildID: 20170509205512
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7
  Date: Fri May 19 21:25:03 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-05-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp9s0 proto static metric 600 
   169.254.0.0/16 dev wlp9s0 scope link metric 1000 
   192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.252 metric 
600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=53.0.2/20170509205512 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to zesty on 2017-05-20 (0 days ago)
  dmi.bios.date: 10/05/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: MA40_HX
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.07:bd10/05/2012:svnAcer:pnAspireM5-481PT:pvrV2.07:rvnAcer:rnMA40_HX:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire M5-481PT
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1692149/+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 1568904] Re: Xorg crashed with SIGABRT

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Xorg crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  After of exit of game, "Snow" of Steam, the error appeared. I had to
  end the session because the system crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.15  Sat Apr  2 21:30:33 
PDT 2016
   GCC version:  gcc version 5.3.1 20160407 (Ubuntu 5.3.1-13ubuntu6)
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Apr 11 11:51:06 2016
  Disassembly: => 0x7f8ff3e40518:   Não é possível acessar a memória no 
endereço 0x7f8ff3e40518
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-18-generic, x86_64: installed
   nvidia-364, 364.15, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.16, 4.4.0-17-generic, x86_64: installed
   vboxhost, 5.0.16, 4.4.0-18-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0616]
 Subsystem: Dell GK208M [GeForce GT 740M] [1028:0616]
  InstallationDate: Installed on 2016-03-19 (23 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Dell Inc. Vostro 5470
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=c1651082-fabc-4b0c-b328-6c708e33f208 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  Stacktrace:
   #0  0x7f8ff3e40518 in ?? ()
   No symbol table info available.
   Backtrace stopped: Não é possível acessar a memória no endereço 
0x7ffd30b6b768
  StacktraceTop: ?? ()
  ThreadStacktrace:
   .
   Thread 1 (LWP 1360):
   #0  0x7f8ff3e40518 in ?? ()
   No symbol table info available.
   Backtrace stopped: Não é possível acessar a memória no endereço 
0x7ffd30b6b768
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F7NWH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn0F7NWH:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Vostro 5470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1568904/+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 1567700] Re: Xorg crashed with SIGABRT

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Xorg crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  After the update of  xorg package and after system rebooting, the
  error is appearing after logged system.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.15  Sat Apr  2 21:30:33 
PDT 2016
   GCC version:  gcc version 5.3.1 20160405 (Ubuntu 5.3.1-13ubuntu4)
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Thu Apr  7 20:15:23 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-16-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed
   nvidia-364, 364.15, 4.4.0-17-generic, x86_64: installed
   vboxhost, 5.0.16, 4.4.0-16-generic, x86_64: installed
   vboxhost, 5.0.16, 4.4.0-17-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0616]
 Subsystem: Dell GK208M [GeForce GT 740M] [1028:0616]
  InstallationDate: Installed on 2016-03-19 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Dell Inc. Vostro 5470
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic.efi.signed 
root=UUID=c1651082-fabc-4b0c-b328-6c708e33f208 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F7NWH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn0F7NWH:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Vostro 5470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1567700/+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 1570129] Re: Xorg crashed with SIGABRT

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Xorg crashed with SIGABRT

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  After the last update and after of reboot system the error appeared.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  364.15  Sat Apr  2 21:30:33 
PDT 2016
   GCC version:  gcc version 5.3.1 20160407 (Ubuntu 5.3.1-13ubuntu6)
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Apr 13 19:42:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-18-generic, x86_64: installed
   nvidia-364, 364.15, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.16, 4.4.0-17-generic, x86_64: installed
   vboxhost, 5.0.16, 4.4.0-18-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0616]
 Subsystem: Dell GK208M [GeForce GT 740M] [1028:0616]
  InstallationDate: Installed on 2016-03-19 (25 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Dell Inc. Vostro 5470
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=c1651082-fabc-4b0c-b328-6c708e33f208 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
   ?? ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F7NWH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn0F7NWH:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Vostro 5470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1570129/+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 2002414] Re: Gnome does not open (appear)

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please check for crashes and also collect a full system
log:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
   Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. Run:
journalctl -b0 > journal.txt
   and attach the resulting text file here.


** Package changed: plymouth (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Gnome does not open (appear)

Status in Ubuntu:
  Incomplete

Bug description:
  Since latest update, on 2023-01-09 my laptop can not reach Gnome,
  stuck on the text boot screen after GRUB. Kernel: 5.19.0-28 (previous
  installed was 5.19.0-26). No useful error message displayed.

  When doing ALT+CTRL+F2 I can log as user and see (top) that the computer is 
not hang.
  When doing CTRL+ALT+TAB, the graphical Ubuntu shutown screen does appear, 
then the computer does reboot.

  When booting with 5.19.0-26 I can the same issue, but with more debug
  lines on the text boot screen. No useful error message displayed.

  OS: ubuntu 22.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: plymouth 22.02.122-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  Uname: Linux 5.19.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 10 16:03:39 2023
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2022-05-03 (251 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros 
QCA9377 Bluetooth
   Bus 001 Device 002: ID 25a7:fa23 Areson Technology Corp 2.4G Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575G
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic 
root=UUID=98c8e2f8-38e3-44ff-a926-d1bd59527ca5 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2017
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 2.30
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32:
  dmi.product.family: KBL
  dmi.product.name: Aspire E5-575G
  dmi.product.sku: Aspire E5-575G_115F_1.32
  dmi.product.version: V1.32
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2002414/+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 2002432] Re: X11 not started during boot, crashed

Thanks for the bug report.

The problem preventing Xorg from loading appears to be:

  intel: waited 2020 ms for i915.ko driver to load

But 'intel' is an old buggy driver that nobody should be using. Please
remove any custom configs in /root/xorg.conf.new and
/usr/share/X11/xorg.conf.d that are loading the 'intel' driver and
reboot. The correct Xorg driver that should be loaded by default is
called 'modesetting'.


** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Won't Fix

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- X11 not started during boot, crashed
+ X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

** Tags added: regression-update

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

Title:
  X11 not started during boot (intel: waited 2020 ms for i915.ko driver
  to load)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Won't Fix

Bug description:
  After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I
  can only boot into recovery mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 10 18:45:16 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed
   acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:501e]
  InstallationDate: Installed on 2015-11-17 (2611 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20AV002WXS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset 
dis_ucode_ldr i915.enable_hangcheck=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2018
  dmi.bios.release: 1.93
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET93WW(1.93)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AV002WXS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540:
  dmi.product.family: ThinkPad L540
  dmi.product.name: 20AV002WXS
  dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  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
  xserver.bootTime: Tue Jan 10 18:24:35 2023
  xserver.configfile: /root/xorg.conf.new
  xserver.devices:
   
  xserver.errors: Server terminated with error (2). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:21.1.3-2ubuntu2.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002432/+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 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

Also your logs are all from recovery mode so that explains why there's
no working graphics driver there.

Can you provide a log from a non-recovery boot? Try:

  journalctl -b-1 > prevboot1.txt
  journalctl -b-2 > prevboot2.txt
  journalctl -b-3 > prevboot3.txt

and attach the resulting text files here.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

** Tags removed: regression-update

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

Title:
  X11 not started during boot (intel: waited 2020 ms for i915.ko driver
  to load)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Won't Fix

Bug description:
  After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I
  can only boot into recovery mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 10 18:45:16 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed
   acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:501e]
  InstallationDate: Installed on 2015-11-17 (2611 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20AV002WXS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset 
dis_ucode_ldr i915.enable_hangcheck=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2018
  dmi.bios.release: 1.93
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET93WW(1.93)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AV002WXS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540:
  dmi.product.family: ThinkPad L540
  dmi.product.name: 20AV002WXS
  dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  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
  xserver.bootTime: Tue Jan 10 18:24:35 2023
  xserver.configfile: /root/xorg.conf.new
  xserver.devices:
   
  xserver.errors: Server terminated with error (2). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:21.1.3-2ubuntu2.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002432/+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 2002432] Re: X11 not started during boot (intel: waited 2020 ms for i915.ko driver to load)

Please also remember to delete /root/xorg.conf.new

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

Title:
  X11 not started during boot (intel: waited 2020 ms for i915.ko driver
  to load)

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Won't Fix

Bug description:
  After update from Ubuntu 20.04->22.10 X11 was not correctly updated. I
  can only boot into recovery mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jan 10 18:45:16 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call/1.2.2, 5.15.0-56-generic, x86_64: installed
   acpi-call/1.2.2, 5.15.0-57-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-56-generic, x86_64: installed
   tp_smapi/0.43, 5.15.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:501e]
  InstallationDate: Installed on 2015-11-17 (2611 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20AV002WXS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=23ec64aa-726f-4a3c-b489-2dbbc0a36528 ro recovery nomodeset 
dis_ucode_ldr i915.enable_hangcheck=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2018
  dmi.bios.release: 1.93
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J4ET93WW(1.93)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AV002WXS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ4ET93WW(1.93):bd05/30/2018:br1.93:svnLENOVO:pn20AV002WXS:pvrThinkPadL540:rvnLENOVO:rn20AV002WXS:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AV_BU_Think_FM_ThinkPadL540:
  dmi.product.family: ThinkPad L540
  dmi.product.name: 20AV002WXS
  dmi.product.sku: LENOVO_MT_20AV_BU_Think_FM_ThinkPad L540
  dmi.product.version: ThinkPad L540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  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
  xserver.bootTime: Tue Jan 10 18:24:35 2023
  xserver.configfile: /root/xorg.conf.new
  xserver.devices:
   
  xserver.errors: Server terminated with error (2). Closing log file.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:21.1.3-2ubuntu2.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002432/+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 2002453] Re: wayland external monitor turned off for second user

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

Thanks for the bug report.

It looks likely that both displays are connected to the Intel GPU. And
the recurring messages in the system log explain why one of them is
blank:

  Failed to post KMS update: drmModeAtomicCommit: Invalid argument
  Page flip discarded: drmModeAtomicCommit: Invalid argument

So I think this is a duplicate of bug 1968040.

** This bug has been marked a duplicate of bug 1968040
   Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument 
invalide] [drmModeAtomicCommit: Invalid argument]

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

Title:
  wayland external monitor turned off for second user

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Im using Gonome-Wayland for the login screen and user sessions on my
  hybrid (Intel+Nvidia) laptop.

  When Im in the login screen all monitors are turned on (and display
  the mouse). The first user that logs in and starts its Wayland session
  can use all screens. This session is left running and the swithc user
  functionality is used to log into the other account. Here only the
  Laptop screen (intel) works, the external screen turns off (no
  signal). Within the login screen all screens work.

  Im using the multiuser capabilities to distinguish between my "work"
  and "personal" user profile.

  Its intended that both users and the login screen may use all screens
  at all times. Theoretically each user may have their personal set of
  devices using advanced features of loginctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 10 23:57:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-07-16 (178 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2002453/+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 1784023] Re: Update profiles for usrmerge

2023-01-10 Thread François Marier

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

** Changed in: fwknop (Ubuntu)
 Assignee: (unassigned) => François Marier (fmarier)

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

Title:
  Update profiles for usrmerge

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-profiles-extra package in Ubuntu:
  New
Status in dhcpcanon package in Ubuntu:
  New
Status in ejabberd package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  In Progress
Status in fwknop package in Ubuntu:
  Fix Released
Status in i2p package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in kopanocore package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-freerdp2 package in Ubuntu:
  Fix Released
Status in lightdm-remote-session-x2go package in Ubuntu:
  Fix Released
Status in man-db package in Ubuntu:
  Fix Released
Status in strongswan package in Ubuntu:
  Fix Released
Status in surf package in Ubuntu:
  Fix Released
Status in telepathy-mission-control-5 package in Ubuntu:
  Fix Released
Status in strongswan package in Debian:
  Fix Released

Bug description:
  this is about / and /usr merge.

  /bin & /sbin merge is out of scope. Anything that was in /sbin/  will
  remain in /{,usr/}sbin/.

  = src:apparmor =
  usr.bin.chromium-browser appears to be out of date w.r.t. apparmor-profiles 
upstream git tree

  /usr/share/apparmor/extra-profiles/usr.sbin.useradd needs update
  upstream https://gitlab.com/apparmor/apparmor/merge_requests/152/diffs

  = other packages =

  Slightly more complete list: https://paste.ubuntu.com/p/4zDJ8mTc5Z/

  $ sudo grep '[[:space:]]/bin' -r .
  ./usr.bin.man:  /bin/bzip2 rmCx -> &man_filter,
  ./usr.bin.man:  /bin/gzip rmCx -> &man_filter,
  ./usr.bin.man:  /bin/bzip2 rm,
  ./usr.bin.man:  /bin/gzip rm,
  ./usr.sbin.libvirtd:  /bin/* PUx,
  ./abstractions/lightdm:  /bin/ rmix,
  ./abstractions/lightdm:  /bin/fusermount Px,
  ./abstractions/lightdm:  /bin/** rmix,
  ./abstractions/libvirt-qemu:  /bin/uname rmix,
  ./abstractions/libvirt-qemu:  /bin/grep rmix,
  ./usr.bin.chromium-browser:  /bin/ps Uxr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.chromium-browser:/bin/grep ixr,
  ./usr.bin.chromium-browser:/bin/readlink ixr,
  ./usr.bin.chromium-browser:/bin/sed ixr,
  ./usr.bin.chromium-browser:/bin/which ixr,
  ./usr.bin.chromium-browser:/bin/mkdir ixr,
  ./usr.bin.chromium-browser:/bin/mv ixr,
  ./usr.bin.chromium-browser:/bin/touch ixr,
  ./usr.bin.chromium-browser:/bin/dash ixr,
  ./usr.bin.firefox:  /bin/which ixr,
  ./usr.bin.firefox:  /bin/ps Uxr,
  ./usr.bin.firefox:  /bin/uname Uxr,
  ./usr.bin.firefox:/bin/dash ixr,
  ./sbin.dhclient:  /bin/bash mr,

  $ sudo grep '[[:space:]]/sbin' -r .
  ./usr.lib.telepathy:deny /sbin/ldconfig x,
  ./usr.sbin.libvirtd:  /sbin/* PUx,
  ./abstractions/lightdm:  /sbin/ r,
  ./abstractions/lightdm:  /sbin/** rmixk,
  ./usr.bin.firefox:  /sbin/killall5 ixr,
  ./sbin.dhclient:  /sbin/dhclient mr,
  ./sbin.dhclient:  # daemon to run arbitrary code via /sbin/dhclient-script, 
it would need to be
  ./sbin.dhclient:  /sbin/dhclient-script   Uxr,

  $ sudo grep '[[:space:]]/lib' -r .
  ./snap.core.4917.usr.lib.snapd.snap-confine:/lib/udev/snappy-app-dev ixr, 
# drop
  ./usr.lib.snapd.snap-confine.real:/lib/udev/snappy-app-dev ixr, # drop
  ./abstractions/lightdm:  /lib/ r,
  ./abstractions/lightdm:  /lib/** rmixk,
  ./abstractions/lightdm:  /lib32/ r,
  ./abstractions/lightdm:  /lib32/** rmixk,
  ./abstractions/lightdm:  /lib64/ r,
  ./abstractions/lightdm:  /lib64/** rmixk,
  ./usr.bin.chromium-browser:/lib/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libgcc_s.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libc-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/libld-*.so* mr,
  ./usr.bin.chromium-browser:/lib{,32,64}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/@{multiarch}/ld-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libm-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libpthread-*.so* mr,
  ./usr.bin.chromium-browser:/lib/tls/*/{cmov,nosegneg}/libc-*.so* mr,

  above list might be incomplete

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

[Desktop-packages] [Bug 1971712] Re: Add support for Intel DG2