User avatar
dcj123
Posts: 50
Joined: Tue Jan 29, 2013 3:59 pm

Midori & uzbl both crash Xorg randomly

Wed Mar 27, 2013 3:01 pm

Hello,

I am using openbox with tint2 and conky and every web browser I test leads to Xorg crashes after a while, usually within five minutes. My raspberry pi is overclocked, usually at 900 Mhz, but the problem remains after setting the clock back down to 700 Mhz so I am not sure thats an issue. Unless something in Xorg has become corrupt data wise and if I so I don't mind trying a clean install.

The only thing I could think of that might be helpful is my Xorg log file,

Code: Select all

[   365.384] 
X.Org X Server 1.14.0
Release Date: 2013-03-05
[   365.397] X Protocol Version 11, Revision 0
[   365.402] Build Operating System: Linux 3.2.34-1-FARM armv6l 
[   365.406] Current Operating System: Linux RaspPI 3.6.11-8-ARCH+ #1 PREEMPT Sat Mar 9 00:38:58 UTC 2013 armv6l
[   365.407] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1680 bcm2708_fb.fbheight=1050 bcm2708.boardrev=0xf bcm2708.serial=0x6aba24f7 smsc95xx.macaddr=B8:27:EB:BA:24:F7 sdhci-bcm2708.emmc_clock_freq=100000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  sdhci-bcm2708.enable_llm=1 sdhci-bcm2708.sync_after_dma=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 loglevel=2 root=/dev/mmcblk0p2 init=/bin/systemd rootfstype=ext4 rootwait
[   365.427] Build Date: 19 March 2013  12:22:42AM
[   365.432]  
[   365.437] Current version of pixman: 0.28.2
[   365.447] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   365.448] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   365.470] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 23 16:27:44 2013
[   365.477] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   365.478] (==) No Layout section.  Using the first Screen section.
[   365.478] (==) No screen section available. Using defaults.
[   365.478] (**) |-->Screen "Default Screen Section" (0)
[   365.478] (**) |   |-->Monitor "<default monitor>"
[   365.479] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   365.480] (==) Automatically adding devices
[   365.480] (==) Automatically enabling devices
[   365.480] (==) Automatically adding GPU devices
[   365.480] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[   365.480] 	Entry deleted from font path.
[   365.480] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   365.481] 	Entry deleted from font path.
[   365.481] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[   365.481] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   365.481] 	Entry deleted from font path.
[   365.481] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   365.481] (==) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/Type1/
[   365.481] (==) ModulePath set to "/usr/lib/xorg/modules"
[   365.481] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   365.481] (II) Loader magic: 0x1c0ab0
[   365.481] (II) Module ABI versions:
[   365.482] 	X.Org ANSI C Emulation: 0.4
[   365.482] 	X.Org Video Driver: 14.1
[   365.482] 	X.Org XInput driver : 19.1
[   365.482] 	X.Org Server Extension : 7.0
[   365.488] Initializing built-in extension Generic Event Extension
[   365.494] Initializing built-in extension SHAPE
[   365.499] Initializing built-in extension MIT-SHM
[   365.505] Initializing built-in extension XInputExtension
[   365.511] Initializing built-in extension XTEST
[   365.516] Initializing built-in extension BIG-REQUESTS
[   365.522] Initializing built-in extension SYNC
[   365.528] Initializing built-in extension XKEYBOARD
[   365.533] Initializing built-in extension XC-MISC
[   365.539] Initializing built-in extension SECURITY
[   365.544] Initializing built-in extension XINERAMA
[   365.550] Initializing built-in extension XFIXES
[   365.555] Initializing built-in extension RENDER
[   365.561] Initializing built-in extension RANDR
[   365.566] Initializing built-in extension COMPOSITE
[   365.571] Initializing built-in extension DAMAGE
[   365.576] Initializing built-in extension MIT-SCREEN-SAVER
[   365.581] Initializing built-in extension DOUBLE-BUFFER
[   365.586] Initializing built-in extension RECORD
[   365.590] Initializing built-in extension DPMS
[   365.595] Initializing built-in extension X-Resource
[   365.600] Initializing built-in extension XVideo
[   365.604] Initializing built-in extension XVideo-MotionCompensation
[   365.609] Initializing built-in extension XFree86-VidModeExtension
[   365.613] Initializing built-in extension XFree86-DGA
[   365.618] Initializing built-in extension XFree86-DRI
[   365.622] Initializing built-in extension DRI2
[   365.622] (II) LoadModule: "glx"
[   365.624] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   365.625] (II) Module glx: vendor="X.Org Foundation"
[   365.625] 	compiled for 1.14.0, module version = 1.0.0
[   365.625] 	ABI class: X.Org Server Extension, version 7.0
[   365.625] (==) AIGLX enabled
[   365.630] Loading extension GLX
[   365.630] (==) Matched modesetting as autoconfigured driver 0
[   365.631] (==) Matched fbdev as autoconfigured driver 1
[   365.631] (==) Assigned the driver to the xf86ConfigLayout
[   365.631] (II) LoadModule: "modesetting"
[   365.633] (WW) Warning, couldn't open module modesetting
[   365.633] (II) UnloadModule: "modesetting"
[   365.633] (II) Unloading modesetting
[   365.633] (EE) Failed to load module "modesetting" (module does not exist, 0)
[   365.633] (II) LoadModule: "fbdev"
[   365.634] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[   365.635] (II) Module fbdev: vendor="X.Org Foundation"
[   365.635] 	compiled for 1.14.0, module version = 0.4.3
[   365.635] 	Module class: X.Org Video Driver
[   365.635] 	ABI class: X.Org Video Driver, version 14.1
[   365.635] (II) FBDEV: driver for framebuffer: fbdev
[   365.636] (++) using VT number 1

[   365.636] (WW) Falling back to old probe method for fbdev
[   365.636] (II) Loading sub module "fbdevhw"
[   365.636] (II) LoadModule: "fbdevhw"
[   365.637] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[   365.638] (II) Module fbdevhw: vendor="X.Org Foundation"
[   365.638] 	compiled for 1.14.0, module version = 0.0.2
[   365.638] 	ABI class: X.Org Video Driver, version 14.1
[   365.638] (II) FBDEV(0): using default device
[   365.639] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   365.639] (II) FBDEV(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 16/16
[   365.639] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
[   365.639] (==) FBDEV(0): RGB weight 565
[   365.639] (==) FBDEV(0): Default visual is TrueColor
[   365.639] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[   365.640] (II) FBDEV(0): hardware: BCM2708 FB (video memory: 3445kB)
[   365.640] (II) FBDEV(0): checking modes against framebuffer device...
[   365.640] (II) FBDEV(0): checking modes against monitor...
[   365.640] (--) FBDEV(0): Virtual size is 1680x1050 (pitch 1680)
[   365.640] (**) FBDEV(0):  Built-in mode "current"
[   365.641] (==) FBDEV(0): DPI set to (96, 96)
[   365.641] (II) Loading sub module "fb"
[   365.641] (II) LoadModule: "fb"
[   365.641] (II) Loading /usr/lib/xorg/modules/libfb.so
[   365.643] (II) Module fb: vendor="X.Org Foundation"
[   365.643] 	compiled for 1.14.0, module version = 1.0.0
[   365.644] 	ABI class: X.Org ANSI C Emulation, version 0.4
[   365.644] (**) FBDEV(0): using shadow framebuffer
[   365.644] (II) Loading sub module "shadow"
[   365.644] (II) LoadModule: "shadow"
[   365.645] (II) Loading /usr/lib/xorg/modules/libshadow.so
[   365.646] (II) Module shadow: vendor="X.Org Foundation"
[   365.646] 	compiled for 1.14.0, module version = 1.1.0
[   365.646] 	ABI class: X.Org ANSI C Emulation, version 0.4
[   365.647] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
[   365.648] (==) FBDEV(0): Backing store disabled
[   365.649] (==) FBDEV(0): DPMS enabled
[   365.649] (==) RandR enabled
[   365.719] (II) AIGLX: Screen 0 is not DRI2 capable
[   365.719] (II) AIGLX: Screen 0 is not DRI capable
[   365.762] (II) AIGLX: Loaded and initialized swrast
[   365.762] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[   366.217] (II) config/udev: Adding input device Alps Electric M2452 (/dev/input/event0)
[   366.217] (**) Alps Electric M2452: Applying InputClass "evdev keyboard catchall"
[   366.217] (II) LoadModule: "evdev"
[   366.219] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[   366.220] (II) Module evdev: vendor="X.Org Foundation"
[   366.220] 	compiled for 1.14.0, module version = 2.7.3
[   366.220] 	Module class: X.Org XInput Driver
[   366.221] 	ABI class: X.Org XInput driver, version 19.1
[   366.221] (II) Using input driver 'evdev' for 'Alps Electric M2452'
[   366.221] (**) Alps Electric M2452: always reports core events
[   366.221] (**) evdev: Alps Electric M2452: Device: "/dev/input/event0"
[   366.222] (--) evdev: Alps Electric M2452: Vendor 0x5ac Product 0x201
[   366.222] (--) evdev: Alps Electric M2452: Found keys
[   366.222] (II) evdev: Alps Electric M2452: Configuring as keyboard
[   366.222] (**) Option "config_info" "udev:/sys/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3.1/1-1.3.3.1:1.0/input/input0/event0"
[   366.223] (II) XINPUT: Adding extended input device "Alps Electric M2452" (type: KEYBOARD, id 6)
[   366.223] (**) Option "xkb_rules" "evdev"
[   366.223] (**) Option "xkb_model" "evdev"
[   366.223] (**) Option "xkb_layout" "us"
[   366.446] (II) config/udev: Adding input device A4Tech PS/2+USB Mouse (/dev/input/event1)
[   366.446] (**) A4Tech PS/2+USB Mouse: Applying InputClass "evdev pointer catchall"
[   366.446] (II) Using input driver 'evdev' for 'A4Tech PS/2+USB Mouse'
[   366.447] (**) A4Tech PS/2+USB Mouse: always reports core events
[   366.447] (**) evdev: A4Tech PS/2+USB Mouse: Device: "/dev/input/event1"
[   366.447] (--) evdev: A4Tech PS/2+USB Mouse: Vendor 0x9da Product 0x6
[   366.447] (--) evdev: A4Tech PS/2+USB Mouse: Found 10 mouse buttons
[   366.447] (--) evdev: A4Tech PS/2+USB Mouse: Found scroll wheel(s)
[   366.447] (--) evdev: A4Tech PS/2+USB Mouse: Found relative axes
[   366.448] (--) evdev: A4Tech PS/2+USB Mouse: Found x and y relative axes
[   366.448] (II) evdev: A4Tech PS/2+USB Mouse: Configuring as mouse
[   366.448] (II) evdev: A4Tech PS/2+USB Mouse: Adding scrollwheel support
[   366.448] (**) evdev: A4Tech PS/2+USB Mouse: YAxisMapping: buttons 4 and 5
[   366.448] (**) evdev: A4Tech PS/2+USB Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   366.448] (**) Option "config_info" "udev:/sys/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0/input/input1/event1"
[   366.449] (II) XINPUT: Adding extended input device "A4Tech PS/2+USB Mouse" (type: MOUSE, id 7)
[   366.449] (II) evdev: A4Tech PS/2+USB Mouse: initialized for relative axes.
[   366.450] (**) A4Tech PS/2+USB Mouse: (accel) keeping acceleration scheme 1
[   366.451] (**) A4Tech PS/2+USB Mouse: (accel) acceleration profile 0
[   366.451] (**) A4Tech PS/2+USB Mouse: (accel) acceleration factor: 2.000
[   366.451] (**) A4Tech PS/2+USB Mouse: (accel) acceleration threshold: 4
[   366.453] (II) config/udev: Adding input device A4Tech PS/2+USB Mouse (/dev/input/mouse0)
[   366.453] (II) No input driver specified, ignoring this device.
[   366.454] (II) This device may have been added with another device file.
[   366.486] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
[   440.982] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
[   441.240] (EE) FBDEV(0): FBIOBLANK: Operation not permitted
(EE) 
(EE) Backtrace:
(EE) 
(EE) Segmentation fault at address 0x4
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:502 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or ErrorFSigSafe().
The offending log format message is:

Fatal server error:

(EE) 
(EE) Backtrace:
(EE) 

Fatal server error:
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:502 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or ErrorFSigSafe().
The offending log format message is:
Caught signal %d (%s). Server aborting

(EE) 
(EE) Backtrace:
(EE) 
Caught signal 11 (Segmentation fault). Server aborting
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:502 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or ErrorFSigSafe().
The offending log format message is:


(EE) 
(EE) Backtrace:
(EE) 
(WW) Warned 3 times about sigsafe logging. Will be quiet now.

(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
Server terminated with error (1). Closing log file.
Ideas? Cause I am out of them.
Last edited by dcj123 on Wed Mar 27, 2013 4:28 pm, edited 1 time in total.


antiloquax
Posts: 406
Joined: Sun Nov 20, 2011 11:37 am
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Wed Mar 27, 2013 4:30 pm

I'm having this problem too. :(

I've been trying uzbl and other wms (evilwm and dwm).
At least I know they are not to blame.

User avatar
dcj123
Posts: 50
Joined: Tue Jan 29, 2013 3:59 pm

Re: Midori & uzbl both crash Xorg randomly

Wed Mar 27, 2013 7:48 pm

I take it there is no fix as the fix grimpirate post is for x86 and intel based graphics.
antiloquax wrote:I'm having this problem too. :(

I've been trying uzbl and other wms (evilwm and dwm).
At least I know they are not to blame.
No they are not to blame, I've tried Openbox and spectrwm plus the ones you mentioned. uzbl is faster than Midori in my experience on the Pi, I highly recommend it if you get it working.

antiloquax
Posts: 406
Joined: Sun Nov 20, 2011 11:37 am
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Wed Mar 27, 2013 7:59 pm

Yes, I like uzbl and it works fine (until X crashes).

I'm hoping there'll be an update for X soon, in the meantime, I have no idea how to fix it. I suppose some of the xorg.conf things mentioned in the thread pepedog linked to may do the trick, but I haven't got around to trying.

vilitux
Posts: 3
Joined: Fri Mar 29, 2013 9:22 am

Re: Midori & uzbl both crash Xorg randomly

Fri Mar 29, 2013 9:30 am

Same problem unfortunately, happens with pretty much everything here.. browsers, terminals, etc.
I guess either wait for an update or rebuild from old sources @ http://cgit.freedesktop.org/xorg/xserver/.

sdjf
Posts: 1395
Joined: Fri Mar 16, 2012 5:20 am
Location: California
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Fri Mar 29, 2013 3:33 pm

I am studying my Xorg log files for X Server 1.13.1 and see no segmentation faults in them at all. I have stopped using my vncserver totally for now, though, because of crashes for other reasons - which may or may not be related - since the connection to my PDA kept crashing due to kevents being dropped and this happened more when I was using vnc vs. just command line.

Anyhow, if anyone would rather get the old already built official packages for 1.13.1 instead of building them and any dependencies they think could be culprits, I could put them somewhere, but bandwidth could be an issue for my own website.

xorg-server-1.13.1-1-armv6h.pkg.tar.xz
xorg-server-common-1.13.1-1-armv6h.pkg.tar.xz

I have no idea if these will run properly on the current version of the kernel, I am still running the 3.6.11-2 kernel from 31 Dec 2012.

Would the Xorg log files be showing if it was the server vs. a dependency causing the seg faults?

Also, I note in the log above that it was a Mouse that seemed to be an issue, is everyone having the issue also using a Mouse, or does the seg fault occur with other input devices as well? I am using a usb keyboard and no mouse.
FORUM TIP: To view someone's posting history, sign in, click on their user name, then on "Search User's Posts." || Running ArchLinuxArm on Model 2B and 512MB Model B

vilitux
Posts: 3
Joined: Fri Mar 29, 2013 9:22 am

Re: Midori & uzbl both crash Xorg randomly

Fri Mar 29, 2013 4:15 pm

To get back on my other post. Managed to build the older version packages.
Besides the packages:
xorg-server-1.13.1-1
xorg-server-common-1.13.1-1
I also had to rebuild:
xf86-video-fbdev-0.4.3-2
xf86-input-evdev-2.7.3-2

Took pretty much the whole day, building those packages on the Pi is not very speedy!

@sdjf:
Using a USB wireless keyboard with integrated mousepad. Grabbed the 3.6.y kernel from github https://github.com/raspberrypi/linux and seems to be working okay now.

User avatar
dcj123
Posts: 50
Joined: Tue Jan 29, 2013 3:59 pm

Re: Midori & uzbl both crash Xorg randomly

Sat Mar 30, 2013 4:10 pm

vilitux wrote:To get back on my other post. Managed to build the older version packages.
Besides the packages:
xorg-server-1.13.1-1
xorg-server-common-1.13.1-1
I also had to rebuild:
xf86-video-fbdev-0.4.3-2
xf86-input-evdev-2.7.3-2

Took pretty much the whole day, building those packages on the Pi is not very speedy!
Do you know if these versions would work on the newest kernel (3.6.11-9), might try it. Though it might be easier to wait for another version release. I don't wanna downgrade my kernel because the last update fixed some stuff for me, in particular, omxplayer giving a blank screen.

I am using a GE dual scroll usb optical mouse, model number HO97769; it works to my knowledge or worked before. Unfortunately its the only usb mouse I have but I could see if uzbl crashes without it and report back.

pepedog
Posts: 1043
Joined: Fri Oct 07, 2011 9:55 am

Re: Midori & uzbl both crash Xorg randomly

Sat Mar 30, 2013 5:00 pm

Kernel version hasn't anything to do with it.
If you get older versions look up how to exclude xorg-server (and the rest) from being updated with pacman -Syu
It might be possible (if not new install) older files can be picked up with
pacman -U /var/cache/pacman/pkg/<pkgname>
The tab key comes in handy here

sdjf
Posts: 1395
Joined: Fri Mar 16, 2012 5:20 am
Location: California
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Sun Mar 31, 2013 3:40 am

man page for pacman lists an --ignore <package> option and --ignoregroup <group> option.

if anyone needs the older packages and does not have them in their cache, PM me. I have them if you do not want to rebuild the ones listed by vilitux.
FORUM TIP: To view someone's posting history, sign in, click on their user name, then on "Search User's Posts." || Running ArchLinuxArm on Model 2B and 512MB Model B

dagnusmaximus
Posts: 3
Joined: Sun Mar 31, 2013 5:23 am

Re: Midori & uzbl both crash Xorg randomly

Sun Mar 31, 2013 5:30 am

sdjf wrote:man page for pacman lists an --ignore <package> option and --ignoregroup <group> option.

if anyone needs the older packages and does not have them in their cache, PM me. I have them if you do not want to rebuild the ones listed by vilitux.
For some reason I can't figure out how to PM. Can you send me links to the older packages? I have been trying for nearly 24 hours but with no luck.

sdjf
Posts: 1395
Joined: Fri Mar 16, 2012 5:20 am
Location: California
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Sun Mar 31, 2013 3:10 pm

To PM a board member, click on their username, and then there should be a link to "Send private message." That works unless the user has set their profile to not get PMs.

And yeah, dagnusmaximus, let me test links first and will PM you.

I uploaded the files the other day and they have disappeared from my server, am working on it. And found them!

EDIT: PM sent, to receive PMs, click on your own user name near the logout button. then click on Inbox or on Private Messages.
FORUM TIP: To view someone's posting history, sign in, click on their user name, then on "Search User's Posts." || Running ArchLinuxArm on Model 2B and 512MB Model B

dagnusmaximus
Posts: 3
Joined: Sun Mar 31, 2013 5:23 am

Re: Midori & uzbl both crash Xorg randomly

Sun Mar 31, 2013 5:02 pm

You sir, are a life-saver(time-saver). Thank you very much!

sdjf
Posts: 1395
Joined: Fri Mar 16, 2012 5:20 am
Location: California
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Sun Mar 31, 2013 5:49 pm

You are very welcome, we are all in the same soup together, and give help when we can.
FORUM TIP: To view someone's posting history, sign in, click on their user name, then on "Search User's Posts." || Running ArchLinuxArm on Model 2B and 512MB Model B

Oppression
Posts: 1
Joined: Sat Mar 30, 2013 8:06 am
Location: Gold Coast, Australia

Re: Midori & uzbl both crash Xorg randomly

Mon Apr 01, 2013 7:38 am

I am having the same issue, figured it was something I screwed up so I tried wiping the SD and starting again from scratch with obviously the same results. I cannot PM sdjf as I am too green so the forum won't let me.
If it isn't too much trouble could I get the link to the precompiled packages PM'd to me please. I tried building 1.12....... from AUR but there were too many missing dependencies not available on AUR for it to work out.

Thanks

pepedog
Posts: 1043
Joined: Fri Oct 07, 2011 9:55 am

Re: Midori & uzbl both crash Xorg randomly

Mon Apr 01, 2013 5:27 pm

I put the files here until this is fixed
http://myplugbox.com/pirescue/

User avatar
gubisan
Posts: 1
Joined: Fri Apr 05, 2013 5:02 am
Location: Nanchang, Jiangxi, China
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Fri Apr 05, 2013 5:36 am

I registered at this awesome board just to let you awesome guys know that you also saved me and my Raspberry from these X crashes. Thank you for compiling and publicly hosting the packages to revert X! You have saved me days of trouble, messing around with old versions of X and probably breaking the entire installation in the process. Thank you!

Before I came across this thread and reverted X using the files you provided, X used to crash after a few minutes every time I started it. The only error in the logs was the somewhat popular "FBDEV(0): FBIOBLANK: Operation not permitted".

I was running i3 and DWM and then decided to give Blackbox a try. In Blackbox, I noticed that the crashes only seemed to occur while I was resizing windows. So, interestingly, Blackbox appeared to be the most stable solution, probably because it is not a tiling window manager and therefore does not have to resize windows as often as i3 and DWM. In fact, if I specifically avoided resizing windows, Blackbox would appear to run stable. Closing windows also seemed to crash X, but by far not as often as resizing did.
Did. Past tense.

In any case, I put all pertinent X packages on hold and your package files somewhere safe. Thank you!

User avatar
graysky
Posts: 93
Joined: Fri Apr 05, 2013 11:43 am
Location: /run/user/1000
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Fri Apr 05, 2013 11:54 am

If you have indeed tracked this back to the specific packages mentioned, please open a bug report with Arch ARM! They do not have the flyspray system that Arch official does but they are using github:

https://github.com/archlinuxarm/PKGBUILDs/issues

kalee
Posts: 1
Joined: Tue Dec 04, 2012 2:01 am
Location: Castle Rock, Colorado

Re: Midori & uzbl both crash Xorg randomly

Sun Apr 07, 2013 4:09 pm

pepedog wrote:I put the files here until this is fixed
http://myplugbox.com/pirescue/
Thank you for the work you put into this and sharing with the community. This fixed the problem right up for me!


Arch Linux - Model B Raspberry Pi

User avatar
graysky
Posts: 93
Joined: Fri Apr 05, 2013 11:43 am
Location: /run/user/1000
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Sun Apr 07, 2013 4:39 pm

graysky wrote:If you have indeed tracked this back to the specific packages mentioned, please open a bug report with Arch ARM! They do not have the flyspray system that Arch official does but they are using github...
https://github.com/archlinuxarm/PKGBUILDs/issues/446

I would invite others experiencing problems to provide some details to help the devs.

tb01110100
Posts: 13
Joined: Fri Jan 04, 2013 2:42 pm
Location: Indianapolis

Re: Midori & uzbl both crash Xorg randomly

Mon Apr 08, 2013 11:45 pm

I have the same problem with AwesomeWM. If I attempt to do to much, regardless the application, the screen blanks and throws me back to SLiM. It doesn't take much work for this to happen. I really hope that Xorg patches this soon.
Arch Linux: Some assembly required.

zyx
Posts: 4
Joined: Fri Apr 12, 2013 2:22 am

Re: Midori & uzbl both crash Xorg randomly

Sat Apr 13, 2013 3:06 am

pepedog wrote:I put the files here until this is fixed
http://myplugbox.com/pirescue/
thank you for this! I was just about to re-install Arch until I found this post!

royleith
Posts: 25
Joined: Sun Jul 01, 2012 2:39 pm

Re: Midori & uzbl both crash Xorg randomly

Sat Apr 13, 2013 2:47 pm

Using xfce4 and having similar problems. Some apps work for a while, but xorg usually crashes eventually.

Just changing the window size of Midori is enough to crash xorg.

BTW, Midori is missing lots of its bits such as bookmarks. The reason is that no .midori folder is created in the home directories on installation or first run. Adding the folder restores Midori functionality - until it crashes!

Roy Leith

sdjf
Posts: 1395
Joined: Fri Mar 16, 2012 5:20 am
Location: California
Contact: Website

Re: Midori & uzbl both crash Xorg randomly

Mon Apr 15, 2013 12:01 am

Roy,

Did you try downgrading the xorg packages that are causing these problems? Pepedog put them on his site, link earlier in this thread.

I am suspicious there may be more packages related to this, though, although I am not using X at all right now. It always was too intense for me to use VNC so sticking with commandline right now with my headless server, but I do watch the Xorg stuff as I expect to go back to using it.

My suspicions come because there are issues with updating mesa that involve a lot of applications, and they use xorg stuff.
FORUM TIP: To view someone's posting history, sign in, click on their user name, then on "Search User's Posts." || Running ArchLinuxArm on Model 2B and 512MB Model B

Return to “Arch”