[Bug 1953249] Re: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing
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 and in lockstep. E.g. 20.04.3 LTS is based on kernel 5.11 from hirsute (21.04), but the linux-firmware collection is left outdated on 1.187.20 that came with kernel 5.4? https://packages.ubuntu.com/hirsute-updates/linux-firmware shows v 1.197.3, so I'd expect a HWE stack with 20.04.3 to also provide the same level of firmware updates for kernel 5.11. > I use UEFI and the module wasn't signed Perhaps installing the official deb/repo instead of upstream has a good shot at the firmware that gets added into initramfs being signed properly (one would hope!). I manged the following workaround, but my case is still legacy BIOS. curl -OL http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.197.3_all.deb sudo dpkg -i linux-firmware_1.197.3_all.deb Extra hint: maybe download the deb from your closest mirror because this package is almost 200MB large. P.S. While most firmware is hopefully decoupled and backward compatible to use with older kernel modules/drivers, one never knows if a bug might show up by using very new firmware with much older modules, since you stray into a untested path between the firmware and the kernel modules. Hence I tried to match the Ubuntu release, kernel versions, and tested- at-the-time firmware more closely than just jumping to latest upstream firmware versions. Its similar but a kinda upside version of the older proprietary graphics driver blob hell that plagued Linux over the previous decade. Firmware is the other way round where the in-tree admgpu driver needs the firmware to provide a stable interface. Can't recall if Linux ever solved the lack of a stable in-kernel/versioned ABI between drivers and binary driver blobs. It's why AMD FGLRX proprietary drivers blobs were always hell, and AMD failed to keep up with ABI changes on the kernel and often didn't work with newer kernels, hence amdgpu became the new middle layer/foundation to bridge this ABI gap and add create a stable/presumably versioned ABI for AMD that the kernel developers never bothered to provide. Now AMD-pro software and extended driver blobs can rely on the opensource amdgpu parts to be less of a moving target as ABI changes on the kernel core will need to update/include required changes to amdgpu because amdgpu is now in-tree and should be tested in lockstep with other kernel changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953249 Title: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940836] Re: Libreoffice Calc rendering very slow on GTK3
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 report, what worked for me was removing the snap and reverting to old deb `sudo apt install libreoffice` back to 6.4.7.2 non- snap version. No rendering performance issues with the older deb package. https://ask.libreoffice.org/t/calc-and-writer-ver-7-0-are-extremely- slow/58522/8 mentions trying this which I tried with the 7.2 snap version: SAL_USE_VCLPLUGIN=gen libreoffice It seemed to work better but still somewhat slow and not nearly as responsive as the 6.4 deb package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940836 Title: Libreoffice Calc rendering very slow on GTK3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1940836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236619] Re: gvfs smb / cifs file copy performance is terribly slow
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 sequential IO read, in terms of latency, bandwidth and IOPS, GVFS is over 10 times slower than CIFS. While I know fuse mounts (userspace filesystems) will be understandably slower than kernel space mounts, more than 10 times slower is significant and indicates there's inefficiencies / room for improvement. ** Attachment added: "GVFS-SMB vs CIFS" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1236619/+attachment/5379760/+files/gvfs-smb_vs_cifs_seq_read_benchmark_ubuntu_18.04.4.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236619 Title: gvfs smb / cifs file copy performance is terribly slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1236619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236619] Re: gvfs smb / cifs file copy performance is terribly slow
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
-- --
4k_4k_seq_readread 4k4k 7.597604 100 25
512k_4k_seq_read read 512k 4k 12.608847148437 312
78.001219
4m_64k_seq_read read 4m64k 58.59852259375 1082
16.91779
8m_256k_seq_read read 8m256k252.2923598125 1010
3.948667
16m_1m_seq_read read 16m 1m 1079.9320893125 946
0.924481
CIFS:
=
name type size block_size latency_(ms)bandwidth_(kb) IOPS
-- --
4k_4k_seq_readread 4k4k 7.226365250 62.5
512k_4k_seq_read read 512k 4k 0.35290271875 9481
2370.37037
4m_64k_seq_read read 4m64k 4.14038503125 15003
234.432234
8m_256k_seq_read read 8m256k17.80018796875 14148
55.267703
16m_1m_seq_read read 16m 1m 83.7329983125 12145
11.860638
Bash script to test this (depends on fio, jq and column)
#json_benchmark_result_summary=''
tempfile=$(mktemp /tmp/read_test..ndjson)
echo "# Using temp file: $tempfile"
function seq_read_benchmark() {
local total_size="$1"
local block_size="$2"
echo "# Testing sequential read of $total_size size in $block_size."
sleep 1
fio --name="${total_size}_${block_size}_seq_read"
--filename="${total_size}_${block_size}_seq_read_test.bin" --rw=read
--iodepth=1 --max-jobs=1 --size="$total_size" --bs="$block_size"
--output-format=json >> "$tempfile"
rm "${total_size}_${block_size}_seq_read_test.bin"
}
seq_read_benchmark 4k 4k # 1 block read
seq_read_benchmark 512k 4k # 128 x 4k blocks read
seq_read_benchmark 4m 64k # 64 x 64k blocks read
seq_read_benchmark 8m 256k # 32 x 128k blocks read
seq_read_benchmark 16m 1m # 16 x 1m blocks read
# Reshaping JSON with jq:
https://programminghistorian.org/en/lessons/json-and-jq#output-a-csv-csv
# How to format a JSON string as a table using jq?:
https://stackoverflow.com/a/39144364/5472444
jq -s -r
'(["name","type","size","block_size","latency_(ms)","bandwidth_(kb)","IOPS"] |
(., map(length*"-"))), (.[] | .jobs[] | [.jobname, ."job options".rw, ."job
options".size, ."job options".bs, (.read.lat_ns.mean/100), .read.bw,
.read.iops]) | @tsv' "$tempfile" | column -t
# Convert JSON lines to JSON array using jq:
https://stackoverflow.com/a/61867230/5472444
#jq -s '[.[] | .jobs[] | {name: .jobname, type: ."job options".rw, size: ."job
options".size, "block size": ."job options".bs, "latency (ms)":
(.read.lat_ns.mean/100), "bandwidth (kb)": .read.bw, IOPS: .read.iops}]'
"$tempfile" > read_test_summary.json
# Cleanup
rm "$tempfile"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236619
Title:
gvfs smb / cifs file copy performance is terribly slow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1236619/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
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 being disabled: $ journalctl --no-hostname -b -p warning _COMM=gnome-shell -- Logs begin at Wed 2019-02-06 14:13:52 SAST, end at Sun 2020-05-03 16:09:45 SAST. -- May 03 14:51:40 org.gnome.Shell.desktop[2284]: glamor: 'wl_drm' not supported May 03 14:51:40 org.gnome.Shell.desktop[2284]: Missing Wayland requirements for glamor GBM backend May 03 14:51:40 org.gnome.Shell.desktop[2284]: Failed to initialize glamor, falling back to sw ... May 03 14:53:25 gnome-shell[6549]: setup_framebuffers: assertion 'width > 0' failed The "EGL failed to allocate resources" error stops happening probably because gnome-shell isn't even using hardware acceleration now. I've also disabled all gnome shell extensions to avoid noise/errors in the logs and will try weed out the problem better. I checked `grep -C2 -E '(EE)|(WW)' /var/log/Xorg.0.log` and things seem fine: [45.181] (II) NVIDIA dlloader X Driver 440.59 Thu Jan 30 01:08:17 UTC 2020 [45.181] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs -- [45.182] (II) LoadModule: "ramdac" [45.182] (II) Module "ramdac" already built-in [45.183] (WW) Falling back to old probe method for modesetting [45.183] (II) NVIDIA(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 -- [46.392] (==) NVIDIA(0): Silken mouse enabled [46.392] (==) NVIDIA(0): DPMS enabled [46.393] (WW) NVIDIA(0): Option "PrimaryGPU" is not used [46.393] (II) Loading sub module "dri2" [46.393] (II) LoadModule: "dri2" Note, I've done no customisation to X config - trying to stick to defaults. xrandr confirms only one provider / hybrid is indeed off and Intel not in use: $ xrandr --listproviders Providers: number : 1 Provider 0: id: 0x218 cap: 0x1, Source Output crtcs: 4 outputs: 6 associated providers: 0 name:NVIDIA-0 I'm guessing the Lenovo P53 impliments a mux/switch to connect the laptop panel to the NVidia card so that Intel is disabled in this mode. And double checking, also no i915 modules are loaded: $ lsmod | grep '^drm' drm_kms_helper180224 1 nvidia_drm drm 491520 10 drm_kms_helper,nvidia_drm So there seems to be, on current Ubuntu 18.04.4 LTS (fully up to date as of today), a 4K / UHD 60Hz issue with Nvidia, as seen in X log [45.228] (II) NVIDIA GLX Module 440.59 Thu Jan 30 01:05:38 UTC 2020 Lastly, I think due to `needs_root_rights=yes` in /etc/X11/Xwrapper.config, X logs to /var/log/Xorg.0.log again instead of the X without root which used to log at ~/.local/share/xorg/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
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 summarise and share my experience of it on a Lenovo P53 and some quirks/workarounds: - `sudo ubuntu-drivers autoinstall` got Nvidia 440.59 drivers installed. - However, Nvidia modeset was not enabled as yet. $ sudo cat /sys/module/nvidia_drm/parameters/modeset N - Blank external screen occurs with modeset=0 (disabled) - Then, using `prime-select nvidia`, I tried to ensure nvidia was primary - `prime-select nvidia` sets `options nvidia-drm modeset=1` but it's not effective, even after I rebooted ~$ cat /lib/modprobe.d/nvidia-kms.conf # This file was generated by nvidia-prime # Set value to 0 to disable modesetting options nvidia-drm modeset=1 - To make it effective, because modeset is done during initramfs part of boot, I ran `sudo update-initramfs -u -k all`. - It seems the prime-select option fails to trigger a intiramfs update (probably should be filed as a separate bug) - Regardless, the blank screen issue occured on my Lenovo P53 with or without Nvidia KMS modeset enabled - But one benefit of KMS modeset for Nvida is now the external display gets properly recognised. /sys/class/drm/card1-HDMI-A-1/ now exists (was missing with Ubuntu 18.04.4 LTS default proprietary install) including the EDID data being read properly and X getting the actual DPI of the screen correctly. Without nvidia modeset, as seen in `journalctl -b _COMM=gdm-x-session | grep -C2 -E '(EE)|(WW)'`: (WW) NVIDIA(0): Unable to get display device for DPI computation. With nvidia modeset: (II) NVIDIA(0): Validated MetaModes: (II) NVIDIA(0): "DFP-3:nvidia-auto-select" (II) NVIDIA(0): Virtual screen size determined to be 3840 x 2160 (--) NVIDIA(0): DPI set to (139, 140); computed from "UseEdidDpi" X config I've also found two workarounds to my issue. 1. Run a script that sets the frequency to 30HZ and then back to 60HZ 2. Switch to discrete only graphics in the BIOS In most cases, when one is using a 2nd display, there's usually a powersource available so the complexity of hybrid graphics isn't worth it and I went with simply disabling hybrid graphics in the BIOS. It's quite interesting that toggling the display refresh rate down to 30HZ and then back up to 60HZ seems to work around the problem of gnome- shell mutter's "EGL failed to allocate resources for the requested operation" bug. To conclude, even with the root access workaround in place: $ tail -n 2 /etc/X11/Xwrapper.config # Added by xserver-xorg-video-nvidia-440 needs_root_rights=yes I still had external display connection issues with 4K 60Hz. This might need to be logged as different bug? I'm unsure it's GDM3s fault given the root workaround was in place, but it's highly related/similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
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 gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to flip: Device or resource busy May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory ... While not sure it's exactly the same, it should still inform the overall discussion about dealing with GDM3 + Mutter + proprietary Nvidia drivers modeset problems. To summarise and share my experience of it on a Lenovo P53 and some quirks/workarounds: - `sudo ubuntu-drivers autoinstall` got Nvidia 440.59 drivers installed. - However, Nvidia modeset was not enabled as yet. $ sudo cat /sys/module/nvidia_drm/parameters/modeset N - - Using prime-select - For laptops like mine, seems the external port is connected to the Nvidia GPU. - Using the proprietary Nvidia drivers seems to then bump into a ** Attachment added: "gnome-shell_journal_warnings_egl_resource_failed.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365716/+files/gnome-shell_journal_warnings_egl_resource_failed.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790816] Re: Terrible sound after update to 18.04
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 \ && rm -r ~/.config/pulse/* \ && pulseaudio --start However, every new boot, the same missing channel mappings cause my audio to sound bad (not mapped correctly to 5.1 channels). Also, try alsa-info which is a script that bundles all the alsa inspection commands and then maybe try fish for the problem in that. Also try figure out how to play a sound file directly to alsa vs via the pulse sound server to rule out pulse causing the problem. I think the speaker-test command also directly tests the alsa layer where as the gnome-control-centre (settings) sound page "Test Speakers" tests the setup via pulse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790816 Title: Terrible sound after update to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1790816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791417] Re: Sound bug ubuntu 18.04
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791417 Title: Sound bug ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1791417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736349] Re: "Test speakers" is silent
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://bugs.launchpad.net/bugs/736349 Title: "Test speakers" is silent To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/736349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774904] Re: No defualt sound. Test speakers not working.
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 the test silently failing (e.g. control-centre doesn't even warn its missing the libs it needs) makes a user (me for example) get lost (i.e. inspecting ALSA, etc) when the silent test failure misleads. Also noted at the end of: https://bugs.launchpad.net/ubuntu/+source /gnome-media/+bug/736349 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774904 Title: No defualt sound. Test speakers not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732450] Re: Lock screen doesn't respect gnome shell theme choice
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1732450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715722] Re: Allow safe override of GDM3 theme
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.launchpad.net/ubuntu/+source/gnome- shell/+bug/1732450. As per https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1732450/comments/5, the nasty I did to work around it shows the gdm3 / session lock screen theme is still pointed directly to /usr/share/gnome-shell/theme/ubuntu.css instead of /usr/share/gnome- shell/theme/gdm3.css. I also checked the alternative symlinking, and indeed, `pop.css` was supposed to be used, yet the lock screen used ubuntu.css. ``` $ update-alternatives --display gdm3.css gdm3.css - auto mode link best version is /usr/share/gnome-shell/theme/pop.css link currently points to /usr/share/gnome-shell/theme/pop.css link gdm3.css is /usr/share/gnome-shell/theme/gdm3.css /usr/share/gnome-shell/theme/pop.css - priority 20 /usr/share/gnome-shell/theme/ubuntu.css - priority 10 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715722 Title: Allow safe override of GDM3 theme To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1715722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732450] Re: Lock screen doesn't respect gnome shell theme choice
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/pop-os/gtk-theme/issues/123 I did this very dodgy hack: ``` cd /usr/share/gnome-shell/theme sudo mv ubuntu.css ubuntu.css.bak-dist_1804 sudo ln -s pop.css ubuntu.css ``` Note, I don't symlink `ubuntu.css` to `gdm3.css`, because this might cause circular referencing if the default theme was selected given this is how symlinks could stack: /usr/share/gnome-shell/theme/gdm3.css -> /etc/alternatives/gdm3.css -> /usr/share/gnome-shell/theme/ubuntu.css Anyhow, the above is temp work-around, and I know that ubuntu.css will get clobbered next time the gnome-shell-common package updates, but so be it. ** Bug watch added: github.com/pop-os/gtk-theme/issues #123 https://github.com/pop-os/gtk-theme/issues/123 -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1732450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775971] Re: [SRU] Update gpaste to 3.28.3 in Bionic
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.28.3.tar.gz gpaste_3.28.3.orig.tar.gz cd gpaste-3.28.0 uupdate ../gpaste_3.28.3.orig.tar.gz cd ../gpaste-3.28.3 #libgpaste soname is now 11 instead of 9 sed -i 's/libgpaste9/libgpaste11/g' debian/control mv debian/libgpaste9.install debian/libgpaste11.install # no clue what to do about symbol files probably used for debug? Complians out of sync if I just rename 9 to 11 and build. Removing for now. rm debian/libgpaste11.symbols debuild I then installed the resulting deb packages, and gpaste runs. Think it's fixed the image crash issue (`3.28.2` NEWS mentions it being fixed). But clueless about how to adjust/create a poper symbol file for the debian folder. I note the upstream make process does and a source file it targets for symbols, but not sure how to get that into the debian package properly - advanced debug features I'm not familiar with. I've also noticed that 3.28.2 for 18.10/cosmic had a number of patches to backport/allow it handle gnome 3.30 and depend on libglib2 2.58, so it's not workable/adaptable to 18.04/bionic. -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpaste/+bug/1775971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775971] Re: [SRU] Update gpaste to 3.28.3 in Bionic
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpaste/+bug/1775971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750325] Re: X crashing due to intel_do_flush_locked failed: Bad address
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/gnome-shell/+bug/1730184 - https://bugs.freedesktop.org/show_bug.cgi?id=101142 - https://ubuntuforums.org/archive/index.php/t-2343879.html ** Bug watch added: freedesktop.org Bugzilla #101142 https://bugs.freedesktop.org/show_bug.cgi?id=101142 ** Also affects: mesa 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/1750325 Title: X crashing due to intel_do_flush_locked failed: Bad address To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1750325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1669620] Re: Reboot when resume from suspend
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/1669620 Title: Reboot when resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1669620] Re: Reboot when resume from suspend
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 patches/changes this): https://lists.debian.org/debian-kernel/2017/04/msg00348.html After installed, I noted `/etc/initramfs-tools/conf.d/resume` uses a UUID, but I had issues getting resume to work, possibly because I recreated my swap partition. As far as I could tell, Ubuntu 16.04.2 LTS seems to ignore the `resume=` kernel parameter as a UUID or LABEL. `apt-cache show initramfs-tools` shows Ubuntu 16.04.2 LTS currently has `Version: 0.122ubuntu8.8`, so it should be free of the bug/regression that caused UUID or LABEL to be ignored in `conf.d/resume` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669620 Title: Reboot when resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568097] Re: Error messages about mdadm --incremental failing
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 released) . However, what seems a bit tardy to me is that v3.3.4 release was published 03 Aug-2015, so why did/does Xenial ship with a v3.3.2 version and miss two minor releases worth of fixes/updates from upstream (or have to back port them)? ``` $ mdadm --version mdadm - v3.3 - 3rd September 2013 $ dpkg-query --show mdadm mdadm 3.3-2ubuntu7.2 ``` Of course, there are back-ported patches from v3.4... https://launchpad.net/ubuntu/+source/mdadm/+changelog -- 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 go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1568097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568097] Re: Error messages about mdadm --incremental failing
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 go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1568097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629512] Re: HDD failed command: SET FEATURES error
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: { DRDY ERR }
error: { ABRT }
```
Note:
- `Emask 0x1` = "device reported error"
- `status: { DRDY ERR }` = device ready, but with error
If it relates to other posts on the internet, it might be benign and
simply failed power management setting attempts, or the like via the
Marvel controller.
To note, I have other SSD drives in the system that are connected via a
different controller (SB850) and also don't support APM, but they don't
exhibit this error!
`cmd ef/05:fe:00:00:00/00:00:00:00:00/40` requires understanding ATA commands
to know what the above command is attempting. As per the "Enable/disable
advanced power management" section of the ATA.8 standard:
- "Subcommand code `05h` allows the host to enable Advanced Power Management."
- `FEh` = Maximum performance
So this confirms:
- ATA command = ef = SET FEATURE
- ATA Feature = 05 = Advanced Power Management4
- ATA NSect = fe = 254 = Maximum performance
- remainder of string ":00:00:00/00:00:00:00:00/40" is addressing
SOMETHING during boot is trying to set APM on drives that don't support
it!!!
I checked udev rules - this doesn't seem to be udev...
```
$ grep -r hdparm /lib/udev/*
/lib/udev/hdparm:. /lib/hdparm/hdparm-functions
/lib/udev/hdparm: if grep -wq nohdparm /proc/cmdline ; then
/lib/udev/hdparm:OPTIONS=$(hdparm_options $DEVNAME)
/lib/udev/hdparm: /sbin/hdparm $OPTIONS $DEVNAME 2>/dev/null
/lib/udev/rules.d/85-hdparm.rules:ACTION=="add", SUBSYSTEM=="block",
KERNEL=="[sh]d[a-z]", RUN+="/lib/udev/hdparm"
```
Tracing the udev -> hdparm scritping, I found that in
`/lib/hdparm/hdparm-functions`, there is `hdparm_options()` and
`hdparm_try_apm()`, which might default to `hdparm_set_option -B254`
```
and
```
hdparm_try_apm()
{
# set our default global apm policy here.
if [ -z "$ID_PATH" ]; then
local ID_PATH="$(udevadm info -n "$1" -q property 2>/dev/null | sed -n
's/^ID_PATH=//p')" || true
fi
case $ID_PATH in
pci-*-ieee1394-*|pci-*-usb-*)
return 1
;;
esac
return 0
}
```
But in my case, when I query udev properties for the device, I see this
```
$ udevadm info -n /dev/sdg
...
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
...
```
But I do not see `ID_ATA_FEATURE_SET_APM=1` so udev is, or it shouldn't
be setting APM on my drive that doesn't support it...
So if it's not the normal system udev rules, I wondered if it might be
something about the init on initramfs trying to enable this, given that
does try to load block device drivers and probably runs udev rules in
preparation for mounting root. I uncompressed initramfs, but failed to
identify anything that sets the APM on drives that don't support it.
So it's still a mystery why APM is attempted when, clearly, it's obvious
the drives don't support it, and also, why only the HDD drives on the
marvel controller vs other SSDs (not on Marvel) that don't have APM?
Also, if I force `sudo hdparm -B 254 /dev/sdg` and tail
/var/log/kern.log, I can't trigger that same error seen during boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629512
Title:
HDD failed command: SET FEATURES error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629512/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659223] [NEW] apparmor regression blocking freshclam process info
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 STIME TTY TIME CMD
clamav 1348 1 0 08:38 ? 00:00:02 /usr/bin/freshclam -d --foregrou
nd=true
$ ls -l /proc/1348/status
-r--r--r-- 1 root root 0 Jan 25 08:38 /proc/1348/status
Shows that root owns the status file, not the clamav user.
Hence denied.
** Affects: clamav (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/1659223
Title:
apparmor regression blocking freshclam process info
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1659223/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645061] Re: apparmor blocks freshclam process info after latest update
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 -l /proc/1348/status
-r--r--r-- 1 root root 0 Jan 25 08:38 /proc/1348/status
Shows that root owns the status file, not the clamav user.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/645061
Title:
apparmor blocks freshclam process info after latest update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/645061/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645956] Re: appamor denying clamd access to its own process
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: appamor denying clamd access to its own process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/645956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645061] Re: apparmor blocks freshclam process info after latest update
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=5588 comm="freshclam" requested_mask="r" denied_mask="r" fsuid=131 ouid=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645061 Title: apparmor blocks freshclam process info after latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/645061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645956] Re: appamor denying clamd access to its own process
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645956 Title: appamor denying clamd access to its own process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/645956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515791] Re: USB passthrough - virt-aa-helper must grant /run/udev/data/ r
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 must grant /run/udev/data/ r To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1515791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384532] Re: Unable to set AppArmor profile [...] no such file or directory
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 (when they do). From virt-manager's perspective, the error in the libvirtd daemon process is not visible... I found reverting changes in `/etc/apparmor/libvirt/TEMPLATE.qemu` seemed to fix my error. As per a prior comment above, a related bug is how cumbersome apparmor error handling is. For example, nothing in libvirt nor apparmor had any indicator that something `TEMPLATE.qemu` was putting it off. It even actually generated the per domain apparmor files (as other have observed) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384532 Title: Unable to set AppArmor profile [...] no such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512848] Re: Radeon VCE Init Error
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 fixes have been worked on? 0 commits to vce_v1_0.c (my graphics card is only VCE 1 capable) `CHIP_PITCAIRN` https://github.com/torvalds/linux/commits/master/drivers/gpu/drm/radeon/vce_v1_0.c https://github.com/torvalds/linux/commits/master/drivers/gpu/drm/radeon/radeon_vce.c However, there might be a way to disable VCE (I need to look into it more) https://github.com/torvalds/linux/commit/fabb5935871db1f31fcd2684fd154e24de04d917 #diff-9bc1b4aaf15dd521a1991717e4e2a2e0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512848 Title: Radeon VCE Init Error To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1512848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598394] Re: intel_pstate has too aggressive frequency selection
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/default/grub and update-grub. This will revert to the acpi-cpufreq driver and ondemand (default) policy. check with `cpupower frequency-info` I've observed more sane scaling of CPU frequencies, and better fan speed and temperature on Haswell. E.g. acpi-cpufreq vs pstate (while relatively idle) * temp: ~52 vs 70 degrees * fan: ~3800 rpm vs 4600 rpm pstate will very often turbo boost many cores and seldom drop below standard max frequency even when lightly loaded per core. When loaded, temp would bounce up to 89 degrees quickly. I suspect the CPU kept needing to throttle back often. ** Bug watch added: Linux Kernel Bug Tracker #115771 http://bugzilla.kernel.org/show_bug.cgi?id=115771 ** Bug watch added: Linux Kernel Bug Tracker #93521 http://bugzilla.kernel.org/show_bug.cgi?id=93521 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598394 Title: intel_pstate has too aggressive frequency selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1598394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540406] Re: warning: file-aligned section .text extends beyond end of file
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 table? This seems related? https://bugs.launchpad.net/launchpad/+bug/1071562 This suggests it isn't as serious as it sounds? http://www.rodsbooks.com /efi-bootloaders/secureboot.html. However, no actual explanation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540406 Title: warning: file-aligned section .text extends beyond end of file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1540406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568123] Re: error messages about /dev/acpi_thermal_rel and /var/run/thermald/thermal-conf.xml
@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]: sysfs write failed trip_point_0_temp Not sure, might be related to https://github.com/01org/thermal_daemon/issues/82 "no kernel driver to handle PCH sensor in Haswell" And that involved a kernel patch? ** Bug watch added: github.com/01org/thermal_daemon/issues #82 https://github.com/01org/thermal_daemon/issues/82 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568123 Title: error messages about /dev/acpi_thermal_rel and /var/run/thermald /thermal-conf.xml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1568123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1079315] Re: Gnome contacts hangs with 100% CPU and growing memory.
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 loading everything into RAM each time the GAL update is done... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079315 Title: Gnome contacts hangs with 100% CPU and growing memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-contacts/+bug/1079315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1389305] Re: sudo doesn't work on unprivileged lxc container on top of ecryptfs
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 unprivileged containers as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389305 Title: sudo doesn't work on unprivileged lxc container on top of ecryptfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1389305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1389305] Re: sudo doesn't work on unprivileged lxc container on top of ecryptfs
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 0 0 Once tested without the bind, the error was gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389305 Title: sudo doesn't work on unprivileged lxc container on top of ecryptfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1389305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613885] [NEW] Multi / Dual screen / monitor support lacking and Unknown setting 'ximerama_head'
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 in backports or something? ** Affects: conky (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/1613885 Title: Multi / Dual screen / monitor support lacking and Unknown setting 'ximerama_head' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1613885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226277] Re: window_type desktop disappears when the desktop is clicked
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', own_window_hints = 'undecorated,sticky,skip_taskbar,skip_pager,below', -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226277 Title: window_type desktop disappears when the desktop is clicked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1226277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559420] Re: plugin install fails in ubuntu/debian packaged version of vagrant (xenial)
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 issues. Options: - backport patch - update to newer upstream vagrant version Assuming vagrant 1.8.x series, 1.8.5 includes a huge set of bug fixes and should be mostly backward compatible with 1.8.1, given it's not a major version change. There was only 3 points noted under "BREAKING CHANGES" for 1.8.3. They didn't seem to be major concerns. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559420 Title: plugin install fails in ubuntu/debian packaged version of vagrant (xenial) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1559420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503565] Re: vagrant depends on bsdtar which depends on libarchive13
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: https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1503565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483071] Re: Error creating new VM with OVMF
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/lib/libvirt/qemu/nvram ... bvirtError: internal error: process exited while connecting to monitor: 2015-11-16T09:39:50.572025Z qemu-system-x86_64: -drive file=/var/lib/libvirt/qemu/nvram/Win10Raw_VARS.fd,if=pflash,format=raw,unit=1: Could not open '/var/lib/libvirt/qemu/nvram/Win10Raw_VARS.fd': Permission denied --- And here is the AppArmour error seen in dmesg --- [ 5576.944602] audit: type=1400 audit(1447663737.977:80): apparmor="DENIED" operation="open" profile="libvirt-bf7063cc-3a6a-4359-88a4-c84bb625a421" name="/var/lib/libvirt/qemu/nvram/Win10Raw_VARS.fd" pid=2802 comm="qemu-system-x86" requested_mask="wr" denied_mask="wr" fsuid=123 ouid=123 --- As per http://wiki.apparmor.net/index.php/Libvirt, virt-aa-helper is used and as per https://www.redhat.com/archives/libvir- list/2015-August/msg00534.html there's a bugfix. However, it still doesn't include and cater for using NVRAM VAR OVMF files generated at /var/lib/libvirt/qemu/nvram/_VARS.fd. The fix for this seems to be in this commit: http://libvirt.org/git/?p=libvirt.git;a=commit;h=91fdcefa7f145c1c39acc8e9a44fbfbf11568e54 The issue is that the libvirtd version in the ubuntu repo for 15.10 is too old to include the patch (i.e. v1.2.16)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483071 Title: Error creating new VM with OVMF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1483071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483071] Re: Error creating new VM with OVMF
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 is to create custom per
VM apparmor profiles with domain specific file names, so *_VARS.fd is
technically insecure given all guest processes could in theory write to
the EFI/OVFM NVRAM image files and proper guest vs guest isolation
requires the fix in virt-aa-helper.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1483071/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082418] Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access
*** 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082418 Title: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471380] Re: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access
*** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471380 Title: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273060] Re: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273060 Title: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451387] Re: Ubuntu UEFI install locks out UEFI firmware
*** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451387 Title: [Fujitsu LIFEBOOK LH532] UEFI firmware becomes locked after installing Ubuntu in UEFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273060] Re: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
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 sadly fails to even manage to enter setup (F2) or the one time boot menu (F12). That's lousy fail-safe coding on the firmware devs part. Surely if searching NVRAM for boot options fails, that shouldn't keep the user locked out of the BIOS settings! Here's what happened in my case: 1. Had a working install of Ubuntu Gnome 15.04 dual booting with Windows 10 and BIOS version A15 for this dell. 2. UEFI Secure Boot was enabled. The UEFI boot order priority options were set to favour the ubuntu entry (which effectively points to the EFI/ubuntu/shimx64.efi entry). 3. I ran the standard upgrade via the GUI from 15.04 to 15.10. 4. Upgrade process reported success, prompted to reboot. After a reboot, the system failed to boot into grub or anything else! Even with a UEFI compatible install CD or USB drive, I couldn't get it to boot. 5. Both F2 (BIOS setup) and F12 (one time boot menu) no longer work! This is a HUGE issue, since now I can't even use the BIOS options to change UEFI settings (e.g. look at enabled boot options, priority or disable secure boot, etc) 6. Opened up the laptop, disconnected the coin-cell CMOS battery, pressed the power button to discharge and force a BIOS settings reset (I've followed this process on many other systems to deal with a bugged out BIOS). Sadly no luck, same issue persists (I'm guessing removing the CMOS battery didn't manage to reset the NVRAM as I hoped). What's interesting is I can take the SSD drive out, put it in a similar laptop, and it boots. It booted into Windows 10 at first, but after using settings (F2) on the working laptop, I could simply switch to the EFI/ubuntu/shimx64.efi as the first option and UEFI secure boot into Ubuntu Gnome 15.10 works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273060 Title: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273060] Re: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
@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 understand that firmware should be written in a way that doesn't allow the nvram boot option changes to cause it to lock up. Still, this kind of bug (even if attributed to firmware and not Linux) is occurring across at least two manufactures (Fujitsu and now Dell) whereby their 'buggy' firmware sees whatever changes ubuntu/Linux made to the NVRAM as NVRAM corruption and fail to even allow entering setup. Given changing NVRAM bios settings during an install or update (as was my case) is high risk, perhaps the install process should at least issue a warning and allow the user to opt out of of clearing and changing NVRAM settings (and potentially trigger a nasty firmware bug). I think it would in some cases be safer for a user to manually go into the BIOS setup and manage the boot options from within the BIOS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273060 Title: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082418] Re: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access
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/bugs/1082418 Title: [Fujitsu Lifebook AH532] Ubuntu UEFI install locks out UEFI firmware (~bios) access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1390923] Re: Mint 17 fails to resume after suspend on Acer Extensa 5220 with Intel GM965/GL960 (GMA X3100) based graphics chipset
** 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 at fault: xf86-video-intel 2) Suspend and resume does not work reliably. After suspending, pressing any key or the power button causes the system to attempt to resume, but during the process it reboots instead of resuming. Only on rare occasions did resume work, so fault appeared intermittent. After much experimentation the following process confirms the bug is related to the Intel graphics driver and DDX 2D acceleration mode by changing X org config: - test suspend and resume with Option AccelMethod snaand resume from suspend often fails and causes reboot - test suspend and resume with Option AccelMethod uxa and resume from suspend seems reliable (no reboot noticed yet) - + Example config to test with /etc/X11/xorg.conf.d/20-intel.conf - Section Device - Identifier Intel Graphics - Driver intel - #Option AccelMethod uxa - Option AccelMethod sna - EndSection + Section Device + Identifier Intel Graphics + Driver intel + #Option AccelMethod uxa + Option AccelMethod sna + EndSection 3) What happened? Laptop rebooted instead of resuming 4) What you expected to happen instead. Expected resume to restore current session with windows previously open, etc 5) If the problem happened once, sometimes, or always. Very frequent. I'd say only 1 in 10 resume attempts (with Option AccelMethod sna) worked and the rest failed and caused a reboot. 6) Other important observations and notes Attempted to follow some suggestions here: https://01.org/linuxgraphics/documentation/how-debug-suspend-resume-issues-0 - resume from S3 suspend to RAM without mdm (display manager) running appeared to work fine, e.g. 'echo mem /sys/power/state' - the default suspend via menu GUI in Cinnamon often caused the resume bug to surface - S4 hibernation worked fine and didn't seem to trigger the bug Found several similar bug reports for Intel 965 / X3100 type laptops and Intel drivers in Ubuntu 14.04 and or Kernel 3.13. My suspicion is newer Intel video drivers have caused a number of regressions in the latest Kernels, especially with older Intel Chipsets. - [TOSHIBA Satellite U400] suspend/resume failure: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1290787 - [965gm regression v3.13] TOSHIBA Satellite U400 intel GM965/GL960 suspend/resume failure kernel 3.14 rc7, rc6, 3.13: https://bugs.freedesktop.org/show_bug.cgi?id=76520 - [Dell Inspiron 1525] Cannot resume from suspend: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331654 - Bug#747247: Problem Solved: https://lists.debian.org/debian-kernel/2014/07/msg00179.html Similar bugs and fixes for drm/i915 already backported to ubuntu kernel 3.13.0.35 http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_3.13.0-39.66/changelog * drm/i915: Avoid div-by-zero when pixel_multiplier is zero - - LP: #1347088 + - LP: #1347088 So the problem I had was additional issue not yet fixed by those previous patches. During reading up, I noticed that a change had occurred in the default acceleration method lntel drivers a while ago. I stumbled on other bugs like this one: - Re: Fonts in Firefox crumble (Mint 16 Mate RC): http://forums.linuxmint.com/viewtopic.php?f=47t=151054start=40 - The workaround/fix was to switch back to uxa After more reading up: * Three backends backends available for accelerating DDX: UXA, SNA and glamor * DDX: Device Dependent X, and is part of the 2D graphics device driver which is hardware specific. * The old methode is UXA - (Unified Acceleration Architecture). More mature and introduced to support the GEM driver model. * The new methode is SNA - (Sandybridge's New Acceleration). Targets newer chipsets. - * xf86-video-intel X.org driver in 13.1 uses the newer SNA acceleration by default. + * Ubuntu 14.04 xf86-video-intel X.org driver uses the newer SNA acceleration by default. My hardware was older (not SandyBridge), so reverting to the UXA acceleration option appears to be a promising workaround as using the SNA (default) option somehow triggers the resume bug. SNA is probably not well suited to or optimised for older graphics like X3100 :-/ A possible solution is for upstream maintainers (or Mint/Ubuntu via a patch) to revert to UXA if older Intel hardware is present and not force the SNA default. The proper fix might be to trace how SNA acceleration causes the suspend resume regression bug to surface, but given the resume crashes and reboots the system, it's hard to find evidence in logs. ** Also
[Bug 1390923] Re: Mint 17 fails to resume after suspend on Acer Extensa 5220 with Intel GM965/GL960 (GMA X3100) based graphics chipset
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 ** Also affects: xserver-xorg-video-intel via https://bugs.freedesktop.org/show_bug.cgi?id=86067 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/1390923 Title: Mint 17 fails to resume after suspend on Acer Extensa 5220 with Intel GM965/GL960 (GMA X3100) based graphics chipset To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1390923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1390923] Re: Mint 17 fails to resume after suspend on Acer Extensa 5220 with Intel GM965/GL960 (GMA X3100) based graphics chipset
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390923 Title: Mint 17 fails to resume after suspend on Acer Extensa 5220 with Intel GM965/GL960 (GMA X3100) based graphics chipset To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1390923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537851] Re: dhclient silently ignores unreadable config-file
** Changed in: dhcp3 (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/537851 Title: dhclient silently ignores unreadable config-file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/537851/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 537851] Re: dhclient silently ignores unreadable config-file
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 new location 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 trace-cust-dhcpclient.log: open(/home/user/Scripts/reroute/dhclient-cust-sbsa.conf, O_RDONLY) = -1 EACCES (Permission denied) In kern.log Nov 7 17:09:18 hostname kernel: [20777.329386] type=1400 audit(1320678558.977:25): apparmor=DENIED operation=open parent=8316 profile=/sbin/dhclient3 name=/home/user/Scripts/reroute/dhclient- cust-sbsa.conf pid=8317 comm=dhclient requested_mask=r denied_mask=r fsuid=0 ouid=1000 The trace was produced as follows: sudo strace -e trace=file dhclient -e IF_METRIC=0 -cf /home/enigma/Scripts/reroute/dhclient-cust-sbsa.conf usb0 trace-cust-dhcpclient.log ** Attachment added: strace log of file IO for dhclient https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/537851/+attachment/2588489/+files/trace-cust-dhcpclient.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/537851 Title: dhclient silently ignores unreadable config-file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/537851/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 537851] Re: dhclient silently ignores unreadable config-file
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/537851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537851] Re: dhclient silently ignores unreadable config-file
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 new location 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 trace-cust-dhcpclient.log: open(/home/user/Scripts/reroute/dhclient-cust-sbsa.conf, O_RDONLY) = -1 EACCES (Permission denied) In kern.log Nov 7 17:09:18 hostname kernel: [20777.329386] type=1400 audit(1320678558.977:25): apparmor=DENIED operation=open parent=8316 profile=/sbin/dhclient3 name=/home/user/Scripts/reroute/dhclient- cust-sbsa.conf pid=8317 comm=dhclient requested_mask=r denied_mask=r fsuid=0 ouid=1000 The trace was produced as follows: sudo strace -e trace=file dhclient -e IF_METRIC=0 -cf /home/enigma/Scripts/reroute/dhclient-cust-sbsa.conf usb0 trace-cust-dhcpclient.log ** Attachment added: strace log of file IO for dhclient https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/537851/+attachment/2588489/+files/trace-cust-dhcpclient.log -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/537851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
