[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:

[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

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

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 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. [

[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

[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

[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

[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

[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

[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

[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.

[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++

[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

[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

[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:

[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

[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

[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]()

[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

[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

[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]