Per coincidence, I worked on this same bug today, as I'm hoping to try
make use of the amdpro legacy OpenCL drivers, which will need amdgpu as
a base.
The issue is Ubuntu is providing newer kernel HWE stacks with amdgpu
driver modules, but failing to keep related Linux firmware packages up
to date
Same issue for me using latest stable NVidia drivers on 20.04 with
latest 7.2 Libre office snap.
I've noticed that only Calc is affected. Impress and Writer are not
affected.
So there must be some calc specific graphics acceleration method causing
high CPU rendering load.
Unlike the orig bug rep
Apologies, launchpad didn't keep the neatly tab separated column format,
but hopefully the script can help others to test.
Attached png of side-by-side comparison of script output.
Only the latency for accessing a single 4K block doesn't seem to differ
too much, but for every other mult-block seq
Hi, to report, also noticed gvfs smb mount being over 10x slower in many
cases depending on the read IO pattern. Seems GVFS alls a lot of
latency. Summary of benchmark via fio:
GVFS SMB:
=
name type size block_size latency_(ms) bandwidth_(kb) IOPS
--
Another correction. For the one workaround, switching to discrete
graphics in the BIOS only seemed to get past the initial gnome login.
But resuming from DPMS off/suspend, the same error loop happens even
when hybrid graphics is disabled in the BIOS.
Even worse, seems hardware acceleration ends up
Apologies, continuing the comment above (mistakenly posted when adding
the log attachment). Let me retry.
Failure loop observed:
- Failed to blit shared framebuffer: EGL failed to allocate resources for the
requested operation.
- Failed to set CRTC mode 3840x2160: No such file or directory
To s
Here's the script I run to workaround the intital failure of gnome to
use the external display after unlocking or resuming from DPMS
suspend/off.
** Attachment added: "fix-hdmi-uhd.sh"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365719/+files/fix-hdmi-uhd.sh
--
Y
Hi, thanks to everyone, especially Daniel for unpacking this issue.
I have had a very similar issue, where gnome shell fails to run my
external 4K/UHD display at 60HZ and I see the following failure loop
triggered in `journalctl -b -p warning _COMM=gnome-shell`:
May 02 20:39:38 JNBA434499PLL gno
It's a shot in the dark, but in my case, pulse sound server (atop of
alsa) seems to have gotten into a mess with an upgrade between 16.04 and
18.04. Post login, removing old / session start user config fixed my
dodgy channel mappings (but not quite the same as crackling, etc):
pulseaudio --kill \
Wish there was a "needs more info" tag or a way to tag bug reports like
this. There's no context as to exactly what the problem is despite the
alsa-info script output being supplied.
It's unfair to maintainers to expect them to fish out the problem.
"Sound bug ubuntu 18.04" is way too generic.
--
See
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774904/comments/4.
gnome-control-center should rather add libcanberra-pulse to depends
rather than just recommends.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Hi, in my case, I think it was simply a missing package dependency.
Installing the libcanberra-pulse package fixed it for me.
gnome-control should probably add libcanberra-pulse to a proper
dependency rather than just recommends since it's likely common that
people would want to test speakers and
** Also affects: gnome-session (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/1732450
Title:
Lock screen doesn't respect gnome shell theme choice
I've noticed in 18.04.2 (upgraded from 16.04 LTS), with gnome-shell
3.28.3-0ubuntu0.18.04.4 and ubuntu-session 3.28.1-0ubuntu3, the *lock*
screen is still pinning to /usr/share/gnome-shell/theme/ubuntu.css.
Note, the login session screen is using the correct theme.
This is related: https://bugs.la
I roughly understand this issue might be something to do with ubuntu-
session package hard configuring the gdm login screen to use ubuntu.css?
Is this not a sub-effect / possible duplicate bug of:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722 ?
Also see: https://github.com/po
I tried rebuilding the current 3.28.3 upstream source from git while
atop of the 3.28.0 debian source via uupdate, e.g.:
apt-get source gpaste
curl -OL https://github.com/Keruspe/GPaste/archive/v3.28.3.tar.gz
# rename v3.28.3.tar.gz else uupdate causes pacakge version 28.3 and breaks on
v3
mv v3.
Forgot to clearly mention, I was building gpaste 3.28.3 on 18.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775971
Title:
[SRU] Update gpaste to 3.28.3 in Bionic
To manage notifications ab
I'm on `4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux` and this bug has only started since
more recent versions of 4.13.
Likely an OpenGL rendering bug in the Intel GPU driver. This looks related:
- https://bugs.launchpad.net/ubuntu/+source/gn
Apologises, I think I'm conflating a resume from hibernate issue vs a
resume from suspend issue, so the previous comment is probably not that
relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/166
No sure if this will help, but there are plenty of debian bugs related
to this to check
If you are relying on the `resume=` kernel parameter with
/etc/default/grub, that might well be ignored. According to the message
below, there are various bugs in upstream debian (and I'm not sure if
Ubuntu pat
Similar mdadm error for me when I resume from suspend on 16.04.2 LTS.
> This bug seems to be fixed in yakkety with mdadm 3.4-4.
Note that while v4.4 was released early 2016, Xenial shipped with v3.3
(which is sane given one wouldn't want to ship with v4.4 just a few mere
months after it was relea
Sorry correction, meant to say v3.4 (not 4.4).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568097
Title:
Error messages about mdadm --incremental failing
To manage notifications about this bug g
I too see this error for Seagate 'ST3500418AS' SATA drives via 88SE9123
PCIe SATA 6.0 Gb/s controller (Ubuntu 16.04.2, latest 4.8 Kernel)
```
exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
irq_stat 0x4001
failed command: SET FEATURES
cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 4
status: { D
Public bug reported:
Very much like, but a new regression with the same issue
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/645061
The following IS in /etc/apparmor.d/usr.bin.freshclam
@{PROC}/filesystems r,
owner @{PROC}/[0-9]*/status r,
And
$ ps -u clamav -f | more
UID PID PPID C ST
Also noted, the following IS in /etc/apparmor.d/usr.bin.freshclam
@{PROC}/filesystems r,
owner @{PROC}/[0-9]*/status r,
And
$ ps -u clamav -f | more
UIDPID PPID C STIME TTY TIME CMD
clamav1348 1 0 08:38 ?00:00:02 /usr/bin/freshclam -d --foregrou
nd=true
$ ls -
Related bug which was marked as fixed, but has now regressed somehow.
645061 / https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/645061
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/645956
Title:
This bug is back?
$ freshclam --version
ClamAV 0.99.2/22939/Tue Jan 24 06:19:06 2017
$ grep DENIED /var/log/kern.log
Jan 24 09:51:04 kernel: [ 41.318809] audit: type=1400
audit(1485244264.939:43): apparmor="DENIED" operation="open"
profile="/usr/bin/freshclam" name="/proc/5588/status" pid=55
Similar issue with freshclam
audit: type=1400 audit(1485244264.939:43): apparmor="DENIED"
operation="open" profile="/usr/bin/freshclam" name="/proc/5588/status"
pid=5588 comm="freshclam" requested_mask="r" denied_mask="r" fsuid=131
ouid=0
--
You received this bug notification because you are a m
In my case, just adding `/run/udev/data/** r,` into
/etc/apparmor.d/libvirt/TEMPLATE.qemu worked 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/1515791
Title:
USB passthrough - virt-aa-helper
I'm running libvirt-bin 1.3.1-1ubuntu10.6 and still getting this error.
And it is not related to a space with the directory of a .iso file or
something.
This is really bizarre. Like other's, those files do exist have other
(world) read access set, so no clue what code is asserting that don't
exist
It's still happening to me on 16.04 (Xenial), fully up to date.
@madbiologist, thanks, good to know where the cause might be.
Still, having to rebuild a kernel with one commit reverted is a fairly
cumbersome work-around and painful given fairly frequent kernel
updates...
As far as I can see, no
Notable upstream bugs with related issues
alegidly patched: https://bugzilla.kernel.org/show_bug.cgi?id=115771
maybe not patched yet: https://bugzilla.kernel.org/show_bug.cgi?id=93521
Workaround (to help other who find this bug)
Add `intel_pstate=disable` to `GRUB_CMDLINE_LINUX_DEFAULT` in
/etc/
Same, here, this message makes me fear that my system won't be able to
boot with the new kernel.
Setting up linux-signed-image-4.4.0-51-generic (4.4.0-51.72) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section tabl
@SunBear
I'm also having issues with these apparent errors:
thermald[1309]: 13 CPUID levels; family:model:stepping 0x6:3c:3 (6:60:3)
thermald[1309]: Polling mode is enabled: 4
thermald[1309]: sysfs write failed enabled
thermald[1309]: sysfs read failed constraint_0_max_power_uw
thermald[1309]: sy
Still a bug because same thing happens with the evolution-ews plugin for
outlook corporate GALs (global address lists) being quite large, e.g.
65K contacts, whereby a single thread can use over 3GB RAM in gnome-
contacts! Clearly it doesn't efficiently iterate through the contact
list if it's bulk
Update on the previous comment, I realised the issue was the the
partition where /var was mounted to hat nosuid set. Seems /var/lib/lxc
must allow for the suid bit to be set. The problem is that people often
have /home mounted with nosuid as a normal security precaution, so this
effects running unp
It also affected me on Ubuntu 16.04 LTS with /var/lib/lxc mount via
bind.
My original setup only had 8GB for /var, so a bind to directory in /home
was the custom hack I did to give lxc more space.
$ grep lxc /etc/fstab
/home/var/lib/lxc /var/lib/lxc nonebind
Public bug reported:
Upstream has enhanced support for multi-monitor setups. Package version
here is too old to include fixes for the 'ximerama_head' option
https://github.com/brndnmtthws/conky/issues/172.
Error
conky: Unknown setting 'xinerama_head'
Is it possible to have 10.1.3 made available
Noticed this problem on Gnome 3.18 in 16.04 LTS as well with conky
v1.10.1. Had to switch to window type 'normal' (default) and used
desktop hints instead. 'desktop' window type stops displaying conky if
an icon on the desktop is clicked.
--own_window_type = 'desktop',
--own_window_type = 'normal'
Still impacting me, and xenial is meant to be LTS, so leaving vagrant
broken is a bit rough?
Also, while upstream provides an alternative, it's quite nasty as it
ends up bundling all it's own lib dependencies and, in my case,
replaced/force upgraded libarchive13 causing some package dependency
iss
doesn't have this error on 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503565
Title:
vagrant depends on bsdtar which depends on libarchive13
To manage notifications about this bug go to:
h
A work-arround is to (ab)use the template file
/etc/apparmor.d/libvirt/TEMPLATE.qemu
---
profile LIBVIRT_TEMPLATE {
#include
/var/lib/libvirt/qemu/nvram/*_VARS.fd rw,
}
---
I'm not too familiar with AppArmour, nor kvm/libvirt's security model,
but I assume the whole point of virt-aa-helper i
I have encoutered a similar bug related to the libvirt per guest
AppArmor profile helper, libvirt-aa-helper
Virtual Machine Manager GUI reports
---
Error starting domain: internal error: process exited while connecting to
monitor: 2015-11-16T09:39:50.572025Z qemu-system-x86_64: -drive
file=/var
@Chistopher, thanks, the problem is now that my A15 bios can't even
enter setup mode or boot anything, so I'm not sure how to try flash the
most recent A16 version from (released just a month ago)? Searched the
laptop's manual, and no indication of any jumpers to clear/reset NVRAM
:-(
I agree and
*** This bug is a duplicate of bug 1082418 ***
https://bugs.launchpad.net/bugs/1082418
** This bug has been marked a duplicate of bug 1273060
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
--
You received this bug notification because you are a member of Ubunt
*** This bug is a duplicate of bug 1273060 ***
https://bugs.launchpad.net/bugs/1273060
** This bug has been marked a duplicate of bug 1273060
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
--
You received this bug notification because you are a member of Ubunt
*** This bug is a duplicate of bug 1273060 ***
https://bugs.launchpad.net/bugs/1273060
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** This bug has been marked a duplicate of bug 1273060
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
--
Y
To summarise, there are at least two other related bug reports (which should
add motivation given the wider impact of the issue):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471380
--
You received this bug notification becaus
And this bug isn't isolated to just to Fujitsu. The same thing just
happened to me with a Dell.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
This bug is high risk! It's effectively bricked a Dell Latitude E6540
:-(
My theory is that, somehow, the update caused a change to the firmware
NVRAM settings and boot entries for UEFI, and the Dell code can't handle
something unexpected. And after I've entered BIOS password, the firmware
code sa
Other similar bugs for the laptop were logged, but not clear if they had been
resolved as they either expired or were triaged .
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1278679
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1285938
--
You received this bug notification because
Sadly, while UXA doesn't trigger the suspend resume bug as often as SNA,
it still sometimes occurs. I've attempted to log a bug upstream related
to the video driver package xf86-video-intel.
** Bug watch added: freedesktop.org Bugzilla #86067
https://bugs.freedesktop.org/show_bug.cgi?id=86067
** Description changed:
1)
- Mint Version: Linux Mint 17 Cinnamon 32 bit,
+ Mint Version: Linux Mint 17 Cinnamon 32 bit,
Kernel Version: 3.13.0-29-generic
Laptop: Acer Extensa 5220
Chipset: Intel GM965/GL960 (GMA X3100)
- Suspected driver at fault: xf86-video-intel
+ Suspected driver
I can confirm this issue. I have reproduced the problem and used strace.
I've also found the app-armour log entry. The app-armour disallowing the
-cf is presumably intentional. The bug is that dhclient3
does not warn the user or log an error when it's unable to open the file
parsed to -cf.
In tra
** Changed in: dhcp3 (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/537851
Title:
dhclient silently ignores unreadable config-file
To manage notification
55 matches
Mail list logo
