[Desktop-packages] [Bug 1856838] Re: [memory leak] gnome-shell using a lot of RAM after repeatedly opening the overview

[Daniel van Vugt]

Is anyone still affected by this bug? If so then please ensure you don't
have any extensions loaded and tell us what version of Ubuntu you are
using.


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

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

Title:
  [memory leak] gnome-shell using a lot of RAM after repeatedly opening
  the overview

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Just noticed my gnome-shell was using 3GB RSS. Which seems excessive.
  Spoke to duflu on irc and he suggested I file a bug, and to make sure
  I'm not using any extra extensions.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 18 10:49:44 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (681 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1856838/+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 1956612] Re: Play in this way

[Ioana Lasc]

** Package changed: nautilus (Ubuntu) => null-and-void

** Changed in: null-and-void
   Status: New => Invalid

** Information type changed from Public to Private Security

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

Title:
  Play in this way

Status in NULL Project:
  Invalid

Bug description:
  how to play DOS/Windows executable (application/x-ms-dos-executable)
  Firstly, it's also a requirement that you must have pc or phone to play it!
  For more Info: https://apkmortgage.com/disney-magic-kingdom-mod-apk-1/

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1956612/+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 1423773] Re: [memory leak] Gnome-Shell don't free ram when changing the wallpaper

[Daniel van Vugt]

If anyone can reproduce this bug on a currently-supported version of
Ubuntu without extensions loaded, then please let us know. Keeping in
mind that growing memory usage by a few hundred MB is not a bug - that's
just how big the last few wallpapers are in memory.

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

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Incomplete

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  [memory leak] Gnome-Shell don't free ram when changing the wallpaper

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Sorry for my bad english, here is the link to see the error by
  yourself: https://www.youtube.com/watch?v=O53tt-6v81Y&feature=youtu.be

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1423773/+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 1423773] Re: [memory leak] Gnome-Shell don't free ram when changing the wallpaper

[Daniel van Vugt]

The video at the top of this bug should probably be removed because:

1. It's 6.5 years old so doesn't represent any supported GNOME code.

2. It shows nonstandard extensions in use.

3. It shows memory usage only increasing by around 100MB per image. If
you have a couple of monitors or just very high resolution wallpapers
then that is just how big they are uncompressed, not a bug. The last few
images will be cached in memory and attributed to the gnome-shell
process.

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

Title:
  [memory leak] Gnome-Shell don't free ram when changing the wallpaper

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Sorry for my bad english, here is the link to see the error by
  yourself: https://www.youtube.com/watch?v=O53tt-6v81Y&feature=youtu.be

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1423773/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Daniel van Vugt]

The patch looks trivial:

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1662/diffs

But before we can propose it for 20.04 we need a test case written out
that anyone can follow. I've tried following some test cases mentioned
above but none seem to reproduce the bug for me.

Can anyone provide a new test case?

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1939163] Re: Screen splash when suspend or resume on I+N platform

[Bin Li]

When I switch to intel mode with 'prime-select intel' it will won't load
nvidia module, and this issue couldn't be reproduced.

And on T14 there are no option to disable the discrete GPU.

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

Title:
  Screen splash when suspend or resume on I+N platform

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  1.when clicking the the "Suspend" from the "shutdown" menu,The screen will 
refresh and then sleep
  2.when resuming ,the desktop in buffer will appear first, and then the lock 
screen will appear

  [Reproduce]
  On Intel + Nvidia platform, do suspend and resume.

  [Expected result]
  1. It should show the screen without splash.

  [Actual result]
  1. the screen display abnormal after suspend or before resume.

  [Additional information]
  Kernel Version: 5.10.0-1038-oem
  Ubuntu Version: 20.04.2 LTS
  Image: Ubuntu Linux 20.04.2
  system-manufacturer: LENOVO
  Platform: ThinkPad L14, P15v or T14.
  Nvidia: 460.91.03-0ubuntu0.20.04.1 or 470.57.02-0ubuntu0.20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1939163/+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 1939163] Re: Screen splash when suspend or resume on I+N platform

[Bin Li]

Sorry for reply late, I tried to swith nouveau, but it couldn't enter
suspend with X crash.

Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]: (EE)
Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]: Fatal server 
error:
Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]: (EE) 
systemd-logind disappeared (stopped/restarted?)
Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]: (EE)
Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]: (EE)
Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]: Please consult 
the The X.Org Foundation support
Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]:  at 
http://wiki.x.org
Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]:  for help.
Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]: (EE) Please also 
check the log file at "/home/u/.local/share/xorg/Xorg.0.log" for additional 
information.
Jan 07 01:35:30 Drfit3-T-2 /usr/lib/gdm3/gdm-x-session[1744]: (EE)


** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1939163/+attachment/5552336/+files/Xorg.0.log

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

Title:
  Screen splash when suspend or resume on I+N platform

Status in OEM Priority Project:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  1.when clicking the the "Suspend" from the "shutdown" menu,The screen will 
refresh and then sleep
  2.when resuming ,the desktop in buffer will appear first, and then the lock 
screen will appear

  [Reproduce]
  On Intel + Nvidia platform, do suspend and resume.

  [Expected result]
  1. It should show the screen without splash.

  [Actual result]
  1. the screen display abnormal after suspend or before resume.

  [Additional information]
  Kernel Version: 5.10.0-1038-oem
  Ubuntu Version: 20.04.2 LTS
  Image: Ubuntu Linux 20.04.2
  system-manufacturer: LENOVO
  Platform: ThinkPad L14, P15v or T14.
  Nvidia: 460.91.03-0ubuntu0.20.04.1 or 470.57.02-0ubuntu0.20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1939163/+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 1956718] Re: Evince sometimes goes behind top bar while in maximized state in Ubuntu 21.10

[Soumadeep Sarkar]

** Description changed:

  When I open evince, in the maximized state, the application sometimes
- goes behind the top bar, I have attached a screenshot of the problem.
+ goes behind the top bar, I have attached a screenshot of the problem. It
+ goes to its correct position after I restore and maximise it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: evince 40.4-2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  7 11:46:45 2022
  InstallationDate: Installed on 2021-12-06 (31 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Evince sometimes goes behind top bar while in maximized state in
  Ubuntu 21.10

Status in evince package in Ubuntu:
  New

Bug description:
  When I open evince, in the maximized state, the application sometimes
  goes behind the top bar, I have attached a screenshot of the problem.
  It goes to its correct position after I restore and maximise it.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: evince 40.4-2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  7 11:46:45 2022
  InstallationDate: Installed on 2021-12-06 (31 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1956718/+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 1956718] [NEW] Evince sometimes goes behind top bar while in maximized state in Ubuntu 21.10

[Soumadeep Sarkar]

Public bug reported:

When I open evince, in the maximized state, the application sometimes
goes behind the top bar, I have attached a screenshot of the problem.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: evince 40.4-2
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  7 11:46:45 2022
InstallationDate: Installed on 2021-12-06 (31 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "The top portion of evince is hidden behind the gnome top 
bar."
   
https://bugs.launchpad.net/bugs/1956718/+attachment/5552329/+files/Screenshot%20from%202022-01-07%2011-46-14.png

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

Title:
  Evince sometimes goes behind top bar while in maximized state in
  Ubuntu 21.10

Status in evince package in Ubuntu:
  New

Bug description:
  When I open evince, in the maximized state, the application sometimes
  goes behind the top bar, I have attached a screenshot of the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: evince 40.4-2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  7 11:46:45 2022
  InstallationDate: Installed on 2021-12-06 (31 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1956718/+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 1956714] Re: gui took long time to return from blank screen

[Daniel van Vugt]

Thanks for the bug report.

If the mouse cursor moves still while there is no image on the screen
then this is indeed a gnome-shell issue. But most gnome-shell issues are
actually bugs in extensions so please start by removing these in the
Extensions app:

'gnome-shell-audio-output-switcher@kgaut',
'drive-m...@gnome-shell-extensions.gcampax.github.com',
'system-moni...@paradoxxx.zero.gmail.com',
'window-l...@gnome-shell-extensions.gcampax.github.com',
'shortc...@kyle.aims.ac.za',
'dash-to-pa...@jderose9.github.com'

and then log in again. If the bug still occurs after that then please
try disabling:

'ubuntu-appindicat...@ubuntu.com',
'ubuntu-d...@ubuntu.com'

and then log in again.



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

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

Title:
  gui took long time to return from blank screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I ignored my system for a while, long enough for the screensaver to
  blank the screen.  When I tried to get it to awake ( I don't need to
  log back in), it seemed to be semihung, showing pretty black screen,
  but a mouse cursor visible.  It did not respond to hitting keys.  I
  tried switching back and forth between VT1 and VT2 to get it to come
  back to life.  Eventually it came back on its own, but it took too
  long.

  Here's a chunk of log from the time this happened.  There are on the
  order of 2000 of the "maximum number of pending replies" messages that
  you see at the end of this log snippet.

  
  Jan 06 23:52:41 cerberus gsd-power[2252]: Error setting property 
'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was 
reached (g-io-error-quark, 24)
  Jan 06 23:52:51 cerberus gvfsd[2276168]: Error 2: PTP Layer error 02ff: Error 
getting friendlyname.
  Jan 06 23:52:51 cerberus gvfsd[2276168]: Error 2: Error 02ff: PTP I/O Error
  Jan 06 23:52:51 cerberus gnome-shell[2987]: [System monitor] applet enabling 
done
  Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Jan 06 23:52:51 cerberus gnome-shell[2987]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Jan 06 23:52:51 cerberus gsd-power[3176]: Error setting property 
'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was 
reached (g-io-error-quark, 24)
  Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Jan 06 23:52:51 cerberus gnome-shell[2987]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Jan 06 23:52:51 cerberus gnome-shell[2987]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Jan 06 23:52:51 cerberus gnome-shell[2987]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
  Jan 06 23:52:51 cerberus gnome-shell[2987]: 
cr_declaration_parse_list_from_buf: assertion 'parser' failed
  Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >
  Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >
  Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >
  Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >
  Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >

  ...

  Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager 
--no-daemon " label="unconfined")>
  Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager 
--no-daemon " label="unconfined")>
  Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager 
--no-daemon " label="unconfined")>
  Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.7" (uid=0 pid=14

[Desktop-packages] [Bug 25830]

[Z-sam-i]

Encountered this bug today trying to get a plaintext format (with the
mime type `application/`) to display as plaintext in the
browser rather than Open With > Firefox (and opening a new window.)

Is there still no workaround for enabling this type of functionality,
even by modifying config files in the profile? I tried messing around
with `handlers.json` (the file that holds the mime type preferences set
in `about:preferences` under the "Files and Applications" header) but
had no luck.

Some content types in `about:preferences` permit users to select "Open
in Firefox" while others don't. Where is the safelist of permitted
content types for this behavior? Could a simple solution to this bug be
to add an `about:config` flag that would allow power users to select
"Open in Firefox" for any content type?

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

Title:
  Option to display file in browser, treat as text/plain

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  A suggestion:

  When you click certain files, like .py or .pl files, for example, Firefox 
brings
  up a dialog that offers you the ability to:
  1. Open with a certain application
  2. Save to disk
  What would be nice is a third option:
  3. Treat as text/plain

  The wording could be altered... "Display as text in browser" or
  something.

  Sometimes you just want to quickly visit a file on the web and look for
  something in it, and the fact that you *could* open it in a more customized
  application is true but not really easier for you at that moment. If you just
  want to look a Python script for a version number at the top it is not 
necessary
  to open it in your IDE or save it to disk; you just want to open it in the
  normal viewing window as plain text and quickly find what you need to look at.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/25830/+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 1956714] [NEW] gui took long time to return from blank screen

[Jerry Quinn]

Public bug reported:

I ignored my system for a while, long enough for the screensaver to
blank the screen.  When I tried to get it to awake ( I don't need to log
back in), it seemed to be semihung, showing pretty black screen, but a
mouse cursor visible.  It did not respond to hitting keys.  I tried
switching back and forth between VT1 and VT2 to get it to come back to
life.  Eventually it came back on its own, but it took too long.

Here's a chunk of log from the time this happened.  There are on the
order of 2000 of the "maximum number of pending replies" messages that
you see at the end of this log snippet.


Jan 06 23:52:41 cerberus gsd-power[2252]: Error setting property 
'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was 
reached (g-io-error-quark, 24)
Jan 06 23:52:51 cerberus gvfsd[2276168]: Error 2: PTP Layer error 02ff: Error 
getting friendlyname.
Jan 06 23:52:51 cerberus gvfsd[2276168]: Error 2: Error 02ff: PTP I/O Error
Jan 06 23:52:51 cerberus gnome-shell[2987]: [System monitor] applet enabling 
done
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: 
assertion 'parser' failed
Jan 06 23:52:51 cerberus gsd-power[3176]: Error setting property 
'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was 
reached (g-io-error-quark, 24)
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: 
assertion 'parser' failed
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: 
assertion 'parser' failed
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: 
assertion 'parser' failed
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
Jan 06 23:52:51 cerberus gnome-shell[2987]: cr_declaration_parse_list_from_buf: 
assertion 'parser' failed
Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >
Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >
Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >
Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >
Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.2990" (uid=1000 pid=2987 comm="/usr/bin/gnome-shell " 
label="unconfined") has been >

...

Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager 
--no-daemon " label="unconfined")>
Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager 
--no-daemon " label="unconfined")>
Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager 
--no-daemon " label="unconfined")>
Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager 
--no-daemon " label="unconfined")>
Jan 06 23:52:52 cerberus gnome-shell[2987]: Error checking authorization for 
action id org.freedesktop.bolt.enroll: 
GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: The maximum>
Jan 06 23:52:52 cerberus gnome-shell[2987]: Error checking authorization for 
action id org.freedesktop.packagekit.trigger-offline-update: 
GDBus.Error:org.freedesktop.DBus.Error.Limit>
Jan 06 23:52:52 cerberus dbus-daemon[1439]: [system] The maximum number of 
pending replies for ":1.7" (uid=0 pid=1440 comm="/usr/sbin/NetworkManager 
--no-daemon " label="unconfined")>

...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  7 00:00:52 2022
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-29 (587 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190

[Desktop-packages] [Bug 1950026] Re: gnome-shell leaks mem, 1.3G reserved after few days of uptime

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell leaks mem, 1.3G reserved after few days of uptime

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  gnome-shell leaks memory like crazy. after 4 days of uptime it uses
  13.8G virt and 1.3G reserved mem. This is after I switched to wayland
  to mitigate the same issue, but on X.org it was much more crazier -
  about 20G virt / 1.5G reserved after one-two days of uptime, only the
  leak was in X.org process (2 of them, greeter and main), not gnome-
  shell.

  
  p.s. I do understand that gnome is the best piece of software, and I just use 
it incorrectly - likely I have some extension or application that is at fault. 
The bug report is sort of rhetorical.

  p.p.s. Unmodified LTS system (focal). Started to manifest about a
  month ago, out of the blue, no changes...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sat Nov  6 01:50:41 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  monitors.xml: Error: path contained symlinks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950026/+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 1806385]

[Qa-admin-q]

Dear Rüdiger Kupper,

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

Title:
  [upstream] Creating a new slide by double click not working correctly

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

Bug description:
  Version: 6.1.3.2
  Build-ID: libreoffice-6.1.3.2-snap1

  You can create new slides in impress by double clicking on the empty
  part of the slides pane (below the existing slide). However, this
  works only as expected while the slides pane actually has empty space
  at the bottom.

  As soon as I have created a few slides, the slides pane is completely
  filled, and two things happen:

  (1) Improvement: It is very hard to double click on the thin white
  space at the bottom of the filled slides pane. This could be improved
  by always letting a few pixels at the bottom to click on.

  (2) Bug: You can actually manage to double click there and this
  creates a new slide. However, this new slide is not filed at the end
  of slides (as it should) but appears at a strange location somewhere
  in the middle of slides. This is definitely wrong.

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

[Aaron Wolf]

The shift+click workaround does NOT work for me when using the normal
interface with the curvy-arrow "reply" buttons. No matter what I do, the
account default for HTML or plain stays.

I figured out that the shift+click works ONLY if I choose "reply" from a
menu, either the "Message" menu or from contextual menu with a right-
click.

Seems absurd that the functionality is clearly present but the UI has
nearly no way to access it in a straightforward sense.

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

Title:
  Stuck in proportional font mode

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  If you start a message in HTML mode, choosing Options->Format->Plain Text Only
  switches to plain text mode but the compose window does not switch to a
  monospace font. Starting a message in plain text mode uses the correct font.

  https://bugzilla.mozilla.org/show_bug.cgi?id=216132:
  https://bugzilla.mozilla.org/show_bug.cgi?id=216132

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/10883/+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 1713021] Re: Minimize/unminimize animations do nothing for the first 100ms or so

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-42.0 fixed-upstream

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

Title:
  Minimize/unminimize animations do nothing for the first 100ms or so

Status in GNOME Shell:
  Expired
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  gnome-shell's minimize/unminimize animations do nothing for almost the
  first 100ms or so. They look slow because the easeInExpo curve does
  nothing for most of the first half of the animation time:

  https://gitlab.gnome.org/GNOME/clutter/-/blob/master/doc/reference/easing-
  modes.svg

  A much more responsive, natural and fluid curve with the same overall
  duration would be to use an easeOut* curve.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1713021/+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 1874262] Re: User session does not start: Problem with chrome-remote-desktop

[Daniel van Vugt]

The above fix was released in gdm3 3.37.1

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

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

Title:
  User session does not start: Problem with chrome-remote-desktop

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14
  https://gitlab.gnome.org/GNOME/gdm/-/issues/593

  ---

  Today I tried to log into my ubuntu session with my personal account
  through Xorg and Xwayland. And I couldn't, I had to install lightdm
  and to be able to enter.

  In my experience, I found this message ($journalctl):
  Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
  Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not 
fatal to the X server

  Attached log of the attempt to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.6.6-050606-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 09:54:26 2020
  InstallationDate: Installed on 2018-12-02 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1874262/+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 1934579] Re: Nautilus crashes when opening places from the dock contextmenu

[chiamin]

Same problem

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

Title:
  Nautilus crashes when opening places from the dock contextmenu

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+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 1956603] Re: /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym .....

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => libx11 (Ubuntu)

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in libx11 package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   Intel Corporation GeminiLake [UHD Graphics 600] [8086:3185] (rev 03) 
(prog-if 00 

[Desktop-packages] [Bug 1956126] Re: xorg metapackage depends on x11-apps and xorg-docs-core

[Daniel van Vugt]

** Changed in: xorg (Ubuntu)
   Status: Opinion => Triaged

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

Title:
  xorg metapackage depends on x11-apps and xorg-docs-core

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  xorg, a required dependency of ubuntu-desktop and ubuntu-desktop-
  minimal requires the package x11-apps. Currently Ubuntu 22.04 Jammy
  defaults to Wayland. These applications are ancient and now most
  people won't even be using X11, much less these example applications.
  Why are x11-apps going to be required in April of 2022?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956126/+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 1956119] Re: gnome-shell requires the gir1.2-gweather-3.0 dependency without gweather

[Daniel van Vugt]

/usr/share/glib-2.0/schemas/org.gnome.GWeather.gschema.xml

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

Title:
  gnome-shell requires the gir1.2-gweather-3.0 dependency without
  gweather

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  On a minimal installation where gweather is not installed, gnome-shell
  requires gir1.2-gweather-3.0. This required dependency pulls in
  libgweather-3-16 which then requires libgweather-common.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956119/+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 1876641] Re: gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is enabled.

[Daniel van Vugt]

'show-trash' is enabled by default and we're still getting reports of
the leak in impish so I think this bug should be queued.

** Tags added: impish

** Tags added: rls-ff-incoming

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

Title:
  gnome-shell leaks hundreds of megabytes when the dock option 'show-
  trash' is enabled.

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

Bug description:
  Gnome shell is the single largest resident memory user on my system.

  It was hovering at ~700mb, then with a few minutes of use of the
  system (nothing in particular, mostly shell windows, one google-chrome
  window) - spiked to ~980mb or so, before retreating to 903m.

  Even with 16gb of ram, that's a huge chunk of the system.

  I've not been able to identify anything in particular that I'm doing
  that triggers the growth.

  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1856838/comments/5, it was suggested to open a new bug,
  instead of adding to one of the several existing bugs for this.  I'm
  happy to help try and debug this, but it's not clear where to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 17:32:52 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-18 (532 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-18 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1876641/+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 1955384] Re: Shell stops responding to input after desktop-icons rubber band

[Daniel van Vugt]

** Bug watch added: 
gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #245
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/245

** Also affects: gnome-shell-extension-desktop-icons via
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/245
   Importance: Unknown
   Status: Unknown

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

Title:
  Shell stops responding to input after desktop-icons rubber band

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  This bug happened when I clicked and held the left mouse button on the
  desktop and moved it to make a rectangular selection window. Next, I
  moved the window to highlight 4 desktop shortcuts on my desktop
  (Middle-earth Shadow of Mordor.desktop, steam.desktop, Trash, and the
  icelancet or Home folder). Next, while still holding the left mouse
  button down, I pressed and released the right mouse button. Now a
  window pops up with more options, however, the window is not removable
  using a normal method like clicking somewhere else on the desktop or
  even choosing an option in the window which does nothing. Also, it
  introduces more bugs like: 1. clicking the icelancet/Home shortcut on
  the desktop does not open the Home folder, or 2. while clicking the
  Home folder shortcut on the sidebar does open the Home folder, this
  window is not moveable by the usual method of pressing down the left
  mouse button on the title bar of the window and moving the mouse. As
  such, when this bug occurs, a hard reboot is necessary to restore the
  stability of the system. I have reproduced the bug after a reboot and
  doing the same procedure - the same thing happens. This is on the
  latest version of Ubuntu (Release 20.04) with all the latest upstream
  updates installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.94  Mon Dec  6 22:42:02 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 20 00:46:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:862a]
  InstallationDate: Installed on 2021-11-23 (27 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Micro-Star International Co., Ltd. MS-7C39
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic 
root=UUID=d206716a-6a84-411d-9038-eb4654efc2ec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: B365M PRO-VDH(MS-7C39)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd09/05/2019:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C39:pvr1.0:skuDefaultstring:rvnMicro-StarInternationalCo.,Ltd.:rnB365MPRO-VDH(MS-7C39):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7C39
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl

[Desktop-packages] [Bug 1955058] Re: gnome-shell memory use climbs to multiple GBs

[Daniel van Vugt]

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

Thanks, we can merge this with bug 1876641 then.

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

** This bug has been marked a duplicate of bug 1876641
   gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is 
enabled.

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

Title:
  gnome-shell memory use climbs to multiple GBs

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

Bug description:
  Gnome Shell memory use grows over time

  Memory for Gnome Shell can be around 2.5 GB, sometimes more. If I do
  Alt-F2 r to restart shell, it drops to 250 MB and then slowly climbs
  up again.

  Occasionally it goes so high on my 16 GB machine that it swaps and
  crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 16 16:53:53 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-03 (1565 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-16 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1955058/+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 1956637] [NEW] I have disabled the touchpad through settings, but that has no effect

[Poldi]

Public bug reported:

I'm running Ubuntu 21.10 on a laptop

Ubuntu-settings is V 21.10.4

Disabling the touchpad on my new laptop has no effect.

The only way to disable the touchpad was to install Touchpad-indicator

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: ubuntu-settings 21.10.4
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
Uname: Linux 5.13.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan  7 12:05:10 2022
InstallationDate: Installed on 2021-12-31 (6 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-settings
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

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

Title:
  I have disabled the touchpad through settings, but that has no effect

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 21.10 on a laptop

  Ubuntu-settings is V 21.10.4

  Disabling the touchpad on my new laptop has no effect.

  The only way to disable the touchpad was to install Touchpad-indicator

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: ubuntu-settings 21.10.4
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  7 12:05:10 2022
  InstallationDate: Installed on 2021-12-31 (6 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Desktop-packages] [Bug 1888238] Re: Ubuntu 20.04 simple-scan brightness and contrast controls have no effect

[tkbuntu]

Hi Martin,
thank you for sharing your exxperience.  Seems you had a more difficult time 
than Swissz, but found a solution.
I will test on a non prodduction 20.04 and see how it goes.
Regards

On Thursday, January 6, 2022, 08:16:01 AM CST, Martin Sorgatz 
<1888...@bugs.launchpad.net> wrote:  
 
 I have an old computer with Ubuntu 18.04 LTS where simple scan works fine with 
an HP Envy printer/scanner.
Now I got a new computer and installed 20.04 LTS where the simple scan shows 
this issue with the same scanner.

The downgrade of libsane-genesys.so from 1.0.29 to 1.0.27 (I took it from the 
old computer) does not help on 20.04.
Maybe there are some more bugs in libsane that are already fixed in Ubuntu 
21.04?
So I copied the complete /usr/lib/x86_64-linux-gnu/sane/ directory from 18.04. 
to the 20.04 installation as "sane-old", including the libsane.so.1.0.27 from 
the directory level above.
I created a shell script that starts simple-scan with 
LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/sane-old.
But it did not work. I checked the process which libs are loaded (using sudo 
pldd ).
It loaded mostly the libs from sane-old, but there were still two of the 
original libs:
.../sane/libsane-ricoh2.so.1
.../sane/libsane-escl.so.1

Then (in /usr/lib/x86_64-linux-gnu) I renamed the "sane" directory to 
"sane-hidden".
Now (without LD_LIBRARY_PATH) no more original lib from the original 
subdirectory is used any more (except the top level libsane.so.1 from 1.0.29).
=> Now brightness and contrast can be applied as expected!

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1888238

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc547d11-1deb-404b-988a-a88d4772e66d ro quiet splash vt.handoff=7
  SimpleScanLog:
  
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.32
  dmi.board.name: 17A7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.32
  dmi.chassis.asset.tag: 8022456
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.32:bd12/05/2012:svnHewlett-Packard:pnHPEliteBook8570p:pvrA1029D1102:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8570p
  dmi.product.sku: D2C13UP#ABA
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1888238/+subscriptions

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

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20

Re: [Desktop-packages] [Bug 1871011] Re: USB scanning and printing broken on focal by ippusbxd (was: hpmud and ippusbxd conflict)

[Robert Dinse]

Ok, well I do not understand, I just know my HP printer stopped working
when I upgraded to 21.04, and installing hplip from HP directly made it work
again.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Thu, 6 Jan 2022, Michel-Ekimia wrote:

> Date: Thu, 06 Jan 2022 08:13:20 -
> From: Michel-Ekimia <1871...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1871011] Re: USB scanning and printing broken on focal by
> ippusbxd (was: hpmud and ippusbxd conflict)
> 
> @Robert : you misunderstood , the problem is not the version of the
> HPLIP , but the conflict with ippusbxd on USB device claiming.
>
> Auto configure usb printers is nice but we can live on 20.04 without it.
>
> -- 
> You received this bug notification because you are subscribed to a
> duplicate bug report (1873748).
> https://bugs.launchpad.net/bugs/1871011
>
> Title:
>  USB scanning and printing broken on focal by ippusbxd (was: hpmud and
>  ippusbxd conflict)
>
> Status in HPLIP:
>  Invalid
> Status in hplip package in Ubuntu:
>  Expired
> Status in ippusbxd package in Ubuntu:
>  Confirmed
>
> Bug description:
>  SOLUTION : sudo apt remove ippusbxd
>
>   Initial report -
>
>  On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3.
>
>  Previously there was a libmtp (udev) bug erroneously detecting HP
>  printers as mtp devices. This was fixed. Now, I can try to scan-- from
>  both simple-scan and hp-scan, hplip errors out:
>
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
> interface conf=0, iface=1, altset=0, index=1
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
> kernel driver on interface=1 ret=0
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
> claim_interface 7/1/2: Device or resource busy
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
> interface conf=0, iface=0, altset=1, index=3
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
> kernel driver on interface=0 ret=0
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
> claim_interface 7/1/4: Device or resource busy
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
> interface conf=0, iface=3, altset=0, index=9
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
> kernel driver on interface=3 ret=0
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
> claim_interface ff/4/1: Device or resource busy
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
> interface conf=0, iface=0, altset=0, index=11
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
> kernel driver on interface=0 ret=0
>  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
> claim_interface ff/cc/0: Device or resource busy
>
>  Printer/scanner is an Officejet 4635. Scanning previously worked just
>  fine a few months ago. Regression?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions
>

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

Title:
  USB scanning and printing broken on focal by ippusbxd (was: hpmud and
  ippusbxd conflict)

Status in HPLIP:
  Invalid
Status in hplip package in Ubuntu:
  Expired
Status in ippusbxd package in Ubuntu:
  Confirmed

Bug description:
  SOLUTION : sudo apt remove ippusbxd

   Initial report -

  On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3.

  Previously there was a libmtp (udev) bug erroneously detecting HP
  printers as mtp devices. This was fixed. Now, I can try to scan-- from
  both simple-scan and hp-scan, hplip errors out:

  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
interface conf=0, iface=1, altset=0, index=1
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
kernel driver on interface=1 ret=0
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
claim_interface 7/1/2: Device or resource busy
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
interface conf=0, iface=0, altset=1, index=3
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
kernel driver on interface=0 ret=0
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
claim_interface 7/1/4: Device or resource busy
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
interface conf=0, iface=3, altset=0, index=9
  Apr 05 21:27:37 d

Re: [Desktop-packages] [Bug 1888238] Re: Ubuntu 20.04 simple-scan brightness and contrast controls have no effect

[tkbuntu]

Thank you for the information!
I will try this.
Kind Regards


   On Tuesday, January 4, 2022, 10:15:47 AM CST, swissz 
<1888...@bugs.launchpad.net> wrote:  
 
 I have found a workaround that kind of works ... The problem is with the
sane library, so it has to be downgraded. I restored
/usr/lib/x86_64-linux-gnu/sane/libsane-genesys.so.1.0.27 from my
previous Ubuntu 18.04 installation and linked it instead of the current
version, and that's all, it works for me in Ubuntu 21.10.

# ls -l /usr/lib/x86_64-linux-gnu/sane/libsane-genesys.so.1
lrwxrwxrwx 1 root root 25 Dez 10 22:52 
/usr/lib/x86_64-linux-gnu/sane/libsane-genesys.so.1 -> libsane-genesys.so.1.0.32

# cd /usr/lib/x86_64-linux-gnu/sane
# ln -fs libsane-genesys.so.1.0.27 libsane-genesys.so.1
# ls -l libsane-genesys.so*
lrwxrwxrwx 1 root root      25 Jan  4 16:56 libsane-genesys.so.1 -> 
libsane-genesys.so.1.0.27

You can try to download the libsane-genesys.so.1.0.27 from here
https://ubuntu.pkgs.org/18.04/ubuntu-main-
amd64/libsane1_1.0.27-1~experimental3ubuntu2_amd64.deb.html

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1888238

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=en_US.UTF-8
  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc547d11-1deb-404b-988a-a88d4772e66d ro quiet splash vt.handoff=7
  SimpleScanLog:
  
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.32
  dmi.board.name: 17A7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.32
  dmi.chassis.asset.tag: 8022456
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.32:bd12/05/2012:svnHewlett-Packard:pnHPEliteBook8570p:pvrA1029D1102:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8570p
  dmi.product.sku: D2C13UP#ABA
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1888238/+subscriptions

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

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc547d11-1deb-404b-988a-a88d4772e66d ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
 

[Desktop-packages] [Bug 1927100] Re: Slow file dialogs, open and save

[buck2202]

I've seen the same issue reported in gnome trackers under
Nautilus+Fedora and Thunar+Arch, so I'm fairly sure it's not a Mint-
specific bug (though those are obviously not Ubuntu-based).

The original report here was for Ubuntu Mate...that's "direct" Ubuntu,
right? If there's anyone out there, I'd be happy to write a script for
verification

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

Title:
  Slow file dialogs, open and save

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Focal:
  Incomplete

Bug description:
  [Description/Impact]
  glib GFileMonitors can cause deadlocks if not explicitly cancelled before 
unref-ing (as of Dec 2021; see 
https://gitlab.gnome.org/GNOME/glib/-/issues/1941). In gvfs <1.46.2, 
gvfsd-trash can cause this deadlock, leading to 25s delays in spawning gtk+ 
dialogs system-wide. The best userspace workaround is explicitly pkill-ing 
gvfsd-trash at a sometimes frequent interval.

  This issue was reported and fixed in gvfs
  issue: https://gitlab.gnome.org/GNOME/gvfs/-/issues/485
  commit: 
https://gitlab.gnome.org/GNOME/gvfs/-/commit/dc21a0948bcbe8a6d79d674bd1e4d63ded57d340
  merge: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96

  [Test Case]
  To my knowledge, there is not a 100% reproducer for gvfs from userspace as 
this is a probable lock-ordering issue in lower-level code. 
https://gitlab.gnome.org/GNOME/glib/-/issues/1941 contains a reproducer for the 
underlying glib issue.

  User reports of gvfsd-trash manifesting this deadlock exist for Focal and 
Focal-based distributions, and it has been acknowledged and worked-around in 
gvfs. See:
  https://forums.linuxmint.com/viewtopic.php?f=47&t=328966 (Linux Mint forums)
  https://github.com/linuxmint/nemo/issues/2497 (Linux Mint nemo -- file 
manager)
  https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 (gvfs bug report, includes 
diagnosis and stacktrace showing the gvfsd-trash thread)

  The code change patched-in here has propagated to various other projects. See:
  https://bugs.launchpad.net/ubuntu/+source/libxmlb/+bug/1890313
  https://github.com/fwupd/fwupd/issues/2350

  [Regression Potential]
  This patch explicitly cancels GFileMonitors before "unreferencing" them to 
workaround a known glib issue. Absent any currently-unknown issues with the 
GFileMonitor framework, code added by this patch should be entirely within 
valid usage of GFileMonitors, is already present in gvfs releases in wide 
distribution, and, at worst, should become superfluous if/when the underlying 
glib issue is fixed.

  In the event that gvfsd-trash had some (currently unknown)
  mismanagement of its file watchers, it's possible that attempting to
  cancel an invalid monitor might behave differently than unref-ing it
  (which was already happening), but, this scenario would likely be bad
  either way.

  [Original Description]

  On Ubuntu Mate 20.04.

  Sometime the Open and Save dialogs in GTK applications will over 20
  seconds to display.

  I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which
  suggested this due to gvfsd-trash, and running `killall gvfsd-trash`
  which does temporary solve the problem.

  The issue is apparently fixed in gvfs 1.46.2

  Please could 1.46.2 or the fix
  https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported
  to Ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+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 1955058] Re: gnome-shell memory use climbs to multiple GBs

[sammy247]

Seems to be this!

https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/+bug/1876641/comments/29

gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false

reboot after uninstalling trash can:

11.33 239 MB
12.19 258 MB
15.12 385 MB
17.07 388 MB
21.53 346 MB

prior to deleting the trash can from the dock, the memory use rose to >3
GB over the same period.

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

Title:
  gnome-shell memory use climbs to multiple GBs

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome Shell memory use grows over time

  Memory for Gnome Shell can be around 2.5 GB, sometimes more. If I do
  Alt-F2 r to restart shell, it drops to 250 MB and then slowly climbs
  up again.

  Occasionally it goes so high on my 16 GB machine that it swaps and
  crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 16 16:53:53 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-03 (1565 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-16 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955058/+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 1927100] Re: Slow file dialogs, open and save

[Robie Basak]

> I guess the goal there would just be to say the issue occurred X times
in Y hours on 1.44.1-1ubuntu1, and zero times in Z hours on -proposed.

I think something like that would be fine, yes.

I'm not sure about using Mint for the test though. Are there any direct
users of Ubuntu who could test in this fashion? If no direct Ubuntu
users appear to be affected, then the race could be manifesting due to
some difference in Mint, at which point there'd be limited benefit for
the regression risk cost of making a change for direct Ubuntu users in a
stable release. But if direct Ubuntu users _are_ affected, then I would
expect at least one of them to be able to step up and help us test.

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

Title:
  Slow file dialogs, open and save

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Focal:
  Incomplete

Bug description:
  [Description/Impact]
  glib GFileMonitors can cause deadlocks if not explicitly cancelled before 
unref-ing (as of Dec 2021; see 
https://gitlab.gnome.org/GNOME/glib/-/issues/1941). In gvfs <1.46.2, 
gvfsd-trash can cause this deadlock, leading to 25s delays in spawning gtk+ 
dialogs system-wide. The best userspace workaround is explicitly pkill-ing 
gvfsd-trash at a sometimes frequent interval.

  This issue was reported and fixed in gvfs
  issue: https://gitlab.gnome.org/GNOME/gvfs/-/issues/485
  commit: 
https://gitlab.gnome.org/GNOME/gvfs/-/commit/dc21a0948bcbe8a6d79d674bd1e4d63ded57d340
  merge: https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96

  [Test Case]
  To my knowledge, there is not a 100% reproducer for gvfs from userspace as 
this is a probable lock-ordering issue in lower-level code. 
https://gitlab.gnome.org/GNOME/glib/-/issues/1941 contains a reproducer for the 
underlying glib issue.

  User reports of gvfsd-trash manifesting this deadlock exist for Focal and 
Focal-based distributions, and it has been acknowledged and worked-around in 
gvfs. See:
  https://forums.linuxmint.com/viewtopic.php?f=47&t=328966 (Linux Mint forums)
  https://github.com/linuxmint/nemo/issues/2497 (Linux Mint nemo -- file 
manager)
  https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 (gvfs bug report, includes 
diagnosis and stacktrace showing the gvfsd-trash thread)

  The code change patched-in here has propagated to various other projects. See:
  https://bugs.launchpad.net/ubuntu/+source/libxmlb/+bug/1890313
  https://github.com/fwupd/fwupd/issues/2350

  [Regression Potential]
  This patch explicitly cancels GFileMonitors before "unreferencing" them to 
workaround a known glib issue. Absent any currently-unknown issues with the 
GFileMonitor framework, code added by this patch should be entirely within 
valid usage of GFileMonitors, is already present in gvfs releases in wide 
distribution, and, at worst, should become superfluous if/when the underlying 
glib issue is fixed.

  In the event that gvfsd-trash had some (currently unknown)
  mismanagement of its file watchers, it's possible that attempting to
  cancel an invalid monitor might behave differently than unref-ing it
  (which was already happening), but, this scenario would likely be bad
  either way.

  [Original Description]

  On Ubuntu Mate 20.04.

  Sometime the Open and Save dialogs in GTK applications will over 20
  seconds to display.

  I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which
  suggested this due to gvfsd-trash, and running `killall gvfsd-trash`
  which does temporary solve the problem.

  The issue is apparently fixed in gvfs 1.46.2

  Please could 1.46.2 or the fix
  https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported
  to Ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+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 1956612] [NEW] Play in this way

[Smith]

Public bug reported:

how to play DOS/Windows executable (application/x-ms-dos-executable)
Firstly, it's also a requirement that you must have pc or phone to play it!
For more Info: https://apkmortgage.com/disney-magic-kingdom-mod-apk-1/

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

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

Title:
  Play in this way

Status in nautilus package in Ubuntu:
  New

Bug description:
  how to play DOS/Windows executable (application/x-ms-dos-executable)
  Firstly, it's also a requirement that you must have pc or phone to play it!
  For more Info: https://apkmortgage.com/disney-magic-kingdom-mod-apk-1/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1956612/+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 1956414] Re: gnome-control-center crashed with "SIGFPE in g_hash_table_remove()" while setting up a printer

[Gunnar Hjalmarsson]

** Information type changed from Private to Public

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

Title:
  gnome-control-center crashed with "SIGFPE in g_hash_table_remove()"
  while setting up a printer

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I went to the Settings to set up my printer. When I wanted to specify
  the model via the "Select from Database" button, the GNOME Control
  Center crashed. I accidentally clicked "Search for Drivers" before.

  Information about versions:
  jerry@B450-AORUS-ELITE:~$ lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  jerry@B450-AORUS-ELITE:~$ apt-cache policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  jerry@B450-AORUS-ELITE:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  5 06:17:16 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-01-05 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220104)
  ProcCmdline: gnome-control-center
  Signal: 8
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_hash_table_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_type_info_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGFPE in g_hash_table_remove()
  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-control-center/+bug/1956414/+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 1955058] Re: gnome-shell memory use climbs to multiple GBs

[sammy247]

Seems to be this!

https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/+bug/1876641/comments/29

gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false

reboot after uninstalling trash can:

11.33 239 MB
12.19 258 MB
15.12 385 MB
17.07 388 MB

prior to deleting the trash can from the dock, the memory use rose to ~3
GB over the same period.

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

Title:
  gnome-shell memory use climbs to multiple GBs

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome Shell memory use grows over time

  Memory for Gnome Shell can be around 2.5 GB, sometimes more. If I do
  Alt-F2 r to restart shell, it drops to 250 MB and then slowly climbs
  up again.

  Occasionally it goes so high on my 16 GB machine that it swaps and
  crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 16 16:53:53 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-03 (1565 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-16 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955058/+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 1956603] XorgLog.txt

[madigal]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552212/+files/XorgLog.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   I

[Desktop-packages] [Bug 1956603] UdevDb.txt

[madigal]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1956603/+attachment/5552211/+files/UdevDb.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   Inte

[Desktop-packages] [Bug 1956603] XorgLogOld.txt

[madigal]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552213/+files/XorgLogOld.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard

[Desktop-packages] [Bug 1956603] xdpyinfo.txt

[madigal]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552216/+files/xdpyinfo.txt

** Summary changed:

- /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym
+ /usr/libexec/gdm-x-session: > Internal error:   Could not resolve keysym .

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! D

[Desktop-packages] [Bug 1956603] Xrandr.txt

[madigal]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1956603/+attachment/5552214/+files/Xrandr.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   Inte

[Desktop-packages] [Bug 1956603] acpidump.txt

[madigal]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552215/+files/acpidump.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
  

[Desktop-packages] [Bug 1956603] ProcCpuinfoMinimal.txt

[madigal]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552208/+files/ProcCpuinfoMinimal.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!

[Desktop-packages] [Bug 1956603] ProcModules.txt

[madigal]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552210/+files/ProcModules.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCa

[Desktop-packages] [Bug 1956603] ProcInterrupts.txt

[madigal]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552209/+files/ProcInterrupts.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  Grap

[Desktop-packages] [Bug 1956603] ProcCpuinfo.txt

[madigal]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552207/+files/ProcCpuinfo.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCa

[Desktop-packages] [Bug 1956603] Lsusb-t.txt

[madigal]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552205/+files/Lsusb-t.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   I

[Desktop-packages] [Bug 1956603] Lsusb.txt

[madigal]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1956603/+attachment/5552204/+files/Lsusb.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   Intel 

[Desktop-packages] [Bug 1956603] Lsusb-v.txt

[madigal]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552206/+files/Lsusb-v.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   I

[Desktop-packages] [Bug 1956603] Lspci.txt

[madigal]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1956603/+attachment/5552202/+files/Lspci.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   Intel 

[Desktop-packages] [Bug 1956603] Lspci-vt.txt

[madigal]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552203/+files/Lspci-vt.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
  

[Desktop-packages] [Bug 1956603] DpkgLog.txt

[madigal]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552201/+files/DpkgLog.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  GraphicsCard:
   I

[Desktop-packages] [Bug 1956603] Dependencies.txt

[madigal]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552200/+files/Dependencies.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  Graphics

[Desktop-packages] [Bug 1956603] Re: /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym

[madigal]

Libx11 is missing some code, and has been fixed with the 1.7.3 version,
then 1.7.3.1 due to packaging issue.

https://lists.x.org/archives/xorg-announce/2021-December/003120.html
https://lists.x.org/archives/xorg-announce/2021-December/003121.html

As of today i have not tested the result, but dev claims it fix that
problem.

Please package that version and upload it to Jammy repo.

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkm

[Desktop-packages] [Bug 1956603] Re: /usr/libexec/gdm-x-session[2536]: > Internal error: Could not resolve keysym

[madigal]

Other fix : https://lists.x.org/archives/xorg-
announce/2021-December/003122.html

** Tags added: apport-collected has-fix jammy reproducible ubuntu

** Description changed:

  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2
  
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu75
+ Architecture: amd64
+ BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
+ CasperMD5CheckResult: unknown
+ CompositorRunning: None
+ CurrentDesktop: MATE
+ DistUpgraded: Fresh install
+ DistroCodename: jammy
+ DistroRelease: Ubuntu 22.04
+ DistroVariant: ubuntu
+ DkmsStatus:
+  fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
+  fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
+  fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
+ GraphicsCard:
+  Intel Corporation GeminiLake [UHD Graphics 600] [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
+Subsystem: Intel Corporation GeminiLake [UHD Graphics 600] [8086:2212]
+ MachineType: To be filled by O.E.M. To be filled by O.E.M.
+ Package: xorg 1:7.7+23ubuntu1
+ Packag

[Desktop-packages] [Bug 1956603] CurrentDmesg.txt

[madigal]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1956603/+attachment/5552199/+files/CurrentDmesg.txt

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

Title:
  /usr/libexec/gdm-x-session: > Internal error:   Could not resolve
  keysym .

Status in xorg package in Ubuntu:
  New

Bug description:
  Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
  Actual libx11 is 1.7.2

  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86MediaRepeat
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF8610ChannelsDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Images
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NotificationCenter
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86PickupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86HangupPhone
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Fn_Esc
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86FnRightShift
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric0
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric1
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric2
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric3
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric4
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric5
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric6
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric7
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric8
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86Numeric9
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericStar
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericPound
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericA
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericB
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericC
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86NumericD
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraFocus
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86WPSButton
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomIn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraZoomOut
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraUp
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraDown
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraLeft
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86CameraRight
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOn
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantOff
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86AttendantToggle
  /usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve 
keysym XF86LightsToggle
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  Graphics

[Desktop-packages] [Bug 1956603] [NEW] /usr/libexec/gdm-x-session: > Internal error: Could not resolve keysym .....

[madigal]

Public bug reported:

Get lot of such warnings into Jammy logged; this makes freezes and browser 
crashes.
Actual libx11 is 1.7.2

/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86MediaRepeat
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF8610ChannelsUp
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF8610ChannelsDown
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Images
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86NotificationCenter
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86PickupPhone
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86HangupPhone
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Fn
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Fn_Esc
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86FnRightShift
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric0
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric1
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric2
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric3
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric4
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric5
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric6
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric7
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric8
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86Numeric9
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86NumericStar
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86NumericPound
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86NumericA
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86NumericB
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86NumericC
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86NumericD
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86CameraFocus
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86WPSButton
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86CameraZoomIn
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86CameraZoomOut
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86CameraUp
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86CameraDown
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86CameraLeft
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86CameraRight
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86AttendantOn
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86AttendantOff
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86AttendantToggle
/usr/libexec/gdm-x-session[2536]: > Internal error:   Could not resolve keysym 
XF86LightsToggle
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: MATE
DistUpgraded: Fresh install
DistroCodename: jammy
DistroRelease: Ubuntu 22.04
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms/21.12.00, 5.15.0-13-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
 fwts-efi-runtime-dkms/21.12.00, 5.15.0-14-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
 fwts-efi-runtime-dkms/21.12.00, 5.15.0-15-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
GraphicsCard:
 Intel Corporation GeminiLake [UHD Graphics 600] [8086:3185] (rev 03) (prog-if 
00 [VGA controller])
   Subsystem: Intel Corporation GeminiLake [UHD Graphics 600] [8086:2212]
MachineType: To be filled by O.E.M. To be filled by O.E.M.
Package: xorg 1:7.7+23ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-15-generic 
root=UUID=d825b0db-c259-4e90-ba12-5f35be939013 ro
ProcVersionSignature: Ubuntu 5.15.

[Desktop-packages] [Bug 1956126] Re: xorg metapackage depends on x11-apps and xorg-docs-core

[wontfix]

>More likely that the two dependencies this bug is about would be cut as
you request, or that nothing will change at all.

I'm  not requesting they be cut. I'm not sure why you keep saying that
when it just isn't true. I'm requesting they change to recommends. If
Ubuntu sees fit to not include recommends for certain packages on the
minimal install to hit certain targets or for users pulling in
metapackages with --no-install-recommends, that obviously isn't up to
me. Giving the user choice does not mean they aren't by default,
installed.

>But I also imagine nobody will ever bother with those because it's not
actually important.

Go look at size reduction over the years from bug reports due to
individual files, kernel drivers, and pulled in packages that weren't
actual depends. It wasn't so long ago this was done on purpose for
Ubuntu server and snap purposes in a very open way. Every single time
you can keep disk and RAM requirements the same LTS over LTS, that is a
win for everyone due to the vast array of devices and service packages
that Ubuntu runs on across countless industries. Every single package
not downloaded, that wasn't needed, is energy and paid bandwidth saved.

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

Title:
  xorg metapackage depends on x11-apps and xorg-docs-core

Status in xorg package in Ubuntu:
  Opinion

Bug description:
  xorg, a required dependency of ubuntu-desktop and ubuntu-desktop-
  minimal requires the package x11-apps. Currently Ubuntu 22.04 Jammy
  defaults to Wayland. These applications are ancient and now most
  people won't even be using X11, much less these example applications.
  Why are x11-apps going to be required in April of 2022?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956126/+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 1956128] Re: xserver-xorg-video-all requires xserver-xorg-video-ati

[wontfix]

> If it were up to me then the rule would be whether OpenGL is supported
in the associated Mesa and kernel drivers

Until recently, QEMU/QXL would have been without display drivers by your
standard, including LTS releases that will be supported for quite some
time still. Given the default targets including new Pis as they come
out, that standard would remove entire targets from Ubuntu's purview
that are works in progress. Given that Vulkan is becoming a common
backend and LLVMPipe exists, how does OpenGL of an unlisted version even
make sense? This standard also has changed since you originally said a
year based range and subsequently modified it when I posted the actual
dates relating to new products and sale ranges.


> xserver-xorg-video-all is a metapackage

Metapackages have both depends and recommends all the time. That is the
norm. Both the Intel and QXL X11 packages are recommends of xserver-
xorg-video-all, not required dependencies. In fact, even xorg has a
recommended package for scalable x fonts.

I am just asking that an old ATI package for a dead company, gets the
same treatment as Intel regarding recommended status even though Intel
is still alive. Intel still gets pulled in by default. Nothing has
changed there. This isn't explicit removal, at all.

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

Title:
  xserver-xorg-video-all requires xserver-xorg-video-ati

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  ATi sold to AMD in 2006. I can remove wacom from input but not ATi
  from video. Are more people running ATi cards in 2022~ than wacom
  input devices? Why is this still a required dependency?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956128/+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 1956119] Re: gnome-shell requires the gir1.2-gweather-3.0 dependency without gweather

[wontfix]

The last dependency in the chain is libgweather-common as noted above.
Can you please point out which specific file is required to run Gnome
shell? It works fine when force removed with dpkg and the schemas seem
to be for weather related features.

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

Title:
  gnome-shell requires the gir1.2-gweather-3.0 dependency without
  gweather

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  On a minimal installation where gweather is not installed, gnome-shell
  requires gir1.2-gweather-3.0. This required dependency pulls in
  libgweather-3-16 which then requires libgweather-common.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956119/+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 1888238] Re: Ubuntu 20.04 simple-scan brightness and contrast controls have no effect

[Martin Sorgatz]

I have an old computer with Ubuntu 18.04 LTS where simple scan works fine with 
an HP Envy printer/scanner.
Now I got a new computer and installed 20.04 LTS where the simple scan shows 
this issue with the same scanner.

The downgrade of libsane-genesys.so from 1.0.29 to 1.0.27 (I took it from the 
old computer) does not help on 20.04.
Maybe there are some more bugs in libsane that are already fixed in Ubuntu 
21.04?
So I copied the complete /usr/lib/x86_64-linux-gnu/sane/ directory from 18.04. 
to the 20.04 installation as "sane-old", including the libsane.so.1.0.27 from 
the directory level above.
I created a shell script that starts simple-scan with 
LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/sane-old.
But it did not work. I checked the process which libs are loaded (using sudo 
pldd ).
It loaded mostly the libs from sane-old, but there were still two of the 
original libs:
.../sane/libsane-ricoh2.so.1
.../sane/libsane-escl.so.1

Then (in /usr/lib/x86_64-linux-gnu) I renamed the "sane" directory to 
"sane-hidden".
Now (without LD_LIBRARY_PATH) no more original lib from the original 
subdirectory is used any more (except the top level libsane.so.1 from 1.0.29).
=> Now brightness and contrast can be applied as expected!

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

Title:
  Ubuntu 20.04 simple-scan brightness and contrast controls have no
  effect

Status in Simple Scan:
  Unknown
Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 simple-scan.  The Brightness and Contrast controls have
  no effect.  No matter how I position the sliders the scan image
  remains the same, ie, a dark background.  It is as if the controls are
  not 'connected'.

  Ubuntu 20.04 is up to date.  The scanner is a Cannon LiDE60.

  I have 19.10 in another partition. Simple-scan works as expected.
  Ditto for 18.04.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 09:47:52 2020
  InstallationDate: Installed on 2020-05-12 (68 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Hewlett-Packard HP EliteBook 8570p
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=dc547d11-1deb-404b-988a-a88d4772e66d ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68ICF Ver. F.32
  dmi.board.name: 17A7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 42.32
  dmi.chassis.asset.tag: 8022456
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.32:bd12/05/2012:svnHewlett-Packard:pnHPEliteBook8570p:pvrA1029D1102:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 8570p
  dmi.product.sku: D2C13UP#ABA
  dmi.product.version: A1029D1102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1888238/+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 1955384] Re: Shell stops responding to input after desktop-icons rubber band

[Marko Drobac]

Ok, will do.

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

Title:
  Shell stops responding to input after desktop-icons rubber band

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  This bug happened when I clicked and held the left mouse button on the
  desktop and moved it to make a rectangular selection window. Next, I
  moved the window to highlight 4 desktop shortcuts on my desktop
  (Middle-earth Shadow of Mordor.desktop, steam.desktop, Trash, and the
  icelancet or Home folder). Next, while still holding the left mouse
  button down, I pressed and released the right mouse button. Now a
  window pops up with more options, however, the window is not removable
  using a normal method like clicking somewhere else on the desktop or
  even choosing an option in the window which does nothing. Also, it
  introduces more bugs like: 1. clicking the icelancet/Home shortcut on
  the desktop does not open the Home folder, or 2. while clicking the
  Home folder shortcut on the sidebar does open the Home folder, this
  window is not moveable by the usual method of pressing down the left
  mouse button on the title bar of the window and moving the mouse. As
  such, when this bug occurs, a hard reboot is necessary to restore the
  stability of the system. I have reproduced the bug after a reboot and
  doing the same procedure - the same thing happens. This is on the
  latest version of Ubuntu (Release 20.04) with all the latest upstream
  updates installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.94  Mon Dec  6 22:42:02 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 20 00:46:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:862a]
  InstallationDate: Installed on 2021-11-23 (27 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Micro-Star International Co., Ltd. MS-7C39
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic 
root=UUID=d206716a-6a84-411d-9038-eb4654efc2ec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: B365M PRO-VDH(MS-7C39)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd09/05/2019:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C39:pvr1.0:skuDefaultstring:rvnMicro-StarInternationalCo.,Ltd.:rnB365MPRO-VDH(MS-7C39):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7C39
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserve

[Desktop-packages] [Bug 1956587] [NEW] Disallowed syscall "mbind" caught in sandbox

[Timo Witte]

Public bug reported:

When the extractor is extracting audio files, it crashes with
"Disallowed syscall "mbind" caught in sandbox".. I reported this in the
gnome issues tracker and it was fixed. We should merge this for jammy,
once the fix is released.

Please see: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/210
and the Fix: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/373

** Affects: tracker-miners (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Disallowed syscall "mbind" caught in sandbox

Status in tracker-miners package in Ubuntu:
  New

Bug description:
  When the extractor is extracting audio files, it crashes with
  "Disallowed syscall "mbind" caught in sandbox".. I reported this in
  the gnome issues tracker and it was fixed. We should merge this for
  jammy, once the fix is released.

  Please see: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/210
  and the Fix: 
https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/373

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1956587/+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 1956581] [NEW] make gtk 3.24.31 available in Ubuntu 21.*

[bluppfisk]

Public bug reported:

A very annoying GTK bug (which breaks copying and pasting, the computer
user's favourite activity) has been fixed in GTK 3.24.31. Unfortunately,
Ubuntu 21.10 is still stuck on 3.24.30. I'd think that making 3.24.31
available wouldn't break much, but would help a lot of us out.

Can this be 'backported' (is this the correct jargon?) or am I better
off upgrading to Jammy Jellyfish even though it's still unstable?

Bug: https://gitlab.gnome.org/GNOME/gtk/-/issues/4340

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  make gtk 3.24.31 available in Ubuntu 21.*

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  A very annoying GTK bug (which breaks copying and pasting, the
  computer user's favourite activity) has been fixed in GTK 3.24.31.
  Unfortunately, Ubuntu 21.10 is still stuck on 3.24.30. I'd think that
  making 3.24.31 available wouldn't break much, but would help a lot of
  us out.

  Can this be 'backported' (is this the correct jargon?) or am I better
  off upgrading to Jammy Jellyfish even though it's still unstable?

  Bug: https://gitlab.gnome.org/GNOME/gtk/-/issues/4340

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1956581/+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 1956365] Re: Firefox snap package can not resolve .local dns names

[Gary Allan]

** Changed in: firefox (Ubuntu)
   Status: New => Invalid

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

Title:
  Firefox snap package can not resolve .local dns names

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Firefox snap package does not resolve .local dns names after recent
  update.

  After a recent snap package update of Firefox I can no longer resolve
  .local DNS names for my local network. This ONLY impacts the Firefox
  snap package. Brave, Chrome and DNS resolution on the local terminal
  (ping) are working correctly.

  When opening https://docker.local developer tools displays the error
  NS_ERROR_UNKNOWN_HOST

  gary@orion:~$ ping docker.local
  PING docker.local (192.168.0.18) 56(84) bytes of data.
  64 bytes from docker.local (192.168.0.18): icmp_seq=1 ttl=64 time=2.37 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=2 ttl=64 time=2.74 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=3 ttl=64 time=2.53 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=4 ttl=64 time=2.46 ms
  64 bytes from docker.local (192.168.0.18): icmp_seq=5 ttl=64 time=2.41 ms

  Running WireShark shows Firefox sending a single SOA DNS request to the local 
DNS server. 
  No DNS requests for the docker.local A record are generated by the Firefox 
snap package.

  563.699461647 192.168.0.101   192.168.0.15DNS 65  
Standard query 0x70f9 SOA local
  573.702560799 192.168.0.15192.168.0.101   DNS 65  
Standard query response 0x70f9 SOA local

  
  I have tested this faulty behavior on multiple machines running Ubuntu 20.04 
and Ubuntu 21.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956365/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Brian Milnes]

Disappointing that this bug is still there in 
20.04.3 LTS
Gnome v. 3.36.8

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1824874/+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 1955058] Re: gnome-shell memory use climbs to multiple GBs

[Daniel van Vugt]

Thanks for checking that.

Next please look at bug 1876641 and bug 1856838 to see if either of
those apply to you. They are the only known leaks we haven't yet checked
for.

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

Title:
  gnome-shell memory use climbs to multiple GBs

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome Shell memory use grows over time

  Memory for Gnome Shell can be around 2.5 GB, sometimes more. If I do
  Alt-F2 r to restart shell, it drops to 250 MB and then slowly climbs
  up again.

  Occasionally it goes so high on my 16 GB machine that it swaps and
  crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 16 16:53:53 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-03 (1565 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-16 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955058/+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 1955058] Re: gnome-shell memory use climbs to multiple GBs

[sammy247]

27;kodi.desktop': <{'position': <5>}>, 
'0c9c6ea8-a25b-4757-841e-b475a3cbfd63': <{'position': <6>}>, 
'8f5a5ea6-02b3-497c-8bc3-c41cb5790b9a': <{'position': <7>}>, 
'menulibre.desktop': <{'position': <8>}>, 
'115aa591-ddd8-4b00-9e59-8245b2ae8334': <{'position': <9>}>, 
'14da8e16-d6b7-4c6d-bdcb-338dcedf8fe5': <{'position': <10>}>, 
'dev.alextren.Spot.desktop': <{'position': <11>}>, 
'dae0aaf1-4f08-4c3c-86af-efd2ba79a28d': <{'position': <12>}>}, {'mpv.desktop': 
<{'position': <0>}>, 'org.gnome.Music.desktop': <{'position': <1>}>, 
'com.nextcloud.desktopclient.nextcloud.desktop': <{'position': <2>}>, 
'nvidia-settings.desktop': <{'position': <3>}>, 
'org.gnome.seahorse.Application.desktop': <{'position': <4>}>, 
'org.gnome.PowerStats.desktop': <{'position': <5>}>, 'pavucontrol.desktop': 
<{'position': <6>}>, 'pymol-oss_pymol-oss.desktop': <{'position': <7>}>, 
'qownnotes_qownnotes.desktop': <{'position': <8>}>, 'rhythmbox.desktop': 
<{'position': <9>}>, 'gnome-control-center.desktop': <{'position': <10>}>, 
'shotwell.desktop': <{'position': <11>}>, 'signal-desktop.desktop': 
<{'position': <12>}>, 'skype_skypeforlinux.desktop': <{'position': <13>}>}, 
{'906a4218-2e08-482b-ba6a-c39aa32e066a': <{'position': <0>}>, 
'soundconverter.desktop': <{'position': <1>}>, 
'b3ebcc95-c87f-431b-aabf-47412a29b547': <{'position': <2>}>, 
'c0b5451e-4281-4c7a-95ca-b98974c7897f': <{'position': <3>}>, 'steam.desktop': 
<{'position': <4>}>, 'Sundry': <{'position': <5>}>, 'supertuxkart.desktop': 
<{'position': <6>}>, 'hardinfo.desktop': <{'position': <7>}>, 
'TaxCalcHub.desktop': <{'position': <8>}>, 'com.teamviewer.TeamViewer.desktop': 
<{'position': <9>}>, 'org.gnome.gedit.desktop': <{'position': <10>}>, 
'thunderbird.desktop': <{'position': <11>}>, 'time.desktop': <{'position': 
<12>}>, 'timeshift-gtk.desktop': <{'position': <13>}>, 
'46c0649b-b105-4678-a0ef-c5b659300c93': <{'position': <14>}>, 
'transmission-gtk.desktop': <{'position': <15>}>, 'org.gnome.tweaks.desktop': 
<{'position': <16>}>}, {'Utilities': <{'position': <0>}>, 'veracrypt.desktop': 
<{'position': <1>}>, 'virtualbox.desktop': <{'position': <2>}>, 'vlc.desktop': 
<{'position': <3>}>, 'wireshark.desktop': <{'position': <4>}>, 
'06500345-0f6b-4621-ac7f-17efd42c49e6': <{'position': <5>}>, 
'y-ppa-manager.desktop': <{'position': <6>}>, 
'zoom-client_zoom-client.desktop': <{'position': <7>}>, 'zotero.desktop': 
<{'position': <8>}>}]
org.gnome.shell had-bluetooth-devices-setup false
org.gnome.shell looking-glass-history @as []
org.gnome.shell enabled-extensions ['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'd...@rastersoft.com']
org.gnome.shell disabled-extensions ['nightshellswitc...@romainvigier.fr', 
'caffe...@patapon.info']
org.gnome.shell development-tools true
org.gnome.shell introspect false
org.gnome.shell remember-mount-password true
org.gnome.shell welcome-dialog-last-shown-version '40.5'
org.gnome.shell.keybindings switch-to-application-4 ['4']
org.gnome.shell.keybindings switch-to-application-7 ['7']
org.gnome.shell.keybindings toggle-message-tray ['v', 'm']
org.gnome.shell.keybindings toggle-application-view ['a']
org.gnome.shell.keybindings focus-active-notification ['n']
org.gnome.shell.keybindings switch-to-application-2 ['2']
org.gnome.shell.keybindings switch-to-application-5 ['5']
org.gnome.shell.keybindings switch-to-application-8 ['8']
org.gnome.shell.keybindings open-application-menu ['F10']
org.gnome.shell.keybindings toggle-overview ['s']
org.gnome.shell.keybindings switch-to-application-3 ['3']
org.gnome.shell.keybindings switch-to-application-6 ['6']
org.gnome.shell.keybindings switch-to-application-9 ['9']
org.gnome.shell.keybindings shift-overview-up ['Up']
org.gnome.shell.keybindings switch-to-application-1 ['1']
org.gnome.shell.keybindings shift-overview-down ['Down']

** Attachment added: "gnome extensions screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955058/+attachment/5551911/+files/20220106-10-31-50.png

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

Title:
  gnome-shell memory use climbs to multiple GBs

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome Shell memory use grows over time

  Memory for Gnome Shell can be around 2.5 GB, sometimes more. If I do
  Alt-F2 r to restart shell, it drops to 250 MB and then slowly climbs
  up again.

  Occasionally it goes so high on my 16 GB machine that it swaps and
  crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 16 16:53:53 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-03 (1565 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-16 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955058/+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 1956119] Re: gnome-shell requires the gir1.2-gweather-3.0 dependency without gweather

[Daniel van Vugt]

gnome-weather is an app that is not required to run gnome-shell.

The other gweather-related packages are supporting data that is required
to run gnome-shell. It doesn't start up without it due to strong runtime
dependencies. If you want to change that then you will need to change
the source code of gnome-shell. Otherwise this bug report is invalid.

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

Title:
  gnome-shell requires the gir1.2-gweather-3.0 dependency without
  gweather

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  On a minimal installation where gweather is not installed, gnome-shell
  requires gir1.2-gweather-3.0. This required dependency pulls in
  libgweather-3-16 which then requires libgweather-common.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956119/+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 1871011] Re: USB scanning and printing broken on focal by ippusbxd (was: hpmud and ippusbxd conflict)

[Michel-Ekimia]

@Robert : you misunderstood , the problem is not the version of the
HPLIP , but the conflict with ippusbxd on USB device claiming.

Auto configure usb printers is nice but we can live on 20.04 without it.

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

Title:
  USB scanning and printing broken on focal by ippusbxd (was: hpmud and
  ippusbxd conflict)

Status in HPLIP:
  Invalid
Status in hplip package in Ubuntu:
  Expired
Status in ippusbxd package in Ubuntu:
  Confirmed

Bug description:
  SOLUTION : sudo apt remove ippusbxd

   Initial report -

  On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3.

  Previously there was a libmtp (udev) bug erroneously detecting HP
  printers as mtp devices. This was fixed. Now, I can try to scan-- from
  both simple-scan and hp-scan, hplip errors out:

  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
interface conf=0, iface=1, altset=0, index=1
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
kernel driver on interface=1 ret=0
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
claim_interface 7/1/2: Device or resource busy
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
interface conf=0, iface=0, altset=1, index=3
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
kernel driver on interface=0 ret=0
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
claim_interface 7/1/4: Device or resource busy
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
interface conf=0, iface=3, altset=0, index=9
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
kernel driver on interface=3 ret=0
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
claim_interface ff/4/1: Device or resource busy
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found 
interface conf=0, iface=0, altset=0, index=11
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active 
kernel driver on interface=0 ret=0
  Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid 
claim_interface ff/cc/0: Device or resource busy

  Printer/scanner is an Officejet 4635. Scanning previously worked just
  fine a few months ago. Regression?

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