Bug 2109187 - lxrandr - displays "Unable to get monitor information!"
Summary: lxrandr - displays "Unable to get monitor information!"
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lxrandr
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-20 15:11 UTC by Edward
Modified: 2022-07-29 02:02 UTC (History)
2 users (show)

Fixed In Version: glib2-2.73.2-7.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-29 02:02:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lxrandr window (6.60 KB, image/png)
2022-07-21 12:43 UTC, Edward
no flags Details
lxrandr window on full desktop at 1024x768 (543.56 KB, image/png)
2022-07-22 16:06 UTC, Edward
no flags Details
LXDE desktop at bootup in virtual machine (103.26 KB, image/jpeg)
2022-07-22 16:07 UTC, Edward
no flags Details
lxrandr after glib2 packages update (18.81 KB, image/png)
2022-07-26 13:18 UTC, Edward
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME glib issues 2700 0 None opened g_regex_match fails on multiple archs (including x86_64) with Fedora glib2-2.73.2-4.fc37 2022-07-25 12:09:11 UTC

Description Edward 2022-07-20 15:11:04 UTC
Description of problem:

Installed Fedora Rawhide LXDE image https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220719.n.0/compose/Spins/x86_64/iso/Fedora-LXDE-Live-x86_64-Rawhide-20220719.n.0.iso into a virtual machine using virt-manager. During and after installation, monitor resolution defaults to 1024x768. Selecting Preferences/Monitor Settings (which is lxrandr) displays a window with "Unable to get monitor information!" 

A workaround is to add:

xrandr --output Virtual-0 -mode 1600x900 

to LXSession configuration Autostart


Version-Release number of selected component (if applicable):

lxrandr-0.3.2-8.fc36.x86_64

Comment 1 Mamoru TASAKA 2022-07-21 01:06:18 UTC
If you don't add the workaround, what does the result of 

$ xrandr

says?

Comment 2 Edward 2022-07-21 12:41:56 UTC
~]$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
Virtual-0 connected primary 1024x768+0+0 0mm x 0mm
   1024x768      60.00*+
   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  
   1280x854      59.95  
   1366x768      59.79    60.00  
   1360x768      60.02  
   1280x800      59.81    59.91  
   1280x768      59.87    59.99  
   1280x720      60.00  
   1152x768      59.95  
   800x600       60.32    56.25  
   848x480       60.00  
   720x480       59.94  
   640x480       59.94  
Virtual-1 disconnected
Virtual-2 disconnected
Virtual-3 disconnected

Comment 3 Edward 2022-07-21 12:43:32 UTC
Created attachment 1898461 [details]
lxrandr window

This is what appears when lxrandr is launched from a terminal window, or from the Preferences/Monitor Settings menu.

Comment 4 Mamoru TASAKA 2022-07-22 07:31:45 UTC
Would you again reboot, reproduce this issue, and again show the output of
$ xrandr
when this issue is appearing? The output of xrandr should be recognized by lxrandr and this issue seems unreproducible to me.

Comment 5 Edward 2022-07-22 16:05:13 UTC
Same output.

 ~]$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
Virtual-0 connected primary 1024x768+0+0 0mm x 0mm
   1024x768      60.00*+
   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  
   1280x854      59.95  
   1366x768      59.79    60.00  
   1360x768      60.02  
   1280x800      59.81    59.91  
   1280x768      59.87    59.99  
   1280x720      60.00  
   1152x768      59.95  
   800x600       60.32    56.25  
   848x480       60.00  
   720x480       59.94  
   640x480       59.94  
Virtual-1 disconnected
Virtual-2 disconnected
Virtual-3 disconnected

Comment 6 Edward 2022-07-22 16:06:22 UTC
Created attachment 1898787 [details]
lxrandr window on full desktop at 1024x768

The lxrandr window with full desktop at 1024x768.

Comment 7 Edward 2022-07-22 16:07:56 UTC
Created attachment 1898788 [details]
LXDE desktop at bootup in virtual machine

Picture of the full LXDE desktop taken with my mobile phone, it defaults to 1024x768 without the added xrandr command in Autostart.

Comment 8 Mamoru TASAKA 2022-07-24 14:38:01 UTC
Note that I just checked F36 behavior, not rawhide behavior yet. Maybe glib2 g_regex behavior changed due to pcre -> pcre2 change??

Comment 9 Mamoru TASAKA 2022-07-26 07:32:04 UTC
Would you check if the following works?

https://download.copr.fedorainfracloud.org/results/mtasaka/glib2-test/fedora-rawhide-x86_64/04685594-glib2/

Comment 10 Edward 2022-07-26 13:16:18 UTC
Yes. It works. Before and after removing the xrandr command from Autostart.

Attached is a new screenshot, after removing the xrandr command.

Thank you.

Comment 11 Edward 2022-07-26 13:18:06 UTC
Created attachment 1899443 [details]
lxrandr after glib2 packages update

The lxrandr window after the glib2 packages update and after removing the xrandr command from Autostart.

Comment 12 Mamoru TASAKA 2022-07-26 13:40:09 UTC
Okay, thank you for confirmation. I guess glib2 2.73.3 will be released in the near future, and then I think we can close this bug.

Comment 13 Edward 2022-07-26 14:33:14 UTC
You're very welcome. And thank you for working on this.

I'll leave the 2.73.2 packages from the above link, installed.

Comment 14 Mamoru TASAKA 2022-07-27 12:48:58 UTC
The upstream fix is backported on glib2-2.73.2-7.fc37, which should fix this issue.
https://koji.fedoraproject.org/koji/buildinfo?buildID=2036974

Comment 15 Mamoru TASAKA 2022-07-29 02:02:47 UTC
Fixed in glib2-2.73.2-7.fc37 . Thank you for reporting.


Note You need to log in before you can comment on or make changes to this bug.