[Desktop-packages] [Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process

2024-05-02 Thread Robert Fletcher
That command did create some users
Restarting gnome remote desktop now gives me

░░ Subject: A start job for unit gnome-remote-desktop.service has begun 
execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit gnome-remote-desktop.service has begun execution.
░░ 
░░ The job identifier is 52156.
May 02 14:27:47 localhost gnome-remote-de[36906]: Init TPM credentials failed 
because No TPM device found, using GKeyFile as fallback
May 02 14:27:47 localhost gnome-remote-de[36906]: Init file credentials failed: 
Error creating directory /var/lib/gnome-remote-desktop: Permission denied
May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: **
May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: 
ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: 
(priv->credentials)
May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: Bail out! 
ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: 
(priv->credentials)
May 02 14:27:47 localhost systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=dumped, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has 
exited.
░░ 
░░ The process' exit code is 'dumped' and its exit status is 6.


Running:  /usr/libexec/gnome-remote-desktop-daemon --system

** (gnome-remote-desktop-daemon:36919): WARNING **: 14:30:22.681: Init TPM 
credentials failed because No TPM device found, using GKeyFile as fallback
Failed to register: Unable to acquire bus name 'org.gnome.RemoteDesktop'

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

Title:
  gnome-remote-desktop.service: Failed to determine user credentials: No
  such process

Status in gnome-remote-desktop package in Ubuntu:
  Triaged
Status in gnome-remote-desktop package in Debian:
  Unknown

Bug description:
  On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop.

  The desktop does not show up though gdm3 is running.

  I see the following error messages which might indicate a dependency
  issue:

  pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 1.
  Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 2.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 3.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: 

[Desktop-packages] [Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process

2024-05-02 Thread Robert Fletcher
Nothing really reported from running the above command

/usr/libexec/gnome-remote-desktop-daemon --system

** (gnome-remote-desktop-daemon:36048): WARNING **: 11:01:25.879: Init
TPM credentials failed because No TPM device found, using GKeyFile as
fallback

But no ports are open

netstat -tnlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address State   
PID/Program name
tcp0  0 127.0.0.1:631   0.0.0.0:*   LISTEN  
29997/cupsd 
tcp0  0 127.0.0.54:53   0.0.0.0:*   LISTEN  
16105/systemd-resol 
tcp0  0 127.0.0.53:53   0.0.0.0:*   LISTEN  
16105/systemd-resol 
tcp6   0  0 ::1:631 :::*LISTEN  
29997/cupsd 
tcp6   0  0 :::22   :::*LISTEN  
1/systemd  

I restarted GDM3

ps -aux | grep gnome
gdm35757  0.0  0.6 233060  6144 tty1 Ssl+ 11:01   0:00 
/usr/libexec/gdm-wayland-session dbus-run-session -- gnome-session --autostart 
/usr/share/gdm/greeter/autostart
gdm35761  0.0  0.2   6500  2432 tty1 S+   11:01   0:00 
dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart
gdm35763  0.0  1.8 518252 18304 tty1 Sl+  11:01   0:00 
/usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart
gdm35772  1.0 22.0 3251940 217456 tty1   Sl+  11:01   0:01 
/usr/bin/gnome-shell
gdm35799  0.0  0.7 236060  7552 tty1 Sl+  11:01   0:00 
/usr/libexec/at-spi2-registryd --use-gnome-session
gdm35822  0.0  2.7 2590472 26852 tty1Sl+  11:01   0:00 /usr/bin/gjs 
-m /usr/share/gnome-shell/org.gnome.Shell.Notifications
gdm36027  0.0  2.7 2590464 26860 tty1Sl+  11:01   0:00 /usr/bin/gjs 
-m /usr/share/gnome-shell/org.gnome.ScreenSaver
root   36090  0.0  1.7 439656 16896 ttyS0Sl+  11:02   0:00 
/usr/libexec/gnome-remote-desktop-daemon --system

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

Title:
  gnome-remote-desktop.service: Failed to determine user credentials: No
  such process

Status in gnome-remote-desktop package in Ubuntu:
  Confirmed

Bug description:
  On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop.

  The desktop does not show up though gdm3 is running.

  I see the following error messages which might indicate a dependency
  issue:

  pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 1.
  Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 2.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 3.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, 

[Desktop-packages] [Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process

2024-05-01 Thread Robert Fletcher
Also seeing the same issue on a headless server (Linode) 24.04 Ubuntu server
Installed ubuntu-desktop 

cat /etc/os-release 
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo


journalctl -xeu gnome-remote-desktop.service
Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
░░ Subject: A start job for unit gnome-remote-desktop.service has begun 
execution
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit gnome-remote-desktop.service has begun execution.
░░ 
░░ The job identifier is 2929.
Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has 
exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 217.

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

Title:
  gnome-remote-desktop.service: Failed to determine user credentials: No
  such process

Status in gnome-remote-desktop package in Ubuntu:
  Confirmed

Bug description:
  On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop.

  The desktop does not show up though gdm3 is running.

  I see the following error messages which might indicate a dependency
  issue:

  pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 1.
  Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:35 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 2.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 3.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main 
process exited, code=exited, status=217/USER
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed 
with result 'exit-code'.
  Apr 24 12:29:36 unmatched systemd[1]: Failed to start 
gnome-remote-desktop.service - GNOME Remote Desktop.
  Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled 
restart job, restart counter is at 4.
  Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service - 
GNOME Remote Desktop...
  Apr 24 12:29:36 unmatched (p-daemon)[1756]: gnome-remote-desktop.service: 
Failed to determine user credentials: No such process
  Apr 24 12:29:36 

Re: [Desktop-packages] [Bug 2023322]

2024-02-26 Thread Robert Polak
Bug driver 470, Nvidia GTX 650

W dniu 26.02.2024 o 04:06, Craig pisze:
> (In reply to Michael Catanzaro from comment #62)
>> Hi Craig and Thomas (and Emil if you're still around): if you're still
>> encountering problems with NVIDIA graphics, please report new a bug and
>> leave a comment here linking to the new bug.
> My problem was on legacy nvidia driver, and newer versions wouldn't even 
> start.  But I now know a workaround (GSK_RENDERER=cairo) and don't expect 
> there will be a fix for my old driver anyway.
> https://gitlab.gnome.org/GNOME/gtk/-/issues/5858
>

** Attachment added: "Zrzut ekranu z 2024-02-26
 14-51-55.png"
   
https://bugs.launchpad.net/bugs/2023322/+attachment/5749476/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-51-55.png

** Attachment added: "Zrzut ekranu z 2024-02-26
 14-52-37.png"
   
https://bugs.launchpad.net/bugs/2023322/+attachment/5749477/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-52-37.png

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 

[Desktop-packages] [Bug 2049192] Re: Audio problem on zoom + kubuntu 23.10

2024-02-20 Thread robert marshall
I didn't see the problem in kubuntu 23.04 either. Bit of experimentation
last night and I see that the audio usually sorts itself out after you
move to another workspace and then return to the one running zoom.

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

Title:
  Audio problem on zoom + kubuntu 23.10

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am using kubuntu 23.10, and have sound issues with zoom. I have
  a Jabra Speak 510 running thorugh USB.
  When I first connect to a meeting, I hear nothing (but apparently my mic does
  work, so others can hear me). If I open audio settings, hit "Test" and then 
switch the profile
  from Analog Stereo Output  + Mono Input to Digital Stereo Output + Mono Input
  (or vice versa, it's the action of changing the profile that seems important),
  then the sound works. 
  At points during a zoom call (seems to be related to other windows/apps 
opening), 
  the sound dies and I have to switch profile again.
  I never had this issue with kubuntu 22.04 LTS. I have not noticed similar
  problems applications which only output audio, eg vlc or clementine.

  STEPS TO REPRODUCE
  1. Join a zoom meeting

  OBSERVED RESULT
  No sound output until switching audio profile

  EXPECTED RESULT
  Sound should work without having to switch profile

  SOFTWARE/OS VERSIONS
  KDE Plasma Version: 5.27.8
  KDE Frameworks Version: 5.110.0.0
  Qt Version: 5.15.10
  Kernel 6.5.0-14
  Zoom 5.16.10 (668).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Jan 12 09:40:10 2024
  InstallationDate: Installed on 2023-11-10 (63 days ago)
  InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2021
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.18
  dmi.board.name: 0T2HR0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.18:bd09/06/2021:br1.1:svnDellInc.:pnXPS8930:pvr1.1.18:rvnDellInc.:rn0T2HR0:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.18
  dmi.sys.vendor: Dell Inc.

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


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


[Desktop-packages] [Bug 2037907] Re: No package 'nss' found

2024-01-23 Thread Robert
I tested version 23.12.0: same problem.
Thanks in advance for analyzing the problem.

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

Title:
  No package 'nss' found

Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Have installed poppler on several systems, but experience issues in
  some cases.

  All the dependencies should be installed!

  Distro: Debian Bullseye 11

  
  # apt-get install libopenjp2-7-dev libfreetype6-dev libfontconfig1-dev 
libjpeg-dev libtiff5-dev
  # cd /var/bin && wget https://poppler.freedesktop.org/poppler-23.09.0.tar.xz 
&& tar -xvf poppler-23.09.0.tar.xz
  # cd poppler-23.09.0 && mkdir build && cd build
  # cmake ..

  
  CMake Warning at CMakeLists.txt:95 (message):

  
 No test data found in $testdatadir.
 You will not be able to run 'make test' successfully.


 The test data is not included in the source packages
 and is also not part of the main git repository. Instead,
 you can checkout the test data from its own git
 repository with:


   git clone git://git.freedesktop.org/git/poppler/test


 You should checkout the test data as a sibling of your
 poppler source folder or specify the location of your
 checkout with -DTESTDATADIR=/path/to/checkoutdir/test.


  -- Checking for module 'nss>=3.49'
  --   No package 'nss' found
  -- Could NOT find NSS3 (missing: NSS3_LIBRARIES NSS3_CFLAGS)
  CMake Warning at cmake/modules/MacroOptionalFindPackage.cmake:32 
(find_package):
By not providing "FindGpgmepp.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Gpgmepp", but
CMake did not find one.

Could not find a package configuration file provided by "Gpgmepp"
(requested version 1.19) with any of the following names:

  GpgmeppConfig.cmake
  gpgmepp-config.cmake

Add the installation prefix of "Gpgmepp" to CMAKE_PREFIX_PATH or set
"Gpgmepp_DIR" to a directory containing one of the above files.  If
"Gpgmepp" provides a separate development package or SDK, be sure it has
been installed.
  Call Stack (most recent call first):
CMakeLists.txt:158 (macro_optional_find_package)

  
  CMake Warning at CMakeLists.txt:198 (find_package):
By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Core", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Core"
(requested version 5.12) with any of the following names:

  Qt5CoreConfig.cmake
  qt5core-config.cmake

Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
"Qt5Core_DIR" to a directory containing one of the above files.  If
"Qt5Core" provides a separate development package or SDK, be sure it has
been installed.

  
  CMake Warning at CMakeLists.txt:199 (find_package):
By not providing "FindQt5Gui.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Gui", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Gui" with any
of the following names:

  Qt5GuiConfig.cmake
  qt5gui-config.cmake

Add the installation prefix of "Qt5Gui" to CMAKE_PREFIX_PATH or set
"Qt5Gui_DIR" to a directory containing one of the above files.  If "Qt5Gui"
provides a separate development package or SDK, be sure it has been
installed.

  
  CMake Warning at CMakeLists.txt:200 (find_package):
By not providing "FindQt5Xml.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Xml", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Xml" with any
of the following names:

  Qt5XmlConfig.cmake
  qt5xml-config.cmake

Add the installation prefix of "Qt5Xml" to CMAKE_PREFIX_PATH or set
"Qt5Xml_DIR" to a directory containing one of the above files.  If "Qt5Xml"
provides a separate development package or SDK, be sure it has been
installed.

  
  CMake Warning at CMakeLists.txt:201 (find_package):
By not providing "FindQt5Widgets.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"Qt5Widgets", but CMake did not find one.

Could not find a package configuration file provided by "Qt5Widgets" with
any of the following names:

  Qt5WidgetsConfig.cmake
  qt5widgets-config.cmake

Add the installation prefix of "Qt5Widgets" to CMAKE_PREFIX_PATH or set
"Qt5Widgets_DIR" to a directory containing one of the above files.  If
"Qt5Widgets" provides a separate development package or SDK, be sure it has
been installed.

  
  CMake Warning at CMakeLists.txt:202 

[Desktop-packages] [Bug 2037907] Re: No package 'nss' found

2024-01-22 Thread Robert
same problem when trying to compile version 24.01.0.

 No package 'nss' found
 Could NOT find NSS3 (missing: NSS3_LIBRARIES NSS3_CFLAGS) (Required is at 
least version "3.68")

But

sudo apt-get install libnss3
-> libnss3 is already the newest version (2:3.68.2-0ubuntu1.2).

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

Title:
  No package 'nss' found

Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Have installed poppler on several systems, but experience issues in
  some cases.

  All the dependencies should be installed!

  Distro: Debian Bullseye 11

  
  # apt-get install libopenjp2-7-dev libfreetype6-dev libfontconfig1-dev 
libjpeg-dev libtiff5-dev
  # cd /var/bin && wget https://poppler.freedesktop.org/poppler-23.09.0.tar.xz 
&& tar -xvf poppler-23.09.0.tar.xz
  # cd poppler-23.09.0 && mkdir build && cd build
  # cmake ..

  
  CMake Warning at CMakeLists.txt:95 (message):

  
 No test data found in $testdatadir.
 You will not be able to run 'make test' successfully.


 The test data is not included in the source packages
 and is also not part of the main git repository. Instead,
 you can checkout the test data from its own git
 repository with:


   git clone git://git.freedesktop.org/git/poppler/test


 You should checkout the test data as a sibling of your
 poppler source folder or specify the location of your
 checkout with -DTESTDATADIR=/path/to/checkoutdir/test.


  -- Checking for module 'nss>=3.49'
  --   No package 'nss' found
  -- Could NOT find NSS3 (missing: NSS3_LIBRARIES NSS3_CFLAGS)
  CMake Warning at cmake/modules/MacroOptionalFindPackage.cmake:32 
(find_package):
By not providing "FindGpgmepp.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Gpgmepp", but
CMake did not find one.

Could not find a package configuration file provided by "Gpgmepp"
(requested version 1.19) with any of the following names:

  GpgmeppConfig.cmake
  gpgmepp-config.cmake

Add the installation prefix of "Gpgmepp" to CMAKE_PREFIX_PATH or set
"Gpgmepp_DIR" to a directory containing one of the above files.  If
"Gpgmepp" provides a separate development package or SDK, be sure it has
been installed.
  Call Stack (most recent call first):
CMakeLists.txt:158 (macro_optional_find_package)

  
  CMake Warning at CMakeLists.txt:198 (find_package):
By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Core", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Core"
(requested version 5.12) with any of the following names:

  Qt5CoreConfig.cmake
  qt5core-config.cmake

Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
"Qt5Core_DIR" to a directory containing one of the above files.  If
"Qt5Core" provides a separate development package or SDK, be sure it has
been installed.

  
  CMake Warning at CMakeLists.txt:199 (find_package):
By not providing "FindQt5Gui.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Gui", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Gui" with any
of the following names:

  Qt5GuiConfig.cmake
  qt5gui-config.cmake

Add the installation prefix of "Qt5Gui" to CMAKE_PREFIX_PATH or set
"Qt5Gui_DIR" to a directory containing one of the above files.  If "Qt5Gui"
provides a separate development package or SDK, be sure it has been
installed.

  
  CMake Warning at CMakeLists.txt:200 (find_package):
By not providing "FindQt5Xml.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Xml", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Xml" with any
of the following names:

  Qt5XmlConfig.cmake
  qt5xml-config.cmake

Add the installation prefix of "Qt5Xml" to CMAKE_PREFIX_PATH or set
"Qt5Xml_DIR" to a directory containing one of the above files.  If "Qt5Xml"
provides a separate development package or SDK, be sure it has been
installed.

  
  CMake Warning at CMakeLists.txt:201 (find_package):
By not providing "FindQt5Widgets.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"Qt5Widgets", but CMake did not find one.

Could not find a package configuration file provided by "Qt5Widgets" with
any of the following names:

  Qt5WidgetsConfig.cmake
  qt5widgets-config.cmake

Add the installation prefix of "Qt5Widgets" to CMAKE_PREFIX_PATH or set
"Qt5Widgets_DIR" to a directory 

[Desktop-packages] [Bug 2045177] [NEW] XWayland Native Game starts with blank region at top

2023-11-29 Thread Robert Leland
Public bug reported:

This happens for Civilization V which runs natively on Linux (No
proton). This did not happen on 22.04 or 22.10. The game runs full
screen. The blank region is horizontal about the size of a menu bar and
when this happens the mouse input regions is off so that you have to
click well below where the rendered button is.


For screenshot see : https://i.stack.imgur.com/ARmwb.jpg

WORK AROUND
Pressing ALT+TAB repeatedly will eventually fix the problem and the application 
behaves correctly afterwards. This problem happens about 95% of the time. 
Sometimes the blank regions is several menu bars  thick and occasionally a 
vertical bar also appears also.

This happens during the initial start of the game during the intro video
and continues on to the game itself.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xwayland 2:23.2.0-1ubuntu0.1
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 29 14:43:10 2023
InstallationDate: Installed on 2022-01-17 (682 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: xwayland
UpgradeStatus: Upgraded to mantic on 2023-10-29 (31 days ago)

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


** Tags: amd64 apport-bug mantic

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/2045177/+attachment/5724821/+files/Screenshot%20from%202023-11-29%2015-06-55.jpg

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

Title:
  XWayland Native Game starts with blank region at top

Status in xwayland package in Ubuntu:
  New

Bug description:
  This happens for Civilization V which runs natively on Linux (No
  proton). This did not happen on 22.04 or 22.10. The game runs full
  screen. The blank region is horizontal about the size of a menu bar
  and when this happens the mouse input regions is off so that you have
  to click well below where the rendered button is.

  
  For screenshot see : https://i.stack.imgur.com/ARmwb.jpg

  WORK AROUND
  Pressing ALT+TAB repeatedly will eventually fix the problem and the 
application behaves correctly afterwards. This problem happens about 95% of the 
time. Sometimes the blank regions is several menu bars  thick and occasionally 
a vertical bar also appears also.

  This happens during the initial start of the game during the intro
  video and continues on to the game itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xwayland 2:23.2.0-1ubuntu0.1
  ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
  Uname: Linux 6.5.0-13-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 29 14:43:10 2023
  InstallationDate: Installed on 2022-01-17 (682 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: xwayland
  UpgradeStatus: Upgraded to mantic on 2023-10-29 (31 days ago)

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


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


[Desktop-packages] [Bug 1912911] Re: When printing with my Brother hl-2170w printer I keep getting an invalid page range error on a blank page, after the desired pages are printed

2023-11-16 Thread Robert Liu
I also observed this issue on my laptop with 20.04.

I created a patched version in this PPA[1] and it seems the issue is resolved 
with the patch mentioned in comment #5.
If anyone can confirm the patched version does help, I'll submit the patch for 
SRU.

[1] https://launchpad.net/~robertliu/+archive/ubuntu/lp-1912911

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

Title:
  When printing with my Brother hl-2170w printer I keep getting an
  invalid page range error on a blank page, after the desired pages are
  printed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I run uname -a, this is basically what I get:
  "5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux"

  apt-cache policy cups gives me the following:

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
===

  4 and 5 are being answered together...

  Before the upgrade, I was able to print one or more pages, and not see the 
extra error page.
  This is the desired behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 23 13:15:24 2021
  InstallationDate: Installed on 2020-12-21 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for SCRIBE: 
dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/
  MachineType: Dell Inc. Inspiron 7773
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/SCRIBE.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/SCRIBE.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=9899e123-f378-4328-a399-78cd6361f58e ro quiet splash 
resume=UUID=46e80ad1-16de-4fdf-b1f7-96f4f58b1c57
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0R58C3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd09/14/2017:br1.2:svnDellInc.:pnInspiron7773:pvr:rvnDellInc.:rn0R58C3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7773
  dmi.product.sku: 0809
  dmi.sys.vendor: Dell Inc.

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


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


[Desktop-packages] [Bug 2041730] [NEW] Error sleep mode

2023-10-28 Thread Robert Polak
Public bug reported:

With the Nvidia 470 driver, sleep mode turns on but wakes up without an image
Sleep mode does not work with the Nvidia 390 and Nouveau drivers.
Many users on forums have been reporting this provlrm for a long time.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.4-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 20:29:39 2023
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2023-10-18 (10 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
SourcePackage: gjs
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gjs (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 gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2041730

Title:
  Error sleep mode

Status in gjs package in Ubuntu:
  New

Bug description:
  With the Nvidia 470 driver, sleep mode turns on but wakes up without an image
  Sleep mode does not work with the Nvidia 390 and Nouveau drivers.
  Many users on forums have been reporting this provlrm for a long time.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 20:29:39 2023
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2023-10-18 (10 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: gjs
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1901586] Re: [snap] CA Certificates from /usr/local/share/ca-certificates are not used

2023-10-02 Thread Robert Sander
Hi Merlijn,

this is what is literally written by me in the first line of the bug
report.

The bug report is not relevant for me any more as I migrated to a Debian
Desktop this year.

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

Title:
  [snap] CA Certificates from /usr/local/share/ca-certificates are not
  used

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  We have a company internal CA and placed its root CA certificate in
  /usr/local/share/ca-certificates and ran update-ca-certificates. This
  always worked for chromium based browsers.

  With chromium-browser as snap in Ubuntu 20.04 this seems to not work
  any more. Chromium reports invalid certificates as it cannot validate
  the chain any more.

  PLease make the snap version of Chromium use the certificates from the
  system (out of /etc/ssl/certs etc).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Oct 26 18:51:29 2020
  InstallationDate: Installed on 2020-09-26 (30 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1970884]

2023-09-09 Thread Robert Mader
IIUC there are now several runners using Ubuntu 22.04, notably for bug
1813588, so I guess this can be closed and most dependent bugs can
depend on that bug instead?

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

Title:
  Firefox snap does not use wayland backend by default

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Previous versions of Firefox worked with the wayland backend, with the
  latest version ( 99.0.1 ) wayland is not available and it has to use
  xwayland. This breaks the screen sharing and also the fonts are not as
  sharp as using the wayland backend.

  Nightly version 101.0a1 without snap works fine.

  ```
  Gtk-Message: 09:20:51.884: Failed to load module "canberra-gtk-module"
  Gtk-Message: 09:20:51.885: Failed to load module "canberra-gtk-module"
  [GFX1-]: glxtest: Could not connect to wayland socket
  ```

  Tested on Ubuntu 21.10 and 22.04 with the latest updates.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-06-21 (315 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Snap: firefox 99.0.1-1 (latest/stable/ubuntu-22.04)
  Snap.Changes: no changes found
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (4 days ago)
  UserGroups: docker sudo
  _MarkForUpload: True

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


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


[Desktop-packages] [Bug 2028886] [NEW] gnome-control-center wifi , crashes selecting wifi adapters for hidden networks

2023-07-27 Thread Robert Hubbard
Public bug reported:

Have two wifi adapters, PCI and USB. When selecting the 2nd adapter from
the  hidden networks options this causes a crash. I can use other tools
like nmtui and wifi works fine, so this is an issue with the parser of
this particular service?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 27 13:19:23 2023
InstallationDate: Installed on 2021-12-14 (590 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Attachment added: "scipt/log of events"
   
https://bugs.launchpad.net/bugs/2028886/+attachment/5688901/+files/gnome-control-center-wifi-crash

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

Title:
  gnome-control-center wifi , crashes selecting  wifi adapters for
  hidden networks

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

Bug description:
  Have two wifi adapters, PCI and USB. When selecting the 2nd adapter
  from the  hidden networks options this causes a crash. I can use other
  tools like nmtui and wifi works fine, so this is an issue with the
  parser of this particular service?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 27 13:19:23 2023
  InstallationDate: Installed on 2021-12-14 (590 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1992688] Re: firefox deb not installed

2023-07-06 Thread Robert C Jennings
FYI, if a user has a 22.04 install where they have explicitly removed
snapd/firefox this will add them back.  Not sure if this was a
consideration in the fix/testing.

Also, the apt resolver is pulling in snapd while holding ubuntu-desktop
back during staging which made finding the cause of the snapd/firefox
installation a bit hard to track down since no packages upgraded in the
same unattended-upgrades operation had dependencies on them.

(thread: https://hachyderm.io/@rcj4747/110667685702206834)

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

Title:
  firefox deb not installed

Status in firefox package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  Invalid
Status in ubuntu-meta source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Applications which use x-www-browser to launch a browser will not work on a 
freshly installed Ubuntu 22.04 system as the firefox deb (which provides 
x-www-browser) is not installed.

  Test Plan
  -
  1) Install Ubuntu 22.04.2 using an amd64 desktop iso image
  2) Open a terminal
  3) Run x-www-browser www.ubuntu.com
  4) Observe a command not found message which recommends installing firefox

  Installing of a daily build of Ubuntu 22.04 with -proposed enabled and
  ubuntu-desktop version 1.481.1 will not exhibit the above problem.

  Where problems could occur
  --

  Other Info
  --
  I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was 
not removed during the upgrade process so upgrades are a non-issue.

  Original Description
  
  Bug 1964036 leads me to believe that the firefox deb provides some important 
functionality (the firefox favourite icon in the gnome shell dock) but there is 
nothing that would require the deb to be installed (it is not seeded nor has an 
rdep) and the package description indicates that it can be safely removed. Is 
there some important functionality that it provides?

  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 11:30:46 2022
  InstallationDate: Installed on 2022-04-27 (167 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago)
  VarLogDistupgradeTermlog:

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


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


[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update

2023-07-03 Thread Olivier Robert
** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Unrequested kernel update

Status in linux-signed-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was
  informed that new packages are available and I just hit update. This
  caused my system running 5.15.0-76-generic to be switched to
  5.19.0-1010-nvidia-lowlatency.

  I noted this as I was now running into bugs like
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/2017980

  The update was, as stated in history.log:

  Start-Date: 2023-07-01  00:25:40
  Commandline: packagekit role='update-packages'
  Requested-By: cm (1000)
  Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, 
automatic)
  Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), 
modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2)

  => This simple update was changing my kernel from 5.15 to 5.19 without
  a request from my side

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10
  ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17
  Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul  1 21:16:09 2023
  InstallationDate: Installed on 2018-10-10 (1724 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+subscriptions


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


[Desktop-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

2023-07-03 Thread Olivier Robert
** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

Status in linux-meta-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I 
experience that google-chrome crashes.
  It shows

  ```shell
  [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap (core dumped)".
  ```

  To be honest I don't think it has anything to do with google-chrome at all.
  When google-chrome starts it (normally) request the system key-manager 
(KWallet in my case) for access to the users keys before it actually shows 
anything from chrome. Not even that part (the KWallet password box) shows up.

  I can only reproduce this problem with this specific kernel. It should
  be possible to take google-chrome out of the equation by using another
  application that starts by request the desktop key manager for access.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-nvidia-5.19 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92
  Uname: Linux 5.15.0-1023-nvidia x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Apr 28 11:23:23 2023
  InstallationDate: Installed on 2016-01-08 (2666 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: linux-meta-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions


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


[Desktop-packages] [Bug 2025537] Re: chrome Check failed

2023-07-02 Thread Olivier Robert
@slboss222 OK, so this is a confirmed kernel stack change.

While this is likely a bug, it’s probably not a Chromium bug, but rater
related to the ubuntu-drivers-common package. Can you post the output of
“LC_ALL=C apt list --installed 'linux-*'” (without the “”) ?

This will help confirm the origin of the bug, as well as determine the
steps to solve the problem.

The possible cause is the Ubuntu third-party driver logic choosing an
Nvidia driver for another kernel stack, which then triggers installation
of those kernels, to satisfy dependencies.

The solution would be to uninstall those non-generic kernels and
associated drivers (provided there’s at least one generic kernel
installed) and then rebooting.

It’s also possible that the Nvidia driver version is too old, and that
may be what triggered the bug. Running “ubuntu-drivers install” should
bring it up to date.

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

Title:
  chrome Check failed

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  local_slava@worksystem:~$ google-chrome
  [19394:19394:0701/201749.072306:FATAL:credentials.cc(127)] Check failed: . : 
Отказано в доступе (13)
  Trace/breakpoint trap (core dumped)

  How fix this? After update ubuntu...

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


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


[Desktop-packages] [Bug 2025537] Re: chrome Check failed

2023-07-01 Thread Olivier Robert
Were you using the generic kernel stack ? If yes, check your kernel
release number (uname -r) to confirm it’s still the generic kernel
(should end with “-generic”).

If your kernel stack suddenly changed, you’re not alone. People have
reported the updates going fancy and installing unwanted kernel stacks.
I hope this won’t get unnoticed by Canonical for too long, as it could
have severe availability consequences for some people.

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

Title:
  chrome Check failed

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  local_slava@worksystem:~$ google-chrome
  [19394:19394:0701/201749.072306:FATAL:credentials.cc(127)] Check failed: . : 
Отказано в доступе (13)
  Trace/breakpoint trap (core dumped)

  How fix this? After update ubuntu...

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


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


[Desktop-packages] [Bug 2025335] [NEW] PCI/internal sound card not detected after upgrade to 22.04

2023-06-29 Thread Robert
Public bug reported:

There is either "dummy" output or it claims the headphones are plugged
in and it is unable to output to the speakers, randomly when rebooting
or walking up from suspend.  Usually there is no sound, but maybe once
in several tries it works.

The sound worked fine in the previous LTS version.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
Uname: Linux 5.15.0-76-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:rr 7999 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Thu Jun 29 09:09:03 2023
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to jammy on 2023-04-29 (60 days ago)
dmi.bios.date: 01/03/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET72W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.22
dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET72W(1.47):bd01/03/2023:br1.47:efr1.22:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2022-04-20T08:54:35.429193

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2025335

Title:
  PCI/internal sound card not detected after upgrade to 22.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is either "dummy" output or it claims the headphones are plugged
  in and it is unable to output to the speakers, randomly when rebooting
  or walking up from suspend.  Usually there is no sound, but maybe once
  in several tries it works.

  The sound worked fine in the previous LTS version.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:rr 7999 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Thu Jun 29 09:09:03 2023
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to jammy on 2023-04-29 (60 days ago)
  dmi.bios.date: 01/03/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET72W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 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.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET72W(1.47):bd01/03/2023:br1.47:efr1.22:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5CTO1WW
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-04-20T08:54:35.429193

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2025335/+subscriptions


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


[Desktop-packages] [Bug 1743029] Re: glib-pacrunner assert failure: *** Error in `/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 0x00007f01e80177d0 ***

2023-06-22 Thread Robert
Frequent error message for years.

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

Title:
  glib-pacrunner assert failure: *** Error in `/usr/lib/glib-
  networking/glib-pacrunner': double free or corruption (!prev):
  0x7f01e80177d0 ***

Status in glib-networking package in Ubuntu:
  Confirmed

Bug description:
  please solve this bug

  
  errors.u.c: 
https://errors.ubuntu.com/problem/852d2ea7be7d213614748a158517c62679fd6883

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: glib-networking-services 2.54.1-2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/glib-networking/glib-pacrunner': 
double free or corruption (!prev): 0x7f01e80177d0 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 13 00:54:46 2018
  ExecutablePath: /usr/lib/glib-networking/glib-pacrunner
  InstallationDate: Installed on 2017-12-29 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/glib-networking/glib-pacrunner
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: glib-networking
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f01fb3974e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f01fb397820 "double free or 
corruption (!prev)", ptr=, ar_ptr=) at 
malloc.c:5425
   _int_free (av=0x7f01e820, p=, have_lock=0) at 
malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   ?? () from /usr/lib/x86_64-linux-gnu/libproxy.so.1
  Title: glib-pacrunner assert failure: *** Error in 
`/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 
0x7f01e80177d0 ***
  UpgradeStatus: Upgraded to bionic on 2018-01-03 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1743029/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-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

2023-06-18 Thread Robert
I am affected by this bug for a Xerox B230, I'd the printer is shut off
and restart. Deleting the certificate fixes it.

-- 
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 1971242] Re: printing PDF appears always grey, no color

2023-06-02 Thread Robert
Should be this change: Fixed default color settings for CMYK printers as
well (Issue #500)

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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


[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

2023-05-24 Thread Robert Phair
I have noted since 2 postings ago that the 44.1 package in lunar-
proposed *does not* fix the mouse cursor problem 100% (I've seen it
still happens since, though maybe less often).

However I would leave my posted tag of verification-done-lunar because
it's a 100% fix for the "single click on title bar" problem as
originally posted.

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

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

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
  --
  Single clicking the title bar of windows without a complex title bar (namely 
a title bar with additional buttons besides the close/maximinze/minimize) does 
not transfer focus to them.

  Test Case
  -
  1. Open gnome-terminal.
  2. Run xedit.
  3. Focus gnome-terminal.
  4. Click Xedit's title bar.

  Expected: Xedit has focus.
  Observed: gnome-terminal retains focus.
  .
  5. Focus Xedit.
  6. Click gnome-terminal's title bar.

  Expected and observed: Xedit relinquishes focus and gnome-terminal
  gets focus.

  Other Info
  --
  I can reproduce this in my main, up to date Lunar system in Xorg and also in 
a virtual machine with the 2023-03-24 09:02 iso 
(https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso).

  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-2ubuntu2
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 29 11:53:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-16 (316 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago)

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


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


[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

2023-05-24 Thread Robert Phair
> I did not receive an update for gnome-shell or gnome-shell-common, as
rphair did. Not sure why.

I added lunar-proposed and disabled updates from it by default, as
described in the Ubuntu wiki, and then ran "aptitude" and selected the
available updates in the "gnome" category.  There were 4 of these
available and selecting gnome-shell selects them all, plus some other
dependencies outside that category, all with version 44.1.

> putting verification-failed would prevent it from landing for all
users

I agree with this comment and would think from other comments above that
we're in a 7-day trial period to see if no testing failures reported.  I
don't use the "snap" packages but I can say it will help a lot of people
if the functionality of the non-snap packages is made generally
available.

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

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

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
  --
  Single clicking the title bar of windows without a complex title bar (namely 
a title bar with additional buttons besides the close/maximinze/minimize) does 
not transfer focus to them.

  Test Case
  -
  1. Open gnome-terminal.
  2. Run xedit.
  3. Focus gnome-terminal.
  4. Click Xedit's title bar.

  Expected: Xedit has focus.
  Observed: gnome-terminal retains focus.
  .
  5. Focus Xedit.
  6. Click gnome-terminal's title bar.

  Expected and observed: Xedit relinquishes focus and gnome-terminal
  gets focus.

  Other Info
  --
  I can reproduce this in my main, up to date Lunar system in Xorg and also in 
a virtual machine with the 2023-03-24 09:02 iso 
(https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso).

  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-2ubuntu2
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 29 11:53:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-16 (316 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago)

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


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


[Desktop-packages] [Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

2023-05-24 Thread Robert Phair
I installed version 44.1 from `lunar-proposed` (plus all dependencies):

gnome-shell/lunar-proposed,now 44.1-0ubuntu1 amd64 [installed]
gnome-shell-common/lunar-proposed,lunar-proposed,now 44.1-0ubuntu1 all 
[installed,automatic]

and I can confirm that click-to-raise for the GNOME default titlebars is
working again, and the resize mouse cursor doesn't erroneously display
inside windows anymore.

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

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

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

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
  --
  Single clicking the title bar of windows without a complex title bar (namely 
a title bar with additional buttons besides the close/maximinze/minimize) does 
not transfer focus to them.

  Test Case
  -
  1. Open gnome-terminal.
  2. Run xedit.
  3. Focus gnome-terminal.
  4. Click Xedit's title bar.

  Expected: Xedit has focus.
  Observed: gnome-terminal retains focus.
  .
  5. Focus Xedit.
  6. Click gnome-terminal's title bar.

  Expected and observed: Xedit relinquishes focus and gnome-terminal
  gets focus.

  Other Info
  --
  I can reproduce this in my main, up to date Lunar system in Xorg and also in 
a virtual machine with the 2023-03-24 09:02 iso 
(https://cdimage.ubuntu.com/daily-live/current/lunar-desktop-amd64.iso).

  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-2ubuntu2
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 29 11:53:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-05-16 (316 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to lunar on 2023-01-17 (70 days ago)

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


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


[Desktop-packages] [Bug 2019559] [NEW] PipeWire Buffer Underruns with Wine

2023-05-15 Thread Robert Dinse
Public bug reported:

This is similar to bug #1929237 but with a different source and since
this involves pulse-pipewire it may be related to that module.

I am SO FRUSTRATED with Ubuntu, seems every release just breaks more
stuff.  I HAD Pulse Audio working perfectly, no matter what source, no
matter how loaded, no stuttering, simply had to adjust some buffer sizes
up from the ridiculous defaults.

Now WinAmp under Wine sounds like shit, stutters horridly, and there
seems to be no decent documentation for the new disaster known as
Pipewire.  Didn't think anyone could possibly write code more buggy than
Poettering but someone had to come along and prove me wrong.

Can someone tell me where to adjust buffer sizes in pipewire to stop
this GawdAweful Stuttering?

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: pipewire 0.3.65-3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon May 15 02:11:39 2023
InstallationDate: Installed on 2023-05-14 (0 days ago)
InstallationMedia: Ubuntu-MATE 23.04 "Lunar Lobster" - Release amd64 (20230415)
SourcePackage: pipewire
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug lunar

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

Title:
  PipeWire Buffer Underruns with Wine

Status in pipewire package in Ubuntu:
  New

Bug description:
  This is similar to bug #1929237 but with a different source and since
  this involves pulse-pipewire it may be related to that module.

  I am SO FRUSTRATED with Ubuntu, seems every release just breaks more
  stuff.  I HAD Pulse Audio working perfectly, no matter what source, no
  matter how loaded, no stuttering, simply had to adjust some buffer
  sizes up from the ridiculous defaults.

  Now WinAmp under Wine sounds like shit, stutters horridly, and there
  seems to be no decent documentation for the new disaster known as
  Pipewire.  Didn't think anyone could possibly write code more buggy
  than Poettering but someone had to come along and prove me wrong.

  Can someone tell me where to adjust buffer sizes in pipewire to stop
  this GawdAweful Stuttering?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire 0.3.65-3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Mon May 15 02:11:39 2023
  InstallationDate: Installed on 2023-05-14 (0 days ago)
  InstallationMedia: Ubuntu-MATE 23.04 "Lunar Lobster" - Release amd64 
(20230415)
  SourcePackage: pipewire
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1972820]

2023-05-09 Thread Nv4y-robert
(In reply to AJ from comment #13)

You couldn't get it working, because the direct connection from LO is a
connection to MariaDB. So newer versions of MySQL might be not supported
with direct connection.

Again: JDBC connection will work. Have a look at Base Guide
https://books.libreoffice.org/en/BG73/BG7302-CreatingADatabase.html#toc9

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

Title:
  LibreOffice crash when entering data in MySQL database

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

Bug description:
  When I try to enter a new record in a MySQL table in LO Base, the new record 
is accepted but Base close suddenly when I close the table.
  MySQL database is connected by the direct connector (embedded).
  Same kind of problem with LO 6.4

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:29:06 2022
  InstallationDate: Installed on 2020-04-10 (759 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1972820/+subscriptions


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


[Desktop-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

2023-05-08 Thread Robert
It is not fixed with cups 2.4.1 
(https://github.com/OpenPrinting/cups/issues/421).
But should be fixed with cups 2.4.3 
(https://github.com/OpenPrinting/cups/pull/500).

Ubuntu 22.04 LTS has cups 2.4.1 (cups-config --version)

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  New
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

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


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


[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2023-04-27 Thread Robert Ancell
Correct, this fix is valuable for core22, so kinetic was skipped. There
should be no issues for anyone updating from jammy to kinetic. Though
this will affect core20, we expect most snaps to be using core22 so no
plan to backport it to focal.

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  Fix Released
Status in glib2.0 source package in Kinetic:
  Won't Fix
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


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


[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2023-04-27 Thread Robert Ancell
Yes, these specific steps performed in a core desktop VM.

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  Fix Committed
Status in glib2.0 source package in Kinetic:
  Won't Fix
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


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


[Desktop-packages] [Bug 2017734] [NEW] package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: triggers looping, abandoned

2023-04-26 Thread Robert Ressl
Public bug reported:

Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1
ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Apr 26 08:57:37 2023
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2023-01-24 (91 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: gdk-pixbuf
Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package lunar

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

Title:
  package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to
  install/upgrade: triggers looping, abandoned

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Apr 26 08:57:37 2023
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2023-01-24 (91 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/2017734/+subscriptions


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


[Desktop-packages] [Bug 2017735] [NEW] package rygel 0.42.1-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

2023-04-26 Thread Robert Ressl
Public bug reported:

Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: rygel 0.42.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Apr 26 08:57:37 2023
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2023-01-24 (91 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: rygel
Title: package rygel 0.42.1-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago)

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


** Tags: amd64 apport-package lunar

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

Title:
  package rygel 0.42.1-1ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in rygel package in Ubuntu:
  New

Bug description:
  Upgrade from Ubuntu 22.10 to 23.04 on iMac 5k 2014

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: rygel 0.42.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Apr 26 08:57:37 2023
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2023-01-24 (91 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: rygel
  Title: package rygel 0.42.1-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (0 days ago)

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


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


[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2023-04-19 Thread Robert Ancell
I tested a standard jammy desktop in a VM by running various apps
including calculator to confirm they were still working (i.e. looking
for regressions).

I tested the core desktop behaviour by building the core22-desktop snap
from https://github.com/canonical/core-base-desktop/ (locally modified
to use updates) and then installing that into a core desktop.

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  Fix Committed
Status in glib2.0 source package in Kinetic:
  Won't Fix
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


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


[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2023-04-17 Thread Robert Ancell
Tested glib2.0 2.72.4-0ubuntu2 in a jammy VM and working.

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

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  Fix Committed
Status in glib2.0 source package in Kinetic:
  Won't Fix
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


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


[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2023-04-17 Thread Robert Ancell
I've looked at the autopkgtests and the failures don't seem to be
related to this change.

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  Fix Committed
Status in glib2.0 source package in Kinetic:
  Won't Fix
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


-- 
Mailing list: https://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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-04-12 Thread Robert Pearson
You're welcome!

On Wed, Apr 12, 2023 at 7:47 AM Rishab raju <2007...@bugs.launchpad.net>
wrote:

> Robert Pearson,
> Man it worked after i did as you said.Thanks for the assist. Truely
> thankful.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2007913
>
> Title:
>   HDMI Output sound has disappeared after Ubuntu update
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After months using the HDMI output without problems, it has stopped
> working after a system update two days ago.
>   HDMI output is not listed in the list of available output devices.
>   Same computer works with this sound output perfectly when booting with
> Windows or an older installation of Ubuntu (18.04).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu7
>   ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
>   Uname: Linux 5.19.0-32-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.3
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Feb 21 08:12:58 2023
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2022-04-30 (296 days ago)
>   InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
> (20220419)
>   PackageArchitecture: all
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ca_ES.UTF-8
>SHELL=/bin/bash
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: USB sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/20/2021
>   dmi.bios.release: 5.13
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: M01EWR120
>   dmi.board.asset.tag: OEM Default string000
>   dmi.board.name: OEM Default string000
>   dmi.board.vendor: OEM Default string000
>   dmi.board.version: OEM Default string000
>   dmi.chassis.asset.tag: OEM Default string000
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: OEM Default string000
>   dmi.chassis.version: OEM Default string000
>   dmi.ec.firmware.release: 1.2
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
>   dmi.product.family: OEM Default string000
>   dmi.product.name: CoreBox
>   dmi.product.sku: OEM Default string000
>   dmi.product.version: OEM Default string000
>   dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
>   mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions
>
>

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000

[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-04-11 Thread Robert Pearson
Rishabraju,
Boot into your BIOS screen (DEL or F2). Select your drive. When the GRUB menu 
opens, select Advanced Features. You should then see a list of available 
kernels. Select 5.19.0-32-generic (the later kernels are broken. 
After you sign in, open the Audio setting, select HDMI hardware, and then test 
the speakers.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions


-- 
Mailing list: https://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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-04-07 Thread Robert Pearson
Interesting. That indicates that the code is "fragile", not robust. I'm
glad you finally got your systems to recognize the speakers. Do they work?
In my system, it recognized the HDMI audio output, it just does not work.
Testing the speakers gives the sound of silence. I'm back to
5.19.0-32-generic. That still works.

On Thu, Apr 6, 2023 at 9:10 PM Nukool Chompuparn <2007...@bugs.launchpad.net>
wrote:

> Now I'm on 5.19.0-38-generic. I had to restart my computers 5 to 6 times
> in a row to make Ubuntu 22.04 LTS detect the HDMI speakers on my
> external monitor, LG 29wk-600W.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2007913
>
> Title:
>   HDMI Output sound has disappeared after Ubuntu update
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After months using the HDMI output without problems, it has stopped
> working after a system update two days ago.
>   HDMI output is not listed in the list of available output devices.
>   Same computer works with this sound output perfectly when booting with
> Windows or an older installation of Ubuntu (18.04).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu7
>   ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
>   Uname: Linux 5.19.0-32-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.3
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Feb 21 08:12:58 2023
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2022-04-30 (296 days ago)
>   InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
> (20220419)
>   PackageArchitecture: all
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ca_ES.UTF-8
>SHELL=/bin/bash
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: USB sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/20/2021
>   dmi.bios.release: 5.13
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: M01EWR120
>   dmi.board.asset.tag: OEM Default string000
>   dmi.board.name: OEM Default string000
>   dmi.board.vendor: OEM Default string000
>   dmi.board.version: OEM Default string000
>   dmi.chassis.asset.tag: OEM Default string000
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: OEM Default string000
>   dmi.chassis.version: OEM Default string000
>   dmi.ec.firmware.release: 1.2
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
>   dmi.product.family: OEM Default string000
>   dmi.product.name: CoreBox
>   dmi.product.sku: OEM Default string000
>   dmi.product.version: OEM Default string000
>   dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
>   mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions
>
>

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default 

[Desktop-packages] [Bug 2012994] Re: Automatic Date & Time switch shows as insensitive when enabled

2023-03-28 Thread Robert Ancell
It's upstream https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/1749

-- 
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 1987976]

2023-03-28 Thread Robert Mader
Oh wow, I think I just managed to reproduce this on my Iris laptop - in
a fresh session with Xwayland on demand. That and comment 45 points to a
race condition in the FF code regarding switching between composited and
non-composited X11.

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

Title:
  firefox black window

Status in Mozilla Firefox:
  Confirmed
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987976]

2023-03-28 Thread Robert Mader
Since this was reported for a device running the Crocus Mesa driver in
situations where implicit drm modifiers are most likely used (Xwayland,
X11 compositor), there's certain chance that it will be fixed by
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21209

Michelet/Alan, any chance you could test that commit?

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

Title:
  firefox black window

Status in Mozilla Firefox:
  Confirmed
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen

2023-03-27 Thread Robert Ancell
** Tags added: rls-ll-incoming

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions


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


[Desktop-packages] [Bug 2012996] [NEW] Editing device name doesn't cancel when pressing escape

2023-03-27 Thread Robert Ancell
Public bug reported:

The device name in the Sharing or About panels can be changed by
clicking the icon to the right of the name (see screenshot). Pressing
escape doesn't cancel the edit and re-show this icon.

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


** Tags: rls-ll-incoming

** Attachment added: "Screenshot of device name widget"
   
https://bugs.launchpad.net/bugs/2012996/+attachment/5658049/+files/Screenshot%20from%202023-03-28%2014-46-06.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/2012996

Title:
  Editing device name doesn't cancel when pressing escape

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

Bug description:
  The device name in the Sharing or About panels can be changed by
  clicking the icon to the right of the name (see screenshot). Pressing
  escape doesn't cancel the edit and re-show this icon.

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


-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] Automatic Date & Time switch shows as insensitive when enabled

2023-03-27 Thread Robert Ancell
Public bug reported:

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.

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


** Tags: rls-ll-incoming

** Attachment added: "Screenshot showing automatic date & time enabled with 
insensitive switch"
   
https://bugs.launchpad.net/bugs/2012994/+attachment/5658048/+files/Screenshot%20from%202023-03-28%2014-41-08.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/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 2012991] Re: Insensitive items in system tray menus not visible

2023-03-27 Thread Robert Ancell
Changing the theme to dark makes the text visible.

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

Title:
  Insensitive items in system tray menus not visible

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  If you use the multicast system tray menu the text on the items that
  are insensitive aren't visible. It appears they have the same colour
  as the background.

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


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


[Desktop-packages] [Bug 2012991] [NEW] Insensitive items in system tray menus not visible

2023-03-27 Thread Robert Ancell
Public bug reported:

If you use the multicast system tray menu the text on the items that are
insensitive aren't visible. It appears they have the same colour as the
background.

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


** Tags: rls-ll-incoming

** Attachment added: "Screenshot of multipass system tray menu"
   
https://bugs.launchpad.net/bugs/2012991/+attachment/5658046/+files/Screenshot%20from%202023-03-28%2014-11-35.png

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

Title:
  Insensitive items in system tray menus not visible

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  If you use the multicast system tray menu the text on the items that
  are insensitive aren't visible. It appears they have the same colour
  as the background.

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


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


[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2023-03-22 Thread Robert Ancell
** Changed in: glib2.0 (Ubuntu Kinetic)
   Status: New => Won't Fix

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  New
Status in glib2.0 source package in Kinetic:
  Won't Fix
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


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


[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2023-03-22 Thread Robert Ancell
** Description changed:

  [ Impact]
  
  glib is not aware of snap confinement and this causes the internal logic
  to decide when to use portals to not work as designed. One important
  case is the gsettings backend, which should use a keyfile when confined
  rather than using dconf. When using a fully confined desktop this is
  required, as dconf is not suitable for sharing between snaps.
  
  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020
  
  [ Test Plan ]
+ 
+ (requires a core snap running the updated glib).
  
  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator
  
  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile
  
  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.
  
  [ Where problems could occur ]
  
  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  New
Status in glib2.0 source package in Kinetic:
  New
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


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


[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-13 Thread Robert Pearson
Will Ubuntu fix kernel 5.19.0-35 or just do another update with a
working kernel?

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions


-- 
Mailing list: https://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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-13 Thread Robert Pearson
Thank you so much!
I have two disk drives; one with 22.04 and one with 18.04.3. When the
update rendered 22.04 useless, I switched to 18.04.3. I got your
explanation on how to use different kernels. When 18.04.3 crashed, I tried
using a different kernel. In grub, I selected Advanced options and selected
the previous generic kernel linux-image-5.19.0-31-generic. That immediately
fixed the problem.
Apparently, the linux-image-5.19.0-35-generic has the bug.
Until they get around to fixing the defective 5.19.0-35 kernel, I will use
5.19.0-31 kernel.
Thank you so much, yet again.
This is the first time that I have gotten a work-around for defective code
since I started using Ubuntu MATE.
Robert Pearson

On Tue, Mar 7, 2023 at 4:20 PM William <2007...@bugs.launchpad.net>
wrote:

> You select your kernel in the grub boot menu. There is an option for
> alternative boot configurations. I have a dual boot environment set up
> so grub comes up every time for me. I think you hit esc to bring it up
> if it normally boots straight into windows. If you have any trouble it
> should come up in a search pretty quick.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2007913
>
> Title:
>   HDMI Output sound has disappeared after Ubuntu update
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After months using the HDMI output without problems, it has stopped
> working after a system update two days ago.
>   HDMI output is not listed in the list of available output devices.
>   Same computer works with this sound output perfectly when booting with
> Windows or an older installation of Ubuntu (18.04).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu7
>   ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
>   Uname: Linux 5.19.0-32-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.3
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Feb 21 08:12:58 2023
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2022-04-30 (296 days ago)
>   InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
> (20220419)
>   PackageArchitecture: all
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ca_ES.UTF-8
>SHELL=/bin/bash
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: USB sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/20/2021
>   dmi.bios.release: 5.13
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: M01EWR120
>   dmi.board.asset.tag: OEM Default string000
>   dmi.board.name: OEM Default string000
>   dmi.board.vendor: OEM Default string000
>   dmi.board.version: OEM Default string000
>   dmi.chassis.asset.tag: OEM Default string000
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: OEM Default string000
>   dmi.chassis.version: OEM Default string000
>   dmi.ec.firmware.release: 1.2
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
>   dmi.product.family: OEM Default string000
>   dmi.product.name: CoreBox
>   dmi.product.sku: OEM Default string000
>   dmi.product.version: OEM Default string000
>   dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
>   mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions
>
>

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesk

Re: [Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-07 Thread Robert Pearson
"Booting with linux-image-5.19.0-21-generic lists the audio
devices again."

So how do I do that?

On Tue, Mar 7, 2023 at 5:20 AM William <2007...@bugs.launchpad.net>
wrote:

> Booting with linux-image-5.19.0-35-generic appears to be the problem in
> 22.10. Booting with linux-image-5.19.0-21-generic lists the audio
> devices again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2007913
>
> Title:
>   HDMI Output sound has disappeared after Ubuntu update
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After months using the HDMI output without problems, it has stopped
> working after a system update two days ago.
>   HDMI output is not listed in the list of available output devices.
>   Same computer works with this sound output perfectly when booting with
> Windows or an older installation of Ubuntu (18.04).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu7
>   ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
>   Uname: Linux 5.19.0-32-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu82.3
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Feb 21 08:12:58 2023
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2022-04-30 (296 days ago)
>   InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
> (20220419)
>   PackageArchitecture: all
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ca_ES.UTF-8
>SHELL=/bin/bash
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: USB sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/20/2021
>   dmi.bios.release: 5.13
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: M01EWR120
>   dmi.board.asset.tag: OEM Default string000
>   dmi.board.name: OEM Default string000
>   dmi.board.vendor: OEM Default string000
>   dmi.board.version: OEM Default string000
>   dmi.chassis.asset.tag: OEM Default string000
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: OEM Default string000
>   dmi.chassis.version: OEM Default string000
>   dmi.ec.firmware.release: 1.2
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
>   dmi.product.family: OEM Default string000
>   dmi.product.name: CoreBox
>   dmi.product.sku: OEM Default string000
>   dmi.product.version: OEM Default string000
>   dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
>   mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions
>
>

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 

[Desktop-packages] [Bug 1970050] Re: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04

2023-03-04 Thread Robert Pearson
This leaves those of us with AMD processors out in the cold. Should I
roll back to Ubuntu MATE 18.04 for a working system until you fix your
update bug?

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

Title:
  [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
  because of upgrade from 20.04 LTS to 22.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After upgrading today from 20.04 LTS to 22.04
  HDMI Audio does not work at all.
  Audio from speakers from a headphone jack works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 23 21:13:23 2022
  InstallationDate: Installed on 2020-04-24 (729 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Built-in Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: Upgraded to jammy on 2022-04-23 (0 days ago)
  dmi.bios.date: 04/21/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH97M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H97M-HD3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970050/+subscriptions


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


[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-04 Thread Robert Pearson
When I run lspci it lists
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP 
Audio Controller.

The latest update to Ubuntu MATE 22.04 just ignores it.

In the control center/sound/output it only sees the IEC958 built-in
audio digital stereo.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions


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


[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-04 Thread Robert Pearson
My system is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Video and audio
output are via HDMI.

As soon as I installed the latest update to Ubuntu MATE 22.04 the audio
broke. When I went to the control center, the entry for HDMI audio
wasn't there.

Apparently, the coder assumed everybody was using the motherboard audio
and nobody uses HDMI or Display Port output.

Please restore the HDMI audio output.

This is a previously reported bug, just different hardware.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions


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


[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

2023-01-17 Thread Robert Liu
I installed the updated version on the platform which needs this patch.
After updating the packages, the platform can scan and connect to a WiFi
network correctly.

I also tried other amd64, armhf and arm64 platforms which don't require
the patch originally and their wifi device still work after upgrading.

$ dpkg -l |grep libnl
ii  libnl-3-200:armhf  3.4.0-1ubuntu0.1  armhf  
  library for dealing with netlink sockets
ii  libnl-genl-3-200:armhf 3.4.0-1ubuntu0.1  armhf  
  library for dealing with netlink sockets - generic netlink
ii  libnl-route-3-200:armhf3.4.0-1ubuntu0.1  armhf  
  library for dealing with netlink sockets - route interface

$ sudo netplan apply
$ ip a
  ...
3: wlan0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
link/ether dc:a6:32:37:fa:a7 brd ff:ff:ff:ff:ff:ff
inet 10.102.138.56/22 brd 10.102.139.255 scope global dynamic wlan0
   valid_lft 600sec preferred_lft 600sec
inet6 fe80::dea6:32ff:fe37:faa7/64 scope link 
   valid_lft forever preferred_lft forever

$ sudo ping -I wlan0 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 10.102.138.56 wlan0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=10.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=5.64 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=5.73 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=6.09 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=6.98 ms


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

** Changed in: oem-priority/focal
   Status: New => Fix Committed

** Changed in: oem-priority/focal
   Importance: Undecided => High

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project focal series:
  Fix Committed
Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Focal:
  Fix Committed
Status in libnl3 source package in Jammy:
  Invalid

Bug description:
  [ Impact ] 
  When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not 
able connect to an AP.

  However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly.

  After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is
  identified as the root cause.

  According to the commit, the "NLA_F_NESTED" flag should be set for
  kernel later than 5.2.

  [ Test Plan ]
  Verify with the updated version, the WIFI module can:
1. scan WIFI networks
2. connect to an available network
3. access to the connected network

  [ Where problems could occur ]
  1. kernel versions without NLA_F_NESTED flag defined
This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have 
it). It would not be a problem for an older kernel to understand/work with this 
change. Since the GA kernel is 5.4, so a generic image would still work.

  2. Drivers don't use the NESTED flag.
According to hui.wang's input, this change should not affect drivers which 
don't use the NESTED flag. But, it'd be better to cover more Wifi modules.

  [ Other Info ]
  22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998765/+subscriptions


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


[Desktop-packages] [Bug 2002212] [NEW] Outdated version of libglib2.0-dev in Ubuntu Jammy

2023-01-07 Thread Bajcsi Elias-Robert
Public bug reported:

The version of libglib2.0-dev that is currently included in the
repositories for Ubuntu is 2.72.1-1, which is outdated and missing
important features and bug fixes. In particular, the
G_APPLICATION_DEFAULT_FLAGS macro, which was added in GTK+ 3.22, is not
available in this version of libglib2.0-dev. This is causing issues with
my application, which requires the use of this macro.

I request that the package be updated to the latest version (currently
2.74) in order to resolve this issue.

Steps to reproduce:
  1. Install libglib2.0-dev version 2.72.1-1 on an Ubuntu system
  2. Attempt to compile an application that uses the 
G_APPLICATION_DEFAULT_FLAGS macro
  3. Observe the compilation error due to the missing macro

Expected result:
The application compiles successfully and can be run.

Actual result:
The application fails to compile due to the missing G_APPLICATION_DEFAULT_FLAGS 
macro.

Release:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

Using version:
2.72.1-1

Requested version:
2.74(+)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Outdated version of libglib2.0-dev in Ubuntu Jammy

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  The version of libglib2.0-dev that is currently included in the
  repositories for Ubuntu is 2.72.1-1, which is outdated and missing
  important features and bug fixes. In particular, the
  G_APPLICATION_DEFAULT_FLAGS macro, which was added in GTK+ 3.22, is
  not available in this version of libglib2.0-dev. This is causing
  issues with my application, which requires the use of this macro.

  I request that the package be updated to the latest version (currently
  2.74) in order to resolve this issue.

  Steps to reproduce:
1. Install libglib2.0-dev version 2.72.1-1 on an Ubuntu system
2. Attempt to compile an application that uses the 
G_APPLICATION_DEFAULT_FLAGS macro
3. Observe the compilation error due to the missing macro

  Expected result:
  The application compiles successfully and can be run.

  Actual result:
  The application fails to compile due to the missing 
G_APPLICATION_DEFAULT_FLAGS macro.

  Release:
Description:Ubuntu 22.04.1 LTS
Release:22.04

  Using version:
  2.72.1-1

  Requested version:
  2.74(+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2002212/+subscriptions


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


[Desktop-packages] [Bug 1970389] Re: [nvidia] Janky text entry and frames appear out of order in Xwayland apps

2022-12-20 Thread Robert Carroll
I'm experiencing this too.  No idea how to replicate it as it seems
pretty random.  Were you able to find a solution?

I find it happens on almost any "Chromium-based" application like
Discord and Brave Browser.

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

Title:
  [nvidia] Janky text entry and frames appear out of order in Xwayland
  apps

Status in X.Org X server:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in xwayland package in Ubuntu:
  Confirmed

Bug description:
  When writing into text fields in some applications (Firefox, VS Code)
  on Jammy in a GNOME / Wayland session, I can see an effect best
  described as the glyphs appearing / disappearing sometimes repeatedly.
  I have attached a recording from my phone (since attempting to record
  a screencast fails).

  This doesn't happen always, and it appear somehow sensitive to some
  environmental condition (load?) since for example when I'm on a video
  call, the effect seems to not be happening so often.

  I have also experienced a few instances of a currently not-focused
  window disappearing (seeing through to a window that is below that
  window), but cannot reproduce that reliably.

  I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1
  Threadripper system with no integrated GPU.

  No similar effects visible when in a GNOME / Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 12:17:02 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-08 (168 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago)

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


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


[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

2022-12-12 Thread Robert Liu
** Description changed:

- When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to
- an AP.
+ [ Impact ] 
+ When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not 
able connect to an AP.
  
- I tried a different libnl3 from BSP and found that WCN3980 can work
- correctly. The version used in BSP is 3.5.0.
+ However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly.
  
- I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
- According to the commit, it seems that the flag should be set for kernel 
later than 5.2.
+ After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is
+ identified as the root cause.
+ 
+ According to the commit, the "NLA_F_NESTED" flag should be set for
+ kernel later than 5.2.
+ 
+ [ Test Plan ]
+ Verify with the updated version, the WIFI module can:
+   1. scan WIFI networks
+   2. connect to an available network
+   3. access to the connected network
+ 
+ [ Where problems could occur ]
+ 1. kernel versions without NLA_F_NESTED flag defined
+   This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have 
it). It would not be a problem for an older kernel to understand/work with this 
change. Since the GA kernel is 5.4, so a generic image would still work.
+ 
+ 2. Drivers don't use the NESTED flag.
+   According to hui.wang's input, this change should not affect drivers which 
don't use the NESTED flag. But, it'd be better to cover more Wifi modules.
+ 
+ [ Other Info ]
+ 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch.
  
  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in OEM Priority Project:
  New
Status in libnl3 package in Ubuntu:
  New

Bug description:
  [ Impact ] 
  When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not 
able connect to an AP.

  However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly.

  After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is
  identified as the root cause.

  According to the commit, the "NLA_F_NESTED" flag should be set for
  kernel later than 5.2.

  [ Test Plan ]
  Verify with the updated version, the WIFI module can:
1. scan WIFI networks
2. connect to an available network
3. access to the connected network

  [ Where problems could occur ]
  1. kernel versions without NLA_F_NESTED flag defined
This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have 
it). It would not be a problem for an older kernel to understand/work with this 
change. Since the GA kernel is 5.4, so a generic image would still work.

  2. Drivers don't use the NESTED flag.
According to hui.wang's input, this change should not affect drivers which 
don't use the NESTED flag. But, it'd be better to cover more Wifi modules.

  [ Other Info ]
  22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998765/+subscriptions


-- 
Mailing list: https://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 1341155] Re: Xorg crashed with SIGABRT in pci_device_next() with mesa utils

2022-12-06 Thread Robert Avant
Hi,

That is fine, having updated I have not had a recurrence of this bug to my
knowledge.

Regards

R. Avant

On Mon, 5 Dec 2022, 6:48 pm Paul White, <1341...@bugs.launchpad.net>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. We are sorry that we do not always have the capacity to
> review all reported bugs in a timely manner.
>
> Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
>
> I'm setting the status of this bug to 'Incomplete' as it's not seen any
> activity for some time. If this issue is still relevant when using a
> currently maintained release of Ubuntu then please let us know which
> one(s) otherwise this bug report can be left to expire in approximately
> 60 days time.
>
> ** Changed in: xorg-server (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1378665).
> https://bugs.launchpad.net/bugs/1341155
>
> Title:
>   Xorg crashed with SIGABRT in pci_device_next() with mesa utils
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   came up when i installed mesa utils with nvidia optimus graphic card
>   and i was testing it happend when i change from nvidia to intel after
>   i tested glxgears
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 14.10
>   Package: xserver-xorg-core 2:1.15.1-0ubuntu8
>   ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
>   Uname: Linux 3.16.0-3-generic x86_64
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.14.4-0ubuntu2
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CrashCounter: 1
>   Date: Sat Jul 12 18:22:19 2014
>   DistUpgraded: Fresh install
>   DistroCodename: utopic
>   DistroVariant: ubuntu
>   ExecutablePath: /usr/bin/Xorg
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation Mobile 4 Series Chipset Integrated Graphics
> Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
>  Subsystem: ASUSTeK Computer Inc. Device [1043:1af2]
>   InstallationDate: Installed on 2014-07-10 (1 days ago)
>   InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
>   MachineType: ASUSTeK Computer Inc. UL30VT
>   ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth
> /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
>   ProcEnviron:
>
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic
> root=UUID=b797dc1a-0cba-433f-89ce-7fb6e4f6d4c9 ro quiet splash vt.handoff=7
>   Signal: 6
>   SourcePackage: xorg-server
>   StacktraceTop:
>pci_device_next () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
>pci_device_find_by_slot () from
> /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
>pci_device_vgaarb_init () from
> /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
>?? ()
>xf86BusConfig ()
>   Title: Xorg crashed with SIGABRT in pci_device_next()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   dmi.bios.date: 07/14/2010
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 211
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: UL30VT
>   dmi.board.vendor: ASUSTeK Computer Inc.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: ATN12345678901234567
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK Computer Inc.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
>   dmi.product.name: UL30VT
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK Computer Inc.
>   version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.54-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.8.2-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.910-0ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.10-1ubuntu2
>   xserver.bootTime: Sat Jul 12 18:22:34 2014
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id4140
>vendor AUO
>   xserver.version: 2:1.15.1-0ubuntu8
>
> To manage notifications about this bug go to:
>
> 

[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

2022-12-05 Thread Robert Liu
this issue was discovered in an OEM project.

** Package changed: libnl3 (Ubuntu) => oem-priority

** Changed in: oem-priority
 Assignee: (unassigned) => Robert Liu (robertliu)

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

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in OEM Priority Project:
  New
Status in libnl3 package in Ubuntu:
  New

Bug description:
  When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect
  to an AP.

  I tried a different libnl3 from BSP and found that WCN3980 can work
  correctly. The version used in BSP is 3.5.0.

  I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
  According to the commit, it seems that the flag should be set for kernel 
later than 5.2.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1998765/+subscriptions


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


[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

2022-12-05 Thread Robert Liu
** Tags added: orignate-from-lp1998578

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in libnl3 package in Ubuntu:
  New

Bug description:
  When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect
  to an AP.

  I tried a different libnl3 from BSP and found that WCN3980 can work
  correctly. The version used in BSP is 3.5.0.

  I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
  According to the commit, it seems that the flag should be set for kernel 
later than 5.2.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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


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


[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

2022-12-05 Thread Robert Liu
I made a test build (debdiff attached) and tried it on the target
device. This version works correctly.


** Patch added: "libnl3_3.4.0-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1998765/+attachment/5634558/+files/libnl3_3.4.0-1ubuntu1.debdiff

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in libnl3 package in Ubuntu:
  New

Bug description:
  When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect
  to an AP.

  I tried a different libnl3 from BSP and found that WCN3980 can work
  correctly. The version used in BSP is 3.5.0.

  I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
  According to the commit, it seems that the flag should be set for kernel 
later than 5.2.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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


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


[Desktop-packages] [Bug 1998765] [NEW] libnl3 3.4.0 doesn't work with WCN3980

2022-12-05 Thread Robert Liu
Public bug reported:

When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to
an AP.

I tried a different libnl3 from BSP and found that WCN3980 can work
correctly. The version used in BSP is 3.5.0.

I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the root 
cause.
According to the commit, it seems that the flag should be set for kernel later 
than 5.2.


[1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in libnl3 package in Ubuntu:
  New

Bug description:
  When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect
  to an AP.

  I tried a different libnl3 from BSP and found that WCN3980 can work
  correctly. The version used in BSP is 3.5.0.

  I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
  According to the commit, it seems that the flag should be set for kernel 
later than 5.2.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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


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


[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2022-11-29 Thread Robert Ancell
Targeting 22.04 so this can become part of the core22 snap fixing the
issue for most modern snaps.

** Changed in: glib2.0 (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu Kinetic)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu Lunar)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu Jammy)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: glib2.0 (Ubuntu Kinetic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: glib2.0 (Ubuntu Lunar)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  New
Status in glib2.0 source package in Jammy:
  New
Status in glib2.0 source package in Kinetic:
  New
Status in glib2.0 source package in Lunar:
  New

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


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


[Desktop-packages] [Bug 1998267] [NEW] glib not aware of snap confinement

2022-11-29 Thread Robert Ancell
Public bug reported:

[ Impact]

glib is not aware of snap confinement and this causes the internal logic
to decide when to use portals to not work as designed. One important
case is the gsettings backend, which should use a keyfile when confined
rather than using dconf. When using a fully confined desktop this is
required, as dconf is not suitable for sharing between snaps.

This has been fixed in glib main:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

[ Test Plan ]

1. Install gnome-calculator snap:
$ snap install gnome-calculator
2. Disconnect gsettings interface:
$ snap disconnect gnome-calculator:gsettings
3. Run gnome-calculator
4. Change mode from basic to advanced
5. Close and re-open gnome-calculator

Expected result:
Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

Observed result:
Mode change not remembered on second run, errors shown in console about 
accessing dconf:
(gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

[ Where problems could occur ]

- New bug introduced in glib causing a crash.
- Security issue introduced in glib due to accessing snapctl.
- Unexpected behaviour change when running snaps with updated glib.

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New

** Affects: glib2.0 (Ubuntu Jammy)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New

** Affects: glib2.0 (Ubuntu Kinetic)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New

** Affects: glib2.0 (Ubuntu Lunar)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New

** Also affects: glib2.0 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  New
Status in glib2.0 source package in Jammy:
  New
Status in glib2.0 source package in Kinetic:
  New
Status in glib2.0 source package in Lunar:
  New

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998267/+subscriptions


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


[Desktop-packages] [Bug 1950094]

2022-11-23 Thread Nv4y-robert
No bug also in
Version: 7.1.5.2 / LibreOffice Community
Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5
CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

on OpenSUSE 15.3 64 bit rpm.

This is (nearly) one of the versions tested for the bug description.

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

Title:
  libreoffice base zone liste choix impossible

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:

  Bonjour,

  Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé
  UbuntuMate 21.10 afin de voir si une modification avait été apporté à
  un éventuel bogue que je vous soumets.

  Le souci est avec la zone de liste dans LibreOffice Base avec la macro
  ci-dessous sur Événement "A réception du focus".

  Sub ActualiserListe(oEv as Object)
  oEv.Source.Model.Refresh
  End Sub

  pour mettre à jour la zone de liste après modification d'un élément.

  La mise à jour fonctionne bien mais je ne peux pas choisir une
  nouvelle entrée dans la liste. Alors que si je choisis un autre
  événement, comme "souris déplacée alors qu'une touche est pressée"
  beaucoup moins pratique, je ne rencontre pas ce problème.

  Après plusieurs recherches sur le forum OpenOffice il s'avère que la
  fonction marche bien mais que le problème pourrait venir de
  l'environnement Ubuntu.

  Sauriez-vous m'aider pour débloquer ma situation ?

  Dommage que je ne puisse pas joindre mon fichier pour des essais sur
  vos propres machines ce serait plus "parlant".

  Merci.
  Éric

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1950094/+subscriptions


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


[Desktop-packages] [Bug 1950094]

2022-11-23 Thread Nv4y-robert
Have tested this:
Opened "fbooks"
Entered new row with 'Informatik'.
Switched to previous row to save the data in table control.
Closed by button.
Switched to listbox.
'Informatik' will be shown.

So: No bug detected on
Version: 7.4.3.2 / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

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

Title:
  libreoffice base zone liste choix impossible

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:

  Bonjour,

  Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé
  UbuntuMate 21.10 afin de voir si une modification avait été apporté à
  un éventuel bogue que je vous soumets.

  Le souci est avec la zone de liste dans LibreOffice Base avec la macro
  ci-dessous sur Événement "A réception du focus".

  Sub ActualiserListe(oEv as Object)
  oEv.Source.Model.Refresh
  End Sub

  pour mettre à jour la zone de liste après modification d'un élément.

  La mise à jour fonctionne bien mais je ne peux pas choisir une
  nouvelle entrée dans la liste. Alors que si je choisis un autre
  événement, comme "souris déplacée alors qu'une touche est pressée"
  beaucoup moins pratique, je ne rencontre pas ce problème.

  Après plusieurs recherches sur le forum OpenOffice il s'avère que la
  fonction marche bien mais que le problème pourrait venir de
  l'environnement Ubuntu.

  Sauriez-vous m'aider pour débloquer ma situation ?

  Dommage que je ne puisse pas joindre mon fichier pour des essais sur
  vos propres machines ce serait plus "parlant".

  Merci.
  Éric

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1950094/+subscriptions


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


[Desktop-packages] [Bug 1950094]

2022-11-23 Thread Nv4y-robert
… and new book types could also be saved in both versions of LO, tested
with OpenSUSE 15.3 64bit rpm Linux.

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

Title:
  libreoffice base zone liste choix impossible

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:

  Bonjour,

  Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé
  UbuntuMate 21.10 afin de voir si une modification avait été apporté à
  un éventuel bogue que je vous soumets.

  Le souci est avec la zone de liste dans LibreOffice Base avec la macro
  ci-dessous sur Événement "A réception du focus".

  Sub ActualiserListe(oEv as Object)
  oEv.Source.Model.Refresh
  End Sub

  pour mettre à jour la zone de liste après modification d'un élément.

  La mise à jour fonctionne bien mais je ne peux pas choisir une
  nouvelle entrée dans la liste. Alors que si je choisis un autre
  événement, comme "souris déplacée alors qu'une touche est pressée"
  beaucoup moins pratique, je ne rencontre pas ce problème.

  Après plusieurs recherches sur le forum OpenOffice il s'avère que la
  fonction marche bien mais que le problème pourrait venir de
  l'environnement Ubuntu.

  Sauriez-vous m'aider pour débloquer ma situation ?

  Dommage que je ne puisse pas joindre mon fichier pour des essais sur
  vos propres machines ce serait plus "parlant".

  Merci.
  Éric

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1950094/+subscriptions


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


[Desktop-packages] [Bug 1969891] Re: Firefox snap can't be added to Dock favorites

2022-10-27 Thread Robert
Hey all,

I have the same issue.

My favourites setting lists the following:

:~$ gsettings get org.gnome.shell favorite-apps
['org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'virt-manager.desktop', 'libreoffice-calc.desktop', 
'signal-desktop_signal-desktop.desktop', 'firefox_firefox.desktop', 
'vivaldi-stable.desktop']


Please let me know if you require any further information as this is 
surprisingly annoying!

Thanks!

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

Title:
  Firefox snap can't be added to Dock favorites

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

Bug description:
  After upgrading from 21.10 to 22.04 the old Firefox was removed from
  my Dock favorites. I readded Firefox to my favorites which adds the
  Firefox icon to the favorites as expected.

  However, clicking on it will open the Firefox snap on the bottom of
  the Dock. So now I have 2 Firefox symbols in my Dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  Uname: Linux 5.17.0-4.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 08:49:32 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-05-31 (325 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

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


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


[Desktop-packages] [Bug 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-20 Thread Robert Bartko
After some testing issue appeared even with Intelligent Autohide
functi0on on Dash to Dock disabled.

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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


[Desktop-packages] [Bug 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-20 Thread Robert Bartko
Additionally it seems to affect only when Intelligent Autohide is on on
the Dash to dock Extension.

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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


[Desktop-packages] [Bug 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-19 Thread Robert Bartko
The screen is rather grey, the "start menu" works - in the upper right
corner. One can reboot the Computer. The icon at the bottom can be only
clicked but nothing happens, open applications not shown in the dock on
bottom as usual. Add-on as open weather is responsive.

Shortcuts don't work, can't launch any applications or switch between
them. Also launching terminal doesn't work or making printscreen
(shortcuts).

** Attachment added: "darkscreen.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993284/+attachment/5625172/+files/darkscreen.png

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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


[Desktop-packages] [Bug 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-18 Thread Robert Bartko
As seen in the attachment, after unlocking the screen only the dots menu
appears, after clicking it, the screen goes dark and only search is
active but not much else. One can still access reboot menu and restart
PC to fix the issue.

** Attachment added: "dashtodockBUG.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993284/+attachment/5624834/+files/dashtodockBUG.png

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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


[Desktop-packages] [Bug 1993284] [NEW] Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-18 Thread Robert Bartko
Public bug reported:

Happening in Ubuntu 22.04

How to reproduce:

Left computer idle and locked for quite some time
Unlock the computer
Only Show Applications icon is shown in dash-to-dock
When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

Log out / restart menu still works so I usually restart my computer to
fix this.

Affected application: micheleg-dash-to-dock

~$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

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

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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


[Desktop-packages] [Bug 1987976]

2022-10-15 Thread Robert Mader
Hm, this pretty much sounds like Gnome-Shell bug around Xwayland-on-
demand to me - so maybe a better place for that would be
https://gitlab.gnome.org/GNOME/mutter/-/issues (or a Ubuntu bug, in case
they ship some custom patches).

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987976]

2022-10-15 Thread Robert Mader
So the fact that even software rendering (`gfx.webrender.software:true`)
is broken strongly suggest that something with the affected setup is
deeply broken - disabling hardware acceleration is usually our last
resort for such issues.

Alan, have you tested a few other Xwayland apps and do they all work
correctly? And is this on a clean system without weird modifications? :P

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987976]

2022-10-15 Thread Robert Mader
Oh, that's really interesting...so does launching with
`MOZ_GTK_TITLEBAR_DECORATION=system` also solve the issue?

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987976]

2022-10-15 Thread Robert Mader
(In reply to Alan Jenkins from comment #35)
> Weird!

Indeed :( But thanks for testing!

> I can run glxgears, xeyes, and xvidtune ok :-). (Didn't bother trying
those immediately after login).

I think these are all apps with server side decorations (SSD). Could you
try `GDK_BACKEND=x11 cheese` or `GDK_BACKEND=x11 gedit`? So we have GTK
apps with client side decorations (CSD)?

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987976]

2022-10-15 Thread Robert Mader
Also, I suppose `gfx.webrender.software:true` works around the issue?

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1987976]

2022-10-15 Thread Robert Mader
Another interesting point would be if setting `gfx.x11-egl.force-
disabled` (in `about:config`) to `true` helps with the issue.

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1991472] [NEW] simple-scan does not work with hp5200

2022-10-01 Thread Robert Dinse
Public bug reported:

 Prior to upgrading from 22.04 to 22.10, simple-scan properly
supported my HP5200, now it fails saying cannot connect to scanner and
cannot connect to dbus.

 I attempted to install HP's version of hplip from their support
site, a fix that previously worked, but it does not work as it is
dependent upon qt4 which apparently is not available under 22.10.

 I attempted to contact their support but could not get through
their online filtering, same for calling them voice, so I was
unsuccessful.  Now I have to boot Win1o to scan documents and to put it
mildly I'm not a happy camper.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: simple-scan 42.0-1
Uname: Linux 5.19.12 x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Sat Oct  1 22:42:43 2022
MachineType: ASUS System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.12 
root=UUID=38243130-3d68-4f18-9973-08b9e226299f ro quiet splash 
i915.enable_gvt=1 intel_iommu=on iommu=pt vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2020
dmi.bios.release: 18.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1802
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z390-A
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.:bvr1802:bd12/01/2020:br18.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  simple-scan does not work with hp5200

Status in simple-scan package in Ubuntu:
  New

Bug description:
   Prior to upgrading from 22.04 to 22.10, simple-scan properly
  supported my HP5200, now it fails saying cannot connect to scanner and
  cannot connect to dbus.

   I attempted to install HP's version of hplip from their support
  site, a fix that previously worked, but it does not work as it is
  dependent upon qt4 which apparently is not available under 22.10.

   I attempted to contact their support but could not get through
  their online filtering, same for calling them voice, so I was
  unsuccessful.  Now I have to boot Win1o to scan documents and to put
  it mildly I'm not a happy camper.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: simple-scan 42.0-1
  Uname: Linux 5.19.12 x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat Oct  1 22:42:43 2022
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.12 
root=UUID=38243130-3d68-4f18-9973-08b9e226299f ro quiet splash 
i915.enable_gvt=1 intel_iommu=on iommu=pt vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2020
  dmi.bios.release: 18.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1802
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  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.:bvr1802:bd12/01/2020:br18.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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


[Desktop-packages] [Bug 1990448] Re: Show Ubuntu Pro settings

2022-09-21 Thread Robert Ancell
** Also affects: software-properties (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Show Ubuntu Pro settings

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Jammy:
  New
Status in software-properties source package in Kinetic:
  New

Bug description:
  Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead
  of just Livepatch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+subscriptions


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


[Desktop-packages] [Bug 1990448] [NEW] Show Ubuntu Pro settings

2022-09-21 Thread Robert Ancell
Public bug reported:

Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of
just Livepatch.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Also affects: software-properties (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Show Ubuntu Pro settings

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Jammy:
  New
Status in software-properties source package in Kinetic:
  New

Bug description:
  Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead
  of just Livepatch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1990448/+subscriptions


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


[Desktop-packages] [Bug 1980781] Re: SRU of ubuntu-advantage-desktop-daemon to older series

2022-09-19 Thread Robert Ancell
** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  SRU of ubuntu-advantage-desktop-daemon to older series

Status in ubuntu-advantage-desktop-daemon package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-desktop-daemon source package in Xenial:
  New
Status in ubuntu-advantage-desktop-daemon source package in Bionic:
  Fix Committed
Status in ubuntu-advantage-desktop-daemon source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  ubuntu-advantage-desktop-daemon is a service we added in 22.04 to let
  desktop application interact easily with Ubuntu Advantage

  adsys makes use of is to check if the system is connected to UA. This is 
supported in 20.04 LTS but until now the daemon was not available there.
  Installing the daemon enables advanced usages (scripts, privilege 
delegation…) which require an Ubuntu Pro account

  Ubuntu Pro integration is being added to software-properties which
  also require the service to be available.

  [Test Plan]

  A. Verify the service

  1. Install:
  $ sudo apt install ubuntu-advantage-desktop-daemon
  2. Check able to access daemon
  $ gdbus call --system --dest com.canonical.UbuntuAdvantage --object-path 
/com/canonical/UbuntuAdvantage/Manager --method 
org.freedesktop.DBus.Properties.GetAll 'com.canonical.UbuntuAdvantage.Manager'
  ({'Attached': , 'DaemonVersion': <'1.8'>},)

  B. Software-properties

  Verify that the new 'Ubuntu Pro' page is working as expected, SRU bug
  #, especially that it reflects the correct status and that
  attaching/detaching a token and enabling/disabling services is working

  C. Adsys (focal)

  1. Ensure that you have an Ubuntu Advantage subcription enabled.
  2. Setup some scripts under AD to be executed, one for machine scripts (on 
startup), one for user scripts (on login). Those scripts can create some 
temporary files under /tmp for instance.
  3. Reboot and login on the Ubuntu laptop connected with AD by adsys.
  4. Check that the scripts were executed by testing that the created file 
under /tmp are present.

  [Where problems could occur]

  This is a code that has not previously been used on 20.04 and thus
  could trigger new bugs. It has been used for since jammy though
  without major issues.

  A. The service itself

  The service shouldn't be active unless it's needed. If you don't have ubuntu 
advantage nor adsys configured check that the service is not loaded.
  The service should low on resource usage, check that it's the case by 
checking the RAM and CPU consumption.

  B. Software-properties

  The Ubuntu Pro tab didn't exist before so there should be no
  regression possible there due to the service. The livepatch enablement
  is handled through the service as part of UA now so check that
  livepatch is correctly working still on upgraded systems

  C. Adsys (focal)

  The behaviour change in adsys should be limited to enabling features
  which weren't available in focal before but we should ensure those are
  correctly working and not providing a buggy user experience

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1980781/+subscriptions


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


[Desktop-packages] [Bug 1917941] Re: System-config-printer keeps asking for network printer credentials

2022-09-15 Thread Robert
Storing the password from printer system dialog was running well for me
with ubuntu 20.04 lts.

Now, with ubuntu 22.04 lts the dialog is looking the same: with the
'remember password' checkbox. But, the password will be not stored any
more.

The dialog appears every time you print, regardless of whether you save
the password.

I have tested the behavior with a newly installed ubuntu 20.04 and
22.04. I printed from firefox with the printer system dialog.

Any ideas how to make this work again?

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

Title:
  System-config-printer keeps asking for network printer credentials

Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  I think I found a small bug in the printing process of Xubuntu
  20.04.02 LTS. I have a networked laser printer (Xerox Phaser 3250)
  that requires username/password credentials to print. The device is
  present in the CUPS page (see the Printers page in
  http://localhost:631) and uses the IPP protocol set to
  "ipp://192.168.1.10:631/ipp" URI. It is also visible in the system-
  config-printer window (XFCE Start button => Settings => Printers) and
  is set as default printer. The printer username/password are different
  than my PC username/password.

  Anyway, I noticed that the OS will sometimes pester me to enter the
  same credentials each time I try to print something. I recall the
  printing authorization window does have a "Remember password" checkbox
  that seemingly does nothing. Now why I am mentioning that this happens
  only sometimes? It's because I noticed that different programs will
  use different authorization windows to get printer credentials. For
  example, Mousepad will try to get credentials by using a CUPS popup
  dialog (I think). LibreOffice seems to popup its own small password
  entry window. This bug only applies to the cases where the printing is
  done via system-config-printer that uses its own authorization dialog.
  The printing works fine after credentials are entered though.

  So, after a short debug session I managed to narrow down the problem
  to this file: /usr/share/system-config-printer/jobviewer.py. I ran the
  applet.py and scp-dbus-service.py with the --debug option from command
  line to get some extra debug messages. Printing from Mousepad did not
  trigger any debug messages, but it did bring up the printing
  authorization dialog regardless. Like I've previously stated, Mousepad
  seems to use a different auth dialog, and I've verified (via seahorse)
  that this dialog works properly because it correctly stores the
  credentials into the keyring, and, if the Remember password checkbox
  is ticked, remembers them next time I try to print something. The
  problem only applies to the auth dialog triggered from jobviewer.py of
  system-config-printer. I managed to trigger the jobviewer auth dialog
  by trying to print something in LibreOffice Writer and then hitting
  Cancel in the small window that pops up. This will then trigger the
  *proper* jobviewer.py auth window to show up. It also triggers upon
  boot when there is something queued to be printed.

  It can also be reliably triggered queueing a print job, killing 
scp-dbus-service.py and applet.py and re-running them in this order:
  1) /usr/share/system-config-printer/scp-dbus-service.py --debug
  2) /usr/share/system-config-printer/applet.py --debug

  
  Though this jobviewer.py auth dialog will successfully save the printer 
credentials to the keyring, if the checkbox is ticked (verified with Seahorse), 
it will fail to read them next time, assume the credentials are missing, and 
ask the user to enter them. The error appears to happen in jobviewer.py:

  Line 1056: search_obj = ItemSearch(service, attrs)

  This line causes the following error to appear in the terminal:
  GLib-GIO-CRITICAL **: 19:28:31.663: g_dbus_connection_call_internal: 
assertion 'G_IS_DBUS_CONNECTION (connection)' failed

  The call fails to fetch any credentials and instead returns an empty
  result. I've written a short python script (see test.py) that
  reproduces the issue and triggers the same error.

  
  Related libsecret documentation:
  https://developer.gnome.org/libsecret/0.20/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer 1.5.12-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   
  CurrentDesktop: XFCE
  Date: Fri Mar  5 19:34:54 2021
  InstallationDate: Installed on 2020-01-20 (409 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Phaser-3250: ipp://192.168.1.10:631/ipp
  

[Desktop-packages] [Bug 1987342] [NEW] package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit statu

2022-08-22 Thread Robert Simpson
Public bug reported:

This was an automated message during an upgrade:

package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade:
installed nvidia-340 package post-installation script subprocess
returned error exit status 10

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Aug 22 20:09:15 2022
ErrorMessage: installed nvidia-340 package post-installation script subprocess 
returned error exit status 10
InstallationDate: Installed on 2021-09-10 (345 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
UpgradeStatus: Upgraded to focal on 2022-08-22 (0 days ago)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal third-party-packages

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

Title:
  package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade:
  installed nvidia-340 package post-installation script subprocess
  returned error exit status 10

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  This was an automated message during an upgrade:

  package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade:
  installed nvidia-340 package post-installation script subprocess
  returned error exit status 10

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug 22 20:09:15 2022
  ErrorMessage: installed nvidia-340 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-09-10 (345 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
  UpgradeStatus: Upgraded to focal on 2022-08-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1987342/+subscriptions


-- 
Mailing list: https://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 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

2022-08-22 Thread Robert P. J. Day
Thanks, I'll check it out.

On Mon, Aug 22, 2022 at 9:50 AM Olivier Tilloy <1987...@bugs.launchpad.net>
wrote:

> This upstream bug seems relevant:
> https://bugs.chromium.org/p/chromium/issues/detail?id=1340181
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987137
>
> Title:
>   Migrating chromium-browser to core22 has libwayland-client0 issues
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   Following on an earlier bug report that related to simple core22
>   migration for chromium-browser, here is a blocker that I don't know
>   how to deal with.
>
>   After checking out the core22 branch from
>   git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
>   (which already contains the early, easy migration commits), doing a
>   build eventually generates (snippet here):
>
>   2022-08-19 20:15:05.809 :: In file included from
> ../../third_party/wayland/src/src/wayland-client.h:40:
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.809 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.809 ::^
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.810 ::^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>   2022-08-19 20:15:05.810 ::  ^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>   and lots more of the same; it seems pretty clear that the relevant
>   wayland library is simply not new enough, and I don't know what to
>   add/modify to add core22 support to the mix, so I am open to
>   suggestions.
>
>   I do notice the file
>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
>   which contains package version manifests for various distros, but not
>   Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
>   that's just a guess.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions
>
>

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  2022-08-19 20:15:05.810 ::  ^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor,

  and lots more of the same; it seems pretty clear that the relevant
  wayland library is simply not new enough, and I don't know what to
  add/modify to add core22 support to the mix, so I am open to
  suggestions.

  I do notice the file
  

Re: [Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

2022-08-22 Thread Robert P. J. Day
OK, I'll take a look at that when time permits.

On Mon, Aug 22, 2022 at 8:36 AM Nathan Teodosio <1987...@bugs.launchpad.net>
wrote:

> > Can I adjust snapcraft.yaml to override 1.20.0 and specifically
> request 1.18.0?
>
> We used override-build to get newer versions of Libva:
> https://git.launchpad.net/~nteodosio/chromium-
> browser/tree/snapcraft.yaml?h=hwacc#n362
>
> I wonder if you could do the same for libwayland-client0, but this could
> be more difficult if it is in a dependency tree...
>
> > Or maybe I can check if there is a development version of chromium
> that has already moved up to 1.20.0.
>
> According to that README file, I would try the "To import a new snapshot
> of wayland:" instructions with git checkout 1.20.0.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987137
>
> Title:
>   Migrating chromium-browser to core22 has libwayland-client0 issues
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   Following on an earlier bug report that related to simple core22
>   migration for chromium-browser, here is a blocker that I don't know
>   how to deal with.
>
>   After checking out the core22 branch from
>   git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
>   (which already contains the early, easy migration commits), doing a
>   build eventually generates (snippet here):
>
>   2022-08-19 20:15:05.809 :: In file included from
> ../../third_party/wayland/src/src/wayland-client.h:40:
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.809 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.809 ::^
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.810 ::^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>   2022-08-19 20:15:05.810 ::  ^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>   and lots more of the same; it seems pretty clear that the relevant
>   wayland library is simply not new enough, and I don't know what to
>   add/modify to add core22 support to the mix, so I am open to
>   suggestions.
>
>   I do notice the file
>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
>   which contains package version manifests for various distros, but not
>   Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
>   that's just a guess.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions
>
>

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  2022-08-19 

Re: [Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

2022-08-22 Thread Robert P. J. Day
Well, yes, that would be the problem. What would be the for-the-moment
hacky workaround (if any)? Can I adjust snapcraft.yaml to override 1.20.0
and specifically request 1.18.0? Or maybe I can check if there is a
development version of chromium that has already moved up to 1.20.0. This
is not a high priority, it would just be nice to have.

On Mon, Aug 22, 2022 at 5:46 AM Olivier Tilloy <1987...@bugs.launchpad.net>
wrote:

>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
> isn't used by the snap build process, so that's not the right thing to
> look at.
>
> There appears to be an incompatibility between the version of libwayland
> in Ubuntu 22.04 (1.20.0) and the version vendored into the chromium
> source tree (1.18.0 according to
>
> https://source.chromium.org/chromium/chromium/src/+/main:third_party/wayland/README.chromium
> ).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987137
>
> Title:
>   Migrating chromium-browser to core22 has libwayland-client0 issues
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   Following on an earlier bug report that related to simple core22
>   migration for chromium-browser, here is a blocker that I don't know
>   how to deal with.
>
>   After checking out the core22 branch from
>   git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
>   (which already contains the early, easy migration commits), doing a
>   build eventually generates (snippet here):
>
>   2022-08-19 20:15:05.809 :: In file included from
> ../../third_party/wayland/src/src/wayland-client.h:40:
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.809 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.809 ::^
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.810 ::^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>   2022-08-19 20:15:05.810 ::  ^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>   and lots more of the same; it seems pretty clear that the relevant
>   wayland library is simply not new enough, and I don't know what to
>   add/modify to add core22 support to the mix, so I am open to
>   suggestions.
>
>   I do notice the file
>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
>   which contains package version manifests for various distros, but not
>   Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
>   that's just a guess.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions
>
>

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 

[Desktop-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2022-08-21 Thread Robert Rongen
Solved by executing amixer -q -D pulse sset Master toggle
https://askubuntu.com/a/1341471

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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


[Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

2022-08-19 Thread Robert P. J. Day
** Description changed:

  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know how
  to deal with.
  
  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (which
  already contains the early, easy migration commits), doing a build
  eventually generates (snippet here):
  
+ 2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
+ 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
+ 2022-08-19 20:15:05.809 ::^
+ 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
+ 2022-08-19 20:15:05.810 ::^
+ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
+ 2022-08-19 20:15:05.810 ::  ^
+ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor,
  
- 2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

- 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
- 2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

- 2022-08-19 20:15:05.809 ::^   

   
- 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
- 2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

- 2022-08-19 20:15:05.810 ::^   

   
- 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
- 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  
- 2022-08-19 20:15:05.810 ::  ^ 

   
- 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
- 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor, 
+ and lots more of the same; it seems pretty clear that the relevant
+ wayland library is simply not new enough, and I don't know what to
+ add/modify to add core22 support to the mix, so I am open to
+ suggestions.
  
- 
- and lots more of the same; it seems pretty clear that the relevant wayland 
library is simply not new enough, and I don't know what to add/modify to add 
core22 support to the mix, so I am open to suggestions.
+ I do notice the file
+ parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
+ which contains package version manifests for various distros, but not
+ Ubuntu 22.04, so I'm *guessing* that might need enhancement. But that's
+ just a guess.

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch 

[Desktop-packages] [Bug 1987137] [NEW] Migrating chromium-browser to core22 has libwayland-client0 issues

2022-08-19 Thread Robert P. J. Day
Public bug reported:

Following on an earlier bug report that related to simple core22
migration for chromium-browser, here is a blocker that I don't know how
to deal with.

After checking out the core22 branch from
git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (which
already contains the early, easy migration commits), doing a build
eventually generates (snippet here):


2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

2022-08-19 20:15:05.809 ::^ 

 
2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

2022-08-19 20:15:05.810 ::^ 

 
2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy 
*) wl_registry, 
 
2022-08-19 20:15:05.810 ::  ^   

 
2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy 
*) wl_compositor, 


and lots more of the same; it seems pretty clear that the relevant wayland 
library is simply not new enough, and I don't know what to add/modify to add 
core22 support to the mix, so I am open to suggestions.

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

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  
  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

  2022-08-19 20:15:05.809 ::^   

   
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

  2022-08-19 20:15:05.810 ::^   

   
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
  2022-08-19 

[Desktop-packages] [Bug 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done

2022-08-19 Thread Robert P. J. Day
** Changed in: chromium-browser (Ubuntu)
   Status: New => Invalid

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

Title:
  snapcraft build fails on second run as "ln -s libdrm.pc libdrm-
  uninstalled.pc" already done

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I'm trying to migrate the chromium browser snapcraft.yaml file to
  core22 and Snapcraft 7 and, after a build error on the first test
  (more on that later), I cleaned and re-ran the build to make sure the
  build error was reproducible, and got:

  ... big snip ...
  2022-08-18 08:50:45.224 :: + OUT=out/Release  
 
  2022-08-18 08:50:45.224 :: + mkdir -p out/Release 
 
  2022-08-18 08:50:45.243 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc
 
  2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 
'libdrm-uninstalled.pc': File exists 
  2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 
1.
  Review the scriptlet and make sure it's correct. 

  Naturally, since that symlink had been created during the first run
  (in a persistent 22.04 LXD container), it was still there for the
  second run. Operations like that should be idempotent so one can run
  multiple builds.

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


-- 
Mailing list: https://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 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

2022-08-19 Thread Robert P. J. Day
Ok, thanks.

On Fri, Aug 19, 2022 at 8:10 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> > Perhaps one should create a core 22 branch where I can submit my
> changes.
>
> I think that is only possible with a team. See if you can push to
> https://code.launchpad.net/~chromium-core22/+git/chromium-core22. If
> yes, just force push your current work to it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

2022-08-19 Thread Robert P. J. Day
My interest in this is that I'm stress testing migrating snaps to core
22/snapcraft 7 as part of the update for the Snapcraft 101 course, and when
I asked my team for an example of a snap that would be challenging to
migrate, one of them immediately suggested chromium, so that's why I'm
working on this. So far, the necessary changes were fairly minimal, until
this issue, which I don't know what to do with.

Perhaps one should create a core 22 branch where I can submit my
changes.

In terms of getting more output, with Snapcraft 7, I'm running "snapcraft
--verbosity=trace" for tons of output.

Anyway, this wl_proxy* stuff is the current bottleneck.

On Fri, Aug 19, 2022 at 7:25 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> For a matter of fact, wl_proxy_marshal_flags is declared in wayland-
> client-core.h, provided by libwayland-dev, which is specified in the
> build-packages of chromium in snapcraft.yaml. As long as it is version
> >=1.20, I'd think it should work, but reality shows otherwise.
>
> I'm trying to build the snap too so I can see full logs, but weirdly
> they are much less verbose than what I'm used to (e.g.
>
> https://launchpadlibrarian.net/618908242/buildlog_snap_ubuntu_jammy_amd64_chromium-
> browser-core22_BUILDING.txt.gz
> ),
> and I don't want to believe that would
> be caused by a mere switch to core22.
>
> > P.S. Thanks for your patience with all of this.
>
> No such thing, it's a pleasure :). This is both useful and a great
> chance to better understand snaps.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying 

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

2022-08-18 Thread Robert P. J. Day
Last comment for the day ... from what little I've seen, it seems like it
might require defining a lengthy list of packages relative to 22.04 to
migrate this snap to 22.04. Or maybe I'm misreading it. In any event, I'd
still like to make this happen.

On Thu, Aug 18, 2022 at 3:56 PM Robert Day 
wrote:

> Actually, another part of my grep search produced the following, which
> seems to suggest that an older version of libwayland-client0 is being used:
>
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mips64el.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm64:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_arm64.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.i386:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_i386.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.armel:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armel.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mipsel:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mipsel.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armhf.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.amd64:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_amd64.deb
>
> At least that's the way I read it.
>
> rday
>
> On Thu, Aug 18, 2022 at 3:43 PM Robert Day 
> wrote:
>
>> A comprehensive grep includes the lines:
>>
>> parts/launcher/state/build:  - libwayland-client0=1.20.0-1
>> parts/va-drivers/state/build:  - libwayland-client0=1.20.0-1
>> parts/pipewire/state/build:  - libwayland-client0=1.20.0-1
>> parts/chromium-build/state/build:  - libwayland-client0=1.20.0-1
>> parts/manpage/state/build:  - libwayland-client0=1.20.0-1
>>
>> Oh, wait, there we
>> go: 
>> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
>> appears to be a version manifest that does not include anything for 22.04.
>> Does that sound like the problem?
>>
>> P.S. Thanks for your patience with all of this.
>>
>> On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <
>> 1986...@bugs.launchpad.net> wrote:
>>
>>> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>>>
>>> wayland-1.21.0/debian/libwayland-client0.symbols:
>>> wl_proxy_marshal_flags@Base 1.20.0
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1986925
>>>
>>> Title:
>>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>>
>>> Status in chromium-browser package in Ubuntu:
>>>   New
>>>
>>> Bug description:
>>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>>   did what seemed necessary to update snapcraft.yaml to build with
>>>   snapcraft 7 for core22. The only change of any significance was to
>>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>>   extension. I started the build and it ran for quite some time (in a
>>>   persistent 22.04 LXD container) until:
>>>
>>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>>
>>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>>
>>>   2022-08-18 09:11:00.888 :: + cp
>>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>>
>>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>>
>>>   2022-08-18 09:11:00.935 :: + cd -
>>>
>>>   2022-08-18 09:11:00.935 ::
>>> /root/snaps

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

2022-08-18 Thread Robert P. J. Day
Actually, another part of my grep search produced the following, which
seems to suggest that an older version of libwayland-client0 is being used:

parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mips64el.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm64:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_arm64.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.i386:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_i386.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.armel:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armel.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mipsel:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mipsel.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armhf.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.amd64:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_amd64.deb

At least that's the way I read it.

rday

On Thu, Aug 18, 2022 at 3:43 PM Robert Day 
wrote:

> A comprehensive grep includes the lines:
>
> parts/launcher/state/build:  - libwayland-client0=1.20.0-1
> parts/va-drivers/state/build:  - libwayland-client0=1.20.0-1
> parts/pipewire/state/build:  - libwayland-client0=1.20.0-1
> parts/chromium-build/state/build:  - libwayland-client0=1.20.0-1
> parts/manpage/state/build:  - libwayland-client0=1.20.0-1
>
> Oh, wait, there we
> go: 
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
> appears to be a version manifest that does not include anything for 22.04.
> Does that sound like the problem?
>
> P.S. Thanks for your patience with all of this.
>
> On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <
> 1986...@bugs.launchpad.net> wrote:
>
>> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>>
>> wayland-1.21.0/debian/libwayland-client0.symbols:
>> wl_proxy_marshal_flags@Base 1.20.0
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1986925
>>
>> Title:
>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>
>> Status in chromium-browser package in Ubuntu:
>>   New
>>
>> Bug description:
>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>   did what seemed necessary to update snapcraft.yaml to build with
>>   snapcraft 7 for core22. The only change of any significance was to
>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>   extension. I started the build and it ran for quite some time (in a
>>   persistent 22.04 LXD container) until:
>>
>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>
>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>
>>   2022-08-18 09:11:00.888 :: + cp
>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>
>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>
>>   2022-08-18 09:11:00.935 :: + cd -
>>
>>   2022-08-18 09:11:00.935 ::
>> /root/snaps/snap-from-source/parts/chromium/build
>>
>>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>
>>   2022-08-18 09:11:07.112 :: ERROR at
>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
>> code.
>>
>>   2022-08-18 09:11:07.112 :: pkgresult =
>> exec_script(pkg_config_script, args, "value")
>>   2022-08-18 09:11:07.113 :: ^--
>>
>>   2022-08-18 09:11:07.113 :: Current dir:
>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>>   2022-08-18 09:11:07.113 :: Command: python3
>> /root/snaps/snap-from-source/parts/chromium/bui

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

2022-08-18 Thread Robert P. J. Day
A comprehensive grep includes the lines:

parts/launcher/state/build:  - libwayland-client0=1.20.0-1
parts/va-drivers/state/build:  - libwayland-client0=1.20.0-1
parts/pipewire/state/build:  - libwayland-client0=1.20.0-1
parts/chromium-build/state/build:  - libwayland-client0=1.20.0-1
parts/manpage/state/build:  - libwayland-client0=1.20.0-1

Oh, wait, there we
go: 
parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
appears to be a version manifest that does not include anything for 22.04.
Does that sound like the problem?

P.S. Thanks for your patience with all of this.

On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>
> wayland-1.21.0/debian/libwayland-client0.symbols:
> wl_proxy_marshal_flags@Base 1.20.0
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

2022-08-18 Thread Robert P. J. Day
This appears to describe precisely this issue:

https://github.com/libsdl-org/SDL/pull/5092

On Thu, Aug 18, 2022 at 1:06 PM Robert Day 
wrote:

> Yup, same errors ... lots of "wl "and "marshal" undefined references.
> Here's just a small sample:
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1038:13:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>
>
> 2022-08-18 17:03:57.646 ::^
>
>
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1062:13:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>
>
> 2022-08-18 17:03:57.646 ::^
>
>
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1175:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>
>
> 2022-08-18 17:03:57.646 ::  ^
>
>
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1291:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>
> 2022-08-18 17:03:57.647 ::  ^
>
>
>
> 2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1307:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>
> 2022-08-18 17:03:57.647 ::  ^
>
>
>
> 2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1371:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_shm_pool,
>
>
> 2022-08-18 17:03:57.647 ::  ^
>
>
> On Thu, Aug 18, 2022 at 1:04 PM Robert Day 
> wrote:
>
>> That's what I did, but that's also when I got the errors I included in my
>> previous comment. I'm rebuilding just to make sure those errors are
>> reproducible.
>>
>> On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <
>> 1986...@bugs.launchpad.net> wrote:
>>
>>> > but that appears to be because this newer gnome does not supply such
>>> an executable; there is no "pkg-config" under
>>> /snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
>>> under gnome-3-38.
>>>
>>> Oh, so this time pkg-config in build-packages could solve it? Probably
>>> you will have to remove the pkg_config line from args.gn, though.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1986925
>>>
>>> Title:
>>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>>
>>> Status in chromium-browser package in Ubuntu:
>>>   New
>>>
>>> Bug description:
>>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>>   did what seemed necessary to update snapcraft.yaml to build with
>>>   snapcraft 7 for core22. The only change of any significance was to
>>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>>   extension. I started the build and it ran for quite some time (in a
>>>   persistent 22.04 LXD container) until:
>>>
>>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>>
>>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>>
>>>   2022-08-18 09:11:00.888 :: + cp
>>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>>
>>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>>
>>>   2022-08-18 09:11:00.935 :: + cd -
>>>
>>>   2022-08-18 09:11:00.935 ::
>>> /root/snaps/snap-from-source/parts/chromium/build
>>>
>>>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>>
>>>   2022-0

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

2022-08-18 Thread Robert P. J. Day
Yup, same errors ... lots of "wl "and "marshal" undefined references.
Here's just a small sample:

2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1038:13:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.646 :: callback =
wl_proxy_marshal_flags((struct wl_proxy *) wl_display,


2022-08-18 17:03:57.646 ::^


2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1062:13:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.646 :: registry =
wl_proxy_marshal_flags((struct wl_proxy *) wl_display,


2022-08-18 17:03:57.646 ::^


2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1175:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_registry,


2022-08-18 17:03:57.646 ::  ^


2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1291:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_compositor,


2022-08-18 17:03:57.647 ::  ^


2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1307:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_compositor,


2022-08-18 17:03:57.647 ::  ^


2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1371:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_shm_pool,


2022-08-18 17:03:57.647 ::  ^


On Thu, Aug 18, 2022 at 1:04 PM Robert Day  wrote:

> That's what I did, but that's also when I got the errors I included in my
> previous comment. I'm rebuilding just to make sure those errors are
> reproducible.
>
> On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <
> 1986...@bugs.launchpad.net> wrote:
>
>> > but that appears to be because this newer gnome does not supply such
>> an executable; there is no "pkg-config" under
>> /snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
>> under gnome-3-38.
>>
>> Oh, so this time pkg-config in build-packages could solve it? Probably
>> you will have to remove the pkg_config line from args.gn, though.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1986925
>>
>> Title:
>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>
>> Status in chromium-browser package in Ubuntu:
>>   New
>>
>> Bug description:
>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>   did what seemed necessary to update snapcraft.yaml to build with
>>   snapcraft 7 for core22. The only change of any significance was to
>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>   extension. I started the build and it ran for quite some time (in a
>>   persistent 22.04 LXD container) until:
>>
>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>
>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>
>>   2022-08-18 09:11:00.888 :: + cp
>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>
>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>
>>   2022-08-18 09:11:00.935 :: + cd -
>>
>>   2022-08-18 09:11:00.935 ::
>> /root/snaps/snap-from-source/parts/chromium/build
>>
>>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>
>>   2022-08-18 09:11:07.112 :: ERROR at
>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
>> code.
>>
>>   2022-08-18 09:11:07.112 :: pkgresult =
>> exec_script(pkg_config_script, args, "value")
>>   2022-08-18 09:11:07.113 :: ^--
>>
>>   2022-08-18 09:11:07.113 :: Current dir:
>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>>   2022-08-18 09:11:07.113 :: Command: python3
>> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
>> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>>
>>   2022-08-18 09:11:07.113 :: Ret

  1   2   3   4   5   6   7   8   9   10   >