Re: iceweasel always requesting to be default browser
Michael M. schrieb: So what is your default browser? Do you have iceweasel set as the default in any DE you are using, if you are using one? What does update-alternatives report? Okay, I'm using Gnome and in the preferred applications settings or whatever it's called in english it says custom with the command to run the application set to /usr/lib/iceweasel/firefox %s. When I set it to iceweasel in the dropdown menu and start iceweasel, it gives me the I'm not your default browser, buhu-crap again. And when I confirm to let the app set itself as default the etnry in the default app-settings from Gnome are as they were in the beginning. So apparently everything is fine but iceweasel doesn't detect that the entry it made itself is actually iceweasel as the default rather than some other program. easiest workaround for now would be to just disable the warning in iceweasel, butr the underlying problem wouldn't be solved by that, now would it? Assuming that you guys don't really now what to do to change this behaviour either, apart from filing a bug report to change the source, I have only one more question: Where should I file this, is it a debian related problem, firefox or Gnome? Thanks again. P.S.: I've never used update-alternatives before but couldnt really figure out how to use it in my case from the man page. I did #update-alternatives --display firefox #update-alternatives --display /usr/bin/firefox #update-alternatives --display /usr/bin/firefox #update-alternatives --display browser and they all returned no alternatives for $command -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
iceweasel always requesting to be default browser
Hi guys! I've got a really strange behaviour in iceweasel since upgrading to the newest package in etch (2.0.0.2+dfsg-3). When I ran it for the first time after upgrading it asked wether I wanted to set it as the default browser. Since the previous version had been my default browser and I intend to keep it that way I was surprised by the prompt, but confirmed it anyway. Now the strange thing is that it keeps aksing the question every time it start it, stating that it is not the default browser atm and wether or not I want to make it. Help greatly appreciated as always. Cheers, Roman. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sources.list urls for Etch
[EMAIL PROTECTED] schrieb: Hi Everyone, I have Etch and got my systems (laptop and desktop) running nicely. I an still realitively new to Debian/Linux and love it. I understand Etch is frozen and will soon be the stable version. I want to make sure I have the correct urls in my sources.list file. This is what I have now: deb http://mirrors.kernel.org/debian/ testing main deb-src http://mirrors.kernel.org/debian/ testing main deb http://security.debian.org/ testing/updates main I looked every where and cannot find anything conclusive. This is what I have found so far: deb http://ftp.debian.org/debian/ etch main contrib non-free deb-src http://ftp.debian.org/debian/ etch main contrib non-free I am in the United States. Will these work? What about the kernel? How about security udates? I use aptitude to maintain my systems and don't want to break anything when I update. Thanks, Danny Murdoch Hi Danny! 1. Yes, that will work 2. Kernel images are usually only upgraded when installed manually (i.e. apt-get install linux-kernel-2.6-latest), wether that also applies to a dist-upgrade as will be the case when etch becomes stable I don't know. But the entry in your sources.list is okay and the kernels in etch are too, so you will be fine wether the kernel is automatically updated or not, if you specifically want a newer kernel the just fire up your favorite package managment tool and install a matching kernel for your system or compile one to fit your needs. 3. To bring some light into the whole sources.list or debian repository thing: On every official debian mirror the directories named testing, stable, unstable etc. are only symbolic links to their respective directories (i.e. testing points to etch, stable to sarge, unstable to sid, etc.). So the easiest thing for you to do is just to change every occurence of testing in your sources.list to etch and your all set. Note however that although with the release of sarge the maintainers, debian crew or whatever you like to call them said that they were going to speed up the release cycle, but unfortunately that wasn't the case since it took us 2 years from woody to sarge and it will also be around 2 years from sarge to etch. What I mean to say by this is that if you want to keep an up-to-date workstation which doesn't have to have 100% uptime, you could just stick with testing since etch will probably as it has been the case with the stable-flavor of debian be out-of-date by the time of release already compared to cutting-edge distros. Cheers, Roman. P.S.: I love Debian and did not mean to offend anyone involved in actually making it. My intention was merely to inform debian-neebies of the fact that what in debian is called 'testing' is indeed less 'faulty' than other distributions stable-tree. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: unable to mount root fs on unknown--block(0,0)
Easiest way to do this is to mount your drives by labels instead of device-names. Search the list for entries by Bob McGowan with the keyword label and you'll find out anything you need to know. Cheers, Roman. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no sound on mplayer + .nsv stream
Hi Jonathan. Don't know if you remember me but we had an e-encounter on this list when you were trying to get your catalan fonts working with unicon. Anyway, just nice to see you're still around. To the facts: Jonathan Kaye schrieb: == Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding) FAAD: compressed input bitrate missing, assuming 128kbit/s! imho this is the problem, probably the actual bitrate is not the detected one, judging fom the fact that the resolution is at 32,5 kHz I'd guess that the bitrate is lower than 128 kbit's. But I have to admit that I don't have a real solution, maybe you should just google the FAAD: compressed input bitrate missing, assuming part. Side-Note: afaik aac is proprietary, so maybe there's just not much doc about the format and so the linux-support pretty bad, maybe you just digged up a bug in the aac-codec. Good luck, Roman. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: old hardware, newer Debian
Ron Johnson schrieb: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/07 00:50, Mike McClain wrote: s. keeling [EMAIL PROTECTED] said: Mike McClain [EMAIL PROTECTED]: I just installed sarge on a box I've happily been running woody on for 5 years and find I can't run X cause the Trident tvga 9800b chipset is no longer supported in the xserver-xfree86 v4.3. Any Try the svga driver. I'm using a PCI Matrox card, development of which was stopped long ago. svga driver picked up the slack and it works beautifully. Pardon the typo, the board is a Trident tvga 8900b, sometimes my fingers seem lisdexic. I've tried 'dpkg-reconfigure xserver-xfree86' with many different combinations. I've tried xf86config, xf86config and xdebconfigurator. I've started over and done a full re-install on another partition, thinking my minimul install might have missed something critical. Not once have I seen a chance to select svga. Vga and vesa yes but not svga. Can you tell me what package gives you that functionality? My board predates vesa hence doesn't answer properly and I get a black screen, that's the case with the latest install now and it's booting Whoa, that's an *old* card. If it's a PCI card, then you should be able to buy a cheap newer one off eBay. I can only concur with that. But to add: I had a a s3 trio64v+ once and had the same problem when upgrading from woody to sarge. In woody there were both v3.3.6 and 4.1.0 versions of XFree86 servers available. So basically if you want to use this card in etch or sarge you need to get Xfree86 3.3.6 in. I'm writing this merely out of curiosity because I really don't consider the following to be a good idea, but I'd love to know wether it works anyway. You could just add entries to oldstable (i.e. woody) to your sources.list and try to # aptitude -t oldstable install xserver-svga or try to # apt-get source xfree86v3 with the appropriate line in your sources.list BUT since you've upgraded to sarge you probably don't want a five (or more) year old xserver that is crippled when it comes to functionality compared to xorg or whatever. So bottom line is, best bet if you want to keep using the card IF the xserver-xorg-trident packages drive your card would be to upgrade top etch or optionally use a backported version in sarge. Cheers, Roman. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: deborphan
Gerard Robin schrieb: On Sat, Feb 03, 2007 at 10:21:04AM -0500, Roberto C. Sanchez wrote: From: Roberto C. Sanchez [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: Re: deborphan Mail-Followup-To: Roberto C. Sanchez [EMAIL PROTECTED], On Sat, Feb 03, 2007 at 03:34:10PM +0100, Gerard Robin wrote: can I remove merely this packages ? That depends. Do you use any of them? it is why I asked advices, by example: if I remove libc6-i386 and after that I install a package x.deb which needs it, will libc6-i386 be reinstalled as dependency of the package x.deb ? Yes, the package wouldn't be able to install faultlessly if the dependencies weren't met, that's the whole point. I've never used deborphan but if it finds that these packages aren't used anymore than you can safely remove them, because: a.) Debian packages are commonly well tested, so generally every package is expected to do what it should. (Sounds pretty superficial, but imho problems with software in debian arise mostly from the fact that it was not installed in a debian way or the user doesn't know the software well enough to configure it the way he wants to use it) b.) Its a package dealing with a package format that originated from and was developed for debian, so if a. is to be untrue 20% of the time then this will make the probability of a being untrue 1% (I sense this is gonna turn out to be a comical coders-short ;)) c.) I don't know exactly how deporphan works but my guess is that it parses the dpkg-database for all the packages installed, reads their dependencies and then rules out which packages are installed but are neither marked as having been manually installed nor are being depended upon by any of the other packages installed. Pretty easy I'd say. And as an additional debugger it gives you (the user) a list of all the packages that match the above named criteria. So, essentially the chance of wrecking your system by uninstalling the suggested packages should be pretty low. ( I know I'm one sardonic bastard, but I like it, AND this is my honest opinion) Cheerio, Roman. So -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: self-built kernel causing boot problems
Bob McGowan schrieb: Roman, For DOS fat based filesystems, you need to install a DOS tool set such as mtools or dosfstools. The mtools includes 'mlabel' to add a DOS label to an existing device. The documentation describes how to set this up. The dosfstools has a 'mkdosfs' command to create a DOS filesystem and it has a '-n' option to provide a 'name' (label). In either case, in /etc/fstab, you use the same LABEL=labelname and the VFAT specific mount command is smart enough to do the right thing. Bob Thank you very much! I didn't know the mlabel tool and since I don't want to format the disk I couldn't find a way to see or change the label. Note on the side though: The Label on the vfat volume is all uppercase and since the entries in fstab are case-sensitive you have to specify LABEL=FOO, not LABEL=foo for it to work. This behaviour can probably by changed by some option to read all the filenames on vfat in lowercase. Also for mlabel to be able to access the disk one has to make an entry for the desired disk in /etc/mtools.conf like so drive c: file=/dev/sdb1 and then mlabel -s c: to display the current disk label, mlabel -c c:foo to change the label to foo. Thanks again, I'll be back on that eth-issue. Cheers, Roman. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: module-assistant/ndiswrapper/kernel-headers
Sven Arvidsson schrieb: On Tue, 2007-01-30 at 12:23 -0800, Freddy Freeloader wrote: The problem is that there is no kernel-headers package with the same exact package version as the installed kernel version. The installed kernel is reported as 2.6.18-3-486 by uname -a. The only kernel headers package available with apt-get for Sid or Etch is 2.6.18-6. Are you sure you have both the linux-kernel-headers and the linux-headers-2.6.18-4-486 packages installed? You know, just rtfm would do the trick. # module-assistant update # module-assistant prepare This should fetch any files you need for building kernel modules, including the headers. AFAIK it doesn't matter wether your headers are x.y.z-a and the image installed is x.y.z.-b but just let module assistant figure that out for you. Then simplest would be to # module-assitant auto-install ndiswrapper but i don't know if it's really ndiswrapper and not ndis-wrapper or something else, if unsure either check you /usr/src/modules directory or simply call module-assistant without any commands and you'll be able to select from a list. Hope I could help, Roman. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
self-built kernel causing boot problems
Hi fellow debianists! I've compiled a kernel from the up-to-date kernel-source-2.6 package with the aim to be able to build realtime linux security module. To do this I followed the instructions from the README.Debian in the realtime-lsm documentation. I got the linux-2.6_2.6.18-7 sources, unpacked them in /usr/src, copied the config of my running kernel from /boot/config-2.6.18-3-686 to /usr/src/linux-2.6-2.6.18/.config and updated it to say CONFIG_SECURITY_CAPABILITIES=m. Now when i try to boot it it sits there wating for root filesystem, after some ta i figured out that somehow the new kernel (or the initrd.img, don't know which is responsible here) registers my external usb hdd as sda and my internal sata hdd as sdb which is usually the other way round. if i turn off the usb disk and boot again it works, but that is not really a viable option and also i discovered that my internet or rather network device doesn't work as well. If I keep the usb drive turned on and change the grub boot option to say kernel /boot/vmlinuz-2.6.18-1-lsm root=/dev/sdb3 ro instead of root=/dev/sda3, the boot process continues until the devices from fstab. fstab: # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/sda3 / ext3defaults,errors=remount-ro 0 1 /dev/sda9 /home ext3defaults0 2 /dev/sda8 /tmpext3defaults0 2 /dev/sda5 /usrext3defaults0 2 /dev/sda6 /varext3defaults0 2 /dev/sda7 noneswapsw 0 0 /dev/hde/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/sdb1 /daten vfatuser,auto,uid=1000,gid=1000 0 2 but of course fails, because sda should be sdb and vice versa. Any help would be greatly appreciated. It would be possible to load different /boot/grub/menu.lst and /etc/fstab files at boot via some shell scripts, but that wouldnt be a really good solution and the ethernet problem remains. Thanks in advance, Roman. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: self-built kernel causing boot problems
Thanks for your answer bob. Now there's only two problems remaining. First, my internet connection still isn't working, but I see I'll have to go investigate on this one but 2nd you might be able to help me with. my usb hdd, /dev/sda on the standard and sdb on my self-built kernel is fat32 or vfat in linux-speech and apparently I've neither found a way to set/change the label on vfat nor would mount care if I could afaik from what I've read on the net. Any ideas on this one? Cheers, Roman. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
