[Desktop-packages] [Bug 2060266] Re: gnome-session.service [unity-session] uses deprecated --builtin parameter

2024-04-09 Thread Tim Andersson
I've also encountered this on the latest ubuntu-unity iso:
54d180e57790c951ca736606ac9951e3ddf4c1773432ac4ed23f5c4da40acfac 
*noble-desktop-amd64.iso

when trying to do a fresh install in a VM, prior to opening the
installer, I'm greeted with the attached screen.

After clicking login, I get a black, blank screen momentarily, then I'm
booted back to the attached screen.


** Attachment added: "Screenshot from 2024-04-09 17-53-05.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2060266/+attachment/5762889/+files/Screenshot%20from%202024-04-09%2017-53-05.png

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

Title:
  gnome-session.service [unity-session] uses deprecated --builtin
  parameter

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Hi,

  `gnome-session.service` has the following:

  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'

  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.

  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages

  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin

  Removing `--builtin` from `/usr/lib/systemd/user/gnome-
  session.service` let's me log in.

  With that though, I was not able to input text in chromium (installed
  via the snap).

  Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
  session` back to 45.0-1ubuntu1 restores things for me:

  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
  | gnome-session-common:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ apt-cache policy unity-session
  | unity-session:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu 
noble-updates/universe amd64 Packages
  | 100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2060266/+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 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

2024-04-08 Thread Tim Richardson
@sbeattie I tested the package you built for 22.04 and it fixes the
problem for me.

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

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged
Status in xwayland package in Ubuntu:
  Triaged

Bug description:
  I just upgraded xserver-xorg-core and xserver-common to
  2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate
  EAP (downloaded from JerBrains website) Xorg server crashes with
  segfault:

  X.Org X Server 1.21.1.4
  X Protocol Version 11, Revision 0
  Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 
#0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr  4 20:28:35 UTC x86_64
  Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot
  xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr  6 15:28:18 2024
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  malloc(): unaligned tcache chunk detected
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9]
  (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc]
  (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476]
  (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3]
  (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc]
  (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d]
  (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da]
  (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635]
  (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4]
  (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7ec01c429d90]
  (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7ec01c429e40]
  (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605]
  (EE) 
  (EE) 
  Fatal server error:
  (EE) Caught signal 6 (Aborted). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (II) AIGLX: Suspending AIGLX clients for VT switch
  (EE) Server terminated with error (1). Closing log file.

  Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like
  security backports were done incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2060354/+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 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

2024-04-08 Thread Tim Richardson
@sbeattie It's broken in mantic too. In xwayland, the window dies. in
xorg, the session crashes, badly.

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

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  I just upgraded xserver-xorg-core and xserver-common to
  2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate
  EAP (downloaded from JerBrains website) Xorg server crashes with
  segfault:

  X.Org X Server 1.21.1.4
  X Protocol Version 11, Revision 0
  Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 
#0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr  4 20:28:35 UTC x86_64
  Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot
  xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr  6 15:28:18 2024
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  malloc(): unaligned tcache chunk detected
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9]
  (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc]
  (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476]
  (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3]
  (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc]
  (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d]
  (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da]
  (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635]
  (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4]
  (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7ec01c429d90]
  (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7ec01c429e40]
  (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605]
  (EE) 
  (EE) 
  Fatal server error:
  (EE) Caught signal 6 (Aborted). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (II) AIGLX: Suspending AIGLX clients for VT switch
  (EE) Server terminated with error (1). Closing log file.

  Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like
  security backports were done incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2060354/+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 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

2024-04-08 Thread Tim Richardson
Yeah, for me it crashed 100% of the time with no changes, and removing a
configuration file (which among other things removed my non-default
preference for grayscale antialias) completely stopped the crashing.
This is in a kvm/qemu VM. So from my perspective, and from a few others
users, it looks like the cause and a good workaround. But other people
in the set of JetBrains tickets report intermittent, unpredictable
crashing that doesn't benefit from such a settings change. I think think
upstream is talking about race conditions.


So far in the bug report (the Ubuntu one) I don't understand what the proposed 
course of action is.

I think this is the upstream bug report:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1659
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659

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

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded xserver-xorg-core and xserver-common to
  2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate
  EAP (downloaded from JerBrains website) Xorg server crashes with
  segfault:

  X.Org X Server 1.21.1.4
  X Protocol Version 11, Revision 0
  Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 
#0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr  4 20:28:35 UTC x86_64
  Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot
  xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr  6 15:28:18 2024
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  malloc(): unaligned tcache chunk detected
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9]
  (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc]
  (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476]
  (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3]
  (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc]
  (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d]
  (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da]
  (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635]
  (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4]
  (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7ec01c429d90]
  (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7ec01c429e40]
  (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605]
  (EE) 
  (EE) 
  Fatal server error:
  (EE) Caught signal 6 (Aborted). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (II) AIGLX: Suspending AIGLX clients for VT switch
  (EE) Server terminated with error (1). Closing log file.

  Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like
  security backports were done incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+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 2050884] Re: Ubuntu Metrics server is not accepting reports

2024-04-08 Thread Tim Andersson
hi, we're still experiencing this just FYI, I've experienced it in every
noble desktop install I've tested today

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

Title:
  Ubuntu Metrics server is not accepting reports

Status in gnome-initial-setup package in Ubuntu:
  In Progress
Status in ubuntu-report package in Ubuntu:
  Triaged

Bug description:
  gnome-initial-setup now prompts to send a report immediately, and when
  it does, it fails, I'll attach a screenshot in the comments. Even when
  I clicked "Don't send to ubuntu" or however it's phrased, I still
  encountered the error message pop up in the comments.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-initial-setup 46~alpha-2ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 10:38:31 2024
  InstallationDate: Installed on 2024-01-23 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2050884/+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 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

2024-04-08 Thread Tim Richardson
for what it's worth, JetBrains bug reports find that the problem is
triggered by requesting grayscale anti-aliasing.

https://youtrack.jetbrains.com/issue/IDEA-350864/Idea.sh-abort-X-window

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

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded xserver-xorg-core and xserver-common to
  2:21.1.4-2ubuntu1.7-22.04.9 and when starting IntelliJ IDEA Ultimate
  EAP (downloaded from JerBrains website) Xorg server crashes with
  segfault:

  X.Org X Server 1.21.1.4
  X Protocol Version 11, Revision 0
  Current Operating System: Linux nazar-pc 6.8.4-x64v4-xanmod1 
#0~20240404.gdb9d4f4 SMP PREEMPT_DYNAMIC Thu Apr  4 20:28:35 UTC x86_64
  Kernel command line: BOOT_IMAGE=/root/boot/vmlinuz-6.8.4-x64v4-xanmod1 
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root 
nosplash amd_iommu=on intel_iommu=on libahci.ignore_sss=1 fastboot
  xorg-server 2:21.1.4-2ubuntu1.7~22.04.9 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr  6 15:28:18 2024
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  malloc(): unaligned tcache chunk detected
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5def21b09ab9]
  (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7ec01c442520]
  (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (pthread_kill+0x12c) [0x7ec01c4969fc]
  (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x16) [0x7ec01c442476]
  (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xd3) [0x7ec01c4287f3]
  (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x426) [0x7ec01c489676]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (timer_settime+0x2cc) [0x7ec01c4a0cfc]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (malloc+0x33c) [0x7ec01c4a53dc]
  (EE) 8: /usr/lib/xorg/Xorg (SetGlyphPicture+0x15d) [0x5def21a6311d]
  (EE) 9: /usr/lib/xorg/Xorg (AddTraps+0x347a) [0x5def21a6b8da]
  (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) [0x5def21993635]
  (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x5def219976b4]
  (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) 
[0x7ec01c429d90]
  (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) 
[0x7ec01c429e40]
  (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x5def21980605]
  (EE) 
  (EE) 
  Fatal server error:
  (EE) Caught signal 6 (Aborted). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (II) AIGLX: Suspending AIGLX clients for VT switch
  (EE) Server terminated with error (1). Closing log file.

  Downgraded to 2:21.1.3-2ubuntu2 for now and it works. Looks like
  security backports were done incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+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 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble

2024-04-05 Thread Tim Andersson
Tried this again today, still an issue, see files attached

** Attachment added: "dist-upgrade.tar"
   
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2043820/+attachment/5761639/+files/dist-upgrade.tar

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

Title:
  Unable to contact snap store on Xubuntu from Jammy to Noble

Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in firefox source package in Noble:
  Confirmed
Status in snapd source package in Noble:
  Confirmed

Bug description:
  When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade
  fails consistently at the `Installing the firefox snap` step.

  This was first detected on Jenkins [1], then reproduced locally with
  `auto-upgrade-testing`, then finally by manually running a `do-
  release-upgrade -d` in a VM.

  [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade-
  list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull
  (Jenkins full log attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.17
  ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Fri Nov 17 18:24:22 2023
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+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 1971434] Re: Display powersave only blanks, but does not turn off

2024-03-16 Thread Tim Richardson
I use the wayland session. I sort of have this bug. The screens do power
off, but then the backlights resume. It is still a blank screen

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

Title:
  Display powersave only blanks, but does not turn off

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

Bug description:
  Recently upgraded to Ubuntu 22.04, and it seems like the power-saving
  feature in Gnome 42 does not actually turn off the screen(s) after X
  minutes, but just blanks them. When I manually run `xset dpms force
  off`, they do properly turn off and go to powersave mode.

  1) Description:   Ubuntu 22.04 LTS
 Release:   22.04

  2) gnome-settings-daemon:
Installed: 42.1-1ubuntu2
Candidate: 42.1-1ubuntu2

  3) In Settings -> Power -> Screen Blank, set the inactivity period to
  5 minutes. After 5 minutes, the screens should turn off.

  4) Screens go black, but remain active and consume (too much) power.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-07-04 (667 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Package: gnome-settings-daemon 42.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 2050884] Re: Ubuntu Metrics server is not accepting reports

2024-01-23 Thread Tim Andersson
Okay, sounds good :)

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

Title:
  Ubuntu Metrics server is not accepting reports

Status in gnome-initial-setup package in Ubuntu:
  Triaged
Status in ubuntu-report package in Ubuntu:
  Triaged

Bug description:
  gnome-initial-setup now prompts to send a report immediately, and when
  it does, it fails, I'll attach a screenshot in the comments. Even when
  I clicked "Don't send to ubuntu" or however it's phrased, I still
  encountered the error message pop up in the comments.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-initial-setup 46~alpha-2ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 10:38:31 2024
  InstallationDate: Installed on 2024-01-23 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2050884/+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 2049670] Re: noble: gnome-initial-setup 20 second delay & error popup

2024-01-23 Thread Tim Andersson
I made a bug report [1] for this also, which I've marked as a duplicate
of this one.


[1] https://bugs.launchpad.net/ubuntu/+source/gnome-initial-
setup/+bug/2050884

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

Title:
  noble: gnome-initial-setup 20 second delay & error popup

Status in gnome-initial-setup package in Ubuntu:
  Triaged

Bug description:
  When GNOME Initial Setup is run in Ubuntu 24.04 LTS (the current
  development release), when clicking Next on the "Help improve Ubuntu"
  screen, the Initial Setup pauses for 20 seconds then shows a popup
  dialog (screenshot attached).

  This happens regardless of whether Yes or No is chosen on that screen.

  Sometimes, the app might go to the next screen and close the popup
  dialog itself.

  Logs
  
  GNOME Initial Setup can be run from the command line by running
  /usr/libexec/gnome-initial-setup --existing-user

  When run from the command line, these warnings are emitted:

  InitialSetup-Message: Starting gnome-initial-setup
  InitialSetup-Message: Production mode: changes will be saved to disk
  INFO[0003] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: 
open /var/lib/ubuntu_dist_channel: no such file or directory 

  (gnome-initial-setup): InitialSetup-WARNING **: Failed to send report 
information: data were not delivered successfully to metrics server, saving for 
a later automated report: couldn't send post http request: Post 
"https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded 
(Client.Timeout exceeded while awaiting headers)
  INFO[0107] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: 
open /var/lib/ubuntu_dist_channel: no such file or directory

  Logs 2
  ==
  If No is selected, the command-line warning is slightly different.

  Failed to send report decline: data were not delivered successfully to
  metrics server, saving for a later automated report: couldn't send
  post http request: Post
  "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline
  exceeded (Client.Timeout exceeded while awaiting headers)

  Other Info
  ==
  Perhaps the metrics server is not set up for Ubuntu 24.04 LTS yet?

  This bug is related to bug 1761742 and I agree with comment #3 there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2049670/+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 2050884] [NEW] gnome-initial-setup always fails on sending first report

2024-01-23 Thread Tim Andersson
Public bug reported:

gnome-initial-setup now prompts to send a report immediately, and when
it does, it fails, I'll attach a screenshot in the comments. Even when I
clicked "Don't send to ubuntu" or however it's phrased, I still
encountered the error message pop up in the comments.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-initial-setup 46~alpha-2ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 10:38:31 2024
InstallationDate: Installed on 2024-01-23 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome-initial-setup always fails on sending first report

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  gnome-initial-setup now prompts to send a report immediately, and when
  it does, it fails, I'll attach a screenshot in the comments. Even when
  I clicked "Don't send to ubuntu" or however it's phrased, I still
  encountered the error message pop up in the comments.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gnome-initial-setup 46~alpha-2ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 10:38:31 2024
  InstallationDate: Installed on 2024-01-23 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2050884/+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 2037604] Re: Backport packages for 22.04.4 HWE stack

2024-01-10 Thread Tim Holmes-Mitra
I've tested the proposed mesa + hwe kernel and as far as I can tell it's
working well. I believe my Z16 is navi 2nd generation and it has an iGPU
and dGPU both AMD (600M series and RX 6500 respectively). What I tested:

- firefox you tube videos (with both DRI_PRIME=0 and 1)
- steam deb running dota and quake2 (with both DRI_PRIME=0 and 1)
- desktop is hardware rendered with the iGPU and working well
- multi-monitor (2 external 4k monitors)

Let me know if there's anything else I should add or test.

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions


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


Re: [Desktop-packages] [Bug 2045820] Re: firefox snap .desktop missing StartupWMClass

2023-12-07 Thread Tim Richardson
Where is the source code for the snap packaging for firefox? How can
patches be submitted?

On Fri, 8 Dec 2023 at 01:10, Maximiliano Bertacchini <
2045...@bugs.launchpad.net> wrote:

> I can confirm adding `StartupWMClass=firefox-beta` in the .desktop file
> fixes the firefox snap icon in the KDE/Plasma task manager. Thanks!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2045820
>
> Title:
>   firefox snap .desktop missing StartupWMClass
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+subscriptions
>
>

-- 
Tim Richardson

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

Title:
  firefox snap .desktop missing StartupWMClass

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
  firefox-desktop-file-missing-startupwmclass/37400

  I have the mozilla stable version installed using the mozilla binary
  method, and snap for the beta channel. The snap icon is broken, both
  in the menu entry and in the panel. That is, there is no icon in menu,
  and the generic cog icon in the panel.

  This is on 22.04 But I have the same problem in 23.10 and in a VM
  22.04. That is, I can reproduce this every time.

  I did snap remove firefox

  to uninstall, but this file

  /home/tim/.local/share/applications/firefox_firefox.desktop

  remains.

  So I remove it manually, and reinstall.

  The desktop file for this is now:

  /var/lib/snapd/desktop/applications/firefox_firefox.desktop

  It is called Firefox Web Browser in the gnome launcher, and it has an
  icon. But after launching, it still uses the generic cog icon in the
  panel. The context menu from this icon has no actions, except to Quit.
  If I create a second window, both are associated with this icon, which
  is good.

  In the Gnome launcher, if you search for an app and if that app is
  running, the Gnome launcher indicates it with a dot. However, while
  this works for the mozilla binary, the icon of Firefox Web Browser
  (installed with snap) does not show a dot, even though I have two
  windows from it open.

  image: see attachment firefox_bug_0.png

  image: see attachment firefox_bug_1.png

  Fix?

  From chatgpt help, I see this:

  image: see attachment firefox_bug_3.png

  Add this line to the snap .destkop file, near the top, fixed it:

  StartupWMClass=firefox-beta

  Therefore my suggestion is that the .desktop file have a channel-
  dependent StartupWMClass value set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+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 2045820] Re: firefox snap .desktop missing StartupWMClass

2023-12-06 Thread Tim Richardson
screenshot 2, chatgpt suggestion which contained the fix

** Attachment added: "firefox_bug_2.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+attachment/5726921/+files/firefox_bug_2.png

** Description changed:

- I have the mozilla stable version installed using the mozilla binary
- method, and snap for the beta channel. The icon is broken, both in the
- menu entry and in the panel. That is, there is no icon in menu, and the
- generic cog icon in the panel.
+ this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
+ firefox-desktop-file-missing-startupwmclass/37400
+ 
+ 
+ I have the mozilla stable version installed using the mozilla binary method, 
and snap for the beta channel. The icon is broken, both in the menu entry and 
in the panel. That is, there is no icon in menu, and the generic cog icon in 
the panel.
  
  This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04.
  That is, I can reproduce this every time.
  
  I did snap remove firefox
  
  to uninstall, but this file
  
  /home/tim/.local/share/applications/firefox_firefox.desktop
  
  remains.
  
  So I remove it manually, and reinstall.
  
  The desktop file for this is now:
  
  /var/lib/snapd/desktop/applications/firefox_firefox.desktop
  
  It is called Firefox Web Browser in the gnome launcher, and it has an
  icon. But after launching, it still uses the generic cog icon in the
  panel. The context menu from this icon has no actions, except to Quit.
  If I create a second window, both are associated with this icon, which
  is good.
  
  In the Gnome launcher, if you search for an app and if that app is
  running, the Gnome launcher indicates it with a dot. However, while this
  works for the mozilla binary, the icon of Firefox Web Browser does not
  show a dot, even though I have two windows from it open.
  
  image
  
- 
  image
  
  Fix?
  
  From chatgpt help, I see this:
  
  image
  
- 
  Add
  this this line to the .destkop file, near the top, fixed it:
  
  StartupWMClass=firefox-beta

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

Title:
  firefox snap .desktop missing StartupWMClass

Status in firefox package in Ubuntu:
  New

Bug description:
  this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
  firefox-desktop-file-missing-startupwmclass/37400

  I have the mozilla stable version installed using the mozilla binary
  method, and snap for the beta channel. The snap icon is broken, both
  in the menu entry and in the panel. That is, there is no icon in menu,
  and the generic cog icon in the panel.

  This is on 22.04 But I have the same problem in 23.10 and in a VM
  22.04. That is, I can reproduce this every time.

  I did snap remove firefox

  to uninstall, but this file

  /home/tim/.local/share/applications/firefox_firefox.desktop

  remains.

  So I remove it manually, and reinstall.

  The desktop file for this is now:

  /var/lib/snapd/desktop/applications/firefox_firefox.desktop

  It is called Firefox Web Browser in the gnome launcher, and it has an
  icon. But after launching, it still uses the generic cog icon in the
  panel. The context menu from this icon has no actions, except to Quit.
  If I create a second window, both are associated with this icon, which
  is good.

  In the Gnome launcher, if you search for an app and if that app is
  running, the Gnome launcher indicates it with a dot. However, while
  this works for the mozilla binary, the icon of Firefox Web Browser
  (installed with snap) does not show a dot, even though I have two
  windows from it open.

  image: see attachment firefox_bug_0.png

  image: see attachment firefox_bug_1.png

  Fix?

  From chatgpt help, I see this:

  image: see attachment firefox_bug_3.png

  Add this line to the snap .destkop file, near the top, fixed it:

  StartupWMClass=firefox-beta

  Therefore my suggestion is that the .desktop file have a channel-
  dependent StartupWMClass value set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+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 2045820] Re: firefox snap .desktop missing StartupWMClass

2023-12-06 Thread Tim Richardson
screen shot of icon problem

** Attachment added: "firefox_bug_0.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+attachment/5726922/+files/firefox_bug_0.png

** Description changed:

  this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
  firefox-desktop-file-missing-startupwmclass/37400
  
- 
- I have the mozilla stable version installed using the mozilla binary method, 
and snap for the beta channel. The icon is broken, both in the menu entry and 
in the panel. That is, there is no icon in menu, and the generic cog icon in 
the panel.
+ I have the mozilla stable version installed using the mozilla binary
+ method, and snap for the beta channel. The icon is broken, both in the
+ menu entry and in the panel. That is, there is no icon in menu, and the
+ generic cog icon in the panel.
  
  This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04.
  That is, I can reproduce this every time.
  
  I did snap remove firefox
  
  to uninstall, but this file
  
  /home/tim/.local/share/applications/firefox_firefox.desktop
  
  remains.
  
  So I remove it manually, and reinstall.
  
  The desktop file for this is now:
  
  /var/lib/snapd/desktop/applications/firefox_firefox.desktop
  
  It is called Firefox Web Browser in the gnome launcher, and it has an
  icon. But after launching, it still uses the generic cog icon in the
  panel. The context menu from this icon has no actions, except to Quit.
  If I create a second window, both are associated with this icon, which
  is good.
  
  In the Gnome launcher, if you search for an app and if that app is
  running, the Gnome launcher indicates it with a dot. However, while this
  works for the mozilla binary, the icon of Firefox Web Browser does not
  show a dot, even though I have two windows from it open.
  
- image
+ image: see attachment firefox_bug_0.png
  
- image
+ image: see attachment firefox_bug_1.png
  
  Fix?
  
  From chatgpt help, I see this:
  
- image
+ image: see attachment firefox_bug_3.png
  
  Add
  this this line to the .destkop file, near the top, fixed it:
  
  StartupWMClass=firefox-beta

** Description changed:

  this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
  firefox-desktop-file-missing-startupwmclass/37400
  
  I have the mozilla stable version installed using the mozilla binary
- method, and snap for the beta channel. The icon is broken, both in the
- menu entry and in the panel. That is, there is no icon in menu, and the
- generic cog icon in the panel.
+ method, and snap for the beta channel. The snap icon is broken, both in
+ the menu entry and in the panel. That is, there is no icon in menu, and
+ the generic cog icon in the panel.
  
  This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04.
  That is, I can reproduce this every time.
  
  I did snap remove firefox
  
  to uninstall, but this file
  
  /home/tim/.local/share/applications/firefox_firefox.desktop
  
  remains.
  
  So I remove it manually, and reinstall.
  
  The desktop file for this is now:
  
  /var/lib/snapd/desktop/applications/firefox_firefox.desktop
  
  It is called Firefox Web Browser in the gnome launcher, and it has an
  icon. But after launching, it still uses the generic cog icon in the
  panel. The context menu from this icon has no actions, except to Quit.
  If I create a second window, both are associated with this icon, which
  is good.
  
  In the Gnome launcher, if you search for an app and if that app is
  running, the Gnome launcher indicates it with a dot. However, while this
  works for the mozilla binary, the icon of Firefox Web Browser does not
  show a dot, even though I have two windows from it open.
  
  image: see attachment firefox_bug_0.png
  
  image: see attachment firefox_bug_1.png
  
  Fix?
  
  From chatgpt help, I see this:
  
  image: see attachment firefox_bug_3.png
  
  Add
  this this line to the .destkop file, near the top, fixed it:
  
  StartupWMClass=firefox-beta

** Description changed:

  this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
  firefox-desktop-file-missing-startupwmclass/37400
  
  I have the mozilla stable version installed using the mozilla binary
  method, and snap for the beta channel. The snap icon is broken, both in
  the menu entry and in the panel. That is, there is no icon in menu, and
  the generic cog icon in the panel.
  
  This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04.
  That is, I can reproduce this every time.
  
  I did snap remove firefox
  
  to uninstall, but this file
  
  /home/tim/.local/share/applications/firefox_firefox.desktop
  
  remains.
  
  So I remove it manually, and reinstall.
  
  The desktop file for this is now:
  
  /var/lib/snapd/desktop/applications/firefox_firefox.desktop
  
  It is called Firefox Web Browser in the gnome launcher, and it has an
  icon. But after launching, it still uses the generic cog icon in the
  panel. T

[Desktop-packages] [Bug 2045820] [NEW] firefox snap .desktop missing StartupWMClass

2023-12-06 Thread Tim Richardson
Public bug reported:

this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
firefox-desktop-file-missing-startupwmclass/37400

I have the mozilla stable version installed using the mozilla binary
method, and snap for the beta channel. The snap icon is broken, both in
the menu entry and in the panel. That is, there is no icon in menu, and
the generic cog icon in the panel.

This is on 22.04 But I have the same problem in 23.10 and in a VM 22.04.
That is, I can reproduce this every time.

I did snap remove firefox

to uninstall, but this file

/home/tim/.local/share/applications/firefox_firefox.desktop

remains.

So I remove it manually, and reinstall.

The desktop file for this is now:

/var/lib/snapd/desktop/applications/firefox_firefox.desktop

It is called Firefox Web Browser in the gnome launcher, and it has an
icon. But after launching, it still uses the generic cog icon in the
panel. The context menu from this icon has no actions, except to Quit.
If I create a second window, both are associated with this icon, which
is good.

In the Gnome launcher, if you search for an app and if that app is
running, the Gnome launcher indicates it with a dot. However, while this
works for the mozilla binary, the icon of Firefox Web Browser (installed
with snap) does not show a dot, even though I have two windows from it
open.

image: see attachment firefox_bug_0.png

image: see attachment firefox_bug_1.png

Fix?

>From chatgpt help, I see this:

image: see attachment firefox_bug_3.png

Add this line to the snap .destkop file, near the top, fixed it:

StartupWMClass=firefox-beta

Therefore my suggestion is that the .desktop file have a channel-
dependent StartupWMClass value set.

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

** Attachment added: "Screenshot 1"
   
https://bugs.launchpad.net/bugs/2045820/+attachment/5726920/+files/firefox_bug_1.png

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

Title:
  firefox snap .desktop missing StartupWMClass

Status in firefox package in Ubuntu:
  New

Bug description:
  this is repost from https://forum.snapcraft.io/t/snap-icons-is-the-
  firefox-desktop-file-missing-startupwmclass/37400

  I have the mozilla stable version installed using the mozilla binary
  method, and snap for the beta channel. The snap icon is broken, both
  in the menu entry and in the panel. That is, there is no icon in menu,
  and the generic cog icon in the panel.

  This is on 22.04 But I have the same problem in 23.10 and in a VM
  22.04. That is, I can reproduce this every time.

  I did snap remove firefox

  to uninstall, but this file

  /home/tim/.local/share/applications/firefox_firefox.desktop

  remains.

  So I remove it manually, and reinstall.

  The desktop file for this is now:

  /var/lib/snapd/desktop/applications/firefox_firefox.desktop

  It is called Firefox Web Browser in the gnome launcher, and it has an
  icon. But after launching, it still uses the generic cog icon in the
  panel. The context menu from this icon has no actions, except to Quit.
  If I create a second window, both are associated with this icon, which
  is good.

  In the Gnome launcher, if you search for an app and if that app is
  running, the Gnome launcher indicates it with a dot. However, while
  this works for the mozilla binary, the icon of Firefox Web Browser
  (installed with snap) does not show a dot, even though I have two
  windows from it open.

  image: see attachment firefox_bug_0.png

  image: see attachment firefox_bug_1.png

  Fix?

  From chatgpt help, I see this:

  image: see attachment firefox_bug_3.png

  Add this line to the snap .destkop file, near the top, fixed it:

  StartupWMClass=firefox-beta

  Therefore my suggestion is that the .desktop file have a channel-
  dependent StartupWMClass value set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2045820/+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 2042764] [NEW] ICC profile has no effect in Wayland session

2023-11-05 Thread Tim Summerer
Public bug reported:

The color profile set either via the Gnome Control Center or colord has
no effect in the Wayland session.

I tested it with Firefox and can see no difference no matter what color profile 
is set in GNOME.
I also changed the color profile in Firefox via the about:config and tried to 
set the color management flag to 1 (to always enable color management to no 
effect).

I then tested eog vs. shotwell.
In the Gnome Wayland session the images I compared looked identical but both 
not in the ICC profile I selected.
In the Gnome Xorg session there was a visible difference between eog which 
displayed the image with the selected ICC profile and shotwell which ignored 
the ICC profile.

This bug might very well be an upstream issue.
I am reporting it because (without diving very deep into the system) I do not 
see anything else to try to remedy this issue.

Ubuntu version: Ubuntu 23.10
colord version: 1.4.6-3 (Maybe this is not the correct package to file this 
against)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: colord 1.4.6-3
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 13:09:08 2023
InstallationDate: Installed on 2023-11-03 (2 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: colord
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  ICC profile has no effect in Wayland session

Status in colord package in Ubuntu:
  New

Bug description:
  The color profile set either via the Gnome Control Center or colord
  has no effect in the Wayland session.

  I tested it with Firefox and can see no difference no matter what color 
profile is set in GNOME.
  I also changed the color profile in Firefox via the about:config and tried to 
set the color management flag to 1 (to always enable color management to no 
effect).

  I then tested eog vs. shotwell.
  In the Gnome Wayland session the images I compared looked identical but both 
not in the ICC profile I selected.
  In the Gnome Xorg session there was a visible difference between eog which 
displayed the image with the selected ICC profile and shotwell which ignored 
the ICC profile.

  This bug might very well be an upstream issue.
  I am reporting it because (without diving very deep into the system) I do not 
see anything else to try to remedy this issue.

  Ubuntu version: Ubuntu 23.10
  colord version: 1.4.6-3 (Maybe this is not the correct package to file this 
against)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: colord 1.4.6-3
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 13:09:08 2023
  InstallationDate: Installed on 2023-11-03 (2 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: colord
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/2042764/+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 2034986] Re: some text became unreadable during a distribution upgrade

2023-10-13 Thread Tim Andersson
I just did this with vanilla ubuntu with the ubuntu-release-upgrader
version from proposed and everything was fine - no wild font changes.

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-meta source package in Lunar:
  Confirmed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

2023-10-13 Thread Tim Andersson
I tested a lunar -> mantic desktop upgrade last night and did not
encounter the bug described here.

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-meta source package in Lunar:
  Confirmed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2037497] Re: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()

2023-10-05 Thread Tim Holmes-Mitra
** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

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

Title:
  gnome-shell crashed with SIGSEGV at NULL from end_query() from
  cogl_gl_create_timestamp_query() from
  cogl_onscreen_egl_swap_buffers_with_damage()

Status in Mesa:
  New
Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Invalid
Status in mesa package in Fedora:
  Confirmed

Bug description:
  crash after update
  wayland session is not accessible anymore

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 05:52:26 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-26 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2037497/+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 2035020] Re: firefox doesn't show the menu entries to move to another workspace

2023-09-21 Thread Tim Holmes-Mitra
Not a release blocker.

** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

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

Title:
  firefox doesn't show the menu entries to move to another workspace

Status in firefox package in Ubuntu:
  New

Bug description:
  firefox doesn't show the menu entries to move to another workspace

  seen with mantic 20230910.

  The menu to keep the window on the workspace, and/or to move it to
  another workspace isn't available anymore.  This still seems to work
  with the chromium snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2035020/+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 1923052] Re: screen reader does not read ubiquity window after it is launched in "Try Ubuntu" session

2023-09-21 Thread Tim Holmes-Mitra
Not a release blocker.

** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

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

Title:
  screen reader does not read ubiquity window after it is launched in
  "Try Ubuntu" session

Status in at-spi2-core package in Ubuntu:
  Incomplete
Status in orca package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Confirmed
Status in at-spi2-core source package in Jammy:
  Incomplete
Status in orca source package in Jammy:
  Incomplete
Status in ubiquity source package in Jammy:
  Confirmed
Status in at-spi2-core source package in Mantic:
  Incomplete
Status in orca source package in Mantic:
  Incomplete
Status in ubiquity source package in Mantic:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 2034069] Re: Animation when exiting the overview doesn't appear to complete properly

2023-09-21 Thread Tim Holmes-Mitra
We should fix this, but not a release blocker.

** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

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

Title:
  Animation when exiting the overview doesn't appear to complete
  properly

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

Bug description:
  Animation when exiting the overview don't appear to complete properly
  often (App icons over the windows will shrink and vanish but the
  windows and overview won't zoom back out).

  # System Details Report
  ---

  ## Report details
  - **Date generated:**  2023-09-04 18:36:39

  ## Hardware Information:
  - **Hardware Model:**  Apple Inc. MacBookPro12,1
  - **Memory:**  8.0 GiB
  - **Processor:**   Intel® Core™ i5-5257U × 4
  - **Graphics:**Intel® Iris® Graphics 6100 
(BDW GT3)
  - **Disk Capacity:**   (null)

  ## Software Information:
  - **Firmware Version:**184.0.0.0.0
  - **OS Name:** Ubuntu Mantic Minotaur 
(development branch)
  - **OS Build:**(null)
  - **OS Type:** 64-bit
  - **GNOME Version:**   Not Available
  - **Windowing System:**Wayland
  - **Kernel Version:**  Linux 6.3.0-7-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 18:27:19 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-31 (522 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034069/+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 2034986] Re: some text became unreadable during a distribution upgrade

2023-09-21 Thread Tim Holmes-Mitra
** Tags removed: rls-mm-incoming

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

Bug description:
  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2019939] Re: Outdated documentation about NetworkManager keyfiles

2023-09-21 Thread Tim Holmes-Mitra
** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

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

Title:
  Outdated documentation about NetworkManager keyfiles

Status in debian-handbook package in Ubuntu:
  Won't Fix
Status in dhcpcanon package in Ubuntu:
  Won't Fix
Status in fai package in Ubuntu:
  New
Status in gnome-user-docs package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  Fix Committed
Status in scap-security-guide package in Ubuntu:
  New
Status in wifi-qr package in Ubuntu:
  New

Bug description:
  The affected packages contain documentation or examples about
  NetworkManager keyfiles, which might not be appropriate anymore on
  Ubuntu, since the Netplan integration was enabled in NetworkManager
  (starting with Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+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 2033688] Re: [mantic] gnome-shell fails to follow accent colours

2023-09-21 Thread Tim Holmes-Mitra
** Tags removed: rls-mm-incoming

** Also affects: gnome-shell (Ubuntu Mantic)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Triaged

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

Title:
  [mantic] gnome-shell fails to follow accent colours

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Mantic:
  Triaged

Bug description:
  When accent colors are selected in gnome-control-center, gnome-shell
  fails to follow with the exception of blue and orange. Screenshots
  attached.

  Test Case
  -
  1. Open the Settings app
  2. Switch to the Appearance page
  3. Choose the Purple color
  4. Click the quick settings area in the far right side of GNOME Shell's top 
bar
  5. The highlights should be purple

  What Happens Instead
  
  The highlights are still orange

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 13:50:24 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-03-04 (180 days ago)
  InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 
(20230304)
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033688/+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 2030951] Re: geoclue service prevented from working by apparmor profile

2023-09-21 Thread Tim Holmes-Mitra
** Tags removed: rls-mm-incoming

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

Title:
  geoclue service prevented from working by apparmor profile

Status in geoclue-2.0 package in Ubuntu:
  Triaged

Bug description:
  The geoclue service doesn't start anymore in mantic, failing with

  (geoclue:8550): Geoclue-CRITICAL **: 10:56:36.151: Failed to acquire
  name 'org.freedesktop.GeoClue2' on system bus or lost it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: geoclue-2.0 2.7.0-3
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Aug 10 10:57:41 2023
  InstallationDate: Installed on 2022-11-26 (256 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  SourcePackage: geoclue-2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/2030951/+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 2031172] Re: Please take a stand on "screen: Use clean env when creating new tab"

2023-09-21 Thread Tim Holmes-Mitra
Lets discuss the behaviour we want, but we don't see this as an interim
release blocker.

** Tags removed: rls-mm-incoming
** Tags added: rls-mm-not-fixing

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

Title:
  Please take a stand on "screen: Use clean env when creating new tab"

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  In gnome-terminal 3.49.92-2ubuntu1 d/p/screen-Use-clean-env-when-
  creating-new-tab.patch is disabled since the code is applied upstream
  in 3.49.92. However, upstream hesitates and has now reverted the code
  in question. Please see this commit message:

  https://salsa.debian.org/gnome-team/gnome-terminal/-/commit/c808edb8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2031172/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

2023-09-21 Thread Tim Holmes-Mitra
** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: Confirmed

** Also affects: mutter (Ubuntu Mantic)
   Importance: High
 Assignee: Daniel van Vugt (vanvugt)
   Status: In Progress

** Tags removed: rls-mm-incoming

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

Title:
  [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland

Status in Linux:
  New
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  In Progress
Status in linux source package in Mantic:
  Confirmed
Status in mutter source package in Mantic:
  In Progress

Bug description:
  I have this issue on Ubuntu 23.10. Lock screen works only with an external 
monitor connected. Otherwise the session is ended and the user is logged out 
and brought to the gdm screen.
  All works in xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~beta.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  6 22:32:22 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2023-09-03 (3 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2034619/+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 2036802] [NEW] HDMI not detected on HP Zbook Power 15 G9

2023-09-20 Thread Tim Lachmann
Public bug reported:

As discussed in this thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811

On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected.

According to the discussion a fix has been implemented in kernel
v6.6-rc1.

If it's possible for Ubuntu to implement some fix in the current LTS
version that would be MUCH helpful and appreciated for me and all other
ubuntu users on the same laptop.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.104.05  Sat Aug 19 
01:15:15 UTC 2023
 GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 20 19:25:44 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 evdi/1.14.1, 6.2.0-32-generic, x86_64: installed
 evdi/1.14.1, 6.2.0-33-generic, x86_64: installed
 nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed
 nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:89c0]
   Subsystem: Hewlett-Packard Company Device [103c:89c1]
InstallationDate: Installed on 2023-08-21 (29 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2023
dmi.bios.release: 8.0
dmi.bios.vendor: HP
dmi.bios.version: U97 Ver. 01.08.00
dmi.board.name: 89C0
dmi.board.vendor: HP
dmi.board.version: KBC Version 11.63.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 17.99
dmi.modalias: 
dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC
dmi.product.sku: 6B867EA#UUW
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

** Summary changed:

- HDMI not detected
+ HDMI not detected on HP Zbook Power 15 G9

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

Title:
  HDMI not detected on HP Zbook Power 15 G9

Status in xorg package in Ubuntu:
  New

Bug description:
  As discussed in this thread:
  https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811

  On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected.

  According to the discussion a fix has been implemented in kernel
  v6.6-rc1.

  If it's possible for Ubuntu to implement some fix in the current LTS
  version that would be MUCH helpful and appreciated for me and all
  other ubuntu users on the same laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  

[Desktop-packages] [Bug 2036764] Re: indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon

2023-09-20 Thread Tim Andersson
** Also affects: ubuntucinnamon-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  indicator keyboard crashes when upgrading from lunar->mantic on ubuntu
  cinnamon

Status in indicator-keyboard package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New

Bug description:
  Log snippet:

  JournalErrors:
   Sep 20 14:52:28 autopkgtest kernel: kauditd_printk_skb: 164 callbacks 
suppressed
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:32 autopkgtest systemd[1]: multipathd.socket: Socket service 
multipathd.service already active, refusing.
   Sep 20 14:52:32 autopkgtest systemd[1]: Failed to listen on 
multipathd.socket - multipathd control socket.
   Sep 20 14:52:34 autopkgtest kernel: kauditd_printk_skb: 205 callbacks 
suppressed
   Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:35 autopkgtest indicator-keybo[747]: g_variant_ref: assertion 
'value != NULL' failed
   Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv4: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
   Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv6: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
   Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Main 
process exited, code=dumped, status=11/SEGV
   Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Failed 
with result 'core-dump'.
   Sep 20 14:52:38 autopkgtest indicator-keybo[27565]: 
gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
   Sep 20 14:52:42 autopkgtest kernel: kauditd_printk_skb: 193 callbacks 
suppressed
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
   Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
  Package: indicator-keyboard 0.0.0+19.10.20220803-0ubuntu1

  I'll attach the full upgrade log.

  This bug was discovered by using autopkgtest. You can reproduce by
  installing autopkgtest, auto-upgrade-testing and cloning auto-upgrade-
  testing-specifications and running this from the parent directory:

  sudo --preserve-env=AUTOPKGTEST_APT_SOURCES_FILE python3 -m
  upgrade_testing.command_line -c auto-upgrade-testing-
  specifications/profiles/ubuntu-lunar-mantic-ubuntucinnamon-
  amd64_qemu.yaml --provision --results-dir /home/$USER/upgrade_cinnamon
  --adt-args=--timeout-factor=10

  I'll attach the full logs below. I'm also trying to recreate using an
  lxd container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/2036764/+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 2036764] [NEW] indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon

2023-09-20 Thread Tim Andersson
Public bug reported:

Log snippet:

JournalErrors:
 Sep 20 14:52:28 autopkgtest kernel: kauditd_printk_skb: 164 callbacks 
suppressed
 Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
 Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
 Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:32 autopkgtest systemd[1]: multipathd.socket: Socket service 
multipathd.service already active, refusing.
 Sep 20 14:52:32 autopkgtest systemd[1]: Failed to listen on multipathd.socket 
- multipathd control socket.
 Sep 20 14:52:34 autopkgtest kernel: kauditd_printk_skb: 205 callbacks 
suppressed
 Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:35 autopkgtest indicator-keybo[747]: g_variant_ref: assertion 
'value != NULL' failed
 Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv4: There appears 
to be another mDNS responder running, or previously systemd-resolved crashed 
with some outstanding transfers.
 Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv6: There appears 
to be another mDNS responder running, or previously systemd-resolved crashed 
with some outstanding transfers.
 Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Main 
process exited, code=dumped, status=11/SEGV
 Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Failed 
with result 'core-dump'.
 Sep 20 14:52:38 autopkgtest indicator-keybo[27565]: 
gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
 Sep 20 14:52:42 autopkgtest kernel: kauditd_printk_skb: 193 callbacks 
suppressed
 Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
 Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message 
bus configuration file
Package: indicator-keyboard 0.0.0+19.10.20220803-0ubuntu1

I'll attach the full upgrade log.

This bug was discovered by using autopkgtest. You can reproduce by
installing autopkgtest, auto-upgrade-testing and cloning auto-upgrade-
testing-specifications and running this from the parent directory:

sudo --preserve-env=AUTOPKGTEST_APT_SOURCES_FILE python3 -m
upgrade_testing.command_line -c auto-upgrade-testing-
specifications/profiles/ubuntu-lunar-mantic-ubuntucinnamon-
amd64_qemu.yaml --provision --results-dir /home/$USER/upgrade_cinnamon
--adt-args=--timeout-factor=10

I'll attach the full logs below. I'm also trying to recreate using an
lxd container

** Affects: indicator-keyboard (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Log snippet:
  
  JournalErrors:
-  Sep 20 14:52:28 autopkgtest kernel: kauditd_printk_skb: 164 callbacks 
suppressed
-  Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
-  Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
-  Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in 
message bus configuration file
-  Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
-  Sep 20 14:52:32 autopkgtest systemd[1]: multipathd.socket: Socket service 
multipathd.service already active, refusing.
-  Sep 20 14:52:32 autopkgtest systemd[1]: Failed to listen on 
multipathd.socket - multipathd control socket.
-  Sep 20 14:52:34 autopkgtest kernel: kauditd_printk_skb: 205 callbacks 
suppressed
-  Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
-  Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in 
message bus configuration file
-  Sep 20 14:52:35 autopkgtest indicator-keybo[747]: g_variant_ref: assertion 
'value != NULL' failed
-  Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv4: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
-  Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv6: There 
appears to be another mDNS responder running, or previously systemd-resolved 
crashed with some outstanding transfers.
-  Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Main 
process exited, code=dumped, status=11/SEGV
-  Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Failed 
with result 'core-dump'.
-  Sep 

[Desktop-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

2023-09-08 Thread Tim Andersson
Looks like it's fixed in today's daily image ! Lovely stuff :)

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

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-desktop package in Ubuntu:
  Won't Fix
Status in language-pack-gnome-en package in Ubuntu:
  Won't Fix
Status in language-pack-gnome-en-base package in Ubuntu:
  Won't Fix
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2033377/+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 2033533] Re: installing with lvm and encryption requires arrow key spam after reboot to get to encryption passphrase prompt

2023-08-30 Thread Tim Andersson
apport information

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

** Tags added: apport-collected third-party-packages

** Description changed:

  This also happens with the canary image and is happening with the Mantic
  daily image.
  
  When installing with LVM and encryption, after the "remove installation
  medium and press enter to reboot", the user is greeted with a permanent
  black screen. After pressing arrow keys, the gui prompt is then shown to
  prompt the user to put in the encryption passphrase.
  
  It is also somehow possible to not get the black screen by changing the
  grub prior to installing by removing splash from the grub options. The
  user is then greeted with a text-only passphrase prompt after rebooting.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 30 16:39:39 2023
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu2
+ Architecture: amd64
+ BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2023-08-30 (0 days ago)
+ InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Lsusb-t:
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ Package: ubiquity
+ PackageArchitecture: amd64
+ ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcEnviron:
+  LANG=en_GB.UTF-8
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+ ProcFB: 0 qxldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.3.0-7-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
+ Tags: mantic third-party-packages wayland-session
+ TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
+ Uname: Linux 6.3.0-7-generic x86_64
+ UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages. If that does not 
work, then remove related third party packages and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
+ _MarkForUpload: True
+ dmi.bios.date: 04/01/2014
+ dmi.bios.release: 0.0
+ dmi.bios.vendor: SeaBIOS
+ dmi.bios.version: 1.16.0-debian-1.16.0-5
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: pc-q35-7.2
+ dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-5:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.2:cvnQEMU:ct1:cvrpc-q35-7.2:sku:
+ dmi.product.name: Standard PC (Q35 + ICH9, 2009)
+ dmi.product.version: pc-q35-7.2
+ dmi.sys.vendor: QEMU

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

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

Title:
  installing with lvm and encryption requires arrow key spam after
  reboot to get to encryption passphrase prompt

Status in subiquity:
  New
Status in plymouth package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  This also happens with the canary image and is happening with the
  Mantic daily image.

  When installing with LVM and encryption, after the "remove
  installation medium and press enter to reboot", the user is greeted
  with a permanent black screen. After pressing arrow keys, the gui
  prompt is then shown to prompt the user to put in the encryption
  passphrase.

  It is also somehow possible to not get the black screen by changing
  the grub 

[Desktop-packages] [Bug 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

2023-08-30 Thread Tim Andersson
This isn't an issue in Lunar which has these packages installed:
```
ubuntu@ubuntu:~$ apt list --installed | grep fonts-noto

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

fonts-noto-cjk/lunar,now 1:20220127+repack1-1 all [installed,automatic]
fonts-noto-color-emoji/lunar,now 2.038-1 all [installed,automatic]
fonts-noto-mono/lunar,now 20201225-1build1 all [installed,automatic]
```
However in Mantic:
```
ubuntu@ubuntu:~$ apt list --installed | grep fonts-noto

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

fonts-noto-cjk/mantic,now 1:20220127+repack1-1 all [installed,automatic]
fonts-noto-color-emoji/mantic,now 2.038-1 all [installed,automatic]
fonts-noto-core/mantic,now 20201225-2 all [installed,automatic]
fonts-noto-mono/mantic,now 20201225-2 all [installed,automatic]
```

Does this suffice?

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

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

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

2023-08-30 Thread Tim Andersson
apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/2033377/+attachment/5696400/+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/2033377

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

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

2023-08-30 Thread Tim Andersson
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2033377/+attachment/5696399/+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/2033377

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033377/+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 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

2023-08-30 Thread Tim Andersson
I've added all the relevant information for you.

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

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

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

2023-08-30 Thread Tim Andersson
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/2033377/+attachment/5696398/+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/2033377

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033377/+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 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

2023-08-30 Thread Tim Andersson
apport information

** Tags added: apport-collected wayland-session

** Description changed:

- This has been confirmed in the daily canary image and the daily normal
- mantic image. This whitespace didn't exist in older images or in
- previous releases. An image will be attached in the comments
+ This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu2
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CloudArchitecture: x86_64
+ CloudID: none
+ CloudName: none
+ CloudPlatform: none
+ CloudSubPlatform: config
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2023-08-30 (0 days ago)
+ InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
+ Package: gnome-shell 44.3-1ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+ ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
+ RelatedPackageVersions: mutter-common 44.3-1ubuntu1
+ Tags: mantic wayland-session
+ Uname: Linux 6.3.0-7-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sudo users
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2033377/+attachment/5696397/+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/2033377

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This has been confirmed in the daily canary image and the daily normal mantic 
image. This whitespace didn't exist in older images or in previous releases. An 
image will be attached in the comments
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-08-30 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230829)
  Package: gnome-shell 44.3-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  RelatedPackageVersions: mutter-common 44.3-1ubuntu1
  Tags: mantic wayland-session
  Uname: Linux 6.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033377/+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 2033377] Re: New whitespace between digits and colon in time at top of desktop screen

2023-08-29 Thread Tim Andersson
** Attachment added: "Screenshot from 2023-08-29 08-37-56.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033377/+attachment/5696033/+files/Screenshot%20from%202023-08-29%2008-37-56.png

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

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This has been confirmed in the daily canary image and the daily normal
  mantic image. This whitespace didn't exist in older images or in
  previous releases. An image will be attached in the comments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033377/+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 2033377] [NEW] New whitespace between digits and colon in time at top of desktop screen

2023-08-29 Thread Tim Andersson
Public bug reported:

This has been confirmed in the daily canary image and the daily normal
mantic image. This whitespace didn't exist in older images or in
previous releases. An image will be attached in the comments

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

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

Title:
  New whitespace between digits and colon in time at top of desktop
  screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This has been confirmed in the daily canary image and the daily normal
  mantic image. This whitespace didn't exist in older images or in
  previous releases. An image will be attached in the comments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033377/+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 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors

2023-05-30 Thread Tim Holmes-Mitra
Fixes in proposed resolves the issue for me.

After testing I removed the packages because overview was very laggy on
my Z16 but only when connected to an external monitor. Not sure if its
related?

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

Title:
  cursor does not track window when dragging between monitors with
  different scaling factors

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Lunar:
  Fix Committed

Bug description:
  Impact
  ---
  I have two screens. My laptop is using 200% scaling and the other external 
screen is using 100% scaling. When I drag windows between the monitors the 
cursor moves to unexpected locations when it moves onto another screen with a 
different scaling factor.

  I would expect the cursor to stay in the relative location when I
  started dragging the window. Hopefully this is clear the the attached
  screencast.

  Test Case
  -
  1. Install the update
  2. Log out
  3. Log back in
  4. If not already done, open the Settings app. Click one of the displays in 
the list and set it to 200%. Leave your other display at 100%.
  5. Drag a window from one screen to the other.
  The cursor and window should smoothly transition from one displays to the 
other without the cursor jumping dramatically to a different location when it 
crosses between the displays.

  Other Info
  --
  Setting different scaling for different displays requires Wayland. This will 
not work with the Ubuntu on Xorg session.

  What Could Go Wrong
  ---
  This fix is included in the upstream mutter 44.1 release. See LP: #2020225 
for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:04:51 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2015861/+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 2000644] Re: switching workspaces with shortcut sometimes freezes screen

2023-05-24 Thread Tim Holmes-Mitra
The workaround resolves the freeze for me so thanks for that.

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

Title:
  switching workspaces with shortcut sometimes freezes screen

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

Bug description:
  The bottom panel with dots to show which workspace you are on when
  switching with ctrl+alt+arrow sometimes doesn't disappear and gets
  stuck in a half faded or not faded state.  In that state the mouse
  appear stuck and the screen freezes until the super key is pressed to
  show overview or the workspace is switched again.

  Ubuntu 22.10, gnome-shell 43.1-0ubuntu1, Wayland, Nvidia on-demand,
  Nvidia driver 525.60.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2000644/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2023-05-12 Thread Tim Woelfle
I'm now on Ubuntu 23.04 (incl. new kernel) and managed to make the bass
work on my Lenovo Yoga 9 14IAP7 through this trick:
https://wiki.archlinux.org/title/Lenovo_Yoga_9i_2022_(14AiPI7)#Audio

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

2023-04-28 Thread Tim Andersson
Okay, ?th time lucky

** Patch removed: "mysuperpatch.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5669367/+files/mysuperpatch.debdiff

** Patch added: "mysuperpatch.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5669368/+files/mysuperpatch.debdiff

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in edubuntu-meta package in Ubuntu:
  New
Status in kubuntu-meta package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

2023-04-28 Thread Tim Andersson
** Patch removed: "mysuperpatch.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5669357/+files/mysuperpatch.debdiff

** Patch removed: "mysuperpatch.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5668944/+files/mysuperpatch.debdiff

** Patch added: "mysuperpatch.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5669367/+files/mysuperpatch.debdiff

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in edubuntu-meta package in Ubuntu:
  New
Status in kubuntu-meta package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

2023-04-28 Thread Tim Andersson
Launchpad is failing when I try to add ubuntu-studio-meta to this bug
report, not sure why

** Also affects: edubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntukylin-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in edubuntu-meta package in Ubuntu:
  New
Status in kubuntu-meta package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New
Status in ubuntukylin-meta package in Ubuntu:
  New
Status in ubuntustudio-meta package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-meta/+bug/2017786/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

2023-04-28 Thread Tim Andersson
Please find attached updated debdiff

** Patch added: "mysuperpatch.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5669357/+files/mysuperpatch.debdiff

** Also affects: ubuntu-unity-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntucinnamon-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: kubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: lubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in kubuntu-meta package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  New
Status in ubuntu-budgie-meta package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-unity-meta package in Ubuntu:
  New
Status in ubuntucinnamon-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/2017786/+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 2017786] Re: update script in ubuntu-meta not handling germinate or specified versions

2023-04-26 Thread Tim Andersson
** Patch added: "mysuperpatch.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+attachment/5668944/+files/mysuperpatch.debdiff

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 2017786] [NEW] update script in ubuntu-meta not handling germinate or specified versions

2023-04-26 Thread Tim Andersson
Public bug reported:

update script handled debootstrap and devscripts, does not handle
germinate. also doesn't handle potential specified versions in the
package directory.

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

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

Title:
  update script in ubuntu-meta not handling germinate or specified
  versions

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  update script handled debootstrap and devscripts, does not handle
  germinate. also doesn't handle potential specified versions in the
  package directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2017786/+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 995406] Re: User not added to group sambashare: "You do not have permission to create a usershare."

2023-04-13 Thread Tim Richardson
This is happening in lunar beta 23.04,.
I install nautilus-share. 
Turned on sharing in Gnome preference (both options)
When attempting to share a folder:

'net usershare' returned error 255: net usershare: cannot open usershare 
directory /var/lib/samba/usershares. Error Permission denied
You do not have permission to create a usershare. Ask your administrator to 
grant you permissions to create a share.

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

Title:
  User not added to group sambashare:  "You do not have permission to
  create a usershare."

Status in nautilus-share package in Ubuntu:
  Confirmed

Bug description:
  I tried to share a folder and was prompted to install samba, which I 
accepted. I did not install pam-smbpass as I don't need it. I was prompted to 
log out and in again, which I did. Now I get this when creating a share:
  ---
  'net usershare' returned error 255: net usershare: cannot open usershare 
directory /var/lib/samba/usershares. Error Permission denied
  You do not have permission to create a usershare. Ask your administrator to 
grant you permissions to create a share.
  ---
  It looks like the user was not added to the group sambashare at all (which 
script is supposed to do this? Where is the log file?).

  Manually running
  # sudo usermod -a -G sambashare jakob
  fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus-share 0.7.3-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Sun May  6 11:37:08 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  SourcePackage: nautilus-share
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/995406/+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 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors

2023-04-11 Thread Tim Holmes-Mitra
** Tags added: rls-ll-incoming

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

Title:
  cursor does not track window when dragging between monitors with
  different scaling factors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have two screens. My laptop is using 200% scaling and the other
  external screen is using 100% scaling. When I drag windows between the
  monitors the cursor moves to unexpected locations when it moves onto
  another screen with a different scaling factor.

  I would expect the cursor to stay in the relative location when I
  started dragging the window. Hopefully this is clear the the attached
  screencast.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:04:51 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015861/+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 2015863] Re: authentication prompt does not respect monitor scaling when there are multiple monitors

2023-04-11 Thread Tim Holmes-Mitra
** Tags added: rls-ll-incoming

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

Title:
  authentication prompt does not respect monitor scaling when there are
  multiple monitors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When the graphical authentication prompt is displayed it follows the
  scaling of the primary monitor even if its displayed on another
  monitor with a different scaling factor.

  In the attached screenshot I've triggered the prompt on my external
  monitor which is at 100% scaling. The primary monitor on my laptop is
  using 200% scaling.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:13:36 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015863/+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 2015865] Re: window size changing randomly

2023-04-11 Thread Tim Holmes-Mitra
** Tags added: rls-ll-incoming

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

Title:
  window size changing randomly

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I create an additional window for an application the previous
  windows size changes abruptly and without any user action.
  Additionally, placement of new windows seems random and unpredictable.

  I've attached a video to demonstrate this when I launch gnome-console
  using `CTRL+ALT+T`. You can see sometimes it is full screen, other
  times its in the top left quadrant, and then when i spawn an
  additional window the previous window's size changes.

  I am experiencing the same behavior with Files.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:29:40 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015865/+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 2015865] [NEW] window size changing randomly

2023-04-11 Thread Tim Holmes-Mitra
Public bug reported:

When I create an additional window for an application the previous
windows size changes abruptly and without any user action. Additionally,
placement of new windows seems random and unpredictable.

I've attached a video to demonstrate this when I launch gnome-console
using `CTRL+ALT+T`. You can see sometimes it is full screen, other times
its in the top left quadrant, and then when i spawn an additional window
the previous window's size changes.

I am experiencing the same behavior with Files.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 11 11:29:40 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-04-05 (5 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
RelatedPackageVersions: mutter-common 44.0-2ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screencast from 2023-04-11 11-25-37.webm"
   
https://bugs.launchpad.net/bugs/2015865/+attachment/5662974/+files/Screencast%20from%202023-04-11%2011-25-37.webm

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

Title:
  window size changing randomly

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I create an additional window for an application the previous
  windows size changes abruptly and without any user action.
  Additionally, placement of new windows seems random and unpredictable.

  I've attached a video to demonstrate this when I launch gnome-console
  using `CTRL+ALT+T`. You can see sometimes it is full screen, other
  times its in the top left quadrant, and then when i spawn an
  additional window the previous window's size changes.

  I am experiencing the same behavior with Files.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:29:40 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015865/+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 2015861] Re: cursor does not track window when dragging between monitors with different scaling factors

2023-04-11 Thread Tim Holmes-Mitra
** Description changed:

  I have two screens. My laptop is using 200% scaling and the other
  external screen is using 100% scaling. When I drag windows between the
  monitors the cursor moves to unexpected locations when it moves onto
  another screen with a different scaling factor.
  
  I would expect the cursor to stay in the relative location when I
  started dragging the window. Hopefully this is clear the the attached
  screencast.
- 
- - running lunar lobster and a wayland session
- - Gnome 44.0
- - Lenovo ThinkPad X1 Carbon Gen 9
- - 11th Gen Intel® Core™ i7-1165G7 × 8
- - Intel® Xe Graphics (TGL GT2)
- - Linux 6.2.0-19-generic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:04:51 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  cursor does not track window when dragging between monitors with
  different scaling factors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have two screens. My laptop is using 200% scaling and the other
  external screen is using 100% scaling. When I drag windows between the
  monitors the cursor moves to unexpected locations when it moves onto
  another screen with a different scaling factor.

  I would expect the cursor to stay in the relative location when I
  started dragging the window. Hopefully this is clear the the attached
  screencast.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:04:51 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015861/+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 2015864] [NEW] tiling only triggers if window is dragged from titlebar

2023-04-11 Thread Tim Holmes-Mitra
Public bug reported:

When you drag a window from the title bar title works as expected.
However, if you use the "window action key" to drag a window from
elsewhere tiling does not trigger. I've attached a screencast to show
the issue.

This works for the gnome half screen tiling so I would expect the same
behaviour with the tiling assistant.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 11 11:18:36 2023
InstallationDate: Installed on 2023-04-05 (5 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-tiling-assistant
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screencast from 2023-04-11 11-17-46.webm"
   
https://bugs.launchpad.net/bugs/2015864/+attachment/5662970/+files/Screencast%20from%202023-04-11%2011-17-46.webm

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

Title:
  tiling only triggers if window is dragged from titlebar

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  New

Bug description:
  When you drag a window from the title bar title works as expected.
  However, if you use the "window action key" to drag a window from
  elsewhere tiling does not trigger. I've attached a screencast to show
  the issue.

  This works for the gnome half screen tiling so I would expect the same
  behaviour with the tiling assistant.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:18:36 2023
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-tiling-assistant
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2015864/+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 2015863] [NEW] authentication prompt does not respect monitor scaling when there are multiple monitors

2023-04-11 Thread Tim Holmes-Mitra
Public bug reported:

When the graphical authentication prompt is displayed it follows the
scaling of the primary monitor even if its displayed on another monitor
with a different scaling factor.

In the attached screenshot I've triggered the prompt on my external
monitor which is at 100% scaling. The primary monitor on my laptop is
using 200% scaling.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 11 11:13:36 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-04-05 (5 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
RelatedPackageVersions: mutter-common 44.0-2ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screenshot from 2023-04-11 11-05-28.png"
   
https://bugs.launchpad.net/bugs/2015863/+attachment/5662963/+files/Screenshot%20from%202023-04-11%2011-05-28.png

** Summary changed:

- authenitcation prompt does not respect monitor scaling
+ authentication prompt does not respect monitor scaling when there are 
multiple monitors

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

Title:
  authentication prompt does not respect monitor scaling when there are
  multiple monitors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When the graphical authentication prompt is displayed it follows the
  scaling of the primary monitor even if its displayed on another
  monitor with a different scaling factor.

  In the attached screenshot I've triggered the prompt on my external
  monitor which is at 100% scaling. The primary monitor on my laptop is
  using 200% scaling.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:13:36 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015863/+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 2015861] [NEW] cursor does not track window when dragging between monitors with different scaling factors

2023-04-11 Thread Tim Holmes-Mitra
Public bug reported:

I have two screens. My laptop is using 200% scaling and the other
external screen is using 100% scaling. When I drag windows between the
monitors the cursor moves to unexpected locations when it moves onto
another screen with a different scaling factor.

I would expect the cursor to stay in the relative location when I
started dragging the window. Hopefully this is clear the the attached
screencast.

- running lunar lobster and a wayland session
- Gnome 44.0
- Lenovo ThinkPad X1 Carbon Gen 9
- 11th Gen Intel® Core™ i7-1165G7 × 8
- Intel® Xe Graphics (TGL GT2)
- Linux 6.2.0-19-generic

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 11 11:04:51 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-04-05 (5 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
RelatedPackageVersions: mutter-common 44.0-2ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "Screencast from 2023-04-11 11-03-57.webm"
   
https://bugs.launchpad.net/bugs/2015861/+attachment/5662945/+files/Screencast%20from%202023-04-11%2011-03-57.webm

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

Title:
  cursor does not track window when dragging between monitors with
  different scaling factors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have two screens. My laptop is using 200% scaling and the other
  external screen is using 100% scaling. When I drag windows between the
  monitors the cursor moves to unexpected locations when it moves onto
  another screen with a different scaling factor.

  I would expect the cursor to stay in the relative location when I
  started dragging the window. Hopefully this is clear the the attached
  screencast.

  - running lunar lobster and a wayland session
  - Gnome 44.0
  - Lenovo ThinkPad X1 Carbon Gen 9
  - 11th Gen Intel® Core™ i7-1165G7 × 8
  - Intel® Xe Graphics (TGL GT2)
  - Linux 6.2.0-19-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 11 11:04:51 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-04-05 (5 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230404)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015861/+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 2013073] Re: gnome-shell: extension fails to install if no "schemas" folder present

2023-03-28 Thread Tim Holmes-Mitra
Fix already merged upstream - https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2727

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

Title:
  gnome-shell: extension fails to install if no "schemas" folder present

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Gnome-shell extensions fail to install if the extension does not have
  a 'schemas' folder. I can replicate this behaviour when installing
  from extensions.gnome.org or gnome-shell-extension-manager. By adding
  an empty schema's folder the extension installs correctly.

  I have checked the gjs extension documentation[1] and afaict the
  'schemas'  folder is not listed as required.

  Relevant logs when installing the weatheroclock[2] extension:

  ```
  Mar 28 12:38:07 eart gnome-shell[1444369]: Archive:  
/tmp/HNKP21.shell-extension.zip
  Mar 28 12:38:07 eart gnome-shell[1444369]:   inflating: 
/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/extension.js
  Mar 28 12:38:07 eart gnome-shell[1444369]:   inflating: 
/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/stylesheet.css
  Mar 28 12:38:07 eart gnome-shell[1444369]:  extracting: 
/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/metadata.json
  Mar 28 12:38:07 eart gnome-shell[1423521]: Error while installing 
weatherocl...@cleomenezesjr.github.io: Error when getting information for file 
“/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/schemas”:
 No such file or directory
  Mar 28 12:38:07 eart extension-manag[1426090]: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code36: 
GDBus.Error:org.gnome.Shell.ExtensionError: Error when getting information for 
file 
“/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/schemas”:
 No such file or directory

  ```

  [1] https://gjs.guide/extensions/overview/anatomy.html#metadata-json-required
  [2] https://extensions.gnome.org/extension/5470/weather-oclock/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013073/+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 2013099] [NEW] overview: windows temporarily vanish when creating workspace to the left

2023-03-28 Thread Tim Holmes-Mitra
Public bug reported:

When you activate overview you can drop a windows to the left / right of
the row of workspaces found just below the search input box at the top
of the screen.

If you have windows on 2+ workspaces (so 3 are shown in overview with
the rightmost empty) and you drag a window to the left to create a new
left-position workspace the windows on your current overview vanish for
a few seconds and then reappear.

Easier to watch the attached screencast.

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


** Tags: lunar rls-ll-incoming

** Attachment added: "Screencast from 2023-03-28 16-09-29.webm"
   
https://bugs.launchpad.net/bugs/2013099/+attachment/5658333/+files/Screencast%20from%202023-03-28%2016-09-29.webm

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

Title:
  overview: windows temporarily vanish when creating workspace to the
  left

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When you activate overview you can drop a windows to the left / right
  of the row of workspaces found just below the search input box at the
  top of the screen.

  If you have windows on 2+ workspaces (so 3 are shown in overview with
  the rightmost empty) and you drag a window to the left to create a new
  left-position workspace the windows on your current overview vanish
  for a few seconds and then reappear.

  Easier to watch the attached screencast.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013099/+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 2013073] [NEW] gnome-shell: extension fails to install if no "schemas" folder present

2023-03-28 Thread Tim Holmes-Mitra
Public bug reported:

Gnome-shell extensions fail to install if the extension does not have a
'schemas' folder. I can replicate this behaviour when installing from
extensions.gnome.org or gnome-shell-extension-manager. By adding an
empty schema's folder the extension installs correctly.

I have checked the gjs extension documentation[1] and afaict the
'schemas'  folder is not listed as required.

Relevant logs when installing the weatheroclock[2] extension:

```
Mar 28 12:38:07 eart gnome-shell[1444369]: Archive:  
/tmp/HNKP21.shell-extension.zip
Mar 28 12:38:07 eart gnome-shell[1444369]:   inflating: 
/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/extension.js
Mar 28 12:38:07 eart gnome-shell[1444369]:   inflating: 
/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/stylesheet.css
Mar 28 12:38:07 eart gnome-shell[1444369]:  extracting: 
/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/metadata.json
Mar 28 12:38:07 eart gnome-shell[1423521]: Error while installing 
weatherocl...@cleomenezesjr.github.io: Error when getting information for file 
“/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/schemas”:
 No such file or directory
Mar 28 12:38:07 eart extension-manag[1426090]: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code36: 
GDBus.Error:org.gnome.Shell.ExtensionError: Error when getting information for 
file 
“/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/schemas”:
 No such file or directory

```

[1] https://gjs.guide/extensions/overview/anatomy.html#metadata-json-required
[2] https://extensions.gnome.org/extension/5470/weather-oclock/

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


** Tags: lunar rls-ll-incoming

** Tags added: rls-ll-incoming

** Summary changed:

- extensions: extension fails to install if no "schemas" folder present
+ gnome-shell: extension fails to install if no "schemas" folder present

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

Title:
  gnome-shell: extension fails to install if no "schemas" folder present

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Gnome-shell extensions fail to install if the extension does not have
  a 'schemas' folder. I can replicate this behaviour when installing
  from extensions.gnome.org or gnome-shell-extension-manager. By adding
  an empty schema's folder the extension installs correctly.

  I have checked the gjs extension documentation[1] and afaict the
  'schemas'  folder is not listed as required.

  Relevant logs when installing the weatheroclock[2] extension:

  ```
  Mar 28 12:38:07 eart gnome-shell[1444369]: Archive:  
/tmp/HNKP21.shell-extension.zip
  Mar 28 12:38:07 eart gnome-shell[1444369]:   inflating: 
/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/extension.js
  Mar 28 12:38:07 eart gnome-shell[1444369]:   inflating: 
/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/stylesheet.css
  Mar 28 12:38:07 eart gnome-shell[1444369]:  extracting: 
/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/metadata.json
  Mar 28 12:38:07 eart gnome-shell[1423521]: Error while installing 
weatherocl...@cleomenezesjr.github.io: Error when getting information for file 
“/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/schemas”:
 No such file or directory
  Mar 28 12:38:07 eart extension-manag[1426090]: 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code36: 
GDBus.Error:org.gnome.Shell.ExtensionError: Error when getting information for 
file 
“/home/tim/.local/share/gnome-shell/extensions/weatherocl...@cleomenezesjr.github.io/schemas”:
 No such file or directory

  ```

  [1] https://gjs.guide/extensions/overview/anatomy.html#metadata-json-required
  [2] https://extensions.gnome.org/extension/5470/weather-oclock/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013073/+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 2013060] [NEW] mutter: nightlight stuck on second monitor when resuming

2023-03-28 Thread Tim Holmes-Mitra
Public bug reported:

I have a dual monitor setup running on AMD RX 480 + wayland + lunar
lobster. If I suspend my machine while night light is enabled and then
resume it a few hours later when night light should now be disabled,
night light is still enabled on the 2nd monitor -- hopefully apparent in
the attached screen shot on the right monitor.

** Affects: mutter (Ubuntu)
 Importance: Low
 Status: New


** Tags: gamma lunar nightlight

** Attachment added: "Screenshot from 2023-03-28 11-49-58.png"
   
https://bugs.launchpad.net/bugs/2013060/+attachment/5658233/+files/Screenshot%20from%202023-03-28%2011-49-58.png

** Description changed:

  I have a dual monitor setup running on AMD RX 480 + wayland + lunar
  lobster. If I suspend my machine while night light is enabled and then
  resume it a few hours later when night light should now be disabled,
  night light is still enabled on the 2nd monitor -- hopefully apparent in
- the attached screen shot.
+ the attached screen shot on the right monitor.

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

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

Title:
  mutter: nightlight stuck on second monitor when resuming

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup running on AMD RX 480 + wayland + lunar
  lobster. If I suspend my machine while night light is enabled and then
  resume it a few hours later when night light should now be disabled,
  night light is still enabled on the 2nd monitor -- hopefully apparent
  in the attached screen shot on the right monitor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2013060/+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 2012994] Re: Automatic Date & Time switch shows as insensitive when enabled

2023-03-28 Thread Tim Holmes-Mitra
You can get various wonky states when playing with the toggles
including:

- enable colouring when the "Automatic Date & Time" toggle was disabled
- after toggling several times it appears to get out of sync and a few seconds 
later will switch the toggle state seemingly without any interaction

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

Title:
  Automatic Date & Time switch shows as insensitive when enabled

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

Bug description:
  Go to Settings > Date & Time and toggle the "Automatic Date & Time"
  switch. When enabled it shows as insensitive (i.e. grey instead of
  orange). The "Automatic Time Zone" switch below behaves as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012994/+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 2012736] Re: language and region > login screen > formats does not display United Kingdom

2023-03-24 Thread Tim Holmes-Mitra
I've been able to re-create the issue on my laptop after adding a second
user so not sure what the difference is in my setups. As requested:

```
[I] tim@saturn ~> cat /etc/default/locale
LANG=en_GB.UTF-8
[I] tim@saturn ~> locale -a
C
C.utf8
en_AG
en_AG.utf8
en_AU.utf8
en_BW.utf8
en_CA.utf8
en_DK.utf8
en_GB.utf8
en_HK.utf8
en_IE.utf8
en_IL
en_IL.utf8
en_IN
en_IN.utf8
en_NG
en_NG.utf8
en_NZ.utf8
en_PH.utf8
en_SG.utf8
en_US.utf8
en_ZA.utf8
en_ZM
en_ZM.utf8
en_ZW.utf8
POSIX
[I] tim@saturn ~> locale
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
```

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

Title:
  language and region > login screen > formats does not display United
  Kingdom

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

Bug description:
  When there are multiple accounts on a machine the "Language and
  Region" settings screen shows a "Login Screen" section. Under the
  "Formats", if "Canada" is selected then the UI shows "Canada",
  however, if "United Kingdom" is selected then the Formats section
  displays "United States".

  It displays correctly under the "Your Account" section.

  I have attached a screen recording to demonstrate.

  This is on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012736/+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 2012736] Re: language and region > login screen > formats does not display United Kingdom

2023-03-24 Thread Tim Holmes-Mitra
** Description changed:

  When there are multiple accounts on a machine the "Language and Region"
- settings screen shows a "Login Screen" section. Under the "Formats"
- heading, if "Canada" is selected then the UI shows "Canada", however, if
- "United Kingdom" is selected then the Formats section displays "United
- States".
+ settings screen shows a "Login Screen" section. Under the "Formats", if
+ "Canada" is selected then the UI shows "Canada", however, if "United
+ Kingdom" is selected then the Formats section displays "United States".
+ 
+ It displays correctly under the "Your Account" section.
  
  I have attached a screen recording to demonstrate.
  
  This is on Lunar.

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

Title:
  language and region > login screen > formats does not display United
  Kingdom

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

Bug description:
  When there are multiple accounts on a machine the "Language and
  Region" settings screen shows a "Login Screen" section. Under the
  "Formats", if "Canada" is selected then the UI shows "Canada",
  however, if "United Kingdom" is selected then the Formats section
  displays "United States".

  It displays correctly under the "Your Account" section.

  I have attached a screen recording to demonstrate.

  This is on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012736/+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 2012738] Re: language support crashes on install missing translations or writing aids

2023-03-24 Thread Tim Holmes-Mitra
Stack trace from journalctl

** Attachment added: "logging.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012738/+attachment/5657278/+files/logging.txt

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

Title:
  language support crashes on install missing translations or writing
  aids

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

Bug description:
  Installing missing "translations or writing aids" crashes the gnome-
  language-selector app.

  I have attached a recording (sorry should have had capture cursor on)
  and relevant stack trace from journalctl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012738/+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 2012738] [NEW] language support crashes on install missing translations or writing aids

2023-03-24 Thread Tim Holmes-Mitra
Public bug reported:

Installing missing "translations or writing aids" crashes the gnome-
language-selector app.

I have attached a recording (sorry should have had capture cursor on)
and relevant stack trace from journalctl.

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


** Tags: bug lunar rls-ll-incoming

** Attachment added: "Screencast from 2023-03-24 13-56-47.webm"
   
https://bugs.launchpad.net/bugs/2012738/+attachment/5657277/+files/Screencast%20from%202023-03-24%2013-56-47.webm

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

Title:
  language support crashes on install missing translations or writing
  aids

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

Bug description:
  Installing missing "translations or writing aids" crashes the gnome-
  language-selector app.

  I have attached a recording (sorry should have had capture cursor on)
  and relevant stack trace from journalctl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012738/+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 2012736] [NEW] language and region > login screen > formats does not display United Kingdom

2023-03-24 Thread Tim Holmes-Mitra
Public bug reported:

When there are multiple accounts on a machine the "Language and Region"
settings screen shows a "Login Screen" section. Under the "Formats"
heading, if "Canada" is selected then the UI shows "Canada", however, if
"United Kingdom" is selected then the Formats section displays "United
States".

I have attached a screen recording to demonstrate.

This is on Lunar.

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


** Tags: bug lunar rls-ll-incoming

** Attachment added: "Screencast from 2023-03-24 12-24-46.webm"
   
https://bugs.launchpad.net/bugs/2012736/+attachment/5657275/+files/Screencast%20from%202023-03-24%2012-24-46.webm

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

Title:
  language and region > login screen > formats does not display United
  Kingdom

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

Bug description:
  When there are multiple accounts on a machine the "Language and
  Region" settings screen shows a "Login Screen" section. Under the
  "Formats" heading, if "Canada" is selected then the UI shows "Canada",
  however, if "United Kingdom" is selected then the Formats section
  displays "United States".

  I have attached a screen recording to demonstrate.

  This is on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012736/+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 2012670] [NEW] plymouth: font missing at decrypt root prompt

2023-03-23 Thread Tim Holmes-Mitra
Public bug reported:

Fonts are missing (incorrectly displayed) at the plymouth splash screen
when prompting for the luks decryption passphrase (ie just below the
input box).

I have the same issue on my laptop (where this report has been
generated) and my desktop (where the photo is from).

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: plymouth 22.02.122-3ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 23 19:40:58 2023
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2023-03-14 (9 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: LENOVO 20XW0055UK
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: Upgraded to lunar on 2023-03-22 (1 days ago)
dmi.bios.date: 02/09/2023
dmi.bios.release: 1.59
dmi.bios.vendor: LENOVO
dmi.bios.version: N32ET83W (1.59 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20XW0055UK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.33
dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET83W(1.59):bd02/09/2023:br1.59:efr1.33:svnLENOVO:pn20XW0055UK:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XW0055UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
dmi.product.family: ThinkPad X1 Carbon Gen 9
dmi.product.name: 20XW0055UK
dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
dmi.product.version: ThinkPad X1 Carbon Gen 9
dmi.sys.vendor: LENOVO

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


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

** Attachment added: "IMG_0743.jpeg"
   
https://bugs.launchpad.net/bugs/2012670/+attachment/5657012/+files/IMG_0743.jpeg

** Description changed:

  Fonts are missing (incorrectly displayed) at the plymouth splash screen
- when prompting for the luks decryption passphrase.
+ when prompting for the luks decryption passphrase (ie just below the
+ input box).
  
  I have the same issue on my laptop (where this report has been
  generated) and my desktop (where the photo is from).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: plymouth 22.02.122-3ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 23 19:40:58 2023
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2023-03-14 (9 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 20XW0055UK
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: Upgraded to lunar on 2023-03-22 (1 days ago)
  dmi.bios.date: 02/09/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET83W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XW0055UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET83W(1.59):bd02/09/2023:br1.59:efr1.33:svnLENOVO:pn20XW0055UK:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XW0055UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XW0055UK
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

Title:
  plymouth: font missing at decrypt root prompt

Status in plymouth package in Ubuntu:
  New

Bug description:
  Fonts are missing (incorrectly displayed) at the 

[Desktop-packages] [Bug 2012527] [NEW] gnome-control-center: mouse scroll direction images missing

2023-03-22 Thread Tim Holmes-Mitra
*** This bug is a duplicate of bug 2011849 ***
https://bugs.launchpad.net/bugs/2011849

Public bug reported:

The new "Mouse & Touchpad" pane has a "Scroll Direction" section. The
images to explain what the setting means are missing in 23.04.

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

** Attachment added: "Screenshot from 2023-03-22 15-54-53.png"
   
https://bugs.launchpad.net/bugs/2012527/+attachment/5656614/+files/Screenshot%20from%202023-03-22%2015-54-53.png

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

Title:
  gnome-control-center: mouse scroll direction images missing

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

Bug description:
  The new "Mouse & Touchpad" pane has a "Scroll Direction" section. The
  images to explain what the setting means are missing in 23.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012527/+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 1996905] Re: Minimise window fails first time

2022-11-17 Thread Tim Passingham
I removed libreoffice-gnome and -gtk3, and the problem went away.  My
version now shows:

Version: 7.4.2.3 / LibreOffice Community
Build ID: 40(Build:3)
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1
Calc: threaded

It's not as user friendly.

Note that my original problem only seems to occur when I open the start
center already full screen from the last time I opened it.

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

Title:
  Minimise window fails first time

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Opening libreoffice full screen, pressing the button at top right to
  shrink the window causes the window to expand beyond the edge of the
  screen.  It is just possible to press it again on the edge of the
  screen, and LO goes back to normal full screen.  Pressing it again
  works normally.

  Version: 7.4.2.3 / LibreOffice Community
  Build ID: 40(Build:3)
  CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
  Locale: en-GB (en_GB.UTF-8); UI: en-GB
  Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1
  Calc: threaded

  In Windows 10 this doesn't happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996905/+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 1996905] Re: Minimise window fails first time

2022-11-17 Thread Tim Passingham
I mean the button that makes the window smaller, not the one that makes
it disappear to the toolbar.

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

Title:
  Minimise window fails first time

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Opening libreoffice full screen, pressing the button at top right to
  shrink the window causes the window to expand beyond the edge of the
  screen.  It is just possible to press it again on the edge of the
  screen, and LO goes back to normal full screen.  Pressing it again
  works normally.

  Version: 7.4.2.3 / LibreOffice Community
  Build ID: 40(Build:3)
  CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
  Locale: en-GB (en_GB.UTF-8); UI: en-GB
  Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1
  Calc: threaded

  In Windows 10 this doesn't happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996905/+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 1996905] [NEW] Minimise window fails first time

2022-11-17 Thread Tim Passingham
Public bug reported:

Opening libreoffice full screen, pressing the button at top right to
shrink the window causes the window to expand beyond the edge of the
screen.  It is just possible to press it again on the edge of the
screen, and LO goes back to normal full screen.  Pressing it again works
normally.

Version: 7.4.2.3 / LibreOffice Community
Build ID: 40(Build:3)
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-GB (en_GB.UTF-8); UI: en-GB
Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1
Calc: threaded

In Windows 10 this doesn't happen.

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

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

Title:
  Minimise window fails first time

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Opening libreoffice full screen, pressing the button at top right to
  shrink the window causes the window to expand beyond the edge of the
  screen.  It is just possible to press it again on the edge of the
  screen, and LO goes back to normal full screen.  Pressing it again
  works normally.

  Version: 7.4.2.3 / LibreOffice Community
  Build ID: 40(Build:3)
  CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
  Locale: en-GB (en_GB.UTF-8); UI: en-GB
  Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.22.04.1~lo1
  Calc: threaded

  In Windows 10 this doesn't happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1996905/+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 1994453] [NEW] Firefox Snap cannot be installed in an LXC Container

2022-10-25 Thread Tim Edwards
Public bug reported:

$ sudo snap install firefox
error: cannot perform the following tasks:
- Run hook connect-plug-host-hunspell of snap "firefox" (run hook 
"connect-plug-host-hunspell": 
-
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none 
bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission 
denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied
update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
error: error running snapctl: cannot start mount unit: systemctl command [start 
var-snap-firefox-common-host\x2dhunspell.mount] failed with exit status 1: A 
dependency job for var-snap-firefox-common-host\x2dhunspell.mount failed. See 
'journalctl -xe' for details.
-)


This makes it very difficult to have LXC containers with a GUI (used via VNC), 
as a web browser is essential.

Workaround:
- Add the Mozillateam PPA 
(https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu)

- Create /etc/apt/preferences.d/mozilla-firefox with:
Package: firefox*
Pin: release o=LP-PPA-mozillateam
Pin-Priority: 1001

- sudo apt install firefox

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Oct 26 14:16:04 2022
InstallationDate: Installed on 2020-11-02 (722 days ago)
InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: Upgraded to jammy on 2022-10-03 (22 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Firefox Snap cannot be installed in an LXC Container

Status in firefox package in Ubuntu:
  New

Bug description:
  $ sudo snap install firefox
  error: cannot perform the following tasks:
  - Run hook connect-plug-host-hunspell of snap "firefox" (run hook 
"connect-plug-host-hunspell": 
  -
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none 
bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission 
denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  error: error running snapctl: cannot start mount unit: systemctl command 
[start var-snap-firefox-common-host\x2dhunspell.mount] failed with exit status 
1: A dependency job for var-snap-firefox-common-host\x2dhunspell.mount failed. 
See 'journalctl -xe' for details.
  -)

  
  This makes it very difficult to have LXC containers with a GUI (used via 
VNC), as a web browser is essential.

  Workaround:
  - Add the Mozillateam PPA 
(https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu)

  - Create /etc/apt/preferences.d/mozilla-firefox with:
  Package: firefox*
  Pin: release o=LP-PPA-mozillateam
  Pin-Priority: 1001

  - sudo apt install firefox

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 26 14:16:04 2022
  InstallationDate: Installed on 2020-11-02 (722 days ago)
  InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-10-03 (22 days ago)

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


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

[Desktop-packages] [Bug 1981163]

2022-10-12 Thread tim
I came to report this bug but found it is already here.

I am on linux (Pop!_OS 22.04 LTS) and am using Thunderbird 102.2.2,
although this was also present in version 91 (I only upgraded recently).

I have Thunderbird set to use the system PDF application (in this case
Evince) for reading PDF files, which works perfectly for reading
messages sent to me.

However, when I attach a PDF document to an email and try to open it to
check something, it only gives me the option for Firefox. Fortunately,
Firefox can display PDF files but it is not the behaviour I
expected.Thanks for digging into it.

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

Title:
  [upstream] In Compose window, if a PDf is joined and clicked to open,
  Thunderbird launches Firefox instead of Evince

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

Bug description:
  In Thunderbird on Ubuntu Gnome, I set Evince as default program to
  open pdf files from Thunderbird.

  In received messages, and those saved on "Sent" folder, it works
  perfectly.

  But in the "Compose" window: if I add a pdf file to the message, and
  double-click on it to open and verify it, Thunderbird always uses
  Firefox to show it.

  In case Firefox is not installed (has been removed), I have an error
  message telling there is not associated application for pdf files and
  to go to Preferences - where Evince is already and still defined as
  default.

  It happens since many months and bug is still present in Thunderbird
  102 / Ubuntu 22.10 beta.

  It's not the same as bug 234349 as here, it's not an URL file but
  directly a pdf joined in a mail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1981163/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid

2022-09-03 Thread Tim Urberg
This worked for me as well with an HP OfficeJet Pro 9025.

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

Title:
  Printing does not work on Ubuntu 22.04 - cups-pki-invalid

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 22.04 printing did not work. There is cups-pki-
  invalid error and printer goes to paused state.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  Uname: Linux 5.17.7-051707-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 15:34:47 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-10-12 (214 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
  Lpstat: device for HP_Color_LaserJet_M552_5F80BF: 
implicitclass://HP_Color_LaserJet_M552_5F80BF/
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic 
root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago)
  dmi.bios.date: 03/29/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: G513QY.318
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G513QY
  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.ec.firmware.release: 0.81
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G513QY_G513QY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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 1988275] [NEW] Xephyr does not recognize keyboard or mouse

2022-08-31 Thread Tim Hawes
Public bug reported:

Xephyr window appears but then does not accept any input from keyboard
or mouse.

This seems related:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1289

Output is:

unrecognised device identifier: /dev/input/event3
unrecognised device identifier: /dev/input/event0
unrecognised device identifier: /dev/input/event2
unrecognised device identifier: /dev/input/event1
Kbd option key (_source) of value (server/udev) not assigned!
Kbd option key (major) of value (13) not assigned!
Kbd option key (minor) of value (70) not assigned!
Kbd option key (config_info) of value 
(udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:258A:003A.0001/input/input13/event6)
 not assigned!
couldn't find driver for keyboard device "HID 258a:003a" (/dev/input/event6)
unrecognised device identifier: /dev/input/event7
unrecognised device identifier: /dev/input/event8
unrecognised device identifier: /dev/input/event9
Pointer option key (_source) of value (server/udev) not assigned!
Pointer option key (major) of value (13) not assigned!
Pointer option key (minor) of value (74) not assigned!
Pointer option key (config_info) of value 
(udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:093A:2510.0003/input/input17/event10)
 not assigned!
couldn't find driver for pointer device "HID 093a:2510" (/dev/input/event10)
Pointer option key (_source) of value (server/udev) not assigned!
Pointer option key (major) of value (13) not assigned!
Pointer option key (minor) of value (33) not assigned!
Pointer option key (config_info) of value 
(udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:093A:2510.0003/input/input17/mouse1)
 not assigned!
couldn't find driver for pointer device "HID 093a:2510" (/dev/input/mouse1)
unrecognised device identifier: /dev/input/event12
unrecognised device identifier: /dev/input/event13
unrecognised device identifier: /dev/input/event14
unrecognised device identifier: /dev/input/event15
unrecognised device identifier: /dev/input/event16
unrecognised device identifier: /dev/input/event17
unrecognised device identifier: /dev/input/event18
unrecognised device identifier: /dev/input/event19
unrecognised device identifier: /dev/input/event11
Kbd option key (_source) of value (server/udev) not assigned!
Kbd option key (major) of value (13) not assigned!
Kbd option key (minor) of value (68) not assigned!
Kbd option key (config_info) of value 
(udev:/sys/devices/platform/i8042/serio0/input/input4/event4) not assigned!
couldn't find driver for keyboard device "AT Translated Set 2 keyboard" 
(/dev/input/event4)
unrecognised device identifier: /dev/input/event5
unrecognised device identifier: /dev/input/mouse0

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xserver-xephyr 2:21.1.3-2ubuntu2.1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Aug 31 03:59:02 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 
00 [VGA controller])
   Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2212]
InstallationDate: Installed on 2022-07-28 (33 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: System76 Galago Pro
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_el3sdk@/vmlinuz-5.15.0-46-generic 
root=ZFS=rpool/ROOT/ubuntu_el3sdk ro quiet splash vt.handoff=1
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2020
dmi.bios.release: 4.11
dmi.bios.vendor: coreboot
dmi.bios.version: 2020-05-20_de5eab8
dmi.board.name: Galago Pro
dmi.board.vendor: System76
dmi.board.version: galp4
dmi.chassis.type: 9
dmi.chassis.vendor: System76
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvncoreboot:bvr2020-05-20_de5eab8:bd05/13/2020:br4.11:efr0.0:svnSystem76:pnGalagoPro:pvrgalp4:rvnSystem76:rnGalagoPro:rvrgalp4:cvnSystem76:ct9:cvr:sku:
dmi.product.name: Galago Pro
dmi.product.version: galp4
dmi.sys.vendor: System76
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
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: 

[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2022-07-20 Thread Tim Woelfle
I have the same problem as Philipp Jungkamp and Clem Schum on the Yoga 9
14IAP7 on Ubuntu 22.04. Hope this can get fixed soon, thank you very
much to everyone who is involved!

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1971434] Re: Display powersave only blanks, but does not turn off

2022-05-29 Thread Tim
Same issue on 22.04 Gnome Wayland session, Nouveau driver on a Geforce
MX450 (Iris Xe Graphics onboard using i915 driver)

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

Title:
  Display powersave only blanks, but does not turn off

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  Recently upgraded to Ubuntu 22.04, and it seems like the power-saving
  feature in Gnome 42 does not actually turn off the screen(s) after X
  minutes, but just blanks them. When I manually run `xset dpms force
  off`, they do properly turn off and go to powersave mode.

  1) Description:   Ubuntu 22.04 LTS
 Release:   22.04

  2) gnome-settings-daemon:
Installed: 42.1-1ubuntu2
Candidate: 42.1-1ubuntu2

  3) In Settings -> Power -> Screen Blank, set the inactivity period to
  5 minutes. After 5 minutes, the screens should turn off.

  4) Screens go black, but remain active and consume (too much) power.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2020-07-04 (667 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Package: gnome-settings-daemon 42.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers 
video wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 1974254] Re: Probles with Clutter

2022-05-22 Thread Tim Blokdijk
Had this error, rebooting my system fixed it.

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

Title:
  Probles with Clutter

Status in clutter-gtk package in Ubuntu:
  Invalid

Bug description:
  Running Xubuntu 20.04.4

  I've started seeing all sorts of programs failing in the last week
  apparently due to clutter.  This includes Geeqie and Cheese, and
  possibly Zoom, although I haven't tracked down the problem there.  For
  example, when I try to start geeqie, I get:

  Can't initialize clutter-gtk.
  Start geeqie with the option: --disable-clutter

  When I try to run cheese I get:

  (cheese:1207183): Clutter-CRITICAL **: 17:54:24.432: Unable to
  initialize Clutter: Unable to initialize the Clutter backend: no
  available drivers found.

  ** (cheese:1207183): ERROR **: 17:54:24.432: cheese-application.vala:89: 
Unable to initialize libcheese-gtk
  Trace/BPT trap(coredump)

  In researching the problem I ran across this article:

  https://blogs.gnome.org/clutter/

  Now, I have no idea what clutter is/does, but it seems to now be
  retired.  Was the package removal back-ported to earlier releases of
  Ubuntu?  The gir1.2-gtkclutter-1.0, gir1-clutter-1.0 and
  gstreamer1.0-clutter-3.0 packages are still installed.

  Any guidelines here?  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1974254/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

2022-05-01 Thread Tim Richardson
see also https://bugzilla.redhat.com/show_bug.cgi?id=2072070 for lengthy
discussion.

** Bug watch added: Red Hat Bugzilla #2072070
   https://bugzilla.redhat.com/show_bug.cgi?id=2072070

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

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

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

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

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

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

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

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


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


[Desktop-packages] [Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions

2022-04-20 Thread Tim Blokdijk
It's fixed as far as I can see. Changed the status to 'Fix Released'.

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

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

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

Title:
  login screen shown twice with VirtualBox Guest Additions

Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  The login screen is shown twice and I have to supply the password
  twice. The system works normally afterwards.  When I select auto-login
  in the settings still one login screen is shown.

  gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
  Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
   Memory: 5.0M
  CPU: 125ms
   CGroup: /system.slice/gdm.service
   └─1915 /usr/sbin/gdm3

  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
  mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) 
by (uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate 
daemon control file
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password 
to try later in open session
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: 
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by 
(uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: 
gnome-keyring-daemon started properly and unlocked keyring
  mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was 
already dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 11:48:17 2022
  InstallationDate: Installed on 2020-01-25 (793 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+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 1966786] Re: login screen shown twice with VirtualBox Guest Additions

2022-04-17 Thread Tim Blokdijk
Can't reproduce the bug as of today (17 April). Suspect that it might
have been fixed with an update the last few days.

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

Title:
  login screen shown twice with VirtualBox Guest Additions

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is shown twice and I have to supply the password
  twice. The system works normally afterwards.  When I select auto-login
  in the settings still one login screen is shown.

  gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
  Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
   Memory: 5.0M
  CPU: 125ms
   CGroup: /system.slice/gdm.service
   └─1915 /usr/sbin/gdm3

  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
  mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) 
by (uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate 
daemon control file
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password 
to try later in open session
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: 
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by 
(uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: 
gnome-keyring-daemon started properly and unlocked keyring
  mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was 
already dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 11:48:17 2022
  InstallationDate: Installed on 2020-01-25 (793 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+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 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

2022-04-01 Thread Tim Richardson
Ubuntu 22.04. 
I still have this problem
intel-media-va-driver 22.3.0

tigerlake laptop

$ apt-cache show intel-media-va-driver
Package: intel-media-va-driver
Architecture: amd64
Version: 22.3.0+dfsg1-1


tim@ochre:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
tim@ochre:~$

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

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in intel-media-driver-non-free package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I noticed that it upgraded mesa to 22.x and now video acceleration is
  not working due to:

  ❯ vainfo 
  libva info: VA-API version 1.14.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_14
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_10
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  ~/Desktop 
  ❯ inxi -G
  Graphics:
Device-1: Intel driver: i915 v: kernel
Device-2: Generalplus GENERAL WEBCAM type: USB
  driver: snd-usb-audio,uvcvideo
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2)
  v: 4.6 Mesa 22.0.0

  I tried rebuilding the i965-va-driver, and it's still the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mesa-vdpau-drivers 22.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 27 10:37:41 2022
  DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed
   rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
  InstallationDate: Installed on 2021-10-05 (172 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  MachineType: ASUS System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 23.1
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: Default string
  dmi.board.name: Pro WS W480-ACE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2
  version.l

[Desktop-packages] [Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions

2022-04-01 Thread Tim Blokdijk
VBoxGuestAdditions_6.1.26.iso gives the same issue.

Removing the guest additions with `sudo ./VBoxLinuxAdditions.run
uninstall` fixes the double login.

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

Title:
  login screen shown twice with VirtualBox Guest Additions

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is shown twice and I have to supply the password
  twice. The system works normally afterwards.  When I select auto-login
  in the settings still one login screen is shown.

  gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
  Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
   Memory: 5.0M
  CPU: 125ms
   CGroup: /system.slice/gdm.service
   └─1915 /usr/sbin/gdm3

  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
  mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) 
by (uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate 
daemon control file
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password 
to try later in open session
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: 
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by 
(uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: 
gnome-keyring-daemon started properly and unlocked keyring
  mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was 
already dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 11:48:17 2022
  InstallationDate: Installed on 2020-01-25 (793 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+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 1966786] Re: login screen shown twice

2022-04-01 Thread Tim Blokdijk
It's the VirtualBox Guest Additions that triggers this bug.
With the latest VBoxGuestAdditions_6.1.32.iso and before.


It's not the `sudo apt install build-essential dkms` that need to be run to 
install the Guest Additions.

** Summary changed:

- login screen shown twice
+ login screen shown twice with VirtualBox Guest Additions

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

Title:
  login screen shown twice with VirtualBox Guest Additions

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is shown twice and I have to supply the password
  twice. The system works normally afterwards.  When I select auto-login
  in the settings still one login screen is shown.

  gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
  Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
   Memory: 5.0M
  CPU: 125ms
   CGroup: /system.slice/gdm.service
   └─1915 /usr/sbin/gdm3

  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
  mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) 
by (uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate 
daemon control file
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password 
to try later in open session
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: 
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by 
(uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: 
gnome-keyring-daemon started properly and unlocked keyring
  mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was 
already dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 11:48:17 2022
  InstallationDate: Installed on 2020-01-25 (793 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+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 1841826] Re: Going to sleep instead of logging in while lid closed & external display

2022-03-30 Thread Tim Wetzel
Two points
-Have not been able to find a combination of logind parameters that avoids this 
issue.
-Have also found that this problem is not limited to HDMI connection. It has 
also now appeared on a T480 in UltraDock using DP++ connection to external 
display. Again, the external display is the primary (only) monitor in use: 
laptop is docked, lid down, and uses external wireless Lenovo keyboard and 
mouse. On power up, after entering Ubuntu password, the system suspends

Please fix this!!! This has been an issue ever since the Ubuntu 20.04
updates September 2020!!!

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

Title:
  Going to sleep instead of logging in while lid closed & external
  display

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:
  I have the above described problem, which seems to be very similar to
  bug #1716160

  - laptop is in docking station and 2 monitors are connected (HDMI,
  DVI)

  - If the lid is closed and I boot the laptop I can input my
  credentials in the login screen and after hitting ENTER the laptop
  goes to sleep

  - If I then press the power button of the docking station the laptop
  wakes up and goes straight to the ubuntu environment w/o any user
  identification

  The device is a Lenovo T420 with classic docking station. Ubuntu
  18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated
  Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior
  independent of the graphics used.

  I do not know what to do now since the latest state of bug #1716160 is
  "fix released" and so I guess it should be part of the ubuntu version
  I use?

  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 20:10:15 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-08-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+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 1966786] Re: login screen shown twice

2022-03-30 Thread Tim Blokdijk
When installed within VirtualBox with Guest Additions the first login prompt is 
sized 800x600 the second login prompt has dynamic screen resolution so is full 
screen.
With "auto-login" for the user enabled the first 800x600 login prompt is 
skipped.

So my guess is that the Guest Additions code is run after you get
through the first login prompt. Other code might also be run that allows
you to successfully login with a second try?

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

Title:
  login screen shown twice

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The login screen is shown twice and I have to supply the password
  twice. The system works normally afterwards.  When I select auto-login
  in the settings still one login screen is shown.

  gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static)
   Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago
  Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1915 (gdm3)
Tasks: 3 (limit: 2291)
   Memory: 5.0M
  CPU: 125ms
   CGroup: /system.slice/gdm.service
   └─1915 /usr/sbin/gdm3

  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager...
  mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager.
  mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) 
by (uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate 
daemon control file
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password 
to try later in open session
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: 
pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by 
(uid=0)
  mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: 
gnome-keyring-daemon started properly and unlocked keyring
  mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was 
already dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 11:48:17 2022
  InstallationDate: Installed on 2020-01-25 (793 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+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 1967025] Re: Double login screen

2022-03-29 Thread Tim Blokdijk
After installation I also added the VB Guest Additions.
`sudo ./VBoxLinuxAdditions.run`
and for that to work I had to run
`sudo apt install build-essential dkms`

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

Title:
  Double login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Installed 22.04 daily (march 29) in VirtualBox.
  Selected "auto login" with user creation.
  After installation and update was greeted with a login screen.
  Disabling the "auto login" for the user in Gnome settings gave me two 
different successive login screens.
  Re-enabling the "auto login" gave me one login screen, where non would be 
expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 02:22:26 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967025/+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 1967025] [NEW] Double login screen

2022-03-29 Thread Tim Blokdijk
Public bug reported:

Installed 22.04 daily (march 29) in VirtualBox.
Selected "auto login" with user creation.
After installation and update was greeted with a login screen.
Disabling the "auto login" for the user in Gnome settings gave me two different 
successive login screens.
Re-enabling the "auto login" gave me one login screen, where non would be 
expected.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 02:22:26 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-29 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Double login screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Installed 22.04 daily (march 29) in VirtualBox.
  Selected "auto login" with user creation.
  After installation and update was greeted with a login screen.
  Disabling the "auto login" for the user in Gnome settings gave me two 
different successive login screens.
  Re-enabling the "auto login" gave me one login screen, where non would be 
expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 02:22:26 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967025/+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 1966007] Re: Flood of Bluetooth Malicious advertisind data

2022-03-29 Thread Andras Tim
The `gnome-terminal` is not affected by the kernel's Bluetooth issue...

** Package changed: gnome-terminal (Ubuntu) => linux-signed (Ubuntu)

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

Title:
  Flood of Bluetooth Malicious advertisind data

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  This problem occurred with the  ugrade of the kernel to patch level
  105.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.2-1ubuntu1~20.04
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:48:22 2022
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2018-06-21 (1370 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANG=en_AU.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1966007/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

2022-03-26 Thread Tim Passingham
Latest Thunderbird (1.91.7), on 21.10, same problem.  mutter is only
40.5.  Is there any chance of a fix to a current version of ubuntu?

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

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Unknown
Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1841826] Re: Going to sleep instead of logging in while lid closed & external display

2022-03-07 Thread Tim Wetzel
Shadrin, I tried that... removed the # from the start of that line so it was 
set to ignore. It had no effect.
I notice that there is another parameter LidSwitchIgnoreInhibited. That is set 
to yes.
What is the function of that parameter, do you know?
Thanks...
AND I CONCUR: Please correct this bug...

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

Title:
  Going to sleep instead of logging in while lid closed & external
  display

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:
  I have the above described problem, which seems to be very similar to
  bug #1716160

  - laptop is in docking station and 2 monitors are connected (HDMI,
  DVI)

  - If the lid is closed and I boot the laptop I can input my
  credentials in the login screen and after hitting ENTER the laptop
  goes to sleep

  - If I then press the power button of the docking station the laptop
  wakes up and goes straight to the ubuntu environment w/o any user
  identification

  The device is a Lenovo T420 with classic docking station. Ubuntu
  18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated
  Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior
  independent of the graphics used.

  I do not know what to do now since the latest state of bug #1716160 is
  "fix released" and so I guess it should be part of the ubuntu version
  I use?

  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 20:10:15 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-08-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+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 1841826] Re: Going to sleep instead of logging in while lid closed & external display

2022-02-21 Thread Tim Wetzel
New wrinkle: over the weekend on startup (from full shutdown), in dock, lid 
down with HDMI monitor and external keyboard and mouse, got to the Ubuntu login 
and put in the password. Was waiting for this suspend bug to appear. Instead: 
got a Linux error as follows at the point where this bug typically exhibits:
>>
setparms 'Ubuntu"
recordfail
load_video
gfxmode $linus_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ] insmod lzopio; fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
   search --no-floppy --fs-uuid --set=root 7c8ac294-9840-4cea-81dd-e9507641f946
else
   search --no-floppy --fs-uuid --set=root 7c8ac294-9840-4cea-81dd-e9507641f946
fi
linux /boot/vmlinuz-5.13.0-30-generic 
root=UUID=7c8ac294-9840-4cea-81dd-e9507641f946 ro quiet splash $vt_handoff
initrd  /boot/initrd.img-5.13.0.30-generic
>>
I pressed ESC to discard edits and return to the GRUB menu. Then tried the same 
thing again. This time it took the password and then displayed this suspend bug 
as expected...
Once at the desktop, I got a message from Software Updater that there are 
pending updates including the following; not sure whether this is related to 
recent nVidia and kernel updates interacting with this bug???
   Daemon and tooling that enable snap packages
   NVIDIA X Server Settings
Note that this is on a Thinkpad T570 set up with dual boot. The most recent 
updates were:
   2/7/22: nVidia update from 470.86~20.04.2 to 470.103.1~20.04.1
   2/17/22: Kernel update from 5.13.0.28.31~20.04.15 to -.30.33~-.17
   and yesterday some (what appeared to be) minor updates.
The machine is running poorly, which is unusual. 
PLEASE! FIX THIS BUG; see post #5 above and prior bug report number 1897185 
where more details were reported.

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

Title:
  Going to sleep instead of logging in while lid closed & external
  display

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:
  I have the above described problem, which seems to be very similar to
  bug #1716160

  - laptop is in docking station and 2 monitors are connected (HDMI,
  DVI)

  - If the lid is closed and I boot the laptop I can input my
  credentials in the login screen and after hitting ENTER the laptop
  goes to sleep

  - If I then press the power button of the docking station the laptop
  wakes up and goes straight to the ubuntu environment w/o any user
  identification

  The device is a Lenovo T420 with classic docking station. Ubuntu
  18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated
  Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior
  independent of the graphics used.

  I do not know what to do now since the latest state of bug #1716160 is
  "fix released" and so I guess it should be part of the ubuntu version
  I use?

  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 20:10:15 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-08-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+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 1841826] Re: Going to sleep instead of logging in while lid closed & external display

2022-02-19 Thread Tim Wetzel
New wrinkle: today on startup (from full shutdown), in dock, lid down with HDMI 
monitor and external keyboard and mouse, got to the Ubuntu login and put in the 
password. Was waiting for this suspend bug to appear. Instead: got a Linux 
error as follows at the point where this bug typically exhibits:
>>
setparms 'Ubuntu"
recordfail
load_video
gfxmode $linus_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ] insmod lzopio; fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
   search --no-floppy --fs-uuid --set=root 7c8ac294-9840-4cea-81dd-e9507641f946
else
   search --no-floppy --fs-uuid --set=root 7c8ac294-9840-4cea-81dd-e9507641f946
fi
linux /boot/vmlinuz-5.13.0-30-generic 
root=UUID=7c8ac294-9840-4cea-81dd-e9507641f946 ro quiet splash $vt_handoff
initrd  /boot/initrd.img-5.13.0.30-generic
>>
I pressed ESC to discard edits and return to the GRUB menu. Then tried the same 
thing again. This time it took the password and then displayed this suspend bug 
as expected...
Once at the desktop, I got a message from Software Updater that there are 
pending updates including the following; not sure whether this is related to 
recent nVidia and kernel updates interacting with this bug???
   Daemon and tooling that enable snap packages
   NVIDIA X Server Settings
Note that this is on a Thinkpad T570 set up with dual boot. The most recent 
updates were:
   2/7/22: nVidia update from 470.86~20.04.2 to 470.103.1~20.04.1
   2/17/22: Kernel update from 5.13.0.28.31~20.04.15 to -.30.33~-.17
   and yesterday some (what appeared to be) minor updates.
The machine is running poorly, which is unusual. 
PLEASE! FIX THIS BUG; see post #5 above and prior bug report number 1897185 
where more details were reported.

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

Title:
  Going to sleep instead of logging in while lid closed & external
  display

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:
  I have the above described problem, which seems to be very similar to
  bug #1716160

  - laptop is in docking station and 2 monitors are connected (HDMI,
  DVI)

  - If the lid is closed and I boot the laptop I can input my
  credentials in the login screen and after hitting ENTER the laptop
  goes to sleep

  - If I then press the power button of the docking station the laptop
  wakes up and goes straight to the ubuntu environment w/o any user
  identification

  The device is a Lenovo T420 with classic docking station. Ubuntu
  18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated
  Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior
  independent of the graphics used.

  I do not know what to do now since the latest state of bug #1716160 is
  "fix released" and so I guess it should be part of the ubuntu version
  I use?

  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 20:10:15 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-08-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+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 1841826] Re: Going to sleep instead of logging in while lid closed & external display

2022-02-10 Thread Tim Wetzel
Yes, this is still a problem. Please see post #5 above and /bugs/1897185 where 
I posted earlier information. As noted by fchen, this started with Ubuntu 
updates and has been a problem ever since, though I started seeing it months 
ago.
PLEASE fix this.
Thanks.

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

Title:
  Going to sleep instead of logging in while lid closed & external
  display

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:
  I have the above described problem, which seems to be very similar to
  bug #1716160

  - laptop is in docking station and 2 monitors are connected (HDMI,
  DVI)

  - If the lid is closed and I boot the laptop I can input my
  credentials in the login screen and after hitting ENTER the laptop
  goes to sleep

  - If I then press the power button of the docking station the laptop
  wakes up and goes straight to the ubuntu environment w/o any user
  identification

  The device is a Lenovo T420 with classic docking station. Ubuntu
  18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated
  Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior
  independent of the graphics used.

  I do not know what to do now since the latest state of bug #1716160 is
  "fix released" and so I guess it should be part of the ubuntu version
  I use?

  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 20:10:15 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-08-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+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 1952107] Re: Google Contacts API Deprecated

2022-01-19 Thread Tim Richardson
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Fix Committed
Status in evolution-data-server source package in Focal:
  Fix Committed
Status in evolution source package in Impish:
  Fix Committed
Status in evolution-data-server source package in Impish:
  Fix Committed

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1952107] Re: Google Contacts API Deprecated

2022-01-19 Thread Tim Richardson
(... Ubuntu 21.10)

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Fix Committed
Status in evolution-data-server source package in Focal:
  Fix Committed
Status in evolution source package in Impish:
  Fix Committed
Status in evolution-data-server source package in Impish:
  Fix Committed

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

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


  1   2   3   4   5   6   7   8   9   10   >