| Summary: | ksmserver crashing when /sys empty or not existing | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Stefan Baur <X2Go-ML-1> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugwatch, slavek.banko, X2Go-ML-1 |
| Priority: | P5 | ||
| Version: | R14.0.1 [Trinity] | ||
| Hardware: | amd64 | ||
| OS: | Debian Wheezy | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2540 | ||
Well, I was hoping that testing patch will be quite simple, but when /sys not mounted on my test machine Xorg cannot start :) Therefore patch preparation will be somewhat blindly. If you have a testing/unstable repository for Debian packages, or you can somehow make a *.deb available to me that works with R14.0.2 I can test your patch. Or you could set up a server that has X2Go installed and do what I did, try to run Trinity on a server machine without /sys via X2Go on another machine (where /sys is mounted and X is running). -Stefan I think that I see the exact point where the crash occurs. I prepare patch and we'll see if I guessed it correctly :) Problem should be fixed by commit f4fb3a8e (master), fd96a6c2 (r14.0.x). Packages for test will be soon available in the Preliminary stable builds repository - exactly tdelibs 14.0.3~pre17 or later. If the problem persists, do not hesitate to reopen this bug report. Note: Updated packages are available in Preliminary stable builds repository. You can verify whether the fix was successful. |
Hi. First of all, I can't file/tag this bug the way it should be filed/tagged, as the bugzilla webgui just doesn't offer the proper options. I can only select R14.0.0, R14.0.1, or R14.1.0 - I'm actually using R14.0.2, though. Same goes for the operating system Version: I can't select anything newer than Debian Wheezy, when I'm actually running Debian Jessie. The options are just not there. So whoever is in charge of your bugtracker, please add the appropriate options. The actual bug that I would like to report is as follows: Certen virtualization environments (Namely Linux-VServer, but probably some others as well) leave /sys empty or nonexistent for their guests. When trying to run Trinity in such a guest, ksmserver crashes (SIGSEGV) during session startup and the session fails to start. This is due to attempting an access to /sys/devices/system/cpu: openat(AT_FDCWD, "/sys/devices/system/cpu", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory) --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x30} --- Please make sure that ksmserver handles a missing directory structure gracefully, by simply continuing and pretending it found an empty directory if it doesn't find the directory. mkdir -p /sys/devices/system/cpu is a confirmed workaround, but it really should be fixed on your end. Thank You. Kind Regards, Stefan Baur