Description of problem: Installed virtual box guest additions, screen size was 1024 but after reboot was a lot smaller, maybe 800x600, or less. Cannot even run the Display program. Using Fedora 23 Games Spin. Version-Release number of selected component: xfce4-settings-4.12.0-6.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: xfce4-display-settings crash_function: convert_xfce_output_info executable: /usr/bin/xfce4-display-settings global_pid: 1847 kernel: 4.5.6-200.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 convert_xfce_output_info at main.c:1618 #1 get_output_for_window at main.c:2671 #2 select_current_output_from_dialog_position at main.c:2708 #3 dialog_map_event_cb at main.c:2722 #4 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #9 gtk_widget_event_internal at gtkwidget.c:5017 #10 gtk_widget_event at gtkwidget.c:4814 #11 gtk_main_do_event at gtkmain.c:1650 #17 gtk_main at gtkmain.c:1268 #18 display_settings_show_main_dialog at main.c:2816
Created attachment 1168476 [details] File: backtrace
Created attachment 1168477 [details] File: cgroup
Created attachment 1168478 [details] File: core_backtrace
Created attachment 1168479 [details] File: dso_list
Created attachment 1168480 [details] File: environ
Created attachment 1168481 [details] File: exploitable
Created attachment 1168482 [details] File: limits
Created attachment 1168483 [details] File: maps
Created attachment 1168484 [details] File: mountinfo
Created attachment 1168485 [details] File: namespaces
Created attachment 1168486 [details] File: open_fds
Created attachment 1168487 [details] File: proc_pid_status
Created attachment 1168488 [details] File: var_log_messages
What does 'xrandr -q' report in the guest?
Hi, I'm at work at the moment and the image is at home. I've fixed the screen resolution part of the problem. I followed the advice here: https://ask.fedoraproject.org/en/question/69797/unable-to-select-right-screen-resolution-in-fedora-22/ When I ran this command, it seemed to give it a kick: xrandr --output VGA-1 --mode "1920x1200" After this, resizing the window from the host worked. Also I could run Display again. I'm still having problems though - Chrome is unusable - the rendering is so bad I can't really see anything at all. I tried to change to GNOME desktop - got a black screen. I changed to GNOME classic. The fonts were unreadable - it looked like all the letters were rendered on top of each other. KDE was unusable - just showed a couple of icons. Xfce is the only desktop I've tried so far that is at least partially usable.
Ok, so I have the problem again. A new version of Virtual Box came out, 5.0.22. So I reinstalled the Virtual Box Guest Additions and the Display program now crashes. Here is the output of xrandr -q [tim@IridiumVM ~]$ xrandr -q Screen 0: minimum 320 x 200, current 1016 x 788, maximum 16384 x 16384 VGA-1 connected 1016x788+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1560x996 59.86 + 2560x1600 59.99 59.97 1920x1440 60.00 1856x1392 60.00 1792x1344 60.00 2048x1152 60.00 1920x1200 59.88 59.95 1920x1080 60.00 1600x1200 60.00 1680x1050 59.95 59.88 1400x1050 59.98 59.95 1600x900 60.00 1280x1024 60.02 1440x900 59.89 59.90 1280x960 60.00 1366x768 59.79 60.00 1360x768 60.02 1280x800 59.81 59.91 1280x768 59.87 59.99 1280x720 60.00 1024x768 60.00 800x600 60.32 56.25 848x480 60.00 640x480 59.94 1016x788 (0x42) 64.750MHz h: width 1016 start 1064 end 1168 total 1320 skew 0 clock 49.05KHz v: height 788 start 791 end 801 total 818 clock 59.97Hz [tim@IridiumVM ~]$ Then I ran this and the window resized, output of that command also changed. [tim@IridiumVM ~]$ xrandr --output VGA-1 --mode "1920x1200" [tim@IridiumVM ~]$ xrandr -q Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384 VGA-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1560x996 59.86 + 2560x1600 59.99 59.97 1920x1440 60.00 1856x1392 60.00 1792x1344 60.00 2048x1152 60.00 1920x1200 59.88* 59.95 1920x1080 60.00 1600x1200 60.00 1680x1050 59.95 59.88 1400x1050 59.98 59.95 1600x900 60.00 1280x1024 60.02 1440x900 59.89 59.90 1280x960 60.00 1366x768 59.79 60.00 1360x768 60.02 1280x800 59.81 59.91 1280x768 59.87 59.99 1280x720 60.00 1024x768 60.00 800x600 60.32 56.25 848x480 60.00 640x480 59.94 [tim@IridiumVM ~]$ It is possible to run display again now.
So, it clearly doesn't like the "non standard" resolutions. ;( Would you care to file this upstream at bugzilla.xfce.org? Or if you prefer I can do so...
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.