[Desktop-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

2024-03-08 Thread Zalán Hári
I did not try that and I hope that I will not need to, but sudo apt
install systemd-resolved seems to be much better.

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

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half our to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

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


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


[Desktop-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half our to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

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


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


[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-03-08 Thread Guy Schlosser
I am seeing this also, as of updating all packages, about fifteen
minutes ago. Is there a definite fix released? This doesn't mean we have
to resort to using firefox from snap, right?

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in geary package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Confirmed
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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


[Desktop-packages] [Bug 2056609] [NEW] right-click and "extract here" does not give the same result as clicking into the tar.gz and hitting "extract"

2024-03-08 Thread carlos
Public bug reported:

right-click and "extract here" does not give the same result as clicking
into the tar.gz and hitting "extract".

I have a tar.gz file where if I run "tar -xzvf " I get a file
that is 30 GB in size.

Similarly, if I double left-click on the file, and click "extract" on
the top left, then it extracts to about 30 GB.

However, if I extract the same file by right clicking on it and hitting
"extract here", I get an output that is about 5GB in size.

If needed I can provide the file. Just contact me via email:
carlos.gonza...@pivotal.aero


Doubt it's relevant, but the file is an image built using yocto.

Ubuntu version:
ubuntu@Latitude-3590:~/Downloads$ lsb_release -rd
Description:Ubuntu 22.04.4 LTS
Release:22.04

File roller version:
ubuntu@Latitude-3590:~/Downloads$ apt-cache policy file-roller
file-roller:
  Installed: 3.42.0-1
  Candidate: 3.42.0-1
  Version table:
 *** 3.42.0-1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status


lscpu output:
ubuntu@Latitude-3590:~/Downloads$ lscpu
Architecture:x86_64
  CPU op-mode(s):32-bit, 64-bit
  Address sizes: 39 bits physical, 48 bits virtual
  Byte Order:Little Endian
CPU(s):  8
  On-line CPU(s) list:   0-7
Vendor ID:   GenuineIntel
  Model name:Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
CPU family:  6
Model:   142
Thread(s) per core:  2
Core(s) per socket:  4
Socket(s):   1
Stepping:10
CPU max MHz: 4000.
CPU min MHz: 400.
BogoMIPS:3999.93
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bt
 s rep_good nopl xtopology nonstop_tsc cpuid aperfmperf 
pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm 
pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_t
 imer aes xsave avx f16c rdrand lahf_lm abm 
3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp 
tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 sme
 p bmi2 erms invpcid mpx rdseed adx smap clflushopt 
intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify 
hwp_act_window hwp_epp vnmi md_clear flush_l1d arch_capa
 bilities
Virtualization features: 
  Virtualization:VT-x
Caches (sum of all): 
  L1d:   128 KiB (4 instances)
  L1i:   128 KiB (4 instances)
  L2:1 MiB (4 instances)
  L3:8 MiB (1 instance)
NUMA:
  NUMA node(s):  1
  NUMA node0 CPU(s): 0-7
Vulnerabilities: 
  Gather data sampling:  Mitigation; Microcode
  Itlb multihit: KVM: Mitigation: VMX disabled
  L1tf:  Mitigation; PTE Inversion; VMX conditional cache 
flushes, SMT vulnerable
  Mds:   Mitigation; Clear CPU buffers; SMT vulnerable
  Meltdown:  Mitigation; PTI
  Mmio stale data:   Mitigation; Clear CPU buffers; SMT vulnerable
  Retbleed:  Mitigation; IBRS
  Spec rstack overflow:  Not affected
  Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:Mitigation; usercopy/swapgs barriers and __user 
pointer sanitization
  Spectre v2:Mitigation; IBRS, IBPB conditional, STIBP conditional, 
RSB filling, PBRSB-eIBRS Not affected
  Srbds: Mitigation; Microcode
  Tsx async abort:   Not affected

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: file-roller 3.42.0-1
ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  8 14:33:34 2024
InstallationDate: Installed on 2024-03-07 (1 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: file-roller
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  right-click and "extract here" does not give the same result as
  clicking into the tar.gz and hitting "extract"

Status in file-roller package in Ubuntu:
  New

Bug description:
  right-click and "extract here" does not give the 

[Desktop-packages] [Bug 2056607] Re: tracker-extract-3 crashed with SIGSYS in epoll_wait()

2024-03-08 Thread Apport retracing service
Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!


** Changed in: tracker-miners (Ubuntu)
   Status: New => Invalid

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2056607/+attachment/5754188/+files/CoreDump.gz

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract-3 crashed with SIGSYS in epoll_wait()

Status in tracker-miners package in Ubuntu:
  Invalid

Bug description:
  Testing of Edubuntu 20240308.1 Noble.
  Live session opened for the installer. System reported an unexpected error.
  Apport started for data collection.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: tracker-extract 3.4.6-3
  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
  CasperVersion: 1.494
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 21:51:03 2024
  ExecutablePath: /usr/libexec/tracker-extract-3
  LiveMediaBuild: Edubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240308.1)
  ProcCmdline: /usr/libexec/tracker-extract-3
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 31
  SignalName: SIGSYS
  SourcePackage: tracker-miners
  StacktraceTop:
   epoll_wait (epfd=7, events=0x7213b69ff11c, maxevents=1, timeout=0) at 
../sysdeps/unix/sysv/linux/epoll_wait.c:30
   ?? () from /lib/x86_64-linux-gnu/libmount.so.1
   mnt_monitor_get_fd () from /lib/x86_64-linux-gnu/libmount.so.1
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: tracker-extract-3 crashed with SIGSYS in epoll_wait()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

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


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


[Desktop-packages] [Bug 2056591] Re: [UIFe] Noble Flavor Wallpapers

2024-03-08 Thread Steve Langasek
The UI Freeze exists to ensure that documentation team and translation
team efforts aren't wasted working on a UI that isn't finalized.

https://wiki.ubuntu.com/FreezeExceptionProcess#UserInterfaceFreeze_Exceptions

UIFreeze granted, provided you notify ubuntu-...@lists.ubuntu.com in
advance.

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Triaged

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

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


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


[Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap

2024-03-08 Thread Heinrich Schuchardt
The same error reoccurred on an arm64 system.
None of two profiles was copied to  ~/snap/thunderbird/common/.thunderbird/. 
Instead a new one was created.

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

Title:
  Thunderbird profile not migrated to snap

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Today's update installed the thunderbird snap and removed the
  thunderbird binary but it did not migrate my thunderbird profile.

  Now I don't have access to any old mails anymore.

  Looking at ~/.thunderbird:

  $ cat profiles.ini 
  [Profile1]
  Name=default
  IsRelative=1
  Path=ao6t0qef.default
  Default=1

  [InstallFDC34C9F024745EB]
  Default=ji04wv64.default-release
  Locked=1

  [Profile0]
  Name=default-release
  IsRelative=1
  Path=ji04wv64.default-release

  [General]
  StartWithLastProfile=1
  Version=2

  
  ji04wv64.default-release is the folder that should have been migrated.

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


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


[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

2024-03-08 Thread Miguel
Sergio any news about this?

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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


[Desktop-packages] [Bug 2056079] Re: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

2024-03-08 Thread Mario Kleiner
Technically this bug belongs to the pulseaudio package in Ubuntu, not
pipewire, but the bug tracker does not let me file a bug against
pulseaudio.

** Tags added: pipewire pulseaudio

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

Title:
  Serious playback timing problems affecting GStreamer and other
  pulseaudio and pipewire audio clients

Status in gst-plugins-good:
  New
Status in PipeWire:
  Fix Released
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 release, to the outdated Pulseaudio
  16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client is affected, even if pipewire is used as
  desktop sound server in recent Ubuntu releases, given that many audio
  applications still access pipewire via its pulseaudio frontend
  (package pipewire-pulse). See pipewire bug
  https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

  The bug in libpulse.so.0, reported against Pulseaudio 16 in
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
  been fixed for the Pulseaudio 17 release.

  See the following merge request for the following trivial one-liner
  patch that would need to be backported to Ubuntu's current
  implementation:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

  I hoped that Pulseaudio 17 would be included in Debian in time for
  integration into Ubuntu 24.04-LTS, but apparently not much maintenance
  of pulseaudio is happening on the Debian side at the moment.

  Given that this bug affects all Ubuntu versions since Ubuntu
  22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio
  15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at
  least for the upcoming 24.04-LTS.

  Alternatively it would have been great to get Pulseaudio upgraded to
  version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
  apparently that is too late now, according to
  https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

  Thanks,
  -mario

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/2056079/+subscriptions


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


[Desktop-packages] [Bug 2056591] [NEW] [UIFe] Noble Flavor Wallpapers

2024-03-08 Thread Philipp Kewisch
Public bug reported:

I am requesting a blanket UI Freeze exception for all flavor wallpaper
packages in advance of the upcoming UI Freeze for a period of 5 days
after it starts. The Noble wallpapers for vanilla Ubuntu will be
available on March 18th, which only gives flavors 2 days to create their
customized wallpapers.

This is a very tight deadline, and we'd like to avoid putting the burden
on flavors to request individual UIFe's or forcing them to rush update
their wallpaper to make the deadline.

I'd appreciate your support on granting this exception.

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

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

Title:
  [UIFe] Noble Flavor Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  I am requesting a blanket UI Freeze exception for all flavor wallpaper
  packages in advance of the upcoming UI Freeze for a period of 5 days
  after it starts. The Noble wallpapers for vanilla Ubuntu will be
  available on March 18th, which only gives flavors 2 days to create
  their customized wallpapers.

  This is a very tight deadline, and we'd like to avoid putting the
  burden on flavors to request individual UIFe's or forcing them to rush
  update their wallpaper to make the deadline.

  I'd appreciate your support on granting this exception.

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


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


[Desktop-packages] [Bug 2056590] [NEW] No physical sound through speakers, settings show sound.

2024-03-08 Thread Thomas Raes
Public bug reported:

Running a dual boot configuration with windows 11 and ubuntu 22.04 LTS.
Bluetooth headset does not give problems.
Microphone works, but bad quality.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-compute-525_525.147.05-0ubuntu0.22.04.1_amd64.deb
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  8 18:11:08 2024
InstallationDate: Installed on 2024-02-28 (9 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/02/2023
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UM3504DA.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UM3504DA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3504DA.307:bd10/02/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook 15 UM3504DA_UM3504DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-08T12:53:04.511698

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  No physical sound through speakers, settings show sound.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Running a dual boot configuration with windows 11 and ubuntu 22.04 LTS.
  Bluetooth headset does not give problems.
  Microphone works, but bad quality.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-compute-525_525.147.05-0ubuntu0.22.04.1_amd64.deb
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 18:11:08 2024
  InstallationDate: Installed on 2024-02-28 (9 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2023
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UM3504DA.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UM3504DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3504DA.307:bd10/02/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook 15 UM3504DA_UM3504DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-08T12:53:04.511698

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


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


[Desktop-packages] [Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano
I did a rollback on the package gnome-shell-extension-ubuntu-dock to the
version 87ubuntu2 and did work. Closing the applications using the
right-button menu in the dock doesn't crash the session anymore.

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

Title:
  GNOME Shell crashes when I close any application

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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


[Desktop-packages] [Bug 2056575] Re: tracker-extract-3 crashed with SIGSYS in epoll_wait()

2024-03-08 Thread Apport retracing service
Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!


** Changed in: tracker-miners (Ubuntu)
   Status: New => Invalid

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2056575/+attachment/5754070/+files/CoreDump.gz

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract-3 crashed with SIGSYS in epoll_wait()

Status in tracker-miners package in Ubuntu:
  Invalid

Bug description:
  Daily  20240308

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: tracker-extract 3.4.6-3
  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
  CasperVersion: 1.494
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 15:45:30 2024
  ExecutablePath: /usr/libexec/tracker-extract-3
  LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
  ProcCmdline: /usr/libexec/tracker-extract-3
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 31
  SignalName: SIGSYS
  SourcePackage: tracker-miners
  StacktraceTop:
   epoll_wait (epfd=7, events=0x71b7f6bff11c, maxevents=1, timeout=0) at 
../sysdeps/unix/sysv/linux/epoll_wait.c:30
   ?? () from /lib/x86_64-linux-gnu/libmount.so.1
   mnt_monitor_get_fd () from /lib/x86_64-linux-gnu/libmount.so.1
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: tracker-extract-3 crashed with SIGSYS in epoll_wait()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

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


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


[Desktop-packages] [Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano
-- 
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/2056506

Title:
  GNOME Shell crashes when I close any application

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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


[Desktop-packages] [Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano
I confess I used to use noble-proposed enabled globally, but I disabled
it and downgraded all the packages that I could find that came from that
archive.

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

Title:
  GNOME Shell crashes when I close any application

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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


[Desktop-packages] [Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano
I finally was able to upload a crash report for gnome-shell:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056568

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

Title:
  GNOME Shell crashes when I close any application

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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


[Desktop-packages] [Bug 2056561] Re: Libc6 bug in gvfs-udisk

2024-03-08 Thread Simon Chopin
Unless I'm missing something, the issue you're linking is about glib,
not glibc. Reassigning the bug accordingly.

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

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

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

Title:
  Libc6 bug in gvfs-udisk

Status in glib2.0 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  Invalid

Bug description:
  Hi,

  Please see https://gitlab.gnome.org/GNOME/glib/-/issues/3168, which is
  a result of https://gitlab.gnome.org/GNOME/glib/-/issues/3168, which
  is fixed but needs a backport or something.

  Thanks,

  tg

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libc6 2.38-1ubuntu6.1
  ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Fri Mar  8 15:15:39 2024
  Dependencies:
   gcc-13-base 13.2.0-4ubuntu3
   libc6 2.38-1ubuntu6.1
   libgcc-s1 13.2.0-4ubuntu3
   libidn2-0 2.3.4-1
   libunistring2 1.0-2
  InstallationDate: Installed on 2022-12-08 (456 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: glibc
  UpgradeStatus: Upgraded to mantic on 2023-10-01 (159 days ago)

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


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


[Desktop-packages] [Bug 1930145] Re: IBus Panel Show Icon on system tray doesn't persist

2024-03-08 Thread Scarlett Gately Moore
This bug is very old, if it is still an issue please update the bug with
information from a supported release.

** Changed in: plasma-desktop (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  IBus Panel Show Icon on system tray doesn't persist

Status in ibus package in Ubuntu:
  Incomplete
Status in plasma-desktop package in Ubuntu:
  Incomplete

Bug description:
  After a reboot in Kubuntu 21.04 (and 20.10) the IBus Panel icon
  appears in the system tray despite "Show icon on system tray" NOT
  being checked.  Right clicking on the IBus Panel icon, checking "Show
  icon on system tray" and then unchecking again it causes the icon to
  be correctly hidden.  But the problem reappears after the next reboot.

  Another user reporting what is almost certainly the same behavior:
  https://www.reddit.com/r/kde/comments/j91t8f/ibus_panel_icon_in_system_tray/

  And this is an _identical_ bug report from 2012, so maybe it's a regression 
of some sort?
  https://bugzilla.redhat.com/show_bug.cgi?id=877135

  Based om the trouble shooting requested at that time I get:

  $ gconftool-2 --get /desktop/ibus/panel/show_icon_on_systray
  No value set for `/desktop/ibus/panel/show_icon_on_systray'

  Note that I am running KDE, in case that's the important detail.

  The primary problem is that if you click on it accidentally and close
  the panel, you lose all keyboard input.

  $ lsb_release -rd
  Description:Ubuntu 21.04
  Release:21.04
  $ apt-cache policy ibus
  ibus:
Installed: 1.5.24-1
Candidate: 1.5.24-1
Version table:
   *** 1.5.24-1 500
  500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

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


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


[Desktop-packages] [Bug 2056557] [NEW] Software & Updates does not currently work in 24.04

2024-03-08 Thread XA Hydra
Public bug reported:

Unable to run "Software & Updates" from either the app menu nor Synaptic
via Settings -> Repositories. The following error is generated:

Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  
^^^
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
self.backup_sourceslist()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
 ^^
  File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, in 
__init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
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: Fri Mar  8 08:56:53 2024
InstallationDate: Installed on 2023-11-02 (127 days ago)
InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231101)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Software & Updates does not currently work in 24.04

Status in software-properties package in Ubuntu:
  New

Bug description:
  Unable to run "Software & Updates" from either the app menu nor
  Synaptic via Settings -> Repositories. The following error is
  generated:

  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  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: Fri Mar  8 08:56:53 2024
  InstallationDate: Installed on 2023-11-02 (127 days ago)
  InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231101)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2056556] [NEW] apt-add-repository incorrectly forces lowercase

2024-03-08 Thread Malcolm Scott
Public bug reported:

I have a local APT repository with a non-lowercase suite identifier.
apt-add-repository always forces it into lowercase, which causes apt to
emit warnings when it notices the mismatch:

$ sudo apt-add-repository "deb http://example.com/deb FooBar Baz"
Repository: 'deb http://example.com/ foobar Baz'
Description:
Archive for codename: foobar components: Baz
More info: http://example.com/
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
(...)
$ sudo apt update
(...)
W: Conflicting distribution: http://example.com/deb foobar InRelease (expected 
foobar but got FooBar)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  apt-add-repository incorrectly forces lowercase

Status in software-properties package in Ubuntu:
  New

Bug description:
  I have a local APT repository with a non-lowercase suite identifier.
  apt-add-repository always forces it into lowercase, which causes apt
  to emit warnings when it notices the mismatch:

  $ sudo apt-add-repository "deb http://example.com/deb FooBar Baz"
  Repository: 'deb http://example.com/ foobar Baz'
  Description:
  Archive for codename: foobar components: Baz
  More info: http://example.com/
  Adding repository.
  Press [ENTER] to continue or Ctrl-c to cancel.
  (...)
  $ sudo apt update
  (...)
  W: Conflicting distribution: http://example.com/deb foobar InRelease 
(expected foobar but got FooBar)

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


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


[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

2024-03-08 Thread Dexter
Is there any known workaround for the spotify breakage? It has been
broken for quite a while now...

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

Title:
  Hardware acceleration broken for amdgpu/mesa in snap

Status in ubuntu-spotify-app:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Snap packages which use hardware accelerated graphics are broken after
  the last routine system upgrade via apt. My system is using AMD Radeon
  RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
  Two snap packages which are now unusable are Mozilla Firefox and
  Chromium browsers. Both display animated speckled color garbage inside
  their windows, overlayed with the correct image. Disabling hardware
  acceleration in the settings for the snap version of Firefox fixed it.
  Also, Firefox version installed from the original Mozilla tarball into
  /opt/ works just fine with the acceleration enabled on the same
  system, as well as glmark2 benchmark. Looks like the issue is only
  affecting snap packages.

  $ snap list firefox chromium
  Name  Version Rev   Tracking   Publisher   Notes
  chromium  109.0.5414.119  2295  latest/stable  canonical✓  -
  firefox   109.0.1-1   2311  latest/stable  mozilla✓-

  $ dpkg -l snapd|grep ^ii
  ii  snapd  2.58+22.10   amd64Daemon and tooling that enable 
snap packages

  $ dpkg -l mesa\* | grep ^ii
  ii  mesa-utils8.5.0-1   amd64Miscellaneous 
Mesa utilities -- symlinks
  ii  mesa-utils-bin:amd64  8.5.0-1   amd64Miscellaneous 
Mesa utilities -- native applications
  ii  mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API 
video acceleration drivers
  ii  mesa-vdpau-drivers:amd64  22.2.5-0ubuntu0.1 amd64Mesa VDPAU video 
acceleration drivers
  ii  mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan 
graphics drivers

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.10
  Release:22.10
  Codename:   kinetic

  $ uname -a
  Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Feb  1 22:55:48 2023
  InstallationDate: Installed on 2020-08-02 (913 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago)
  ---
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
   modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 
640x480 640x480 640x480
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p2 ext4   916G  222G  648G  26% /
   tmpfs  tmpfs   16G 0   16G   0% /dev/shm
   /dev/nvme0n1p2 ext4   916G  222G  648G  26% /
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-08-02 (914 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUS System Product Name
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic 
root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Snap.Changes: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119 

[Desktop-packages] [Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano
I think this crash can be enlightening. It's related to mutter:
1859fc3a-dd48-11ee-ba9e-fa163e171f02

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

Title:
  GNOME Shell crashes when I close any application

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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


[Desktop-packages] [Bug 1950703] Re: Keyboard input does't work in several apps with iBus running

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

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

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

Title:
  Keyboard input does't work in several apps with iBus running

Status in snapd:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  If installed through Snap and with iBus running the keyboard doesn't work in 
Standard Notes, XMind and Chromium apps on Manjaro 21.1. Killing iBus fixes the 
issue.
  The keyboard works in Visual Studio, however
  

  
  snap 2.51.3-2
  snapd 2.51.3-2
  series 16
  manjaro -
  kernel 5.10.70-1-MANJARO
  
  
  
   sudo snap connections chromium

  Interface PlugSlot
 Notes
  audio-playbackchromium:audio-playback 
:audio-playback  -
  audio-record  chromium:audio-record   
:audio-record-
  bluez chromium:bluez  :bluez  
 -
  browser-support   chromium:browser-sandbox
:browser-support -
  camerachromium:camera :camera 
 -
  content[gnome-3-28-1804]  chromium:gnome-3-28-1804
gnome-3-28-1804:gnome-3-28-1804  -
  content[gtk-3-themes] chromium:gtk-3-themes   
gtk-common-themes:gtk-3-themes   -
  content[icon-themes]  chromium:icon-themes
gtk-common-themes:icon-themes-
  content[sound-themes] chromium:sound-themes   
gtk-common-themes:sound-themes   -
  cups-control  chromium:cups-control   
:cups-control-
  desktop   chromium:desktop:desktop
 -
  desktop-legacychromium:desktop-legacy 
:desktop-legacy  -
  gsettings chromium:gsettings  :gsettings  
 -
  home  chromium:home   :home   
 -
  joystick  chromium:joystick   :joystick   
 -
  mount-observe chromium:mount-observe  -   
 -
  mpris -   
chromium:mpris   -
  network   chromium:network:network
 -
  network-bind  chromium:network-bind   
:network-bind-
  network-manager   chromium:network-manager-   
 -
  openglchromium:opengl :opengl 
 -
  password-manager-service  chromium:password-manager-service   -   
 -
  personal-fileschromium:chromium-config
:personal-files  -
  pulseaudiochromium:pulseaudio -   
 -
  raw-usb   chromium:raw-usb-   
 -
  removable-media   chromium:removable-media
:removable-media -
  screen-inhibit-controlchromium:screen-inhibit-control 
:screen-inhibit-control  -
  system-files  chromium:etc-chromium-browser-policies  
:system-files-
  system-packages-doc   chromium:system-packages-doc
:system-packages-doc -
  u2f-devices   chromium:u2f-devices
:u2f-devices -
  unity7chromium:unity7 :unity7 
 -
  upower-observechromium:upower-observe 
:upower-observe  -
  wayland   chromium:wayland:wayland
 -
  x11   chromium:x11:x11
 -


  
  sudo snap connections standard-notes

  Interface Plug Slot   
  Notes
  audio-playbackstandard-notes:audio-playback
:audio-playback  -
  browser-support   standard-notes:browser-support   
:browser-support -
  content[gnome-3-28-1804]  standard-notes:gnome-3-28-1804   
gnome-3-28-1804:gnome-3-28-1804  -
  content[gtk-3-themes] 

[Desktop-packages] [Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano
** Attachment added: "prevjournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056506/+attachment/5754030/+files/prevjournal.txt

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

Title:
  GNOME Shell crashes when I close any application

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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


[Desktop-packages] [Bug 2056506] Re: GNOME Shell crashes when I close any application

2024-03-08 Thread Marcos Alano
** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056506/+attachment/5754029/+files/journal.txt

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

Title:
  GNOME Shell crashes when I close any application

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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


[Desktop-packages] [Bug 1808123]

2024-03-08 Thread Juwaretu Yusuf
A Golden Ratio Calculator determines the golden ratio, which is
approximately 1.61803398875. It factors in parameters such as the length
of a line segment to calculate the golden ratio or the longer and
shorter segments of a line that are divided in such a way that the ratio
of the whole to the longer part is the same as the ratio of the longer
part to the shorter part. This tool aids in mathematics, architecture,
art, and design by providing a means to identify and apply the golden
ratio, which is often considered aesthetically pleasing and harmonious.
https://calculatoruniverse.com/golden-ratio-calculator/

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

Title:
  [upstream] Fullscreen view lands on another monitor

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

Bug description:
  As described above. I work in the classroom with my notebook, to which I have 
connected a beamer. Sometimes I write things down in the Writer and show it via 
the beamer. I would like to use the fullscreen mode here. 
  Unfortunately, the fullscreen mode is always displayed on the internal 
monitor, even if the window with the Writer maximized was previously displayed 
on the beamer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 12 10:44:00 2018
  InstallationDate: Installed on 2018-11-30 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1949291]

2024-03-08 Thread Heiko-tietze-g
(In reply to Stéphane Guillou (stragu) from comment #19)
> Heiko, are these delayed until the next opportunity, or are they just not
> shown at all?
Just delayed. GetInvolved will come first and Donate the next program start, if 
no other infobar is shown.

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

Title:
  LibreOffice has started displaying a donation nag

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I just opened up a spreadsheet (technically a CSV file, but who's
  counting), to discover LibreOffice displaying an eye-catching blue
  "Your donations support our worldwide community." banner just below
  the toolbars and about a toolbar and a half tall.

  This irritating nag is apparently supposed to display every 90 to 180
  days with no in-application means to disable it permanently, and
  there's apparently also a "Help us make LibreOffice even better!"
  banner that can appear too.

  According to this blog post...

  https://www.remembertheusers.com/2019/11/0580-libreoffice-nag-
  notices.html

  ...it is not responsive to configuration overrides within the user
  profile and the only apparent solution that doesn't require patching
  the source and rebuilding is to create a file containing the following
  markup in `$BASEDIR/share/registry`
  (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu
  package):

  
  http://www.w3.org/2001/XMLSchema; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:oor="http://openoffice.org/2001/registry;>

http://openoffice.org/2004/installation; oor:name="Setup" 
oor:package="org.openoffice">
  

  0


  0

  

  

  Regardless of how it's achieved, I think it's tasteless, irritating,
  and probably doesn't give a very good image to any office customers
  Ubuntu may have downstream for random employees to be receiving nag
  banners like that in IT-installed software.

  Please consider patching it out or otherwise ensuring it never
  triggers in distro-provided builds of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 04:32:03 2021
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1949291]

2024-03-08 Thread Stephane-guillou-i
(In reply to Heiko Tietze from comment #16)
> The patch hides the Donate and GetInvolved infobar if another one is visible.
Heiko, are these delayed until the next opportunity, or are they just not shown 
at all?

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

Title:
  LibreOffice has started displaying a donation nag

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I just opened up a spreadsheet (technically a CSV file, but who's
  counting), to discover LibreOffice displaying an eye-catching blue
  "Your donations support our worldwide community." banner just below
  the toolbars and about a toolbar and a half tall.

  This irritating nag is apparently supposed to display every 90 to 180
  days with no in-application means to disable it permanently, and
  there's apparently also a "Help us make LibreOffice even better!"
  banner that can appear too.

  According to this blog post...

  https://www.remembertheusers.com/2019/11/0580-libreoffice-nag-
  notices.html

  ...it is not responsive to configuration overrides within the user
  profile and the only apparent solution that doesn't require patching
  the source and rebuilding is to create a file containing the following
  markup in `$BASEDIR/share/registry`
  (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu
  package):

  
  http://www.w3.org/2001/XMLSchema; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xmlns:oor="http://openoffice.org/2001/registry;>

http://openoffice.org/2004/installation; oor:name="Setup" 
oor:package="org.openoffice">
  

  0


  0

  

  

  Regardless of how it's achieved, I think it's tasteless, irritating,
  and probably doesn't give a very good image to any office customers
  Ubuntu may have downstream for random employees to be receiving nag
  banners like that in IT-installed software.

  Please consider patching it out or otherwise ensuring it never
  triggers in distro-provided builds of LibreOffice.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Oct 31 04:32:03 2021
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-03-08 Thread Xavier Guillot
I reported the bug upstream for Firefox - if you have a Bugzilla account
on Mozilla and are affected, you could confirm it please :

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

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

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in geary package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Confirmed
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Fix Committed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

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


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


[Desktop-packages] [Bug 2056543] [NEW] Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04

2024-03-08 Thread Carlos H Simoes
Public bug reported:

Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and
several instabilities when using GDM3 instead of Waylan after upgrading
from 22.04 to 24.04.

> Oh no! Something has gone worng; A problem has occurred and the system
cant recover. Please log out and try again.


ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdm3 45.0.1-1ubuntu2
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: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  8 07:50:09 2024
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32
InstallationDate: Installed on 2020-12-12 (1182 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
ProcEnviron:
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
SourcePackage: gdm3
UpgradeStatus: Upgraded to noble on 2024-02-28 (9 days ago)
mtime.conffile..etc.init.d.apport: 2024-02-22T11:20:00

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


** Tags: amd64 apport-bug noble

** Description changed:

- Ubuntu 24.04 quebrando o gnome, apresetando "Ops.." solicitando logout,
- e varias instabilidades ao usar o GDM3 ao inves de Waylan apos atualizar
- do 22.04 para 24.04
+ Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and
+ several instabilities when using GDM3 instead of Waylan after upgrading
+ from 22.04 to 24.04.
+ 
+ > Oh no! Something has gone worng; A problem has occurred and the system
+ cant recover. Please log out and try again.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdm3 45.0.1-1ubuntu2
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 07:50:09 2024
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32
  InstallationDate: Installed on 2020-12-12 (1182 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
-  LANG=pt_BR.UTF-8
-  LANGUAGE=pt_BR:pt:en
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
+  LANG=pt_BR.UTF-8
+  LANGUAGE=pt_BR:pt:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to noble on 2024-02-28 (9 days ago)
  mtime.conffile..etc.init.d.apport: 2024-02-22T11:20:00

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

Title:
  Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and
  several instabilities when using GDM3 instead of Waylan after
  upgrading from 22.04 to 24.04

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and
  several instabilities when using GDM3 instead of Waylan after
  upgrading from 22.04 to 24.04.

  > Oh no! Something has gone worng; A problem has occurred and the
  system cant recover. Please log out and try again.


  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdm3 45.0.1-1ubuntu2
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 07:50:09 2024
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32
  InstallationDate: Installed on 2020-12-12 (1182 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to noble on 2024-02-28 (9 days ago)
  mtime.conffile..etc.init.d.apport: 2024-02-22T11:20:00

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1825227] Re: gnome-calendar overcompensates time zone difference in web ics calendar

2024-03-08 Thread Bug Watch Updater
** Changed in: gnome-calendar
   Status: New => Fix Released

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

Title:
  gnome-calendar overcompensates time zone difference in web ics
  calendar

Status in GNOME Calendar:
  Fix Released
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  Upon adding a web ics calendar (via Evolution due to Bug #1825224),
  the events from this calendar were not properly time-compensated for
  my time zone. While Evolution and Gnome Shell displayed the time of my
  events properly, gnome-calendar displayed the events 7 hours in the
  past, likely attempting to compensate for my time zone (GMT -7).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:47:17 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1825227/+subscriptions


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


[Desktop-packages] [Bug 2047579] Re: gnome-software unuable to install updates (Prepared update not found)

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

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

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

Title:
  gnome-software unuable to install updates (Prepared update not found)

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Click on 'Software' then 'Updates' then on 'Download' then 'Restart & Update' 
I have a error message:
  'Unable to install updates: Prepared update not 
found:/var/lib/PackageKit/prepared-update'

  lsb_release -a : 'Ubuntu 22.04.3 LTS' (however this is Xubuntu
  22.04.3).

  apt-cache policy gnome-software: installed 41.5-2ubuntu2

  Note: My bug report seems very similar to bug #1900167 opened in
  october 2020 by a other user (on Ubuntu 20.10).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-software 41.5-2ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Dec 27 17:36:48 2023
  InstallationDate: Installed on 2023-03-27 (275 days ago)
  InstallationMedia: Xubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap41.5-2ubuntu2
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

2024-03-08 Thread Daniel van Vugt
** Changed in: initramfs-tools (Ubuntu)
   Status: Opinion => New

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

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
quiet splash loglevel=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

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


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


[Desktop-packages] [Bug 2056529] [NEW] network-manager segfaults on multiple wifi scans

2024-03-08 Thread Felix Kopf
Public bug reported:

When I quickly fire

nmcli d wifi rescan ssid test-hidden

multiple times, the network-manager crashes with segfault.

Here a coredump:

PID: 4760 (NetworkManager)
UID: 0 (root)
GID: 0 (root)
Signal: 11 (SEGV)
Timestamp: Wed 2024-03-06 11:39:52 CET (9min ago)
Command Line: /usr/sbin/NetworkManager --no-daemon
Executable: /sbin/NetworkManager
Control Group: /system.slice/NetworkManager.service
Unit: NetworkManager.service
Slice: system.slice
Boot ID: 
Machine ID: 
Hostname: 
Storage:
/var/lib/systemd/coredump/core.NetworkManager.0.7f830276610c4ea886c51f8b922e9e3d.47
60.1709721592.lz4
Message: Process 4760 (NetworkManager) of user 0 dumped core.
Stack trace of thread 4760:
#0 0x7f1780fa2efb c_list_unlink_stale (libnm-device-plugin-wifi.so + 
0x17efb)
#1 0x7f1780fa349f _scan_request_ssids_remove (libnm-device-plugin-wifi.so + 
0x1849f)
#2 0x7f1780fa37e8 _scan_request_ssids_fetch (libnm-device-plugin-wifi.so + 
0x187e8)
#3 0x7f1780fa70aa _scan_request_ssids_build_hidden 
(libnm-device-plugin-wifi.so + 0x1c0aa)
#4 0x7f1780fa945a _scan_kickoff (libnm-device-plugin-wifi.so + 0x1e45a)
#5 0x7f1780fa7d0a _scan_kickoff_timeout_cb (libnm-device-plugin-wifi.so + 
0x1cd0a)
#6 0x7f1787bd4be8 n/a (libglib-2.0.so.0 + 0x52be8)
#7 0x7f1787bd404e g_main_context_dispatch (libglib-2.0.so.0 + 0x5204e)
#8 0x7f1787bd4400 n/a (libglib-2.0.so.0 + 0x52400)
#9 0x7f1787bd46f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
#10 0x564a05942577 n/a (/sbin/NetworkManager + 0x3c577)
#11 0x7f1787989083 __libc_start_main (libc.so.6 + 0x24083)
#12 0x564a059410de n/a (/sbin/NetworkManager + 0x3b0de)


Ubuntu 22.04.3 LTS
network-manager 1.36.6-0ubuntu2

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: manager network scan wifi

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

Title:
  network-manager segfaults on multiple wifi scans

Status in network-manager package in Ubuntu:
  New

Bug description:
  When I quickly fire

  nmcli d wifi rescan ssid test-hidden

  multiple times, the network-manager crashes with segfault.

  Here a coredump:

  PID: 4760 (NetworkManager)
  UID: 0 (root)
  GID: 0 (root)
  Signal: 11 (SEGV)
  Timestamp: Wed 2024-03-06 11:39:52 CET (9min ago)
  Command Line: /usr/sbin/NetworkManager --no-daemon
  Executable: /sbin/NetworkManager
  Control Group: /system.slice/NetworkManager.service
  Unit: NetworkManager.service
  Slice: system.slice
  Boot ID: 
  Machine ID: 
  Hostname: 
  Storage:
  
/var/lib/systemd/coredump/core.NetworkManager.0.7f830276610c4ea886c51f8b922e9e3d.47
  60.1709721592.lz4
  Message: Process 4760 (NetworkManager) of user 0 dumped core.
  Stack trace of thread 4760:
  #0 0x7f1780fa2efb c_list_unlink_stale (libnm-device-plugin-wifi.so + 
0x17efb)
  #1 0x7f1780fa349f _scan_request_ssids_remove (libnm-device-plugin-wifi.so 
+ 0x1849f)
  #2 0x7f1780fa37e8 _scan_request_ssids_fetch (libnm-device-plugin-wifi.so 
+ 0x187e8)
  #3 0x7f1780fa70aa _scan_request_ssids_build_hidden 
(libnm-device-plugin-wifi.so + 0x1c0aa)
  #4 0x7f1780fa945a _scan_kickoff (libnm-device-plugin-wifi.so + 0x1e45a)
  #5 0x7f1780fa7d0a _scan_kickoff_timeout_cb (libnm-device-plugin-wifi.so + 
0x1cd0a)
  #6 0x7f1787bd4be8 n/a (libglib-2.0.so.0 + 0x52be8)
  #7 0x7f1787bd404e g_main_context_dispatch (libglib-2.0.so.0 + 0x5204e)
  #8 0x7f1787bd4400 n/a (libglib-2.0.so.0 + 0x52400)
  #9 0x7f1787bd46f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
  #10 0x564a05942577 n/a (/sbin/NetworkManager + 0x3c577)
  #11 0x7f1787989083 __libc_start_main (libc.so.6 + 0x24083)
  #12 0x564a059410de n/a (/sbin/NetworkManager + 0x3b0de)

  
  Ubuntu 22.04.3 LTS
  network-manager 1.36.6-0ubuntu2

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


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


[Desktop-packages] [Bug 1164315] Re: Shutdown splash failing to load properly

2024-03-08 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.

Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: plymouth (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Shutdown splash failing to load properly

Status in plymouth package in Ubuntu:
  Won't Fix

Bug description:
  When shutting down ubuntu, there should be a splash screen showing up
  with the "Ubuntu" and the pricks Going white below.

  I am running 13.04 beta - and i have tested it now for one day.

  When shutting down the computer, the pricks in the splash shows up
  ONLY. All the other screen is black, with terminal-like text. The
  pricks are surrounded by squares and appears only when they are going
  "white", and then they stays there.

  ---

  So: 1) Ubuntu Raring Ringtail (13.04 - Beta branch)

  2) n/a

  3) I was expecting it to show the whole splash screen on Shutdown
  stage with a purple background.

  4) The Background was black, and only the pricks showed up when they
  was going "white".

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


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


[Desktop-packages] [Bug 2056526] [NEW] Plymouth's hidden console contains squares instead of bold text on live session shutdown

2024-03-08 Thread Daniel van Vugt
Public bug reported:

Plymouth's hidden console contains squares instead of bold text on live
session shutdown.

You can see it by pressing Escape instead of Enter.

It seems somewhat related to the fix for bug 1942987, which only
preloads non-bold text for the live session shutdown splash.

** Affects: plymouth (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: noble visual-quality

** Attachment added: "image.png"
   https://bugs.launchpad.net/bugs/2056526/+attachment/5753978/+files/image.png

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

Title:
  Plymouth's hidden console contains squares instead of bold text on
  live session shutdown

Status in plymouth package in Ubuntu:
  Triaged

Bug description:
  Plymouth's hidden console contains squares instead of bold text on
  live session shutdown.

  You can see it by pressing Escape instead of Enter.

  It seems somewhat related to the fix for bug 1942987, which only
  preloads non-bold text for the live session shutdown splash.

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


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


[Desktop-packages] [Bug 2054769] Re: Boot animation and login screen use different display scales

2024-03-08 Thread Daniel van Vugt
Also everything is back in git again:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/main

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

Title:
  Boot animation and login screen use different display scales

Status in Plymouth:
  New
Status in mutter package in Ubuntu:
  Won't Fix
Status in plymouth package in Ubuntu:
  In Progress

Bug description:
  Boot animation and login screen use different display scales, on some
  (not many) machines.

  For example on a Microsoft Surface Laptop 4, Plymouth seems to use
  scale 2 for the boot screen while GNOME selects scale 1 for the login
  screen. This means the Ubuntu logo shrinks.

  I've tried a few laptops and so far it's only the Surface Laptop 4
  that has the problem: 13.5" 2256x1504, 201 PPI

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


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


[Desktop-packages] [Bug 2054769] Re: Boot animation and login screen use different display scales

2024-03-08 Thread Daniel van Vugt
Here's the fix for Noble.

** Patch added: "plymouth_24.004.60-1ubuntu5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2054769/+attachment/5753977/+files/plymouth_24.004.60-1ubuntu5.debdiff

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

Title:
  Boot animation and login screen use different display scales

Status in Plymouth:
  New
Status in mutter package in Ubuntu:
  Won't Fix
Status in plymouth package in Ubuntu:
  In Progress

Bug description:
  Boot animation and login screen use different display scales, on some
  (not many) machines.

  For example on a Microsoft Surface Laptop 4, Plymouth seems to use
  scale 2 for the boot screen while GNOME selects scale 1 for the login
  screen. This means the Ubuntu logo shrinks.

  I've tried a few laptops and so far it's only the Surface Laptop 4
  that has the problem: 13.5" 2256x1504, 201 PPI

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


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