https://bugzilla.novell.com/show_bug.cgi?id=721676
https://bugzilla.novell.com/show_bug.cgi?id=721676#c17
--- Comment #17 from David Martin
(In reply to comment #14)
On the other hand all installs since build 315 and later stop at: "error: can't create transaction lock on /var/lib/rpm/.rpm.lock (No such file or directory)" at which point the installation hangs. /home only has /lost+found and nothing
That is not the cause of the failed installation.
In other words: all installs that I performed on my PC from build 315 on stop at "transaction lock"... I was illustrating the only events that made themselves visible. Surely someone with familiarity with the code and scripts would look for completed events that may lead to the visible ones.
Aside from the logs that are generated is there a trace that can be turned on to indicate which lines of code from which executable is issuing which messages?
Yes, either check vt8 (switch via alt+f8) or /var/log/Xorg.0.log for a backtrace indicating a segfault in the evdev driver. That is the likely cause of this report and a number of other potential dupes of bug #720571.
No. I am talking about a trace similar to what compilers offer. A check into the /var/log of the involved partitions show NO Xorg*.* none. If you look at the ls -l /r5/var/log/* in comment 14 you will see that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.