[Bug 2063827] Re: Gnome apps segfault in Nvidia Wayland sessions on Noble

[Jonathan Cave]

In my specific case I've never had Steam installed, can't really think
of any third apps that should impact the driver on my install.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063827

Title:
  Gnome apps segfault in Nvidia Wayland sessions on Noble

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063827] Re: Gnome apps segfault in Nvidia Wayland sessions on Noble

[Jonathan Cave]

I have now tried nvidia driver 550 (which isn't currently suggested by
Additional Drivers). I found that gnome apps no longer crash, but I did
notice the following messages are printed when calling from commandline:

❯ gnome-control-center 
MESA: error: ZINK: failed to choose pdev
libEGL warning: egl: failed to create dri2 screen

I have also experienced a problem on a few boots where no desktop
manager is displayed and I have to reset from power button and make
another boot attempt to bring up the login screen.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063827

Title:
  Gnome apps segfault in Nvidia Wayland sessions on Noble

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067872] Re: Gnome apps segfault in wayland session (noble)

[Jonathan Cave]

This appears to be a relevant crash report:
https://errors.ubuntu.com/oops/2d43fe25-2263-11ef-9e41-fa163ec44ecd

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067872

Title:
  Gnome apps segfault in wayland session (noble)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067872] Re: Gnome apps segfault in wayland session (noble)

[Jonathan Cave]

** Attachment added: "journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2067872/+attachment/5785815/+files/journalctl.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067872

Title:
  Gnome apps segfault in wayland session (noble)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067872] Re: Gnome apps segfault in wayland session (noble)

[Jonathan Cave]

I confirmed that I did have the Unknown Display problem so I blacklisted
simpledrm_platform_driver_init ass suggested and the extra display went
away. However, gnome apps continue to segfault while in a Wayland
session.

Will attachi the other logs as requested when I've switched back to xorg
session...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067872

Title:
  Gnome apps segfault in wayland session (noble)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067872] Re: Gnome apps segfault in wayland session (noble)

[Jonathan Cave]

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/2067872/+attachment/5785814/+files/lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067872

Title:
  Gnome apps segfault in wayland session (noble)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2067872] [NEW] Gnome apps segfault in wayland session (noble)

[Jonathan Cave]

Public bug reported:

I was happily using a wayland session on lunar on an AMD Threadripper
workstation with an NVIDIA Quadro discrete graphics card.

Since upgrade to noble I have experienced the similar symptons as
https://askubuntu.com/questions/1514352/ubuntu-24-04-with-nvidia-driver-
libegl-warning-egl-failed-to-create-dri2-scre except in this case there
is no Intel chipset to be a root cause.

I am using nividia-driver-535

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun  3 09:14:55 2024
DisplayManager: gdm3
InstallationDate: Installed on 2023-05-23 (377 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
RelatedPackageVersions: mutter-common 46.0-1ubuntu9
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to noble on 2024-04-29 (35 days ago)

** Affects: egl-wayland (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067872

Title:
  Gnome apps segfault in wayland session (noble)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected

[Jonathan Gilbert]

A further update -- a bit of a hack, but, I liked my "whiteglass"
cursor, and I found that copying its left_ptr and right_ptr files from
/usr/share/icons/whiteglass/cursors overtop of the corresponding ones in
/usr/share/icons/Breeze_Snow/cursors gave me back my whiteglass cursor,
at least for the pointer. :-P (I made backups of the originals before
doing this.) Except in Firefox for some reason. Anyway, I don't see this
as a long-term solution, but it at least helps somewhat with visibility
for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062377

Title:
  Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme
  is selected

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected

[Jonathan Gilbert]

I upgraded from 22.04 to 24.04 and could no longer log in. Just
immediately got the sad computer face screen. Can confirm that
installing `breeze` fixed this. I don't really know what's going on but
it seems to provide a functional fallback for when the selected cursor
theme isn't working. Trying to explicitly change the cursor theme with
dconf did not fix the problem, but installing breeze got me going again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062377

Title:
  Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme
  is selected

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063888] Re: 24.04 unusable after Gnome-Tweaks change to the mouse pointer

[Jonathan Gilbert]

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

Hello :-) I don't really know much about what's going on but I just
encountered this exact problem. I wasn't able to log in because Xorg
would immediately display the sad computer screen. I found another post,
though, where someone said that installing the `breeze` package worked.
I tried it and it got me back to my desktop.

Step 1: From login screen, Ctrl-Alt-F4
Step 2: Log in
Step 3: sudo apt install breeze

If your experience is like mine, this will allow you to log in once
more. Your cursor selection from gnome-tweaks will be ineffectual, but
it will now have a fallback that allows you to use the system again.

(I was using "whiteglass".)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063888

Title:
  24.04 unusable after Gnome-Tweaks change to the mouse pointer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066116] [NEW] GIMP crashed with a fatal error: fatal error: Segmentation fault

[Jonathan Long]

Public bug reported:




```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 27669 - Thread 27669 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 27877]
[New LWP 27835]
[New LWP 27833]
[New LWP 27685]
[New LWP 27682]
[New LWP 27681]
[New LWP 27679]
[New LWP 27678]
[New LWP 27677]
[New LWP 27676]
[New LWP 27675]
[New LWP 27674]
[New LWP 27673]
[New LWP 27672]
[New LWP 27671]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7d9c0ef1ba9a in __GI___libc_read (nbytes=256, buf=0x7ffef82867f0, fd=20) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x7d9c0e4e0640 (LWP 27669) "gimp-2.10"0x7d9c0ef1ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffef82867f0, fd=20) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7d9c02a006c0 (LWP 27877) "paint"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7d9beb4006c0 (LWP 27835) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7d9bf8e006c0 (LWP 27833) "threaded-ml"  0x7d9c0ef1b4cd in 
__GI___poll (fds=0x7d9bb40071a0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  5Thread 0x7d9bebe006c0 (LWP 27685) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7d9bf98006c0 (LWP 27682) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7d9c020006c0 (LWP 27681) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7d9c034006c0 (LWP 27679) "gdbus"0x7d9c0ef1b4cd in 
__GI___poll (fds=0x7d9bd4000b90, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  9Thread 0x7d9c08e006c0 (LWP 27678) "dconf worker" 0x7d9c0ef1b4cd in 
__GI___poll (fds=0x7d9bd8000b90, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  10   Thread 0x7d9c098006c0 (LWP 27677) "gmain"0x7d9c0ef1b4cd in 
__GI___poll (fds=0x555bc32411b0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  11   Thread 0x7d9c0a2006c0 (LWP 27676) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7d9c0ba006c0 (LWP 27675) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7d9c03e006c0 

Re: [Bug 2065644] Re: Right click Rename file or folder freeze

[Jonathan Smith]

Hi Sebastien,

it freezes

at first i just logout

then i actually open process to kill the process

then i figure if i click on the location bar /home/Documents on the same 
window, it allows me to get back control

but i have to tap a few times which is still annoying and this is just 
to regain back control of the ui

i then went to settings touch-pad and disable the tap to click

i now have to push every time to execute an event in any part of the ui

but at least i don't run into that issue where it just freeze

i install ubuntu on a macbook pro 2012 13'


On 5/14/24 02:38, Sebastien Bacher wrote:
> Thank you for your bug report.So is the issue just the tapping not
> working as expected or is it really freezing, the description is a bit
> confusing
>
> ** Changed in: nautilus (Ubuntu)
> Importance: Undecided => Low
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065644

Title:
  Right click Rename file or folder freeze

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065644] Re: Right click Rename file or folder freeze

[Jonathan Smith]

It appears when you right click and the context menu appears, you can
not tap on the Rename item, you need to do a hard click, meaning, if you
have a system with touch-pad, like a laptop, and you are use to tapping
and not clicking on the touch-pad, it is actually 2 different functions
on the Ubuntu OS, or at least Ubuntu treats it that way since i was able
to `click` on the context menu item Rename and make it work versus the
first time when i was just tapping on the context item menu
Rename...this really sucks since you are used to tapping everywhere on
the ui but all of the sudden you start finding out that tapping does not
work everywhere.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065644

Title:
  Right click Rename file or folder freeze

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065644] [NEW] Right click Rename file or folder freeze

[Jonathan Smith]

Public bug reported:

Ubuntu 24.04
All Updates as of 2024-05-13
Open Files
Right click on a file
Select Rename from context menu
Does not popup or allow to rename file
Same with folder
F2 key does works though
but I want to use Right click if that is an option

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 13 22:48:45 2024
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2024-05-12 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   44.1-1
 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065644

Title:
  Right click Rename file or folder freeze

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065234] Re: can't unlock and xfce4-screensaver-dialog segfaults if weston running

[Jonathan H N Chin]

I discovered that invoking weston as `weston --socket=something`
prevents the segfaults.

But perhaps there should be some code in the screensaver to detect this
problem and prevent the crash?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065234

Title:
  can't unlock and xfce4-screensaver-dialog segfaults if weston running

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065234] [NEW] can't unlock and xfce4-screensaver-dialog segfaults if weston running

[Jonathan H N Chin]

Public bug reported:

laptop running xubuntu 22.04.4, logged into xubuntu session.

xfce4-screensaver 4.16.0-1
weston 9.0.0-4ubuntu1
firefox 125.0.3-1 (snap)

Run firefox.
In terminal: tail -f /var/log/syslog
In another terminal: weston
Lock the screen by hotkey calling: xflock4

Press key to bring up dialog but only black shows - can see backlight
periodically turning on/off and flashes of cursor when pressing keys.

Ctrl-Alt-F1; login; pkill weston; Alt-F7 back to locked session.

Now unlocking works normally again.
However, after unlocking, many firefox empty windows have been created.

/var/log/syslog shows new output:

May  9 02:02:55 hostname kernel: [387457.737377] xfce4-screensav[355062]: 
segfault at 7fda0084 ip 7fdac936052f sp 7ffd6783c1a0 error 4 in 
libgdk-3.so.0.2404.29[7fdac9324000+83000]
May  9 02:02:55 hostname kernel: [387457.737387] Code: 57 82 fc ff 49 8b 9c 24 
70 01 00 00 48 85 db 74 4e 49 89 c5 eb 0a 0f 1f 44 00 00 48 85 db 74 3f 48 8b 
2b 48 89 de 48 8b 5b 08 <48> 8b 45 08 48 85 c0 74 e8 4c 39 e8 7f e3 49 8b bc 24 
70 01 00 00
May  9 02:02:55 hostname xfce4-screensav[2995]: g_object_ref: assertion 
'G_IS_OBJECT (object)' failed
May  9 02:02:57 hostname kernel: [387459.627666] xfce4-screensav[355067]: 
segfault at 2580418 ip 559c184c2e59 sp 7ffc0b3c1370 error 4 in 
xfce4-screensaver-dialog[559c184be000+e000]
May  9 02:02:57 hostname kernel: [387459.627676] Code: 48 8d 74 24 30 4c 89 e7 
e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 
e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 
10 4c 89 ff
May  9 02:03:01 hostname kernel: [387464.025803] xfce4-screensav[355081]: 
segfault at 2580418 ip 5646542f7e59 sp 7ffeed5fe800 error 4 in 
xfce4-screensaver-dialog[5646542f3000+e000]
May  9 02:03:01 hostname kernel: [387464.025813] Code: 48 8d 74 24 30 4c 89 e7 
e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 
e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 
10 4c 89 ff
May  9 02:03:03 hostname kernel: [387466.135825] xfce4-screensav[355094]: 
segfault at 2580418 ip 557eccebee59 sp 7ffc5a202b10 error 4 in 
xfce4-screensaver-dialog[557ecceba000+e000]
May  9 02:03:03 hostname kernel: [387466.135837] Code: 48 8d 74 24 30 4c 89 e7 
e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 
e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 
10 4c 89 ff
May  9 02:03:07 hostname kernel: [387469.786031] xfce4-screensav[355107]: 
segfault at 2580418 ip 5627b214be59 sp 7ffc56cbb780 error 4 in 
xfce4-screensaver-dialog[5627b2147000+e000]
May  9 02:03:07 hostname kernel: [387469.786041] Code: 48 8d 74 24 30 4c 89 e7 
e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 
e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 
10 4c 89 ff
May  9 02:03:08 hostname kernel: [387471.125899] xfce4-screensav[355120]: 
segfault at 2580418 ip 558dad3b5e59 sp 7fff8de7d090 error 4 in 
xfce4-screensaver-dialog[558dad3b1000+e000]
May  9 02:03:08 hostname kernel: [387471.125909] Code: 48 8d 74 24 30 4c 89 e7 
e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 
e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 
10 4c 89 ff
May  9 02:03:09 hostname wireplumber[2810]: [string 
"policy-bluetooth.lua"]:121: bad argument #1 to 'find' (string expected, got 
nil)#012stack traceback:#012#011[C]: in function 'string.find'#012#011[string 
"policy-bluetooth.lua"]:121: in upvalue 'isBluez5AudioSink'#012#011[string 
"policy-bluetooth.lua"]:389: in function <[string "policy-bluetooth.lua"]:387>
May  9 02:03:09 hostname systemd[2801]: Started 
snap.firefox.firefox-caf74e0d-aff8-419d-9e3c-44aabb8abacb.scope.
May  9 02:03:09 hostname systemd[2801]: Started 
snap.firefox.firefox-254eb60d-01c9-4a44-9558-825d8954d937.scope.
May  9 02:03:09 hostname systemd[2801]: Started 
snap.firefox.firefox-0cb163b8-0ef8-4e3c-94e7-8cfc3f1873b0.scope.
May  9 02:03:09 hostname systemd[2801]: Started 
snap.firefox.firefox-56b82216-0fe6-4bc2-afee-c1ebb971e98a.scope.
May  9 02:03:10 hostname systemd[2801]: Started 
snap.firefox.firefox-ccecdc0f-7743-4791-bd4a-f53a4e64b9ff.scope.
May  9 02:03:13 hostname wireplumber[2810]: SPA handle 'api.bluez5.enum.dbus' 
could not be loaded; is it installed?
May  9 02:03:13 hostname wireplumber[2810]: PipeWire's BlueZ SPA missing or 
broken. Bluetooth not supported.
May  9 02:03:14 hostname systemd[2801]: Started 
snap.firefox.firefox-8702c3ef-c11f-4c45-bb50-0a3873dd084c.scope.
May  9 02:03:14 hostname systemd[2801]: Started 
snap.firefox.firefox-8c3507de-27d0-4af8-88cc-c5ce8bb6438c.scope.
May  9 02:03:14 hostname systemd[2801]: Started 
snap.firefox.firefox-d43f024e-731a-4b55-ba1b-5ce97f58c116.scope.
May  9 02:03:14 hostname systemd[2801]: Started 

[Bug 2037335] Re: kernel leaking TCP_MEM

[Jonathan Heathcote]

Hello there,

I think this may be the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
aws-6.2/+bug/2045560

I believe this might be related to the following kernel bug which
impacts Linux 6.0.0+:

https://lore.kernel.org/netdev/vi1pr01mb42407d7947b2ea448f1e04efd1...@vi1pr01mb4240.eurprd01.prod.exchangelabs.com/

A patch has been produced which fixes this issue (but has not yet made
it into a Linux release):

https://lore.kernel.org/all/20240421175248.1692552-1-eduma...@google.com/

Hope this helps!

Jonathan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2037335

Title:
  kernel leaking TCP_MEM

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2045560] Re: TCP memory leak, slow network (arm64)

[Jonathan Heathcote]

The bug report can be found here:

https://lore.kernel.org/netdev/vi1pr01mb42407d7947b2ea448f1e04efd1...@vi1pr01mb4240.eurprd01.prod.exchangelabs.com/

The subsequently produced patch (not by me!) to fix this can be found
here:

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=3584718cf2ec

I've also verified that the above patch does fix the problem at least in
my case!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045560

Title:
  TCP memory  leak, slow network (arm64)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2045560] Re: TCP memory leak, slow network (arm64)

[Jonathan Heathcote]

I've been digging into this and this appears to be a regression
introduced by the following patch
https://github.com/torvalds/linux/commit/3cd3399dd7a84 which was first
released in Linux 6.0.0.

The bug is not a memory leak but rather a bug in how memory usage is
counted. Excess memory is not actually being consumed, though the bug is
still fatal since the counter controls Linux's memory pressure logic.

The (apparently) responsible patch is a performance optimisation which
attempts to reduce the frequency of writes to the system-wide counter
which (I suspect) is subtly misusing some atomic operation on ARM. If
you undo this patch in a recent kernel, the bug disappears.

I am currently working on a detailed bug report for the relevant Kernel
maintainers.

NB: It appears that the "5.15" kernel shipped by Rocky (and RHEL)
includes a back-port of this bug, hence my seeing the bug in that kernel
version on Rocky Linux. A non-RedHat-patched vanilla build of 5.15 does
not exhibit the bug in my system either.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045560

Title:
  TCP memory  leak, slow network (arm64)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2045560] Re: TCP memory leak, slow network (arm64)

[Jonathan Heathcote]

As another "me too" situation, I'm seeing the same phenomenon, though on
Rocky 9 rather than Ubuntu and on older kernels (5.14). Reporting
details here on the off chance this provides some insight.

Hardware: Ampere Altra Max 128 cores (aarch64), ConnectX6-DX NICs (2 x dual 
100G port)
Kernel versions tested: 5.15 (Rocky 9 native kernel) and 6.8 (elrepo kernel), 
both configured with 64 KB pages
OS: Rocky Linux 9
Software: nginx serving ~90k HTTPS clients at ~350 GBit/s (a synthetic load 
test)
Bare-metal (no virtualisation).

In my test environment, ~90k HTTPS connections are opened (and reused
via keepalive) and used to stream ~350 GBit/s of traffic to a cluster of
load generators. In this scenario, TCP memory gradually creeps up until
reaching the memory pressure threshold in /proc/sys/net/ipv4/tcp_mem
(243890 pages, or 15.6 GB in this system). At this point memory usage
growth actually increases slightly (and increased CPU load and response
times are also observed). The system eventually reaches the ultimate
limit (365832 pages, or 23.4 GB) at which point most connections fail
and all requests receive very slow responses.

Closing all connections or restarting nginx does not free up the memory,
only a reboot resolves the situation -- as reported above already.

Leaked memory appears to persist even if all connections are closed
prior to hitting any of the above limits.

Unfortunately I don't yet have any ideas on how to fix this but would be
glad to hear (and will share) any insights about what might be going on
here!

** Attachment added: "TCP memory consumption"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+attachment/5763728/+files/boom.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045560

Title:
  TCP memory  leak, slow network (arm64)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws-6.2/+bug/2045560/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+

[Jonathan Higdon]

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

I have the same issue. When i start the computer normally it stalls after the 
showing the ubuntu logo. 
So I can only use ubuntu with version 6.2.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051436

Title:
  Nvidia 390 Needs Patched for Kernel 6.5+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

[Jonathan Stucklen]

Turns out after a fresh reboot the memory usage isn't much different
after I close all apps and VmData for gnome shell is only about 400MB.
So, perhaps this isn't the smoking gun I thought it was.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297

Title:
  gnome-shell uses lots of memory, and grows over time

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

[Jonathan Stucklen]

Thanks @vanvugt, this was helpful. I'm running ubuntu 23.10. It's been
about a week since I rebooted and I noticed swap usage was quite high.
I've got 32GB of RAM and am a developer with a bunch of stuff open at
once. Decided to investigate. Closed everything, but left just gnome
running and a terminal. Did a swapoff -a to clear swap and dropped
caches to get it as close to just what was allocated as possible. It
still showed 14GB of memory used with 5GB in cache. That seems high.

So, ran this to take a look at VmData for gnome-shell:

  cat /proc/$(pgrep -f /usr/bin/gnome-shell)/status | grep VmData

That reveals:

  VmData:1231000 kB

That seems a bit excessive.

Full disclosure. I do use extensions. It's too bare-bones without them.

I miss being able to Alt-F2 -> R and reboot gnome, but it appears to not
be possible now with Wayland.



> It's important to remember that RSS increases is no indication of a leak - it 
> will rise and fall according to how busy the machine is and not how much new 
> memory the process has allocated. Please ignore all RSS values as they are 
> going to be unpredictable and misleading.
> 
> As for VSZ, that's kind of related to potential leaks. The problem with VSZ 
> is that it's a measure of the address space mappings size and is also not a 
> measure of regular memory allocated by the process. Although you can use 
> changes in VSZ to detect leaks and bloat, address space used by VSZ is not an 
> indication of the memory requirements of the process.
> 
> Probably a better field to monitor for actual leaks is VmData which you can 
> find in:
>   /proc/PID/status
> 
> VmData is a more realistic indication of memory allocated by the process.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672297

Title:
  gnome-shell uses lots of memory, and grows over time

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 2051045] Re: Freeze

[Jonathan Higdon]

So i reported the bug for you. But my computer is still in the same bad 
shape. Will the new kernel fix it? Or will I have to format and 
reinstall ubuntu again?

Em 30/01/2024 01:34, Daniel van Vugt escreveu:
> Oh I missed that. Having a problem with recovery mode probably means
> this isn't as simple as bug 2028165. Instead I'll move this to being
> just some new bug in kernel 6.5.
>
> ** Summary changed:
>
> - Freeze
> + Freeze in kernel 6.5 (but 6.2 works)
>
> ** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)
>
> ** Changed in: linux-hwe-6.5 (Ubuntu)
> Status: Incomplete => New
>
-- 
J.P.

3D Studio

www.jonathanpaul.com.br

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051045

Title:
  Freeze in kernel 6.5 (but 6.2 works)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051045/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977512] [NEW] package linux-firmware 1.187.31 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

[Jonathan Baumann]

Public bug reported:

Same issue as reported before for other versions.
Here 1.187.31

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.31
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1265 F pulseaudio
  jomini 1780 F pulseaudio
 /dev/snd/controlC0:  gdm1265 F pulseaudio
  jomini 1780 F pulseaudio
CasperMD5CheckResult: skip
Date: Fri Jun  3 08:56:22 2022
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-12-03 (546 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20BECTO1WW
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-40-generic 
root=UUID=8977a535-929a-4a34-b7a2-2b906d8dd2d3 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.31 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2021
dmi.bios.release: 2.39
dmi.bios.vendor: LENOVO
dmi.bios.version: GMET91WW (2.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BECTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnLENOVO:bvrGMET91WW(2.39):bd06/03/2021:br2.39:efr1.15:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20BE:
dmi.product.family: ThinkPad T540p
dmi.product.name: 20BECTO1WW
dmi.product.sku: LENOVO_MT_20BE
dmi.product.version: ThinkPad T540p
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977512

Title:
  package linux-firmware 1.187.31 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975597] [NEW] Python files are still packaged for Python 3.8

[Jonathan Kamens]

Public bug reported:

The Python files in the indicator-keyboard package are being installed
in /usr/lib/python3.8 instead of /usr/lib/python3.10.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: indicator-keyboard 0.0.0+19.10.20190716-0ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May 24 10:08:37 2022
InstallationDate: Installed on 2019-08-16 (1011 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: indicator-keyboard
UpgradeStatus: Upgraded to jammy on 2021-11-09 (196 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975597

Title:
  Python files are still packaged for Python 3.8

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970013] Re: Totem Video player displays distorted video (Intel Ivy Bridge)

[Jonathan]

This also affects me too. It's more of an annoyance (at least in my
case), as clicking the back arrow in the top left corner, and then
clicking on the video thumbnail temporarily fixes the issue. It's
opening video files directly that causes this glitch for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970013

Title:
  Totem Video player displays distorted video (Intel Ivy Bridge)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path

[Jonathan]

Updated 20.04 VM to 5.13.0-41-generic #46~20.04.1-Ubuntu and nfs bug is
fixed.

Updated 18.04 machine to 5.4.0-110-generic #124~18.04.1-Ubuntu and nfs
bug is fixed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  Regression: nfs cannot access/list wildcard file unless its cached
  when there is a symlink in path

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path

[Jonathan]

Great thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  Regression: nfs cannot access/list wildcard file unless its cached
  when there is a symlink in path

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached when there is a symlink in path

[Jonathan]

** Summary changed:

- Regression: nfs cannot access/list wildcard file unless its cached
+ Regression: nfs cannot access/list wildcard file unless its cached when there 
is a symlink in path

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  Regression: nfs cannot access/list wildcard file unless its cached
  when there is a symlink in path

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached

[Jonathan]

Do these changes also effect the linux-hwe branches?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  Regression: nfs cannot access/list wildcard file unless its cached

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached

[Jonathan]

How do I add 18.04 Bionic to the affects list?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  Regression: nfs cannot access/list wildcard file unless its cached

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer

[Jonathan Kamens]

Yes, the print job in question works when I print it to the driverless printer.
I would not say that it is therefore reasonable to declare that this issue is 
resolved, but *shrug* whatever.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968722

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: Regression: nfs cannot access/list wildcard file unless its cached

[Jonathan]

Looks like this patch solves the problem as we have a symlink in the
test path.  This needs to be applied to Ubuntu's hwe-5.4 and hwe-5.13
kernels.  Probably anywhere else the above commits got backported to.

[PATCH] NFS: LOOKUP_DIRECTORY is also ok with symlinks

https://lore.kernel.org/all/f7a7d0e1-41ab-f648-97a3-9fd92e0e2...@leemhuis.info/T/#m5d587247611e36afcfcd157125e910d4f7075cb7

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  Regression: nfs cannot access/list wildcard file unless its cached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1971482/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached

[Jonathan]

I checked out the focal kernel and reverted the following commits. And
the problem went away, reverting just the 1st one wasn't enough to fix
the issue.

- NFSv4: nfs_atomic_open() can race when looking up a non-regular file
- NFSv4: Handle case where the lookup of a directory fails


git clone git://kernel.ubuntu.com/ubuntu/ubuntu-focal.git linux-ubuntu-focal
cd linux-ubuntu-focal
git checkout Ubuntu-hwe-5.13-5.13.0-40.45_20.04.1 -b 
Ubuntu-hwe-5.13-5.13.0-40.45_20.04.1

vim debian/changelog # modify version in head of file
LANG=C fakeroot debian/rules clean
LANG=C fakeroot debian/rules binary-headers binary-generic binary-perarch 
skipmodule=true

** Also affects: linux-signed-hwe-5.13 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- nfs cannot access/list wildcard file unless its cached
+ Regression: nfs cannot access/list wildcard file unless its cached

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  Regression: nfs cannot access/list wildcard file unless its cached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1971482/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached

[Jonathan]

Looks like a nfs patch for
https://bugs.launchpad.net/bugs/cve/2022-24448  was introduced in
5.13.0-40 and linux-image-5.4.0-109.  So could be cause of regression.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  nfs cannot access/list wildcard file unless its cached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached

[Jonathan]

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24448

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  nfs cannot access/list wildcard file unless its cached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached

[Jonathan]

Also noticed the issue on a 20.04 server which got updated to kernel
5.13.0-40.  Downgrading to 5.13.0-39 fixed the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  nfs cannot access/list wildcard file unless its cached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] Re: nfs cannot access/list wildcard file unless its cached

[Jonathan]

Attaching tcpdump for machine seeing errors
$ sudo tcpdump -w /tmp/data.pcap -i bond0 host 10.0.0.23


** Attachment added: "data.pcap"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+attachment/5586399/+files/data.pcap

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  nfs cannot access/list wildcard file unless its cached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971482] [NEW] nfs cannot access/list wildcard file unless its cached

[Jonathan]

Public bug reported:

Some of our build machines have recently started failing builds.  It was
noted that all the machines that fail the build are running the most
recent kernel 5.4.0-109-generic #123~18.04.1-Ubuntu.

The following command was created to minimally reproduce the issue:

$ while true; do sudo /usr/local/scripts/drop_cache.sh;  ls -la 
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk 
| tee -a /tmp/ls.log 2>&1; sleep 1;done
ls: cannot access 
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
 No such file or directory
ls: cannot access 
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
 No such file or directory
ls: cannot access 
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
 No such file or directory
ls: cannot access 
'/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq*.ipk':
 No such file or directory


Note directly trying to list the file works every time, it seems the bug must 
be related to the use of the wildcard.

$ while true; do sudo /usr/local/scripts/drop_cache.sh;  ls -la 
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
 | tee -a /tmp/ls.log 2>&1; sleep 1;done
-rw-r--r-- 1 jenkins engineer 202526 May  2 13:47 
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
-rw-r--r-- 1 jenkins engineer 202526 May  2 13:47 
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk
-rw-r--r-- 1 jenkins engineer 202526 May  2 13:47 
/shared/projects/MityCAM-jenkins/intermediates/MityCAM-Yocto/latest/libdaq_1.0.9323-r3_cortexa9hf-neon.ipk

The drop_cache was needed to force the error everytime, otherwise it
would fail only a few times then succeed a bunch in a row before
randomly failing again.

$ cat /usr/local/scripts/drop_cache.sh 
#!/bin/bash

# Test script to drop filesystem cache
sync

# Clear pagecache, dentries, and inodes
echo 3 > /proc/sys/vm/drop_caches


Downgrading the kernel to 5.4.0-107-generic on one of the machines caused the 
problem to go away.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-109-generic 5.4.0-109.123~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174
Uname: Linux 5.4.0-107-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
Date: Tue May  3 15:04:34 2022
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: linux-signed-hwe-5.4
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971482

Title:
  nfs cannot access/list wildcard file unless its cached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1971482/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971232] [NEW] [Dell XPS 8940] [ALC3861] No audio from headset mic when plugged into front panel jack, works under Windows

[Jonathan Yip]

Public bug reported:

There is no audio coming from the headset mic when plugged into the
front panel headset jack (bog standard wired headphones with mic, Sony
MDR-EX15AP). Upon plugging in Gnome should offer a choice of "Headset"
amongst others, but the only ones available are "Headphones" and
"Microphone", neither of which enables the mic on the headset. The same
headset works under Windows, so it shouldn't be an issue of mismatching
TRRS.

I'm happy to provide any further details if needed.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jonathan   8896 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue May  3 13:54:25 2022
InstallationDate: Installed on 2021-08-16 (260 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jonathan   8896 F pulseaudio
Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all
UpgradeStatus: Upgraded to jammy on 2022-04-27 (5 days ago)
dmi.bios.date: 03/29/2022
dmi.bios.release: 2.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.1
dmi.board.name: 0427JK
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd03/29/2022:br2.5:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
dmi.product.family: XPS
dmi.product.name: XPS 8940
dmi.product.sku: 09C5
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-28T14:25:53.371743

** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971232

Title:
  [Dell XPS 8940] [ALC3861] No audio from headset mic when plugged into
  front panel jack, works under Windows

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966793] Re: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

[Jonathan Hayes]

I haven't seen a posted workaround for this anywhere so here is what I
found to work on both v20.04 and v22.04:

For those loading iwlwifi-QuZ-a0-jf-b0-XX.ucode, use the 55 version as
shown:

/lib/iwlwifi-QuZ-a0-jf-b0-55.ucode

I just moved all newer firmware that are higher than 55 out of the
/lib/firmware directory.

In v20.04, after removing newer firmware, it just auto loads and starts working.
In v22.04, you must reboot after removing the firmware that is higher than 55.

So something changed after v55 that broke the wireless functionality on
the 440 G8 with AX201.

Here is a before and after hardware snapshot:

-  *-network DISABLED
+  *-network 
description: Wireless interface
product: Wi-Fi 6 AX201
vendor: Intel Corporation
physical id: 14.3
bus info: pci@:00:14.3
logical name: wlp0s20f3
version: 20
serial: 28:d0:ea:15:fc:c0
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
-   configuration: broadcast=yes driver=iwlwifi 
driverversion=5.15.0-27-generic firmware=66.f1c864e0.0 QuZ-a0-jf-b0-66.u 
latency=0 link=no multicast=yes wireless=IEEE 802.11
+   configuration: broadcast=yes driver=iwlwifi 
driverversion=5.15.0-28-generic firmware=55.d9698065.0 QuZ-a0-jf-b0-55.u 
ip=192.168.247.110 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: iomemory:600-5ff irq:16 memory:600324c000-600324

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966793

Title:
  Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar
  11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969280] [NEW] gnome-terminal not obeying light vs. dark theme

[Jonathan Kamens]

Public bug reported:

In a brand new account created just to test this issue, gnome-terminal
has a dark background and light fonts even when the GNOME them is set to
light. I am not sure if this is a new issue in Jammy, but it sure is
frustrating that when I switch to light mode every app switches to a
white background except gnome-terminal.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-terminal 3.44.0-1ubuntu1 [modified: 
usr/share/applications/org.gnome.Terminal.desktop]
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 16 14:44:00 2022
InstallationDate: Installed on 2019-08-16 (973 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to jammy on 2021-11-09 (158 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969280

Title:
  gnome-terminal not obeying light vs. dark theme

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1308439] Re: add --version argument

[Jonathan H N Chin]

version option was added in 2.19

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308439

Title:
  add --version argument

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer

[Jonathan Kamens]

>Do you have cups-filter 1.28.15 installed

Yes, and I rebooted after installing it just to make sure. Problem
persists.

>Or did you try the option "pdftops-renderer=gs" as described there and
which you confirmed as fixing that bug?

I _also_ have this setting in my printers.conf. So clearly this bug is
different from that one.

> Generally, driverless printing is more reliable than PostScript
printing. PostScript interpreters in printers often have bugs.

These two statements seem to be contradictory. If driverless printing is
more reliable, that would seem to imply that files sent directly to the
printer print more reliably than files sent through the CUPS filters,
which would seem to imply that it is the filters, not the printer, that
have bugs.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968722

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer

[Jonathan Kamens]

Here's my printers.conf, since it doesn't look like ubuntu-bug attached
it, and there's no sensitive information in it.


** Attachment added: "printers.conf"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+attachment/5579950/+files/printers.conf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968722

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968722] [NEW] File fails to print when rendered with CUPS, prints fine when fed directly to printer

[Jonathan Kamens]

Public bug reported:

I have a printer named "duplex" configured to print through CUPS
PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
(recommended)", "DeviceURI socket://m551dn.kamens.brookline.ma.us:9100"
in printers.conf) and the same physical printer configured driverless in
CUPS with a different name ("MakeModel HP LaserJet 500 color M551,
driverless, cups-filters 1.28.15", "DeviceURI
implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
browsed-dest-printer "1625
ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
pdf 600dpi"") in printers.conf.

The attached file prints just fine when sent to the latter printer,
i.e., prints fine with driverless printing, but fails to print when sent
through the CUPS Postscript renderer, i.e., the former printer. In
particular, the file stops printing after four pages and then the
printer spits out this error page:

ERROR:
typecheck
OFFENDING-COMMAND:
known

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 08:21:44 2022
InstallationDate: Installed on 2019-01-02 (1195 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lpstat:
 device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
 device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
 device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
 grep: /etc/cups/ppd/duplex.ppd: Permission denied
 grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug jammy

** Attachment added: "comics.pdf"
   https://bugs.launchpad.net/bugs/1968722/+attachment/5579931/+files/comics.pdf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968722

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1701788] Re: /usr/bin/plasmashell debug symbols are not provided by plasma-workspace-dbgsym

[Jonathan Watts]

Since the problem is with `plasma-workspace-dbgsym`, how would the
availability of `plasma-workspace-dev` affect this issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701788

Title:
  /usr/bin/plasmashell debug symbols are not provided by plasma-
  workspace-dbgsym

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it

[Jonathan Kamens]

The file prints with pdftops-renderer=gs.

I can fix this for me personally, but is there any way to adjust the
default CUPS configuration for the type of printer that I have to make
this setting the default for others with the same printer, so they don't
also run into this issue?


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967816

Title:
  PDF file completely silently fails to print, computer claims it
  printed, printer shows no trace of it

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967816] [NEW] PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it

[Jonathan Kamens]

Public bug reported:

I have an HP LaserJet M551dn printer which usually works just fine with
CUPS. Tonight, however, I discovered that I was completely unable to
print one particular PDF file (unfortunately I can't provide you with
the file because it's a scan of a tax form with PII on it). CUPS claimed
that it printed the file and there are no errors in the log. On the
other side, the printer doesn't show any trace of the file haven't been
sent to it. The print job isn't in the job log, and at no point while
CUPS claims it's printing does the printer make any noise or any of its
lights blink as they usually do when a job is being sent to it.

I don't know how to debug this further. I'm attaching the section of
/var/log/cups/error_log from the attempt to print the file.

This is reproducible every time with this particular file, including
immediately after updating to all current Jammy packages and rebooting.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  4 20:51:23 2022
InstallationDate: Installed on 2019-01-02 (1188 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lpstat:
 device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
 device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
 device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
 grep: /etc/cups/ppd/duplex.ppd: Permission denied
 grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug jammy

** Attachment added: "/var/log/cups/error_log excerpt"
   https://bugs.launchpad.net/bugs/1967816/+attachment/5577050/+files/error_log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967816

Title:
  PDF file completely silently fails to print, computer claims it
  printed, printer shows no trace of it

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967637] Re: gnome-extensions-app crashing on startup, not producing reportable crash for some reason

[Jonathan Kamens]

I just installed another round of new Jammy updates on the laptop where
gnome-extensions-app was crashing, and it's not crashing anymore. I
don't know if it's the installing of the updates that fixed this or if
it's an intermittent issue and just not happening at the moment. Hard to
tell since no crash report was generated. :shrug:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967637

Title:
  gnome-extensions-app crashing on startup, not producing reportable
  crash for some reason

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963755] Re: extensions get turned off spontaneously when I log out and log back in

[Jonathan Kamens]

I can no longer reproduce this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963755

Title:
  extensions get turned off spontaneously when I log out and log back in

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967637] Re: gnome-extensions-app crashing on startup, not producing reportable crash for some reason

[Jonathan Kamens]

I have two machines with Jammy on them and this is happening reliably on
one but not the other.

On the one where it's happening, it happens even immediately after I've
updated all out-of-date packages and rebooted the machine.

I don't know why it's not generating a crash report. :-(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967637

Title:
  gnome-extensions-app crashing on startup, not producing reportable
  crash for some reason

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967637] [NEW] gnome-extensions-app crashing on startup, not producing reportable crash for some reason

[Jonathan Kamens]

Public bug reported:

$ /usr/bin/gnome-extensions-app
Segmentation fault (core dumped)

There's nothing in /var/crash.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-prefs 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr  2 17:01:32 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (960 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 42.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2021-11-09 (144 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967637

Title:
  gnome-extensions-app crashing on startup, not producing reportable
  crash for some reason

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967539] Re: All file downloads fail

[Jonathan Brodmann]

I can confirm that this is not just related to firefox and snap.  After
adding the Brave browser, I am unable to be prompted to save downloaded
files.  The prompt does not appear.  I have heard that this is also
apparent in Chrome.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967539

Title:
  All file downloads fail

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967315] [NEW] package linux-firmware 1.187.29 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

[Jonathan Baumann]

Public bug reported:

While installing full upgrade from terminal - sudo apt full-upgrade

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.29
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Mar 31 10:45:37 2022
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-12-03 (482 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20BECTO1WW
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic 
root=UUID=8977a535-929a-4a34-b7a2-2b906d8dd2d3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.29 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2021
dmi.bios.release: 2.39
dmi.bios.vendor: LENOVO
dmi.bios.version: GMET91WW (2.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BECTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnLENOVO:bvrGMET91WW(2.39):bd06/03/2021:br2.39:efr1.15:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20BE:
dmi.product.family: ThinkPad T540p
dmi.product.name: 20BECTO1WW
dmi.product.sku: LENOVO_MT_20BE
dmi.product.version: ThinkPad T540p
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967315

Title:
  package linux-firmware 1.187.29 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966614] Re: I am getting calendar notification pop-ups even though I've turned them off

[Jonathan Kamens]

Yes they are Reminders from the Calendar app. For a Google account.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966614

Title:
  I am getting calendar notification pop-ups even though I've turned
  them off

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966614] [NEW] I am getting calendar notification pop-ups even though I've turned them off

[Jonathan Kamens]

Public bug reported:

I keep getting calendar notification pop-ups -- at the top middle of my
screen -- even though in the calendar settings in Notifications I have
"Notification Popups" turned off.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-calendar 41.2-3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 27 20:20:15 2022
InstallationDate: Installed on 2019-08-16 (954 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to jammy on 2021-11-09 (138 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966614

Title:
  I am getting calendar notification pop-ups even though I've turned
  them off

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.

[Jonathan George]

You referenced the original report, patch, and promotion to Linux Next for 
review. The new information is that the resolution for the issue you referenced 
was reviewed and promoted by Greg KH from Linux Next to his queue for Linus 
https://lore.kernel.org/all/yayq%2fxdb%2fphss7%...@kroah.com/ in the production 
kernel back on December 5, 2021. BTW it was accepted into Linus's mainline 
queue with commit 
https://lore.kernel.org/all/163872600645.987.7156724710444619664.pr-tracker-...@kernel.org/
 later that day.
Interestingly Greg mentioned merging these changes into the stable queue. If he 
actually did so (I didn't notice where) it might help to make sure that 21.10 
and 22.04 are immediately rebased to include the mainline included patches.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963555

Title:
  xhci: Fix command ring abort, write all 64 bits to CRCR register.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.

[Jonathan George]

This appears to be the resolution upstream:
https://lore.kernel.org/linux-usb/yay1eiy%2ff7ezp...@kroah.com/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963555

Title:
  xhci: Fix command ring abort, write all 64 bits to CRCR register.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963555] Re: xhci: Fix command ring abort, write all 64 bits to CRCR register.

[Jonathan George]

I have also experienced this upstream bug which causes the USB hubs to
drop all attached devices. This means that external drive devices all
disappear almost as quickly as they appear. Basically it's a show
stopper since I can't use my USB attached data drives at all any more.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963555

Title:
  xhci: Fix command ring abort, write all 64 bits to CRCR register.

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964976] [NEW] gnome-remote-desktop is not listening on port 5900, no sign of why

[Jonathan Kamens]

Public bug reported:

With all current packages from jammy, gnome-remote-desktop is not
listening on port 5900. Lsof doesn't show it listening on that port,
attempting to connect to that port yields connection refused), with no
indication of why. There are no errors matching the pattern "gnome-
remote-desktop" in /var/log/syslog, "journalctl --user --unit gnome-
remote-desktop" doesn't show any errors, "systemctl status --user gnome-
remote-desktop" shows that it is running, my settings show that screen
sharing is enabled, this used to work, and I haven't changed anything
since it did.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-remote-desktop 42~rc-1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 15 10:49:08 2022
InstallationDate: Installed on 2019-01-02 (1167 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-remote-desktop
UpgradeStatus: Upgraded to jammy on 2022-02-20 (22 days ago)

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964976

Title:
  gnome-remote-desktop is not listening on port 5900, no sign of why

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1

[Jonathan Kamens]

Works for me as well.
(Does Ubuntu have some sort of karma system similar to Fedora's, i.e., is there 
another web site somewhere we should be going to to indicate that the fix works 
for us?)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964814

Title:
  linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963756] Re: Desktop Icons NG doesn't display icons on desktop on login until I turn it off and turn it back on

[Jonathan Kamens]

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

I don't think these two issues are duplicates, which is why I filed them
separately.

This issue occurs even when the other one, which is intermittent, does
not.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963756

Title:
  Desktop Icons NG doesn't display icons on desktop on login until I
  turn it off and turn it back on

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1963756/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864215] Re: Please add webp loader to gdk-pixbuf

[Jonathan Yip]

In case you don't want to wait for aruiz's loader to be packaged in Debian (and 
then trickled down to Ubuntu), here's a PPA:
https://code.launchpad.net/~helkaluin/+archive/ubuntu/webp-pixbuf-loader

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864215

Title:
  Please add webp loader to gdk-pixbuf

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963766] Re: Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8

[Jonathan Kamens]

All of these problems seem to go away when I download GnuCash 4.9 from
gnucash.org, build it from source after `apt-get build-dep gnucash` with
an install prefix of /opt/gnucash, install it in /opt/gnucash, and run
it from there.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963766

Title:
  Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963766] [NEW] Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8

[Jonathan Kamens]

Public bug reported:

After installing the recent upgrade from gnucash 4.4 to 4.8 and opening
gnucash, it doesn't start with my previously opened gnucash file opened
as it usually does, but that's the only start of the problems.

When I open the file explicitly, it only shows two account tabs even
though there were previously a lot more tabs than that open, it doesn't
show the main Accounts tab, and there appears to be no way to get it to
open the main Accounts tab.

My previously configured preferences are all gone.

Changing preferences does not seem to have any effect, and when I change
preferences and then close and reopen the preferences window my changes
are gone.

Removing ~/.config/gnucash has no effect on any of this.

Removing ~/.cache/gnucash has no effect on any of this.

Removing ~/.gnucash has no effect on any of this.

Removing ~/.local/share/gnucash at least brings back the Accounts tab
but all the other problems enumerated above remain.

Basically, things are completely screwed up and I can't find any way to
fix it.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnucash 1:4.8-1build2
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  5 15:05:29 2022
InstallationDate: Installed on 2019-01-02 (1158 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnucash
UpgradeStatus: Upgraded to jammy on 2022-02-20 (12 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963766

Title:
  Gnucash is completely screwed up after recent upgrade from 4.4 to 4.8

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1403454] Re: Latex Formula crashes with Unrecoverable error: stackunderflow in .setdistillerparams

[Jonathan Hofinger]

The pdflatex extension no loger uses pstoedit, so closing.

Closed by https://gitlab.com/jhofinger

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

** Changed in: inkscape
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403454

Title:
  Latex Formula crashes with Unrecoverable error: stackunderflow in
  .setdistillerparams

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1210287] Re: LaTeX renderer shows an error message (but does render LaTeX formula)

[Jonathan Hofinger]

The pdflatex extension no longer uses pstoedit, closing.

Closed by https://gitlab.com/jhofinger

** Changed in: ubuntu
   Status: Confirmed => Invalid

** Changed in: inkscape
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210287

Title:
  LaTeX renderer shows an error message (but does render LaTeX formula)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963755] [NEW] extensions get turned off spontaneously when I log out and log back in

[Jonathan Kamens]

Public bug reported:

1. Have some GNOME shell extensions installed (I have Allow Locked Remote 
Desktop, Mpris Indicator Button, Removable Drive Menu, User Themes, plus 
built-ins Desktop Icons NG, Ubuntu AppIndicators, Ubuntu Dock).
2. Open the Extensions app.
3. Confirm that the switch at the top controlling all extensions is on.
4. Log out.
5. Log back in.
6. Observe that your extensions are not running.
7. Open the Extensions app.
8. Observe that the switch at the top is now off, even though you never turned 
it off.

This is reproducible for me.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 41.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  5 13:02:55 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (1158 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 41.3-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-02-20 (12 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963755

Title:
  extensions get turned off spontaneously when I log out and log back in

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1963756] [NEW] Desktop Icons NG doesn't display icons on desktop on login until I turn it off and turn it back on

[Jonathan Kamens]

Public bug reported:

1. Observe icons from Desktop Icons NG on desktop.
2. Log out.
3. Log back in.
4. Observe that desktop icons are gone.
5. Open Extensions app.
6. Observe that the Desktop Icons NG extension is enabled.
7. Turn it off and turn it back on.
8. Observe that the missing desktop icons now appear.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-desktop-icons-ng 39-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  5 13:06:10 2022
InstallationDate: Installed on 2019-01-02 (1158 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-desktop-icons-ng
UpgradeStatus: Upgraded to jammy on 2022-02-20 (12 days ago)

** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963756

Title:
  Desktop Icons NG doesn't display icons on desktop on login until I
  turn it off and turn it back on

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1963756/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 591435] Re: Cancel button does not halt extensions

[Jonathan Hofinger]

Hi, I'm closing this issue - a duplicate of it has been opened on
GitLab: https://gitlab.com/inkscape/inkscape/-/issues/1553

Closed by https://gitlab.com/jhofinger

** Bug watch added: gitlab.com/inkscape/inkscape/-/issues #1553
   https://gitlab.com/inkscape/inkscape/-/issues/1553

** Changed in: inkscape
   Status: Triaged => Invalid

** Changed in: inkscape (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/591435

Title:
  Cancel button does not halt extensions

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1194871] Re: Huge Memory consumption by extension and pipe not closed

[Jonathan Hofinger]

Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new
bug tracker on GitLab, and closed it here.

Please feel free to file new bugs about the issues you're seeing at
http://inkscape.org/report.

Moved to: https://gitlab.com/inkscape/inbox/-/issues/6489
Closed by: https://gitlab.com/jhofinger

** Bug watch added: gitlab.com/inkscape/inbox/-/issues #6489
   https://gitlab.com/inkscape/inbox/-/issues/6489

** Changed in: inkscape
   Status: Triaged => Invalid

** Changed in: inkscape (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194871

Title:
  Huge Memory consumption by extension and pipe not closed

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 479944] Re: Extensions check for Perl dependencies

[Jonathan Hofinger]

Closing because there are no perl extensions shipped with Inkscape
anymore, starting with Inkscape 1.0.

Closed by: https://gitlab.com/jhofinger

** Changed in: inkscape
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/479944

Title:
  Extensions check for Perl dependencies

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960508] [NEW] glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386

[Jonathan Camara]

Public bug reported:

After running "sudo apt upgrade" and approving the listed packages, the
following error occurred after unpacking a number of packages:

dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:

 
 libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however:

 
  Package libmount1:i386 is not configured yet.

output from "dpkg-reconfigure libmount1:i386":

/usr/sbin/dpkg-reconfigure: libmount1:i386 is broken or not fully
installed

output from "sudo apt install libmount1:i386":

Reading package lists... Done   

 
Building dependency tree... Done

 
Reading state information... Done   

 
libmount1:i386 is already the newest version (2.36.1-8ubuntu2.2).
...

output from "sudo apt reinstall libmount1:i386":

E: Internal Error, No file name for libmount1:i386

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


** Tags: impish

** Tags added: impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960508

Title:
  glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960426] [NEW] Warnings during package installation

[Jonathan Yu]

Public bug reported:

When installing on focal (replicated with docker run --rm -it
ubuntu:focal), the following warning is emitted during installation:

Setting up mitmproxy (4.0.4-6.1) ...
/usr/lib/python3/dist-packages/mitmproxy/contentviews/image/image_parser.py:57: 
SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if comment is not b'':

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960426

Title:
  Warnings during package installation

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956542] Re: usb devices connected via usb 3.*-Hub are not detected

[Jonathan Schmidt-Dominé]

Dear Matthew,

I do not know if it is exactly the same situation here, but after a
recent upgrade (early January) I noticed that my external Realtex USB
3.0 hub only gets recognised as VIA Labs USB 2.0 hub and usually does
not work at all then.

usb 1-1: new high-speed USB device number 6 using xhci_hcd
usb 1-1: New USB device found, idVendor=2109, idProduct=2813, bcdDevice=90.11
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: USB2.0 Hub
usb 1-1: Manufacturer: VIA Labs, Inc.
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected

When I attach it to a USB 2.0 port, it works.

I tested with 5.13.0-22-generic and it was the same.

Best,

Jonathan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956542

Title:
  usb devices connected via usb 3.*-Hub are not detected

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958651] Re: Out of memory error when attempting to use Camera Module on RPi4

[Jonathan Cave]

Board info for rpi4b8g-002:
Hardware: BCM2711
Revision: d03114
...
Model   : Raspberry Pi 4 Model B Rev 1.4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958651

Title:
  Out of memory error when attempting to use Camera Module on RPi4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1958651/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958651] Re: Out of memory error when attempting to use Camera Module on RPi4

[Jonathan Cave]

Board info for rpi24b4g-002:
Hardware: BCM2711
Revision: c03111
...
Model   : Raspberry Pi 4 Model B Rev 1.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958651

Title:
  Out of memory error when attempting to use Camera Module on RPi4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1958651/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958651] [NEW] Out of memory error when attempting to use Camera Module on RPi4

[Jonathan Cave]

Public bug reported:

Image: Ubuntu Core 20 armhf
Devices: Raspberry Pi 4 2GB / 4GB / 8GB
Camera Module v2.1

Steps to reproduce:

* Install the image
* Edit /writable/system-data/var/lib/snapd/seed/config.txt to ensure the 
following lines are present:
start_x=1
gpu_mem=128
* Reboot
* sudo snap install checkbox --channel=uc20/stable --devmode
* sudo checkbox.checkbox-cli
* hit "/" then type "camera" to search for the camera tests
* Press spacebar on the automated ones to select them, then enter
* It will take you to another screen where you can deselect things, don't worry 
about it - just press "T" to start testing
* It will ask you to confirm that you have a camera attached, just select yes, 
then "T" again to start testing


The modules/cables in the lab have been moved to rpi2/rpi3 to confirm they are 
working

** Affects: linux-firmware-raspi2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958651

Title:
  Out of memory error when attempting to use Camera Module on RPi4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1958651/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1275740] Re: Installer fails when preseeding 'partman-partitioning/confirm_resize'

[Jonathan]

Circumvented this issue by adding: partman-partitioning/new_size

d-i partman-partitioning/confirm_resize true
d-i partman-partitioning/new_size string max

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275740

Title:
  Installer fails when preseeding 'partman-partitioning/confirm_resize'

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1957010] [NEW] After upgrade to FlameShot 11, complains about bad config file and system tray icon is missing

[Jonathan Kamens]

Public bug reported:

After upgrade from Flameshot 0.10 to Flameshot 11, upon login I get a
pop-up notification telling me that there's an error in the Flameshot
configuration file and it's reverting to the default settings, but then
there's no Flameshot icon in the system tray and seemingly no way to
bring up the Flameshot UI -- opening the Flameshot app doesn't do
anything. Note however that there's a flameshot process running in the
background.

I had to trash ~/.config/flameshot and then kill and restart Flameshot
to get it back.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: flameshot 11.0~rc1+ds1-2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 10 16:26:23 2022
InstallationDate: Installed on 2019-08-16 (878 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: flameshot
UpgradeStatus: Upgraded to jammy on 2021-11-09 (62 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

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


** Tags: amd64 apport-bug jammy regression-release

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957010

Title:
  After upgrade to FlameShot 11, complains about bad config file and
  system tray icon is missing

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956850] [NEW] Please upgrade to GNU mailutils 3.14 to fix incorrect time zones in Date headers of sent messages

[Jonathan Kamens]

Public bug reported:

I just ran into this bug: https://savannah.gnu.org/bugs/?61239 . In
particular, apticron used the mailutils version of /usr/bin/mail to send
me an email message, and the Date header in the email message had a
completely bogus UTC offset in it.

This bug is fixed in mailutils 3.14.

Please upgrades mailutils to 3.14 or at least pull the patch for this
bug:

http://git.savannah.gnu.org/cgit/mailutils.git/commit/libmailutils/datetime/utcoff.c?id=305b124c78459fe1d89a6ed4ebf30a955d530a4c

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mailutils 1:3.13-1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan  8 22:40:41 2022
InstallationDate: Installed on 2019-08-16 (876 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: mailutils
UpgradeStatus: Upgraded to jammy on 2021-11-09 (61 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: mailutils
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug jammy upgrade-software-version

** Bug watch added: GNU Savannah Bug Tracker #61239
   http://savannah.gnu.org/bugs/?61239

** Also affects: mailutils via
   http://savannah.gnu.org/bugs/?61239
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956850

Title:
  Please upgrade to GNU mailutils 3.14 to fix incorrect time zones in
  Date headers of sent messages

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1955485] [NEW] install crashed: Grub

[jonathan chetwynd]

Public bug reported:

DK
system did not install...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 21 14:43:20 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955485

Title:
  install crashed: Grub

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

No longer reproducible for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953209] [NEW] ICS imported into GNOME calendar (Google Calendar) with UTC start and end times breaks if you edit it

[Jonathan Kamens]

Public bug reported:

1. Your local computer should be in a time zone other than UTC.
2. Save the attached sample.ics to your Desktop.
3. Double-click on it to import it into GNOME Calendar.
4. Save the imported event. Observe that it is saved at the correct time in 
your calendar.
5. In GNOME calendar, click on the event and click edit.
6. Expand the start and end time sections and observe that the times next to 
"Starts" and "Ends" are the UTC times for the event, while the times in the 
time pickers are the correct time in the local time zone.
7. Click the "Done" button without actually changing anything and observe that 
the event moves to the incorrect time, interpreting the original UTC times of 
the event as local times.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-calendar 41.1-1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  3 21:28:09 2021
InstallationDate: Installed on 2019-08-16 (840 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: gnome-calendar
UpgradeStatus: Upgraded to jammy on 2021-11-09 (24 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

** Affects: gnome-calendar
 Importance: Unknown
 Status: Unknown

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


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

** Attachment added: "sample ICS file to demonstrate bug"
   https://bugs.launchpad.net/bugs/1953209/+attachment/5545308/+files/sample.ics

** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #755
   https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/755

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953209

Title:
  ICS imported into GNOME calendar (Google Calendar) with UTC start and
  end times breaks if you edit it

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly

[Jonathan Kamens]

1) ~/.local/share/gnome-shell/extensions is empty

2) I reproduced this issue with Chromium and there is no Chromium crash
in /var/crash, nor is there an error report for Chromium tied to my
whoopsie ID.

Since the chromium snap is provided by Canonical and this issue is
reproducible with Chromium does that mean it's no longer an "Invalid"
issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952557

Title:
  Jammy after logging out of wayland session and back in Chrome says it
  wasn't shut down correctly

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952619] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()

[Jonathan Kamens]

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

It's hard to see why the retracing service marked this as a duplicate of
1751508. I'm fairly certain it is not.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952619

Title:
  Xwayland crashed with SIGABRT in __libc_start_call_main()

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

(Though why _Wayland_ is crashing when I'm trying to log into an _Xorg_
session and the options menu on the login screen says that I have Xorg
selected remains a mystery.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

Problem still occurs with mprisindicatorbutton, batime, and
allowlockedremotedesktop completely uninstalled. Can't uninstall multi-
volume because neither Extensions app nor extensions.gnome.org say it's
installed.

Probably relevant crash:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1952619

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly

[Jonathan Kamens]

I removed 'mprisindicatorbut...@jasonlg1979.github.io',
'bat...@martin.zurowietz.de', and 'allowlockedremotedesk...@kamens.us',
but GNOME doesn't seem to think I have  'multi-volume@tigersoldier'
installed, so I'm not sure where you got that from or what to do with
it. See attached screenshot of Extensions app. I also looked on
extensions.gnome.org and it also doesn't list it as an installed
extension.

With the other three extensions removed completely the problem still
occurs even after two logout / login cycles after removing the
extensions to ensure they're completely purged.

Regarding the crash instructions you sent, there is in fact a Chrome
crash in /var/crash that looks relevant but of course I can't report it
with ubuntu-bug because Chrome is not an Ubuntu package. There are no
crashes on errors.ubuntu.com for my Whoopsie ID, and I've already got
the workaround from bug 994921.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952557

Title:
  Jammy after logging out of wayland session and back in Chrome says it
  wasn't shut down correctly

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952557] Re: Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly

[Jonathan Kamens]

** Attachment added: "screenshot showing no multi-volume@tigersoldier"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952557/+attachment/5544070/+files/extensions%20app.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952557

Title:
  Jammy after logging out of wayland session and back in Chrome says it
  wasn't shut down correctly

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952557] [NEW] Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly

[Jonathan Kamens]

Public bug reported:

In Jammy when I have Chrome running and I log out of a Wayland session
and then log back in and restart Chrome it says it wasn't shut down
correctly.

I'm pretty sure in earlier releases Chrome was given the opportunity to
shut down cleanly when I logged out, but :shrug: I could be remembering
this incorrectly.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 28 11:17:25 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (834 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 40.5-1ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952557

Title:
  Jammy after logging out of wayland session and back in Chrome says it
  wasn't shut down correctly

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952555] Re: Flameshot can't take screenshots, 22.04, wayland

[Jonathan Kamens]

Screenshots work in Xorg session.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952555

Title:
  Flameshot can't take screenshots, 22.04, wayland

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952556] [NEW] Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

Public bug reported:

On Jammy, I log out of a Wayland session, click my name on the login
screen, go down to the options menu and select Ubuntu on Xorg, enter my
password, get "Oh no! Something has gone wrong. A probleme has occurred
and the system can't recover. Please log out and try again. [Log Out]" I
click the log out button and log in again, and I'm logged into a Wayland
session. Why was I logged into a Wayland session when I selected Xorg
the last time I tried to log in?

This issue is intermittent I had been able to log into an Xorg session
just a few minutes prior.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 28 11:10:10 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (834 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 40.5-1ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952556] Re: Jammy, attempt to log into Xorg session, "Oh no! Something has gone wrong."

[Jonathan Kamens]

I logged out immediately after logging in again as described above, then
went to log in again and checked the options menu, and it correctly had
"Ubuntu on Xorg" selected as my session type, but when I finished
logging in I was in a Wayland session, not an Xorg session. So for some
reason my selection of Xorg as my desired session is being ignored?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952556

Title:
  Jammy, attempt to log into Xorg session, "Oh no! Something has gone
  wrong."

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1952555] [NEW] Flameshot can't take screenshots, 22.04, wayland

[Jonathan Kamens]

Public bug reported:

With all current packages from Jammy, Flameshot does nothing when I
click on the top bar icon and select "Take screenshot". If, after doing
that, I click on the icon again and select "Quit", *then* as Flameshot
is exiting it pops up a notification that says "Unable to capture
screen".

There's some discussion that seems relevant at
https://github.com/flameshot-org/flameshot/issues/1910, but that
discussion claims screenshots work in Flameshot 10.2, and that appears
to be the version currently in Jammy, so I'm not sure why it's not
working.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: flameshot 0.10.2+ds1-1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 28 11:02:58 2021
InstallationDate: Installed on 2019-08-16 (834 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: flameshot
UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952555

Title:
  Flameshot can't take screenshots, 22.04, wayland

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947723] Re: /dev/ttyUSB? port lost on upgrading to 21.10

[Jonathan Wheeler]

Confirmed working on the latest -proposed 5.13.0-1011-raspi with my FTDI
USB-to-TTL device. Thank you! Changed the tag to verification-done-
impish.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947723

Title:
  /dev/ttyUSB? port lost on upgrading to 21.10

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947905] Re: mate-screensaver SegFault when it autostarts. Prevents system from sleeping or exiting sleep

[Jonathan Polak]

This bug affects both AMD and Intel architecture. this bug is on AMD,
the linked duplicate bug was on intel architecture.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947905

Title:
  mate-screensaver SegFault when it autostarts. Prevents system from
  sleeping or exiting sleep

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1948031] [NEW] Screensaver SegFault (libmate-menu & mate-screensaver)

[Jonathan Polak]

Public bug reported:

Screensaver crashes -- then fails to lock screen -- here is syslog

Oct 20 19:07:44 ThinkPad-T460s acpid: input device has been disconnected, fd 21
Oct 20 19:07:44 ThinkPad-T460s dbus-daemon[2431]: [session uid=1001 pid=2431] 
Successfully activated service 'org.freedesktop.Notifications'
Oct 20 19:08:13 ThinkPad-T460s kernel: [ 4398.269137] mate-screensave[2896]: 
segfault at 0 ip 7fefaf1d2b07 sp 7ffd19181278 error 6 in 
libmate-menu.so.2.4.9[7fefaf1cf000+d000]
Oct 20 19:08:13 ThinkPad-T460s kernel: [ 4398.269150] Code: da fe ff ff e8 8a 
d6 ff ff 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 f0 83 07 01 c3 0f 
1f 40 00 f3 0f 1e fa 48 89 f8  83 07 01 c3 0f 1f 40 00 f3 0f 1e fa f0 83 2f 
01 74 06 c3 0f 1f
Oct 20 19:08:13 ThinkPad-T460s systemd[1]: Starting Process error reports when 
automatic reporting is enabled...
Oct 20 19:08:15 ThinkPad-T460s mate-session[2434]: WARNING: Detected that 
screensaver has left the bus
Oct 20 19:08:15 ThinkPad-T460s dbus-daemon[2431]: [session uid=1001 pid=2431] 
Activating service name='org.mate.ScreenSaver' requested by ':1.55' (uid=1001 
pid=2892 comm="mate-power-manager " label="unconfined")
Oct 20 19:08:15 ThinkPad-T460s dbus-daemon[2431]: [session uid=1001 pid=2431] 
Successfully activated service 'org.mate.ScreenSaver'

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: libmate-menu2 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Thu Oct 21 07:31:01 2021
InstallationDate: Installed on 2016-07-23 (1915 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: mate-menus
UpgradeStatus: Upgraded to impish on 2021-10-14 (6 days ago)

** Affects: mate-menus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948031

Title:
  Screensaver SegFault (libmate-menu & mate-screensaver)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs