xtrs loops after opening Window

Bug #97476 reported by Ralf Folkerts
6
Affects Status Importance Assigned to Milestone
xtrs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xtrs

Please note, this happened with Kubuntu 7.04/Beta!

After installation of xtrs, when it's being started it opens it's Window and then loops, i.e. it won't "boot" into the ROM-Image.

Step by step: Install xtrs, then start. I tried with and w/o specifiying a ROM-Image (I also use xtrs on FreeBSD and Gentoo and copied to xtrsrom4p.hex over to the Kubuntu-machine in case the compiled-in-Image was broken (i.e. start with "xtrs -romfile /home/ralf/xtrsrom4p -model 4p"). However , just after displaying it's Window it loops.

I also tried to compile my own xtrs, both with and w/o built-in ROM-Images; however, I get the same Results.

When watching the process with strace it loops somewhere around reading the /tmp/.X11-unix/X0-Socket..

connect(3, {sa_family=AF_FILE, path="/tmp/.X11-unix/X0"}, 110) = 0
getpeername(3, {sa_family=AF_FILE, path="/tmp/.X11-unix/X0"}, [20]) = 0
uname({sys="Linux", node="flounder", ...}) = 0
access("/home/ralf/.Xauthority", R_OK) = 0
open("/home/ralf/.Xauthority", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=163, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7
f46000
read(4, "\0\0\0\4\n\0\0n\0\0010\0\22MIT-MAGIC-COOKIE-1\0"..., 4096) = 163
read(4, "", 4096) = 0
close(4) = 0
munmap(0xb7f46000, 4096) = 0
fcntl64(3, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
select(4, [3], [3], NULL, NULL) = 1 (out [3])
writev(3, [{"l\0\v\0\0\0\22\0\20\0", 10}, {"\0\0", 2}, {"MIT-MAGIC-COOKIE-1", 18
}, {"\0\0", 2}, {"\201\354;U\304\273\177\312\264\3222Jx\272\300>", 16}, {"", 0}]
, 6) = 48
read(3, "\1\0\v\0\0\0\231\0", 8) = 8
read(3, "\300*/\4\0\0@\4\377\377\37\0\0\1\0\0\24\0\377\377\1\7\0"..., 612) = 612

[...]

sigreturn() = ? (mask now [])
read(3, 0x821504c, 4096) = ? ERESTARTSYS (To be restarted)
--- SIGALRM (Alarm clock) @ 0 (0) ---
gettimeofday({1175099063, 502315}, NULL) = 0
setitimer(ITIMER_REAL, {it_interval={0, 25000}, it_value={0, 22685}}, NULL) = 0
sigreturn() = ? (mask now [])
read(3, 0x821504c, 4096) = ? ERESTARTSYS (To be restarted)
--- SIGALRM (Alarm clock) @ 0 (0) ---
gettimeofday({1175099063, 533385}, NULL) = 0
setitimer(ITIMER_REAL, {it_interval={0, 25000}, it_value={0, 16615}}, NULL) = 0
sigreturn() = ? (mask now [])
read(3, 0x821504c, 4096) = ? ERESTARTSYS (To be restarted)
--- SIGALRM (Alarm clock) @ 0 (0) ---
gettimeofday({1175099063, 554218}, NULL) = 0
setitimer(ITIMER_REAL, {it_interval={0, 25000}, it_value={0, 20782}}, NULL) = 0
sigreturn() = ? (mask now [])

Would be great if anyone had a hint/solution. However, I know the 7.04 is BETA and so it's just
a "nice to have" re. Priority :-)

Cheers & thanks!
_ralf_

Revision history for this message
Ralf Folkerts (ralf-folkerts) wrote :

Pls. note: After todays (2007-04-03, ~18:00h UTC) xtrs seems to work again! xtrs was not part of the Update but doesn't loop any longer but boots correcly into the (command-line supplied disk). As xtrs did not work yesterday but does today and as xtrs was not updated today it must have been somthing outside of xtrs.

As I cannot change the status, pls. set this to "Fixed"!

Cheers!

Daniel T Chen (crimsun)
Changed in xtrs:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.