Version: (using KDE KDE 3.1.4) Installed from: Debian testing/unstable Packages How's that for a bug title ? ;) Anyway, this is basically a forward of Debian bug report #219648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=219648. I hope you know how to find the cause, thanks. Of course, please do not forget to CC the original reporter if you ask for more information. cheers domi From: Matthias Urlichs <smurf@debian.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: kstars: no display on PPC Date: Fri, 07 Nov 2003 21:56:45 +0100 Package: kstars Version: 4:3.1.4-1 Severity: important -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 kstars shows an empty sky. The lower-right corner says 2147483648'-2147483648" which looks rather suspicious. Big/little-endian problem? (It works on i386... I don't have any other big-endian archs to test on.) - -- System Information: Debian Release: testing/unstable Architecture: powerpc Kernel: Linux linux 2.6.0-test7-smurf5 #61 Fri Oct 10 01:13:52 CEST 2003 ppc Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 Versions of packages kstars depends on: ii kdelibs4 4:3.1.4-2 KDE core libraries ii libart-2.0-2 2.3.16-1 Library of functions for 2D graphi ii libaudio2 1.6-6 The Network Audio System (NAS). (s ii libc6 2.3.2-9 GNU C Library: Shared libraries an ii libfam0c102 2.6.10-4 client library to control the FAM ii libfontconfig1 2.2.1-8 generic font configuration library ii libfreetype6 2.1.5-3 FreeType 2 font engine, shared lib ii libgcc1 1:3.3.2-3 GCC support library ii libpng12-0 1.2.5.0-4 PNG library - runtime ii libqt3c102-mt 3:3.2.1-6 Qt GUI Library (Threaded runtime v ii libstdc++5 1:3.3.2-3 The GNU Standard C++ Library v3 ii libxcursor1 1.0.2-2 X Cursor management library ii libxft2 2.1.2-4 FreeType-based font drawing librar ii libxrender1 0.8.3-4 X Rendering Extension client libra ii xlibmesa3-gl [libgl1] 4.2.1-13 Mesa 3D graphics library [XFree86] ii xlibs 4.2.1-13 X Window System client libraries ii zlib1g 1:1.1.4-16 compression library - runtime
Subject: Re: New: Empty Sky on PPC Hello, We generally prefer bug reports against more recent development code, since this problem may have already been fixed. However, since you describe a pretty serious problem, I am still very interested in tracking this down. We've had similar bug reports (e.g., #64827, #67299) on i386, and I know of people successfully using KStars on PPC, so I don't think this is an endian issue. In past cases, the behavior you are describing usually results from the focus position getting assigned an undefined position in the sky. Do you get this problem only under certain circumstances, or all the time? What happens if you try to change your geographic location, or change the focus position with one of the n,s,e,w,z,0-9 keys ? If you quit KStars while it is in this undefined state, what do the "FocusRA" and "FocusDec" entries look like in your $KDEHOME/share/config/kstarsrc file? If they are nonsense, what happens when you delete/rename that file and start again? Thanks in advance for your continued help, Jason On Sunday 07 December 2003 05:03 pm, you wrote: > kstars shows an empty sky. The lower-right corner says > > 2147483648'-2147483648" > > which looks rather suspicious. Big/little-endian problem? (It works on > i386... I don't have any other big-endian archs to test on.) >
Subject: Re: New: Empty Sky on PPC Hello, > Sorry -- I don't know where uptodate snapshots for Debian/PPC are > available and I don't have the resources to compile KDE myself -- > not enough disk space. :-/ > FYI, you can compile latest KStars without compiling all of KDE...if interested, I can tell you how. > All the time. > Bummer :( > nsew and geo don't change anything. > > 0-9 return KStars to normal operation. Thank you. > That's pretty interesting. Almost as if it can focus on a named object, but not on blank parts fo the sky. What happens if you do "Ctrl+F" to bring up the Find Object window when it is in the undefined state, and select a named object from the list? Does that also fix it? Once it is "fixed", does it remain ok, or does it ever go back to the undefined state? When you get "nan" for FocusRA and FocusDec, are any of the other values in kstarsrc obviously nonsense? > So it seems that KStars just gets confused about whatever it's supposed > to display on startup. > Yeah, looks that way. I'm at a loss trying to understand what it's problem is, but I'll think about it a while. > (On a totally unrelated note, why does the label of _every_ toggle > button include the word 'toggle'? It takes up too much space on the > toolbar.) > An untested usability issue; none of us on the kstars team put text on the toolbar buttons, so we didn't appreciate the problem. Thanks for the report; if you want to make sure we get it fixed after the strings freeze thaws, please file a report at bugs.kde.org. thanks for the further information; I may contact you again if/when I think of something else to try. regards, Jason
Subject: Re: New: Empty Sky on PPC Hi Jason, > FYI, you can compile latest KStars without compiling all of KDE...if > interested, I can tell you how. > Please do. > That's pretty interesting. Almost as if it can focus on a named object, but > not on blank parts fo the sky. What happens if you do "Ctrl+F" to bring up > the Find Object window when it is in the undefined state, and select a named > object from the list? Does that also fix it? Once it is "fixed", does it > remain ok, or does it ever go back to the undefined state? > ^f does the same as 0..9, i.e. fixes the problem. > When you get "nan" for FocusRA and FocusDec, are any of the other values in > kstarsrc obviously nonsense? > No (I diffed it). Interestingly, when I start kstars without a config file I do get the messed-up display, but the initial kstarsrc is saved with reasonable values: directly quitting and re-starting makes the error go away. It is rewritten with "nan" if I actually try to move around.
It's almost been a year and a half since this bug was reported. Do you experience the same issue now on KDE 3.4 or HEAD?
Jasem Mutlaq writes: > It's almost been a year and a half since this bug was reported. Do > you experience the same issue now on KDE 3.4 or HEAD? As you can see in the bug report, you shouldn't be asking me this, but the person who reported it as a debian bug ( address is in the bug report ).. cheers domi
Closing ancient bug "WORKSFORME"