K3b settings cdrdao change won't stick
Dear friends: [Using Xandros 2/Debian] I recently reinstalled my Xandros 2. In my earlier installation, I succeeded in pressing ENTER and saving the new settings in K3b (Settings, bottom box), where I UNchecked "cdrecord" and "cdread", leaving only "cdrdao" checked. This time, though, I have encountered the strange situation where K3b informs me that I have succeeded in making the changes in Setup but, in fact, when I close K3b and restart it, all options are still checked. I've done this several times, each time with the same results. Please see screenshot at: http://www.websher.net/k3b1.png Any suggestions? Could it harm my system if I did NOT succeed in making these changes stick? Thank you in advance. Benjamin -- Sher's Russian Web http://www.websher.net Benjamin and Anna Sher [EMAIL PROTECTED]
Re: k3b & kernel 2.6 (cdrdao)
On Tue, Jan 13, 2004 at 12:09:46AM +0100, Jean-Michel Kelbert wrote: > > OK. I'll report a bug anyway. Thanks for checking. > > I'll solve it in next version. > Please set bug to normal. Too much users are using bad levels. > > -- > Jean-Michel Kelbert I have a question: would this fix affect only k3b, or cdrdao in general? I have ATAPI, a very difficult HP cdwritter that has been reported as conflicting with scsi in the kernel (I had to remove scsi from kernel, kept throwing it into panick), therefore I have been using cdrecord with ATAPI. But I also like using cdrdao from command line, besides k3b, etc. If not, could someone explain what the fix would be for cdrdao? I got late on the thread. Thanks to all.
Re: No dead keys (fixed)
On Thursday 25 December 2003 12:51, Anders Ellenshøj Andersen wrote: > > Did you enable keyboard layouts and choose correct keyboard model & > > variant? > > I have tried 102-keys 104-keys and 105-keys, and different variants, > including nodeadkeys. > > With nodeadkeys enabled, I do get the correct character when pressing a > dead key, but if I go back to basic or full variant the dead keys simply do > not function at all. > > This used to work with the KDE keyboard layouts disabled completely. Well nothing I tried worked, so finally I figured there had to be some bug in the packages themselves. So I went all out and purged KDE completely and reinstalled everything again. Now everything works like it should. éèöãï :) Anders -- This email was generated using KMail from KDE 3.1.5 on Debian GNU/Linux
Re: k3b with ATAPI cdrom
On Monday 12 January 2004 19:37, Todd Charron wrote: > On January 12, 2004 08:32 am, Tom Badran wrote: > > When calling cdrecord, k3b only passes dev=/dev/hdc instead of the > > required dev=ATAPI:/dev/hdc and i cant find any way of changing this. > > > > Anyone know how? > > Under Settings -> Configure K3B -> Programs -> User Paramters you can tell > K3B what options you want passed to cdrecord. Excellent, it puts those after the where it adds a dev= parameter so this works great. Tom
Kbear screenshot
Dear friends: This is a follow-up to my earlier letter about not being able to access my web site. Here is a screenshot: http://www.websher.net/kbear1.png. Yet, I can access other sites with Kbear. And I can also access my own site with gftp and IgloofTP but not with Kbear. Any help would be appreciated. Benjamin -- Sher's Russian Web http://www.websher.net Benjamin and Anna Sher [EMAIL PROTECTED]
Kbear now works fine
Dear friends: Well, it looks like Kbear now accesses my site perfectly well. Don't know what happened but looks like a configuration error. Thank you all. Benjamin -- Sher's Russian Web http://www.websher.net Benjamin and Anna Sher [EMAIL PROTECTED]
Re: kompare: "Could not find our Part!"
On Tuesday 13 January 2004 16:15, Dominique Devriese wrote: > Michael Schuerig writes: > > For some time now, even after reinstallation of the package, > > kompare k^Hcomplains to me that it can't find its part. > > Specifically, it can't find the file comparison part, selection of > > files works fine. > > > > Does this happen to anyone else? > > Can you try to start kompare from a terminal, and see if there's an > error ? It doesn't produce any error output, neither on stdout nor in ~/.xsession-errors > Have you recently installed or compiled any > non-default-debian KDE or Qt libraries ? No. But the problem appears to be on my side of the fence. I've tried kompare in a chrooted install and there it works. Curiously (or rather luckily), I don't have any other problems of this kind. Michael -- Michael Schuerig What if the enemy / Isn't in a distant land mailto:[EMAIL PROTECTED] What if it lies behind / The voice of command http://www.schuerig.de/michael/ --Ani DiFranco, "Roll With It"
juk skipping
Just moved from woody to sarge. This went fine. I tried out the juk mp3 player. The interface seems a lot nicer then that of xmms but the performance really sucks. It has artsd running at 50% CPU load, whereas artsd will consume 1-5% of CPU cycles under xmms. I also get skips whenever I move a window. I tried running artsd with and without real time priority but this won't make a difference. Is there a secret word that makes this work? alex -- Alex Polite http://plusseven.com/whoami
Re: K3b, cdrecord and user...
Le 13/01/04 à 14:37 Lars Schimmer ([EMAIL PROTECTED]) écrivait : > Hi! > > I just setup Debian sarge with KDE 3.1 and an IDE/ATAPI burner and k3b. > While starting K3b as a user, I get the message: Can't find cdrecord, > install package cdrtools for cdrecord." > But apt-cache doesn't show ANY cdrtools package, only cdrecord, which is > in the system. > How do I get K3B to run as a user and burn as a user? 0) apt-get install cdrecord 1) at the setuid question, say yes. 2) add the user to the cdrom group -- Jean-Michel Kelbert signature.asc Description: Digital signature
Re: Kbear screenshot
hi, > This is a follow-up to my earlier letter about not being able to access > my web site. Here is a screenshot: > > http://www.websher.net/kbear1.png. well, at least I can't access your server... so long, Timo
K3b, cdrecord and user...
Hi! I just setup Debian sarge with KDE 3.1 and an IDE/ATAPI burner and k3b. While starting K3b as a user, I get the message: Can't find cdrecord, install package cdrtools for cdrecord." But apt-cache doesn't show ANY cdrtools package, only cdrecord, which is in the system. How do I get K3B to run as a user and burn as a user? Cya Lars -- - Technische Universität Braunschweig, Institut für Computergraphik Tel.: +49 531 391-2109E-Mail: [EMAIL PROTECTED]
Re: k3b & kernel 2.6 (cdrdao)
On Tuesday 13 January 2004 02:20 am, Antonio Rodriguez wrote: > On Tue, Jan 13, 2004 at 12:09:46AM +0100, Jean-Michel Kelbert wrote: >> > OK. I'll report a bug anyway. Thanks for checking. >> >> I'll solve it in next version. >> Please set bug to normal. Too much users are using bad levels. >> >> -- >> Jean-Michel Kelbert > > I have a question: would this fix affect only k3b, or cdrdao in > general? I have ATAPI, a very difficult HP cdwritter that has been > reported as conflicting with scsi in the kernel (I had to remove scsi > from kernel, kept throwing it into panick), therefore I have been > using cdrecord with ATAPI. But I also like using cdrdao from command > line, besides k3b, etc. > If not, could someone explain what the fix would be for cdrdao? I got > late on the thread. > Thanks to all. > > The fix only affects k3b. It's bug #227336 For cdrdao to work with kernel 2.6 atapi you will need cdrdao 1.1.7-5. It's in both testing and unstable. To run it from the command line, I use options: "--device /dev/hdc --driver generic-mmc" Hope this helps. John Stamp
Re: Kbear -- Is it broken?
On Tuesday 13 January 2004 03:46, Benjamin Sher wrote: > Anyone had the same problem? Any suggestions? I use version 2.1.1-1 from Debian sid and it works just fine. -- --- Magnus von Koeller --- email:[EMAIL PROTECTED] address: International University Campus 9, App. 13 D-76646 Bruchsal / Germany phone:+49-7251-700-659 mobile: +49-179-4562940 web: http://www.vonkoeller.de pgp42cntVL6jz.pgp Description: signature
Re: kompare: "Could not find our Part!"
Michael Schuerig writes: >> Have you recently installed or compiled any non-default-debian KDE >> or Qt libraries ? > No. But the problem appears to be on my side of the fence. I've > tried kompare in a chrooted install and there it works. Curiously > (or rather luckily), I don't have any other problems of this kind. Did you change the setting of the KDEDIR or KDEDIRS environment variables ? cheers domi
Re: kompare: "Could not find our Part!"
On Tuesday 13 January 2004 17:56, Michael Schuerig wrote: > On Tuesday 13 January 2004 17:27, Dominique Devriese wrote: > > Michael Schuerig writes: > > >> Have you recently installed or compiled any non-default-debian KDE > > >> or Qt libraries ? > > > > > > No. But the problem appears to be on my side of the fence. I've > > > tried kompare in a chrooted install and there it works. Curiously > > > (or rather luckily), I don't have any other problems of this kind. > > > > Did you change the setting of the KDEDIR or KDEDIRS environment > > variables ? > > ~$ echo $KDEDIRS > /usr:/usr/local/kde:/usr/local > > There are no conflicting libs in the local dirs. /usr/local is > unecessary and I just removed it, but I use /usr/local/kde for my own > development; it's easier that way than to create a package for every > test run. is kompare in /usr or /usr/local/kde? If in /usr/local/kde, check if it is already in KDEDIRS when startkde runs. Cheers, Kevin pgpHmpKal0miz.pgp Description: signature
KDE crash when initializing keyboard
Hi I have installed debian woody on my laptop as well as kde and kdm which I installed with apt-get. Now when starting kde through kdm it crashes when initializing the keyboard. When starting with twm every thing is working perfectly. So can some one tell me what do I have to change to let kdm start kde correctly. Thanks thomas
Re: KDE crash when initializing keyboard
On Tuesday 13 of January 2004 10:15, Thomas Baumann wrote: > Now when starting kde through kdm it crashes when initializing > the keyboard. When starting with twm every thing is working > perfectly. This rather mysterious problem presented itself, when I was installing Debian on my wife's notebook to show her how dependable Linux is :-). After two hours of banging our heads again the wall, we found out that the problem was that the video adapter doesn't support DPMI. Try to put Option "DPMI" "Off" to /etc/X11/XF86Config-4. Does it help? Matej -- Matej Cepl, http://www.ceplovi.cz/matej GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 He has never been known to use a word that might send a reader to the dictionary. -- William Faulkner (about Ernest Hemingway) pgpjhkzhL8bZp.pgp Description: signature
Re: kompare: "Could not find our Part!"
On Tuesday 13 January 2004 17:27, Dominique Devriese wrote: > Michael Schuerig writes: > >> Have you recently installed or compiled any non-default-debian KDE > >> or Qt libraries ? > > > > No. But the problem appears to be on my side of the fence. I've > > tried kompare in a chrooted install and there it works. Curiously > > (or rather luckily), I don't have any other problems of this kind. > > Did you change the setting of the KDEDIR or KDEDIRS environment > variables ? ~$ echo $KDEDIRS /usr:/usr/local/kde:/usr/local There are no conflicting libs in the local dirs. /usr/local is unecessary and I just removed it, but I use /usr/local/kde for my own development; it's easier that way than to create a package for every test run. Michael -- Michael Schuerig What if the enemy / Isn't in a distant land mailto:[EMAIL PROTECTED] What if it lies behind / The voice of command http://www.schuerig.de/michael/ --Ani DiFranco, "Roll With It"
Re: kompare: "Could not find our Part!"
Michael Schuerig writes: > For some time now, even after reinstallation of the package, kompare > k^Hcomplains to me that it can't find its part. Specifically, it > can't find the file comparison part, selection of files works fine. > Does this happen to anyone else? Can you try to start kompare from a terminal, and see if there's an error ? Have you recently installed or compiled any non-default-debian KDE or Qt libraries ? cheers domi
Re: kompare: "Could not find our Part!"
On Tuesday 13 January 2004 18:24, Kevin Krammer wrote: > On Tuesday 13 January 2004 17:56, Michael Schuerig wrote: > > ~$ echo $KDEDIRS > > /usr:/usr/local/kde:/usr/local > > > > There are no conflicting libs in the local dirs. /usr/local is > > unecessary and I just removed it, but I use /usr/local/kde for my > > own development; it's easier that way than to create a package for > > every test run. > > is kompare in /usr or /usr/local/kde? > If in /usr/local/kde, check if it is already in KDEDIRS when startkde > runs. It's in /usr -- standard install from debian package. Michael -- Michael Schuerig There is no matrix, mailto:[EMAIL PROTECTED]only reality. http://www.schuerig.de/michael/ --Lawrence Fishburn
kompare: "Could not find our Part!"
For some time now, even after reinstallation of the package, kompare k^Hcomplains to me that it can't find its part. Specifically, it can't find the file comparison part, selection of files works fine. Does this happen to anyone else? Michael -- Michael Schuerig Nothing is as brilliantly adaptive mailto:[EMAIL PROTECTED] as selective stupidity. http://www.schuerig.de/michael/ --A.O. Rorty, "The Deceptive Self"
KDE crashes on startup
Hi. I've been having a few problems with getting debian woody working, it must be about 2 weeks now since I first installed it. Thanks to google and guys over at the debian-user list I've gotten X at least starting now (with the vesa drivers, it still won't start with the nvidia ones) The computer still isn't working correctly, when I log in KDE crashes just after it gets to the initalising peripherals stage. I can start sawfish and gnome and ok so I think this is a problem with KDE. I'm not sure what details to post here. When X wasn't working I'd put my XFree86.log online, but I don't know what the KDE equivalent is. This seems like a KDE bug, but I don't think I have enough information to make a bug report. Hardware: Gigabyte GA-7VAX mobo (uses via KT400), GeForce Ti 4200 video card, Hauppauge wintv, AthlonXP, Logitech MX700 usb mouse, SoundBlaster live! soundcard Regards, -- Jim
Konqueror open and open and open...
Sometimes i click to open a window in the konqueror and he open a infinity of windows, my only way is exit session, if someone had this problem and solve i like to know how to fix it.
Re: KDE crashes on startup
On Wed, 14 Jan 2004 02:03:29 -, Jim Higson <[EMAIL PROTECTED]> wrote: Hi. I've been having a few problems with getting debian woody working, it must be about 2 weeks now since I first installed it. Thanks to google and guys over at the debian-user list I've gotten X at least starting now (with the vesa drivers, it still won't start with the nvidia ones) The computer still isn't working correctly, when I log in KDE crashes just after it gets to the initalising peripherals stage. I can start sawfish and gnome and ok so I think this is a problem with KDE. I'm not sure what details to post here. When X wasn't working I'd put my XFree86.log online, but I don't know what the KDE equivalent is. This seems like a KDE bug, but I don't think I have enough information to make a bug report. Hardware: Gigabyte GA-7VAX mobo (uses via KT400), GeForce Ti 4200 video card, Hauppauge wintv, AthlonXP, Logitech MX700 usb mouse, SoundBlaster live! soundcard Regards, Forgot to mention - the error I get is: "Caught signal 11. Server aborting" which i think is to do with memory segmentation. and I've put a few relevent-looking files up here http://users.aber.ac.uk/jqh1/x/ -- Jim Higson
Re: KDE crashes on startup
On Tue 13 Jan 2004 7:51 pm, Jim Higson wrote: > On Wed, 14 Jan 2004 02:03:29 -, Jim Higson <[EMAIL PROTECTED]> wrote: > > Hi. I've been having a few problems with getting debian woody working, > > it must be about 2 weeks now since I first installed it. Thanks to > > google and guys over at the debian-user list I've gotten X at least > > starting now (with the vesa drivers, it still won't start with the > > nvidia ones) > > > > The computer still isn't working correctly, when I log in KDE crashes > > just after it gets to the initalising peripherals stage. I can start > > sawfish and gnome and ok so I think this is a problem with KDE. > > > > I'm not sure what details to post here. When X wasn't working I'd put my > > XFree86.log online, but I don't know what the KDE equivalent is. This > > seems like a KDE bug, but I don't think I have enough information to > > make a bug report. > > > > Hardware: Gigabyte GA-7VAX mobo (uses via KT400), GeForce Ti 4200 video > > card, Hauppauge wintv, AthlonXP, Logitech MX700 usb mouse, SoundBlaster > > live! soundcard > > > > Regards, > > Forgot to mention - the error I get is: > "Caught signal 11. Server aborting" which i think is to do with memory > segmentation. > > and I've put a few relevent-looking files up here > http://users.aber.ac.uk/jqh1/x/ > > -- > Jim Higson Hmmm. I took a look at the log files you put on your web site (which are useful), and it looks like XFree86 itself is crashing. FYI, as far as signal 11, aka segmentation faults... Linux uses a feature found in most modern CPUs called protected memory. Each program (including KDE's programs and XFree86) running in Linux is allocated it's own memory space. The program can do whatever it wants in it's memory space, but is forbidden from stepping outside it's memory space, or segment (I'm oversimplifying, but hear me out.) Sometimes, due to bugs, a program tries to illegally access a memory address outside it's allocated area. The CPU and kernel will catch the the program and terminate it with extreme prejudice, leaving you with a segmentation fault error. This is a Good Thing, because if a program was allowed to address memory outside of it's allocated area, it could scribble all over other programs or the kernel itself, which could crash your entire system. Now, as to why XFree86 is crashing... You've already had problems with the nvidia drivers, so you switched to the vesa drivers. According to the XFree86.0.log file, it crashed soon after you try to load OpenGL related stuff, which won't work very well because the vesa drivers won't give you hardware-accelerated 3-d. Things to try: Comment out or remove the lines 'Load "GLcore"' and 'Load "glx"' under Section "Module" in your XF86Config-4. OpenGL will be dog slow without NVidia's accelerated drivers anyways, so if you won't be using them, get rid of them. Without them, OpenGL programs probably won't work at all. You may also want to uninstall nvidia's glx drivers (the nvidia-glx package) so the system goes back to using the generic glx libraries. Another alternative if you want accelerated 3-D for games and such is to get the nvidia drivers working, which is definitely tricky, but may solve your segfault problems. It requires compiling and installing nvidia's kernel driver (and it looks like you already have nvidia's glx libraries which may be trying to do their thing but can't talk to the nvidia driver). Let us know what happens. If you want to get nvidia's driver working, let me know. I've had to wrestle with them a couple times (though in sid, not woody), so I might be able to help you get them working. Doug pgpfCXOXze8s0.pgp Description: signature
