[Bug 1621753] Re: Google Cast no longer finds Chromecast device

2017-03-14 Thread firespeaker
I appear to be having a similar issue in the following versions: Chromium 56.0.2924.76 built on Debian 9.0, running on Debian 9.0 Chromium 57.0.2987.98 built on Debian 9.0, running on Debian 9.0 But it seems to be okay in this version: Chromium 56.0.2924.76 Built on 8.7, running on Debian 8.7

[Bug 388724] Re: ACPI lid event occurs constantly until system crashes

2010-09-05 Thread firespeaker
This fix helped me: https://bugzilla.kernel.org/show_bug.cgi?id=13802 ** Bug watch added: Linux Kernel Bug Tracker #13802 http://bugzilla.kernel.org/show_bug.cgi?id=13802 -- ACPI lid event occurs constantly until system crashes https://bugs.launchpad.net/bugs/388724 You received this bug

[Bug 373245] Re: karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)

2010-01-24 Thread firespeaker
I disabled the CONFIG_SCHED_SMT option in my kernel's .config and recompiled, installed, and rebooted. It's possible this is the wrong option, so let me know if I should be looking for something else. -- karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)

[Bug 373245] Re: karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)

2010-01-23 Thread firespeaker
Both removing the wifi driver and disabling compositing seem not to change anything significantly. Top causes for wakeups: 38.1% (140.4) kernel core : hrtimer_start_range_ns (tick_sched_timer) 17.6% ( 64.8) interrupt : PS/2 keyboard/mouse/touchpad 11.0% ( 40.4) interrupt :

[Bug 373245] Re: karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)

2010-01-23 Thread firespeaker
luarvik1: yes, I disabled hyperthreading in the kernel only. How did you disable it in the BIOS? -- karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer) https://bugs.launchpad.net/bugs/373245 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 373245] Re: karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)

2009-10-17 Thread firespeaker
I disabled hyperthreading in my 2.6.31 kernel on my N270 and still get around 200 wakeups per second (usually anywhere from 100 to 300) from hrtimer_start_range_ns (tick_sched_timer). -- karmic: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)

[Bug 373245] Re: wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)

2009-07-28 Thread firespeaker
On 2.6.30.1, in powertop I get e.g. 30.0% (261.0) kernel core : hrtimer_start_range_ns (tick_sched_timer) -- wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer) https://bugs.launchpad.net/bugs/373245 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 47903] Re: File overwrite conflict with ancient version

2006-10-08 Thread firespeaker
I get the same problem dist-upgrading from breezy to dapper. ** Changed in: xffm4 (Ubuntu) Status: Rejected = Confirmed -- File overwrite conflict with ancient version https://launchpad.net/bugs/47903 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 47903] Re: File overwrite conflict with ancient version

2006-10-08 Thread firespeaker
The following work-around can be used to avoid the issue: $ apt-get -f remove libxfce4mcs-client3 libxfce4util4 libxfcegui4-4 libxfce4mcs-manager3 xfwm4 xfprint4 xfce4-utils xfce4-panel xfce4-mcs- plugins xfce4-mcs-manager xfce4 xfce4-cpugraph-plugin xfce4-mixer xfce4-toys