Resize of divider window causes X to crash

[Keith Buel]

Binary package hint: bzr

This is reproducible.

This is actually caused when using Bazaar Explorer, so i'm not sure if the package should be updated or not. (this is what ubuntu-bug picked when I chose the pid.)

When I click the commit button, the commit dialog pops up with the "Message" text box at the top and the changed files at the bottom.

There is a divider separating the two. When I try to resize the the two panes by dragging the divider, the screen goes black and I am presented with the login screen.

I have done this twice, to prove that this was in fact the cause.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bzr 2.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sun Dec 26 23:13:22 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bzr
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.6
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: bzr

[Dave Gilbert (ubuntu-treblig)]

Hi,
  Just after you manage to crash it and relog in you should find that there is a /var/log/Xorg.0.log.old - can you add that to this bug report; I suspect the bug is actually the X server, but that might help tell us.

Dave

[Keith Buel (kbuel)]

Dave Gilbert,

Here is Xorg.0.log.old right after I relog in after the crash.

[Dave Gilbert (ubuntu-treblig)]

Thanks Keith;
reassigning this bug to fglrx - here's the backtrace from the log file keith attached:

Backtrace:
[ 46618.364] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a0fa8]
[ 46618.364] 1: /usr/bin/X (0x400000+0x60fcd) [0x460fcd]
[ 46618.364] 2: /lib/libpthread.so.0 (0x7f925d483000+0xfb40) [0x7f925d492b40]
[ 46618.364] 3: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x6e) [0x7f925943c22e]
[ 46618.364] 4: /usr/lib/xorg/extra-modules/modules/glesx.so (0x7f925740a000+0x36709) [0x7f9257440709]
[ 46618.364] 5: /usr/lib/xorg/extra-modules/modules/glesx.so (0x7f925740a000+0x37e75) [0x7f9257441e75]
[ 46618.364] 6: /usr/bin/X (0x400000+0xd82e0) [0x4d82e0]
[ 46618.364] 7: /usr/bin/X (0x400000+0xd13d9) [0x4d13d9]
[ 46618.365] 8: /usr/bin/X (0x400000+0x2c2d9) [0x42c2d9]
[ 46618.365] 9: /usr/bin/X (0x400000+0x2184b) [0x42184b]
[ 46618.365] 10: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7f925c3eed8e]
[ 46618.365] 11: /usr/bin/X (0x400000+0x213d9) [0x4213d9]
[ 46618.365] Segmentation fault at address 0x18
[ 46618.365]
Caught signal 11 (Segmentation fault). Server aborting

[dz0ny (janez-troha)]

For me it chrashes at gdm start, the log is attached. To note i also tried with new xorg-edgers ppa and result is same.

update-initramfs: Generating /boot/initrd.img-2.6.35-24-generic
update-initramfs: Generating /boot/initrd.img-2.6.35-23-generic
Loading new fglrx-8.801 DKMS files...
Building for 2.6.35-23-generic and 2.6.35-24-generic
Building for architecture x86_64
Building initial module for 2.6.35-23-generic
Done.

fglrx.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/2.6.35-23-generic/updates/dkms/

depmod....

DKMS: install Completed.
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
update-initramfs: Generating /boot/initrd.img-2.6.35-24-generic

[Dave Gilbert (ubuntu-treblig)]

Hi cupacup,
  Can you file that as a separate bug; the bugs may get merged if it actually turns out it's the same cause.

Dave

[bugbot (bugbot)]

Hey Keith,

Hi, have you had a chance to test if this bug is still present in natty?

If it does (and if you're the original reporter), please boot into natty
and run the command:

  apport-collect <bug-number>

which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.