Resizing on bottom screen crashes windows

Bug #796444 reported by Paweł on 2011-06-13
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Unity
Expired
Undecided
Unassigned
unity (Ubuntu)
Undecided
Unassigned

Bug Description

While I reported this on Bug #751605, I think problem with resizing is different thing.

I have dual monitor setup with laptop on bottom and external monitor over the laptop.
When I try resize any window on my bottom screen it crashes. Even when I add seccond tab in Terminal, and window is automatically expands to fit the tabs bar, it crashes after that.

I have to move that window to my upper screen, resize, add tab, and then move it back to lower monitor.

Bilal Akhtar (bilalakhtar) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in unity:
status: New → Invalid
Changed in unity (Ubuntu):
status: New → Invalid
Paweł (paff) wrote :

I will prepare crash report later, but can anyone try to reporoduce this? I tried to resize on 2 different computers with 2 monitors, every of them crashes, when resizing windows on lower monitor (vertical screens).

Paweł (paff) wrote :

I've tried to generate crash report, but I cant.

pmanski@thinkpad:~$ sudo service apport start force_start=1
[sudo] password for pmanski:
apport start/running

So, apport is running. Now I resized TERMINAL, EMPATHY, BANSHEE, SHOTWELL, and ther was not any file in /var/crash

pmanski@thinkpad:~$ ls -al /var/crash
razem 8
drwxrwxrwt 2 root root 4096 2011-05-26 08:31 .
drwxr-xr-x 15 root root 4096 2011-04-23 00:02 ..

I tried also Chromium, and after crash Ubuntu asks me for sending crash report, but after while said, that I cant fill the report, cause the software is not from canonical. When I tried seccond time with Chromium, Every windows frame dissapered (unity-window-decorator).

Only after Opera crashed, I have some file in /var/crash, but trying to send:

pmanski@thinkpad:~$ unity-window-decorator ubuntu-bug /var/crash/_usr_lib_opera_opera.1000.crash
The program 'unity-window-decorator' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 4172 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Paweł (paff) wrote :

Sorry, I made mistake in command :)

When trying to send crash report from Opera, I have the same message like in Chromium. Report cant be send, because application is not oryginal form Ubuntu.

TERMINAL, EMPATHY, BANSHEE, SHOTWELL - they dont save any file in /var/crash.

Paweł (paff) wrote :

Can anyone try such configuration? VERTICAL screens, and resizing windows on lower screen.

Changed in unity:
status: Invalid → Confirmed
Changed in unity (Ubuntu):
status: Invalid → Confirmed
Omer Akram (om26er) wrote :

you cannot confirm your own bug.

Changed in unity:
status: Confirmed → New
Changed in unity (Ubuntu):
status: Confirmed → New
Bilal Akhtar (bilalakhtar) wrote :

Okay then. Try running the crashing apps from a terminal on the upper screen, move them to the lower and resize them. Then, after the crash, paste the terminal output here.

Changed in unity:
status: New → Incomplete
Changed in unity (Ubuntu):
status: New → Incomplete
Paweł (paff) wrote :

pmanski@thinkpad:~$ opera
Attempting to load the system libmoon
opera: Activated running instance
Naruszenie ochrony pamięci

pmanski@thinkpad:~$ evolution

(evolution:3304): GLib-GObject-CRITICAL **: Object class EMFolderTree doesn't implement property 'paste-target-list' from interface 'ESelectable'

(evolution:3304): GLib-GObject-CRITICAL **: Object class EMFolderTree doesn't implement property 'copy-target-list' from interface 'ESelectable'
The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 23317 error_code 8 request_code 59 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

pmanski@thinkpad:~$ firefox

(firefox-bin:3339): LIBDBUSMENU-GTK-CRITICAL **: dbusmenu_menuitem_property_set_shortcut: assertion `gtk_accelerator_valid(key, modifier)' failed
###!!! ABORT: X_ShapeRectangles: BadMatch (invalid parameter attributes); 1126 requests ago: file /build/buildd/firefox-4.0.1+build1+nobinonly/build-tree/mozilla/toolkit/xre/nsX11ErrorHandler.cpp, line 203
###!!! ABORT: X_ShapeRectangles: BadMatch (invalid parameter attributes); 1126 requests ago: file /build/buildd/firefox-4.0.1+build1+nobinonly/build-tree/mozilla/toolkit/xre/nsX11ErrorHandler.cpp, line 203

Paweł (paff) wrote :

I think this is connected with the inability to move a window betwen screens (from main to seccond-bottom - the other way I can move window).
And Unity Panel is visible on both screens - upeer and lower - I got used to arleady, but I do not really like it.

Paweł (paff) wrote :

pmanski@thinkpad:~$ xrandr
Screen 0: minimum 320 x 200, current 1366 x 1792, maximum 8192 x 8192
LVDS1 connected 1366x768+0+1024 (normal left inverted right x axis y axis) 293mm x 165mm
   1366x768 60.0*+ 50.0
   1360x768 59.8 60.0
   1024x768 60.0
   800x600 60.3 56.2
   640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm
   1280x1024 60.0 + 75.0*
   1280x960 60.0
   1152x864 75.0
   1024x768 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3 56.2
   640x480 72.8 75.0 66.7 60.0
   720x400 70.1
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)

Omer Akram (om26er) wrote :

so if you are in Ubuntu Classic session this issue does not happen? what about metacity as the window manager?

wesdeboer (wesdeboer) wrote :

I'm having to same issue. I can resize windows on my secondary (top) monitor no problem, but resizing windows on my primary (bottom) monitor the app crashes. I have tried in Ubuntu Classic and windows will resize correctly on both monitors top and bottom.

A partial workaround I noticed is that I can grab the top left and top right corners to resize the window, but the bottom left and bottom right corners crash the app.

Also to note, the app never crashed until I tried to logout/restart. I used nautilus to test it out. Opened it up, dragged it to the bottom monitor, resized the window using the bottom right corner to drag and it immediately disappeared. No crash logs. I logout/restart and I get the standard app is not responding dialog and that's when the crash report is generated.

Launchpad Janitor (janitor) wrote :

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
Changed in unity (Ubuntu):
status: Expired → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for Unity because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
Changed in unity:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers