[Desktop-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor

[postal]

I have the same problem on a PC. This also came with the last update.

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

Title:
  [raspi] Ubuntu 22.10 does not turn off monitor

Status in linux-raspi package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a
  strange behaviour of the screen saver.

  In settings -> energy -> power saving options I selected Screen Blank
  after 5 minutes. After 5 minutes of inactivity, the screen goes blank,
  the monitor says No Signal and turns off, but a few seconds after it
  turns on again, showing a completely black screen.

  The desired behaviour here is that Ubuntu sends no signal to the
  monitor, so the monitor goes into low-consumption mode. But this is
  not happening, the monitor is on and showing a black screen.

  I wonder how to solve this problem, especially given the current
  energy situation in Europe.

  This bug is related to the Ubuntu 22.04 LTS and 22.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7
  Uname: Linux 5.19.0-1009-raspi aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  4 21:31:27 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  ImageMediaBuild: 20221018.1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+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 2003410] Re: freeze after lead is closest, have black screen without any message, just after hard reset it work

[Daniel van Vugt]

** Tags added: nvidia

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

Title:
  freeze after lead is closest, have black screen without any message,
  just after hard reset it work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  freeze after lead is closest, have black screen without any message,
  just after hard reset it work

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 20 10:29:14 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-19 (1157 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-11-11 (69 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003410/+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 2003762] Re: [amdgpu] alienware aw3423dwf flickers at 165hz under linux only.

[Daniel van Vugt]

Oh no, you seem to have installed graphics packages from the 'oibaf'
PPA. That PPA is known to cause bugs like this and is unsupported.

Please remove the PPA from your system completely, and then report a new
bug if the flickering persists.


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

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

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

Title:
  [amdgpu] alienware aw3423dwf flickers at 165hz under linux only.

Status in kwin package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  alienware aw3423dwf flickers when set to 165hz. Doesn't at 100hz.
  Works fine under windows. GPU is Radeon 6950XT. If I change refresh
  rate down to 100hz it's fine.

  Happened on 22.04 LTS, and the amdgpu ppa made games not work, so I
  upgraded to 22.10 instead.

  Description:Ubuntu 22.10
  Release:22.10

  I expect the display not to flicker at 165hz. monitor doesn't lose
  sync, it's just like a few pixel wide bar that runs the width of the
  screen that shows up randomly for a fraction of a second. Happens when
  just using the desktop environment, not sure if it happens when
  playing a game.

  filename:   
/lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
  srcversion: BB7C61D4A8F6AFF924034AA

  99% sure I should be under X11, not wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon Jan 23 18:38:03 2023
  DisplayManager: sddm
  InstallationDate: Installed on 2022-10-23 (92 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  ShellJournal: -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-11-06 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2003762/+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 2003762] Re: alienware aw3423dwf flickers at 165hz under linux only.

[Daniel van Vugt]

This sounds like a bandwidth management issue, which I know Linux
doesn't do as well as Windows (on Intel graphics either).

Firstly you seem to have the wrong (old) kernel still installed. It
should be version 5.19 so please try fixing that with:

  sudo apt install linux-generic

or

  sudo apt install linux-generic-hwe-22.04

and reboot.

If the problem persists after that then please run:

  journalctl -b0 > journal.txt
  lspci -k > lspci.txt

and attach the resulting text files here.


** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu)

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

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

** Summary changed:

- alienware aw3423dwf flickers at 165hz under linux only.
+ [amdgpu] alienware aw3423dwf flickers at 165hz under linux only.

** Tags added: amdgpu

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

Title:
  [amdgpu] alienware aw3423dwf flickers at 165hz under linux only.

Status in kwin package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  alienware aw3423dwf flickers when set to 165hz. Doesn't at 100hz.
  Works fine under windows. GPU is Radeon 6950XT. If I change refresh
  rate down to 100hz it's fine.

  Happened on 22.04 LTS, and the amdgpu ppa made games not work, so I
  upgraded to 22.10 instead.

  Description:Ubuntu 22.10
  Release:22.10

  I expect the display not to flicker at 165hz. monitor doesn't lose
  sync, it's just like a few pixel wide bar that runs the width of the
  screen that shows up randomly for a fraction of a second. Happens when
  just using the desktop environment, not sure if it happens when
  playing a game.

  filename:   
/lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
  srcversion: BB7C61D4A8F6AFF924034AA

  99% sure I should be under X11, not wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon Jan 23 18:38:03 2023
  DisplayManager: sddm
  InstallationDate: Installed on 2022-10-23 (92 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  ShellJournal: -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-11-06 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2003762/+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 2003743] Re: Fix Plasma + Realtek ALC4080 USB audio device support

[Daniel van Vugt]

** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #2744
   https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2744

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

** Summary changed:

- Fix Plasma + Realtek ALC4080 USB audio device support
+ Realtek ALC4080 USB audio device support

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

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

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

** Tags added: fixed-in-pipewire-0.3.60 fixed-upstream

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

Title:
  Realtek ALC4080 USB audio device support

Status in PipeWire:
  Unknown
Status in pipewire package in Ubuntu:
  Fix Released

Bug description:
  Audio does not work on the MSI Z690 TOMAHAWK WIFI DDR4 (MS-7D32)
  motherboard when using Kubuntu 22.10 due to Realtek ALC4080 USB audio
  device issues.  Earlier ALC4080 problems were resolved against Gnome
  but under Plasma desktop it's still broken due to a pipewire problem.

  This patch
  https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1429
  resolves the issue and has been merged to pipewire master.  Please
  patch kinetic so MSI Z690 Plasma users don't have to wait another 6
  months for this to be resolved in kinetic-updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   7291 F wireplumber
   /dev/snd/controlC1:  dave   7291 F wireplumber
   /dev/snd/seq:dave   7288 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon Jan 23 10:57:51 2023
  InstallationDate: Installed on 2022-05-03 (264 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-12-02 (52 days ago)
  dmi.bios.date: 03/21/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.31
  dmi.board.asset.tag: Default string
  dmi.board.name: MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.31:bd03/21/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGZ690TOMAHAWKWIFIDDR4(MS-7D32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D32
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pipewire/+bug/2003743/+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 2003611] Re: Incorrect icon when launching app from symlink

[Daniel van Vugt]

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

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

Title:
  Incorrect icon when launching app from symlink

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Package freefilesync installs /usr/bin/FreeFileSync and
  /usr/bin/freefilesync is a symlink to FreeFileSync

  If you launch the programme from the command line with freefilesync
  the icon will be the default system wheel icon and not the icon of the
  app.

  If using FreeFileSync icon is the one of the app as expected.

  Btw: There is no such problem on KDE. Icon is always correct in the
  taskbar.

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


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

[Desktop-packages] [Bug 2001922] Re: Xorg crash

[Daniel van Vugt]

Thanks. That's a good start but the symbols are bogus:

[   160.566] (EE) Backtrace:
[   160.569] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x56325264c719]
[   160.569] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x7f5527424520]
[   160.569] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x258) 
[0x5632524e1298]
[   160.569] (EE) 3: /usr/lib/xorg/Xorg (ProcSendEvent+0x848) [0x5632524e9688]
[   160.570] (EE) 4: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1e43) 
[0x5632525c28b3]
[   160.570] (EE) 5: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) 
[0x5632525ece7c]
[   160.570] (EE) 6: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) 
[0x5632525e5f51]
[   160.570] (EE) 7: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) 
[0x5632525e614e]
[   160.570] (EE) 8: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x563252645c90]
[   160.570] (EE) 9: /usr/lib/xorg/Xorg (WaitForSomething+0x258) 
[0x563252645f18]
[   160.570] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) 
[0x5632524d6267]
[   160.570] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5632524da534]
[   160.571] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7f552740bd90]
[   160.571] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7f552740be40]
[   160.571] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5632524c3605]
[   160.571] (EE)
[   160.571] (EE) Segmentation fault at address 0x7ffe2c2b8000

We need proper debug symbols so please install
https://launchpad.net/~ubuntu-
security/+archive/ubuntu/ppa/+build/24907314/+files/xserver-xorg-core-
dbgsym_21.1.3-2ubuntu2.5_amd64.ddeb and continue to report all new
crashes after that.

Although I can see other recent crashes from the machine in:

https://errors.ubuntu.com/user/03ee3ad05735e452058026f308fdab5a759c144bde76f488875d1d877224459da0fcea51f892a6f2d385c5ffbdcf99758f4ae9764bad8eb4f0f322cbda9ac72b

it seems your system is being silently rejected for automated crash
analysis. I guess some part of the dist upgrades over the years has made
the system ineligible and sadly I don't know how to fix that other than
a fresh install of 22.04.

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

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

  There are files in /var/crash/

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

  
  and .xsession-errors.old ends with

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

  Is it safe and useful to upload the 

[Desktop-packages] [Bug 62949]

[Linut]

(In reply to Rob Kam from comment #48)
> Twenty years later and this is still unresolved?
> 
> Going to System Settings > Input Devices > Keyboard > Advanced > Swap ESC
> and Caps Lock is a piece of cake.
> 
> Then going to System Settings > Input Devices > Mouse there is nothing for
> changing e.g.
> Wheel Down > Screen down 
> Wheel Up > Screen up
> Button Forward > Control + Left click
> Button Back > Shift + Left click

Well, when you're on Wayland, there is actually an interface for setting up the 
additional mouse buttons, but it only works for extra mouse buttons (10+) and 
not for those that are mapped by default (1-9).
And at least with the current versions even that is broken, e.g. you can assign 
a keypress event to a mouse button, but it won't work.
In principle if you would like to reassign buttons 8 (back) and 9 (forward), 
you could remap your mouse so that these are e.g. button 11 and 12 and then you 
should be able to reassign them to a keyboard combination you could then use. I 
haven't checked though whether this works, because as mentioned above it's 
broken.
And it should be possible to directly assign mouse buttons in khotkeys (bug 
96431).

But in general I agree, it should be possible in the kcm to remap mouse buttons 
to different functions or even a key combination.
I would like to have a list of detected mouse buttons, each with a dropdown 
list and a couple of predefined mouse actions, e.g. the default mouse actions + 
selected commands (like those listed for the screen edges), e.g. present 
windows, peek at desktop, activity manager, close tab …
And as the final settings I would like to have "Mouse button 10" (if it's 
button 10) or "Use as hotkey", so that it can be assigned to any (possibly 
program-dependent) hotkey function and "Key combination".
Of course that also means that there is some duplication in the functionality, 
but I think it would be nice to present a selection of predefined commands to 
the user.

For me, these possibilities are – together with the problem of restarting kwin 
– the main showstopper to switch to Wayland.
On X11, I'm using imwheel, but that doesn't work on Wayland anymore. There are 
some options out there to get something like imwheel on Wayland, too, but they 
basically require working around the compositor and usually are way more 
complicated to setup, so I really would like to avoid those.
Plus, I think in 2023, it should be really possible to properly setup your 
mouse in KDE without needing to fall back to 3rd party programs. :/

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

Title:
  No way to configure mouse button number

Status in kdelibs:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-system-tools package in Ubuntu:
  Invalid
Status in kde4libs package in Ubuntu:
  Won't Fix

Bug description:
  Using kde-systemsettings, I can't configure my 6 button mouse. It
  would be interesting to just have a way to say "this mouse has X
  buttons".

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdelibs/+bug/62949/+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 1897249] Re: Scrolling in Chromium stops working when moving mouse when running in virtual machine

[Launchpad Bug Tracker]

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

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

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

Title:
  Scrolling in Chromium stops working when moving mouse when running in
  virtual machine

Status in chromium-browser package in Ubuntu:
  Expired
Status in falkon package in Ubuntu:
  Expired
Status in qutebrowser package in Ubuntu:
  Expired
Status in chromium package in Arch Linux:
  Invalid
Status in chromium package in openSUSE:
  Invalid

Bug description:
  When Ubuntu is running in a virtual machine scrolling in Chromium
  stops working when moving the mouse even the slightest. Also the first
  scroll step is always ignored after moving the mouse. This results in
  a very uneven scrolling which is very difficult to use. Scrolling
  works perfectly in other applications like for example Firefox.

  This bug seems to have appeared in Ubuntu 16.04.0, as all Ubuntu
  releases before 16.04 works correctly, while all releases after 16.04
  are affected by this bug. Ubuntu is not the only distro that has this
  bug, but there are also several distros that are not affected by it.

  My current testing have shown the following distros to be affected:
  - Arch Linux
  - Linux Mint 20 Cinnamon
  - Manjaro XFCE 20.1
  - OpenSUSE Tumbleweed
  - Ubuntu 16.04, 18.04, 20.04

  And the following distros and operating systems are NOT affected:
  - Centos 8
  - Debian 10 (Buster)
  - DragonFly BSD 5.8.1
  - Fedora 32
  - GhostBSD 20.08.04
  - Ubuntu 12.04 to 15.10
  - Windows 10

  The fact that there are current updated distros that are unaffected
  indicates to me that this is probably not a bug in Chromium upstream,
  but I've not been able to pinpoint whether the problem is caused by
  something in the Chromium packaged by Ubuntu or some other difference
  in the system like the kernel or system libraries.

  I have already reported the bug to Chromium, link to the bug report
  here: https://bugs.chromium.org/p/chromium/issues/detail?id=1128405.

  There is also another bug report here:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1100179

  
  I've already spent well over a week trying to troubleshoot this issue. I'm 
willing to do most of the work myself, but I really need some guidance as to 
what are the best next steps in troubleshooting this. Any help would be greatly 
appreciated!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897249/+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 1814936] Re: chromium-browser fails to start, with message [...:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction Proxy DB: 3

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  chromium-browser fails to start, with message
  [...:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction
  Proxy DB: 3

Status in chromium-browser package in Ubuntu:
  Expired
Status in chromium-browser package in Debian:
  Incomplete

Bug description:
  EDIT: upstream report at
  https://bugs.chromium.org/p/chromium/issues/detail?id=944295

  ps shows chromium-browser processes are running, but no windows
  appear.

  I've been able to correlate the message
  "[...:ERROR:data_store_impl.cc(131)] Failed to open Data Reduction
  Proxy DB: 3" with this failure mode.

  Users are frustrated when it happens to them, and advice online is to
  delete your profile and reboot, which is suboptimal, because it
  removes all bookmarks, history, settings, etc.  I have one user that
  gets this error almost daily, even after workstation swap, so I'm
  guessing there's a behavioral component as well.

  I have confirmed that killing all chromium-browser processes and
  rolling back just $HOME/.config/chromium/Default/Preferences to the
  state it was before a prior successful start is enough to fix the
  issue when it happens to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 71.0.3578.98-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: MATE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGs6EyAQEBAQgcAQOARid46g8lqFRDliIaUFS/74BxT4GAgQCzAIFAlQCpQNHAVl4AoKCgKVAwIDUAuokhAAAS/QAySx5aGAAKICAgICAg/ABWQTMyQVEKICAgICAg/wBKMkxNQVMwMDExOTQKARECAyXxSpAEAwEUEgUfBxMjCQcHgwEAAG0DDAAQADgxAjqAGHE4LUBYLEUAuokhAAAfVl4AoKCgKVAwIDUAuokhAAAeAR0AclHQHiBuKFUAuokhAAAf1QmAoCDgLRAIYCIAuokhCAgY9A==
   modes: 2560x1440 2560x1440 1920x1080 1920x1080 1920x1080i 1920x1080i 
1920x1080 1920x1080i 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 
800x600 800x600 800x600 800x600 720x576 720x480 720x480 720x480i 720x480i 
640x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  Date: Wed Feb  6 08:45:01 2019
  Desktop-Session:
   'mate'
   '/etc/xdg/xdg-mate:/etc/xdg'
   
'/usr/share/mate:/usr/share/mate:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:

  Env:
   'None'
   'None'
  InstalledPlugins:

  Load-Avg-1min: 3.04
  Load-Processes-Running-Percent:   0.1%
  MachineType: Shuttle Inc. DX30D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=dc6e336f-c022-11e8-b65f-80ee73d362fb ro
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FDX30
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd02/15/2017:svnShuttleInc.:pnDX30D:pvrV1.0:rvnShuttleInc.:rnFDX30:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: D
  dmi.product.name: DX30D
  dmi.product.version: V1.0
  dmi.sys.vendor: Shuttle Inc.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1814936/+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 1897249] Re: Scrolling in Chromium stops working when moving mouse when running in virtual machine

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Scrolling in Chromium stops working when moving mouse when running in
  virtual machine

Status in chromium-browser package in Ubuntu:
  Expired
Status in falkon package in Ubuntu:
  Expired
Status in qutebrowser package in Ubuntu:
  Expired
Status in chromium package in Arch Linux:
  Invalid
Status in chromium package in openSUSE:
  Invalid

Bug description:
  When Ubuntu is running in a virtual machine scrolling in Chromium
  stops working when moving the mouse even the slightest. Also the first
  scroll step is always ignored after moving the mouse. This results in
  a very uneven scrolling which is very difficult to use. Scrolling
  works perfectly in other applications like for example Firefox.

  This bug seems to have appeared in Ubuntu 16.04.0, as all Ubuntu
  releases before 16.04 works correctly, while all releases after 16.04
  are affected by this bug. Ubuntu is not the only distro that has this
  bug, but there are also several distros that are not affected by it.

  My current testing have shown the following distros to be affected:
  - Arch Linux
  - Linux Mint 20 Cinnamon
  - Manjaro XFCE 20.1
  - OpenSUSE Tumbleweed
  - Ubuntu 16.04, 18.04, 20.04

  And the following distros and operating systems are NOT affected:
  - Centos 8
  - Debian 10 (Buster)
  - DragonFly BSD 5.8.1
  - Fedora 32
  - GhostBSD 20.08.04
  - Ubuntu 12.04 to 15.10
  - Windows 10

  The fact that there are current updated distros that are unaffected
  indicates to me that this is probably not a bug in Chromium upstream,
  but I've not been able to pinpoint whether the problem is caused by
  something in the Chromium packaged by Ubuntu or some other difference
  in the system like the kernel or system libraries.

  I have already reported the bug to Chromium, link to the bug report
  here: https://bugs.chromium.org/p/chromium/issues/detail?id=1128405.

  There is also another bug report here:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1100179

  
  I've already spent well over a week trying to troubleshoot this issue. I'm 
willing to do most of the work myself, but I really need some guidance as to 
what are the best next steps in troubleshooting this. Any help would be greatly 
appreciated!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897249/+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 1897249] Re: Scrolling in Chromium stops working when moving mouse when running in virtual machine

[Launchpad Bug Tracker]

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

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

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

Title:
  Scrolling in Chromium stops working when moving mouse when running in
  virtual machine

Status in chromium-browser package in Ubuntu:
  Expired
Status in falkon package in Ubuntu:
  Expired
Status in qutebrowser package in Ubuntu:
  Expired
Status in chromium package in Arch Linux:
  Invalid
Status in chromium package in openSUSE:
  Invalid

Bug description:
  When Ubuntu is running in a virtual machine scrolling in Chromium
  stops working when moving the mouse even the slightest. Also the first
  scroll step is always ignored after moving the mouse. This results in
  a very uneven scrolling which is very difficult to use. Scrolling
  works perfectly in other applications like for example Firefox.

  This bug seems to have appeared in Ubuntu 16.04.0, as all Ubuntu
  releases before 16.04 works correctly, while all releases after 16.04
  are affected by this bug. Ubuntu is not the only distro that has this
  bug, but there are also several distros that are not affected by it.

  My current testing have shown the following distros to be affected:
  - Arch Linux
  - Linux Mint 20 Cinnamon
  - Manjaro XFCE 20.1
  - OpenSUSE Tumbleweed
  - Ubuntu 16.04, 18.04, 20.04

  And the following distros and operating systems are NOT affected:
  - Centos 8
  - Debian 10 (Buster)
  - DragonFly BSD 5.8.1
  - Fedora 32
  - GhostBSD 20.08.04
  - Ubuntu 12.04 to 15.10
  - Windows 10

  The fact that there are current updated distros that are unaffected
  indicates to me that this is probably not a bug in Chromium upstream,
  but I've not been able to pinpoint whether the problem is caused by
  something in the Chromium packaged by Ubuntu or some other difference
  in the system like the kernel or system libraries.

  I have already reported the bug to Chromium, link to the bug report
  here: https://bugs.chromium.org/p/chromium/issues/detail?id=1128405.

  There is also another bug report here:
  https://bugs.chromium.org/p/chromium/issues/detail?id=1100179

  
  I've already spent well over a week trying to troubleshoot this issue. I'm 
willing to do most of the work myself, but I really need some guidance as to 
what are the best next steps in troubleshooting this. Any help would be greatly 
appreciated!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897249/+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 1994562] Re: Ubuntu settings gets very laggy most of the times in 22.10

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu settings gets very laggy most of the times in 22.10

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

Bug description:
  Everything related to settings in the newly released Ubuntu 22.10 is
  very laggy. It might work fine for a while, then when I try scrolling,
  it laggs and nothing happens for a few seconds. It might even crash.
  This happens in Settings, in Extension Manager or some GS extension's
  settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: ubuntu-settings 22.10.1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 26 15:47:01 2022
  InstallationDate: Installed on 2022-10-24 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  PackageArchitecture: all
  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/gnome-control-center/+bug/1994562/+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 1997177] Re: package libaa1:i386 1.4p5-50build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

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

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

Title:
  package libaa1:i386 1.4p5-50build1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in aalib package in Ubuntu:
  Expired

Bug description:
  ran into issue after installing ubuntu for the first time and trying
  to install a package reader like wine or bottles

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libaa1:i386 1.4p5-50build1
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Nov 20 20:20:05 2022
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2022-11-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: aalib
  Title: package libaa1:i386 1.4p5-50build1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aalib/+bug/1997177/+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 1994010] Re: gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from mozilla::detail::IntrinsicMemoryOps

[Daniel van Vugt]

With some luck this might have been fixed in lunar already because it's
not mentioned in
https://errors.ubuntu.com/?release=Ubuntu%2023.04=gnome-
shell=week and lunar has newer mozjs102 and gjs than kinetic.

We should probably check the release notes and commit history of those
updates that are in lunar but not kinetic.

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

Title:
  gnome-shell crashed with SIGSEGV in std::__atomic_base::load(__m=std::memory_order_relaxed, this=0x0) from
  mozilla::detail::IntrinsicMemoryOps::load()

Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mozjs102 package in Ubuntu:
  Confirmed

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

  gnome-shell crashed with SIGSEGV:

  #0  std::__atomic_base::load (__m=std::memory_order_relaxed, 
this=0x0) at /usr/include/c++/12/bits/atomic_base.h:486
  __b = std::memory_order_relaxed
  #1  mozilla::detail::IntrinsicMemoryOps::load (aPtr=...) at 
.././debian/build/dist/include/mozilla/Atomics.h:195
  No locals.
  #2  mozilla::detail::AtomicBaseIncDec::operator unsigned long (this=0x0) at 
.././debian/build/dist/include/mozilla/Atomics.h:340
  No locals.
  #3  js::gc::CellWithTenuredGCPointer::headerPtr 
(this=0x0) at .././js/src/gc/Cell.h:802
  No locals.
  #4  JSObject::shape (this=, this=) at 
.././js/src/vm/JSObject.h:99
  No locals.
  #5  JSObject::nonCCWRealm (this=0x0) at .././js/src/vm/JSObject.h:413
  No locals.
  #6  JSContext::enterRealmOf (target=0x0, this=0x561efe351c00) at 
.././js/src/vm/JSContext-inl.h:318
  No locals.
  #7  JSAutoRealm::JSAutoRealm (this=, cx=, 
target=, this=, cx=, 
target=) at .././js/src/jsapi.cpp:519
  No locals.
  #8  0x7f9b4910db2a in gjs_object_set_gproperty (object=, 
property_id=, value=0x7ffc738467d0, pspec=0x561efe19be10) at 
../gi/gobject.cpp:209
  priv = 
  cx = 0x561efe351c00
  js_obj = {> = { = {stack = 0x561efe351c18, prev = 0x0}, 
},  >> = 
{ >> = 
{, void>> = {}, }, }, ptr = 0x0}
  ar = {cx_ = 0x561efe351c00, oldRealm_ = 0x0}
  ...

  https://errors.ubuntu.com/problem/d31a7f723bab2a42586060136dc27f56bc71

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1994010/+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 874181] Re: brltty daemon prevents creation of ttyUSB0 device link

[Tony Kerr]

This is still an issue in Ubuntu 22.04. I solved it by using apt to
remove brltty. Unfortunately this is likely to be temporary as an update
will reinstate it.

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

Title:
  brltty daemon prevents creation of ttyUSB0 device link

Status in brltty package in Ubuntu:
  Confirmed
Status in brltty source package in Oneiric:
  Fix Released

Bug description:
  Impact:
  This bug is somewhat hardware specific, affecting all users of the USB serial 
controller, device 10c4:ea60.

  Test case:
  With the current version of brltty in Oneiric, brltty takes over any device 
using the above mentioned USB serial controller, whether it is a Braille 
display or not. This is because one of Brltty's supported displays uses this 
USB serial control internally for ocmmunication. The brltty package in 
oneiric-proposed has the udev rule for this controller commented out, allowing 
other users of devices based on this controller to work properly.

  Regression potential:
  All users of the supported Seika will have to load Brltty manually, as the 
udev rule for their device is commented out, to allow other USB serial 
controller users to use their device as a proper serial device.

  Original description follows:

  After upgrading from Ubuntu 11.04 to 11.10, I no longer found a
  '/dev/ttyUSB0' for my serial-to-USB converter. The device is part  of
  a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products,
  Inc. CP210x Composite Device".

  Every time I plugged in the device, dmesg showed the device coming up
  and 'brltty' did *something* to it. At this point, no device was
  present in '/dev'.

  [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected
  [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd
  [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0
  [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1

  After removing 'brltty', the '/dev/ttyUSB0' device appears again like
  it used to.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: brltty (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 14 14:39:29 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   LC_TIME=C
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: brltty
  UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

[Daniel van Vugt]

I think bug 1994010 should be fixed before this proceeds. It's the top
gnome-shell crash on kinetic by a long way and looks likely to spread to
jammy if gjs and mozjs get upgraded.

https://errors.ubuntu.com/?release=Ubuntu%2022.10=gnome-
shell=week

I mentioned this on mattermost a week ago but it seems nobody saw the
message.

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

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

Title:
  [jammy] Update gjs to 1.74 using mozjs102 102.3

Status in gjs package in Ubuntu:
  Fix Released
Status in mozjs102 package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  --
  GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). 
Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 
ESR series for security updates for the next year.

  This requires updating gjs from 1.72 to 1.74 from GNOME 43, as
  packaged in Ubuntu 22.10.

  This will be done as a Security Update.

  Updating mozjs in stable Ubuntu releases was recommended when Ubuntu
  first switched back to GNOME, but this is the first time it's been
  done.

  Security Impact
  ---
  I looked through
  https://github.com/mozilla/gecko-dev/commits/esr102/js
  and searched for referenced bug numbers in
  https://www.mozilla.org/en-US/security/advisories/
  for Firefox ESR releases since Ubuntu's 91.10

  and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE
  issued) mentioned at

  https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/

  Uploaded Packages
  -
  We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being 
careful to publish it in main, not universe.
  And we'll update gjs.
  No other packages need to be updated for this change.
  mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are 
generally not possible), but nothing else in Ubuntu uses it.

  Test Case
  -
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  Security Sponsoring
  ---
  sudo apt install git-buildpackage
  gbp clone https://salsa.debian.org/gnome-team/gjs
  cd gjs
  git checkout ubuntu/jammy
  gbp buildpackage --git-builder="debuild -S -nc"

  mkdir ../tarballs; cd ../tarballs
  pull-lp-source mozjs102 kinetic
  cd ..
  gbp clone https://salsa.debian.org/gnome-team/mozjs
  cd mozjs
  git checkout ubuntu/102/jammy
  gbp buildpackage --git-builder="debuild --no-lintian -S -nc" 
--git-tarball-dir=../tarballs
  # That avoids needing to recreate the original tarball from pristine-tar 
which takes a while. Also, running lintian takes a while.

  Initial Testing Done
  
  I built the packages in my PPA.
  I installed the packages on Ubuntu 22.04 LTS and successfully completed the 
Test Case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 2003762] [NEW] alienware aw3423dwf flickers at 165hz under linux only.

[Al]

Public bug reported:

alienware aw3423dwf flickers when set to 165hz. Doesn't at 100hz. Works
fine under windows. GPU is Radeon 6950XT. If I change refresh rate down
to 100hz it's fine.

Happened on 22.04 LTS, and the amdgpu ppa made games not work, so I
upgraded to 22.10 instead.

Description:Ubuntu 22.10
Release:22.10

I expect the display not to flicker at 165hz. monitor doesn't lose sync,
it's just like a few pixel wide bar that runs the width of the screen
that shows up randomly for a fraction of a second. Happens when just
using the desktop environment, not sure if it happens when playing a
game.

filename:   
/lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
srcversion: BB7C61D4A8F6AFF924034AA

99% sure I should be under X11, not wayland.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Mon Jan 23 18:38:03 2023
DisplayManager: sddm
InstallationDate: Installed on 2022-10-23 (92 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2022-11-06 (78 days ago)

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


** Tags: amd64 apport-bug kinetic third-party-packages

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

Title:
  alienware aw3423dwf flickers at 165hz under linux only.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  alienware aw3423dwf flickers when set to 165hz. Doesn't at 100hz.
  Works fine under windows. GPU is Radeon 6950XT. If I change refresh
  rate down to 100hz it's fine.

  Happened on 22.04 LTS, and the amdgpu ppa made games not work, so I
  upgraded to 22.10 instead.

  Description:Ubuntu 22.10
  Release:22.10

  I expect the display not to flicker at 165hz. monitor doesn't lose
  sync, it's just like a few pixel wide bar that runs the width of the
  screen that shows up randomly for a fraction of a second. Happens when
  just using the desktop environment, not sure if it happens when
  playing a game.

  filename:   
/lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
  srcversion: BB7C61D4A8F6AFF924034AA

  99% sure I should be under X11, not wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon Jan 23 18:38:03 2023
  DisplayManager: sddm
  InstallationDate: Installed on 2022-10-23 (92 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  ShellJournal: -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-11-06 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003762/+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 821883] Re: [MIR] argyll

[Bryce Harrington]

colord recently re-enabled argyll support.  Unfortunately since argyll
is in universe and colord is in main, this is causing an 'impossible
depends' migration error for colord.

colord-sensor-argyll/amd64 in main cannot depend on argyll in universe 
Impossible Depends: colord -> argyll/2.3.1+repack-1ubuntu1/amd64 

colord (1.4.6-2) unstable; urgency=medium

  * debian/control:
- Build-Depend on polkitd. Fixes FTBFS (Closes: #1022355)
- Bump Standards-Version to 4.6.1 (no changes needed)
  * debian/rules:
  * debian/control:
  * debian/not-installed:
- Re-enable Argyll support. Argyll no longer appears in danger of
  being removed from the archive.
  * debian/copyright:
- Fix misspelling of Richard Hughes' name
- Drop no-longer-necessary Files: stanzas
- Include full license details of data/profiles

 -- Christopher James Halse Rogers   Tue, 01 Nov 2022
11:02:35 +0100

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

Title:
  [MIR] argyll

Status in argyll package in Ubuntu:
  Incomplete
Status in colord package in Ubuntu:
  New

Bug description:
  Note this MIR is for both argyll and libicc2 (both packages are
  currently in Universe). With the most recent argyll package the binary
  packages of argyll and libicc2 are now all produced by the argyll
  source package. We followed Debian to unsplit here as the upstream
  source for both is argyll. The libicc2 source package in Universe can
  get dropped.

  Availability: Currently available in Universe, building on all
  currently supported architectures, see
  https://launchpad.net/ubuntu/+source/argyll

  Rationale: In Oneiric we want to introduce ICC-based color management
  on the operating system level, using the same architecture as Fedora
  does. argyll (support for color calibration) and libicc2 (ICC handling
  library) are part of this architecture. Therefore we need them in
  Main. This MIR is a work item of the following Blueprint:

  https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-icc-color-
  management

  According to the Blueprint additional demand on CD space for the whole
  introduction of color management is around 300K only.

  Security: No security vulnerabilities known at CVE and Secunia for the
  current version (1.3.3), vulnerabilities of older versions are all
  fixed, no SUID components, no daemons.

  Quality assurance: Installs without debconf questions. The package is
  maintained upstream as new releases occur regularly and they get
  packaged for Debian by Roland Mas (see debian/changelog).

  UI standards: The package are a library and command line utilities.
  The complete upstream documentation is available in
  /usr/share/doc/argyll/. Each command shows a help page by calling it
  without parameters.

  Dependencies: Depends only on standard libraries for X and images.
  They are all in Main.

  Maintenance: See "Quality assurance".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argyll/+bug/821883/+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 821883] Re: [MIR] argyll

[Bryce Harrington]

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

** Tags added: update-excuse

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

Title:
  [MIR] argyll

Status in argyll package in Ubuntu:
  Incomplete
Status in colord package in Ubuntu:
  New

Bug description:
  Note this MIR is for both argyll and libicc2 (both packages are
  currently in Universe). With the most recent argyll package the binary
  packages of argyll and libicc2 are now all produced by the argyll
  source package. We followed Debian to unsplit here as the upstream
  source for both is argyll. The libicc2 source package in Universe can
  get dropped.

  Availability: Currently available in Universe, building on all
  currently supported architectures, see
  https://launchpad.net/ubuntu/+source/argyll

  Rationale: In Oneiric we want to introduce ICC-based color management
  on the operating system level, using the same architecture as Fedora
  does. argyll (support for color calibration) and libicc2 (ICC handling
  library) are part of this architecture. Therefore we need them in
  Main. This MIR is a work item of the following Blueprint:

  https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-icc-color-
  management

  According to the Blueprint additional demand on CD space for the whole
  introduction of color management is around 300K only.

  Security: No security vulnerabilities known at CVE and Secunia for the
  current version (1.3.3), vulnerabilities of older versions are all
  fixed, no SUID components, no daemons.

  Quality assurance: Installs without debconf questions. The package is
  maintained upstream as new releases occur regularly and they get
  packaged for Debian by Roland Mas (see debian/changelog).

  UI standards: The package are a library and command line utilities.
  The complete upstream documentation is available in
  /usr/share/doc/argyll/. Each command shows a help page by calling it
  without parameters.

  Dependencies: Depends only on standard libraries for X and images.
  They are all in Main.

  Maintenance: See "Quality assurance".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argyll/+bug/821883/+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 2003564] Re: Sync xfonts-scalable 1:1.0.3-1.3 (main) from Debian unstable (main)

[Simon Quigley]

This bug was fixed in the package xfonts-scalable - 1:1.0.3-1.3
Sponsored for Hans Joachim Desserud (hjd)

---
xfonts-scalable (1:1.0.3-1.3) unstable; urgency=medium

  * Non-maintainer upload, incorporating changes from the maintainers'
packaging repository

  [ Julien Cristau ]
  * Remove Cyril and David from Uploaders.
  * Add Vcs-* control fields.
  * Use https URL in debian/watch.

  [ Simon McVittie ]
  * d/control: Update Vcs-* for migration to salsa.debian.org
  * Use recommended debhelper compat level 13 (Closes: #965894)
  * d/rules: Add missing build-arch, build-indep targets (Policy §4.9)
  * d/control: Declare that the build does not require (fake)root

 -- Simon McVittie   Sun, 15 Jan 2023 14:18:32 +

** Changed in: xfonts-scalable (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync xfonts-scalable 1:1.0.3-1.3 (main) from Debian unstable (main)

Status in xfonts-scalable package in Ubuntu:
  Fix Released

Bug description:
  Please sync xfonts-scalable 1:1.0.3-1.3 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Update to dh7 to fix the build
* Update to dh7 to fix the build
* Update to dh7 to fix the build

  Current Ubuntu delta:
  
https://patches.ubuntu.com/x/xfonts-scalable/xfonts-scalable_1:1.0.3-1.2ubuntu1.patch

  Debian has updated debhelper dependency from 5 to 13 now.
  Relevant commit:
  
https://salsa.debian.org/xorg-team/font/xfonts-scalable/-/commit/020b14f4ce6c9add3e4a7d71578771c66547656e
  resulting in curent control file:
  https://tracker.debian.org/media/packages/x/xfonts-scalable/control-11.0.3-1.3

  
  Changelog entries since current lunar version 1:1.0.3-1.2ubuntu1:

  xfonts-scalable (1:1.0.3-1.3) unstable; urgency=medium

* Non-maintainer upload, incorporating changes from the maintainers'
  packaging repository

[ Julien Cristau ]
* Remove Cyril and David from Uploaders.
* Add Vcs-* control fields.
* Use https URL in debian/watch.

[ Simon McVittie ]
* d/control: Update Vcs-* for migration to salsa.debian.org
* Use recommended debhelper compat level 13 (Closes: #965894)
* d/rules: Add missing build-arch, build-indep targets (Policy §4.9)
* d/control: Declare that the build does not require (fake)root

   -- Simon McVittie   Sun, 15 Jan 2023 14:18:32 +

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfonts-scalable/+bug/2003564/+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 2003735] Re: [SRU] libreoffice 7.4.4 updates for kinetic

[Bug Watch Updater]

Launchpad has imported 10 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=153059.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2023-01-17T09:24:43+00:00 Xiscofauli wrote:

Steps to reproduce:
1. Open attachment 178682from bug 147802
2. In the first page, click on the header -> The header button is displayed
3. Scroll down to a different page
4. Click on the header button

-> Crash

Reproduced in

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: b9411e587586750f36ba9009b5f1e29fe461d8b5
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: de-DE (es_ES.UTF-8); UI: en-US
Calc: threaded

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/comments/0


On 2023-01-17T09:26:47+00:00 Xiscofauli wrote:

Another way to reproduce it:
1. Open a new writer document
2. Insert a page break
3. Go to page 1 and click on the header
4. Go to page 2 and click on the header button
-> Crash

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/comments/1


On 2023-01-17T09:31:10+00:00 Xiscofauli wrote:

regression introduced by:

author  Caolán McNamara 2022-11-15 16:02:06 +
committer   Caolán McNamara 2022-11-15 20:34:51 
+0100
commit  701e8d06484fb8781e43017ccf4ac1a3d64ac9e8 (patch)
tree34001a0f4fdf15168ca8d8ccd08e9435d91b7c93
parent  2550835bde036a2809d693d9633b8b736c035ecb (diff)
Resolves: tdf#147802 don't create a header/footer control for every page

Bisected with: bibisect-linux64-7.5

Adding Cc: to Caolán McNamara

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/comments/2


On 2023-01-17T09:32:56+00:00 Xiscofauli wrote:

I found this crash after checking 
https://crashreport.libreoffice.org/stats/version/7.4.4.2 and finding 
https://crashreport.libreoffice.org/stats/signature/SwHeaderFooterWin::LinkStubClickHdl(void%20*,weld::Button%20&)
 is the most reported crash in that version.
Increasing importance

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/comments/3


On 2023-01-17T10:22:31+00:00 Caolanm wrote:

Cursor is still on page one so when a header is added it jumps back to
that page, so the widget on the now hidden page is removed, but the
click handler hasn't completed so the follow up action to change it from
a "plus" button to a dropdown menubutton is on a disposed widget

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/comments/4


On 2023-01-17T20:36:08+00:00 Libreoffice-commits wrote:

Caolán McNamara committed a patch related to this issue.
It has been pushed to "libreoffice-7-4":

https://git.libreoffice.org/core/commit/cd0ea49d95fcb3af5b7408c9bbea553480a12f92

Resolves: tdf#153059 after ChangeHeaderOrFooter the control can be
disposed

It will be available in 7.4.5.

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

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/comments/5


On 2023-01-17T20:36:11+00:00 Libreoffice-commits wrote:

Caolán McNamara committed a patch related to this issue.
It has been pushed to "libreoffice-7-5":

https://git.libreoffice.org/core/commit/a64d8610fdbe56df67df03e6fadfff9ab7a0c441

Resolves: tdf#153059 after ChangeHeaderOrFooter the control can be
disposed

It will be available in 7.5.1.

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

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/comments/6


On 2023-01-17T21:05:16+00:00 Libreoffice-commits wrote:

Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/a21258c86e7fd1c64b11216a809f430627a06476

Resolves: tdf#153059 

[Desktop-packages] [Bug 1968610] Re: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia

[librenyaa]

** Description changed:

  When launching Chromium as a snap on Ubuntu 22.04, it will not open
  properly and will open the browser with only the titlebar and a
  transparent window. I am using an Nvidia Graphics card with the
  510.60.02 Nvidia proprietary drivers.
  
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Chromium Version: 100.0.4896.75 2022-04-07
  
  When running "snap run chromium" in the terminal, the following output
  happens. Attached screenshot of result.
  
  nyaa@nyaa-desktop:~$ snap run chromium
  Gtk-Message: 13:42:20.777: Failed to load module "canberra-gtk-module"
  Gtk-Message: 13:42:20.778: Failed to load module "canberra-gtk-module"
  MESA-LOADER: failed to retrieve device information
  MESA-LOADER: failed to open nvidia-drm: 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so:
 cannot open shared object file: Permission denied (search paths 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
  failed to load driver: nvidia-drm
  MESA-LOADER: failed to open kms_swrast: 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/kms_swrast_dri.so:
 cannot open shared object file: Permission denied (search paths 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
  failed to load driver: kms_swrast
  MESA-LOADER: failed to open swrast: 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: 
cannot open shared object file: Permission denied (search paths 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
  failed to load swrast driver
  [9358:9478:0411/134223.111306:ERROR:udev_watcher.cc(98)] Failed to begin udev 
enumeration.
  
  Edit: I have recently tested this more, and I've isolated it to Wayland
  and the snap version of Chromium. On X, the chromium snap runs
  correctly.
  
- When I run Chromium as a direct download, the issue doesn't occur on
- Wayland.
+ When I run Chromium as a binary from the Chromium website, the issue
+ doesn't occur on Wayland.

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

Title:
  Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  When launching Chromium as a snap on Ubuntu 22.04, it will not open
  properly and will open the browser with only the titlebar and a
  transparent window. I am using an Nvidia Graphics card with the
  510.60.02 Nvidia proprietary drivers.

  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Chromium Version: 100.0.4896.75 2022-04-07

  When running "snap run chromium" in the terminal, the following output
  happens. Attached screenshot of result.

  nyaa@nyaa-desktop:~$ snap run chromium
  Gtk-Message: 13:42:20.777: Failed to load module "canberra-gtk-module"
  Gtk-Message: 13:42:20.778: Failed to load module "canberra-gtk-module"
  MESA-LOADER: failed to retrieve device information
  MESA-LOADER: failed to open nvidia-drm: 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so:
 cannot open shared object file: Permission denied (search paths 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
  failed to load driver: nvidia-drm
  MESA-LOADER: failed to open kms_swrast: 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/kms_swrast_dri.so:
 cannot open shared object file: Permission denied (search paths 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
  failed to load driver: kms_swrast
  MESA-LOADER: failed to open swrast: 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: 
cannot open shared object file: Permission denied (search paths 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
  failed to load swrast driver
  [9358:9478:0411/134223.111306:ERROR:udev_watcher.cc(98)] Failed to begin udev 
enumeration.

  Edit: I have recently tested this more, and I've isolated it to
  Wayland and the snap version of Chromium. On X, the chromium snap runs
  correctly.

  When I run Chromium as a binary from the Chromium website, the issue
  doesn't occur on Wayland.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968610/+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 2003611] ProcCpuinfoMinimal.txt

[Jhonny Oliveira]

apport information

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

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

Title:
  Incorrect icon when launching app from symlink

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Package freefilesync installs /usr/bin/FreeFileSync and
  /usr/bin/freefilesync is a symlink to FreeFileSync

  If you launch the programme from the command line with freefilesync
  the icon will be the default system wheel icon and not the icon of the
  app.

  If using FreeFileSync icon is the one of the app as expected.

  Btw: There is no such problem on KDE. Icon is always correct in the
  taskbar.

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

[Jhonny Oliveira]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2003611/+attachment/5643072/+files/ProcEnviron.txt

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

Title:
  Incorrect icon when launching app from symlink

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Package freefilesync installs /usr/bin/FreeFileSync and
  /usr/bin/freefilesync is a symlink to FreeFileSync

  If you launch the programme from the command line with freefilesync
  the icon will be the default system wheel icon and not the icon of the
  app.

  If using FreeFileSync icon is the one of the app as expected.

  Btw: There is no such problem on KDE. Icon is always correct in the
  taskbar.

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

[Jhonny Oliveira]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/2003611/+attachment/5643073/+files/ShellJournal.txt

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

Title:
  Incorrect icon when launching app from symlink

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Package freefilesync installs /usr/bin/FreeFileSync and
  /usr/bin/freefilesync is a symlink to FreeFileSync

  If you launch the programme from the command line with freefilesync
  the icon will be the default system wheel icon and not the icon of the
  app.

  If using FreeFileSync icon is the one of the app as expected.

  Btw: There is no such problem on KDE. Icon is always correct in the
  taskbar.

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

[Jhonny Oliveira]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/2003611/+attachment/5643070/+files/GsettingsChanges.txt

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

Title:
  Incorrect icon when launching app from symlink

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Package freefilesync installs /usr/bin/FreeFileSync and
  /usr/bin/freefilesync is a symlink to FreeFileSync

  If you launch the programme from the command line with freefilesync
  the icon will be the default system wheel icon and not the icon of the
  app.

  If using FreeFileSync icon is the one of the app as expected.

  Btw: There is no such problem on KDE. Icon is always correct in the
  taskbar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003611/+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 2003611] Re: Incorrect icon when launching app from symlink

[Jhonny Oliveira]

ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2022-10-21 (94 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
Package: gnome-shell 43.1-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
Tags:  kinetic wayland-session
Uname: Linux 5.19.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True


** Tags added: apport-collected kinetic wayland-session

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

Title:
  Incorrect icon when launching app from symlink

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Package freefilesync installs /usr/bin/FreeFileSync and
  /usr/bin/freefilesync is a symlink to FreeFileSync

  If you launch the programme from the command line with freefilesync
  the icon will be the default system wheel icon and not the icon of the
  app.

  If using FreeFileSync icon is the one of the app as expected.

  Btw: There is no such problem on KDE. Icon is always correct in the
  taskbar.

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

[Jhonny Oliveira]

apport information

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

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

Title:
  Incorrect icon when launching app from symlink

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Package freefilesync installs /usr/bin/FreeFileSync and
  /usr/bin/freefilesync is a symlink to FreeFileSync

  If you launch the programme from the command line with freefilesync
  the icon will be the default system wheel icon and not the icon of the
  app.

  If using FreeFileSync icon is the one of the app as expected.

  Btw: There is no such problem on KDE. Icon is always correct in the
  taskbar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003611/+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 2003743] Re: Fix Plasma + Realtek ALC4080 USB audio device support

[Dave G]

wrong package

** Package changed: pulseaudio (Ubuntu) => pipewire (Ubuntu)

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2003743/+attachment/5643065/+files/ProcEnviron.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2003743/+attachment/5643064/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "PaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2003743/+attachment/5643063/+files/PaInfo.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2003743/+attachment/5643062/+files/Dependencies.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2003743/+attachment/5643061/+files/CurrentDmesg.txt

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2003743/+attachment/5643060/+files/AlsaInfo.txt

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

Title:
  Fix Plasma + Realtek ALC4080 USB audio device support

Status in pipewire package in Ubuntu:
  New

Bug description:
  Audio does not work on the MSI Z690 TOMAHAWK WIFI DDR4 (MS-7D32)
  motherboard when using Kubuntu 22.10 due to Realtek ALC4080 USB audio
  device issues.  Earlier ALC4080 problems were resolved against Gnome
  but under Plasma desktop it's still broken due to a pipewire problem.

  This patch
  https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1429
  resolves the issue and has been merged to pipewire master.  Please
  patch kinetic so MSI Z690 Plasma users don't have to wait another 6
  months for this to be resolved in kinetic-updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   7291 F wireplumber
   /dev/snd/controlC1:  dave   7291 F wireplumber
   /dev/snd/seq:dave   7288 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon Jan 23 10:57:51 2023
  InstallationDate: Installed on 2022-05-03 (264 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-12-02 (52 days ago)
  dmi.bios.date: 03/21/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.31
  dmi.board.asset.tag: Default string
  dmi.board.name: MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.31:bd03/21/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGZ690TOMAHAWKWIFIDDR4(MS-7D32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D32
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2003743/+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 1968610] Re: Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia

[Bram Stolk]

I am hitting this too.

Unlike OP, I am on 22.10
Like OP, I am on nvidia 510 proprietary drivers.

Adding --ozone-platform=wayland fixes the issue for me.


$ chromium
Gtk-Message: 10:43:34.433: Not loading module "atk-bridge": The functionality 
is provided by GTK natively. Please try to not load it.
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open nvidia-drm: 
/snap/chromium/2271/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so:
 cannot open shared object file: Permission denied (search paths 
/snap/chromium/2271/gnome-platform/usr/lib/x86_64-linux-gnu/dri, suffix _dri)
failed to load driver: nvidia-drm

chromium snap version: 109.0.5414.74 (latest/stable channel)

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

Title:
  Chromium snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  When launching Chromium as a snap on Ubuntu 22.04, it will not open
  properly and will open the browser with only the titlebar and a
  transparent window. I am using an Nvidia Graphics card with the
  510.60.02 Nvidia proprietary drivers.

  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Chromium Version: 100.0.4896.75 2022-04-07

  When running "snap run chromium" in the terminal, the following output
  happens. Attached screenshot of result.

  nyaa@nyaa-desktop:~$ snap run chromium
  Gtk-Message: 13:42:20.777: Failed to load module "canberra-gtk-module"
  Gtk-Message: 13:42:20.778: Failed to load module "canberra-gtk-module"
  MESA-LOADER: failed to retrieve device information
  MESA-LOADER: failed to open nvidia-drm: 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so:
 cannot open shared object file: Permission denied (search paths 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
  failed to load driver: nvidia-drm
  MESA-LOADER: failed to open kms_swrast: 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/kms_swrast_dri.so:
 cannot open shared object file: Permission denied (search paths 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
  failed to load driver: kms_swrast
  MESA-LOADER: failed to open swrast: 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: 
cannot open shared object file: Permission denied (search paths 
/snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri)
  failed to load swrast driver
  [9358:9478:0411/134223.111306:ERROR:udev_watcher.cc(98)] Failed to begin udev 
enumeration.

  Edit: I have recently tested this more, and I've isolated it to
  Wayland and the snap version of Chromium. On X, the chromium snap runs
  correctly.

  When I run Chromium as a direct download, the issue doesn't occur on
  Wayland.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968610/+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 2003743] [NEW] Fix Plasma + Realtek ALC4080 USB audio device support

[Dave G]

Public bug reported:

Audio does not work on the MSI Z690 TOMAHAWK WIFI DDR4 (MS-7D32)
motherboard when using Kubuntu 22.10 due to Realtek ALC4080 USB audio
device issues.  Earlier ALC4080 problems were resolved against Gnome but
under Plasma desktop it's still broken due to a pipewire problem.

This patch
https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1429
resolves the issue and has been merged to pipewire master.  Please patch
kinetic so MSI Z690 Plasma users don't have to wait another 6 months for
this to be resolved in kinetic-updates.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dave   7291 F wireplumber
 /dev/snd/controlC1:  dave   7291 F wireplumber
 /dev/snd/seq:dave   7288 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Mon Jan 23 10:57:51 2023
InstallationDate: Installed on 2022-05-03 (264 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to kinetic on 2022-12-02 (52 days ago)
dmi.bios.date: 03/21/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.31
dmi.board.asset.tag: Default string
dmi.board.name: MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.31:bd03/21/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGZ690TOMAHAWKWIFIDDR4(MS-7D32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D32
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

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

Title:
  Fix Plasma + Realtek ALC4080 USB audio device support

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Audio does not work on the MSI Z690 TOMAHAWK WIFI DDR4 (MS-7D32)
  motherboard when using Kubuntu 22.10 due to Realtek ALC4080 USB audio
  device issues.  Earlier ALC4080 problems were resolved against Gnome
  but under Plasma desktop it's still broken due to a pipewire problem.

  This patch
  https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1429
  resolves the issue and has been merged to pipewire master.  Please
  patch kinetic so MSI Z690 Plasma users don't have to wait another 6
  months for this to be resolved in kinetic-updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   7291 F wireplumber
   /dev/snd/controlC1:  dave   7291 F wireplumber
   /dev/snd/seq:dave   7288 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon Jan 23 10:57:51 2023
  InstallationDate: Installed on 2022-05-03 (264 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-12-02 (52 days ago)
  dmi.bios.date: 03/21/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.31
  dmi.board.asset.tag: Default string
  dmi.board.name: MAG Z690 TOMAHAWK WIFI DDR4 (MS-7D32)
  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: 

[Desktop-packages] [Bug 2003735] Re: [SRU] libreoffice 7.4.4 updates for kinetic

[Rico Tzschichholz]

** Bug watch added: Document Foundation Bugzilla #153059
   https://bugs.documentfoundation.org/show_bug.cgi?id=153059

** Also affects: df-libreoffice via
   https://bugs.documentfoundation.org/show_bug.cgi?id=153059
   Importance: Unknown
   Status: Unknown

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

Title:
  [SRU] libreoffice 7.4.4 updates for kinetic

Status in LibreOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Kinetic:
  In Progress
Status in libreoffice source package in Lunar:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release
   https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1

   * It includes one crash fix for 
https://bugs.documentfoundation.org/show_bug.cgi?id=153059
   
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1=ef02234e55c1ca0890b6882fb2d9a33328cbb88e

   * This SRU will cherry-pick this specific patch only.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1604/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

  [Regression Potential]

   * This is well defined and upstream tested patch to fix a specific
  crash.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/2003735/+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 2003735] Re: [SRU] libreoffice 7.4.4 updates for kinetic

[Rico Tzschichholz]

** Also affects: libreoffice (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu Lunar)
   Status: New => In Progress

** Changed in: libreoffice (Ubuntu Lunar)
   Importance: Undecided => Medium

** Changed in: libreoffice (Ubuntu Lunar)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

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

Title:
  [SRU] libreoffice 7.4.4 updates for kinetic

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Kinetic:
  In Progress
Status in libreoffice source package in Lunar:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release
   https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1

   * It includes one crash fix for 
https://bugs.documentfoundation.org/show_bug.cgi?id=153059
   
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1=ef02234e55c1ca0890b6882fb2d9a33328cbb88e

   * This SRU will cherry-pick this specific patch only.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1604/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

  [Regression Potential]

   * This is well defined and upstream tested patch to fix a specific
  crash.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/+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 2003735] Re: [SRU] libreoffice 7.4.4 updates for kinetic

[Rico Tzschichholz]

** Patch added: "libreoffice_7.4.4-0ubuntu0.22.10.2.patch"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/+attachment/5643032/+files/libreoffice_7.4.4-0ubuntu0.22.10.2.patch

** Description changed:

  [Impact]
  
   * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release
+  https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1
  
   * It includes one crash fix for 
https://bugs.documentfoundation.org/show_bug.cgi?id=153059
-  
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1=ef02234e55c1ca0890b6882fb2d9a33328cbb88e
+  
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1=ef02234e55c1ca0890b6882fb2d9a33328cbb88e
  
-  * This SRU will cherry-pick this specific patch only.
+  * This SRU will cherry-pick this specific patch only.
  
  [Testing]
  
   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).
  
    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1604/
  
    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
  
  [Regression Potential]
  
   * This is well defined and upstream tested patch to fix a specific
  crash.
  
   * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

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

Title:
  [SRU] libreoffice 7.4.4 updates for kinetic

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Kinetic:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release
   https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1

   * It includes one crash fix for 
https://bugs.documentfoundation.org/show_bug.cgi?id=153059
   
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1=ef02234e55c1ca0890b6882fb2d9a33328cbb88e

   * This SRU will cherry-pick this specific patch only.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1604/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

  [Regression Potential]

   * This is well defined and upstream tested patch to fix a specific
  crash.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/+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 2003735] [NEW] [SRU] libreoffice 7.4.4 updates for kinetic

[Rico Tzschichholz]

Public bug reported:

[Impact]

 * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line:
 https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release
 https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1

 * It includes one crash fix for 
https://bugs.documentfoundation.org/show_bug.cgi?id=153059
 
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1=ef02234e55c1ca0890b6882fb2d9a33328cbb88e

 * This SRU will cherry-pick this specific patch only.

[Testing]

 * Upstream testing. Bugs fixed upstream typically include
unit/regression tests, and the release itself is extensively exercised
(both in an automated manner and manually).

  * A recent set of upstream's automated jenkins testing can be found here:
https://ci.libreoffice.org/job/gerrit_74/1604/

  * More information about the upstream QA testing can be found here:
* Automated tests
  https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests
  https://wiki.documentfoundation.org/Development/UITests
* Regression tests
  https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests
  https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

[Regression Potential]

 * This is well defined and upstream tested patch to fix a specific
crash.

 * A combination of autopkgtests and careful smoke testing as described
above should provide reasonable confidence that no regressions sneaked
in.

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

** Affects: libreoffice (Ubuntu Kinetic)
 Importance: Critical
 Assignee: Rico Tzschichholz (ricotz)
 Status: In Progress

** Also affects: libreoffice (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu Kinetic)
   Status: New => In Progress

** Changed in: libreoffice (Ubuntu Kinetic)
   Importance: Undecided => Critical

** Changed in: libreoffice (Ubuntu Kinetic)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

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

Title:
  [SRU] libreoffice 7.4.4 updates for kinetic

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Kinetic:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 7.4.5.1 is a hotfix release of the 7.4 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.5_release
   https://cgit.freedesktop.org/libreoffice/core/log/?h=libreoffice-7.4.5.1

   * It includes one crash fix for 
https://bugs.documentfoundation.org/show_bug.cgi?id=153059
   
https://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-7.4.5.1=ef02234e55c1ca0890b6882fb2d9a33328cbb88e

   * This SRU will cherry-pick this specific patch only.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_74/1604/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

  [Regression Potential]

   * This is well defined and upstream tested patch to fix a specific
  crash.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2003735/+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 2003649] Re: Illegal block number passed to ext2fs_test_block_bitmap

[geole0]

Hello
Case with size 32 blocks. 21,4% of files are not identified

** Attachment added: "CR execution"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+attachment/5643031/+files/Debugfs-4.txt

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

Title:
  Illegal block number passed to ext2fs_test_block_bitmap

Status in evince package in Ubuntu:
  New

Bug description:
  Hello
  I am trying to understand how the three commands testb, icheck and ncheck of 
the debugfs command work.
  My goal is to use them to find all the sectors allocated to a file.
  For this, I created a test set consisting of a 100% full EXT4 partition 
containing only one file.
  Here are the features:

  mount /dev/sda9 /mnt/TEST
  df --block-size=512 -text4 | grep TEST
  /dev/sda94245641392  0 100% /mnt/TEST
   
  So I think there are only 1064 (42456-41392) unused sectors. To check it, I 
make this script:
  rm -v testb.in
  for ((k=1;k<42457;k++));do
  echo   testb $k >>testb.in
  done
  debugfs -f testb.in /dev/sda9 > testb.out 2>err

  then I control
  head -2 testb.out; tail -2 testb.out ; head -2 err; tail -1 err
  debugfs: testb 1
  Block 1 marked in use
  debugfs: testb 42456
  Block 42456 not in use
  debugfs 1.46.5 (30-Dec-2021)
  Illegal block number passed to ext2fs_test_block_bitmap #6656 for block 
bitmap for /dev/sda9
  Illegal block number passed to ext2fs_test_block_bitmap #42456 for block 
bitmap for /dev/sda9

  
  I can only find this reported incident:  
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1487787

  
  grep "Illegal block number passed to ext2fs_test_block_bitmap" err | wc -l
  35801

  i.e. 84% rejection. The rest of the treatment will not be good

  grep "marked in use" testb.out | wc -l
  6522

  grep "not in use" testb.out | wc -l
  35934
   
  I don't know if it's because of a missing option, misuse or malfunction of 
the command.

  thank you for looking into the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 22 16:18:03 2023
  InstallationDate: Installed on 2022-02-16 (339 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (156 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+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 2003649] Re: Illegal block number passed to ext2fs_test_block_bitmap

[geole0]

Hello
Case with size 16 blocks. 25% of files are not identified

** Attachment added: "CR execution"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+attachment/5643030/+files/Debugfs-2.txt

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

Title:
  Illegal block number passed to ext2fs_test_block_bitmap

Status in evince package in Ubuntu:
  New

Bug description:
  Hello
  I am trying to understand how the three commands testb, icheck and ncheck of 
the debugfs command work.
  My goal is to use them to find all the sectors allocated to a file.
  For this, I created a test set consisting of a 100% full EXT4 partition 
containing only one file.
  Here are the features:

  mount /dev/sda9 /mnt/TEST
  df --block-size=512 -text4 | grep TEST
  /dev/sda94245641392  0 100% /mnt/TEST
   
  So I think there are only 1064 (42456-41392) unused sectors. To check it, I 
make this script:
  rm -v testb.in
  for ((k=1;k<42457;k++));do
  echo   testb $k >>testb.in
  done
  debugfs -f testb.in /dev/sda9 > testb.out 2>err

  then I control
  head -2 testb.out; tail -2 testb.out ; head -2 err; tail -1 err
  debugfs: testb 1
  Block 1 marked in use
  debugfs: testb 42456
  Block 42456 not in use
  debugfs 1.46.5 (30-Dec-2021)
  Illegal block number passed to ext2fs_test_block_bitmap #6656 for block 
bitmap for /dev/sda9
  Illegal block number passed to ext2fs_test_block_bitmap #42456 for block 
bitmap for /dev/sda9

  
  I can only find this reported incident:  
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1487787

  
  grep "Illegal block number passed to ext2fs_test_block_bitmap" err | wc -l
  35801

  i.e. 84% rejection. The rest of the treatment will not be good

  grep "marked in use" testb.out | wc -l
  6522

  grep "not in use" testb.out | wc -l
  35934
   
  I don't know if it's because of a missing option, misuse or malfunction of 
the command.

  thank you for looking into the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 22 16:18:03 2023
  InstallationDate: Installed on 2022-02-16 (339 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (156 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+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 2003649] Re: Illegal block number passed to ext2fs_test_block_bitmap

[geole0]

Hello
Case with size 8 blocks. 9% of files are not identified

** Attachment added: "CR execution"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+attachment/5643029/+files/Debugfs-3.txt

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

Title:
  Illegal block number passed to ext2fs_test_block_bitmap

Status in evince package in Ubuntu:
  New

Bug description:
  Hello
  I am trying to understand how the three commands testb, icheck and ncheck of 
the debugfs command work.
  My goal is to use them to find all the sectors allocated to a file.
  For this, I created a test set consisting of a 100% full EXT4 partition 
containing only one file.
  Here are the features:

  mount /dev/sda9 /mnt/TEST
  df --block-size=512 -text4 | grep TEST
  /dev/sda94245641392  0 100% /mnt/TEST
   
  So I think there are only 1064 (42456-41392) unused sectors. To check it, I 
make this script:
  rm -v testb.in
  for ((k=1;k<42457;k++));do
  echo   testb $k >>testb.in
  done
  debugfs -f testb.in /dev/sda9 > testb.out 2>err

  then I control
  head -2 testb.out; tail -2 testb.out ; head -2 err; tail -1 err
  debugfs: testb 1
  Block 1 marked in use
  debugfs: testb 42456
  Block 42456 not in use
  debugfs 1.46.5 (30-Dec-2021)
  Illegal block number passed to ext2fs_test_block_bitmap #6656 for block 
bitmap for /dev/sda9
  Illegal block number passed to ext2fs_test_block_bitmap #42456 for block 
bitmap for /dev/sda9

  
  I can only find this reported incident:  
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1487787

  
  grep "Illegal block number passed to ext2fs_test_block_bitmap" err | wc -l
  35801

  i.e. 84% rejection. The rest of the treatment will not be good

  grep "marked in use" testb.out | wc -l
  6522

  grep "not in use" testb.out | wc -l
  35934
   
  I don't know if it's because of a missing option, misuse or malfunction of 
the command.

  thank you for looking into the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 22 16:18:03 2023
  InstallationDate: Installed on 2022-02-16 (339 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (156 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+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 2003732] [NEW] Update mutter to 43.2

[Jeremy Bicha]

Public bug reported:

Impact
--
There is a new bugfix release in the stable 43 series.
https://gitlab.gnome.org/GNOME/mutter/-/blob/43.2/NEWS

The current version in Ubuntu 22.10 is 43.0

Test Case
-
Complete the test case from

https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

What Could Go Wrong
---
Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

A severe enough bug could mean that people are unable to use their
desktop version of Ubuntu.

Smaller bugs could interrupt people's workflows.

mutter is part of GNOME Core and is included in the GNOME micro release
exception

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Other Info
--
This update introduces a behavior change. Fullscreen apps can no longer be 
transparent or translucent. However, this behavior change was made to comply 
with the Wayland spec and better protects against apps trying to work around 
intentional Wayland restrictions. See the upstream bugs for 
https://launchpad.net/bugs/2003104 for more background.

** Affects: mutter (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: mutter (Ubuntu Kinetic)
 Importance: High
 Status: Triaged


** Tags: kinetic upgrade-software-version

** Also affects: mutter (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

** Changed in: mutter (Ubuntu Kinetic)
   Status: New => Triaged

** Description changed:

  Impact
  --
  There is a new bugfix release in the stable 43 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/43.2/NEWS
  
  The current version in Ubuntu 22.10 is 43.0
  
  Test Case
  -
  Complete the test case from
  
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter
  
  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.
  
  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.
  
  Smaller bugs could interrupt people's workflows.
  
  mutter is part of GNOME Core and is included in the GNOME micro release
  exception
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
+ 
+ Other Info
+ --
+ This update introduces a behavior change. Fullscreen apps can no longer be 
transparent or translucent. However, this behavior change was made to comply 
with the Wayland spec and better protects against apps trying to work around 
intentional Wayland restrictions. See the upstream bugs for 
https://launchpad.net/bugs/2003104 for more background.

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

Title:
  Update mutter to 43.2

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Kinetic:
  Triaged

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 43 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/43.2/NEWS

  The current version in Ubuntu 22.10 is 43.0

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  This update introduces a behavior change. Fullscreen apps can no longer be 
transparent or translucent. However, this behavior change was made to comply 
with the Wayland spec and better protects against apps trying to work around 
intentional Wayland restrictions. See the upstream bugs for 
https://launchpad.net/bugs/2003104 for more background.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003732/+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 2003726] [NEW] pipewire-pulse unnecessarily recommends pipewire-alsa to emulate pulseaudio's packaging

[Erich Eickmeyer]

Public bug reported:

Reported to Debian: https://bugs.debian.org/1029377

pipewire-pulse and pulseaudio can be co-installed on a system, but if
both are installed at once, the "Recommends: pipewire-alsa" line in
pipewire-pulse creates a situation where the dependency cannot be
resolved due to a conflict between pipewire-alsa and pulseaudio. This is
especially true when both are being seeded in Ubuntu Studio with the
intent of being switchable via services with a utility such as Studio
Controls.

This also causes a regression in https://bugs.debian.org/1020903 in
which a conflict existed between pipewire-pulse and pulseaudio that was
unnecessary because, as stated in the bug report, both can be installed
simultaneously and enabled/disabled via services.

If Debian does not resolve this upstream, I recommend we fix this in our
own packaging as to not break workflows. Professional audio users cannot
use the pipewire-jack system as it does not provide the right kind of
functionality for some hardware, which is why the switch was to be
implemented. For example, the alsa backend for jack must be disabled for
some firewire devices which require the FFADO backend instead.

This has been resolved, hopefully temporarily, by removing pulseaudio
from Ubuntu Studio's seed. We hope to bring it back, but this issue has
caused some very unfortunate issues that will become workflow issues for
our users.

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

** Affects: pipewire (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #1029377
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029377

** Also affects: pipewire (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029377
   Importance: Unknown
   Status: Unknown

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

Title:
  pipewire-pulse unnecessarily recommends pipewire-alsa to emulate
  pulseaudio's packaging

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

Bug description:
  Reported to Debian: https://bugs.debian.org/1029377

  pipewire-pulse and pulseaudio can be co-installed on a system, but if
  both are installed at once, the "Recommends: pipewire-alsa" line in
  pipewire-pulse creates a situation where the dependency cannot be
  resolved due to a conflict between pipewire-alsa and pulseaudio. This
  is especially true when both are being seeded in Ubuntu Studio with
  the intent of being switchable via services with a utility such as
  Studio Controls.

  This also causes a regression in https://bugs.debian.org/1020903 in
  which a conflict existed between pipewire-pulse and pulseaudio that
  was unnecessary because, as stated in the bug report, both can be
  installed simultaneously and enabled/disabled via services.

  If Debian does not resolve this upstream, I recommend we fix this in
  our own packaging as to not break workflows. Professional audio users
  cannot use the pipewire-jack system as it does not provide the right
  kind of functionality for some hardware, which is why the switch was
  to be implemented. For example, the alsa backend for jack must be
  disabled for some firewire devices which require the FFADO backend
  instead.

  This has been resolved, hopefully temporarily, by removing pulseaudio
  from Ubuntu Studio's seed. We hope to bring it back, but this issue
  has caused some very unfortunate issues that will become workflow
  issues for our users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2003726/+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 1993214] Re: [jammy] Update gjs to 1.74 using mozjs102 102.3

[Jeremy Bicha]

I installed gjs 1.74.0-0ubuntu1 (which pulled in libmozjs-102-0) on
Ubuntu 22.04 LTS and successfully completed Test Case 1 and Test Case 2
from https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

I installed libmozjs-102-0 102.6.0-0ubuntu0.22.10.1 on Ubuntu 22.10 and
successfully completed Test Case 1 and Test Case 2 from
https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

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

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

Title:
  [jammy] Update gjs to 1.74 using mozjs102 102.3

Status in gjs package in Ubuntu:
  Fix Released
Status in mozjs102 package in Ubuntu:
  Fix Released
Status in gjs source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Jammy:
  Fix Committed
Status in mozjs102 source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  --
  GNOME Shell uses the SpiderMonkey JavaScript engine from Firefox ESR (mozjs). 
Firefox 92 ESR has reached end of life; therefore, we should switch to the 102 
ESR series for security updates for the next year.

  This requires updating gjs from 1.72 to 1.74 from GNOME 43, as
  packaged in Ubuntu 22.10.

  This will be done as a Security Update.

  Updating mozjs in stable Ubuntu releases was recommended when Ubuntu
  first switched back to GNOME, but this is the first time it's been
  done.

  Security Impact
  ---
  I looked through
  https://github.com/mozilla/gecko-dev/commits/esr102/js
  and searched for referenced bug numbers in
  https://www.mozilla.org/en-US/security/advisories/
  for Firefox ESR releases since Ubuntu's 91.10

  and found one CVE. Also, there's the vague Mozilla Bug 1771084 (no CVE
  issued) mentioned at

  https://www.mozilla.org/en-US/security/advisories/mfsa2022-24/

  Uploaded Packages
  -
  We will introduce mozjs102, a new source package for Ubuntu 22.04 LTS, being 
careful to publish it in main, not universe.
  And we'll update gjs.
  No other packages need to be updated for this change.
  mozjs91 will remain in Ubuntu 22.04 LTS (source package removals are 
generally not possible), but nothing else in Ubuntu uses it.

  Test Case
  -
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs

  Security Sponsoring
  ---
  sudo apt install git-buildpackage
  gbp clone https://salsa.debian.org/gnome-team/gjs
  cd gjs
  git checkout ubuntu/jammy
  gbp buildpackage --git-builder="debuild -S -nc"

  mkdir ../tarballs; cd ../tarballs
  pull-lp-source mozjs102 kinetic
  cd ..
  gbp clone https://salsa.debian.org/gnome-team/mozjs
  cd mozjs
  git checkout ubuntu/102/jammy
  gbp buildpackage --git-builder="debuild --no-lintian -S -nc" 
--git-tarball-dir=../tarballs
  # That avoids needing to recreate the original tarball from pristine-tar 
which takes a while. Also, running lintian takes a while.

  Initial Testing Done
  
  I built the packages in my PPA.
  I installed the packages on Ubuntu 22.04 LTS and successfully completed the 
Test Case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1993214/+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 2003715] [NEW] "Unable to open document", "PDF document is damaged" when opening a DocuSigned document

[Tomislav]

Public bug reported:

Got a document to sign via DocuSign. Signed it, followed the "view
completed document" link provided by DocuSign, downloaded the "combined"
document.

Observed behaviour: Firefox opens the PDF without issue, evince fails.

Expected behaviour: evince opens the document without an error, just
like Firefox.

Don't know how repeatable this is, can't attach the document because of
its contents, can't generate a new one. I hope an example of a DocuSign-
ed document can be found on-line to help reproduce the issue.

Workarounds: use another PDF viewer

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evince 3.28.4-0ubuntu1.2
ProcVersionSignature: Ubuntu 5.4.0-136.153~18.04.1-generic 5.4.218
Uname: Linux 5.4.0-136-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 23 15:03:03 2023
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2018-05-10 (1719 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
SourcePackage: evince
UpgradeStatus: Upgraded to bionic on 2020-03-04 (1055 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  "Unable to open document", "PDF document is damaged" when opening a
  DocuSigned document

Status in evince package in Ubuntu:
  New

Bug description:
  Got a document to sign via DocuSign. Signed it, followed the "view
  completed document" link provided by DocuSign, downloaded the
  "combined" document.

  Observed behaviour: Firefox opens the PDF without issue, evince fails.

  Expected behaviour: evince opens the document without an error, just
  like Firefox.

  Don't know how repeatable this is, can't attach the document because
  of its contents, can't generate a new one. I hope an example of a
  DocuSign-ed document can be found on-line to help reproduce the issue.

  Workarounds: use another PDF viewer

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.4-0ubuntu1.2
  ProcVersionSignature: Ubuntu 5.4.0-136.153~18.04.1-generic 5.4.218
  Uname: Linux 5.4.0-136-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 23 15:03:03 2023
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (1719 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: evince
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (1055 days ago)

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


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

[Desktop-packages] [Bug 2001922] Re: Xorg crash

[pd]

Uh, did not have time for this until now, got quite a few crashes in the
meantime. I am attaching the latest xorg log that gives a backtrace


** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2001922/+attachment/5642994/+files/Xorg.0.log.old

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

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

  There are files in /var/crash/

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

  
  and .xsession-errors.old ends with

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

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

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

[Desktop-packages] [Bug 2003703] Re: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

[Tom Lavin]

Thank you, in advance, for your line by line assistance in helping me.
electron_...@protonmail.com

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

Title:
  package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libxcb package in Ubuntu:
  New

Bug description:
  I have tried to fix but to no avail.
  Please send fix to electron_...@protonmail.com

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libxcb-record0:amd64 1.14-3ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  AptOrdering:
   python3-setuptools:amd64: Install
   python3-pkg-resources:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Mon Jan 23 06:19:00 2023
  DistUpgraded: 2022-12-30 12:11:30,358 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libxcb-record0:amd64:1.14-3ubuntu3
   Setting up python3-setuptools (59.6.0-1.2ubuntu0.22.04.1) ...
   dpkg: error processing package libxcb-record0:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0505]
  InstallationDate: Installed on 2022-09-16 (128 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. Inspiron N5040
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=d2132e07-1c79-4672-8cc8-f180b680d7ba ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: libxcb
  Title: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to jammy on 2022-12-30 (23 days ago)
  dmi.bios.date: 08/22/2011
  dmi.bios.release: 254.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0THYJV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.ec.firmware.release: 254.3
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/22/2011:br254.3:efr254.3:svnDellInc.:pnInspironN5040:pvrA03:rvnDellInc.:rn0THYJV:rvrA03:cvnDellInc.:ct8:cvrA03:skuTobefilledbyO.E.M.:
  dmi.product.name: Inspiron N5040
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/2003703/+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 2003703] [NEW] package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[Tom Lavin]

Public bug reported:

I have tried to fix but to no avail.
Please send fix to electron_...@protonmail.com

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libxcb-record0:amd64 1.14-3ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
AptOrdering:
 python3-setuptools:amd64: Install
 python3-pkg-resources:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
Date: Mon Jan 23 06:19:00 2023
DistUpgraded: 2022-12-30 12:11:30,358 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DuplicateSignature:
 package:libxcb-record0:amd64:1.14-3ubuntu3
 Setting up python3-setuptools (59.6.0-1.2ubuntu0.22.04.1) ...
 dpkg: error processing package libxcb-record0:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0505]
InstallationDate: Installed on 2022-09-16 (128 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Dell Inc. Inspiron N5040
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=d2132e07-1c79-4672-8cc8-f180b680d7ba ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: libxcb
Title: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to jammy on 2022-12-30 (23 days ago)
dmi.bios.date: 08/22/2011
dmi.bios.release: 254.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0THYJV
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A03
dmi.ec.firmware.release: 254.3
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/22/2011:br254.3:efr254.3:svnDellInc.:pnInspironN5040:pvrA03:rvnDellInc.:rn0THYJV:rvrA03:cvnDellInc.:ct8:cvrA03:skuTobefilledbyO.E.M.:
dmi.product.name: Inspiron N5040
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: A03
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-package jammy ubuntu

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

Title:
  package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libxcb package in Ubuntu:
  New

Bug description:
  I have tried to fix but to no avail.
  Please send fix to electron_...@protonmail.com

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libxcb-record0:amd64 1.14-3ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  AptOrdering:
   python3-setuptools:amd64: Install
   python3-pkg-resources:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Mon Jan 23 06:19:00 2023
  DistUpgraded: 2022-12-30 12:11:30,358 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libxcb-record0:amd64:1.14-3ubuntu3
   Setting up python3-setuptools (59.6.0-1.2ubuntu0.22.04.1) ...
   dpkg: error processing package libxcb-record0:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Core Processor Integrated Graphics 

[Desktop-packages] [Bug 2003703] Re: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libxcb package in Ubuntu:
  New

Bug description:
  I have tried to fix but to no avail.
  Please send fix to electron_...@protonmail.com

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libxcb-record0:amd64 1.14-3ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  AptOrdering:
   python3-setuptools:amd64: Install
   python3-pkg-resources:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  Date: Mon Jan 23 06:19:00 2023
  DistUpgraded: 2022-12-30 12:11:30,358 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libxcb-record0:amd64:1.14-3ubuntu3
   Setting up python3-setuptools (59.6.0-1.2ubuntu0.22.04.1) ...
   dpkg: error processing package libxcb-record0:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0505]
  InstallationDate: Installed on 2022-09-16 (128 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. Inspiron N5040
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=d2132e07-1c79-4672-8cc8-f180b680d7ba ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: libxcb
  Title: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to jammy on 2022-12-30 (23 days ago)
  dmi.bios.date: 08/22/2011
  dmi.bios.release: 254.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0THYJV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.ec.firmware.release: 254.3
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/22/2011:br254.3:efr254.3:svnDellInc.:pnInspironN5040:pvrA03:rvnDellInc.:rn0THYJV:rvrA03:cvnDellInc.:ct8:cvrA03:skuTobefilledbyO.E.M.:
  dmi.product.name: Inspiron N5040
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/2003703/+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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

[Launchpad Bug Tracker]

This bug was fixed in the package language-selector - 0.219.1

---
language-selector (0.219.1) jammy; urgency=medium

  * data/pkg_depends, fontconfig/64-language-selector-prefer.conf:
- Make Noto Sans Sinhala and Noto Serif Sinhala default fonts for
  rendering Sinhala (LP: #2000551).

 -- Gunnar Hjalmarsson   Wed, 28 Dec 2022 20:41:53
+0100

** Changed in: language-selector (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  [System Fonts] Replace default sinhala font from LKLUG to Noto

Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in language-selector source package in Jammy:
  Fix Released
Status in language-selector source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG,
  and that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.

  [ Test Plan ]

  * Install language-selector-[common,gnome] from
  [jammy,kinetic]-proposed.

  * Open Language Support and install the Sinhala language.

  * Open a terminal window and run this command:

    fc-match -a | grep -E 'LKLUG|Sinhala'

  * Confirm that Noto Sans Sinhala is listed before LKLUG.

  * Close Firefox and re-open it.

  * Visit e.g. https://si.wikipedia.org and confirm the
    improvement. (Also I (Gunnar), who don't speak Sinhala,
    notice a remarkable difference.)

  [ Where problems could occur ]

  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise
  ought to make them happy. :)

  Please note Robie Basak's warning about the changed font metrics in
  comment #7, though.

  [ Original description ]

  **What's the problem?**

  Currently ubuntu comes with LKLUG font for sinhala (si). it's not
  clear. e.g. we cannot recognize vowel signs and read websites using
  that font. We can change it manually but such changes do not apply to
  some applications or application types e.g. snap apps etc.

  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug

  **What expected to happen?**

  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]

  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]

  **Additional details**

  Screenshots (see the difference: LKLUG/Noto)

  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg

  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg

  If you need more examples or clarifications, please add a comment

  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/

  Also, some developers already have designed tools, scripts for that problem 
however many people do not try to find these scripts and switch to other OS
  1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache)
  2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79
  3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer

  Please review details, screenshots and posts. This is not a personal
  opinion and atleast, i expect to see this change in the next interim
  or LTS release.

  Furthermore, please let me know if i can help to speed-up this
  replacement process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

[Launchpad Bug Tracker]

This bug was fixed in the package language-selector - 0.219.22.10.1

---
language-selector (0.219.22.10.1) kinetic; urgency=medium

  * data/pkg_depends, fontconfig/64-language-selector-prefer.conf:
- Make Noto Sans Sinhala and Noto Serif Sinhala default fonts for
  rendering Sinhala (LP: #2000551).

 -- Gunnar Hjalmarsson   Thu, 05 Jan 2023 14:01:47
+0100

** Changed in: language-selector (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  [System Fonts] Replace default sinhala font from LKLUG to Noto

Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in language-selector source package in Jammy:
  Fix Committed
Status in language-selector source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG,
  and that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.

  [ Test Plan ]

  * Install language-selector-[common,gnome] from
  [jammy,kinetic]-proposed.

  * Open Language Support and install the Sinhala language.

  * Open a terminal window and run this command:

    fc-match -a | grep -E 'LKLUG|Sinhala'

  * Confirm that Noto Sans Sinhala is listed before LKLUG.

  * Close Firefox and re-open it.

  * Visit e.g. https://si.wikipedia.org and confirm the
    improvement. (Also I (Gunnar), who don't speak Sinhala,
    notice a remarkable difference.)

  [ Where problems could occur ]

  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise
  ought to make them happy. :)

  Please note Robie Basak's warning about the changed font metrics in
  comment #7, though.

  [ Original description ]

  **What's the problem?**

  Currently ubuntu comes with LKLUG font for sinhala (si). it's not
  clear. e.g. we cannot recognize vowel signs and read websites using
  that font. We can change it manually but such changes do not apply to
  some applications or application types e.g. snap apps etc.

  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug

  **What expected to happen?**

  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]

  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]

  **Additional details**

  Screenshots (see the difference: LKLUG/Noto)

  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg

  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg

  If you need more examples or clarifications, please add a comment

  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/

  Also, some developers already have designed tools, scripts for that problem 
however many people do not try to find these scripts and switch to other OS
  1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache)
  2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79
  3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer

  Please review details, screenshots and posts. This is not a personal
  opinion and atleast, i expect to see this change in the next interim
  or LTS release.

  Furthermore, please let me know if i can help to speed-up this
  replacement process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+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 1999098] Re: Update glib to 2.74.3

[Launchpad Bug Tracker]

This bug was fixed in the package glib2.0 - 2.74.3-0ubuntu1

---
glib2.0 (2.74.3-0ubuntu1) kinetic; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release (LP: #1999098)

  [ Simon McVittie ]
  * d/patches: Drop patches that were applied upstream
  * d/rules, d/watch, d/copyright: Bundle source for Unicode files

 -- Jeremy Bicha   Wed, 07 Dec 2022 20:17:41 -0500

** Changed in: glib2.0 (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  Update glib to 2.74.3

Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in glib2.0 source package in Kinetic:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 2.74 series

  The current release in Ubuntu 22.10 is 2.74.0

  https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS

  Test Case 1
  ---
  glib has an extensive test suite.

  Failing tests will fail the build.
  This update will also trigger a lot of autopkgtests.

  Ensure that there aren't autopgktest regressions triggered by this
  update and that the builds complete successfully

  Test Case 2
  ---
  Pretty much all parts of GNOME use GLib, so test anything in the desktop that 
you can. If you reboot the machine and can get to the desktop, that's already 
tested GLib extensively. But also run applications like the terminal, the file 
browser and epiphany-browser

  Test Case 3 (Extra)
  --
  Install gnome-characters 43.1. (This is being SRU'd, but the version from 
Lunar also works.)
  Open the Characters app.
  Use the search feature to search for "moose"
  A moose emoji should show up. This is one of the new Emoji 15.
  https://blog.emojipedia.org/whats-new-in-unicode-15-0/

  With glib 2.74.0, the moose emoji won't be searchable but it does show
  in the Animals category.

  What Could Go Wrong
  ---
  This update contains fixes in multiple places so multiple apps could be 
affected. The consequences of a broken GLib can range from some functions 
returning bad results sometimes, which have minimal runtime implications, up to 
the system simply crashing all the time.

  Other Info
  --
  Unicode 15 enablement was granted a User Interface Freeze Exception for 
Ubuntu 22.10: https://launchpad.net/bugs/1989626

  glib and gnome-characters are the only 2 late pieces that the Ubuntu
  Desktop team plans to SRU for Ubuntu 22.10.

  Ubuntu 23.04 has 2.74.2 with the commits from 2.74.3 backported so
  they are functionally equivalent. Ubuntu 23.04 will get newer glib
  versions before 23.04 is released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1999098/+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 1999098] Update Released

[Łukasz Zemczak]

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

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

Title:
  Update glib to 2.74.3

Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in glib2.0 source package in Kinetic:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 2.74 series

  The current release in Ubuntu 22.10 is 2.74.0

  https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS

  Test Case 1
  ---
  glib has an extensive test suite.

  Failing tests will fail the build.
  This update will also trigger a lot of autopkgtests.

  Ensure that there aren't autopgktest regressions triggered by this
  update and that the builds complete successfully

  Test Case 2
  ---
  Pretty much all parts of GNOME use GLib, so test anything in the desktop that 
you can. If you reboot the machine and can get to the desktop, that's already 
tested GLib extensively. But also run applications like the terminal, the file 
browser and epiphany-browser

  Test Case 3 (Extra)
  --
  Install gnome-characters 43.1. (This is being SRU'd, but the version from 
Lunar also works.)
  Open the Characters app.
  Use the search feature to search for "moose"
  A moose emoji should show up. This is one of the new Emoji 15.
  https://blog.emojipedia.org/whats-new-in-unicode-15-0/

  With glib 2.74.0, the moose emoji won't be searchable but it does show
  in the Animals category.

  What Could Go Wrong
  ---
  This update contains fixes in multiple places so multiple apps could be 
affected. The consequences of a broken GLib can range from some functions 
returning bad results sometimes, which have minimal runtime implications, up to 
the system simply crashing all the time.

  Other Info
  --
  Unicode 15 enablement was granted a User Interface Freeze Exception for 
Ubuntu 22.10: https://launchpad.net/bugs/1989626

  glib and gnome-characters are the only 2 late pieces that the Ubuntu
  Desktop team plans to SRU for Ubuntu 22.10.

  Ubuntu 23.04 has 2.74.2 with the commits from 2.74.3 backported so
  they are functionally equivalent. Ubuntu 23.04 will get newer glib
  versions before 23.04 is released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1999098/+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 1999100] Update Released

[Łukasz Zemczak]

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

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

Title:
  Update gnome-characters to 43.1

Status in gnome-characters package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Kinetic:
  Fix Released

Bug description:
  NOTE TO SRU TEAM
  
  Please accept the glib2.0 SRU first. To enable the new feature to work best, 
I have added a Build-Depends (which results in a Depends) on the new glib 
version.

  Impact
  --
  There is a new bugfix release in the stable 43 series

  https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/43.1/NEWS

  This adds one new feature: new emoji and Unicode characters from
  Unicode 15.

  Test Case 1
  ---
  Install the update
  Open the Characters app.
  Select an emoji character and click Copy Character
  Paste the emoji somewhere.
  You should see the emoji you pasted.

  Test Case 2
  ---
  Open the Characters app.
  Use the search feature to search for "moose"
  A moose emoji should show up. This is one of the new Emoji 15.
  https://blog.emojipedia.org/whats-new-in-unicode-15-0/

  (This is Test Case 3 (Extra) from https://launchpad.net/bugs/1999098)

  What Could Go Wrong
  ---
  GNOME Characters is part of GNOME Core and falls under the GNOME Stable 
Release Update microrelease exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  It is installed by default in Ubuntu Desktop and Ubuntu Budgie.

  Other Info
  --
  Unicode 15 enablement was granted a User Interface Freeze Exception for 
Ubuntu 22.10: https://launchpad.net/bugs/1989626

  glib and gnome-characters are the only 2 late pieces that the Ubuntu
  Desktop team plans to SRU for Ubuntu 22.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1999100/+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 1999100] Re: Update gnome-characters to 43.1

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-characters - 43.1-0ubuntu1

---
gnome-characters (43.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1999100)
- Add Unicode 15 characters
  * Bump minimum glib to 2.74.1 for better searching of Unicode 15 characters

 -- Jeremy Bicha   Wed, 07 Dec 2022 20:16:09 -0500

** Changed in: gnome-characters (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-characters to 43.1

Status in gnome-characters package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Kinetic:
  Fix Released

Bug description:
  NOTE TO SRU TEAM
  
  Please accept the glib2.0 SRU first. To enable the new feature to work best, 
I have added a Build-Depends (which results in a Depends) on the new glib 
version.

  Impact
  --
  There is a new bugfix release in the stable 43 series

  https://gitlab.gnome.org/GNOME/gnome-characters/-/blob/43.1/NEWS

  This adds one new feature: new emoji and Unicode characters from
  Unicode 15.

  Test Case 1
  ---
  Install the update
  Open the Characters app.
  Select an emoji character and click Copy Character
  Paste the emoji somewhere.
  You should see the emoji you pasted.

  Test Case 2
  ---
  Open the Characters app.
  Use the search feature to search for "moose"
  A moose emoji should show up. This is one of the new Emoji 15.
  https://blog.emojipedia.org/whats-new-in-unicode-15-0/

  (This is Test Case 3 (Extra) from https://launchpad.net/bugs/1999098)

  What Could Go Wrong
  ---
  GNOME Characters is part of GNOME Core and falls under the GNOME Stable 
Release Update microrelease exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  It is installed by default in Ubuntu Desktop and Ubuntu Budgie.

  Other Info
  --
  Unicode 15 enablement was granted a User Interface Freeze Exception for 
Ubuntu 22.10: https://launchpad.net/bugs/1989626

  glib and gnome-characters are the only 2 late pieces that the Ubuntu
  Desktop team plans to SRU for Ubuntu 22.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1999100/+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 2000551] Update Released

[Łukasz Zemczak]

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

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

Title:
  [System Fonts] Replace default sinhala font from LKLUG to Noto

Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in language-selector source package in Jammy:
  Fix Committed
Status in language-selector source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG,
  and that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.

  [ Test Plan ]

  * Install language-selector-[common,gnome] from
  [jammy,kinetic]-proposed.

  * Open Language Support and install the Sinhala language.

  * Open a terminal window and run this command:

    fc-match -a | grep -E 'LKLUG|Sinhala'

  * Confirm that Noto Sans Sinhala is listed before LKLUG.

  * Close Firefox and re-open it.

  * Visit e.g. https://si.wikipedia.org and confirm the
    improvement. (Also I (Gunnar), who don't speak Sinhala,
    notice a remarkable difference.)

  [ Where problems could occur ]

  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise
  ought to make them happy. :)

  Please note Robie Basak's warning about the changed font metrics in
  comment #7, though.

  [ Original description ]

  **What's the problem?**

  Currently ubuntu comes with LKLUG font for sinhala (si). it's not
  clear. e.g. we cannot recognize vowel signs and read websites using
  that font. We can change it manually but such changes do not apply to
  some applications or application types e.g. snap apps etc.

  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug

  **What expected to happen?**

  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]

  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]

  **Additional details**

  Screenshots (see the difference: LKLUG/Noto)

  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg

  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg

  If you need more examples or clarifications, please add a comment

  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/

  Also, some developers already have designed tools, scripts for that problem 
however many people do not try to find these scripts and switch to other OS
  1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache)
  2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79
  3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer

  Please review details, screenshots and posts. This is not a personal
  opinion and atleast, i expect to see this change in the next interim
  or LTS release.

  Furthermore, please let me know if i can help to speed-up this
  replacement process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+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 2003577] Re: Night Light doesn't get automatically active on second screen when turned on

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1972720, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1972720
   Night light does not work on laptop screen when disconnecting from external 
screen

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

Title:
  Night Light doesn't get automatically active on second screen when
  turned on

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm using a laptop and I close the main screen (from the laptop) when i'm 
connected to a secondary screen. Then at night when it gets activated the Night 
Light if i open the main screen, the Night Light it's not applied to this main 
screen. On the secondary it can be noticed it's activated.
  Deactivating from the menu (corner top right) the Night Light and activating 
it again it fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003577/+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 1995783] Re: Nightlight fails after suspend

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1752680, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1752680
   Night light does not work after resume from suspend or unlock.

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

Title:
  Nightlight fails after suspend

Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Nightlight activates when turned on in settings but after closing the
  lid or otherwise suspending and then resuming power nightlight fails
  to change the color temperature.  Settings still indicates that
  nightlight is on.  If nightlight setting is cycled nightlight works
  again until the next suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.154  Wed Jun 22 04:50:54 
UTC 2022
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1)
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  5 22:03:14 2022
  DistUpgraded: 2022-10-29 22:31:31,858 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/390.154, 5.15.0-52-generic, x86_64: installed
   nvidia/390.154, 5.19.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:212b]
   NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:1247] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GeForce GT 635M [1043:212b]
  InstallationDate: Installed on 2019-01-15 (1390 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: ASUSTeK Computer Inc. N55SL
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=47b67201-d4ee-44d7-adec-9d457d3c9b5c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (6 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SL.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SL
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN55SL.204:bd10/24/2012:br4.6:svnASUSTeKComputerInc.:pnN55SL:pvr1.0:rvnASUSTeKComputerInc.:rnN55SL:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:sku:
  dmi.product.family: N
  dmi.product.name: N55SL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: 

[Desktop-packages] [Bug 1752680] Re: Night light does not work after resume from suspend or unlock.

[Daniel van Vugt]

** Tags added: kinetic

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

Title:
  Night light does not work after resume from suspend or unlock.

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The night light feature does not work in these cases
   * Computer's screen shuts off due to timeout, and then is reactivated.
   * Computer is brought back from suspend
   * Computer desktop is locked, and unlocked using the password

  In all these cases, the night light icon is present in the
  notification area, and it says "Night Light On". But the screen
  temperature is that of normal daylight.

  In all these cases, disabling and re-enabling the night light using
  the notification area icon reactivates the night light.

  Version information

  Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

  4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64
  x86_64 x86_64 GNU/Linux

  17.10 Artful Aardvark

  Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
   /dev/snd/controlC0: talonx 2732 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
  InstallationDate: Installed on 2016-05-05 (659 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Micro-Star International Co., Ltd. GP62 6QE
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash 
acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop 
usbcore.autosuspend=-1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic N/A
   linux-firmware 1.169.3
  Tags: artful
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J5IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP62 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1752680/+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 1972720] Re: Night light does not work on laptop screen when disconnecting from external screen

[Launchpad Bug Tracker]

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

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

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

Title:
  Night light does not work on laptop screen when disconnecting from
  external screen

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When I turn on my laptop while it is connected to an external screen
  (my display settings are such that only the external screen is used
  while it is connected) and later disconnect it, Night Light does not
  work on the laptop screen (it did on the external screen). I have
  Night Light on "Manual Schedule" from 00:00 to 23:59 so it would
  always be on. Turning the Night Light setting off and on again does
  not help.

  After restarting the laptop while it is not connected to the external
  screen, Night Light will work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 21:27:17 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-01-09 (120 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1972720/+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 1972720] Re: Night light does not work on laptop screen when disconnecting from external screen

[Launchpad Bug Tracker]

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

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

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

Title:
  Night light does not work on laptop screen when disconnecting from
  external screen

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When I turn on my laptop while it is connected to an external screen
  (my display settings are such that only the external screen is used
  while it is connected) and later disconnect it, Night Light does not
  work on the laptop screen (it did on the external screen). I have
  Night Light on "Manual Schedule" from 00:00 to 23:59 so it would
  always be on. Turning the Night Light setting off and on again does
  not help.

  After restarting the laptop while it is not connected to the external
  screen, Night Light will work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  9 21:27:17 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-01-09 (120 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1972720/+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 2003577] Re: Night Light doesn't get automatically active on second screen when turned on

[Adolfo Jayme Barrientos]

** Package changed: ubuntu => 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/2003577

Title:
  Night Light doesn't get automatically active on second screen when
  turned on

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm using a laptop and I close the main screen (from the laptop) when i'm 
connected to a secondary screen. Then at night when it gets activated the Night 
Light if i open the main screen, the Night Light it's not applied to this main 
screen. On the secondary it can be noticed it's activated.
  Deactivating from the menu (corner top right) the Night Light and activating 
it again it fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003577/+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 1999216] Re: Secondary monitor tears when connected to a secondary GPU using Wayland

[Daniel van Vugt]

Ubuntu fix proposed here:
https://salsa.debian.org/gnome-team/mutter/-/merge_requests/87

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

Title:
  Secondary monitor tears when connected to a secondary GPU using
  Wayland

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Secondary monitor tears when connected to a secondary GPU using
  Wayland.

  Confirmed locally and first reported in:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1609480

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999216/+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 2003577] Re: Night Light doesn't get automatically active on second screen when turned on

[Daniel van Vugt]

** Tags added: gamma nightlight

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

Title:
  Night Light doesn't get automatically active on second screen when
  turned on

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm using a laptop and I close the main screen (from the laptop) when i'm 
connected to a secondary screen. Then at night when it gets activated the Night 
Light if i open the main screen, the Night Light it's not applied to this main 
screen. On the secondary it can be noticed it's activated.
  Deactivating from the menu (corner top right) the Night Light and activating 
it again it fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003577/+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 2003656] Re: [nvidia] "night light" setting only affects one of 2 used screens

[Daniel van Vugt]

Can you provide a full system log?

  journalctl -b0 > journal.txt


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

Title:
  [nvidia] "night light" setting only affects one of 2 used screens

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have an external display that I declared my primary display (my
  laptop screen being the 2nd one). When night light is applied, it only
  affects the built-in display. It should affect both, otherwise it's
  kind of useless.

  I noticed this just now, no clue how repeatable it is. No known
  workaround (maybe "don't use the computer at night?").

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 22 20:16:01 2023
  InstallationDate: Installed on 2022-11-03 (80 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003656/+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 2003577] [NEW] Night Light doesn't get automatically active on second screen when turned on

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm using a laptop and I close the main screen (from the laptop) when i'm 
connected to a secondary screen. Then at night when it gets activated the Night 
Light if i open the main screen, the Night Light it's not applied to this main 
screen. On the secondary it can be noticed it's activated.
Deactivating from the menu (corner top right) the Night Light and activating it 
again it fix it.

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


** Tags: bot-comment
-- 
Night Light doesn't get automatically active on second screen when turned on
https://bugs.launchpad.net/bugs/2003577
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 2003656] Re: [nvidia] "night light" setting only affects one of 2 used screens

[Daniel van Vugt]

See also https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nightlight

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

Title:
  [nvidia] "night light" setting only affects one of 2 used screens

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have an external display that I declared my primary display (my
  laptop screen being the 2nd one). When night light is applied, it only
  affects the built-in display. It should affect both, otherwise it's
  kind of useless.

  I noticed this just now, no clue how repeatable it is. No known
  workaround (maybe "don't use the computer at night?").

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 22 20:16:01 2023
  InstallationDate: Installed on 2022-11-03 (80 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003656/+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 2003656] Re: "night light" setting only affects one of 2 used screens

[Daniel van Vugt]

It sounds like night light is working on the Intel GPU (laptop screen)
but not on the Nvidia GPU (external monitor).

** Tags added: gamma nightlight

** Tags added: nvidia

** Summary changed:

- "night light" setting only affects one of 2 used screens
+ [nvidia] "night light" setting only affects one of 2 used screens

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

Title:
  [nvidia] "night light" setting only affects one of 2 used screens

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have an external display that I declared my primary display (my
  laptop screen being the 2nd one). When night light is applied, it only
  affects the built-in display. It should affect both, otherwise it's
  kind of useless.

  I noticed this just now, no clue how repeatable it is. No known
  workaround (maybe "don't use the computer at night?").

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 22 20:16:01 2023
  InstallationDate: Installed on 2022-11-03 (80 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003656/+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 2003620] Re: Setting power mode to "Power Saver" dims screen even if "Dim Screen" option is not on.

[Sebastien Bacher]

Thank you for your bug report, that seems to be by design,
https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/merge_requests/256

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Setting power mode to "Power Saver" dims screen even if "Dim Screen"
  option is not on.

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

Bug description:
  Setting power mode to "Power Saver" dims screen even if "Dim Screen"
  option is not on.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  Uname: Linux 6.1.5-060105-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 21 22:54:36 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-10-12 (466 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-24 (89 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2003620/+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 2003656] Re: "night light" setting only affects one of 2 used screens

[Sebastien Bacher]

** Package changed: gnome-control-center (Ubuntu) => 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/2003656

Title:
  [nvidia] "night light" setting only affects one of 2 used screens

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have an external display that I declared my primary display (my
  laptop screen being the 2nd one). When night light is applied, it only
  affects the built-in display. It should affect both, otherwise it's
  kind of useless.

  I noticed this just now, no clue how repeatable it is. No known
  workaround (maybe "don't use the computer at night?").

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 22 20:16:01 2023
  InstallationDate: Installed on 2022-11-03 (80 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003656/+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 2003104] Re: gnome-terminal transparency ignored in full screen mode

[Daniel van Vugt]

For completeness I bisected the cause of the issue (introduced in mutter
43.1):

909616b20876478bc56932cd18c8e85e982645f6 is the first bad commit
commit 909616b20876478bc56932cd18c8e85e982645f6
Author: Sebastian Wick 
Date:   Tue May 3 18:47:57 2022 +0200

window-actor/wayland: Draw black background for fullscreen windows

Fullscreen Wayland toplevel surfaces don't need to respect the
configured size in which case it should be shown centered on the monitor
with a black background. The black background becomes part of the window
geometry.

The surface container is responsible for correctly culling the surfaces
and making sure the surface actors are removed from the actor tree to
avoid destroying them.

The window actor culling implementation assumes all surfaces to be direct
children of said actor. The introduction of the surface_container actor
broke that assumption. This implements the culling interface in
MetaWindowActorWayland which is aware of the actor surface_container and
fullscreen state.

v2: Fix forwarding culling to surface even if there is a background.
v2: Don't alter passed geometry.
v2: Update window geometry code documentation to reflect these changes.
v2: Only use constrained rect if we're acked fullscreen.

Part-of: 

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

Title:
  gnome-terminal transparency ignored in full screen mode

Status in Mutter:
  New
Status in wayland:
  New
Status in mutter package in Ubuntu:
  Won't Fix
Status in wayland package in Ubuntu:
  Won't Fix

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

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