** Tags added: community-security
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975660
Title:
Disabling fprintd.service prevents boot
To
I first disabled it by including fprintd in a list of packages to purge,
in an installation script. There, the service wasn't expressly
disabled; the package was simply purged (apt purge fprintd).
That machine then suffered similar boot hangs, so I installed a new
system and debugged the script b
Public bug reported:
Disabling fprintd.service prevents boot.
System: Ubuntu Desktop 22.04
Behavior: Rebooting immediately after disabling and masking
fprintd.service, fails.
A series of [DEPEND] messages scroll past in tty1 early in the boot
process, too quickly to read but that appear to be
Public bug reported:
Autogenerated by install script.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: sudo 1.9.9-1ubuntu2
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
CasperMD5CheckRe
I've already disabled the .timer units for the Pomodoro sounds.
I'll investigate the kernel angle.
Here's an odd angle: Could this be a Vulkan issue? I picked up on a
thread that pre-Haswell GPUs and integrated CPUs may have trouble
implementing Vulkan. Graphics are discrete but my CPU is a Xe
Thanks for the thoughts.
I've got enough clutter around not to need to spend several hundred
dollars for a test card.
I also have no idea how to compile a new kernel, but do know that my
being asked that confirms someone goofed.
Anyway, maybe something else is afoot. Some noodles, please let me
Here's the other file ...
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1970072/+attachment/5584573/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Thanks. I'm glad to learn that the problems could be discerned.
I made the change you suggested to /etc/default/grub and did <# update-
grub>.
I also removed the Fildem menu GNOME extension, messages about which
preceded every crash.
Attached are the logs from te latest hang, which occurred ju
Regarding 22.04, please advise what reason exists to think it might be
better.
Also, please advise why I should spend days reinstalling because of
someone else's failure instead of the failure being addressed.
Besides, note https://bugs.launchpad.net/subiquity/+bug/1970140. The
22.04 server inst
Trying the attachment again.
The interface won't allow designation of more than one.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970072/+attachment/5584043/+files/lspci.txt
--
You received this bug notification because you are a member of Ubu
Regarding the file request, please see attached.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970072/+attachment/5584042/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Except that I'm experiencing the issue with X, not Wayland.
Also, Ubuntu 20.04, not Fedora
** This bug is no longer a duplicate of bug 1698083
Maximize vertically/horizontally doesn't work (in some apps) if configured
via middle-click
--
You received this bug notification because you are a
This actually is not a duplicate bug because I have successfully mapped
ctrl-alt-v to maximize the active window.
This bug concerns the gsettings configuration of the middle mouse
button.
Specifically, that the selected option behaves as another.
FYI, this arose because the interface no longer m
Public bug reported:
While no audio at all is playing, pulseaudio loops through its
configuration and also loops through complaints about latency,
generating tens of thousands of messages per hour, writing constantly to
disk and bringing system performance to a crawl, culminating in a GUI
freeze.
I have a very similar issue.
See https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970072
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919071
Title:
Gsd media keys crashed SIGSEGV
To m
Public bug reported:
A fresh install of Ubuntu 20.04.4 has GUI freezes frequently (i.e., a
dozen times daily) at inconsistent intervals and times, and not
obviously in response to any particular user input. The system then is
unresponsive to user input, although the mouse cursor does continue to
Public bug reported:
Simply, configuring the middle mouse button in dconf-editor to maximize
a window vertically when its title bar is middle-clicked, causes the
window instead to maximize fully.
In dconf-editor, the setting is
/org/gnome/desktop/wm/preferences/action-middle-click-titlebar.
The
Public bug reported:
The installer for Ubuntu Server 20.04.4 has no ability to designate an
existing EFI system paretition as the boot partition.
The volume is already partitioned and has a valid 512MB EFI system
partition formatted as FAT32 and with type code ef00 at /dev/sda1. The
installer st
@till-kamppeter, I'm not certain what you mean by the "upstream source."
The printer auto-installed when I installed Ubuntu 20.04 shortly after
its release.
After your post, I did:
# apt purge cups cups-client cups-bsd
# apt purge hplip hpijs printer-driver-gutenprint
# apt autoremove
# reboot
#
Public bug reported:
I printed yesterday.
I updated Ubuntu 20.04.3 this morning.
The system now does not detect the HP LaserJet P2055dn to which it has
been connected for years.
The output of the command "apt-cache policy cups" is:
cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu
Try nvidia-graphics-driver-390.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892973
Title:
[nvidia] Repeated screen freezes with GeForce GT 640 (GK107)
To manage notifications about this bug go t
Some additional information:
When the boot sequence is
- GRUB boot to recovery mode
- Drop to root prompt
- Remove a driver and install a driver
- Exit root prompt (Ctrl-D)
- Resume normal boot as per the recovery mode menu
Then the display comes up at a degraded resolution (1024x768) but no
gnom
Thanks for responding.
Some delays in responding because of client demands, then because the
storage configuration of the machine was incomplete and the debug files
couldn't be networked, then because the incessant gnome-session hangs
required a hard-reset at nearly every step along the way.
The
Public bug reported:
Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia-
driver-440. Both drivers expressly support the hardware. All varieties
of desktop environment (Xorg, Gnome Classic, Ubuntu)
Bug summary
Screen hangs randomly and iretrievably with the only possibility of reco
24 matches
Mail list logo
