[Bug 778490] Re: Random logout after upgrading to Natty Narwhal 11.04

2011-05-30 Thread Martin Vielsmaier
In response to #32.


** Attachment added: Xorg.0.log.old
   
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/778490/+attachment/2147627/+files/Xorg.0.log.old

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

Title:
  Random logout after upgrading to Natty Narwhal 11.04

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


[Bug 788627] [NEW] compiz crash when using grid to arrange window

2011-05-26 Thread Martin Vielsmaier
Public bug reported:

Binary package hint: compiz

While I played a little with the grid plugin compiz crashed. I'm not
sure what I did right before the crash, but I think I moved the window
away from the screen edge. I tried to reproduce the crash for some
minutes without success.

Backtrace:
*** glibc detected *** compiz: double free or corruption (fasttop): 
0x03baf520 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x78a8f)[0x7f3a16530a8f]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x73)[0x7f3a165348e3]
/usr/lib/compiz/libgrid.so(_ZN10GridScreen11handleEventEP7_XEvent+0x7cb)[0x7f3a0d751a2b]
compiz(_ZN10CompScreen11handleEventEP7_XEvent+0xe3)[0x44e9a3]
/usr/lib/compiz/libregex.so(_ZN11RegexScreen11handleEventEP7_XEvent+0x2f)[0x7f3a0d53d4bf]
compiz(_ZN10CompScreen11handleEventEP7_XEvent+0xe3)[0x44e9a3]
/usr/lib/compiz/libmove.so(_ZN10MoveScreen11handleEventEP7_XEvent+0xbc)[0x7f3a0d1097bc]
compiz(_ZN10CompScreen11handleEventEP7_XEvent+0xe3)[0x44e9a3]
/usr/lib/compiz/libsession.so(_ZN13SessionScreen11handleEventEP7_XEvent+0x40)[0x7f3a0cae33c0]
compiz(_ZN10CompScreen11handleEventEP7_XEvent+0xe3)[0x44e9a3]
=== Memory map: 
0040-0046f000 r-xp  08:01 377
/usr/bin/compiz
0066e000-0066f000 r--p 0006e000 08:01 377
/usr/bin/compiz
0066f000-0067 rw-p 0006f000 08:01 377
/usr/bin/compiz
0067-00671000 rw-p  00:00 0 
0186f000-04401000 rw-p  00:00 0  [heap]
7f39f2d56000-7f39f4556000 rw-s 112606000 00:05 1493  
/dev/dri/card0
7f39f4556000-7f39f5d56000 rw-s 110e06000 00:05 1493  
/dev/dri/card0
7f39f5d56000-7f39f800 r--p  08:01 418190 
/usr/share/icons/gnome/icon-theme.cache
7f39f800-7f39f8279000 rw-p  00:00 0 
7f39f8279000-7f39fc00 ---p  00:00 0 
7f39fd089000-7f39fd0e9000 r--p  08:01 656308 
/usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-RI.ttf
7f39fd0e9000-7f39fd14d000 r--p  08:01 434804 
/usr/share/locale-langpack/de/LC_MESSAGES/evolution-2.32.mo
7f39fd14d000-7f39fd183000 r-xp  08:01 3962   
/usr/lib/libcroco-0.6.so.3.0.1
7f39fd183000-7f39fd382000 ---p 00036000 08:01 3962   
/usr/lib/libcroco-0.6.so.3.0.1
7f39fd382000-7f39fd383000 r--p 00035000 08:01 3962   
/usr/lib/libcroco-0.6.so.3.0.1
7f39fd383000-7f39fd386000 rw-p 00036000 08:01 3962   
/usr/lib/libcroco-0.6.so.3.0.1
7f39fd386000-7f39fd3ba000 r-xp  08:01 4547   
/usr/lib/librsvg-2.so.2.32.1
7f39fd3ba000-7f39fd5ba000 ---p 00034000 08:01 4547   
/usr/lib/librsvg-2.so.2.32.1
7f39fd5ba000-7f39fd5bb000 r--p 00034000 08:01 4547   
/usr/lib/librsvg-2.so.2.32.1
7f39fd5bb000-7f39fd5bc000 rw-p 00035000 08:01 4547   
/usr/lib/librsvg-2.so.2.32.1
7f39fd5bc000-7f39fd5be000 r-xp  08:01 5882   
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
7f39fd5be000-7f39fd7bd000 ---p 2000 08:01 5882   
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
7f39fd7bd000-7f39fd7be000 r--p 1000 08:01 5882   
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
7f39fd7be000-7f39fd7bf000 rw-p 2000 08:01 5882   
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
7f39fd7bf000-7f39fdc62000 r--p  08:01 442350 
/usr/share/icons/hicolor/icon-theme.cache
7f39fdc62000-7f39fdd4c000 r--p  08:01 409926 
/usr/share/icons/Humanity/icon-theme.cache
7f39fdd4c000-7f39fdd6 r-xp  08:01 5995   
/usr/lib/gio/modules/libgioremote-volume-monitor.so
7f39fdd6-7f39fdf5f000 ---p 00014000 08:01 5995   
/usr/lib/gio/modules/libgioremote-volume-monitor.so
7f39fdf5f000-7f39fdf6 r--p 00013000 08:01 5995   
/usr/lib/gio/modules/libgioremote-volume-monitor.so
7f39fdf6-7f39fdf61000 rw-p 00014000 08:01 5995   
/usr/lib/gio/modules/libgioremote-volume-monitor.so
7f39fdf61000-7f39fdf63000 r-xp  08:01 135189 
/lib/x86_64-linux-gnu/libutil-2.13.so
7f39fdf63000-7f39fe162000 ---p 2000 08:01 135189 
/lib/x86_64-linux-gnu/libutil-2.13.so
7f39fe162000-7f39fe163000 r--p 1000 08:01 135189 
/lib/x86_64-linux-gnu/libutil-2.13.so
7f39fe163000-7f39fe164000 rw-p 2000 08:01 135189 
/lib/x86_64-linux-gnu/libutil-2.13.so
7f39fe164000-7f39fe171000 r-xp  08:01 135188 
/lib/x86_64-linux-gnu/libudev.so.0.11.1
7f39fe171000-7f39fe37 ---p d000 08:01 135188 

[Bug 788627] Re: compiz crash when using grid to arrange window

2011-05-26 Thread Martin Vielsmaier
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788627

Title:
  compiz crash when using grid to arrange window

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


[Bug 788627] Re: compiz crash when using grid to arrange window

2011-05-26 Thread Martin Vielsmaier
Just noticed that you can reproduce the crash by moving a Java (Swing)
window to the screen edge. It happens shortly after the grid plugin
offers to arrange the window by showing the yellowish box.

The valgrind log looks not very helpful, but I still attached it. I started 
compiz/unity with the following command:
G_SLICE=always-malloc G_DEBUG=gc-friendly  valgrind -v --tool=memcheck 
--leak-check=full --num-callers=40 --log-file=valgrind.log unity

** Attachment added: valgrind.log
   
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/788627/+attachment/2143741/+files/valgrind.log

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

Title:
  compiz crash when using grid to arrange window

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


[Bug 446717] Re: [gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 4810T and 5810T models

2010-09-23 Thread Martin Vielsmaier
The bug is fixed for me by the following commit: 
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4e5359cd053bfb7d8dabe4a63624a5726848ffbc
It is part of kernels = 2.6.36-rc4.
Setting the brightness for me still is somehow weird (after pressing 
Fn+left_arrow more than one time, Fn+right_arrow switches the brightness down 
instead of up one time, it has just got 5-6 levels, while the /sys and /proc 
filesystems suggest 10 levels), but it is a great thing to be able to press 
buttons without the constant fear of a freeze.

-- 
[gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 
4810T and 5810T models
https://bugs.launchpad.net/bugs/446717
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 446717] Re: [gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 4810T and 5810T models

2010-07-14 Thread Martin Vielsmaier
When the system is frozen it is enough to kill compiz to break the freeze.
I attached gdb to compiz while frozen, here is the stack:
(gdb) info stack 
#0  0x7fc45b2d2187 in ioctl () from /lib/libc.so.6
#1  0x7fc45891e84d in drm_intel_gem_bo_start_gtt_access () from 
/lib/libdrm_intel.so.1
#2  0x7fc458d8d70f in ?? () from /usr/lib/dri/i965_dri.so
#3  0x7fc45ba3d612 in glXSwapBuffers () from /usr/lib/mesa/libGL.so.1
#4  0x00413302 in eventLoop ()
#5  0x0040d8e9 in main ()

A second time with some more debug symbols installed:
(gdb) info stack 
#0  0x7f2c27198187 in ioctl () from /lib/libc.so.6
#1  0x7f2c247e484d in drm_intel_gem_bo_start_gtt_access (bo=0x1ac6960, 
write_enable=value optimized out)
at ../../intel/intel_bufmgr_gem.c:1145
#2  0x7f2c24c5370f in ?? () from /usr/lib/dri/i965_dri.so
#3  0x7f2c27903116 in ?? () from /usr/lib/mesa/libGL.so.1
#4  0x00412afb in eventLoop ()
#5  0x0040d8e9 in main ()

I also believe that this problem is closely linked to OpenGL activity. Before I 
touch the brightness keys everything is fine. Compiz and glxgears run. When I 
touched the brightness keys (sometimes I need to touch them more than one 
time), compiz freezes. When I kill it via a SSH session and then start glxgears 
it freezes too. 
Attached gdb to frozen glxgears, stack:
(gdb) info stack
#0  0x7ff3a3abf187 in ioctl () from /lib/libc.so.6
#1  0x7ff3a1c6c84d in drm_intel_gem_bo_start_gtt_access () from 
/lib/libdrm_intel.so.1
#2  0x7ff3a20db70f in ?? () from /usr/lib/dri/i965_dri.so
#3  0x7ff3a4560612 in glXSwapBuffers () from /usr/lib/mesa/libGL.so.1
#4  0x0040339f in ?? ()
#5  0x7ff3a39ffc4d in __libc_start_main () from /lib/libc.so.6
#6  0x004018c9 in ?? ()
#7  0x7fff1b7b1d78 in ?? ()
#8  0x001c in ?? ()
#9  0x0001 in ?? ()
#10 0x7fff1b7b3645 in ?? ()
#11 0x in ?? ()

Second time:
(gdb) info stack
#0  0x7f0027c5d187 in ioctl () from /lib/libc.so.6
#1  0x7f0025e0a84d in drm_intel_gem_bo_start_gtt_access (bo=0x25f8be0, 
write_enable=value optimized out)
at ../../intel/intel_bufmgr_gem.c:1145
#2  0x7f002627970f in ?? () from /usr/lib/dri/i965_dri.so
#3  0x7f00286fe612 in glXSwapBuffers () from /usr/lib/mesa/libGL.so.1
#4  0x0040339f in ?? ()
#5  0x7f0027b9dc4d in __libc_start_main () from /lib/libc.so.6
#6  0x004018c9 in ?? ()
#7  0x77897138 in ?? ()
#8  0x001c in ?? ()
#9  0x0001 in ?? ()
#10 0x77897680 in ?? ()
#11 0x in ?? ()

Any ideas what could trigger the bug? (Note that when the brightness
keys were touched once, this bug persists. So I think that some register
on the graphics card is set wrong and from then on causes problems... Is
there a way to read them all at once to see what changes?)

-- 
[gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 
4810T and 5810T models
https://bugs.launchpad.net/bugs/446717
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 446717] Re: [gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 4810T and 5810T models

2010-07-12 Thread Martin Vielsmaier
Well +1 :-(

I'm running Lucid on a 4810TG (with ATI, but not using the ATI card,
because it drains my battery, see
http://ubuntuforums.org/showpost.php?p=7933876postcount=11 for a module
that powers off the ATI card.)

My tries to fix include the following:
- Tried kernel 2.6.34 (package from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/): No change, still get a freeze
- Tried the acpi_backlight=vendor boot option: No change
- Tried the nomodeset and acpi_backlight=vendor boot options: Seems to fix 
it, BUT nomodeset breaks lots of stuff for me, so this is not an acceptable 
option.

There is a working way to set the brightness (see script below
Brightness Control  9.10 on
https://help.ubuntu.com/community/AspireTimeline/Fixes).

So all I need for a satisfactory workaround is a way to prevent the kernel and 
friends from trying to set the brightness. Didn't manage to do so yet:
1) Tried the acpi.brightness_switch_enabled=0 boot option: No change (even 
seems like this does not work at all, because less 
/sys/module/video/parameters/brightness_switch_enabled still shows Y)
2) Tried echo 0  /sys/module/video/parameters/brightness_switch_enabled (as 
root): No change, still changes the brightness and freezes
3) Tried the acpi_backlight=vendor boot option and additionally modprobe -r 
acer_wmi (acer_wmi is the module I suspect to be in charge when the vendor 
option is passed): No change
4) 3) + modprobe -r acer_wmi: No change

So: Is there some way to prevent the kernel and modules from trying to
set the brightness? This is really annoying because when you remove the
AC plug it tries to change the brightness and freezes...

-- 
[gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 
4810T and 5810T models
https://bugs.launchpad.net/bugs/446717
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 446717] Re: [gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 4810T and 5810T models

2010-07-12 Thread Martin Vielsmaier
oh:
4) should be 2) + ...

-- 
[gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 
4810T and 5810T models
https://bugs.launchpad.net/bugs/446717
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 446717] Re: [gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 4810T and 5810T models

2010-07-12 Thread Martin Vielsmaier
I found a way to prevent the kernel from setting the brightness:
acpi=off boot option, but that is not what you want to do an a laptop
:-)

-- 
[gm45] Adjusting Brightness in Acer Aspire Timelines causes system freeze in 
4810T and 5810T models
https://bugs.launchpad.net/bugs/446717
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 499511] [NEW] GemCutter should be a source by default

2009-12-22 Thread Martin Vielsmaier
Public bug reported:

When installing rubygems1.8 (which is rubygems 1.3.5) on Karmic 
http://gemcutter.org; is NOT a source of gems by default.
It should be a default source starting from version 1.3.5. This also prevents 
the gem tumble command (which is the standard way of adding GemCutter as an 
source of gems) from working, because it was deprecated in version 1.3.5.

** Affects: libgems-ruby (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  When installing rubygems1.8 (which is rubygems 1.3.5) on Karmic 
http://gemcutter.org; is NOT a source of gems by default.
- It should be a default source starting from version 1.3.5. This also prevents 
the gem tumble command (which is the standard way of adding GemCutter as an 
source of gems) from work, because it was deprecated in version 1.3.5.
+ It should be a default source starting from version 1.3.5. This also prevents 
the gem tumble command (which is the standard way of adding GemCutter as an 
source of gems) from working, because it was deprecated in version 1.3.5.

-- 
GemCutter should be a source by default
https://bugs.launchpad.net/bugs/499511
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