[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB

2024-04-10 Thread Erkin Alp Güney
The "journalctl -xb" one, right?

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

Title:
  gnome desktop cannot start as mutter fails to find drmModeCloseFB

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0:
  undefined symbol: drmModeCloseFB

  Package libdrm2: 
  i   2.4.120-2 noble 
500 

  Package libdrm2:i386:
  i   2.4.120-2 noble 
500 

  Package libmutter-14-0:
  i   46.0-1ubuntu6 noble 
500 

  Package mutter:
  i   46.0-1ubuntu6 noble 
500

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


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


[Desktop-packages] [Bug 1958019]

2024-04-10 Thread thornley.david
FYI, broken again in 6.8.4, 6.8.3 (not sure about 6.8.2).

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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


[Desktop-packages] [Bug 2052913] Re: [nvidia] Large Performance Regression in fullscreen windows from Ubuntu Jammy to Ubuntu Noble

2024-04-10 Thread Eduard Kachur
Can be related, I see that fullscreen windows are not being unredirected when 
running Wayland session with mutter 46 (gfx1103_r1, LLVM 15.0.7, DRM 3.57, 
6.8.0-22-generic):
RENDER: No direct scanout candidate: paint-box 
(1688.00,-11.00,62.00,62.00) does not match stage-view layout 
(0,0,1920,1080)

Actually right after boot when opening video in firefox I can see that
it's being unredirected, but after launching few apps, log above is
being shown for fullscreen windows.

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

Title:
  [nvidia] Large Performance Regression in fullscreen windows from
  Ubuntu Jammy to Ubuntu Noble

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble 
(gnome-shell 45.3-1ubuntu1)
  Default Ubuntu GNOME desktop environment used with no user added extensions.

  GPU driverstack identical between the two distros (eliminated as a variable).
  Linux kernel identical between distros (eliminated as a variable)
  CPU, GPU, and RAM clocks pinned to max.

  Test case: Minecraft Java Edition (shared drive with identical setup
  between Ubuntu versions). Fullscreen 1080p. Xorg display server.

  FPS (uncapped):
  Ubuntu Jammy: 177fps
  Ubuntu Noble: 140fps

  Observations:
  Ubuntu Jammy:
  gnome-shell process cpu% when camera is still: 0-1%
  gnome-shell process cpu% when camera is moving: 10-20%
  Memory Bandwidth (CPU and GPU shared): 40%

  Ubuntu Noble:
  gnome-shell process cpu% when camera is still: 20-55%
  gnome-shell process cpu% when camera is moving: 30-55%
  Memory Bandwidth (CPU and GPU shared): 50%

  In both cases GPU utilization is observed to be near 100%.

  So in summary, large performance regression regression which appears
  to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on
  ubuntu jammy when there the camera is still (even with a fps graph
  drawn onscreen) in stark contrast to ubuntu noble.

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


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


[Desktop-packages] [Bug 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git

2024-04-10 Thread Andreas Karlson
Till,
Thanks for the quick reply!

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

Title:
  cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported
  commits from 2.4.x git

Status in cups package in Ubuntu:
  In Progress

Bug description:
  While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 
2.4.7-1.2ubuntu5),
  I noticed that cupsd crashes consistently after closing my Firefox tab / 
window.
  The title of the crash (from the bug-report window) is "cupsd crashed with 
SIGSEGV in ???()"

  I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying
  some updates from the noble and noble-proposed pockets.

  Reproduction steps:
  1. Open Firefox and manage CUPS on http://localhost:631
  2. Go to Administration -> Printers -> Add Printer and choose your printer
  3. Add your printer (I used the ipps:// protocol to manage the printer)
  4. After clicking the "Add printer" button, immediately close your Firefox tab
  5. cupsd will crash and Ubuntu will display a bug-report popup

  Versions:
  Firefox - 124.0.1-1 r4033
  CUPS - 2.4.7-1.2ubuntu5

  Printer:
  Lexmark MS415dn (supported)

  I am unable to reproduce this bug on versions prior to
  2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2).

  Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from 
the 2.4.x upstream git branch, so I also opened an issue on GitHub:
  https://github.com/OpenPrinting/cups/issues/934

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


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


[Desktop-packages] [Bug 2060361] Re: Dateisysten

2024-04-10 Thread Christian Ehrhardt 
Nautilus Problem, möglich.

Kernel problem, halte ich für unwahrscheinlich aber nicht unmöglich.

Sicher ist allerdings das ohne Nachvollziehbare Schritte hier leider
keine weiterhelfen kann.

Ich aktualisiere den Fall dazu passend, aber ohne weitere Info wird
leider nichts mehr passieren.

P.S. Ich halte es auch immer noch für möglich das es eine
Unsicherheit/Unklarheit bei der verwendung ist und alles eigentlich OK
ist. Doch auch das kann man ohne Nachvollziehbares nicht prüfen.

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

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

** Changed in: cloud-images
   Status: Incomplete => Invalid

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

Title:
  Dateisysten

Status in cloud-images:
  Invalid
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  
  Wenn ich eine grosse Datei lösche wird dasDateisysten
  Nicht freigegeben

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2060361/+subscriptions


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


[Desktop-packages] [Bug 2060659] Re: X11 fractional scaling support is missing in 46.0

2024-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  X11 fractional scaling support is missing in 46.0

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  X11 fractional scaling support is missing in mutter/gnome-shell 46.0

  https://salsa.debian.org/gnome-
  team/mutter/-/commit/414010ddef06757000175c30238371739199d29a

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


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


[Desktop-packages] [Bug 2060762] Re: Yaru cursor theme is different at windows created by GNOME Core applications

2024-04-10 Thread Daniel van Vugt
OK the broken cursor is just some leftover from previous system
customizations. To fix it just run:

  gsettings set org.gnome.desktop.interface cursor-theme Yaru

** Changed in: yaru-theme (Ubuntu)
   Status: Incomplete => Invalid

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3184
   https://gitlab.gnome.org/GNOME/mutter/-/issues/3184

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

Title:
  Yaru cursor theme is different at windows created by GNOME Core
  applications

Status in yaru-theme package in Ubuntu:
  Invalid

Bug description:
  I am using Ubuntu 24.04 LTS. When I hover over windows created by
  Nautilus, GNOME Maps, Epiphany etc. (Evolution is OK), the cursor
  becomes extremely huge. I have attached screenshots showing the
  change. Zenity has the same problem. I know: it is a bit humorous that
  I report bugs with the cursor in the middle of that thing with XZ, but
  it can be fixed in 24.04.1 or even before the final freeze.

  Yaru version: 24.04.0-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: yaru-theme-gnome-shell 24.04.0-0ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 06:49:20 2024
  Dependencies:
   
  InstallationDate: Installed on 2023-07-05 (280 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2060762/+subscriptions


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


[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB

2024-04-10 Thread Daniel van Vugt
Thanks, they do look correct. Can you attach more of the system log from
when 'symbol lookup error' is mentioned?

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

Title:
  gnome desktop cannot start as mutter fails to find drmModeCloseFB

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0:
  undefined symbol: drmModeCloseFB

  Package libdrm2: 
  i   2.4.120-2 noble 
500 

  Package libdrm2:i386:
  i   2.4.120-2 noble 
500 

  Package libmutter-14-0:
  i   46.0-1ubuntu6 noble 
500 

  Package mutter:
  i   46.0-1ubuntu6 noble 
500

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


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


[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

2024-04-10 Thread Thierry MACHICOANE
Running "journalctl -b0 | grep MetaSyncRing", I confirm having this bug,
which appeared roughly 2 w-ago after classical update.

This implies lack of responsiveness (up to 2 seconds lags) in terminal
as well as in GUI, especially when dragging objects, scrolling, double-
clicking and so on.

Configuration:
 * 6.5.0-27-generic #28~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 15 10:51:06 
UTC 2 x86_64 x86_64 x86_64 GNU/Linux
 * NVIDIA-SMI 535.161.07

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  In Progress
Status in mutter source package in Mantic:
  In Progress
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Run: journalctl -b0 | grep MetaSyncRing
  4. Verify the above command does NOT show "MetaSyncRing" messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since the code
  being modified is only used with that driver.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2060799] [NEW] no ubuntu's parameter is found

2024-04-10 Thread Hoang
Public bug reported:

There is not any found ubuntu's parameter

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-control-center 1:45.0-1ubuntu3.1
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 12:53:12 2024
InstallationDate: Installed on 2023-09-18 (205 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to mantic on 2024-03-25 (16 days ago)

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


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

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

Title:
  no ubuntu's parameter is found

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

Bug description:
  There is not any found ubuntu's parameter

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 12:53:12 2024
  InstallationDate: Installed on 2023-09-18 (205 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2024-03-25 (16 days ago)

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


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


[Desktop-packages] [Bug 2060679] Re: No icons for gtk4 applications under noble

2024-04-10 Thread Sebastien Bacher
It seems to be a mesa issue which should get fixed with the incoming
point release

https://gitlab.freedesktop.org/mesa/mesa/-/issues/10853

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #10853
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/10853

** Package changed: gtk4 (Ubuntu) => mesa (Ubuntu)

** Changed in: mesa (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  No icons for gtk4 applications under noble

Status in mesa package in Ubuntu:
  In Progress

Bug description:
  While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta,
  I noticed that all GTK4 applications appear to be missing various
  icons. All lack the minimize / maximize / close icons (which are left
  as three empty circles on the window), and others lack icons within
  the windows, e.g. on various controls like radio buttons, or folder
  icons in nautilus. GTK3 applications appear unaffected. I'll attach
  some screenshots demonstrating the issue.

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


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


[Desktop-packages] [Bug 2052913] Re: [Xorg] Large performance regression in fullscreen windows

2024-04-10 Thread Daniel van Vugt
** Summary changed:

- [nvidia] Large Performance Regression in fullscreen windows from Ubuntu Jammy 
to Ubuntu Noble
+ [Xorg] Large performance regression in fullscreen windows

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

Title:
  [Xorg] Large performance regression in fullscreen windows

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble 
(gnome-shell 45.3-1ubuntu1)
  Default Ubuntu GNOME desktop environment used with no user added extensions.

  GPU driverstack identical between the two distros (eliminated as a variable).
  Linux kernel identical between distros (eliminated as a variable)
  CPU, GPU, and RAM clocks pinned to max.

  Test case: Minecraft Java Edition (shared drive with identical setup
  between Ubuntu versions). Fullscreen 1080p. Xorg display server.

  FPS (uncapped):
  Ubuntu Jammy: 177fps
  Ubuntu Noble: 140fps

  Observations:
  Ubuntu Jammy:
  gnome-shell process cpu% when camera is still: 0-1%
  gnome-shell process cpu% when camera is moving: 10-20%
  Memory Bandwidth (CPU and GPU shared): 40%

  Ubuntu Noble:
  gnome-shell process cpu% when camera is still: 20-55%
  gnome-shell process cpu% when camera is moving: 30-55%
  Memory Bandwidth (CPU and GPU shared): 50%

  In both cases GPU utilization is observed to be near 100%.

  So in summary, large performance regression regression which appears
  to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on
  ubuntu jammy when there the camera is still (even with a fps graph
  drawn onscreen) in stark contrast to ubuntu noble.

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


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


[Desktop-packages] [Bug 2049670] Re: noble: gnome-initial-setup 20 second delay & error popup

2024-04-10 Thread Nathan Teodosio
** Changed in: gnome-initial-setup (Ubuntu)
   Status: Fix Committed => Fix Released

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

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

Status in gnome-initial-setup package in Ubuntu:
  Fix Released

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

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

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

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

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

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

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

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

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

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

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

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


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


[Desktop-packages] [Bug 2050884] Re: Ubuntu Metrics server is not accepting reports

2024-04-10 Thread Nathan Teodosio
** Changed in: gnome-initial-setup (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu Metrics server is not accepting reports

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

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

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

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


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


[Desktop-packages] [Bug 2050884] Re: Ubuntu Metrics server is not accepting reports

2024-04-10 Thread Leó Kolbeinsson
Confirm this no longer present in Ubuntu Noble Desktop daily ISO dated
20240410

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

Title:
  Ubuntu Metrics server is not accepting reports

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

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

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

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


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


[Desktop-packages] [Bug 2058459] Re: [FFe] Replace cheese by gnome-snapshot in the desktop image

2024-04-10 Thread Sebastien Bacher
** Changed in: gnome-snapshot (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [FFe] Replace cheese by gnome-snapshot in the desktop image

Status in gnome-snapshot package in Ubuntu:
  Fix Released

Bug description:
  Replacing cheese by gnome-snapshot is on the desktop plans for this
  cycle but has been taking longer than expected (rust packaging
  complication + MIR delays). We got a +1 MIR review on the MIR bug
  #2052652 now and security team said they should have their review also
  done by the end of the week.

  The rational for the change is that cheese has been in low maintenance
  mode for years and is quite buggy. GNOME switched their default camera
  application in GNOME 45 (a cycle ago).

  It's also an oem team request since 22.04 to 'fix or replace" cheese
  since it has flaws which are problematic for hardware enablement. The
  fact that there was no action on fixing those problems since 22.04  is
  confirming that the project isn't really active anymore.

  gnome-shapshot is also using the current gtk4 version (which will make
  it more consistent with the other desktop applications, cheese is
  still using gtk3) and libcamera which is making it compatible with
  newer mipi/ipu6 cameras.

  The regression potential is limited since that's a standalone
  application mostly used to test the camera and do selfies and video
  recordings.

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


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


[Desktop-packages] [Bug 2037015] Re: Screen corruption of slides during install on Raspberry Pi

2024-04-10 Thread Daniel van Vugt
** Changed in: webkit2gtk (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Screen corruption of slides during install on Raspberry Pi

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  During the initial configuration of the Ubuntu Desktop for Raspberry
  Pi (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out
  and the process moves onto configuration, the "slide deck" that is
  usually displayed during the process appeared corrupted as if a
  horizontal stride were incorrectly set somewhere.

  I'm attached a photo of the screen (as, while I could take a
  screenshot during the process, it evidently wasn't saved somewhere
  persistent).

  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal
  stride causing "banding"), but I tested the embedded browser (via the
  help system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

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


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


[Desktop-packages] [Bug 2035304] Re: Ubuntu Dock briefly has a border and rounded corners when it restarts

2024-04-10 Thread Daniel van Vugt
Possible solutions in order of preference:

* Apply the extension's stylesheet before rendering the dock. That might
just fix it.

* Apply the same slide-in animation (after LP: #2058468) to unlocking
the screen.

** Tags added: noble

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Triaged

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

Title:
  Ubuntu Dock briefly has a border and rounded corners when it restarts

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

Bug description:
  Ubuntu Dock briefly has a border and rounded corners when it restarts
  (after VT switches or unlocking the screen). It looks like it takes a
  couple of frames to apply the correct appearance.

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


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


[Desktop-packages] [Bug 2052913] Re: [Xorg] Large performance regression in fullscreen windows

2024-04-10 Thread Daniel van Vugt
** Tags added: amd64

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

Title:
  [Xorg] Large performance regression in fullscreen windows

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble 
(gnome-shell 45.3-1ubuntu1)
  Default Ubuntu GNOME desktop environment used with no user added extensions.

  GPU driverstack identical between the two distros (eliminated as a variable).
  Linux kernel identical between distros (eliminated as a variable)
  CPU, GPU, and RAM clocks pinned to max.

  Test case: Minecraft Java Edition (shared drive with identical setup
  between Ubuntu versions). Fullscreen 1080p. Xorg display server.

  FPS (uncapped):
  Ubuntu Jammy: 177fps
  Ubuntu Noble: 140fps

  Observations:
  Ubuntu Jammy:
  gnome-shell process cpu% when camera is still: 0-1%
  gnome-shell process cpu% when camera is moving: 10-20%
  Memory Bandwidth (CPU and GPU shared): 40%

  Ubuntu Noble:
  gnome-shell process cpu% when camera is still: 20-55%
  gnome-shell process cpu% when camera is moving: 30-55%
  Memory Bandwidth (CPU and GPU shared): 50%

  In both cases GPU utilization is observed to be near 100%.

  So in summary, large performance regression regression which appears
  to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on
  ubuntu jammy when there the camera is still (even with a fps graph
  drawn onscreen) in stark contrast to ubuntu noble.

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


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


[Desktop-packages] [Bug 2060009] Re: mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

2024-04-10 Thread Timo Aaltonen
you probably meant "fixed in mesa 24.0.4"?

Anyway, we'll get that in the next merge after beta.

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

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

Title:
  mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

Status in mesa package in Ubuntu:
  In Progress

Bug description:
  With mesa 24.0.3-1ubuntu3 OpenSCAD does not work correctly on AMD GPUs.
  Cf. https://github.com/openscad/openscad/issues/5072

  According to OpenSCAD maintainers this was a bug in Mesa-24.0.4. Cf. 
https://docs.mesa3d.org/relnotes/24.0.4.html
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroRelease: Ubuntu 24.04
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/24.01.00, 6.8.0-11-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/24.01.00, 6.8.0-20-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2021-07-01 (1006 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: LENOVO 20KV0008GE
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-20-generic 
root=/dev/mapper/vgubuntu-root ro
  ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
  Tags: noble ubuntu regression reproducible
  Uname: Linux 6.8.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare 
sbuild sispmctl sudo
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 1.63
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET83W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KV0008GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.63
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET83W(1.63):bd02/08/2023:br1.63:efr1.63:svnLENOVO:pn20KV0008GE:pvrThinkPadE585:rvnLENOVO:rn20KV0008GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KV_BU_Think_FM_ThinkPadE585:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KV0008GE
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB

2024-04-10 Thread Daniel van Vugt
Something like that. To get the log from the latest boot I would use:

  journalctl -b0 > journal.txt

which seems to be almost the same as 'journalctl -xb'.

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

Title:
  gnome desktop cannot start as mutter fails to find drmModeCloseFB

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0:
  undefined symbol: drmModeCloseFB

  Package libdrm2: 
  i   2.4.120-2 noble 
500 

  Package libdrm2:i386:
  i   2.4.120-2 noble 
500 

  Package libmutter-14-0:
  i   46.0-1ubuntu6 noble 
500 

  Package mutter:
  i   46.0-1ubuntu6 noble 
500

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


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


[Desktop-packages] [Bug 2052913] Re: [Xorg] Large performance regression in fullscreen windows

2024-04-10 Thread Daniel van Vugt
I can reproduce this bug in Xorg sessions with Intel graphics. My
fullscreen benchmark results are about a quarter of what they should be
when mutter/gnome-shell is running. 4x performance is achieved by
running on a bare Xorg server without mutter/gnome-shell.

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

Title:
  [Xorg] Large performance regression in fullscreen windows

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble 
(gnome-shell 45.3-1ubuntu1)
  Default Ubuntu GNOME desktop environment used with no user added extensions.

  GPU driverstack identical between the two distros (eliminated as a variable).
  Linux kernel identical between distros (eliminated as a variable)
  CPU, GPU, and RAM clocks pinned to max.

  Test case: Minecraft Java Edition (shared drive with identical setup
  between Ubuntu versions). Fullscreen 1080p. Xorg display server.

  FPS (uncapped):
  Ubuntu Jammy: 177fps
  Ubuntu Noble: 140fps

  Observations:
  Ubuntu Jammy:
  gnome-shell process cpu% when camera is still: 0-1%
  gnome-shell process cpu% when camera is moving: 10-20%
  Memory Bandwidth (CPU and GPU shared): 40%

  Ubuntu Noble:
  gnome-shell process cpu% when camera is still: 20-55%
  gnome-shell process cpu% when camera is moving: 30-55%
  Memory Bandwidth (CPU and GPU shared): 50%

  In both cases GPU utilization is observed to be near 100%.

  So in summary, large performance regression regression which appears
  to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on
  ubuntu jammy when there the camera is still (even with a fps graph
  drawn onscreen) in stark contrast to ubuntu noble.

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


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


[Desktop-packages] [Bug 2060679] Re: No icons for gtk4 applications under noble

2024-04-10 Thread Sebastien Bacher
** Also affects: mesa (Ubuntu Noble)
   Importance: High
 Assignee: Timo Aaltonen (tjaalton)
   Status: In Progress

** Tags removed: rls-nn-incoming

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

Title:
  No icons for gtk4 applications under noble

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Noble:
  In Progress

Bug description:
  While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta,
  I noticed that all GTK4 applications appear to be missing various
  icons. All lack the minimize / maximize / close icons (which are left
  as three empty circles on the window), and others lack icons within
  the windows, e.g. on various controls like radio buttons, or folder
  icons in nautilus. GTK3 applications appear unaffected. I'll attach
  some screenshots demonstrating the issue.

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


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


[Desktop-packages] [Bug 2060806] Re: Update gstreamer to 1.24.2

2024-04-10 Thread Jeremy Bícha
** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: Triaged => In Progress

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Update gstreamer to 1.24.2

Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in gst-plugins-good1.0 package in Ubuntu:
  In Progress

Bug description:
  Yesterday, there was a new bugfix release in the stable 1.24.2 series.
  This bug is to track updates for Ubuntu 24.04 LTS.

  https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2060806/+subscriptions


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


[Desktop-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.4 to lower cpu and disk usage

2024-04-10 Thread Jeremy Bícha
** Changed in: upower (Ubuntu)
   Status: New => Triaged

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

** Tags added: noble upgrade-software-version

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

Title:
  Upgrade UPower to 1.90.4 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Triaged
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB

2024-04-10 Thread Erkin Alp Güney
Journal dump uploaded.

** Attachment added: "boot.log"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+attachment/5763348/+files/boot.log

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

Title:
  gnome desktop cannot start as mutter fails to find drmModeCloseFB

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0:
  undefined symbol: drmModeCloseFB

  Package libdrm2: 
  i   2.4.120-2 noble 
500 

  Package libdrm2:i386:
  i   2.4.120-2 noble 
500 

  Package libmutter-14-0:
  i   46.0-1ubuntu6 noble 
500 

  Package mutter:
  i   46.0-1ubuntu6 noble 
500

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


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


[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB

2024-04-10 Thread Erkin Alp Güney
The "symbol lookup error" happens regardless of what way it has been
started, even invoking "mutter --version" from the command line fails.

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

Title:
  gnome desktop cannot start as mutter fails to find drmModeCloseFB

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0:
  undefined symbol: drmModeCloseFB

  Package libdrm2: 
  i   2.4.120-2 noble 
500 

  Package libdrm2:i386:
  i   2.4.120-2 noble 
500 

  Package libmutter-14-0:
  i   46.0-1ubuntu6 noble 
500 

  Package mutter:
  i   46.0-1ubuntu6 noble 
500

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


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


[Desktop-packages] [Bug 2060534] Re: Thunderbird disk usage out of control

2024-04-10 Thread luca moscato
Seems a thunderbird bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1878541


** Bug watch added: Mozilla Bugzilla #1878541
   https://bugzilla.mozilla.org/show_bug.cgi?id=1878541

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

Title:
  Thunderbird disk usage out of control

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Environment: Thunderbird 124.0 64bits installed as SNAP on Ubuntu 22.04 LTS
  3 gmail imap account

  This (monday) morning Ubuntu notify me that I was running out of disk
  space, and while I was checking where the problem was, the disk
  analyzer told me the answer

  snap/thunderbird/common directory has a size of more than 360GB, pretty 
strange since my gmail account have 15GB and 30GB of quota (half used more or 
less)
  One of them is a shared one we use for notfication with almost 100k emails, 
flow is very high since with my team we receive emails, handle and archive them.

  I tryed to compact database, keep on disk only latest 90 days email
  but the sistem started to suffer issues due to no disk space so that I
  tried to remove that account and instantly more than 250GB of data on
  disk disappeared.

  Issue found and fixed but:
  - Thunderbird should NOT use so much disk space, some cleanup process MUST be 
implemented to keep disk usage under control, as I wrote system usage is 
impaired
  - Is this issue index-related? Since I do a lot of quick search on that 
account
  - Is something snap/linux related? Could be found also on Windows/Mac?
  - If someone needs logs, I'd be happy to provide them but I need instructions 
about how to retrieve them.

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


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


[Desktop-packages] [Bug 2060814] [NEW] dist-upgrade in noble fails when using TPM FDE

2024-04-10 Thread Ken VanDine
Public bug reported:

When doing a dist-upgrade of noble during the devel cycle I'm hitting
this upgrade bug in the package.  /lib/firmware is read-only because
it's provided by the pc-kernel snap.


Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libpoppler134 poppler-utils
The following packages will be upgraded:
  printer-driver-foo2zjs
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
416 not fully installed or removed.
Need to get 0 B/142 kB of archives.
After this operation, 12.3 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 140132 files and directories currently installed.)
Preparing to unpack .../printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb 
...
Unpacking printer-driver-foo2zjs (20200505dfsg0-2ubuntu5) over 
(20200505dfsg0-2ubuntu3) ...
dpkg: error processing archive 
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb 
(--unpack)
:
 error creating directory './lib/firmware/hp': Read-only file system
dpkg: error while cleaning up:
 unable to remove newly-extracted version of '/lib/firmware/hp': Read-only file 
system
Errors were encountered while processing:
 /var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: printer-driver-foo2zjs 20200505dfsg0-2ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr 10 09:39:01 2024
InstallationDate: Installed on 2024-03-08 (33 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: foo2zjs
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  dist-upgrade in noble fails when using TPM FDE

Status in foo2zjs package in Ubuntu:
  New

Bug description:
  When doing a dist-upgrade of noble during the devel cycle I'm hitting
  this upgrade bug in the package.  /lib/firmware is read-only because
  it's provided by the pc-kernel snap.

  
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
libpoppler134 poppler-utils
  The following packages will be upgraded:
printer-driver-foo2zjs
  1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
  416 not fully installed or removed.
  Need to get 0 B/142 kB of archives.
  After this operation, 12.3 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 140132 files and directories currently installed.)
  Preparing to unpack 
.../printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb ...
  Unpacking printer-driver-foo2zjs (20200505dfsg0-2ubuntu5) over 
(20200505dfsg0-2ubuntu3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb 
(--unpack)
  :
   error creating directory './lib/firmware/hp': Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of '/lib/firmware/hp': Read-only 
file system
  Errors were encountered while processing:
   
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: printer-driver-foo2zjs 20200505dfsg0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 10 09:39:01 2024
  InstallationDate: Installed on 2024-03-08 (33 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: foo2zjs
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: 

[Desktop-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.4 to lower cpu and disk usage

2024-04-10 Thread Jeremy Bícha
** Bug watch added: Debian Bug tracker #1068763
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068763

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

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

Title:
  Upgrade UPower to 1.90.4 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Triaged
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Desktop-packages] [Bug 2060813] Re: Upgrade UPower to 1.90.3 to lower cpu and disk usage

2024-04-10 Thread Jeremy Bícha
The Debian maintainer pointed out 1.90.3 is the same as 1.90.4 except
for the version change so 1.90.3 is good enough for the fix you are
wanting.

** Summary changed:

- Upgrade UPower to 1.90.4 to lower cpu and disk usage
+ Upgrade UPower to 1.90.3 to lower cpu and disk usage

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

Title:
  Upgrade UPower to 1.90.3 to lower cpu and disk usage

Status in upower package in Ubuntu:
  Triaged
Status in upower package in Debian:
  Unknown

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Desktop-packages] [Bug 2060009] Re: mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

2024-04-10 Thread Heinrich Schuchardt
** Description changed:

  With mesa 24.0.3-1ubuntu3 OpenSCAD does not work correctly on AMD GPUs.
  Cf. https://github.com/openscad/openscad/issues/5072
  
- According to OpenSCAD maintainers this was a bug in Mesa-24.0.4. Cf. 
https://docs.mesa3d.org/relnotes/24.0.4.html
- --- 
+ According to OpenSCAD maintainers this was a bug fixed in Mesa-24.0.4. Cf. 
https://docs.mesa3d.org/relnotes/24.0.4.html
+ ---
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroRelease: Ubuntu 24.04
  DistroVariant: ubuntu
  DkmsStatus:
-  fwts-efi-runtime-dkms/24.01.00, 6.8.0-11-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
-  fwts-efi-runtime-dkms/24.01.00, 6.8.0-20-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
+  fwts-efi-runtime-dkms/24.01.00, 6.8.0-11-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
+  fwts-efi-runtime-dkms/24.01.00, 6.8.0-20-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
  DpkgLog:
-  
+ 
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
+  Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2021-07-01 (1006 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
-  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
+  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: LENOVO 20KV0008GE
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-20-generic 
root=/dev/mapper/vgubuntu-root ro
  ProcVersionSignature: Ubuntu 6.8.0-20.20-generic 6.8.1
  Tags: noble ubuntu regression reproducible
  Uname: Linux 6.8.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare 
sbuild sispmctl sudo
  _MarkForUpload: True
  dmi.bios.date: 02/08/2023
  dmi.bios.release: 1.63
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET83W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KV0008GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.63
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET83W(1.63):bd02/08/2023:br1.63:efr1.63:svnLENOVO:pn20KV0008GE:pvrThinkPadE585:rvnLENOVO:rn20KV0008GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KV_BU_Think_FM_ThinkPadE585:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KV0008GE
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

Title:
  mesa 24.0.3-1ubuntu3 breaks OpenGL applications on amdgpu

Status in mesa package in Ubuntu:
  In Progress

Bug description:
  With mesa 24.0.3-1ubuntu3 OpenSCAD does not work correctly on AMD GPUs.
  Cf. https://github.com/openscad/openscad/issues/5072

  According to OpenSCAD 

[Desktop-packages] [Bug 2060806] [NEW] Update gstreamer to 1.24.2

2024-04-10 Thread Jeremy Bícha
Public bug reported:

Yesterday, there was a new bugfix release in the stable 1.24.2 series.
This bug is to track updates for Ubuntu 24.04 LTS.

https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Medium
 Status: Triaged

** Affects: gst-plugins-good1.0 (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: noble upgrade-software-version

** Also affects: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => Triaged

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Update gstreamer to 1.24.2

Status in gst-plugins-bad1.0 package in Ubuntu:
  Triaged
Status in gst-plugins-good1.0 package in Ubuntu:
  Triaged

Bug description:
  Yesterday, there was a new bugfix release in the stable 1.24.2 series.
  This bug is to track updates for Ubuntu 24.04 LTS.

  https://gstreamer.freedesktop.org/releases/1.24/#1.24.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2060806/+subscriptions


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


[Desktop-packages] [Bug 1991496] Re: Permission denied when trying to open a pdf file form Google Drive

2024-04-10 Thread Bug Watch Updater
** Changed in: evince
   Status: Unknown => New

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

Title:
  Permission denied when trying to open a pdf file form Google Drive

Status in Evince:
  New
Status in evince package in Ubuntu:
  Triaged

Bug description:
  I logged into Google Drive on Gnome Online Accounts, and I can access my 
Google Drive files from nautilus.
  However, when I try to open a pdf file from said folder, I can't open it. I 
get a "permission denied".

  Other files open fine. Okular is also able to open the pdf file.

  See attached screenshot with the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: evince 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  2 17:27:12 2022
  InstallationDate: Installed on 2022-02-02 (242 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: evince
  UpgradeStatus: Upgraded to kinetic on 2022-09-29 (3 days ago)

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


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


[Desktop-packages] [Bug 2060809] [NEW] davinci not opening bro

2024-04-10 Thread Mani P
Public bug reported:

gpu no to supporter

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.154.05_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.157-0ubuntu0.22.04.2_i386.deb
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 18:14:28 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation HD Graphics 530 [8086:2212]
InstallationDate: Installed on 2024-04-08 (1 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
MachineType: ZEBRONICS H110
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=f3ebdcea-9cba-4457-97c2-ffcbed104226 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2023
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.name: H110
dmi.board.vendor: ZEBRONICS
dmi.board.version: Ver:2.32
dmi.chassis.type: 3
dmi.chassis.vendor: ZEBRONICS
dmi.chassis.version: H110
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/11/2023:br5.12:svnZEBRONICS:pnH110:pvr:rvnZEBRONICS:rnH110:rvrVer2.32:cvnZEBRONICS:ct3:cvrH110:sku:
dmi.product.name: H110
dmi.sys.vendor: ZEBRONICS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  davinci not opening bro

Status in xorg package in Ubuntu:
  New

Bug description:
  gpu no to supporter

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.154.05_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.157-0ubuntu0.22.04.2_i386.deb
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:14:28 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 530 [8086:2212]
  InstallationDate: Installed on 2024-04-08 (1 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: ZEBRONICS H110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=f3ebdcea-9cba-4457-97c2-ffcbed104226 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2023
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.name: H110
  dmi.board.vendor: ZEBRONICS
  dmi.board.version: Ver:2.32
  dmi.chassis.type: 3
  dmi.chassis.vendor: ZEBRONICS
  dmi.chassis.version: H110
  dmi.modalias: 

[Desktop-packages] [Bug 2060814] Re: dist-upgrade in noble fails when using TPM FDE

2024-04-10 Thread Till Kamppeter
This means that /lib/firmware is repurposed, at least on some systems.

So no problem for me to move the firmware directory to /usr/lib or
/usr/share.

Questions is now, do we have a kernel Snap on standard *.deb-based
Ubuntu? If we had kernel Snaps only on Ubuntu Core (Desktop) there the
printer-driver-foo2zjs package does not make sense. We work with the
CUPS Snap on such systems and printer drivers work only in the new
Printer Application format. For the printers supported by foo2zjs one
would use the Ghostscript Printer Application.

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

Title:
  dist-upgrade in noble fails when using TPM FDE

Status in foo2zjs package in Ubuntu:
  New

Bug description:
  When doing a dist-upgrade of noble during the devel cycle I'm hitting
  this upgrade bug in the package.  /lib/firmware is read-only because
  it's provided by the pc-kernel snap.

  
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
libpoppler134 poppler-utils
  The following packages will be upgraded:
printer-driver-foo2zjs
  1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
  416 not fully installed or removed.
  Need to get 0 B/142 kB of archives.
  After this operation, 12.3 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 140132 files and directories currently installed.)
  Preparing to unpack 
.../printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb ...
  Unpacking printer-driver-foo2zjs (20200505dfsg0-2ubuntu5) over 
(20200505dfsg0-2ubuntu3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb 
(--unpack)
  :
   error creating directory './lib/firmware/hp': Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of '/lib/firmware/hp': Read-only 
file system
  Errors were encountered while processing:
   
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: printer-driver-foo2zjs 20200505dfsg0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 10 09:39:01 2024
  InstallationDate: Installed on 2024-03-08 (33 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: foo2zjs
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2060813] [NEW] Upgrade UPower to 1.90.4 to lower cpu and disk usage

2024-04-10 Thread ktecho
Public bug reported:

Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

Upower 1.90.4 has been released, which fixes an issue making some users
(maybe having Logitech devices and others) use more cpu and disk than
intended.

For me (I have Logitech mouse receiver), when I look at htop without
doing anything, I see upower appearing there as using CPU.

If the upgrade cannot be done at this stage, maybe the patch can be
added to 1.90.2 (the current version in the repository of 24.04):
https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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

** Package changed: apport (Ubuntu) => upower (Ubuntu)

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

Title:
  Upgrade UPower to 1.90.4 to lower cpu and disk usage

Status in upower package in Ubuntu:
  New

Bug description:
  Reference: https://www.phoronix.com/news/UPower-1.90.4-Released

  Upower 1.90.4 has been released, which fixes an issue making some
  users (maybe having Logitech devices and others) use more cpu and disk
  than intended.

  For me (I have Logitech mouse receiver), when I look at htop without
  doing anything, I see upower appearing there as using CPU.

  If the upgrade cannot be done at this stage, maybe the patch can be
  added to 1.90.2 (the current version in the repository of 24.04):
  https://gitlab.freedesktop.org/upower/upower/-/merge_requests/212

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


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


[Desktop-packages] [Bug 2050884] Re: Ubuntu Metrics server is not accepting reports

2024-04-10 Thread Nathan Teodosio
Corrado, the released fix was only for the consumer (gnome-initial-
setup).

I think that, if you chose to send system information to Canonical and
it failed, which is at the moment guaranteed to happen because the
service is not up yet, ubuntu-report schedules a new attempt to send the
report.

If that is ad infinitum or spams your system logs, please file a new bug
against ubuntu-report[1].

[1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+filebug.

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

Title:
  Ubuntu Metrics server is not accepting reports

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

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

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

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


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


[Desktop-packages] [Bug 1991496] Re: Permission denied when trying to open a pdf file form Google Drive

2024-04-10 Thread Jeremy Bícha
** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #1781
   https://gitlab.gnome.org/GNOME/evince/-/issues/1781

** Also affects: evince via
   https://gitlab.gnome.org/GNOME/evince/-/issues/1781
   Importance: Unknown
   Status: Unknown

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

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

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

Title:
  Permission denied when trying to open a pdf file form Google Drive

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  Triaged

Bug description:
  I logged into Google Drive on Gnome Online Accounts, and I can access my 
Google Drive files from nautilus.
  However, when I try to open a pdf file from said folder, I can't open it. I 
get a "permission denied".

  Other files open fine. Okular is also able to open the pdf file.

  See attached screenshot with the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: evince 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  2 17:27:12 2022
  InstallationDate: Installed on 2022-02-02 (242 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: evince
  UpgradeStatus: Upgraded to kinetic on 2022-09-29 (3 days ago)

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


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


[Desktop-packages] [Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble

2024-04-10 Thread Jeremy Bícha
** Changed in: gnome-keyring (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gnome-keyring package in Ubuntu:
  Triaged

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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


[Desktop-packages] [Bug 2050884] Re: Ubuntu Metrics server is not accepting reports

2024-04-10 Thread corrado venturini
after fix i see many messages about:
Apr 10 13:16:06 corrado-n9-nn-0410 systemd[1883]: Started ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 13:16:17 corrado-n9-nn-0410 systemd[2530]: Started ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 13:16:29 corrado-n9-nn-0410 systemd[1883]: Stopped ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 13:18:50 corrado-n9-nn-0410 systemd[2530]: Stopped ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 13:19:14 corrado-n9-nn-0410 systemd[1329]: Started ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 13:19:34 corrado-n9-nn-0410 systemd[1877]: Started ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 13:19:46 corrado-n9-nn-0410 systemd[1329]: Stopped ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 13:21:47 corrado-n9-nn-0410 systemd[1877]: Stopped ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 14:08:33 corrado-n9-nn-0410 systemd[1344]: Started ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 14:08:45 corrado-n9-nn-0410 systemd[1897]: Started ubuntu-report.path - 
Pending report trigger for Ubuntu Report.
Apr 10 14:08:57 corrado-n9-nn-0410 systemd[1344]: Stopped ubuntu-report.path - 
Pending report trigger for Ubuntu Report.

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

Title:
  Ubuntu Metrics server is not accepting reports

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

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

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

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


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


[Desktop-packages] [Bug 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git

2024-04-10 Thread Andreas Karlson
Till,
I have pushed another commit that fixes this regression.
https://github.com/OpenPrinting/cups/issues/934#issuecomment-2047651106

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

Title:
  cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported
  commits from 2.4.x git

Status in cups package in Ubuntu:
  In Progress

Bug description:
  While checking out the latest versions of cups (2.4.7-1.2ubuntu4 and 
2.4.7-1.2ubuntu5),
  I noticed that cupsd crashes consistently after closing my Firefox tab / 
window.
  The title of the crash (from the bug-report window) is "cupsd crashed with 
SIGSEGV in ???()"

  I'm running the noble-desktop-amd64.iso from 2024-03-25 after applying
  some updates from the noble and noble-proposed pockets.

  Reproduction steps:
  1. Open Firefox and manage CUPS on http://localhost:631
  2. Go to Administration -> Printers -> Add Printer and choose your printer
  3. Add your printer (I used the ipps:// protocol to manage the printer)
  4. After clicking the "Add printer" button, immediately close your Firefox tab
  5. cupsd will crash and Ubuntu will display a bug-report popup

  Versions:
  Firefox - 124.0.1-1 r4033
  CUPS - 2.4.7-1.2ubuntu5

  Printer:
  Lexmark MS415dn (supported)

  I am unable to reproduce this bug on versions prior to
  2.4.7-1.2ubuntu4 (Tried with 2.4.7-1.2ubuntu1 and 2.4.7-1.2ubuntu2).

  Versions 2.4.7-1.2ubuntu4 and 2.4.7-1.2ubuntu5 only backported commits from 
the 2.4.x upstream git branch, so I also opened an issue on GitHub:
  https://github.com/OpenPrinting/cups/issues/934

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


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


[Desktop-packages] [Bug 2060814] Re: dist-upgrade in noble fails when using TPM FDE

2024-04-10 Thread Ken VanDine
Yes, classic deb based ubuntu utilizing TPM FDE does use a snapped
kernel.  In fact, it boots ubuntu-core and pivots to classic.

ken@t14:~$ df -h /lib/firmware/
Filesystem  Size  Used Avail Use% Mounted on
/dev/loop1  328M  328M 0 100% /snap/pc-kernel/1669


** Changed in: foo2zjs (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  dist-upgrade in noble fails when using TPM FDE

Status in foo2zjs package in Ubuntu:
  New

Bug description:
  When doing a dist-upgrade of noble during the devel cycle I'm hitting
  this upgrade bug in the package.  /lib/firmware is read-only because
  it's provided by the pc-kernel snap.

  
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
libpoppler134 poppler-utils
  The following packages will be upgraded:
printer-driver-foo2zjs
  1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
  416 not fully installed or removed.
  Need to get 0 B/142 kB of archives.
  After this operation, 12.3 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 140132 files and directories currently installed.)
  Preparing to unpack 
.../printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb ...
  Unpacking printer-driver-foo2zjs (20200505dfsg0-2ubuntu5) over 
(20200505dfsg0-2ubuntu3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb 
(--unpack)
  :
   error creating directory './lib/firmware/hp': Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of '/lib/firmware/hp': Read-only 
file system
  Errors were encountered while processing:
   
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: printer-driver-foo2zjs 20200505dfsg0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 10 09:39:01 2024
  InstallationDate: Installed on 2024-03-08 (33 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: foo2zjs
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2060817] [NEW] gnome-initial-setup hardcoded to Ubuntu branding, not overridable

2024-04-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

gnome-initial-setup is hardcoded to Ubuntu branding but there is no way
to override. Whoever patched it did not check to see that it was also
seeded in Edubuntu before making this call.

This directly affects Edubuntu and is therefore a critical bug.

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


** Tags: iso-testing
-- 
gnome-initial-setup hardcoded to Ubuntu branding, not overridable
https://bugs.launchpad.net/bugs/2060817
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-initial-setup in Ubuntu.

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


[Desktop-packages] [Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil

2024-04-10 Thread Rodrigo Barbieri
** Also affects: ssl-cert (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Status in hplip package in Ubuntu:
  Fix Released
Status in ssl-cert package in Ubuntu:
  Fix Released
Status in hplip source package in Jammy:
  New
Status in ssl-cert source package in Jammy:
  New
Status in ssl-cert package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/990228:

  Package: openssl
  Version: 3.0.0~~alpha16-1
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: piuparts

  Hi,

  during a test with piuparts I noticed your package causes other package
  to fail installation/upgrading.

  From the attached log (scroll to the bottom...):

  ...
Setting up openssl (3.0.0~~alpha16-1) ...
Setting up libbsd0:amd64 (0.11.3-1) ...
Setting up readline-common (8.1-2) ...
Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ...
Setting up libgdbm6:amd64 (1.19-2) ...
Setting up postgresql-client-common (226) ...
Setting up libedit2:amd64 (3.1-20210522-1~exp1) ...
Setting up libreadline8:amd64 (8.1-2) ...
Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ...
Setting up libllvm11:amd64 (1:11.0.1-2) ...
Setting up ssl-cert (1.1.0+nmu1) ...
Could not create certificate. Openssl output was:
Generating a RSA private key

..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+

..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+
Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
-
Warning: No -copy_extensions given; ignoring any extensions in the request
Cannot write random bytes:
8022CB35777F:error:127A:random number generator:RAND_write_file:Not 
a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
dpkg: error processing package ssl-cert (--configure):
 installed ssl-cert package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of postgresql-common:
 postgresql-common depends on ssl-cert (>= 1.0.11); however:
  Package ssl-cert is not configured yet.
  ...

  Hmm, well, yes, /dev/urandom is not a regular file. It's a character
  device node.

  
  cheers,

  Andreas

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


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


[Desktop-packages] [Bug 2060817] Re: Either remove ubuntu welcome or override some text

2024-04-10 Thread Erich Eickmeyer
** No longer affects: edubuntu-meta (Ubuntu)

** Description changed:

- Ubuntu's new welcome app shows too much Ubuntu branding and doesn't help
- set-up Gnome Online Accounts as originally intended. We need to either
- remove it from the seed or rebrand it somehow.
+ gnome-initial-setup is hardcoded to Ubuntu branding but there is no way
+ to override. Whoever patched it did not check to see that it was also
+ seeded in Edubuntu before making this call.
+ 
+ This directly affects Edubuntu and is therefore a critical bug.

** Changed in: edubuntu-artwork (Ubuntu)
   Importance: Undecided => Critical

** Summary changed:

- Either remove ubuntu welcome or override some text
+ gnome-initial-setup hardcoded to Ubuntu branding, not overridable

** Package changed: edubuntu-artwork (Ubuntu) => gnome-initial-setup
(Ubuntu)

** Tags added: noble rls-nn-incoming

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

Title:
  gnome-initial-setup hardcoded to Ubuntu branding, not overridable

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

Bug description:
  gnome-initial-setup is hardcoded to Ubuntu branding but there is no
  way to override. Whoever patched it did not check to see that it was
  also seeded in Edubuntu before making this call.

  This directly affects Edubuntu and is therefore a critical bug.

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


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


[Desktop-packages] [Bug 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil

2024-04-10 Thread Rodrigo Barbieri
Apparently this is still happening in Jammy for some reason (maybe a
regression), as according to this [1] bug report claiming that this bug
is the cause of it.

This is the command that I run to hit it (doesn't need anything in
particular for the command to work, can run anywhere such as a fresh new
container):

mellon_create_metadata https://sp.10.5.100.3/mellon
https://sp.10.5.100.3/v3/OS-
FEDERATION/identity_providers/idp.10.5.100.2/protocols/saml2/auth/mellon

It fails silently to create the xml file that it should be creating. It
works fine in focal, but doesn't work in jammy.

Versions in jammy:
libapache2-mod-auth-mellon  0.18.0-1build1
apache2-bin 2.4.52-1ubuntu4.8
openssl 3.0.2-0ubuntu1.15
libssl3:amd64   3.0.2-0ubuntu1.15
libxmlsec1-openssl:amd641.2.33-1build2

versions in focal:
libapache2-mod-auth-mellon   0.16.0-1ubuntu0.1
apache2-bin  2.4.41-4ubuntu3.16
openssl  1.1.1f-1ubuntu2.22
libssl1.1:amd64  1.1.1f-1ubuntu2.22
libxmlsec1-openssl:amd64 1.2.28-2

[1] https://bugs.launchpad.net/ubuntu/+source/ssl-cert/+bug/2052795

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

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Status in hplip package in Ubuntu:
  Fix Released
Status in ssl-cert package in Ubuntu:
  Fix Released
Status in hplip source package in Jammy:
  New
Status in ssl-cert source package in Jammy:
  New
Status in ssl-cert package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/990228:

  Package: openssl
  Version: 3.0.0~~alpha16-1
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: piuparts

  Hi,

  during a test with piuparts I noticed your package causes other package
  to fail installation/upgrading.

  From the attached log (scroll to the bottom...):

  ...
Setting up openssl (3.0.0~~alpha16-1) ...
Setting up libbsd0:amd64 (0.11.3-1) ...
Setting up readline-common (8.1-2) ...
Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ...
Setting up libgdbm6:amd64 (1.19-2) ...
Setting up postgresql-client-common (226) ...
Setting up libedit2:amd64 (3.1-20210522-1~exp1) ...
Setting up libreadline8:amd64 (8.1-2) ...
Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ...
Setting up libllvm11:amd64 (1:11.0.1-2) ...
Setting up ssl-cert (1.1.0+nmu1) ...
Could not create certificate. Openssl output was:
Generating a RSA private key

..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+

..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+
Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
-
Warning: No -copy_extensions given; ignoring any extensions in the request
Cannot write random bytes:
8022CB35777F:error:127A:random number generator:RAND_write_file:Not 
a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
dpkg: error processing package ssl-cert (--configure):
 installed ssl-cert package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of postgresql-common:
 postgresql-common depends on ssl-cert (>= 1.0.11); however:
  Package ssl-cert is not configured yet.
  ...

  Hmm, well, yes, /dev/urandom is not a regular file. It's a character
  device node.

  
  cheers,

  Andreas

To manage notifications about this bug go to:

[Desktop-packages] [Bug 2060400] Re: Remmina crashes instantly when trying to open a remote session

2024-04-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Remmina crashes instantly when trying to open a remote session

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  I've been testing Noble for a couple of weeks and Remmina has not been
  working. Fully upto date with regards to updates now and it's still
  crashing.

  The initial windows comes up allowing you to select a session. The
  various preference dialogues seem to work but as soon as you try to
  initiate a remote session it crashes instantly.

  No crash is shown on the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: remmina 1.4.35+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 20:17:02 2024
  InstallationDate: Installed on 2024-03-25 (13 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04

2024-04-10 Thread Jeremy Bícha
*** This bug is a duplicate of bug 1949340 ***
https://bugs.launchpad.net/bugs/1949340

Please do not add comments here because this bug has been marked as a
duplicate of https://launchpad.net/bugs/1949340

Gabriel, please open a new bug for your issue. Bug 1949340 does not
affect Ubuntu 23.10.

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

Title:
  Save As Dialog Box does not get focus in Ubuntu 22.04

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When using a browser to right click a file and save as, the save as
  window does not get focus, which means you can't just type the name of
  the file you want, you have to force focus onto the window to use it
  by clicking it.

  This defeats the entire purpose of 2 built in features, 1 being the
  pre-selected original file name (since you can't rename until you re-
  aquire focus for that window, thereby undoing the pre-selection
  programmed in) and 2, the ability to quickly save the file with a
  keystroke.

  A side note to this, ubuntu-bug should have an option to report bugs
  with other WITHOUT having to specify a package. This is a bug in
  ubuntu-bug. Not a feature. Because we don't always know what
  package(s) are involved. This needs to be addressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.8
  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-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 07:55:24 2022
  InstallationDate: Installed on 2022-03-31 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04

2024-04-10 Thread Jeremy Bícha
*** This bug is a duplicate of bug 1949340 ***
https://bugs.launchpad.net/bugs/1949340

Oh I guess GTK3 is still affected so bug 1949340 would affect people
using desktops other than GNOME.

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

Title:
  Save As Dialog Box does not get focus in Ubuntu 22.04

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When using a browser to right click a file and save as, the save as
  window does not get focus, which means you can't just type the name of
  the file you want, you have to force focus onto the window to use it
  by clicking it.

  This defeats the entire purpose of 2 built in features, 1 being the
  pre-selected original file name (since you can't rename until you re-
  aquire focus for that window, thereby undoing the pre-selection
  programmed in) and 2, the ability to quickly save the file with a
  keystroke.

  A side note to this, ubuntu-bug should have an option to report bugs
  with other WITHOUT having to specify a package. This is a bug in
  ubuntu-bug. Not a feature. Because we don't always know what
  package(s) are involved. This needs to be addressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.8
  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-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 07:55:24 2022
  InstallationDate: Installed on 2022-03-31 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2060204] Re: Resolution drop on third monitor on USB C

2024-04-10 Thread Robby ROUDON
I downgraded successfully, I was able to do a weird manipulation (see below) 
and when I upgraded again the changes remained and it works with the last 
packages
Manipulation :
In the settings, 
I increased the resolution of the monitor A which was downgraded (I could not 
apply due to "hardware limitations")
I chose the second external monitor B, changed the resolutions and I was to 
apply the changes
At that point I had monitor A with the highest resolution and monitor B with a 
lower resolution
I changed again the resolution of monitor B (and only B) back to the highest 
and applied
Both monitors were back to maximum

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

Title:
  Resolution drop on third monitor on USB C

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a laptop with an integrated intel intel gpu, 2/3 days ago it was 
working fine; I have 1 monitor plugged with hdmi and the other one with USB-c
  Now, the one plugged with USB-C get a lower resolution 1024*768 (not 
changeable) if the HDMI is plugged at the same time (it works well if I only 
have the USB c plugged)
  Feel free to ask if you need information

  cat /var/log/apt/history.log (relevant lines)
  Start-Date: 2024-03-29  14:21:01
  Commandline: apt upgrade -y
  Requested-By: roudonro (1000)
  Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04)
  End-Date: 2024-03-29  14:21:15

  Start-Date: 2024-04-02  16:06:48
  Commandline: apt upgrade gnome-calendar
  Requested-By: roudonro (1000)
  Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 
(2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8)
  End-Date: 2024-04-02  16:06:51

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 09:15:15 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21]
  InstallationDate: Installed on 2024-03-27 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Dell Inc. Latitude 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0DPC2R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5520
  dmi.product.sku: 0A21
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 1838902] Re: GNOME Control Center hangs for some time when I add other keyboard in settings

2024-04-10 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: New => Fix Released

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

Title:
  GNOME Control Center hangs for some time when I add other keyboard in
  settings

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  But then the list of languages opens and I can choose needing variant.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.32.2-1ubuntu4
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  4 22:30:32 2019
  InstallationDate: Installed on 2019-08-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1990592] Re: Desktop environment fails to start

2024-04-10 Thread Brian Murray
This happened to me today with a Noble daily build - Ubuntu 24.04 LTS
"Noble Numbat" - Beta amd64 (20240410.2)

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

Title:
  Desktop environment fails to start

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  A fresh installation of the Kinetic daily image dated 20220920 fails
  to start the graphical environment when using the nouveau drivers and
  I'm only able to log in on the console. The system under test is using
  QEMU w/ GPU passthrough and an NVIDIA GeForce GTX 650 device.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xserver-xorg-video-nouveau 1:1.0.17-2build1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Thu Sep 22 16:39:27 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650] [3842:2652]
  InstallationDate: Installed on 2022-09-22 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220920)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-6.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-6.2
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.112-3ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.1.7-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1990592/+subscriptions


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


[Desktop-packages] [Bug 2060204] Re: Resolution drop on third monitor on USB C

2024-04-10 Thread Daniel van Vugt
** Tags added: regression-update

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Resolution drop on third monitor on USB C

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a laptop with an integrated intel intel gpu, 2/3 days ago it was 
working fine; I have 1 monitor plugged with hdmi and the other one with USB-c
  Now, the one plugged with USB-C get a lower resolution 1024*768 (not 
changeable) if the HDMI is plugged at the same time (it works well if I only 
have the USB c plugged)
  Feel free to ask if you need information

  cat /var/log/apt/history.log (relevant lines)
  Start-Date: 2024-03-29  14:21:01
  Commandline: apt upgrade -y
  Requested-By: roudonro (1000)
  Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04)
  End-Date: 2024-03-29  14:21:15

  Start-Date: 2024-04-02  16:06:48
  Commandline: apt upgrade gnome-calendar
  Requested-By: roudonro (1000)
  Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 
(2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8)
  End-Date: 2024-04-02  16:06:51

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 09:15:15 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21]
  InstallationDate: Installed on 2024-03-27 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Dell Inc. Latitude 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0DPC2R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5520
  dmi.product.sku: 0A21
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

2024-04-10 Thread Daniel van Vugt
Everyone should also pay attention to the date and time shown in the
output from 'journalctl -b0 | grep MetaSyncRing'. If you have installed
the PPA then we only care about timestamps after the PPA was installed
and after you logged in again to apply the change.

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  In Progress
Status in mutter source package in Mantic:
  In Progress
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Run: journalctl -b0 | grep MetaSyncRing
  4. Verify the above command does NOT show "MetaSyncRing" messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since the code
  being modified is only used with that driver.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2060809] Re: davinci not opening bro

2024-04-10 Thread Daniel van Vugt
The integrated GPU of your Intel i5-6400 is all that I can see, which
understandably may not be enough to run Davinci. What error do you see
exactly?

Also note that errors have been reported on your installation media,
probably meaning the USB drive used to install Ubuntu was faulty. You
may want to reinstall Ubuntu using a different thumb drive.


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

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

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

Title:
  davinci not opening bro

Status in Ubuntu:
  Incomplete

Bug description:
  gpu no to supporter

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.154.05_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.157-0ubuntu0.22.04.2_i386.deb
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:14:28 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 530 [8086:2212]
  InstallationDate: Installed on 2024-04-08 (1 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: ZEBRONICS H110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=f3ebdcea-9cba-4457-97c2-ffcbed104226 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2023
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.name: H110
  dmi.board.vendor: ZEBRONICS
  dmi.board.version: Ver:2.32
  dmi.chassis.type: 3
  dmi.chassis.vendor: ZEBRONICS
  dmi.chassis.version: H110
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/11/2023:br5.12:svnZEBRONICS:pnH110:pvr:rvnZEBRONICS:rnH110:rvrVer2.32:cvnZEBRONICS:ct3:cvrH110:sku:
  dmi.product.name: H110
  dmi.sys.vendor: ZEBRONICS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


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

2024-04-10 Thread Brian Murray
I believe this is Fixed by the following upload:

gnome-session (46.0-1ubuntu3) noble; urgency=medium

  * Fix failure in starting a Unity session due to the removal of the
--builtin/--systemd flags in 46~alpha-1ubuntu1.

 -- Simon Quigley   Tue, 09 Apr 2024 00:24:03 -0500

** Changed in: gnome-session (Ubuntu)
   Status: New => Fix Released

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

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

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  `gnome-session.service` has the following:

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

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

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

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

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

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

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

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

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


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


[Desktop-packages] [Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB

2024-04-10 Thread Daniel van Vugt
Thanks. Next please run:

  env > env.txt

and attach the resulting text file here.

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

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

Title:
  gnome desktop cannot start as mutter fails to find drmModeCloseFB

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0:
  undefined symbol: drmModeCloseFB

  Package libdrm2: 
  i   2.4.120-2 noble 
500 

  Package libdrm2:i386:
  i   2.4.120-2 noble 
500 

  Package libmutter-14-0:
  i   46.0-1ubuntu6 noble 
500 

  Package mutter:
  i   46.0-1ubuntu6 noble 
500

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


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


[Desktop-packages] [Bug 2060893] [NEW] Ubuntu logo on the login screen jumps up after selecting the user

2024-04-10 Thread Daniel van Vugt
Public bug reported:

Ubuntu logo on the login screen jumps up after selecting the user.

Be careful to avoid confusing this with bug 1872594.

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

** Affects: yaru-theme (Ubuntu)
 Importance: Medium
 Status: New


** Tags: flickerfreeboot noble

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Ubuntu logo on the login screen jumps up after selecting the user

Status in gnome-shell package in Ubuntu:
  New
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  Ubuntu logo on the login screen jumps up after selecting the user.

  Be careful to avoid confusing this with bug 1872594.

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


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


[Desktop-packages] [Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears (before selecting the user)

2024-04-10 Thread Daniel van Vugt
It got a bit worse in Noble recently so we should track that separately
in bug 2060893.

** Summary changed:

- Ubuntu logo shifts vertically when the login screen appears
+ Ubuntu logo shifts vertically when the login screen appears (before selecting 
the user)

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

Title:
  Ubuntu logo shifts vertically when the login screen appears (before
  selecting the user)

Status in Yaru Theme:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in plymouth package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
  Ubuntu logo shifts upward about 1px when the purple login screen
  appears.

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


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


[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

2024-04-10 Thread threadbareobserve
** Changed in: mutter (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Fix Released
Status in mutter source package in Mantic:
  In Progress
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Run: journalctl -b0 | grep MetaSyncRing
  4. Verify the above command does NOT show "MetaSyncRing" messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since the code
  being modified is only used with that driver.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2060898] [NEW] Trying to install gimp-help-en threatens to install wslu

2024-04-10 Thread Aaron Rainbolt
Public bug reported:

Filing this against ubuntu-meta since I believe this is a seed problem
that potentially affects all variants of Ubuntu (flavors or otherwise).

wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
such as for converting Linux paths to a Windows paths or creating Linux
application shortcuts on the Windows 10 Desktop." Obviously this package
should *never* be installed on a desktop or even on most VMs, but only
within WSL instances. However...

wslu provides the virtual package www-browser, as one of its features is
to open links in Windows 10 using the default browser set there. This
means that if a package depends or recommends www-browser, it may
attempt to pull in one of several packages, wslu included. In the past,
this hasn't been a problem because Firefox was present on all flavor
images, and Firefox provides www-browser as well. However, now that
Firefox is a Snap, it is possible for Firefox to be installed without
the firefox transitional apt package being installed. (This is the case
in a default installation of Kubuntu Noble Beta.) As it turns out,
Kubuntu Noble Beta ships with *no* packages that provide www-browser,
meaning that any package that depends on it will have to install a new
browser.

Due to some stroke of misfortune, apt is picking wslu out of all
packages as the package for this use case. Installing gimp-help-en will
also install www-browser, which results in wslu becoming installed.

wslu causes quite a few problems when installed on a desktop system -
among them, the syslog is spammed with errors due to the system not in
fact being a WSL VM, audio breaks in weird ways, and application
launchers sometimes fail. Why this happens is unclear, but the issues
appear to resolve once wslu is removed from the system. It is therefore
probably a good idea to avoid wslu becoming installed on accident in
this way.

Probably the best way to resolve this is to ensure that some package
that provides www-browser is available on every Ubuntu image. This could
be done via seeding or by adding a package to ubuntu-minimal.
Alternatively, wslu could be set to no longer provide www-browser,
though it's unclear if that would break its functionality.

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

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

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

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in ubuntu-meta package in Ubuntu:
  New
Status in wslu package in Ubuntu:
  New

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no 

[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

2024-04-10 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Jammy)
   Status: Fix Released => In Progress

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

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  In Progress
Status in mutter source package in Mantic:
  In Progress
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Run: journalctl -b0 | grep MetaSyncRing
  4. Verify the above command does NOT show "MetaSyncRing" messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since the code
  being modified is only used with that driver.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2060893] Re: Ubuntu logo on the login screen jumps up after selecting the user

2024-04-10 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Ubuntu logo on the login screen jumps up after selecting the user

Status in gnome-shell package in Ubuntu:
  New
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  Ubuntu logo on the login screen jumps up after selecting the user.

  Be careful to avoid confusing this with bug 1872594.

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


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


[Desktop-packages] [Bug 2060204] Re: Resolution drop on third monitor on USB C

2024-04-10 Thread Kai-Heng Feng
Sorry I don't quite follow. Does that mean the issue goes away after
downgrade and upgrade? Does USB-C display resolution can be changed now?

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

Title:
  Resolution drop on third monitor on USB C

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a laptop with an integrated intel intel gpu, 2/3 days ago it was 
working fine; I have 1 monitor plugged with hdmi and the other one with USB-c
  Now, the one plugged with USB-C get a lower resolution 1024*768 (not 
changeable) if the HDMI is plugged at the same time (it works well if I only 
have the USB c plugged)
  Feel free to ask if you need information

  cat /var/log/apt/history.log (relevant lines)
  Start-Date: 2024-03-29  14:21:01
  Commandline: apt upgrade -y
  Requested-By: roudonro (1000)
  Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04)
  End-Date: 2024-03-29  14:21:15

  Start-Date: 2024-04-02  16:06:48
  Commandline: apt upgrade gnome-calendar
  Requested-By: roudonro (1000)
  Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 
(2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8)
  End-Date: 2024-04-02  16:06:51

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 09:15:15 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21]
  InstallationDate: Installed on 2024-03-27 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Dell Inc. Latitude 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0DPC2R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5520
  dmi.product.sku: 0A21
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Desktop-packages] [Bug 2060799] Re: no ubuntu's parameter is found

2024-04-10 Thread Daniel van Vugt
Thanks for the bug report. Can you explain in more detail what you mean?

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

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

Title:
  no ubuntu's parameter is found

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

Bug description:
  There is not any found ubuntu's parameter

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 12:53:12 2024
  InstallationDate: Installed on 2023-09-18 (205 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2024-03-25 (16 days ago)

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


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


[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program

2024-04-10 Thread Mikhail Medvedev
Linux Mint 21.3 XFCE - 
I fully confirm the words "I used to use the Ctrl-Shift combination to switch 
keyboard layouts (ru <--> us)
but in this case I can't use any of the Ctrl-Shift-* hotkeys in any programme I 
try."

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  Won't Fix
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions


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


[Desktop-packages] [Bug 2049988] Re: Latest kernel kills wifi.

2024-04-10 Thread Patrick M
Any news on this?

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

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+subscriptions


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


[Desktop-packages] [Bug 2060898] Re: Trying to install gimp-help-en threatens to install wslu

2024-04-10 Thread Aaron Rainbolt
** Also affects: ubuntu-meta (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: wslu (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu Noble)
Milestone: None => ubuntu-24.04

** Changed in: wslu (Ubuntu Noble)
Milestone: None => ubuntu-24.04

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

Title:
  Trying to install gimp-help-en threatens to install wslu

Status in ubuntu-meta package in Ubuntu:
  New
Status in wslu package in Ubuntu:
  New
Status in ubuntu-meta source package in Noble:
  New
Status in wslu source package in Noble:
  New

Bug description:
  Filing this against ubuntu-meta since I believe this is a seed problem
  that potentially affects all variants of Ubuntu (flavors or
  otherwise).

  wslu is "a collection of utilities for the Windows 10 Linux Subsystem,
  such as for converting Linux paths to a Windows paths or creating
  Linux application shortcuts on the Windows 10 Desktop." Obviously this
  package should *never* be installed on a desktop or even on most VMs,
  but only within WSL instances. However...

  wslu provides the virtual package www-browser, as one of its features
  is to open links in Windows 10 using the default browser set there.
  This means that if a package depends or recommends www-browser, it may
  attempt to pull in one of several packages, wslu included. In the
  past, this hasn't been a problem because Firefox was present on all
  flavor images, and Firefox provides www-browser as well. However, now
  that Firefox is a Snap, it is possible for Firefox to be installed
  without the firefox transitional apt package being installed. (This is
  the case in a default installation of Kubuntu Noble Beta.) As it turns
  out, Kubuntu Noble Beta ships with *no* packages that provide www-
  browser, meaning that any package that depends on it will have to
  install a new browser.

  Due to some stroke of misfortune, apt is picking wslu out of all
  packages as the package for this use case. Installing gimp-help-en
  will also install www-browser, which results in wslu becoming
  installed.

  wslu causes quite a few problems when installed on a desktop system -
  among them, the syslog is spammed with errors due to the system not in
  fact being a WSL VM, audio breaks in weird ways, and application
  launchers sometimes fail. Why this happens is unclear, but the issues
  appear to resolve once wslu is removed from the system. It is
  therefore probably a good idea to avoid wslu becoming installed on
  accident in this way.

  Probably the best way to resolve this is to ensure that some package
  that provides www-browser is available on every Ubuntu image. This
  could be done via seeding or by adding a package to ubuntu-minimal.
  Alternatively, wslu could be set to no longer provide www-browser,
  though it's unclear if that would break its functionality.

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


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


[Desktop-packages] [Bug 2060204] Re: Resolution drop on third monitor on USB C

2024-04-10 Thread Daniel van Vugt
I think I misread comment #8. It sounds like a workaround has been
found, but perhaps there's still a regression?

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

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

Title:
  Resolution drop on third monitor on USB C

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop with an integrated intel intel gpu, 2/3 days ago it was 
working fine; I have 1 monitor plugged with hdmi and the other one with USB-c
  Now, the one plugged with USB-C get a lower resolution 1024*768 (not 
changeable) if the HDMI is plugged at the same time (it works well if I only 
have the USB c plugged)
  Feel free to ask if you need information

  cat /var/log/apt/history.log (relevant lines)
  Start-Date: 2024-03-29  14:21:01
  Commandline: apt upgrade -y
  Requested-By: roudonro (1000)
  Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04)
  End-Date: 2024-03-29  14:21:15

  Start-Date: 2024-04-02  16:06:48
  Commandline: apt upgrade gnome-calendar
  Requested-By: roudonro (1000)
  Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 
(2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8)
  End-Date: 2024-04-02  16:06:51

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 09:15:15 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21]
  InstallationDate: Installed on 2024-03-27 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Dell Inc. Latitude 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0DPC2R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5520
  dmi.product.sku: 0A21
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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