I was getting this problem in 12.10 and I continued to get it after an
upgrade to 13.04.
Today in 13.04 I edited /etc/rc6.d/S90reboot to run sh and examined the
situation. (If I simply ran sh, I got no output, just like other
messages in that script aren't displayed. I ended up using sh
In 14.10 amd64, mountall keeps running, causing init to keep
/var/log/upstart/mountall.log open for writing, which prevents root from
being remounted read-only.
These things are easy to examine by adding a /bin/sh line to /etc/init.d/reboot
in do_stop() before reboot -d -f -i. Then when you
Adding sleep 2 results in a different error: init: /etc/init
/plymouth-upstart-bridge.conf:18: Unknown stanza. I wonder if this
causes plymouth-upstart-bridge to not run at all? I have not encountered
any problems running like that for many months, but I wonder if some
situations could lead to
I solved the problem. This was wake on LAN. When I ran sudo ethtool eth0 the
output included:
Supports Wake-on: pumbg
Wake-on: ug
From the ethtool man page:
u Wake on unicast messages
g Wake on MagicPacket™
This was wake on unicast messages.
This also affects me in vivid. The problem is that min_fanval wasn't set. Up
above it is set inside an
if [[ -n ${fan} ]] block, so it's not set if you're not using fan RPM
sensors. This was fixed in r6255: http://lm-sensors.org/changeset/6255
--
You received this bug notification because you
I can reproduce this with v4.1-rc1-vivid. I had to uninstall
nvidia-340-updates because the DKMS module failed to build and boot hung
while it was installed. So, I was using nouveau for my GeForce 8600GT
PCI express graphics card.
I can't reproduce it if not running X, or running X, twm and xterm
Public bug reported:
I'm running 64-bit Ubuntu 15.04 on a Gigabyte GA-P35-DS3R rev 1.0
motherboard with BIOS F13. I also have 32-bit Windows 7 SP1. If power
was fully cut, including standby power, and Windows has not been run
since then, Ubuntu will quickly wake from S3 sleep without any apparent
This happened to me once when I was trying to connect to WiFi from the
command line. It seemed to happen because multiple wpa_supplicant
processes were running. You could try ps xa | grep wpa_supplicant to
see if you have multiple processes running. Doing sudo killall
wpa_supplicant stopped it.
Public bug reported:
Occasionally the onboard gigabit Ethernet on this Gigabyte GA-P35-DS3R
rev 1.0 motherboard doesn't work after suspend. This happens less than
one out of ten times. Over the last several Ubuntu releases, sudo
ifconfig eth0 down followed by sudo ifconfig eth0 up has always been
This keeps happening to me occasionally, less than one out of ten times.
Over the last several Ubuntu releases, sudo ifconfig eth0 down
followed by sudo ifconfig eth0 up has always been enough to re-
establish connectivity. A long time ago, I sometimes had to unload and
reload the r8169 module.
I refuse to test this with the latest upstream kernel. That is because
the bug happens rarely and the upstream kernel breaks other stuff. I
would have to use Ubuntu for a prolonged period with the upstream
kernel, putting up with that brokenness, or I would have to go into
suspend and wake many
I never experienced any significant problems because of this bug. It
only results in those error messages. If your system fails to boot or
other things crash, that is probably due to a different unrelated issue.
The "sleep" in /etc/init/plymouth-upstart-bridge.conf does make these
error messages
Public bug reported:
In /etc/X11/Xsession.d/70gconfd_path-on-session these lines fail if
there is a space in ${DESKTOP_SESSION}:
export MANDATORY_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.mandatory.path
export DEFAULTS_PATH=${GCONF_PREFIX}/${DESKTOP_SESSION}.default.path
The error output to
This seems to be a bug in gconf-common. LXDM sets the DESKTOP_SESSION
environment variable to the Name string from the desktop file, and
/etc/X11/Xsession.d/70gconfd_path-on-session cannot handle the space due
to lack of quoting.
I'm not sure if setting DESKTOP_SESSION to the Name from the
I'm getting a similar bug in 16.04 on my Inspiron 6400 with X1300 and a
1680x1050 display. I have disabled graphical overlays during boot
because I prefer to see boot text. Corruption starts after the switch
from ordinary VGA text mode to a high resolution text mode which I
assume is implemented
I'm also having this problem copying to an external USB 3 drive, with
Nemo (Cinnamon file manager) copies around 35 MiB/s on my Q6600 CPU.
big_writes helped, but although file copying via Nemo sped up to around
60 MiB/s, it was still CPU bound. Copying via pv < source_file >
dest_file is faster
Public bug reported:
If audio is muted, then instead of the volume level arcs in front of the
speaker icon, there is an x. Mute button needs to be pressed to get
sound. Volume keys still affect the volume setting, but there is no
visual indication of that on the icon, or any audio indication
Public bug reported:
I used Ubuntu 16.04.1 LTS dump and restore version 0.4b44-7 to dump and
restore a Raspbian Jessie ext4 file system from an SD card. After
restoring, the _CACHE_00?_ files from ~/.cache/mozilla/firefox//Cache/ have differing contents. On the original file system they
consist
After upgrading to Ubuntu 16.10 I removed the r8168-dkms package so I
could see if this bug still exists in 4.8.0 kernels. I upgraded on
October 13th, and everything worked fine until today, October 24th.
After waking from sleep eth0 appeared up according to ifconfig, but I
had no connectivity and
I wonder if this is the same bug which I am seeing on my Dell Inspiron
6400 laptop with Radeon X1400 video. Occasionally I get white lines
which are very similar to the
https://www.youtube.com/watch?v=nx2-Fvihzxg video posted at the
beginning. The only difference is that more lines are present at
Public bug reported:
If my /etc/network/interfaces settings for wlan0 include a "hwaddress
ether" line, then running ifup for that interface fails at the very end,
after successfully authenticating with the access point. Here is what
happens:
systemd[1]: Started ifup for wlan0.
This seems to be an old bug, which is also mentioned elsewhere:
https://unix.stackexchange.com/questions/26126/spoofed-mac-address-ignored-by-wpa-supplicant
https://bugs.launchpad.net/neutron/+bug/1193972
Another symptom of this bug is probably inability to connect if you need
the changed MAC
Public bug reported:
I'm running my ncursesw application, displaying a black background. When
the screen or a region scrolls up by one line, empty areas of the screen
in the newly visible line show the default white background of gnome-
terminal.
If I remove the bce capability from the Terminfo
https://bugzilla-attachments.libsdl.org/attachment.cgi?id=1715 does not
fix the issue I reported. I still can't get full screen mode to work
properly. Normally I still get the large scrolling virtual desktop
issue, and with SDL_VIDEO_X11_XRANDR=0 set in the environment things are
even worse.
--
Public bug reported:
If I start with an 80x24 terminal, resize to 80x25 with printf("\e[8;25;80t")
and then quickly send output via Ncurses, then xfce4-terminal crashes:
Vte-0.0:ERROR:/build/vte-jOPZPt/vte-0.28.2/./src/ring.c:370:_vte_ring_thaw_one_row:
assertion failed: (ring->start <
Public bug reported:
I have a GeForce 8600GT card and am using nvidia-340 drivers, version
340.101-0ubuntu0.16.10.1. Going into full screen mode results in a mode
smaller than the displayed area, where the mouse can be used to scroll
the screen viewport around. Returning from full screen mode
Public bug reported:
The first mode change always works, but subsequent mode changes keep
failing. Running xrandr --output DVI-I-2 --mode 1600x1200 to go back to
the native resolution or any other supported resolution fails with:
xrandr: Configure crtc 0 failed
X Error of failed request:
SDL 2 is able to go back to the proper desktop resolution when exiting
full screen if and only if the top left corner of the current viewport
is at the top left of the displayed area. In other words, if I don't
scroll the viewport right or down by going to those edges with the
mouse, or if I
Public bug reported:
When installing an icon using a command such as "sudo xdg-icon-resource
install --novendor --context apps --size 256 synaesthesia.png
synaesthesia", the ownership of the file created at
/usr/local/share/icons/hicolor/256x256/apps/synaesthesia.png is set to
root:root, but the
I'm not able to reproduce this now in Zesty with gnome-terminal
3.20.2-1ubuntu8. Program that was causing problems before is DOSBox SVN
with ncursesw output added, https://github.com/dreamlayers/em-
dosbox/tree/contxt-only but that works fine now. infocmp $TERM shows I'm
using
I'm not able to reproduce this in Zesty xfce4-terminal 0.8.4-1. So, it
seems you're right and this has been fixed. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677961
Title:
I tried installing some old libraries and binaries from Yakkety but even
with that I couldn't reproduce it in Ubuntu 17.04. I don't have any more
Yakkety systems to test on. I also can't reproduce it in 16.04.2 LTS in
Windows 10. I don't think any DOSBox changes could have changed this
either. So
Public bug reported:
In past versions of Ubuntu, the XFCE sensors plugin worked. I just
upgraded to Artful 17.10 and it does not work anymore. The problem seems
to be that settings were lost and cannot be configured anymore. All I
see on the panel is the word "Sensors" in bold. Double clicking
Public bug reported:
I'm opening a raw disk device (like /dev/sdb) with O_DIRECT and then
doing write() calls. The device is actually USB mass storage. Looking at
the USB packets with Wireshark, I see that the write() calls are being
split into multiple SCSI writes. That part is okay I guess. The
Public bug reported:
xfce4-power-manager has a tray icon which shows current status and has a
graph when a battery is inserted. The green bar in the icon should be
showing current battery level, but it varies weirdly. If I place my
mouse cursor over the icon the tooltip which appears shows the
rmmod b43 works in 4.15.0-21-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763967
Title:
rmmod b43 hangs
To manage notifications about this bug go to:
I don't know of any way to make this work with the package from 17.10 /
Artful, but installing the current 1.2.6-1 xfce4-sensors-plugin from
17.04 / Zesty makes the plugin work. No other changes were needed. With
the plugin from Zesty the plugin output on the panel immediately changes
when I
>From http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.9/ I installed:
linux-headers-4.15.9-041509_4.15.9-041509.201803111231_all.deb
linux-headers-4.15.9-041509-generic_4.15.9-041509.201803111231_amd64.deb
linux-image-4.15.9-041509-generic_4.15.9-041509.201803111231_amd64.deb
And booted into
Public bug reported:
When I boot linux-image-4.13.0-36-generic then I get an eth0 interface
and dmesg output includes:
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x42
43)
b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0
b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100
After installing
linux-headers-4.16.0-041600rc4_4.16.0-041600rc4.201803041930_all.deb ,
linux-headers-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
and
linux-image-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
from
Public bug reported:
I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell
Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43" always
hangs. So far I have only tried it while connected to a wireless
network. I immediately disconnect from the wireless network, so it seems
In 4.15.0-13-generic, BCM4321 WiFi works via b43 and BCM4401-B0 b44
Ethernet eth0 exists. So, it seems this has been fixed. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754911
Title:
Bug does not exist in 4.16.2-041602-generic. I did rmmod b43 4 times and
it always succeeded immediately. It never worked properly in
4.15.0-13-generic so I am confident this isn't just random success, and
it means the bug is fixed in upstream.
What older version should I try? Currently I don't
Public bug reported:
In Ubuntu 18.04 this problem did not exist. After upgrading to 18.10 the
backgrounds of system tray icons in the Xfce panel are not drawn
properly on my Inspiron 6400 laptop with ATI/AMD Mobility Radeon X1400
graphics and the open source radeon driver. This problem does not
Compositing was disabled. When I enabled it, the problem was fixed
instantly. I have not seen any more signs of the problem with
compositing enabled. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My main computer with GeForce 8600 GT and driver 340.107-0ubuntu2 had
Compton compositor running via Application Autostart in Session and
Startup. Disabling that, logging out and logging back in brings up some
corruption there as well.
** Attachment added: "Tray corruption on main computer"
My main computer with GeForce 8600 GT and driver 340.107-0ubuntu2 had
Compton compositor running via Application Autostart in Session and
Startup. Disabling that, logging out and logging back in brings up some
corruption there as well.
** Attachment added: "Tray corruption on main computer"
This never happened in 18.04, and started happening after upgrading to
18.10. The keyring daemon when taking 100% CPU on one core also seems to
hang and not respond to applications. I've had Chrome hang on startup,
and I've had ssh and scp hang.
--
You received this bug notification because you
Public bug reported:
If I run sudo fstrim -av I see:
/media/SSD_Data: 2 GiB (2145820672 bytes) trimmed
fstrim: /media/Win7: FITRIM ioctl failed: Bad file descriptor
/: 26.9 GiB (28823887872 bytes) trimmed
/media/SSD_Data is read-write mounted NTFS via ntfs-3g, and /media/Win7 is
read-only
Maybe I was confused. I was just setting up xfce4-sensors-plugin 1.3.0-2
Ubuntu 18.10 and noticed something. When I double-click on the plugin it
opens "Sensors Viewer". If I want to reconfigure the plugin I need to
right click on it and select "Properties". This opens "Sensors Plugin".
The
Public bug reported:
This problem started after upgrading to Ubuntu 19.04. It was not present
with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic
kernel. Ever time during boot there is a null pointer dereference in the
b44 driver for the on-board Ethernet on this Dell Inspiron
Using Geeqie 1:1.4+git20180820-1 in Ubuntu 18.10, I see that it does
render the directory listing window. The problem is that the window
takes a long time to render. During that time I still see a photo and
can go to the next photo via the space bar, but the image overlay with
the histogram and
linux-image-
unsigned-4.20.0-042000-generic_4.20.0-042000.201812232030_amd64.deb is
good but linux-image-
unsigned-5.0.0-05rc1-generic_5.0.0-05rc1.201901062130_amd64.deb
is bad. I'm not sure I'll have time for a git bisect.
--
You received this bug notification because you are a member
Sorry, I mean bug is not present in 4.18.0-16-generic and present in
5.0.0-7-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821564
Title:
b44 Ethernet driver null pointer during
I'm also getting this crash in eoan. Building with a patch made from the
commit linked in the Debian bug report ( https://github.com/projectM-
visualizer/projectm/commit/c87f208c47252b47b117db73cc28a053d5133ffd )
makes it work.
--
You received this bug notification because you are a member of
Right now in 19.10, /lib/systemd/system/fstrim.service runs /sbin/fstrim
--fstab --verbose --quiet , which doesn't cause the service to report
these errors. According to the fstrim man page, for the --fstab option:
"Errors from filesystems that do not support the discard operation,
read-only
Public bug reported:
On my Dell Inspiron 6400 laptop with Mobility Radeon X1400 and built in
Intel HDA audio with STAC9200 codec, audio is normally perfect. Even
with 100% load on both CPU cores audio is perfect. However, while
playing high resolution video, audio has many tiny regular
Public bug reported:
My Inspiron 6400 laptop has a Dell Wireless 1500 Draft 802.11n WLAN
Mini-Card with BCM4321 chip. I was using airmon-ng from aircrack-ng to
enter monitor mode. It claims the chipset is "non-mac80211 device?
(report this!)" but I think that's incorrect information and only
I don't normally use Ethernet on my laptop, and for some reason the b44
module for Ethernet doesn't get loaded normally. So I didn't notice
this. But I'm getting the same problem reported in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821564/comments/8
in Ubuntu 19.10 with
Public bug reported:
PulseAudio currently doesn't see the analog audio output in my Dell
Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
SPDIF output. This is the situation in both "pactl list sinks" and
pavucontrol. I hear no sound from applications, probably because it's
It was easy to fix this by adding the following line to /etc/pulse/default.pa
load-module module-alsa-sink device=hw:0,0
After doing that and rebooting, I had to set the analog device as the
fallback device in pavucontrol. (Before the default.pa change, the SPDIF
device had been the only playback
I did some more investigation and found that without the workaround the
analog output only appears while headphones are plugged in. The SPDIF
output disappears while headphones are plugged in.
The bug has been submitted with this new information at
iommu=soft does not help, and I don't understand why it would help
theoretically when the Core 2 Duo T7400 CPU doesn't have a hardware
IOMMU. The problem seems to be that the 64 MB buffer is allocated beyond
1 GB.
One theoretical good workaround would be to boot up with only 1 GB and
then enable
This problem still exists in Ubuntu Focal Fossa (development branch)
20.04 with linux-image-5.4.0-21-generic. It also exists in linux-image-
unsigned-5.6.2-050602-generic_5.6.2-050602.202004020822_amd64.deb
With linux-image-5.4.0-21-generic I didn't get any error messages after
"insmod b44" in
Public bug reported:
Yesterday I booted into Ubuntu's memtest86+. I wasn't experiencing or
expecting problems, and only wanted to make sure memory is okay after I
had to remove modules to take the PSU out and put it back in. I ran it
twice, and both times it hung at exactly 79% in the first test.
Source package differences between memtest86+ 3ubuntu2 (which does a
whole pass without errors) and 3.1ubuntu1 (which locks up at 79% in test
1) don't seem to explain this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
My it8718 chip measures voltages, fan RPM and temperatures. I want to
monitor what sensors.conf calls temp1, labelled "NBr Temp". I can set
that up via the GUI and it works. But when I log out and back in or
restart the Xfce panel, that shows +3.3V instead, which is in2 in
I don't see a null pointer message but the b44 driver is still broken in
5.4.0-33-generic on my Dell Inspiron 6400:
[ 3148.539194] ssb: Found chip with id 0x4401, rev 0x02 and package 0x00
[ 3148.599317] b44 :03:00.0: Sonics Silicon Backplane found on PCI device
:03:00.0
[ 3148.599414]
Public bug reported:
My Dell Inspiron 6400 laptop has a Synaptics touchpad. If I'm using
xserver-xorg-input-synaptics and I use Control-Alt-Fkey or sudo chvt to
switch to a text virtual console and then switch back to X, the mouse
stops moving via the touchpad. The touchpad seems totally ignored,
Public bug reported:
If I run scrot 1.4-1 to take a screenshot from a MicroVAX with a QDSS display
device running ULTRIX 4.5, I get:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 91 (X_QueryColors)
Value in failed
Public bug reported:
After upgrading to Ubuntu 20.10, VLC started crashing when I tried to
play video. I tried changing to different video output methods, but none
of them worked. In the past, I remember several methods working fine.
In the ffmpeg advanced preferences page, disabling the direct
But, not all VLC video outputs are supposed to use OpenGL, so I don't
see why Mesa is relevant. One of the crash backtraces doesn't involve
Mesa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912030
Public bug reported:
I had a Telegram account created via the official client (telegram-
desktop package) in Ubuntu, where I logged in using a code sent via SMS.
Using telegram-purple for the first time on another PC, I provided the
same mobile phone number, and then Pidgin asked me to input a
This also fixes the Lxdm greeter crash I reported at
https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443. I installed
the pre-release builds from
https://launchpad.net/ubuntu/+source/glib2.0/2.68.1-1~ubuntu21.04.1/+build/21536716
and confirm that the bug is fixed.
--
You received this
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316 is the
bug which is causing this problem. A fix is committed but it hasn't been
released yet for 21.04, and apparently has some test failures in the
proposed queue. In installed the pre-release files from
Seems this should also fix LXDM GTK greeter:
https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1922443
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926316
Title:
lxappearance crashes on launch
Wake worked with kernel 5.11.0-16-generic. So, I guess this 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/1922439
Title:
X hangs after wake on Mobility Radeon x1400
To manage
The problem seems to be /usr/lib/lxdm/lxdm-greeter-gtk crashing at
g_key_file_load_from_file(). Also, lxappearance crashes similarly. This
may be related: https://gitlab.gnome.org/GNOME/glib/-/issues/2361 . But
the crash seems to be triggered by plasma.desktop and twm.desktop in
Public bug reported:
I'm using Audacious media player in Winamp 2.x skin mode. It consists of
two windows: the main window with playback controls, whose title shows
the current track, and the playlist editor window, whose title is
constant. These windows are grouped into one Plasma Task Manager
Public bug reported:
I have a Dell Inspiron 6400 with Mobility Radeon x1400. In Ubuntu 20.10
and earlier, wake from sleep worked properly. In Ubuntu 21.04, X does
not work after wake from sleep. It fails in Plasma, Xfce, Openbox and
Twm. With both Plasma and Xfce the screen is totally black. In
Public bug reported:
In the past I used lxdm on my Dell Inspiron 6400 laptop without
problems. After upgrading from Ubuntu 20.10 to 21.04, lxdm shows a fully
black screen, without even a mouse cursor. Attempts to interact with it
blindly don't work, which suggests it's somehow hanging, and not
The same problem happens on my main PC (with GeForce GT 710 graphics and
460.56-0ubuntu1 driver). I'm now using sddm instead of lxdm on both
systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Wake from sleep works in Xfce and Plasma in Ubuntu 21.04 when using
kernel 5.12.0-051200rc5-generic from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.12-rc5/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
If I start Firefox with in KDE Plasma with kwin compositing disabled,
and the Firefox title bar is disabled via Customize, the whole window
has a border. Otherwise my computer is configured to not have window
borders, and other applications don't have such a border. I don't
I got upgraded back to 470 because new 460 transitional dummy packages
were released, which caused the upgrade. I could have prevented that via
apt-mark hold.
When I was getting these problems with 470 I had
nvidia.NVreg_PreserveVideoMemoryAllocations=1 in my kernel command line,
via
Public bug reported:
Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake
from suspend. It does start running again, but there is no video output. I'm
attaching text for two crashes from kernel log output. First is:
/var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967
Public bug reported:
When I ran Giara for the first time, it gave a button for logging in,
which opened a Reddit login confirmation for Giara in my default
browser, Firefox. After confirming that, Firefox asked me to open a
link in Giara. That failed, with Giara printing:
Error authorizing
Public bug reported:
After installing Giara, when trying to start it I got:
Traceback (most recent call last):
File "/usr/bin/giara", line 69, in
gi.require_version('Handy', '1')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in
require_version
raise
In Ubuntu 21.10 with 5.13.0-16-generic kernel, I don't get any dmesg
errors after I "modprobe b44" and Ethernet works initially at reasonable
speed, but the whole system freezes totally after a few minutes. I
suppose this means the b44 driver still doesn't work properly, because I
don't get such
Public bug reported:
I was trying to use checkinstall to create a package for projectM music
visualizer which I compiled. I already made a tar.xz and was doing "sudo
checkinstall tar -C / -xJf /d/projectm-linux-x86_64-20211102.tar.xz" and
that was failing with a bunch of errors after
No, "pcie_aspm=off" does not help.
I also tried uninstalling broadcom-sta-dkms. It blacklists the b44
module via /etc/modprobe.d/broadcom-sta-dkms.conf and also
https://wiki.debian.org/wl says that b44 is incompatible with wl. This
did not help either.
My laptop seems fine with just having the
I managed to install and use ntfs-3g 1:2021.8.22-3ubuntu1 from Ubuntu
22.04 into Ubuntu 21.10. (It was usable despite failing to satisfy
dependencies, but this is not recommended and I was only doing it as a
test.) Even with that newer version, the same bug still exists. I've
reported the bug at
Public bug reported:
In Ubuntu 21.10 using ntfs-3g 1:2017.3.23AR.3-3ubuntu5 I can create
sparse files which result in the following messages from Windows 10 21H2
disk scanning:
Stage 1: Examining basic file system structure ...
The allocated length 0x41000 is not in multiple of 0x1 for
Public bug reported:
In the File menu, "Load random example" fails, saying "Error: Could not
open examples". This is because examples are in subdirectories of
/usr/share/XaoS/examples, and XaoS is not capable of finding examples in
subdirectories. XaoS looks in /usr/share/XaoS/examples and in a
Public bug reported:
My Dell Inspiron 6400 laptop has HDA Intel audio with a STAC9200 codec.
It has speakers and a headphone jack. Previously when the headphone jack
was unplugged sound came from the speakers, and when headphones were
plugged in, sound came only from the headphones. In Ubuntu
Public bug reported:
I have an Nvidia GeForce GT 710, which requires the legacy 470 proprietary
driver. Both foliate and epiphany-browser display improperly by default. Some
user interface elements are missing, and e-book and web pages are totally
blank. To fix this, I added the following
Public bug reported:
After upgrading to Ubuntu 24.04, Foliate won't start. I get this output:
(com.github.johnfactotum.Foliate:14787): Gjs-CRITICAL **: 19:08:02.419: JS
ERROR: Error: Argument display may not be null
@resource:///com/github/johnfactotum/Foliate/themes.js:110:18
I have reported the bug at
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2062995
In Ubuntu 24.04, I need both GSK_RENDERER=cairo and
WEBKIT_DISABLE_DMABUF_RENDERER=1 to work around this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
98 matches
Mail list logo
