Same here: can't appear to install anything new
zfs-2.1.5-1ubuntu6~22.04.4
zfs-kmod-2.2.0-0ubuntu1~23.10.2
I'm not seeing any time-to-fix notices
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Description:Ubuntu 20.04.2 LTS
Release:20.04
First occurrence. Using text editor after starting from hibernation.
GIMP was still running in the background with low res scanned doc.
Months of error free graphics since graphics-card upgrade which I don't
believe
Public bug reported:
I was just upgrading from 16 LTS to 18 LTS to 20 LTS and this popped up.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: tex-common 6.09
ProcVersionSignature: Ubuntu 4.15.0-154.161-generic 4.15.18
Uname: Linux 4.15.0-154-generic x86_64
ApportVersion:
Public bug reported:
The fading happens online at . But it also happens offline in games.
Using Ubuntu 20.04
Unable to locate package pkgname
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux
Public bug reported:
On attempted upgrade from 18.04LTS to 20LTS
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: wireguard-dkms 1.0.20201112-1~20.04.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Public bug reported:
This is just happening after installing fd-find
ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: fd-find 8.1.1-1
ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
Uname: Linux 5.8.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
AptOrdering:
Follow post of a work around that automatically enables the resolution I
want.
I added a file named: 45custom_xrandr_settings
in folder: /etc/X11/Xsession.d
containing:
xrandr --newmode "Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync
-vsync
xrandr --addmode HDMI-1-1 "Mode 0"
Public bug reported:
No audio at all
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.10
output from: grep . /sys/class/drm/*/modes > modes.txt
** Attachment added: "modes.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+attachment/5428462/+files/modes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: "NvidiaBugReportLog.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427749/+files/NvidiaBugReportLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427744/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427757/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427752/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427755/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
apport information
** Attachment added: "nvidia-settings.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427764/+files/nvidia-settings.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427742/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
Title:
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427765/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427763/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427747/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
Title:
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427761/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
Title:
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427760/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
apport information
** Tags added: apport-collected ubuntu
** Description changed:
The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4,
the max resolution presented in the Settings app is 1920x1080, and this
resolution is the one that it uses. Switching between the
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427741/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427753/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427759/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427745/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427746/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
Title:
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427748/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427754/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427750/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901470
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1901470/+attachment/5427743/+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/1901470
Title:
** Attachment added: "after xrandr --addmode"
https://bugs.launchpad.net/ubuntu/+bug/1901470/+attachment/5427131/+files/Screenshot%20from%202020-10-26%2013-23-41.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4,
the max resolution presented in the Settings app is 1920x1080, and this
resolution is the one that it uses. Switching between the Nvidia driver
or the Intel driver (laptop has low-power intel gpu too)
@mlx I'm running eth0 in bridge, and also using a tunnel broker ipv6
tunnel like the original poster. How would I go about running the
testing kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm having the same issue, including on multiple raspberry pi
3s, one with an IPv6 tunnel from tunnelbroker.net, and one without. It
can be triggered by a lot of IPv4 traffic for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've actually found if you keep toggling the switch it will eventually
work. Sometimes it only takes a couple or other times I've clicked it
30 times.
Before I discovered this I was removing and re-adding my devices to get
them to reconnect.
--
You received this bug notification because you
** Description changed:
New MATE 20.04 installation with all original settings for Power Management
and Screensaver on desktop computer. After awakening computer from Screensaver,
explosion of log entries in syslog fills up root partition (normal free space
is 20GB). If explosion does not
** Description changed:
New MATE 20.04 installation with all original settings for Power Management
and Screensaver on desktop computer. After awakening computer from Screensaver,
explosion of log entries in syslog fills up root partition (normal free space
is 20GB). If explosion does not
** Description changed:
New MATE 20.04 installation with all original settings for Power Management
and Screensaver on desktop computer. After awakening computer from Screensaver,
explosion of log entries in syslog fills up root partition (normal free space
is 20GB). If explosion does not
Any other suggestions for what I should try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
Title:
[Dell Venue 11 Pro 7140] Trackpad does not work
To manage notifications about this bug go
Gave it a go - similar results to what happens when I first power it up
and log in - the trackpad controls the pointer for a few seconds then
stops once the desktop (I assume) is done loading.
Is there any kind of command to find out what devices X and/or gnome is
responding to? It almost feels
No change. Still stops working after a few seconds once the full
desktop is active. Also I notice once it stops working at that point,
if I log out the trackpad continues to not work at the logon screen.
Rebooting the system brings back trackpad functionality until I log back
in.
--
You
I assume you mean output from hid-recorder - I'll attach the 4 files one
at a time:
This one contains hidraw0 which is the touchpad input - data in it
includes me moving my finger on the touch pad.
** Attachment added: "hidraw0"
This last one is hidraw3 - I have NO CLUE what this one is.
** Attachment added: "hidraw3"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370367/+files/hidraw3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This one is hidraw1, it is the keyboard (see sample keypresses in the
output)
** Attachment added: "hidraw1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370365/+files/hidraw1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is hidraw2 which is the touch screen, I let it record me touching
and moving my finger on the screen.
** Attachment added: "hidraw2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877655/+attachment/5370366/+files/hidraw2
--
You received this bug notification because you are a
vanvugt: Well, I ran into a little issue. I went ahead and did a
reinstall of ubuntu (at the point when I submitted my original bug, I
was running PopOS). Before ANY updates, the trackpad works as it should
until I launch software center (or even dmesg -w). The instant I run
one of those, the
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369853/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369849/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369851/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
Title:
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369852/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369847/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I should note - I did try out xserver-xorg-input-synaptics yesterday
prior to getting your email, it had no effect
One thing I did find, I'm not sure if it has any bearing, but my current
kernel is:
5.4.0-7626-generic
With this kernel, as I mentioned before I could move the trackpad at the
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369848/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369850/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369841/+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/1877655
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369838/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369845/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369843/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369842/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
apport information
** Tags added: apport-collected ubuntu
** Description changed:
I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery
dock. PopOS 20.04 fully updated. I have experienced this bug on stock
Ubuntu 20.04 as well as Kubuntu 20.04.
When at the login
apport information
** Attachment added: "DkmsStatus.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369839/+files/DkmsStatus.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369846/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369844/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
Title:
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1877655/+attachment/5369840/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877655
Title:
I have no idea what sub group/package this belongs in. I know it
affects Gnome and KDE on Xorg. I don't know if GDM (or whatever now
handles the login process) does differently from the full gnome that
allows the trackpad to at least partially work (movement, but not button
clicks)
**
Update note: I just rebooted again, I somehow didn't notice, but during
the login window currently, I can move the pointer with the trackpad,
but the left/right click doesn't work. Once logged into the actual
desktop the trackpad (still) completely ceases to work. Just wanted to
fix that.
--
I am seeing this issue with the stock kernel in Ubuntu 20.04 on a Dell
Venue Pro 7140
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846539
Title:
[broadwell-rt286, playback] Since Linux 5.2rc2
Public bug reported:
I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery
dock. PopOS 20.04 fully updated. I have experienced this bug on stock
Ubuntu 20.04 as well as Kubuntu 20.04.
When at the login page, the trackpad and keyboard operate as they
should. Once the login
I notice that the output from setupcon mentions loading the font twice.
That seems to correspond to this fragment of code in setupcon:
# FONTFILES
FONTFILES=''
if [ "$FONT" ]; then
for f in $FONT; do
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
Public bug reported:
When I specify a large font file using the FONT variable in .console-
setup, setupcon fails to load the font, reporting "putfont: KDFONTOP:
Invalid argument". If I specify the same font by setting CODESET,
FONTFACE, and FONTSIZE, the setupcon loads it fine.
For instance, if
** Patch removed:
"qtwayland-opensource-src-package-qtwayland-private-headers-as-qtwayland5-private-dev-package.diff"
** Patch added:
"qtwayland-opensource-src-package-qtwayland-private-headers-as-qtwayland5-private-dev-package.diff"
Upon further inspection I think qtwayland-opensource-src is the package
this bug should be filed against.
** Package changed: qtbase-opensource-src (Ubuntu) => qtwayland-
opensource-src (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Trying to build QGNOMEPlatform
(https://github.com/FedoraQt/QGnomePlatform/releases) fails with the
following error message:
Project ERROR: Unknown module(s) in QT: waylandclient-private
Running `dpkg -L qtbase5-private-dev | grep -i wayland` shows nothing,
running
This affects me, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854601
Title:
Ubiquity installation says "You can try Ubuntu without making any
changes to your computer directly from this CD
Public bug reported:
Couldn't play my music because gstreamer wasn't installed. After
installation of gstreamer music can play but can't be heard. System
settings have dummy output as the selected sound card.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
Public bug reported:
I was installing Ubuntu Mate 19.04 on a Dell XPS17 which has 16 GB RAM
and 2 1TB SHDD drives.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion:
Broken on 19.04, at least under unity-desktop. Downgrading works,
however the notification icon is a red circle with a diagonal line going
through it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Chris: Thank you for your quick response.
Graphics: Intel® HD Graphics 520 (Skylake GT2)
The install was an upgrade from 18.04 LTS to 18.04 to 19.04. After the
upgrade was completed, I could not understand why my Dell laptop screen
was blanking out. I discovered that my "color management
Public bug reported:
The screen started to "blank out" (goes to a black screen) after a few
seconds of no input. For example, started to read a webpage and the
screen suddenly went to black after less than ten seconds. Or, when
typing this bug report the screen display would shut off. After
@brian-murray thanks for the suggestion. Have done you suggest but
apport-cli on the system with the GUI does not seem to allow an existing
bug to be updated with the info, so rather than generating a new bug
report am copying the file generated by apport-cli --save below.
ProblemType: Bug
Sorry I cannot run apport-collect as the machine has no GUI. I have
tried the command on the console and via ssh but the resulting text-mode
screen seems to prevent me entering my email address to log in.
I also tried apport-cli but it had the same problem with the same
authentication screen.
As
Setting package to linux kernel as advised for a filesystem issue.
Ran apport-collect -p linux 1828712 per the instructions but I don't
know that it worked as machine has no GUI.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of
Public bug reported:
Command
sudo mount -t vfat flop1 /mnt/flop1
fails. The image is readable but the log shows many I/O errors such as
May 12 07:57:24 us64a kernel: [69801.335823] print_req_error: I/O error, dev
loop0, sector 0
May 12 07:57:24 us64a kernel: [69801.337707] print_req_error:
Here's one (e.g. my) case:
Asus AC1200 USB-AC53 Nano wifi adapter. No linux driver available from
the manufacturer. But there are open-source drivers available that work
well, but that require the -D parameter in order to be able to use
wpa_supplicant.
Quoting
Re range of possible values for -D option:
>From man wpa_supplicant:
AVAILABLE DRIVERS
A summary of available driver backends is below. Support for each of
the driver backends is
chosen at wpa_supplicant compile time. For a list of supported driver
backends that may be used
Effect also observed if tab begins playing audio after reader mode is
opened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813170
Title:
Opening reader mode causes audio distortion in all other
Observed that effect seems to resolve if audio/video is stopped for a
short while (~5 minutes in this case).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813170
Title:
Opening reader mode causes
Public bug reported:
Description:Ubuntu 18.10
Release:18.10
firefox:
Installed: 64.0+build3-0ubuntu0.18.10.1
Candidate: 64.0+build3-0ubuntu0.18.10.1
Version table:
*** 64.0+build3-0ubuntu0.18.10.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64
I have exactly the same problem, on a clean install of Bionic/18.04
Desktop AMD64, with a locally-attached (USB) 2TB SATA hard drive which
works perfectly AFAIK for all functions other than Deja Dup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've struggled through this several times now. I don't have a definitive
solution but the general routine was something like this. When you asked
to enroll the machine owner key to sign the kernel module there is an
interface that popups up and waits for user input. I tried this in in a
shell-only
In reply to #105
Have tested reverting that fix and it just re-introduces the bug
"After locking screen there is no input field to type password for unlock"
Having no input field is worse.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
HOLY COW This bug was reported in 2010 AND STILL HAS NOT BEEN FIXED
! Totally unacceptable.
To make sure we have a common understanding. I have linux on partition
sda9 and "other" version of linux on partitions sda8, sdb8, and sdb9.
The menu entries for ALL the "other" linuxes all specify
Public bug reported:
sudo apt-get install curl python-software-properties
[sudo] password for pedro:
Reading package lists... Done
Building dependency tree
Reading state information... Done
curl is already the newest version (7.47.0-1ubuntu2.8).
The following packages were automatically
This has happened to me a couple times, I dont have a clear answer how
to fix it yet, but the dkms install hangs waiting for input at the
secure-boot update screen, but it seems to open in different tty so I
end up having to kill the process to regain control of the terminal. You
can see
As per https://patchwork.kernel.org/patch/10384111/ message from Bluez
mailing list, editing 97-hid2hci.rules as follows works around the new
uevents added to the kernel in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65
It appears that the Ubuntu policy is that, if dumpcap is to be given
elevated privileges, it be executable only by its owner (presumably
root) and by members of the group that owns it, which appears to be the
"wireshark" group. The intent is presumably not to give *everybody* on
the system
Duplicate of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767603
Title:
BCM2046B1 and hid2hci generates highcpu usage due to udev
It's a known kernel bug that Dell bluetooth is broken in kernels >=4.14,
so sticking with the old kernel that works for now.
Kernel bluetooth bug causes bluez 97-hid2hci.rules udev rule to fail.
systemd-udevd has always consumed 100% whenever a udev rule fails (could be
argued that's also a bug
1 - 100 of 891 matches
Mail list logo
