mjbeverley / inxi

Automatically exported from code.google.com/p/inxi
0 stars 0 forks source link

no infos about Xorg and resolution when inxi run as root #8

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

Running 'inxi -F' as root gives no info about
* Xorg-server (e.g. version)
* displayed resolution

What is the expected output? What do you see instead?

Output of inxi invoking as normal-user and root differ!

[normal user]
$ inxi -F
System:    Host seduxbox running  Linux 2.6.27-6.slh.5-sidux-686 i686
Distro sidux 2008-03 Ουρέα - kde-lite - (200809221818) 
CPU:       Dual Core Intel Core2 T7200 cache 4096 KB bmips 7979.88 
           Clock Speeds: (1) 2000.00 MHz (2) 2000.00 MHz
           CPU Flags fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush 
           dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc
arch_perfmon pebs bts pni monitor 
           ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm 
Graphics:  Card ATI M52 [Mobility Radeon X1300] | X.Org 1.5.3 | Res
1280x800@59.9hz
           GLX Renderer Mesa DRI R300 20060815 x86/MMX/SSE2 TCL | GLX
Version 1.3 Mesa 7.2
Audio:     Card Intel 82801G (ICH7 Family) High Definition Audio Controller
driver HDA-Intel
           Sound: Advanced Linux Sound Architecture Version 1.0.17
Network:   Card-1 Broadcom NetXtreme BCM5753M Gigabit Ethernet PCI Express
           Card-2 Intel PRO/Wireless 3945ABG [Golan] Network Connection
Disks:     HDD Total Size: 80.0GB (86.8% used) (1)/dev/sda Hitachi HTS54168
80.0GB
Partition: ID:/ size: 9.2G used: 2.8G (32%) ID: swap:/dev/sda7 size: 0.53GB 
Info:      Processes 103 | Uptime 23:37 | Memory 619.2/2026.8MB | Client
Shell | inxi v:0.5.34 
[/normal user]

[root]
# inxi -F
System:    Host seduxbox running  Linux 2.6.27-6.slh.5-sidux-686 i686
Distro sidux 2008-03 Ουρέα - kde-lite - (200809221818) 
CPU:       Dual Core Intel Core2 T7200 cache 4096 KB bmips 7979.88 
           Clock Speeds: (1) 2000.00 MHz (2) 2000.00 MHz
           CPU Flags fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush 
           dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc
arch_perfmon pebs bts pni monitor 
           ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm 
Graphics:  Card ATI M52 [Mobility Radeon X1300] |   | Res 
Audio:     Card Intel 82801G (ICH7 Family) High Definition Audio Controller
driver HDA-Intel
           Sound: Advanced Linux Sound Architecture Version 1.0.17
Network:   Card-1 Broadcom NetXtreme BCM5753M Gigabit Ethernet PCI Express
           Card-2 Intel PRO/Wireless 3945ABG [Golan] Network Connection
Disks:     HDD Total Size: 80.0GB (86.8% used) (1)/dev/sda Hitachi HTS54168
80.0GB
Partition: ID:/ size: 9.2G used: 2.8G (32%) ID: swap:/dev/sda7 size: 0.53GB 
Info:      Processes 104 | Uptime 23:38 | Memory 617.0/2026.8MB | Client
Shell | inxi v:0.5.34
[/root]

What version of the product are you using? On what operating system?

1. inxi v0.5.34
2. sidux 2008-03 ourea-release 32bit (with latest dist-upgrades as of
2008-11-19)
3. xorg-server (1.5.3-1) from debian/experimental
4. mesa (7.2-1) from debian/experimental

Please provide any additional information below.

Keep on the good work!

Original issue reported on code.google.com by sedat.di...@gmail.com on 19 Nov 2008 at 10:25

GoogleCodeExporter commented 9 years ago
This is correct, the cause is this, as root:

#xrandr
Invalid MIT-MAGIC-COOKIE-1 keyCan't open display :0.0

#xdpyinfo
Invalid MIT-MAGIC-COOKIE-1 keyxdpyinfo:  unable to open display ":0.0".

#glxinfo
Invalid MIT-MAGIC-COOKIE-1 keyError: unable to open display :0.0

These are the methods that get_graphics_glx_data(), get_graphics_res_data(), 
and 
get_graphics_x_data() use to get the x data.

So the solution would need to have a work around for case: if root/then use 
alternate method, or get those functions to give output.

If anyone knows a solution, please post it.

Original comment by inxi-...@techpatterns.com on 19 Nov 2008 at 10:32

GoogleCodeExporter commented 9 years ago

Original comment by inxi-...@techpatterns.com on 7 Jan 2009 at 8:39