[Bug 1813400] Re: systemctl doesn't respect --dry-run
Still happens on 237-3ubuntu10.31 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813400 Title: systemctl doesn't respect --dry-run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631161] Re: Preferred output device is not remembered between logins
It is not HDMI specific. I have a similar problem: every start up, output is selected on (usb) headphones, but actual audio comes out my motherboard line out. Volume control adjusts headphones, so apparently has no effect. I have to go change it to line out, then the volume control works. Should I create yet another duplicate? Or can someone familiar suggest the right bug to follow? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631161 Title: Preferred output device is not remembered between logins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
I have an APC UPS too. Great find. Who would have guessed an IRQ handling problem message from the kernel was due to a serial or USB device. Wow. On Thu, Apr 18, 2019 at 7:16 AM Kai-Heng Feng wrote: > Thanks for the info. Have anyone filed a bug against upstream apcupsd? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1781016 > > Title: > Slow flood of do_IRQ: No irq for vector > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Every few seconds I get something like this in my dmesg: > > [44984.933221] do_IRQ: 1.34 No irq handler for vector > [44986.933976] do_IRQ: 1.34 No irq handler for vector > [44991.935614] do_IRQ: 1.34 No irq handler for vector > [45004.938590] do_IRQ: 1.34 No irq handler for vector > [45005.939002] do_IRQ: 4.34 No irq handler for vector > [45034.949161] do_IRQ: 4.34 No irq handler for vector > [45051.954569] do_IRQ: 4.34 No irq handler for vector > [45058.956019] do_IRQ: 4.34 No irq handler for vector > [45062.957727] do_IRQ: 4.34 No irq handler for vector > [45063.958204] do_IRQ: 4.34 No irq handler for vector > [45073.961103] do_IRQ: 4.34 No irq handler for vector > > The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, > 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log > is just messages like above with varying #.## numbers. > > I researched it and tried disabling irqbalance. It had no effect, the > messages continued. > > The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. > I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 > NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never > occurred before installing 18.03 on the same hardware. No overclocking > whatsoever has ever been done to this machine. > > Also, I had to disable selective suspend on USB in this version to > prevent major USB issues, which was not required in 17.10, that might > be related. > > My system seems stable, but spurious IRQs can't be good. I'd like to > resolve this if possible. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-26-generic 4.15.0-26.28 > ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 > Uname: Linux 4.15.0-26-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: gdm2145 F pulseaudio > doug 3736 F pulseaudio >/dev/snd/controlC1: gdm2145 F pulseaudio > doug 3736 F pulseaudio > Date: Tue Jul 10 12:49:00 2018 > HibernationDevice: > > InstallationDate: Installed on 2017-06-26 (379 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > MachineType: System manufacturer System Product Name > ProcEnviron: >LANGUAGE=en_CA:en >TERM=xterm-256color >PATH=(custom, no user) >LANG=en_CA.UTF-8 >SHELL=/bin/bash > ProcFB: > > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic > root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal > video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 > PulseList: >Error: command ['pacmd', 'list'] failed with exit code 1: Home > directory not accessible: Permission denied >No PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.15.0-26-generic N/A >linux-backports-modules-4.15.0-26-generic N/A >linux-firmware 1.173.1 > RfKill: > > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/19/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 4011 > dmi.board.asset.tag: Default string > dmi.board.name: PRIME B350-PLUS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood
Re: [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
Mine is a desktop, and no suspend occurs, ever. Are you (Kai-Heng Feng) asking me to suspend it and wake it up and see if it goes away? On Mon, Sep 24, 2018 at 10:45 AM Kai-Heng Feng wrote: > Do you see this after S3? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1781016 > > Title: > Slow flood of do_IRQ: No irq for vector > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Every few seconds I get something like this in my dmesg: > > [44984.933221] do_IRQ: 1.34 No irq handler for vector > [44986.933976] do_IRQ: 1.34 No irq handler for vector > [44991.935614] do_IRQ: 1.34 No irq handler for vector > [45004.938590] do_IRQ: 1.34 No irq handler for vector > [45005.939002] do_IRQ: 4.34 No irq handler for vector > [45034.949161] do_IRQ: 4.34 No irq handler for vector > [45051.954569] do_IRQ: 4.34 No irq handler for vector > [45058.956019] do_IRQ: 4.34 No irq handler for vector > [45062.957727] do_IRQ: 4.34 No irq handler for vector > [45063.958204] do_IRQ: 4.34 No irq handler for vector > [45073.961103] do_IRQ: 4.34 No irq handler for vector > > The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, > 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log > is just messages like above with varying #.## numbers. > > I researched it and tried disabling irqbalance. It had no effect, the > messages continued. > > The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. > I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 > NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never > occurred before installing 18.03 on the same hardware. No overclocking > whatsoever has ever been done to this machine. > > Also, I had to disable selective suspend on USB in this version to > prevent major USB issues, which was not required in 17.10, that might > be related. > > My system seems stable, but spurious IRQs can't be good. I'd like to > resolve this if possible. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-26-generic 4.15.0-26.28 > ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 > Uname: Linux 4.15.0-26-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: gdm2145 F pulseaudio > doug 3736 F pulseaudio >/dev/snd/controlC1: gdm2145 F pulseaudio > doug 3736 F pulseaudio > Date: Tue Jul 10 12:49:00 2018 > HibernationDevice: > > InstallationDate: Installed on 2017-06-26 (379 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > MachineType: System manufacturer System Product Name > ProcEnviron: >LANGUAGE=en_CA:en >TERM=xterm-256color >PATH=(custom, no user) >LANG=en_CA.UTF-8 >SHELL=/bin/bash > ProcFB: > > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic > root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal > video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 > PulseList: >Error: command ['pacmd', 'list'] failed with exit code 1: Home > directory not accessible: Permission denied >No PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.15.0-26-generic N/A >linux-backports-modules-4.15.0-26-generic N/A >linux-firmware 1.173.1 > RfKill: > > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/19/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 4011 > dmi.board.asset.tag: Default string > dmi.board.name: PRIME B350-PLUS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood of do_IRQ: No irq for vector To manage notifications
[Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
Still happening: doug@doug-dt:~$ uname -a Linux doug-dt 4.18.0-041800rc5-generic #201807152130 SMP Sun Jul 15 21:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux doug@doug-dt:~$ dmesg | tail [ 169.701341] usb 1-4: Warning! Unlikely big volume range (=4096), cval->res is probably wrong. [ 169.701344] usb 1-4: [11] FU [Headset Playback Volume] ch = 1, val = 0/4096/1 [ 169.755604] usbcore: registered new interface driver snd-usb-audio [ 2603.508893] do_IRQ: 15.38 No irq handler for vector [ 2611.510716] do_IRQ: 15.38 No irq handler for vector [ 2624.514513] do_IRQ: 15.38 No irq handler for vector [ 2627.515471] do_IRQ: 15.38 No irq handler for vector [ 2642.520161] do_IRQ: 15.38 No irq handler for vector [ 2644.520907] do_IRQ: 15.38 No irq handler for vector [ 2647.522088] do_IRQ: 15.38 No irq handler for vector doug@doug-dt:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood of do_IRQ: No irq for vector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
Exactly. It never happened in ubuntu 17.10. Started happening after installing ubuntu 18.04. Can't say I know exactly what kernel version 17.10 was up to, sorry. It was the standard one, whatever dist-upgrade would have gave me. I'll try the kernel version you proposed and update this bug after I try it. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood of do_IRQ: No irq for vector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781016] [NEW] Slow flood of do_IRQ: No irq for vector
Public bug reported: Every few seconds I get something like this in my dmesg: [44984.933221] do_IRQ: 1.34 No irq handler for vector [44986.933976] do_IRQ: 1.34 No irq handler for vector [44991.935614] do_IRQ: 1.34 No irq handler for vector [45004.938590] do_IRQ: 1.34 No irq handler for vector [45005.939002] do_IRQ: 4.34 No irq handler for vector [45034.949161] do_IRQ: 4.34 No irq handler for vector [45051.954569] do_IRQ: 4.34 No irq handler for vector [45058.956019] do_IRQ: 4.34 No irq handler for vector [45062.957727] do_IRQ: 4.34 No irq handler for vector [45063.958204] do_IRQ: 4.34 No irq handler for vector [45073.961103] do_IRQ: 4.34 No irq handler for vector The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log is just messages like above with varying #.## numbers. I researched it and tried disabling irqbalance. It had no effect, the messages continued. The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never occurred before installing 18.03 on the same hardware. No overclocking whatsoever has ever been done to this machine. Also, I had to disable selective suspend on USB in this version to prevent major USB issues, which was not required in 17.10, that might be related. My system seems stable, but spurious IRQs can't be good. I'd like to resolve this if possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-26-generic 4.15.0-26.28 ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 Uname: Linux 4.15.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2145 F pulseaudio doug 3736 F pulseaudio /dev/snd/controlC1: gdm2145 F pulseaudio doug 3736 F pulseaudio Date: Tue Jul 10 12:49:00 2018 HibernationDevice: InstallationDate: Installed on 2017-06-26 (379 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-26-generic N/A linux-backports-modules-4.15.0-26-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781016 Title: Slow flood of do_IRQ: No irq for vector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564997] Re: index++ crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1551886 *** https://bugs.launchpad.net/bugs/1551886 The automated link to bug 1551886 does not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564997 Title: index++ crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swish++/+bug/1564997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658252] [NEW] nvidia-304 304.134-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build
Public bug reported: nvidia-367 broke my system. Now I can't get any nvidia-xxx version to work. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-304 304.134-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 4.4.0-62-generic Date: Fri Jan 20 19:28:03 2017 DistUpgraded: 2016-11-19 22:58:31,519 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-53-generic, x86_64: installed bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-53-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-57-generic, x86_64: installed nvidia-304, 304.134: added GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 4th Gen Core Processor Integrated Graphics Controller [1025:091d] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 860M] [1025:091d] InstallationDate: Installed on 2015-05-21 (610 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Acer Aspire VN7-791 PackageVersion: 304.134-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=e983f70e-9e5b-4d5a-90b4-0f4025b8f2b6 ro ath9k.nohwcrypt=1 ath9k.btcoex_enable=1 modprobe.blacklist=ath3k acpi_osi=Linux RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: nvidia-graphics-drivers-304 Title: nvidia-304 304.134-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build UpgradeStatus: Upgraded to xenial on 2016-11-20 (61 days ago) dmi.bios.date: 09/05/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-791 dmi.board.vendor: Acer dmi.board.version: V1.07 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2014:svnAcer:pnAspireVN7-791:pvrV1.07:rvnAcer:rnAspireVN7-791:rvrV1.07:cvnAcer:ct10:cvrV1.07: dmi.product.name: Aspire VN7-791 dmi.product.version: V1.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 20 19:28:53 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1129 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 possible-manual-nvidia-install third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658252 Title: nvidia-304 304.134-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1658252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613032] Re: nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build
367 broke my OS, and now the older versions don't work either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613032 Title: nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1613032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639471] Re: nvidia-367 broken by upgrade to .57
Why in the world is every earlier version dependent upon the 367 version? So I can't go back to a working driver? Asinine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639471 Title: nvidia-367 broken by upgrade to .57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1639471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639471] Re: nvidia-367 broken by upgrade to .57
`sudo apt-get install --reinstall bumblebee bumblebee-nvidia` didn't work for me. When I try to my prime on NVIDIA performance mode it goes back to intel power save mode on logout/login. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639471 Title: nvidia-367 broken by upgrade to .57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1639471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228201] Re: g++ doesn't compile simple code, using thread header
Static link with `-static` also reproduces the issue, even with `-Wl ,--no-as-needed`. Removing `-static` fixed the issue for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228201 Title: g++ doesn't compile simple code, using thread header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1228201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1060167] Re: indicator doesn't always work properly after suspend
Michael, you can work around that for now by running killall nm-applet with a script in your sleep.d directory: http://askubuntu.com/questions/92218/how-to-execute-a-command-after- resume-from-suspend#92235 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060167 Title: indicator doesn't always work properly after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1060167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581920] Re: Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
I tried `apport-collect 1581920` in a terminal (without backticks) and it says "No additional information collected" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581920 Title: Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1581920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581920] Re: Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
You may notice that the assertion failures are happening so fast that a whole screen full of syslog messages are all in the same second. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581920 Title: Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1581920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581920] [NEW] Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed
Public bug reported: Every time I look at my syslog it is a sea of assertions interspersed with actual relevant logs. I have been letting this go for a long time. I think it is time I tried to stop the log spam. I love the applet, it is great! My syslog consists of endless spam like this: May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:01:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 14 16:03:52 doug-lt org.gnome.panel.applet.IndicatorAppletCompleteFactory[2376]: (indicator-applet-complete:2791): Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed ** Affects: indicator-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581920 Title: Endless syslog assert spam: Gtk-CRITICAL **: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1581920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1402857] Re: crashed to text only screen, kernel panic
I have almost the same issues, except I run Metacity, so it's not related to compiz, and in my case, the panic can happen at resume but it frequently happens when I (try to) restart or shutdown. It kernel panics with either black screen or text mode, with flashing numlock. Stack trace scrolls off the top, but the symbols clearly indicate it is executing in the wl driver. My NIC is similar: 02:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1402857 Title: crashed to text only screen, kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1402857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449893] [NEW] i915 dmesg spam and poor battery life
Public bug reported: Since upgrading my i915 lockups are fixed (yay!) but now I have poor battery life and I get a lot of spam in dmesg: WARN_ON(!power_well-count) at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_runtime_pm.c:680 intel_display_power_put+0x103/0x170 [i915]() ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doug 1868 F pulseaudio /dev/snd/controlC0: doug 1868 F pulseaudio Date: Wed Apr 29 03:23:53 2015 HibernationDevice: RESUME=UUID=7048b86e-1bcb-41e3-900d-d8453f419503 InstallationDate: Installed on 2014-12-31 (118 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20238 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=a5b6eaae-04b1-418f-9b9a-5b3f1450bb8b ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-25 (4 days ago) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN50WW(V3.09) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G510 dmi.modalias: dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG510: dmi.product.name: 20238 dmi.product.version: Lenovo G510 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449893 Title: i915 dmesg spam and poor battery life To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1449893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449893] Re: i915 dmesg spam and poor battery life
Oh, my stress test is http://jsfiddle.net/GzSWJ/123/show/ it reliably caused i915 gpu hangs for me before upgrading to 15.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449893 Title: i915 dmesg spam and poor battery life To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1449893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449893] Re: i915 dmesg spam and poor battery life
I installed the packages (needed headers too), rebooted into and selected that version in grub, and so far it is passing my stress test that provokes gpu hangs, and no hang yet, which is great! Also, I haven't seen the warning yet (the ones I originally reported), but that happens durng normal operation and may never happen during stress. I'll use it normally for a bit and report what happens. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449893 Title: i915 dmesg spam and poor battery life To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1449893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449893] Re: i915 dmesg spam and poor battery life
Still got the WARN_ON: [ 4616.728430] [ cut here ] [ 4616.728453] WARNING: CPU: 0 PID: 2575 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_runtime_pm.c:676 intel_display_power_put+0x163/0x170 [i915]() [ 4616.728455] WARN_ON(!power_domains-domain_use_count[domain]) [ 4616.728456] Modules linked in: [ 4616.728457] thinkpad_acpi nvram msr acpi_call(OE) binfmt_misc nls_iso8859_1 rtsx_usb_ms memstick wl(POE) uvcvideo videobuf2_vmalloc videobuf2_memops snd_hda_codec_conexant snd_hda_codec_generic snd_hda_codec_hdmi videobuf2_core intel_rapl iosf_mbi v4l2_common videodev snd_hda_intel x86_pkg_temp_thermal intel_powerclamp media coretemp snd_hda_controller snd_hda_codec kvm_intel snd_hwdep kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_pcm i915 cfg80211 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer drm_kms_helper snd cryptd joydev serio_raw soundcore drm lpc_ich ie31200_edac mei_me mei i2c_algo_bit edac_core ideapad_laptop sparse_keymap shpchp mac_hid video parport_pc ppdev lp parport autofs4 rtsx_usb_sdmmc rtsx_usb psmouse ahci libahci alx mdio [ 4616.728492] CPU: 0 PID: 2575 Comm: kworker/0:1 Tainted: PW OE 3.19.0-11-generic #11-Ubuntu [ 4616.728493] Hardware name: LENOVO 20238/INVALID, BIOS 79CN50WW(V3.09) 10/20/2014 [ 4616.728511] Workqueue: events edp_panel_vdd_work [i915] [ 4616.728512] c05b70e0 880308cfbca8 817c15b5 0007 [ 4616.728515] 880308cfbcf8 880308cfbce8 8107595a 88035f214278 [ 4616.728517] 88034fdc002c 88034fdc 88034fdc8980 88034fdc [ 4616.728519] Call Trace: [ 4616.728525] [817c15b5] dump_stack+0x45/0x57 [ 4616.728528] [8107595a] warn_slowpath_common+0x8a/0xc0 [ 4616.728531] [810759d6] warn_slowpath_fmt+0x46/0x50 [ 4616.728547] [c0549e8f] ? gen6_read32+0x9f/0x140 [i915] [ 4616.728557] [c050cf83] intel_display_power_put+0x163/0x170 [i915] [ 4616.728573] [c0580c2b] edp_panel_vdd_off_sync+0xcb/0x1c0 [i915] [ 4616.728577] [817c6206] ? mutex_lock+0x16/0x40 [ 4616.728593] [c0581b01] edp_panel_vdd_work+0x31/0x40 [i915] [ 4616.728596] [8108eb78] process_one_work+0x158/0x430 [ 4616.728598] [8108f6bb] worker_thread+0x5b/0x530 [ 4616.728600] [8108f660] ? rescuer_thread+0x3a0/0x3a0 [ 4616.728603] [81094759] kthread+0xc9/0xe0 [ 4616.728606] [81094690] ? kthread_create_on_node+0x1c0/0x1c0 [ 4616.728609] [817c8618] ret_from_fork+0x58/0x90 [ 4616.728611] [81094690] ? kthread_create_on_node+0x1c0/0x1c0 [ 4616.728613] ---[ end trace 82df9c2e032f7bcf ]--- and doug@doug-lt:~$ modinfo i915 filename: /lib/modules/3.19.0-11-generic/kernel/drivers/gpu/drm/i915/i915.ko license:GPL and additional rights description:Intel Graphics author: Intel Corporation author: Tungsten Graphics, Inc. srcversion: F2EAB55B6DC31E8C80AE987 alias: pci:v8086d191Dsv*sd*bc03sc*i* [snip...] alias: pci:v8086d3577sv*sd*bc03sc*i* depends:drm_kms_helper,drm,video,i2c-algo-bit intree: Y vermagic: 3.19.0-11-generic SMP mod_unload modversions signer: Magrathea: Glacier signing key sig_key:E4:10:43:D5:D2:15:9D:3C:83:74:A3:04:5E:64:6E:0A:7A:BF:D8:16 sig_hashalgo: sha512 parm: modeset:Use kernel modesetting [KMS] (0=DRM_I915_KMS from .config, 1=on, -1=force vga console preference [default]) (int) parm: panel_ignore_lid:Override lid status (0=autodetect, 1=autodetect disabled [default], -1=force lid closed, -2=force lid open) (int) parm: powersave:Enable powersavings, fbc, downclocking, etc. (default: true) (int) parm: semaphores:Use semaphores for inter-ring sync (default: -1 (use per-chip defaults)) (int) parm: enable_rc6:Enable power-saving render C-state 6. Different stages can be selected via bitmask values (0 = disable; 1 = enable rc6; 2 = enable deep rc6; 4 = enable deepest rc6). For example, 3 would enable rc6 and deep rc6, and 7 would enable everything. default: -1 (use per-chip default) (int) parm: enable_fbc:Enable frame buffer compression for power savings (default: -1 (use per-chip default)) (int) parm: lvds_downclock:Use panel (LVDS/eDP) downclocking for power savings (default: false) (int) parm: lvds_channel_mode:Specify LVDS channel mode (0=probe BIOS [default], 1=single-channel, 2=dual-channel) (int) parm: lvds_use_ssc:Use Spread Spectrum Clock with panels [LVDS/eDP] (default: auto from VBT) (int) parm: vbt_sdvo_panel_type:Override/Ignore selection of SDVO panel mode in the VBT (-2=ignore, -1=auto [default], index in VBT BIOS table) (int) parm: reset:Attempt GPU resets (default: true) (bool) parm: enable_hangcheck:Periodically check GPU activity for detecting hangs. WARNING:
