[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
** Tags removed: regression-update verification-needed ** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Released Status in dkms source package in Disco: Fix Released Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837717] Re: [0.8 regression] zfs mount -a dataset mount ordering issues
** Changed in: zfs Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1837717 Title: [0.8 regression] zfs mount -a dataset mount ordering issues Status in Native ZFS for Linux: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Bug description: Update: I was able to reproduce it with a simpler schema (/ isn't always mounted before /var). This is to mimick the official zol guide with zfs on root: https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS $ zpool create -o ashift=12 -O atime=off -O canmount=off -O normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2 $ zfs create rpool/ROOT -o canmount=off -o mountpoint=none $ zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/ $ zfs create rpool/ROOT/ubuntu_123456/var $ zpool create -o ashift=12 -O atime=off -O canmount=off -O normalization=formD -O mountpoint=/ -R /mnt rpool /dev/vda2 $ zfs create rpool/ROOT -o canmount=off -o mountpoint=none $ zfs create rpool/ROOT/ubuntu_123456 -o mountpoint=/ $ zfs create rpool/ROOT/ubuntu_123456/var $ zfs create rpool/ROOT/ubuntu_123456/var/lib -o canmount=off $ zfs create rpool/var -o canmount=off $ zfs create rpool/var/lib $ zfs create rpool/var/games $ zfs create rpool/ROOT/ubuntu_123456/var/lib/apt # Zfs mount is what we expect (5 datasets mounted): $ zfs mount rpool/ROOT/ubuntu_123456/mnt rpool/ROOT/ubuntu_123456/var/mnt/var rpool/var/games /mnt/var/games rpool/var/lib /mnt/var/lib rpool/ROOT/ubuntu_123456/var/lib/apt /mnt/var/lib/apt $ zfs umount -a # Everything unmounted as expected: $ find /mnt/ /mnt/ # However, zfs mount -a doesn't mount everything in the correct order reliably: $ zfs mount -a cannot mount '/mnt': directory is not empty # In that case, rpool/ROOT/ubuntu_123456 wasn't mounted: $ zfs mount rpool/ROOT/ubuntu_123456/var/mnt/var rpool/var/lib /mnt/var/lib rpool/var/games /mnt/var/games rpool/ROOT/ubuntu_123456/var/lib/apt /mnt/var/lib/apt $ find /mnt/ /mnt/ /mnt/var /mnt/var/lib /mnt/var/lib/apt /mnt/var/games $ zfs umount -a $ find /mnt/ /mnt/ # Everything was umounted, let's try to remount all again: $ zfs mount -a cannot mount '/mnt/var/lib': failed to create mountpoint $ zfs mount rpool/ROOT/ubuntu_123456/mnt rpool/ROOT/ubuntu_123456/var/mnt/var rpool/var/games /mnt/var/games rpool/ROOT/ubuntu_123456/var/lib/apt /mnt/var/lib/apt #This time, rpool/ROOT/ubuntu_123456 was mounted, but not rpool/var/lib (before rpool/ROOT/ubuntu_123456/var/lib/apt) Note: the same ordering issue can happen on zfs umount -a. Tested as well with zfs 0.7: tried to zfs mount -a && zfs umount -a in loop, no issue: all datasets are mounted in the correct order reliably. Note that it seems to be slightly related to the version of zfs we created a pool with: - Try zfs mount -a on zfs 0.7 with a pool/datasets created under zfs 0.8: the ordering issues still happens. - However, the contrary isn't try: try zfs mount -a on zfs 0.8 with a pool/datasets created under zfs 0.7: there can be some ordering issues. There is nothing specific in the journal log: juil. 24 10:59:27 ubuntu kernel: ZFS: Loaded module v0.8.1-1ubuntu5, ZFS pool version 5000, ZFS filesystem version 5 juil. 24 10:59:39 ubuntu systemd[1]: mnt-var-lib.mount: Succeeded. juil. 24 10:59:39 ubuntu systemd[1116]: mnt-var-lib.mount: Succeeded. juil. 24 10:59:39 ubuntu systemd[1]: mnt-var-games.mount: Succeeded. juil. 24 10:59:39 ubuntu systemd[1116]: mnt-var-games.mount: Succeeded. juil. 24 10:59:42 ubuntu systemd[1116]: mnt-var-lib-apt.mount: Succeeded. juil. 24 10:59:42 ubuntu systemd[1]: mnt-var-lib-apt.mount: Succeeded. juil. 24 10:59:42 ubuntu systemd[1116]: mnt-var-games.mount: Succeeded. juil. 24 10:59:42 ubuntu systemd[1]: mnt-var-games.mount: Succeeded. juil. 24 10:59:42 ubuntu systemd[1116]: mnt-var.mount: Succeeded. juil. 24 10:59:42 ubuntu systemd[1]: mnt-var.mount: Succeeded. juil. 24 10:59:42 ubuntu systemd[1116]: mnt.mount: Succeeded. juil. 24 10:59:42 ubuntu systemd[1]: mnt.mount: Succeeded. juil. 24 10:59:45 ubuntu systemd[1116]: mnt-var-lib.mount: Succeeded. juil. 24 10:59:45 ubuntu systemd[1]: mnt-var-lib.mount: Succeeded. juil. 24 10:59:46 ubuntu systemd[1116]: mnt-var-games.mount: Succeeded. juil. 24 10:59:46 ubuntu systemd[1]: mnt-var-games.mount: Succeeded. juil. 24 11:01:06 ubuntu systemd[1116]: mnt-var-lib-apt.mount: Succeeded. juil. 24 11:01:06 ubuntu systemd[1]: mnt-var-lib-apt.mount: Succeeded. juil. 24 11:01:06 ubuntu systemd[1]: mnt-var-games.mount: Succeeded. juil. 24 11:01:06 ubuntu systemd[1116]: mnt-var-games.mount: Succeeded. juil. 24 11:01:06 ubuntu syst
[Kernel-packages] [Bug 1567557] Re: Performance degradation of "zfs clone"
** Changed in: zfs Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1567557 Title: Performance degradation of "zfs clone" Status in Native ZFS for Linux: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in zfs-linux source package in Zesty: Fix Released Status in zfs-linux source package in Artful: Fix Released Bug description: [SRU Justification] Creating tens of hundreds of clones can be prohibitively slow. The underlying mechanism to gather clone information is using a 16K buffer which limits performance. Also, the initial assumption is to pass in zero sized buffer to the underlying ioctl() to get an idea of the size of the buffer required to fetch information back to userspace. If we bump the initial buffer to a larger size then we reduce the need for two ioctl calls which improves performance. [Fix] Bump initial buffer size from 16K to 256K [Regression Potential] This is minimal as this is just a tweak in the initial buffer size and larger sizes are handled correctly by ZFS since they are normally used on the second ioctl() call once we have established the size of the buffer required from the first ioctl() call. Larger initial buffers just remove the need for the initial size estimation for most cases where the number of clones is less than ~5000. There is a risk that a larger buffer size could lead to a ENOMEM issue when allocating the buffer, but the size of buffer used is still trivial for modern large 64 bit servers running ZFS. [Test case] Create 4000 clones. With the fix this takes 35-40% less time than without the fix. See the example test.sh script as an example of how to create this many clones. -- I've been running some scale tests for LXD and what I've noticed is that "zfs clone" gets slower and slower as the zfs filesystem is getting busier. It feels like "zfs clone" requires some kind of pool-wide lock or something and so needs for all operations to complete before it can clone a new filesystem. A basic LXD scale test with btrfs vs zfs shows what I mean, see below for the reports. The test is run on a completely dedicated physical server with the pool on a dedicated SSD, the exact same machine and SSD was used for the btrfs test. The zfs filesystem is configured with those settings: - relatime=on - sync=disabled - xattr=sa So it shouldn't be related to pending sync() calls... The workload in this case is ultimately 1024 containers running busybox as their init system and udhcpc grabbing an IP. The problem gets significantly worse if spawning busier containers, say a full Ubuntu system. === zfs === root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 --image=images:alpine/edge/amd64 --privileged=true Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: zfs Storage version: 5 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 06:42:51.170] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 06:42:52.657] Starting the test [Apr 3 06:42:53.994] Started 8 containers in 1.336s [Apr 3 06:42:55.521] Started 16 containers in 2.864s [Apr 3 06:42:58.632] Started 32 containers in 5.975s [Apr 3 06:43:05.399] Started 64 containers in 12.742s [Apr 3 06:43:20.343] Started 128 containers in 27.686s [Apr 3 06:43:57.269] Started 256 containers in 64.612s [Apr 3 06:46:09.112] Started 512 containers in 196.455s [Apr 3 06:58:19.309] Started 1024 containers in 926.652s [Apr 3 06:58:19.309] Test completed in 926.652s === btrfs === Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: btrfs Storage version: 4.4 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 07:42:12.053] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 07:42:13.351] Starting the test [Apr 3 07:42:14.793] Started 8 containers in 1.442s [Apr 3 07:42:16.495] Started 16 containers in 3.144s [Apr 3 07:42:19.881] Started 32 containers in 6.530s [Apr 3 07:42:26.798] Started 64 co
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
** Changed in: dkms
Status: In Progress => Fix Released
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
Status in DKMS:
Fix Released
Status in dkms package in Ubuntu:
Fix Released
Status in dkms source package in Bionic:
Fix Released
Bug description:
update for SRU process:
[Impact]
1. dkms script is missing function find_module
2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
[Test case]
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
- the target dkms defined OBSOLETE_BY and FORCE
- user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- the dkms can be installed well.
[Regression potential]
medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
The logic has been verified by #5 and me.
Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
# tree = $1
# module = $2
find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843960] Re: cherrypick has_sipl fix
[PATCH][UNSTABLE][EOAN] UBUNTU: SAUCE: s390/sclp: Fix bit checked for has_sipl https://lists.ubuntu.com/archives/kernel-team/2019-September/103721.html ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Tags added: s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843960 Title: cherrypick has_sipl fix Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: cherrypick has_sipl fix from the s390 maintainer tree https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/patch/?id=4df9a82549cfed5b52da21e7d007b79b2ea1769a Otherwise, has_secure sysfs attribute is never correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1843960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843961] Re: s390/setup: Actually init kernel lock down
[PATCH][UNSTABLE][EOAN] UBUNTU: SAUCE: (lockdown) s390/setup: Actually init kernel lock down https://lists.ubuntu.com/archives/kernel-team/2019-September/103722.html ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Tags added: s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843961 Title: s390/setup: Actually init kernel lock down Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: Kernel lock down isn't initalized in common but in arch code. So initialize it for s390 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1843961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
in the final release of Linux 5.3 are going to be these patches? I ask because I am buying an amd laptop right now with ryzen 5 3550 H and want to know how was going this problem ! In an acer swift with AMD ryzen I had the problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate daily)
I can reproduce this issue on an Ubuntu 18.04-based distribution, too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842382 Title: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate daily) Status in linux package in Ubuntu: Triaged Bug description: Using Lubuntu 19.10 daily 'live' : (later confirmed with Ubuntu/kubuntu/xubuntu too if `vlc` is added if not already present) From menu option, from pcmanfm-qt (trying to open an appropriate file), or from terminal I've been unable to start vlc. lubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lubuntu:~$ No crash reports are visible (/var/crash/ is empty) and I see no reason, but I cannot get vlc to play files, or open. I'll continue to explore as I'm able. QA-test on lenovo thinkpad x201 (i5-m520, 4gb, i915) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: vlc 3.0.8-2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CurrentDesktop: LXQt Date: Tue Sep 3 06:03:17 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190902) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate daily)
I can confirm that: Kubuntu 18.04 daily ISO with linux-image-5.0.0-27-generic = vlc fails to start Kubuntu 18.04.3 release ISO with linux-image-5.0.0-23-generic = vlc starts ok /proc/self/maps in the daily looks the same as Eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842382 Title: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate daily) Status in linux package in Ubuntu: Triaged Bug description: Using Lubuntu 19.10 daily 'live' : (later confirmed with Ubuntu/kubuntu/xubuntu too if `vlc` is added if not already present) From menu option, from pcmanfm-qt (trying to open an appropriate file), or from terminal I've been unable to start vlc. lubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lubuntu:~$ No crash reports are visible (/var/crash/ is empty) and I see no reason, but I cannot get vlc to play files, or open. I'll continue to explore as I'm able. QA-test on lenovo thinkpad x201 (i5-m520, 4gb, i915) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: vlc 3.0.8-2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CurrentDesktop: LXQt Date: Tue Sep 3 06:03:17 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190902) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate daily)
The reason why vlc does not start is definitely the overlay filesystem. How can I know that? I use Ubuntu on a fully encrypted USB stick with overlay root filesystem (which makes the USB super fast, even faster than ssd). To enable the overlay root filesystem I use the following initramfs script: https://gist.github.com/niun/34c945d70753fc9e2cc7 (FYI: the script has a little bug, it can not handle tabulators in fstab, you have to fix that if you want use it for testing, just insert tr "\t" ' ' before grep -v ' / ') You can disable this script with the kernel command line parameter disable-root-to=yes. I tested, once with overlay fs and once without overlay fs. vlc starts as long as you do not use overlay fs. But it does not start with enabled overlay fs. Therefore, the reason must be the overlay filesystem. It can be assumed that thus bug affects all systems that use overlay fs. Not only debian but all distributions. Therefore, I would give this bug a high priority. In addition, my strace looks a bit different than the strace that has been posted here (see attachment). Last 5 lines: mmap2(NULL, 26374, PROT_READ, MAP_SHARED, 3, 0) = 0xb7f94000 close(3)= 0 futex(0xb7f2bfe4, FUTEX_WAKE_PRIVATE, 2147483647) = 0 exit_group(1) = ? +++ exited with 1 +++ I suspect the futex () call fails. The bug probably has nothing to do with /proc/self/maps. ** Attachment added: "strace vlc" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+attachment/5288850/+files/vlc_strace.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842382 Title: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate daily) Status in linux package in Ubuntu: Triaged Bug description: Using Lubuntu 19.10 daily 'live' : (later confirmed with Ubuntu/kubuntu/xubuntu too if `vlc` is added if not already present) From menu option, from pcmanfm-qt (trying to open an appropriate file), or from terminal I've been unable to start vlc. lubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lubuntu:~$ No crash reports are visible (/var/crash/ is empty) and I see no reason, but I cannot get vlc to play files, or open. I'll continue to explore as I'm able. QA-test on lenovo thinkpad x201 (i5-m520, 4gb, i915) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: vlc 3.0.8-2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CurrentDesktop: LXQt Date: Tue Sep 3 06:03:17 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190902) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
I can confirm the same is happening to me at Disco running on Dell XPS 13 9380. Disabling wakeup for XHC a sort of helps, however, it also disables wakeup for a touchpad; I suppose this is because pci::00:14.0 is a USB controller so everything under USB bus is disabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735099] Re: Realtek Card Reader not working (kernel driver)
The linked github repository doesn't break out whatever the fix is to the rtsx_pci driver is. Therefore it is all but impossible to figure out what was changed. Another user reported this today with 5.0.0-27-generic where 64GB cards are readable but 256GB cards are not. It isn't clear if the power- signalling errors are critical or incidental: Sep 15 11:55:59 kubuntu-laptop kernel: mmc0: cannot verify signal voltage switch Sep 15 11:56:00 kubuntu-laptop kernel: mmc0: new ultra high speed SDR104 SDXC card at address 0001 Sep 15 11:56:00 kubuntu-laptop kernel: mmcblk0: mmc0:0001 GC2QT 59.6 GiB Sep 15 11:56:00 kubuntu-laptop kernel: mmcblk0: p1 Sep 15 11:57:06 kubuntu-laptop kernel: mmc0: card 0001 removed Sep 15 11:57:14 kubuntu-laptop kernel: mmc0: cannot verify signal voltage switch Sep 15 11:57:14 kubuntu-laptop kernel: mmc0: tuning execution failed: -22 Sep 15 11:57:14 kubuntu-laptop kernel: mmc0: error -22 whilst initialising SD card Sep 15 11:57:15 kubuntu-laptop kernel: mmc0: error -110 whilst initialising SD card Sep 15 11:57:17 kubuntu-laptop kernel: mmc0: cannot verify signal voltage switch Sep 15 11:57:17 kubuntu-laptop kernel: mmc0: tuning execution failed: -22 Sep 15 11:57:17 kubuntu-laptop kernel: mmc0: error -22 whilst initialising SD card Sep 15 11:58:08 kubuntu-laptop kernel: mmc0: cannot verify signal voltage switch Sep 15 11:58:08 kubuntu-laptop kernel: mmc0: new ultra high speed SDR104 SDXC card at address 0001 Sep 15 11:58:08 kubuntu-laptop kernel: mmcblk0: mmc0:0001 GC2QT 59.6 GiB Sep 15 11:58:08 kubuntu-laptop kernel: mmcblk0: p1 Sep 15 11:58:46 kubuntu-laptop kernel: mmc0: card 0001 removed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1735099 Title: Realtek Card Reader not working (kernel driver) Status in linux package in Ubuntu: Triaged Bug description: This is the situation if I use the normal 4.13 kernel driver [ 1899.245301] mmc0: cannot verify signal voltage switch [ 1899.377540] mmc0: new ultra high speed SDR104 SDXC card at address e624 [ 1899.401829] mmcblk0: mmc0:e624 AGGCE 59.5 GiB [ 1899.404700] mmcblk0: p1 [ 1899.620084] mmcblk0: error -110 sending status command, retrying [ 1899.620231] mmcblk0: error -22 sending status command, retrying [ 1899.620419] mmcblk0: error -22 sending status command, aborting [ 1899.905535] mmc0: cannot verify signal voltage switch [ 1900.136253] mmcblk0: error -22 sending status command, retrying [ 1900.136396] mmcblk0: error -22 sending status command, retrying [ 1900.240070] mmcblk0: error -110 sending status command, aborting [ 1900.240084] print_req_error: I/O error, dev mmcblk0, sector 8 but it works perfectly if I use the patched driver on kernel 4.4-4.7 this one https://github.com/Zibri/Realtek-rts5229-for-4.4-kernel the problem is that I can't compile it on 4.13 and anyway this affects a lot of systems using 5229/5227 many laptops use this. any solution?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
Huh, I wonder if this is a Gnome Shell issue and not a kernel issue after all. After switching to Ubuntu Mate, and uninstalling the kernel mentioned above, I have not had a flicker yet. Anecdotally, I have also heard of people installing KDE on an XPS 13 9380 and also not having this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735099] Re: Realtek Card Reader not working (kernel driver)
Just wanted to update, I am the user TJ is referring to. The issue was resolved after running "sudo update-initramfs -u" after the commands in the readme of the linked github repository as detailed here: http ://baby-panda.github.io/linux/RTS5229_driver/ The new driver installation be verified by running "lspci -v" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1735099 Title: Realtek Card Reader not working (kernel driver) Status in linux package in Ubuntu: Triaged Bug description: This is the situation if I use the normal 4.13 kernel driver [ 1899.245301] mmc0: cannot verify signal voltage switch [ 1899.377540] mmc0: new ultra high speed SDR104 SDXC card at address e624 [ 1899.401829] mmcblk0: mmc0:e624 AGGCE 59.5 GiB [ 1899.404700] mmcblk0: p1 [ 1899.620084] mmcblk0: error -110 sending status command, retrying [ 1899.620231] mmcblk0: error -22 sending status command, retrying [ 1899.620419] mmcblk0: error -22 sending status command, aborting [ 1899.905535] mmc0: cannot verify signal voltage switch [ 1900.136253] mmcblk0: error -22 sending status command, retrying [ 1900.136396] mmcblk0: error -22 sending status command, retrying [ 1900.240070] mmcblk0: error -110 sending status command, aborting [ 1900.240084] print_req_error: I/O error, dev mmcblk0, sector 8 but it works perfectly if I use the patched driver on kernel 4.4-4.7 this one https://github.com/Zibri/Realtek-rts5229-for-4.4-kernel the problem is that I can't compile it on 4.13 and anyway this affects a lot of systems using 5229/5227 many laptops use this. any solution?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844072] [NEW] nouveau core notifier timeout
Public bug reported: Newly installed Ubuntu 19.04 system. AMD Ryzen 3700X. NVIDIA GeForce RTX 2060. When the system is left for a while and the screen goes to sleep, then sometimes but not always, upon return there is no reaction to keyboard and mouse. Most likely the system is still running fine, but the only thing one can do is reboot. Afterwards, /var/log/kern.log shows lines like Sep 15 21:50:50 if kernel: [35590.756691] nouveau :07:00.0: DRM: core notifier timeout Sep 15 21:50:52 if kernel: [35592.756660] nouveau :07:00.0: DRM: wndw-0: timeout Ubuntu 5.0.0-27.28-generic 5.0.21 $ sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1844072/+attachment/5288871/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844072 Title: nouveau core notifier timeout Status in linux package in Ubuntu: Incomplete Bug description: Newly installed Ubuntu 19.04 system. AMD Ryzen 3700X. NVIDIA GeForce RTX 2060. When the system is left for a while and the screen goes to sleep, then sometimes but not always, upon return there is no reaction to keyboard and mouse. Most likely the system is still running fine, but the only thing one can do is reboot. Afterwards, /var/log/kern.log shows lines like Sep 15 21:50:50 if kernel: [35590.756691] nouveau :07:00.0: DRM: core notifier timeout Sep 15 21:50:52 if kernel: [35592.756660] nouveau :07:00.0: DRM: wndw-0: timeout Ubuntu 5.0.0-27.28-generic 5.0.21 $ sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844072] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1844072 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844072 Title: nouveau core notifier timeout Status in linux package in Ubuntu: Incomplete Bug description: Newly installed Ubuntu 19.04 system. AMD Ryzen 3700X. NVIDIA GeForce RTX 2060. When the system is left for a while and the screen goes to sleep, then sometimes but not always, upon return there is no reaction to keyboard and mouse. Most likely the system is still running fine, but the only thing one can do is reboot. Afterwards, /var/log/kern.log shows lines like Sep 15 21:50:50 if kernel: [35590.756691] nouveau :07:00.0: DRM: core notifier timeout Sep 15 21:50:52 if kernel: [35592.756660] nouveau :07:00.0: DRM: wndw-0: timeout Ubuntu 5.0.0-27.28-generic 5.0.21 $ sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
the source code for the serverguide is migrating to a different markup language for 20.04. The migration was done a few days before these revisions were committed. They need to be copied to the new source. I am attempting to add "target to series" stuff to this bug report, but it is not working, like other ones I have done already. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: Fix Released Status in hw-detect source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: Fix Released Status in debian-installer source package in Cosmic: Fix Released Status in hw-detect source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: Fix Released Status in debian-installer source package in Disco: Fix Released Status in hw-detect source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: Fix Released Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect/partman-iscsi package: See comments 11, 12, 13. [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect/partman-iscsi: - d-i: kernel version update to include iscsi_ibft module, based on kernel released to -updates plus one week monitoring bug reports -- it should be OK. Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64 on baremetal -- see comment 11. - hw-detect: low, the changes are enabled by a preseed option. see comment 12. - partman-iscsi: low, simple changes, plus one fix that has been tested in detail, and falls back to previous behavior if it fails. see comment 13. [Other Info] * This has been verified both by the developer with a simple iSCSI iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE) and by an user with system/firmware that supports iBFT for iSCSI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
But just to confirm, I think the patched kernel did improve the amount of flickering. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844081] [NEW] Touch Pad not working on lenovo thinkpad L480
Public bug reported: Version: Ubuntu 5.0.0-27.28-generic 5.0.21 Touchpad is not working at all on my Lenovo Thinkpad L480 Computer Type: 20LT-S59S00 S/N:PF-16AJ83 cat /proc/bus/input/devices: I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=22d4 Product=130c Version=0100 N: Name="Laview Technology Mionix Naos 7000" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:22D4:130C.0001/input/input6 U: Uniq=STM32 H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=22d4 Product=130c Version=0100 N: Name="Laview Technology Mionix Naos 7000 Keyboard" P: Phys=usb-:00:14.0-1/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:22D4:130C.0002/input/input7 U: Uniq=STM32 H: Handlers=sysrq kbd event5 B: PROP=0 B: EV=100013 B: KEY=e080ffdf01cf fffe B: MSC=10 I: Bus=0019 Vendor=17aa Product=5054 Version=4101 N: Name="ThinkPad Extra Buttons" P: Phys=thinkpad_acpi/input0 S: Sysfs=/devices/platform/thinkpad_acpi/input/input8 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=33 B: KEY=10040 0 1804 0 50 0 1701b02102004 c000280051115000 10e 0 B: MSC=10 B: SW=8 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04ca Product=7070 Version=0023 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input10 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input17 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-27-generic 5.0.0-27.28 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bendercharls 1385 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 15 19:38:58 2019 InstallationDate: Installed on 2019-09-16 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04ca:7070 Lite-On Technology Corp. Bus 001 Device 005:
[Kernel-packages] [Bug 1844081] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844081 Title: Touch Pad not working on lenovo thinkpad L480 Status in linux package in Ubuntu: Confirmed Bug description: Version: Ubuntu 5.0.0-27.28-generic 5.0.21 Touchpad is not working at all on my Lenovo Thinkpad L480 Computer Type: 20LT-S59S00 S/N:PF-16AJ83 cat /proc/bus/input/devices: I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=22d4 Product=130c Version=0100 N: Name="Laview Technology Mionix Naos 7000" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:22D4:130C.0001/input/input6 U: Uniq=STM32 H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=22d4 Product=130c Version=0100 N: Name="Laview Technology Mionix Naos 7000 Keyboard" P: Phys=usb-:00:14.0-1/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:22D4:130C.0002/input/input7 U: Uniq=STM32 H: Handlers=sysrq kbd event5 B: PROP=0 B: EV=100013 B: KEY=e080ffdf01cf fffe B: MSC=10 I: Bus=0019 Vendor=17aa Product=5054 Version=4101 N: Name="ThinkPad Extra Buttons" P: Phys=thinkpad_acpi/input0 S: Sysfs=/devices/platform/thinkpad_acpi/input/input8 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=33 B: KEY=10040 0 1804 0 50 0 1701b02102004 c000280051115000 10e 0 B: MSC=10 B: SW=8 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04ca Product=7070 Version=0023 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input10 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input17 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug D
[Kernel-packages] [Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies)
Lubuntu 18.04 daily (2019-09-15) Vlc is not installed by default on 18.04 (mpv is used), however adding it via `apt install` during live session has same issue as with eoan/1910; it won't start from menu or terminal. Thanks to Rik Mills & Matthias lubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lublubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lubuntu:~$ head /etc/apt/sources.list deb cdrom:[Lubuntu 18.04.3 LTS _Bionic Beaver_ - Release amd64 (20190915)]/ bionic main multiverse restricted universe lubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lubuntu:~$ head /etc/apt/sources.list deb cdrom:[Lubuntu 18.04.3 LTS _Bionic Beaver_ - Release amd64 (20190915)]/ bionic main multiverse restricted universe lubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lubuntu:~$ head /etc/apt/sources.list deb cdrom:[Lubuntu 18.04.3 LTS _Bionic Beaver_ - Release amd64 (20190915)]/ bionic main multiverse restricted universe untu:~$ head /etc/apt/sources.list deb cdrom:[Lubuntu 18.04.3 LTS _Bionic Beaver_ - Release amd64 (20190915)]/ bionic main multiverse restricted universe This was done on a QA-test on 18.04 daily; however it won't be recorded as a critical bug there due to vlc not being installed on default ISO for Lubuntu. I'll endeavor to check x86 too. ** Summary changed: - /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate daily) + /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies) ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842382 Title: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies) Status in linux package in Ubuntu: Triaged Bug description: Using Lubuntu 19.10 daily 'live' : (later confirmed with Ubuntu/kubuntu/xubuntu too if `vlc` is added if not already present) From menu option, from pcmanfm-qt (trying to open an appropriate file), or from terminal I've been unable to start vlc. lubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lubuntu:~$ No crash reports are visible (/var/crash/ is empty) and I see no reason, but I cannot get vlc to play files, or open. I'll continue to explore as I'm able. QA-test on lenovo thinkpad x201 (i5-m520, 4gb, i915) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: vlc 3.0.8-2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CurrentDesktop: LXQt Date: Tue Sep 3 06:03:17 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190902) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies)
Lubuntu 18.04 daily (2019-09-15) i386 tested on hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, winfast clone of nvidia 7600gt) as with amd64, vlc is not installed by default, so had to `sudo apt install vlc` on live system for test, once installed it failed to start from terminal or menu in same manner as amd64 18.04 or 19.10 ** Tags added: i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842382 Title: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies) Status in linux package in Ubuntu: Triaged Bug description: Using Lubuntu 19.10 daily 'live' : (later confirmed with Ubuntu/kubuntu/xubuntu too if `vlc` is added if not already present) From menu option, from pcmanfm-qt (trying to open an appropriate file), or from terminal I've been unable to start vlc. lubuntu@lubuntu:~$ vlc VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) lubuntu@lubuntu:~$ No crash reports are visible (/var/crash/ is empty) and I see no reason, but I cannot get vlc to play files, or open. I'll continue to explore as I'm able. QA-test on lenovo thinkpad x201 (i5-m520, 4gb, i915) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: vlc 3.0.8-2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.415 CurrentDesktop: LXQt Date: Tue Sep 3 06:03:17 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190902) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg
The bug was fixed in nvidia-settings 418.56, but I am using the nvidia 1650 gpu and the 418.56 driver doesn't support my gpu. Will the fix be released for the 430 driver as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-settings source package in Disco: In Progress Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
