Re: KLF setup
<< It wouldn't be so bad if there was just one concise piece of documentation but alas, we have all manor of stuff out in the wide on the net. Much of it is not correct for Ubuntu or your particular version of Ubuntu. Tools we really need but also good docs for each release. >> I think this is indicative of Linux, not just Ubuntu. Every distro and every release invents some new and improved wheels, and neglects documentation. We badly need a standards body to dampen the chaos. LSB? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu-devel-discuss Digest, Vol 3, Issue 22
<< They are actually supposed to go to ~/.xsession-errors. Please file bugs if that doesn't happen for a particular case. At least it works fine for me with f-spot under Gnome. >> YES, that's the problem. And the real problem is that Linux gurus don't understand that it's a problem. I went looking in .xsession-errors for hints about why Totem bombs when trying to play a quicktime file. I found hundreds of messages. Below is a sample of each type. Makes a lot of sense, doesn't it? I have been "learning" Linux for almost two years now, and I have written about 20K lines of GTK code. This is the first time I ever heard about .xsession-errors. How much of a chance do you think the average non-technical person has dealing with Linux? It is hard enough for people like me with lots of experience. Ubuntu may soon have enough critical mass to set the agenda and the standards that will make Linux more viable. I hope it happens, but it would need someone caring about the little details like hidden error messages and decent documentation. my .xsession-errors file: /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "mico" /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/mico1:/tmp/.ICE-unix/4491 Gnome-Message: gnome_execute_async_with_env_fds: returning -1 Gnome-Message: gnome_execute_async_with_env_fds: returning -1 ** Message: plugin_get_value 1 (1) totem-video-thumbnailer couln't thumbnail file: 'file:///home/mico/.Trash/Gammelsdorf190207.mov' Reason: Took too much time to thumbnail. DOUBLE-CLICK: 500 --> -1 THRESHOLD: 5 --> -1 DOUBLE-CLICK: 500 --> -1 THRESHOLD: 5 --> -1 ** (nautilus:4566): WARNING **: file already in tree (parent_ptr: (nil))!!! Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x243 (fotox.09); these messages lack timestamps and therefore suck. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
hidden error messages
I just had yet another unpleasant experience trying to play a multimedia file (quick time .mov file). I tried several media players and I witnessed crashes, cryptic messages and often nothing at all unless I ran the app from a terminal in order to see messages to stdout and stderr. I got the messages, but they were no help. I gave up and booted windows to view the file. The point of this message is the crappy state of user messages and diagnostics, not particularly in Ubuntu, but Linux in general. Perhaps Gnome apps are the greatest offenders here (weak opinion). When a GUI application outputs error messages to stdout or stderr, it is like writing them into a black hole. This stupid practice should stop. Messages to stdout or stderr should pop-up in a text window. This should be a standard part of Gnome/GTK or any other desktop GUI. stdout and stderr should be piped to another process to display. Better yet, printf() should not be used at all in such apps, since popping up a message window is so easy. In the case where a GUI front-end is driving a command-line back-end, output can still be piped back and displayed, although obviously there is more work to filter and recognize the error messages that the user needs to see. Can't this sorry situation be improved? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
