[Bug 877236] Re: QGtkStyle gets incorrect colors for tooltips on unity2d

2014-04-10 Thread Exterminans
Still an issue in 13.10 (and also in other distributions, including
Arch)

The bug is somewhere in the config loader of Qt, every other color
except for the tooltip background color is read from the Trolltech.conf
as expected. Tooltip background color is hardcoded to #dc and the
settings in th Trolltech.conf are not respected at all.

This affects Qt3 and Qt4 applications.

qtconfig will actually set a tooltip color, apply it to all running Qt
applications and write it correctly to Trolltech.conf, but will falsely
read the constant value back on the next startup.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877236

Title:
  QGtkStyle gets incorrect colors for tooltips on unity2d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/877236/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1045771] Re: Underruns and stuttering

2013-07-27 Thread Exterminans
It doesn't look like the problem is in pulseaudio though.
I have the very same problem (buffer underruns in alsa and the resulting 
stuttering / crackling), but the issue not only occurs when I use Pulseaudio.

It's a generic issue with all applications which access Alsa, although
varying the size of the buffers in pulseaudio can reduce the interval of
stutters.

For me it's not the Wifi driver which is causing the issue, but (i think) 
something in the graphics driver since I get the stuttering whenever large 
bitmaps get drawn on screen.
This seems to be highly dependent on the hardware and there appear to be 
multiple hardware configurations which can trigger the underruns in Alsa.
I can e.g. trigger it reliably by switching the video renderer in VLC from GLX 
to Xvideo and back and it will start stuttering as soon as the Xserver is under 
load. Switching between Pulseaudio and Alsa (direct, PA suspended) as audio 
backend makes no difference at all, well except that the interval of the cracks 
is directly related to the buffer size used by the corresponding applications.

What would be noteworthy, this issue is rather new for me.
There appears to be some regression in the Alsa driver which makes it less 
tolerant towards long running, non-interruptible service routines from other 
drivers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045771

Title:
  Underruns and stuttering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1045771/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 985820] Re: Xorg freeze or compiz freeze

2012-04-24 Thread Exterminans
Xorg does not freeze, all hotkeys still work, even applications stay
responding as in they still accept mouse and keyboard-inputs. (e.g.
applications can still be terminated with alt+F4, tested by terminating
a running skype call while the screen was frozen, rhytmbox was also
still controlable)

Only the composed image seems to be frozen.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985820

Title:
  Xorg freeze or compiz freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/985820/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 396268] Re: Banshee uses too much CPU

2011-06-29 Thread Exterminans
Same problem here, CPU frequently jumps up to 200% while banshee is
running. banshee itself only consumes only ~5% (still inacceptable for
just decoding a mp3 file!), but it causes pulseaudio to consume 100-150%
cpu sometimes, rendering the whole system (including nautilus and ALL
processes which connect to pulseaudio) unresponsable.

Same problem also occures with rhythmbox, so it looks more like a bug in
ubuntus pulseaudio integration.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/396268

Title:
  Banshee uses too much CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/banshee/+bug/396268/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 598857] Re: OpenGL artifacts for surfaces >> 1280x1024

2011-01-09 Thread Exterminans
No, this problem seems to be resolved since Ubuntu 10.10. At least i was
able tu run both glxgears and tremolous in full 1080p without artifacts.

** Changed in: fglrx-installer (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598857

Title:
  OpenGL artifacts for surfaces >> 1280x1024

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 575460] Re: memory leak

2010-07-03 Thread Exterminans
This  bug affects me too, with both 1.0.6 from the lucid repo and 1.1.0
from the c-korn-ppa. Their is no output on stdout or stderr, vlc just
suddenly takes up a full core and starts to allocate memory at an
incredible speed. Video will continue playing, at least until the swap
slows down the system so this leak does not seem to be allocated in the
main thread.

dmesg-output:
[113735.650674] vlc invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0
[113735.650683] vlc cpuset=/ mems_allowed=0
[113735.650690] Pid: 30854, comm: vlc Not tainted 2.6.32-23-generic #37-Ubuntu
[113735.650695] Call Trace:
[113735.650709]  [] ? cpuset_print_task_mems_allowed+0x9d/0xb0
[113735.650719]  [] oom_kill_process+0xd4/0x2f0
[113735.650726]  [] ? select_bad_process+0xd0/0x110
[113735.650733]  [] __out_of_memory+0x58/0xc0
[113735.650740]  [] out_of_memory+0x12e/0x1a0
[113735.650749]  [] ? _spin_lock+0xe/0x20
[113735.650757]  [] __alloc_pages_slowpath+0x511/0x580
[113735.650765]  [] __alloc_pages_nodemask+0x15e/0x1a0
[113735.650774]  [] alloc_pages_current+0x87/0xd0
[113735.650780]  [] __page_cache_alloc+0x67/0x70
[113735.650788]  [] __do_page_cache_readahead+0xc9/0x210
[113735.650795]  [] ra_submit+0x21/0x30
[113735.650802]  [] ondemand_readahead+0x115/0x240
[113735.650810]  [] ? __dequeue_entity+0x30/0x50
[113735.650817]  [] page_cache_sync_readahead+0x31/0x50
[113735.650824]  [] filemap_fault+0x42c/0x460
[113735.650833]  [] ? default_spin_lock_flags+0x9/0x10
[113735.650841]  [] __do_fault+0x54/0x500
[113735.650848]  [] handle_mm_fault+0x1a8/0x3c0
[113735.650856]  [] ? hrtimer_wakeup+0x0/0x30
[113735.650863]  [] do_page_fault+0x12a/0x3b0
[113735.650870]  [] page_fault+0x25/0x30
[113735.650875] Mem-Info:
[113735.650878] Node 0 DMA per-cpu:
[113735.650884] CPU0: hi:0, btch:   1 usd:   0
[113735.650888] CPU1: hi:0, btch:   1 usd:   0
[113735.650892] Node 0 DMA32 per-cpu:
[113735.650897] CPU0: hi:  186, btch:  31 usd: 124
[113735.650902] CPU1: hi:  186, btch:  31 usd:  34
[113735.650912] active_anon:524584 inactive_anon:130600 isolated_anon:0
[113735.650914]  active_file:174 inactive_file:230 isolated_file:0
[113735.650916]  unevictable:24 dirty:0 writeback:0 unstable:0
[113735.650918]  free:4760 slab_reclaimable:4044 slab_unreclaimable:9025
[113735.650920]  mapped:8578 shmem:10933 pagetables:8317 bounce:0
[113735.650925] Node 0 DMA free:12072kB min:32kB low:40kB high:48kB 
active_anon:1872kB inactive_anon:1832kB active_file:28kB inactive_file:68kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15340kB 
mlocked:0kB dirty:0kB writeback:0kB mapped:8kB shmem:0kB slab_reclaimable:0kB 
slab_unreclaimable:8kB kernel_stack:0kB pagetables:8kB unstable:0kB bounce:0kB 
writeback_tmp:0kB pages_scanned:135 all_unreclaimable? no
[113735.650945] lowmem_reserve[]: 0 3013 3013 3013
[113735.650954] Node 0 DMA32 free:6968kB min:7004kB low:8752kB high:10504kB 
active_anon:2096464kB inactive_anon:520568kB active_file:668kB 
inactive_file:852kB unevictable:96kB isolated(anon):0kB isolated(file):0kB 
present:3085360kB mlocked:96kB dirty:0kB writeback:0kB mapped:34304kB 
shmem:43732kB slab_reclaimable:16176kB slab_unreclaimable:36092kB 
kernel_stack:2600kB pagetables:33260kB unstable:0kB bounce:0kB 
writeback_tmp:0kB pages_scanned:1344 all_unreclaimable? no
[113735.650976] lowmem_reserve[]: 0 0 0 0
[113735.650984] Node 0 DMA: 2*4kB 2*8kB 1*16kB 2*32kB 1*64kB 1*128kB 2*256kB 
2*512kB 2*1024kB 2*2048kB 1*4096kB = 12072kB
[113735.651005] Node 0 DMA32: 774*4kB 20*8kB 0*16kB 4*32kB 4*64kB 2*128kB 
2*256kB 1*512kB 2*1024kB 0*2048kB 0*4096kB = 6968kB
[113735.651025] 11378 total pagecache pages
[113735.651029] 0 pages in swap cache
[113735.651034] Swap cache stats: add 1216995, delete 1216995, find 39116/54531
[113735.651037] Free swap  = 0kB
[113735.651040] Total swap = 0kB
[113735.667098] 786128 pages RAM
[113735.667103] 13358 pages reserved
[113735.667106] 24312 pages shared
[113735.667109] 756928 pages non-shared
[113735.667116] Out of memory: kill process 30189 (bash) score 3307240 or a 
child
[113735.667123] Killed process 30850 (vlc)

-- 
memory leak
https://bugs.launchpad.net/bugs/575460
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 598857] Re: OpenGL artifacts for surfaces >> 1280x1024

2010-07-01 Thread Exterminans
** Summary changed:

- OpenGL artifacts for surfaces >> 1024x1024
+ OpenGL artifacts for surfaces >> 1280x1024

-- 
OpenGL artifacts for surfaces >> 1280x1024
https://bugs.launchpad.net/bugs/598857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 395155] Re: Too long and unhelpful notification for ".local" domains

2010-06-30 Thread Exterminans
** Changed in: avahi (Ubuntu)
   Status: New => Confirmed

-- 
Too long and unhelpful notification for ".local" domains
https://bugs.launchpad.net/bugs/395155
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 395155] Re: Too long and unhelpful notification for ".local" domains

2010-06-30 Thread Exterminans
** Tags added: lucid

-- 
Too long and unhelpful notification for ".local" domains
https://bugs.launchpad.net/bugs/395155
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon

2010-06-30 Thread Exterminans
Sorry, forgott to add the corrected line in the previous post:
if echo "$OUT" | egrep -vq 'has no|not found|^;; '; then

-- 
Some ISPs have .local domain which disables avahi-daemon
https://bugs.launchpad.net/bugs/327362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon

2010-06-30 Thread Exterminans
I think we are talking about two different bugs: In some networks there
is actually a .local-domain defined, but there are also a lot of false
positives!

In /usr/lib/avahi/avahi-daemon-check-dns.sh line 58 is faulty:
if echo "$OUT" | egrep -vq 'has no|not found'; then

The "host"-command might return additional lines which contain debug-
messages with a trailing ";; " but those are not recognized by this
script and therby result in the shutdown of avahi-daemon.

Line 58 must be changed into the following to get rid of the false positives:
if echo "$OUT" | egrep -vq 'has no|not found'; then

The suggested solution with adding AVAHI_DAEMON_DETECT_LOCAL=0 will
disable the faulty check, but it does not solve the bug itself, even
worse it will cause avahi to enabled in networks where the local-domain
may be used by important services!

-- 
Some ISPs have .local domain which disables avahi-daemon
https://bugs.launchpad.net/bugs/327362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 395155] Re: Too long and unhelpful notification for ".local" domains

2010-06-30 Thread Exterminans
This message is thrown in /usr/lib/avahi/avahi-daemon-check-dns.sh and
causes avahi-daemon to be shut down. Therby zeroconf is no longer
avaible, not even when the "faulty" network was left.

Furthermore in most networks this message and the shutdown are the
result of a bug in this script, the network itself is just fine!

Line 58 is faulty:
if echo "$OUT" | egrep -vq 'has no|not found'; then

The "host"-command may throw comments and debug-messages with a trailing
";; " but those are not recognized by this script and therby result in
the unnecessary shutdown of avahi-daemon.

Change line 58 into the following to make the script work as supposed (and stop 
the unwanted shutdown):
if echo "$OUT" | egrep -vq 'has no|not found|^;; '; then

avahi-daemon will no longer die without a reason after this and the
message will only occur on networks which are truly configured wrong.

-- 
Too long and unhelpful notification for ".local" domains
https://bugs.launchpad.net/bugs/395155
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 598857] Re: OpenGL artifacts for surfaces >> 1024x1024

2010-06-26 Thread Exterminans

** Attachment added: "Width > 1280, height > 1024"
   http://launchpadlibrarian.net/50956147/glxgears10.png

** Description changed:

  When running any OpenGL-apps in windowed- or in fullscreenmode artifacts
  appaer once the size of the rendersurface exceeds 1280x1024px in both
  width and height. If either height or width of the surface stay less or
  equal 1280x1024 px no artifacts appear. This bug occured for me with
  Tremolous and glxgears, tested both each in windows and in
  fullscreenmode with different windowsizes and resolutions.
  
  == System information ==
  Description:  Ubuntu 10.04 LTS 64bit
  Release:  10.04
  Graficscard: Radeon HD 5770
  Displaysize: 1980x1...@60 + 1280x1...@75 (Even with second display not 
connected artifacts appear)
  fglrx: 2:8.723-0ubuntu4 (from ubuntu 10.4 repository)
+ 
+ Their are no messages related to fglrx in syslog or dmesg.

** Description changed:

  When running any OpenGL-apps in windowed- or in fullscreenmode artifacts
  appaer once the size of the rendersurface exceeds 1280x1024px in both
  width and height. If either height or width of the surface stay less or
  equal 1280x1024 px no artifacts appear. This bug occured for me with
- Tremolous and glxgears, tested both each in windows and in
+ Tremolous and glxgears, tested both each in windowed and in
  fullscreenmode with different windowsizes and resolutions.
  
  == System information ==
  Description:  Ubuntu 10.04 LTS 64bit
  Release:  10.04
  Graficscard: Radeon HD 5770
  Displaysize: 1980x1...@60 + 1280x1...@75 (Even with second display not 
connected artifacts appear)
  fglrx: 2:8.723-0ubuntu4 (from ubuntu 10.4 repository)
- 
- Their are no messages related to fglrx in syslog or dmesg.

-- 
OpenGL artifacts for surfaces >> 1024x1024
https://bugs.launchpad.net/bugs/598857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 598857] Re: OpenGL artifacts for surfaces >> 1024x1024

2010-06-26 Thread Exterminans

** Attachment added: "Width <= 1280, height > 1024"
   http://launchpadlibrarian.net/50956050/glxgears9.png

** Description changed:

  When running any OpenGL-apps in windowed- or in fullscreenmode artifacts
- appaer once the size of the rendersurface exceeds 1024px in both width
- and height. If either height or width of the surface stay less or equal
- 1024 px no artifacts appear. This bug occured for me with Tremolous and
- glxgears, tested both each in windows and in fullscreenmode with
- different windowsizes and resolutions.
+ appaer once the size of the rendersurface exceeds 1280x1024px in both
+ width and height. If either height or width of the surface stay less or
+ equal 1280x1024 px no artifacts appear. This bug occured for me with
+ Tremolous and glxgears, tested both each in windows and in
+ fullscreenmode with different windowsizes and resolutions.
  
  == System information ==
  Description:  Ubuntu 10.04 LTS 64bit
  Release:  10.04
  Graficscard: Radeon HD 5770
  Displaysize: 1980x1...@60 + 1280x1...@75 (Even with second display not 
connected artifacts appear)
  fglrx: 2:8.723-0ubuntu4 (from ubuntu 10.4 repository)

-- 
OpenGL artifacts for surfaces >> 1024x1024
https://bugs.launchpad.net/bugs/598857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 598857] Re: OpenGL artifacts for surfaces >> 1024x1024

2010-06-26 Thread Exterminans

** Attachment added: "Width > 1024, height > 1024"
   http://launchpadlibrarian.net/50956008/glxgears3.png

-- 
OpenGL artifacts for surfaces >> 1024x1024
https://bugs.launchpad.net/bugs/598857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 598857] Re: OpenGL artifacts for surfaces >> 1024x1024

2010-06-26 Thread Exterminans

** Attachment added: "WIdth > 1024, height <= 1024"
   http://launchpadlibrarian.net/50955989/glxgears1.png

-- 
OpenGL artifacts for surfaces >> 1024x1024
https://bugs.launchpad.net/bugs/598857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 598857] Re: OpenGL artifacts for surfaces >> 1024x1024

2010-06-26 Thread Exterminans

** Attachment added: "fglrxinfo -v"
   http://launchpadlibrarian.net/50955913/fglrxinfo.txt

-- 
OpenGL artifacts for surfaces >> 1024x1024
https://bugs.launchpad.net/bugs/598857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 598857] [NEW] OpenGL artifacts for surfaces >> 1024x1024

2010-06-26 Thread Exterminans
Public bug reported:

When running any OpenGL-apps in windowed- or in fullscreenmode artifacts
appaer once the size of the rendersurface exceeds 1280x1024px in both
width and height. If either height or width of the surface stay less or
equal 1280x1024 px no artifacts appear. This bug occured for me with
Tremolous and glxgears, tested both each in windowed and in
fullscreenmode with different windowsizes and resolutions.

== System information ==
Description:Ubuntu 10.04 LTS 64bit
Release:10.04
Graficscard: Radeon HD 5770
Displaysize: 1980x1...@60 + 1280x1...@75 (Even with second display not 
connected artifacts appear)
fglrx: 2:8.723-0ubuntu4 (from ubuntu 10.4 repository)

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New

-- 
OpenGL artifacts for surfaces >> 1024x1024
https://bugs.launchpad.net/bugs/598857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs