New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Waiting for qubes-session hanging #1309

Closed
adrelanos opened this Issue Oct 9, 2015 · 11 comments

Comments

Projects
None yet
2 participants
@adrelanos
Member

adrelanos commented Oct 9, 2015

qvm-start sys-whonix hangs at Waiting for qubes-session hanging.... Started happening after merging the 3.0 changes.

After sudo xl console sys-whonix login as user user and manually starting qubes-session-autostart, the following /tmp/Xorg.0.log was created.

[     6.226] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[     6.226] X Protocol Version 11, Revision 0
[     6.226] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[     6.226] Current Operating System: Linux host 3.18.17-6.pvops.qubes.x86_64 #1 SMP Sat Aug 8 21:27:00 UTC 2015 x86_64
[     6.226] Kernel command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH 3 nopat
[     6.226] Build Date: 11 February 2015  12:32:02AM
[     6.226] xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
[     6.226] Current version of pixman: 0.32.6
[     6.226]    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[     6.226] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     6.226] (++) Log file: "/tmp/Xorg.0.log", Time: Fri Oct  9 17:57:05 2015
[     6.228] (++) Using config file: "/etc/X11/xorg-qubes.conf"
[     6.228] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     6.229] (==) ServerLayout "Default Layout"
[     6.229] (**) |-->Screen "Screen0" (0)
[     6.229] (**) |   |-->Monitor "Monitor0"
[     6.229] (**) |   |-->Device "Videocard0"
[     6.229] (**) |-->Input Device "qubesdev"
[     6.229] (==) Automatically adding devices
[     6.229] (==) Automatically enabling devices
[     6.229] (==) Automatically adding GPU devices
[     6.231] (WW) The directory "/usr/share/fonts/X11/misc" does not exist.
[     6.231]    Entry deleted from font path.
[     6.231] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     6.231]    Entry deleted from font path.
[     6.234] (==) FontPath set to:
    /usr/share/fonts/X11/100dpi/:unscaled,
    /usr/share/fonts/X11/75dpi/:unscaled,
    /usr/share/fonts/X11/Type1,
    /usr/share/fonts/X11/100dpi,
    /usr/share/fonts/X11/75dpi,
    built-ins
[     6.234] (==) ModulePath set to "/usr/lib/xorg/modules"
[     6.234] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
[     6.234] (II) Loader magic: 0x7f3c0a4f6d80
[     6.234] (II) Module ABI versions:
[     6.234]    X.Org ANSI C Emulation: 0.4
[     6.234]    X.Org Video Driver: 18.0
[     6.234]    X.Org XInput driver : 21.0
[     6.234]    X.Org Server Extension : 8.0
[     6.234] (II) no primary bus or device found
[     6.234] (II) LoadModule: "glx"
[     6.235] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     6.245] (II) Module glx: vendor="X.Org Foundation"
[     6.245]    compiled for 1.16.4, module version = 1.0.0
[     6.245]    ABI class: X.Org Server Extension, version 8.0
[     6.245] (==) AIGLX enabled
[     6.245] (II) LoadModule: "dummyqbs"
[     6.245] (II) Loading /usr/lib/xorg/modules/drivers/dummyqbs_drv.so
[     6.245] (II) Module dummyqbs: vendor="X.Org Foundation"
[     6.245]    compiled for 1.16.4, module version = 0.3.6
[     6.245]    Module class: X.Org Video Driver
[     6.245]    ABI class: X.Org Video Driver, version 18.0
[     6.245] (II) LoadModule: "qubes"
[     6.246] (II) Loading /usr/lib/xorg/modules/drivers/qubes_drv.so
[     6.246] (II) Module qubes: vendor="X.Org Foundation"
[     6.246]    compiled for 1.16.4, module version = 0.0.1
[     6.246]    Module class: X.Org XInput Driver
[     6.246]    ABI class: X.Org XInput driver, version 21.0
[     6.246] (II) DUMMYQBS: Driver for Dummy chipsets: dummy
[     6.246] (WW) Falling back to old probe method for dummyqbs
[     6.246] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[     6.246] (II) DUMMYQBS(0): Chipset is a DUMMY
[     6.246] (**) DUMMYQBS(0): Depth 24, (--) framebuffer bpp 32
[     6.246] (==) DUMMYQBS(0): RGB weight 888
[     6.246] (==) DUMMYQBS(0): Default visual is TrueColor
[     6.246] (==) DUMMYQBS(0): Using gamma correction (1.0, 1.0, 1.0)
[     6.246] (**) DUMMYQBS(0): VideoRAM: 65536 kByte
[     6.246] (--) DUMMYQBS(0): Max Clock: 230000 kHz
[     6.246] (II) DUMMYQBS(0): Monitor0: Using hsync range of 49.00-50.00 kHz
[     6.246] (II) DUMMYQBS(0): Monitor0: Using vrefresh range of 64.00-65.00 Hz
[     6.246] (II) DUMMYQBS(0): Clock range:  11.00 to 300.00 MHz
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x350" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "320x175" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x400" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "320x200" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "720x400" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "360x200" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x480" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "320x240" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x480" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "320x240" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x480" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "320x240" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x480" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "320x240" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "400x300" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "400x300" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "400x300" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "400x300" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "400x300" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1024x768i" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "512x384i" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1024x768" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "512x384" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1024x768" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "512x384" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1024x768" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "512x384" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1024x768" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "512x384" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1152x864" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "576x432" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1280x960" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x480" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1280x960" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x480" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1280x1024" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x512" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1280x1024" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x512" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1280x1024" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "640x512" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1600x1200" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1600x1200" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1600x1200" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1600x1200" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1600x1200" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "800x600" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1792x1344" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "896x672" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1792x1344" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "896x672" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1856x1392" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "928x696" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1856x1392" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "928x696" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1920x1440" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "960x720" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1920x1440" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "960x720" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "832x624" (vrefresh out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "416x312" (vrefresh out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1152x864" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "576x432" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1152x864" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "576x432" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1152x864" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "576x432" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1152x864" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "576x432" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1152x864" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "576x432" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1152x864" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "576x432" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1360x768" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "680x384" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1360x768" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "680x384" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1400x1050" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "700x525" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1400x1050" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "700x525" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "1400x1050" (hsync out of range)
[     6.246] (II) DUMMYQBS(0): Not using default mode "700x525" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1400x1050" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "700x525" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1440x900" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "720x450" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1600x1024" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "800x512" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1680x1050" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "840x525" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1680x1050" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "840x525" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1680x1050" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "840x525" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1680x1050" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "840x525" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1680x1050" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "840x525" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1920x1080" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "960x540" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1920x1200" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "960x600" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
[     6.247] (II) DUMMYQBS(0): Not using default mode "960x720" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "2048x1536" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1024x768" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1024x768" (hsync out of range)
[     6.247] (II) DUMMYQBS(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
[     6.247] (II) DUMMYQBS(0): Not using default mode "1024x768" (hsync out of range)
[     6.247] (--) DUMMYQBS(0): Virtual size is 1280x768 (pitch 1280)
[     6.247] (**) DUMMYQBS(0): *Mode "QB1280x768": 64.0 MHz, 49.9 kHz, 64.7 Hz
[     6.247] (II) DUMMYQBS(0): Modeline "QB1280x768"x64.7   64.00  1280 1281 1282 1283  768 769 770 771 (49.9 kHz z)
[     6.247] (==) DUMMYQBS(0): DPI set to (96, 96)
[     6.247] (II) Loading sub module "fb"
[     6.247] (II) LoadModule: "fb"
[     6.247] (II) Loading /usr/lib/xorg/modules/libfb.so
[     6.248] (II) Module fb: vendor="X.Org Foundation"
[     6.248]    compiled for 1.16.4, module version = 1.0.0
[     6.248]    ABI class: X.Org ANSI C Emulation, version 0.4
[     6.248] (II) Loading sub module "ramdac"
[     6.248] (II) LoadModule: "ramdac"
[     6.248] (II) Module "ramdac" already built-in
[     6.248] (--) Depth 24 pixmap format is 32 bpp
[     6.249] (II) DUMMYQBS(0): Output DUMMY0 using monitor section Monitor0
[     6.249] (II) DUMMYQBS(0): Output DUMMY0 has no monitor section
[     6.249] (II) DUMMYQBS(0): Created crtc (0x7f3c0b6edfe0) and output DUMMY0 (0x7f3c0b6eeab0)
[     6.249] (II) DUMMYQBS(0): Output DUMMY1 has no monitor section
[     6.249] (II) DUMMYQBS(0): Created crtc (0x7f3c0b6eeeb0) and output DUMMY1 (0x7f3c0b6ef980)
[     6.249] (II) DUMMYQBS(0): Output DUMMY2 has no monitor section
[     6.249] (II) DUMMYQBS(0): Created crtc (0x7f3c0b6efd80) and output DUMMY2 (0x7f3c0b6f0850)
[     6.249] (II) DUMMYQBS(0): Output DUMMY3 has no monitor section
[     6.249] (II) DUMMYQBS(0): Created crtc (0x7f3c0b6f0c50) and output DUMMY3 (0x7f3c0b6f1720)
[     6.249] (II) DUMMYQBS(0): Printing probed modes for output DUMMY0
[     6.249] (II) DUMMYQBS(0): Modeline "QB1280x768"x64.7   64.00  1280 1281 1282 1283  768 769 770 771 (49.9 kHz UzP)
[     6.249] (II) DUMMYQBS(0): EDID for output DUMMY1
[     6.249] (II) DUMMYQBS(0): EDID for output DUMMY2
[     6.249] (II) DUMMYQBS(0): EDID for output DUMMY3
[     6.249] (II) DUMMYQBS(0): Output DUMMY0 connected
[     6.249] (II) DUMMYQBS(0): Output DUMMY1 disconnected
[     6.249] (II) DUMMYQBS(0): Output DUMMY2 disconnected
[     6.249] (II) DUMMYQBS(0): Output DUMMY3 disconnected
[     6.249] (II) DUMMYQBS(0): Using user preference for initial modes
[     6.249] (II) DUMMYQBS(0): Output DUMMY0 using initial mode QB1280x768
[     6.249] (II) DUMMYQBS(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[     6.249] (II) DUMMYQBS(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[     6.249] (II) DUMMYQBS(0): Using 12339 scanlines of offscreen memory 
[     6.249] (==) DUMMYQBS(0): Backing store enabled
[     6.249] (==) DUMMYQBS(0): Silken mouse enabled
[     6.249] (--) RandR disabled
[     6.253] (II) SELinux: Disabled on system
[     6.253] (II) AIGLX: Screen 0 is not DRI2 capable
[     6.253] (EE) AIGLX: reverting to software rendering

Can you make head or tail of it? Interestingly this does not happen for whonix-ws based AppVMs. Only for sys-whonix. So perhaps some missing package?

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 9, 2015

Member

There was missing python-dbus dependency. Fixed package
(qubes-core-agent 3.0.17) landed today in the stable repository.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Oct 9, 2015

There was missing python-dbus dependency. Fixed package
(qubes-core-agent 3.0.17) landed today in the stable repository.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Oct 9, 2015

Member

That package is installed.

Member

adrelanos commented Oct 9, 2015

That package is installed.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 9, 2015

Member

On Fri, Oct 09, 2015 at 11:13:50AM -0700, Patrick Schleizer wrote:

qvm-start sys-whonix hangs at Waiting for qubes-session hanging.... Started happening after merging the 3.0 changes.

After sudo xl console sys-whonix login as user user and manually starting qubes-session-autostart, the following /tmp/Xorg.0.log was created.

Check ~/.xsession-errors.

Can you make head or tail of it? Interestingly this does not happen for whonix-ws based AppVMs. Only for sys-whonix. So perhaps some missing package?

Is it reproducible?

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Oct 9, 2015

On Fri, Oct 09, 2015 at 11:13:50AM -0700, Patrick Schleizer wrote:

qvm-start sys-whonix hangs at Waiting for qubes-session hanging.... Started happening after merging the 3.0 changes.

After sudo xl console sys-whonix login as user user and manually starting qubes-session-autostart, the following /tmp/Xorg.0.log was created.

Check ~/.xsession-errors.

Can you make head or tail of it? Interestingly this does not happen for whonix-ws based AppVMs. Only for sys-whonix. So perhaps some missing package?

Is it reproducible?

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Oct 10, 2015

Member

Always reproducible.

~/.xsession-errors

X.Org X Server 1.16.4
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux host 3.18.17-6.pvops.qubes.x86_64 #1 SMP Sat Aug 8 21:27:00 UTC 2015 x86_64
Kernel command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH 3 nopat
Build Date: 11 February 2015  12:32:02AM
xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
Current version of pixman: 0.32.6
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.0.log", Time: Fri Oct  9 17:57:05 2015
(++) Using config file: "/etc/X11/xorg-qubes.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 492: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed!
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Network is unreachable
/usr/bin/xinit: server error
Member

adrelanos commented Oct 10, 2015

Always reproducible.

~/.xsession-errors

X.Org X Server 1.16.4
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux host 3.18.17-6.pvops.qubes.x86_64 #1 SMP Sat Aug 8 21:27:00 UTC 2015 x86_64
Kernel command line: root=/dev/mapper/dmroot ro nomodeset console=hvc0 rd_NO_PLYMOUTH 3 nopat
Build Date: 11 February 2015  12:32:02AM
xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
Current version of pixman: 0.32.6
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.0.log", Time: Fri Oct  9 17:57:05 2015
(++) Using config file: "/etc/X11/xorg-qubes.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 492: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed!
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Network is unreachable
/usr/bin/xinit: server error
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 10, 2015

Member

On Sat, Oct 10, 2015 at 01:44:03AM -0700, Patrick Schleizer wrote:

Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 492: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed!
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Network is unreachable
/usr/bin/xinit: server error

Quick google shows that it is most likely some filesystem corruption.
Run fsck, verify libraries (does dpkg have an option to verify installed
files using some checksum?).

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Oct 10, 2015

On Sat, Oct 10, 2015 at 01:44:03AM -0700, Patrick Schleizer wrote:

Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 492: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed!
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Network is unreachable
/usr/bin/xinit: server error

Quick google shows that it is most likely some filesystem corruption.
Run fsck, verify libraries (does dpkg have an option to verify installed
files using some checksum?).

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Oct 10, 2015

Member

Marek Marczykowski-Górecki:

On Sat, Oct 10, 2015 at 01:44:03AM -0700, Patrick Schleizer wrote:

Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 492: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed!
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Network is unreachable
/usr/bin/xinit: server error

Quick google shows that it is most likely some filesystem corruption.
Run fsck, verify libraries

Sorry, I haven't found this on google...

How can on boot into emergency mode in an App/Template VM to run fsck in
Qubes?

(does dpkg have an option to verify installed
files using some checksum?)

package: debsums
(sudo) debsums -s

(Btw, debsums is not a security tool.)

(debsums found nothing related.)

Member

adrelanos commented Oct 10, 2015

Marek Marczykowski-Górecki:

On Sat, Oct 10, 2015 at 01:44:03AM -0700, Patrick Schleizer wrote:

Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 492: elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff) == 8' failed!
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Network is unreachable
/usr/bin/xinit: server error

Quick google shows that it is most likely some filesystem corruption.
Run fsck, verify libraries

Sorry, I haven't found this on google...

How can on boot into emergency mode in an App/Template VM to run fsck in
Qubes?

(does dpkg have an option to verify installed
files using some checksum?)

package: debsums
(sudo) debsums -s

(Btw, debsums is not a security tool.)

(debsums found nothing related.)

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 10, 2015

Member

On Sat, Oct 10, 2015 at 08:20:00AM -0700, Patrick Schleizer wrote:

How can on boot into emergency mode in an App/Template VM to run fsck in
Qubes?

Try this:
http://freedesktop.org/wiki/Software/systemd/Debugging/#bootingintorescueoremergencytargets

(does dpkg have an option to verify installed
files using some checksum?)

package: debsums
(sudo) debsums -s

(Btw, debsums is not a security tool.)

(debsums found nothing related.)

Hmm, if that would be about broken library file, it should find
something.
I'm not sure which executable failed here - there is some xinit message
later (so the process is still alive), so probably not this one. Do you
have abrt installed? If so, maybe it logged what crashed?

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Oct 10, 2015

On Sat, Oct 10, 2015 at 08:20:00AM -0700, Patrick Schleizer wrote:

How can on boot into emergency mode in an App/Template VM to run fsck in
Qubes?

Try this:
http://freedesktop.org/wiki/Software/systemd/Debugging/#bootingintorescueoremergencytargets

(does dpkg have an option to verify installed
files using some checksum?)

package: debsums
(sudo) debsums -s

(Btw, debsums is not a security tool.)

(debsums found nothing related.)

Hmm, if that would be about broken library file, it should find
something.
I'm not sure which executable failed here - there is some xinit message
later (so the process is still alive), so probably not this one. Do you
have abrt installed? If so, maybe it logged what crashed?

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Oct 10, 2015

Member

fsck was also clean.

abrt? Debian does not have this? It's a Fedora tool or what do you mean?

Member

adrelanos commented Oct 10, 2015

fsck was also clean.

abrt? Debian does not have this? It's a Fedora tool or what do you mean?

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Oct 10, 2015

Member

I've deleted all templates in the build VM, did "make clean-all" and
recreated the image. Issue vanished. Strange.

Member

adrelanos commented Oct 10, 2015

I've deleted all templates in the build VM, did "make clean-all" and
recreated the image. Issue vanished. Strange.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 10, 2015

Member

On Sat, Oct 10, 2015 at 02:07:47PM -0700, Patrick Schleizer wrote:

abrt? Debian does not have this?

Apparently not, so never mind.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Member

marmarek commented Oct 10, 2015

On Sat, Oct 10, 2015 at 02:07:47PM -0700, Patrick Schleizer wrote:

abrt? Debian does not have this?

Apparently not, so never mind.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

@adrelanos

This comment has been minimized.

Show comment
Hide comment
@adrelanos

adrelanos Oct 10, 2015

Member

Heisenbug.

Member

adrelanos commented Oct 10, 2015

Heisenbug.

@adrelanos adrelanos closed this Oct 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment