[Kernel-packages] [Bug 1949924] Re: yelp crashes in wayland session
This seems to be NVIDIA related (I'm using nvidia-driver-470). Downgrading the libnvidia-egl-wayland1 package to the version used in impish fixes the issue; hence it's a 1.1.9 regression. Setting GDK_BACKEND=x11, as mentioned in the upstream issue, works around the problem. ** Bug watch added: github.com/NVIDIA/egl-wayland/issues #27 https://github.com/NVIDIA/egl-wayland/issues/27 ** Also affects: egl-wayland via https://github.com/NVIDIA/egl-wayland/issues/27 Importance: Unknown Status: Unknown ** Also affects: egl-wayland (Ubuntu) Importance: Undecided Status: New ** Changed in: yelp (Ubuntu) Importance: High => Undecided ** Changed in: yelp (Ubuntu) Status: New => Invalid ** Tags added: regression-release ** Summary changed: - yelp crashes in wayland session + yelp crashes in wayland session with NVIDIA 470 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to egl-wayland in Ubuntu. https://bugs.launchpad.net/bugs/1949924 Title: yelp crashes in wayland session with NVIDIA 470 Status in NVIDIA / egl-wayland: Unknown Status in egl-wayland package in Ubuntu: New Status in yelp package in Ubuntu: Invalid Bug description: $ yelp yelp: ../src/wayland-thread.c:87: wlExternalApiLock: Assertion `!"failed to lock pthread mutex"' failed. Aborted (core dumped) This does not happen in Debian testing, and it also works as expected in an Ubuntu on Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 41.1-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 5 02:51:43 2021 InstallationDate: Installed on 2019-11-10 (725 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1949924/+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 195982] Re: Shift key (and caps lock) stop working when using VMWare
@Gary: Please submit a new bug report. You won't call anyone's attention by a comment on this old closed one. -- 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/195982 Title: Shift key (and caps lock) stop working when using VMWare Status in Linux: Invalid Status in linux package in Ubuntu: Won't Fix Status in xkeyboard-config package in Ubuntu: Invalid Status in Gentoo Linux: New Bug description: [Problem] VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys stopping functionality when running under VMWare, requiring the user to setup their configuration settings manually in VMWare. For a detailed explanation see the following article: http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html [Original Report] After a day or so of running the shift key mysteriously stops working as does the cap lock. In other words I cannot enter shifted characters of any kind. The keyboard is connected to a KVM and all other systems respond to it properly. In additional any VMWare sessions I have open respond correctly. So I have the condition where all non-vmware applications in Ubuntu Hardy (all updates applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT applications within an active (a paused/restarted session also works) VMWare sessions running DO recognize the key. When this condition occurs ALL applications (except those within a VMWare session) are also unstable and will usually crash within a few keystrokes.If I continue to operate in this mode. I cannot pinpoint what, if any, application triggers this. It has always happened while working within terminal/browser/vmware sessions and NOT when opening a new application. It could be related to the KVM switch, but none of my other systems (2 Mandriva, 1 Windows) are affected by this. This bug has been present on my system for a number of days across daily updates and reboots (if the update requested it) and I think since I installed Hardy Alpha 1. A work around: log off and back on. A reboot/restart does not appear to be needed. Error logs show some unusual activity. --- MARK ... ... kernel ... rtc lost 7 interrupts ... --- MARK --- Plus some segfaults indicating which application crashed as I tried to type into it (mouse works fine). System: HP dv9743cl (which otherwise works lovely) Ubuntu: Hardy 8.04 (from lsb-release) TEST CASE: 1. Click inside the VM and 2. Hold any of the Ctrl, Alt and/or shift keys while releasing the keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt to revert back to windowed mode, as the cursor is then released from the VM). WORKAROUND: After this happens to recover your keyboard execute 'setxkbmap' in a terminal To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/195982/+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 1902001] Re: USB keyboard layout incorrect after unplugging and replugging
*** This bug is a duplicate of bug 1899206 *** https://bugs.launchpad.net/bugs/1899206 ** This bug is no longer a duplicate of bug 1899509 Mouse/touchpad settings not applied on hotplug/reconnect/resume ** This bug has been marked a duplicate of bug 1899206 Keyboard and mouse configuration not persisting on USB keyboard unplug/reconnect -- 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/1902001 Title: USB keyboard layout incorrect after unplugging and replugging Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Kernel version: 5.4.0-52-generic (but problem began with 5.4.0-51-generic) Keyboard: Bus 001 Device 018: ID 056e:1063 Elecom Co., Ltd ELECOM TK-FCP097 Expected behaviour: USB keyboard layout remains the same when unplugging and replugging in same keyboard (This was the behaviour on 5.4.0-48-generic and earlier.) What happened instead: USB keyboard layout changes from: < _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,jp,us,us", ",,intl,", "grp_led:scroll" to: > _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,us", ",intl", "grp:alt_shift_toggle,grp_led:scroll" (output of xprop -root | grep XKB ) The keyboard layout is reset to the correct layout after logging out and back in (or after suspend/resume); however, unplugging and replugging the keyboard in causes the same unexpected behaviour. Same problem occurs with a different USB keyboard: Bus 001 Device 019: ID 0d62:8070 Darfon Electronics Corp. ELECOM Wired Keyboard ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tyler 18578 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 16:35:31 2020 InstallationDate: Installed on 2020-02-05 (266 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude 5500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=fa5c4fdb-0e37-4ef5-b109-3c129736f66c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-12 (170 days ago) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd07/06/2020:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902001/+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 1860519] Re: Out of memory running crashkernel in ubuntu18.04.1. (Regression/qla2xxx/ubuntu18.04.1/BostonLC)(Documentation?)
This is not a bug about the Ubuntu desktop guide. Please stop using ubuntu-docs for bugs like this. ** No longer affects: ubuntu-docs (Ubuntu) -- 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/1860519 Title: Out of memory running crashkernel in ubuntu18.04.1. (Regression/qla2xxx/ubuntu18.04.1/BostonLC)(Documentation?) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Naresh Bannoth - 2018-06-06 01:49:02 == ---Problem Description--- getting the following kernel panic message while trying to dump the crash over local directory of ubuntu18.04.1. "Kernel panic - not syncing: Out of memory and no killable processes..." This is a Regression BUG, as it worked fine in Ubuntu18.04 for local dump. configuration details are as follows, root@ltciofvtr-bostonlc1:~# free -g totalusedfree shared buff/cache available Mem:123 20 97 0 5 101 Swap: 1 0 1 root@ltciofvtr-bostonlc1:~# df -h Filesystem Size Used Avail Use% Mounted on udev 59G 0 59G 0% /dev tmpfs13G 21M 13G 1% /run /dev/sde2 5.5T 98G 5.1T 2% / tmpfs62G 0 62G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs62G 0 62G 0% /sys/fs/cgroup tmpfs13G 0 13G 0% /run/user/0 tmpfs 128K 0 128K 0% /var/lib/lxd/shmounts tmpfs 128K 0 128K 0% /var/lib/lxd/devlxd root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# service kdump-tools restart root@ltciofvtr-bostonlc1:~# service kdump-tools status ? kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Tue 2018-06-05 06:51:45 EDT; 6s ago Process: 18478 ExecStop=/etc/init.d/kdump-tools stop (code=exited, status=0/SUCCESS) Process: 18519 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 18519 (code=exited, status=0/SUCCESS) Jun 05 06:51:44 ltciofvtr-bostonlc1 systemd[1]: Starting Kernel crash dump capture service... Jun 05 06:51:44 ltciofvtr-bostonlc1 kdump-tools[18519]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz Jun 05 06:51:44 ltciofvtr-bostonlc1 kdump-tools[18519]: * Creating symlink /var/lib/kdump/initrd.img Jun 05 06:51:44 ltciofvtr-bostonlc1 kdump-tools[18519]: Modified cmdline:root=UUID=6e1afd6a-a199-4bc5-a324-b65d5607d03b ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb Jun 05 06:51:45 ltciofvtr-bostonlc1 kdump-tools[18519]: * loaded kdump kernel Jun 05 06:51:45 ltciofvtr-bostonlc1 systemd[1]: Started Kernel crash dump capture service. root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# cat /proc/cmdline root=UUID=6e1afd6a-a199-4bc5-a324-b65d5607d03b ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=6e1afd6a-a199-4bc5-a324-b65d5607d03b ro quiet splash nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# cat /sys/kernel/kexec_crash_loaded 1 root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# cat /etc/default/kdump-tools | grep -i crash KDUMP_COREDIR="/var/crash" KDUMP_COREDIR="/var/crash" # the crash dump. The syntax must be {HOSTNAME}:{MOUNTPOINT} # (e.g. remote:/var/crash) root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# == Snippet of Error logs, [ OK ] Reached target System Time Synchronized. [ 32.167186] Out of memory: Kill process 2958 (systemd-udevd) score 1 or sacrifice child [ 32.167270] Killed process 2958 (systemd-udevd) total-vm:23616kB, anon-rss:0kB, file-rss:1856kB, shmem-rss:0kB [ 32.180509] Out of memory: Kill process 432 (systemd-network) score 1 or sacrifice child [ 32.180565] Killed process 432 (systemd-network) total-vm:19520kB,
[Kernel-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
@Maxim Smih: Why did you subscribe all those teams and individuals? If you don't have a good reason (I doubt you have) it's bad manners. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, when I turn off the computer, it hangs on the logo. I can not turn off the computer using alt + SysRq + REISUO. The light on the system unit continues to light, and the fan runs. This is a problem with kernel 5.0, 5.3 Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq https://ibb.co/4JMGwvC sudo dmesg|grep ACPI|less - https://pastebin.com/PZxRGNyJ ProblemType: Bug DistroRelease: Ubuntu 18.04 Пакет: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 CurrentDesktop: XFCE Дата: Четверг 5 09:44:35 2019 Дата установки: установлено в 2019-08 -09 (26 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 (20190210) ProcEnviron: LANGUAGE = ru_UA: ru PATH = (пользовательский, нет пользователя) XDG_RUNTIME_ DIR = LANG = ru_UA.UTF -8 SHELL = / bin / bash SourcePackage: gvfs UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) --- Тип проблемы: ошибка ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 AudioDevicesInUse: КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID / dev / snd / controlC0: макс. 1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Установлен 2019-08-09 (37 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 (20190210) IwConfig: enp0s25 без беспроводных расширений. enp7s4 нет беспроводных расширений. нет никаких беспроводных расширений. Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower Пакет: Linux (не установлен) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень = UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1 ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18 RelatedPackageV ersions: linux- restricted- modules- 4.15.0- 62-родовое N / A linux- backports- modules- 4.15.0 - 62-типовой N / A linux-прошивка 1.173.9 RfKill: Теги: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: нет журнала обновления (возможно, новая установка) Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 26.10.2015 dmi. bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board. asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis. asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: rn2820h: rvr: cvnHewlett- Packard: ct6: cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dvtwelet dv00 от компании HP : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865/+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 1782835] Re: d-i step "Configure the keyboard" fails
This might be related to the fix of bug #1762952, whose purpose is to not accomplish keyboard configuration in connection with an upgrade of the keyboard-configuration package. The complaint seems to be "dpkg-query: not found", and the dpkg-query command is indeed used in the pending change. Is d-i run in an environment where dpkg is not present? -- 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/1782835 Title: d-i step "Configure the keyboard" fails Status in console-setup package in Ubuntu: Fix Committed Status in console-setup source package in Bionic: Fix Committed Bug description: Testing a bionic build of d-i w/ proposed results in a failure. From d-i's /var/log/syslog: Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected Jul 20 20:03:25 main-menu[897]: (process:1567): /var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' failed with error code 127 Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' failed. Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:46 kernel: [ 224.155631] random: crng init done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1782835/+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 1245081] Re: macbook keyboard layout maps the tilde key to something else
There is an XKB option solution to this issue on Debian/Ubuntu: setxkbmap -option apple:badmap -- 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/1245081 Title: macbook keyboard layout maps the tilde key to something else Status in linux package in Ubuntu: Confirmed Bug description: 1. install ubuntu on Macbook Air 6,2 2. press the key with the tilde ('~') written on it. 3. see that is prints '§' instead. This is particularly annoying since the way to switch between windows uses the tilde. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kms1491 F pulseaudio /dev/snd/controlC1: kms1491 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=9e7b2d0e-6a44-4ad7-9725-f9a3f5f39c33 InstallationDate: Installed on 2013-10-25 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac (20131016.1) MachineType: Apple Inc. MacBookAir6,2 MarkForUpload: True NonfreeKernelModules: wl Package: linux 3.11.0.12.13 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=079cbe6b-6488-4e57-85d3-c3e3e2fcbe40 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/12/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B01.1307121317 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B01.1307121317:bd07/12/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245081/+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 1584106] Re: Login to Unity session fails with linux 4.4.0-22
4.4.0-23.41 is in -release - let's consider this fixed. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1584106 Title: Login to Unity session fails with linux 4.4.0-22 Status in linux package in Ubuntu: Fix Released Bug description: My attempts to launch Unity sessions on an updated yakkety fails with linux 4.4.0-22 (both 4.4.0-22.39 and 4.4.0-22.40). Just some blinking on the screen, and I'm thrown back to the greeter. It happens when I try to launch a guest session too, so it shouldn't be anything in my $HOME. linux 4.4.0-21.37 does not trigger this issue. Attaching .xsession-errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584106/+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 1584106] Re: Login to Unity session fails with linux 4.4.0-22
I installed linux 4.4.0-23.41 from yakkety-proposed, and that fixed the issue. Fortunately I didn't meet the problem on xenial; the problem was linux 4.4.0-22 on Ubuntu 16.10, but since it's fixed in -proposed, it will soon be history, right? (don't know how to use apport-collect in a situation like this) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: unity (Ubuntu Xenial) ** Tags removed: xenial -- 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/1584106 Title: Login to Unity session fails with linux 4.4.0-22 Status in linux package in Ubuntu: Confirmed Status in unity package in Ubuntu: New Bug description: My attempts to launch Unity sessions on an updated yakkety fails with linux 4.4.0-22 (both 4.4.0-22.39 and 4.4.0-22.40). Just some blinking on the screen, and I'm thrown back to the greeter. It happens when I try to launch a guest session too, so it shouldn't be anything in my $HOME. linux 4.4.0-21.37 does not trigger this issue. Attaching .xsession-errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584106/+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 1584106] [NEW] Login to Unity session fails with linux 4.4.0-22
Public bug reported: My attempts to launch Unity sessions on an updated yakkety fails with linux 4.4.0-22 (both 4.4.0-22.39 and 4.4.0-22.40). Just some blinking on the screen, and I'm thrown back to the greeter. It happens when I try to launch a guest session too, so it shouldn't be anything in my $HOME. linux 4.4.0-21.37 does not trigger this issue. Attaching .xsession-errors. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Attachment added: ".xsession-errors" https://bugs.launchpad.net/bugs/1584106/+attachment/4666992/+files/.xsession-errors ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- 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/1584106 Title: Login to Unity session fails with linux 4.4.0-22 Status in linux package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: My attempts to launch Unity sessions on an updated yakkety fails with linux 4.4.0-22 (both 4.4.0-22.39 and 4.4.0-22.40). Just some blinking on the screen, and I'm thrown back to the greeter. It happens when I try to launch a guest session too, so it shouldn't be anything in my $HOME. linux 4.4.0-21.37 does not trigger this issue. Attaching .xsession-errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584106/+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 1503655] Re: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107
I have successfully installed and run these kernels: - version 3.13.0-66.108 from trusty-proposed (on Ubuntu 14.04 64bits) - version 3.19.0-31.36 from vivid-proposed (on Ubuntu 15.04 32bits) ** Tags removed: verification-needed-trusty verification-needed-vivid ** Tags added: verification-done-trusty verification-done-vivid -- 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/1503655 Title: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107 Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux-lts-utopic source package in Vivid: Invalid Status in linux source package in Wily: Confirmed Status in linux-lts-utopic source package in Wily: Invalid Bug description: With the latest kernel in trusty-proposed I seem to get panics on my X230 laptop: BUG: unable to handle kernel paging request at fff8 IP: [] eventpoll_release_file+0x46/0xa0 PGD 1c11067 PUD 1c13067 PMD 0 Oops: [#1] SMP Modules linked in: snd_hrtimer ip6table_filter ip6_tables ebtable_nat ebt CPU: 1 PID: 1939 Comm: pulseaudio Not tainted 3.13.0-66-generic #107-Ubun Hardware name: LENOVO 2324CTO/2324CTO, BIOS G2ET94WW (2.54 ) 04/30/2013 task: 8800c2068000 ti: 8800c4826000 task.ti: 8800c4826000 RIP: 0010:[] [] eventpoll_release_fi RSP: 0018:8800c4827e78 EFLAGS: 00010286 RAX: RBX: ffb7 RCX: 000f RDX: 0100 RSI: RDI: 81c72e80 RBP: 8800c4827ea0 R08: R09: 0004 R10: 880210471e61 R11: 0206 R12: ffa8 R13: 880210471e61 R14: 8800c4bc6c00 R15: 8800c4acc8f0 FS: 7f3dbedd6740() GS:88021e24() knlGS:0 CS: 0010 DS: ES: CR0: 80050033 CR2: fff8 CR3: ce1da000 CR4: 001407e0 Stack: 8800c4acc840 0008 880210471e61 8800c4bc6c00 8800c4afdc00 8800c4827ee8 811c00aa 8800c2068000 81ebb680 8800c2068620 Call Trace: [] __fput+0x24a/0x260 [] fput+0xe/0x10 [] task_work_run+0xa7/0xe0 [] do_notify_resume+0x97/0xb0 [] int_signal+0x12/0x17 Code: 00 41 56 41 55 41 54 53 e8 68 37 52 00 49 8b 07 48 8b 08 49 39 c7 4 RIP [] eventpoll_release_file+0x46/0xa0 RSP CR2: fff8 ---[ end trace f2ee3b43ddaf4bd4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503655/+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 1503655] Re: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107
On 2015-10-08 07:08, JBF wrote: > Gunnar said: A consequence of this buggy kernel upload is that many > 'non-expert users' now have seemingly useless systems, and are unable > to resolve the problem themselves. > > Please note that non expert users should not activate proposed > repository. The latter is indeed true. But (1) all users don't know that, and (2) people do not always do as they are recommended. So yes, it's true in a sense that those affected have themselves to blame. But IMO that's not a reason to belittle the significance of the incident. Quite a few users out there are stuck because they used Update Manager to keep their systems up to date. -- 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/1503655 Title: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107 Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux-lts-utopic source package in Vivid: Invalid Status in linux source package in Wily: Confirmed Status in linux-lts-utopic source package in Wily: Invalid Bug description: With the latest kernel in trusty-proposed I seem to get panics on my X230 laptop: BUG: unable to handle kernel paging request at fff8 IP: [] eventpoll_release_file+0x46/0xa0 PGD 1c11067 PUD 1c13067 PMD 0 Oops: [#1] SMP Modules linked in: snd_hrtimer ip6table_filter ip6_tables ebtable_nat ebt CPU: 1 PID: 1939 Comm: pulseaudio Not tainted 3.13.0-66-generic #107-Ubun Hardware name: LENOVO 2324CTO/2324CTO, BIOS G2ET94WW (2.54 ) 04/30/2013 task: 8800c2068000 ti: 8800c4826000 task.ti: 8800c4826000 RIP: 0010:[] [] eventpoll_release_fi RSP: 0018:8800c4827e78 EFLAGS: 00010286 RAX: RBX: ffb7 RCX: 000f RDX: 0100 RSI: RDI: 81c72e80 RBP: 8800c4827ea0 R08: R09: 0004 R10: 880210471e61 R11: 0206 R12: ffa8 R13: 880210471e61 R14: 8800c4bc6c00 R15: 8800c4acc8f0 FS: 7f3dbedd6740() GS:88021e24() knlGS:0 CS: 0010 DS: ES: CR0: 80050033 CR2: fff8 CR3: ce1da000 CR4: 001407e0 Stack: 8800c4acc840 0008 880210471e61 8800c4bc6c00 8800c4afdc00 8800c4827ee8 811c00aa 8800c2068000 81ebb680 8800c2068620 Call Trace: [] __fput+0x24a/0x260 [] fput+0xe/0x10 [] task_work_run+0xa7/0xe0 [] do_notify_resume+0x97/0xb0 [] int_signal+0x12/0x17 Code: 00 41 56 41 55 41 54 53 e8 68 37 52 00 49 8b 07 48 8b 08 49 39 c7 4 RIP [] eventpoll_release_file+0x46/0xa0 RSP CR2: fff8 ---[ end trace f2ee3b43ddaf4bd4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503655/+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 1503655] Re: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107
These are two related Ask Ubuntu questions: http://askubuntu.com/q/682589 http://askubuntu.com/q/682682 -- 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/1503655 Title: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107 Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux-lts-utopic source package in Vivid: Invalid Status in linux source package in Wily: Confirmed Status in linux-lts-utopic source package in Wily: Invalid Bug description: With the latest kernel in trusty-proposed I seem to get panics on my X230 laptop: BUG: unable to handle kernel paging request at fff8 IP: [] eventpoll_release_file+0x46/0xa0 PGD 1c11067 PUD 1c13067 PMD 0 Oops: [#1] SMP Modules linked in: snd_hrtimer ip6table_filter ip6_tables ebtable_nat ebt CPU: 1 PID: 1939 Comm: pulseaudio Not tainted 3.13.0-66-generic #107-Ubun Hardware name: LENOVO 2324CTO/2324CTO, BIOS G2ET94WW (2.54 ) 04/30/2013 task: 8800c2068000 ti: 8800c4826000 task.ti: 8800c4826000 RIP: 0010:[] [] eventpoll_release_fi RSP: 0018:8800c4827e78 EFLAGS: 00010286 RAX: RBX: ffb7 RCX: 000f RDX: 0100 RSI: RDI: 81c72e80 RBP: 8800c4827ea0 R08: R09: 0004 R10: 880210471e61 R11: 0206 R12: ffa8 R13: 880210471e61 R14: 8800c4bc6c00 R15: 8800c4acc8f0 FS: 7f3dbedd6740() GS:88021e24() knlGS:0 CS: 0010 DS: ES: CR0: 80050033 CR2: fff8 CR3: ce1da000 CR4: 001407e0 Stack: 8800c4acc840 0008 880210471e61 8800c4bc6c00 8800c4afdc00 8800c4827ee8 811c00aa 8800c2068000 81ebb680 8800c2068620 Call Trace: [] __fput+0x24a/0x260 [] fput+0xe/0x10 [] task_work_run+0xa7/0xe0 [] do_notify_resume+0x97/0xb0 [] int_signal+0x12/0x17 Code: 00 41 56 41 55 41 54 53 e8 68 37 52 00 49 8b 07 48 8b 08 49 39 c7 4 RIP [] eventpoll_release_file+0x46/0xa0 RSP CR2: fff8 ---[ end trace f2ee3b43ddaf4bd4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503655/+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 1503655] Re: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107
@Thomas: I think it's handled for wily as well. See this IRC conversation: http://irclogs.ubuntu.com/2015/10/07/%23ubuntu-kernel.html#t15:36 -- 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/1503655 Title: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107 Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux-lts-utopic source package in Vivid: Invalid Status in linux source package in Wily: Confirmed Status in linux-lts-utopic source package in Wily: Invalid Bug description: With the latest kernel in trusty-proposed I seem to get panics on my X230 laptop: BUG: unable to handle kernel paging request at fff8 IP: [] eventpoll_release_file+0x46/0xa0 PGD 1c11067 PUD 1c13067 PMD 0 Oops: [#1] SMP Modules linked in: snd_hrtimer ip6table_filter ip6_tables ebtable_nat ebt CPU: 1 PID: 1939 Comm: pulseaudio Not tainted 3.13.0-66-generic #107-Ubun Hardware name: LENOVO 2324CTO/2324CTO, BIOS G2ET94WW (2.54 ) 04/30/2013 task: 8800c2068000 ti: 8800c4826000 task.ti: 8800c4826000 RIP: 0010:[] [] eventpoll_release_fi RSP: 0018:8800c4827e78 EFLAGS: 00010286 RAX: RBX: ffb7 RCX: 000f RDX: 0100 RSI: RDI: 81c72e80 RBP: 8800c4827ea0 R08: R09: 0004 R10: 880210471e61 R11: 0206 R12: ffa8 R13: 880210471e61 R14: 8800c4bc6c00 R15: 8800c4acc8f0 FS: 7f3dbedd6740() GS:88021e24() knlGS:0 CS: 0010 DS: ES: CR0: 80050033 CR2: fff8 CR3: ce1da000 CR4: 001407e0 Stack: 8800c4acc840 0008 880210471e61 8800c4bc6c00 8800c4afdc00 8800c4827ee8 811c00aa 8800c2068000 81ebb680 8800c2068620 Call Trace: [] __fput+0x24a/0x260 [] fput+0xe/0x10 [] task_work_run+0xa7/0xe0 [] do_notify_resume+0x97/0xb0 [] int_signal+0x12/0x17 Code: 00 41 56 41 55 41 54 53 e8 68 37 52 00 49 8b 07 48 8b 08 49 39 c7 4 RIP [] eventpoll_release_file+0x46/0xa0 RSP CR2: fff8 ---[ end trace f2ee3b43ddaf4bd4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503655/+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 1503655] Re: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107
A thought: A consequence of this buggy kernel upload is that many 'non-expert users' now have seemingly useless systems, and are unable to resolve the problem themselves. Take bug #1503787 as an example of what I'm talking about. Is there any suitable tutorial for this type of issue to which they can be pointed? If not, I think it would be an important goodwill gesture to write something up. -- 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/1503655 Title: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107 Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux-lts-utopic source package in Trusty: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux-lts-utopic source package in Vivid: Invalid Status in linux source package in Wily: Confirmed Status in linux-lts-utopic source package in Wily: Invalid Bug description: With the latest kernel in trusty-proposed I seem to get panics on my X230 laptop: BUG: unable to handle kernel paging request at fff8 IP: [] eventpoll_release_file+0x46/0xa0 PGD 1c11067 PUD 1c13067 PMD 0 Oops: [#1] SMP Modules linked in: snd_hrtimer ip6table_filter ip6_tables ebtable_nat ebt CPU: 1 PID: 1939 Comm: pulseaudio Not tainted 3.13.0-66-generic #107-Ubun Hardware name: LENOVO 2324CTO/2324CTO, BIOS G2ET94WW (2.54 ) 04/30/2013 task: 8800c2068000 ti: 8800c4826000 task.ti: 8800c4826000 RIP: 0010:[] [] eventpoll_release_fi RSP: 0018:8800c4827e78 EFLAGS: 00010286 RAX: RBX: ffb7 RCX: 000f RDX: 0100 RSI: RDI: 81c72e80 RBP: 8800c4827ea0 R08: R09: 0004 R10: 880210471e61 R11: 0206 R12: ffa8 R13: 880210471e61 R14: 8800c4bc6c00 R15: 8800c4acc8f0 FS: 7f3dbedd6740() GS:88021e24() knlGS:0 CS: 0010 DS: ES: CR0: 80050033 CR2: fff8 CR3: ce1da000 CR4: 001407e0 Stack: 8800c4acc840 0008 880210471e61 8800c4bc6c00 8800c4afdc00 8800c4827ee8 811c00aa 8800c2068000 81ebb680 8800c2068620 Call Trace: [] __fput+0x24a/0x260 [] fput+0xe/0x10 [] task_work_run+0xa7/0xe0 [] do_notify_resume+0x97/0xb0 [] int_signal+0x12/0x17 Code: 00 41 56 41 55 41 54 53 e8 68 37 52 00 49 8b 07 48 8b 08 49 39 c7 4 RIP [] eventpoll_release_file+0x46/0xa0 RSP CR2: fff8 ---[ end trace f2ee3b43ddaf4bd4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503655/+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 1503647] Re: System hangs with kernel 3.19.0-31
Hi Luis! I can confirm that version 3.19.0-31.36 fixes the issue on my vivid 64bits install. (The observations mentioned in comment #4 was from a vivid 32bits install.) I don't see any linux package in the trusty or vivid upload queues. Or does it work differently with the kernel? -- 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/1503647 Title: System hangs with kernel 3.19.0-31 Status in linux package in Ubuntu: Confirmed Bug description: After installing kernel 3.19.0-31, the system freezes at login. I got following error during install, I don't know if that is the reason for the freeze. sudo dpkg-reconfigure linux-headers-3.19.0-31 linux- headers-3.19.0-31-generic Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.19.0-31-generic /boot/vmlinuz-3.19.0-31-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/i915-3.15-3.13-dkms.0.crash' Error! Bad return status for module build on kernel: 3.19.0-31-generic (x86_64) Consult /var/lib/dkms/i915-3.15-3.13/0.01/build/make.log for more information. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-headers-3.19.0-31-generic 3.19.0-31.35 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simon 2192 F pulseaudio /dev/snd/controlC1: simon 2192 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 7 12:18:47 2015 HibernationDevice: RESUME=UUID=c929a208-30d1-4e36-9943-d68352b90a26 InstallationDate: Installed on 2014-07-28 (435 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Notebook W65_67SZ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=da3171d0-cb60-47b3-8584-e10466a6c8a9 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_67SZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd02/26/2014:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W65_67SZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503647/+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 1503647] Re: System hangs with kernel 3.19.0-31
My system (15.04 Unity) doesn't freeze completely, but it certainly behaves badly. For example: Takes ages to log in, and the sound can't be enabled. This kernel version should apparently be replaced ASAP. ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/1503647 Title: System hangs with kernel 3.19.0-31 Status in linux package in Ubuntu: Confirmed Bug description: After installing kernel 3.19.0-31, the system freezes at login. I got following error during install, I don't know if that is the reason for the freeze. sudo dpkg-reconfigure linux-headers-3.19.0-31 linux- headers-3.19.0-31-generic Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.19.0-31-generic /boot/vmlinuz-3.19.0-31-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/i915-3.15-3.13-dkms.0.crash' Error! Bad return status for module build on kernel: 3.19.0-31-generic (x86_64) Consult /var/lib/dkms/i915-3.15-3.13/0.01/build/make.log for more information. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-headers-3.19.0-31-generic 3.19.0-31.35 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simon 2192 F pulseaudio /dev/snd/controlC1: simon 2192 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 7 12:18:47 2015 HibernationDevice: RESUME=UUID=c929a208-30d1-4e36-9943-d68352b90a26 InstallationDate: Installed on 2014-07-28 (435 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Notebook W65_67SZ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=da3171d0-cb60-47b3-8584-e10466a6c8a9 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.05 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_67SZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd02/26/2014:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W65_67SZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503647/+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 1400155] Re: inconsistent backlight brightness behaviour
@David, Thanks for providing the additional info which Christopher asked for, and for filing bug #1400345 against a more correct - probably the right ;) - package. Just to prevent any misunderstandings: Your reported observations and suggestions are much appreciated. However, so far you haven't answered my question why both this bug and bug #1400147 were initially filed against the ubuntu-docs package (which is not correct). I asked you about that only because I would honestly like to know what lead you in that direction. You are certainly not alone. Quite often I see bugs filed against ubuntu-docs which have nothing to do with documentation. That makes me suspect that there is an erroneous link or something somewhere which should be corrected. So, if you are able to recall how you did, it would be much appreciated if you could let me know. Cheers, -- 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/1400155 Title: inconsistent backlight brightness behaviour Status in linux package in Ubuntu: Incomplete Bug description: This bug refers to a Dell XPS13-9333 running Ubuntu 14.10. I discovered a workaround to prevent the screen starting with full brightness. The reference to the workaround advice is: http://ubuntuhandbook.org/index.php/2014/04/save-screen-brightness-settings-in-ubuntu-14-04/ There is a folder sys/class/backlight/intel_backlight/ containing a number of files such as brightness, actual_brightness and max_brightness. When using Fn-F4 & F5 to control the screen backlight, the two files: brightness and actual_brightness respond by changing there contents to a number which is a proportion of the contents of max_brightness (937). The workaround was to include the line: echo 569 > /sys/class/backlight/intel_backlight/brightness at the end of the file: /etc/rc.local using gedit (where 569 is a value noted for a typically comfortable level of backlight). This works when doing a restart but, when logging back in after logging out, the backlight comes on at maximum brightness. This particular laptop has a front-facing webcam fitted. Its function can be confirmed by running the Cheese webcam Booth. It would be a vast improvement if the ambient brightness could be sensed by the webcam and used to adjust the backlight brightness. Auto brightness could be selected or not by a tick box in the Brightness & Lock section of System Settings. Similarly, a tick box might also be provided to enable saving of the backlight brightness when shutting down or logging off --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 2755 F pulseaudio /dev/snd/controlC1: david 2755 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=2ce4d026-79c8-46d8-aa78-9a01276f4ada InstallationDate: Installed on 2014-11-08 (29 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=10c98fc6-0c96-44d3-9e0e-ba93d84dffe6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: utopic Uname: Linux 3.16.0-25-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-11-21 (16 days ago) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0D13CR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/11/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 2755 F pulseaudio /dev/snd/controlC1: david 2755 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroReleas