ALSA lib control.c:601:(snd_ctl_open_noupdate) Invalid CTL default
hi, I re-installed ALSA on my debian 2.4.19 system and it installed fine.but when I use amixer I get this error. ## ALSA lib control.c:601:(snd_ctl_open_noupdate) Invalid CTL default amixer: Mixer attach default error: No such file or directory ### is it looking for some default file or is it some setup problem. any suggestions on how to fix it. thanks suresh __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com
KDE3-Usage
Hi, some thanks to the good packaging :D Installation from testing is a bit difficult, though, and really needs a lot of packages from unstable, even ones that I would not think of like cdparanoia and lots of others (although it makes no sense to request version 3a9.8-7 when version 3a9.8-6 is present!). So there it is, KDE3.0.4. Works great, although at first I cannot see any advances to KDE2.2.2 at all. The proposed feature that it might load faster simply does not exist (here). The font handling did not get any better. Klipper can be on its own in the control bar although it would make more sense when it simply stays with the system tray. The Liquid (0.9.5-1) style got a lot worse, though. The translucency is unusable because it is crippled. The problem is that the menus "unfold" in a short animation (how can I turn this off?). This creates some kind of background image instead of the translucency effect. BTW, are there plans to make X use an alpha channel for such things? XFree5? ;) Beside that: it is looking much better than the default style. An advantage is that sound now also works without starting artsd (I never did). Interesting but sadly incomplete: noatun does not want to start without artsd running, so I use xmms. But xmms has still the same problem: I can only choose between a working dock icon (systen tray) or the "show no window managers window frame around my window, so that attaching playlist, etc. works". Still, there is nothing that can be done with kstart to work around this :( Kmail now works quite a bit faster on downloading mails :) But on the change to the new version, the gpg setting got lost - well, it took some work to go through all the options again. Kscd works a lot better now, especially the track names display is ot broke anymore :) Finally: a thanks to the developers, packagers and the bug hunting community... HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org
kdbg and kde3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have kde3 (3.0.4) installed I am setting up my development environment around kdevelop which appears to be built with the kde3 libraries. However, it seems to use kdbg in order to provide debugging capabilities, and therefore I would like to install that too. At the moment, kdbg only appears to be built against kde2 libraries, so I have loaded up the source and was looking to change the debian/control file to allow it to build against kdelibs4. I would make my own deb. However, one of the binary dependancies is shown as kdebase-libs. Looking at the version numbers in dselect, this package seems to be one of the kde2 ones, and there is no matching package for kde3. Do I need that dependancy anymore, or is kdelibs4 sufficient? - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qTKzuFHxcV2FFoIRAlplAJ4vAavV69keuZiPntuC61UNoWjXywCeIEFN sebWL3DgMxW/ideYFkeXOF8= =dogW -END PGP SIGNATURE-
Re: kdbg and kde3
A version of kdbg built against KDE3 is available from the same site as the koffice packages: deb http://people.debian.org/~bab/kde3 ./ > Do I need that dependancy anymore, or is kdelibs4 sufficient? You can happily remove it; it's already been removed from 1.2.5-3 (which is the package available from the above site). Ben (kdbg maintainer). -- Ben Burton [EMAIL PROTECTED] | [EMAIL PROTECTED] Public Key: finger [EMAIL PROTECTED] Questions are never indiscreet. Answers sometimes are. - Oscar Wilde
Re: kdbg and kde3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 13 October 2002 10:01 am, Ben Burton wrote: > deb http://people.debian.org/~bab/kde3 ./ Thanks - saves a bit of work - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qTmquFHxcV2FFoIRAjPZAJ9FHn4nIAsx4mDVcEC+S1WCz7fW8QCfSZMK r85ezfSrW46SoBqR+hRA2Ow= =nAkD -END PGP SIGNATURE-
Re: KDE 3.1beta2 packages
Sylvain Joyeux <[EMAIL PROTECTED]> writes: > I they are no more on ftp.kde.org. Where are they located now ? I'm still wondering where these packages have gone. deb ftp://download.kde.org/pub/kde/unstable/kde-3.1-beta2/Debian/woody/ ./ does not work atm. Now where can I get the latest Beta packages? Michael
libarts1-alsa ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, is there such a thing? Generally, my problem is the following: I installed the alsa vir-midi module (I want to connect this with sequencer support to the timidity sequencer client and then write a how-to about this ;)) I can see that the virmidi is active: - ---snip--- $ cat /proc/asound/oss/sndstat Sound Driver:3.8.1a-980706 (ALSA v0.9.0rc3 emulation code) Kernel: Linux linux 2.4.19acpi #3 Son Sep 29 11:58:47 CEST 2002 i686 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: VIA 8233 at 0xe400, irq 12 Virtual MIDI Card 1 Audio devices: 0: VIA 8233 (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: 1: Virtual Raw MIDI Timers: 7: system timer Mixers: 0: mixer00 1: mixer10 - -snip- and this also shows up in kcontrol. But neither kmix sees this mixer10 nor can I select the new midi device in kcontrol. Please help me HS - -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qUKizvr6q9zCwcERAhsTAKCNFnzPsT5PK3zNpHzApbLU3acezgCfbJ+S ixFTUJCUo9uuL7Y7S3SCGos= =HLet -END PGP SIGNATURE-
Re: KDE 3.1beta2 packages
On Sun, Oct 13, 2002 at 11:48:16AM +0200, Michael Stucki wrote: > deb ftp://download.kde.org/pub/kde/unstable/kde-3.1-beta2/Debian/woody/ ./ > > Now where can I get the latest Beta packages? They seem to of gone as of last week. Have a look for a post earlier in the week from Ralf Nolden. The only source of KDE-3.1-beta2 packages which I am aware of is Karolina's at: deb http://shakti.ath.cx/debian/kde3.1-beta2 ./ There is a mirror site, but the mirror isn't in sync with upstream. David Pashley you should update the FAQ with these locations. Mark
KDE3 - Debian/experimental distribution proposal (was: yes i am alive ;)
On Sat, Oct 12, 2002 at 02:05:38AM -0500, Chris Cheney wrote: > Feel free to reply to this thread regarding any ideas on cleanups, or > anything else related to packaging. There seems to be a lot of confusion about Debian and KDE3 and I think most of it stems from not having a standard consistent location were people can find the Debian KDE3 debs from. While we don't want to pollute Debian/unstable with non gcc-3.2 KDE3 packages, we also aren't building and managing the Debian KDE3 packages in a coherent fashion. Enter the Debian/experimental distribution, which is a perfect place for the various Debian KDE3 package maintainers to coordinate their packages: The packages with this distribution value are deemed by their maintainers to be high risk. Oftentimes they represent early beta or developmental packages from various sources that the maintainers want people to try, but are not ready to be a part of the other parts of the Debian distribution tree. Download at your own risk. For example over the last few months if you were on the ball you knew you could chase up and around the following locations to get a hold of a 'full' KDE3 suite of Debian packages: people.debian.org # Various additional KDE maintainers such as myself kde3.geniussystems.net # Seems to come and go, but it currently has some 3.0.8 deb's up! shakti.ath.cx # Karolina's great but different work with 3.0.8 download.uk.kde.org # Linked to official KDE release, current best source for 3.0.4, had some 3.0.8 for a while but then they went again :-( plus there are mirrors of all of the above sites in various states of completion and many mirrors are lagging synchronisation by a couple of releases. So if I'm a user and want to have these various packages I need an extra couple if not 4 or 5 different apt/sources lines included. If I'm one of the many other KDE3 package maintainers (which I am) I have a real problem deciding which fork of the above I should build my packages for which I then upload to people.debian.org. My proposal is that Debian KDE3 maintainers use the Debian/experimental distribution for the coordination of Debian KDE3. This has the advantages that these packages then become a part of the Debian distribution/ mirrors but are flagged as being 'work in progress', other Debian KDE3 developers know what the current core is and can work to uploading complementary packages to a known state and location. All Debian developers are able to upload their packages to the experimental distribution by indicating this in the package debian/changelog. Once the gcc-3.2 transition is developed then this can be the appropriate time to move KDE3 from experimental to unstable. Mark pgpkEw9cFhGoR.pgp Description: PGP signature
Re: KDE3 - Debian/experimental distribution proposal (was: yes i am alive ;)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 13 October 2002 12:53, Mark Purcell wrote: Hi Mark, well, as much as this would work out, someone has to do the work actually. And regarding the experimental distribution - that brings your work environment to a highly unstable state, not to speak about the packagers having to build the packages on this system. Now, let's please be reasonable about what can be done easily and what is desireable. Have a quick look at the current state: - - KDE 3.1 has entered message freeze. The RC's are not too far away now, so we should better take care of fixing remaining issues and completing installation routines (this is what chris, bab, dpash and I do now). - - KDE 3.1 beta2 is a different story. If yenar wouldn't have provided his build, then there would have been none at all. From the user perspective I'd say, oooh too bad, why did those packages disappear ? From the developer perspective, I say, well, this build wasn't done correctly anyway because it did't take the tag that was used for the beta but has been a CVS checkout shortly after the beta and was compiled using qt-copy from CVS which was qt-3.1 beta 1 at that time, which was known to be binary incompatible to everything else. So, sorry to say that, but I just uploaded yenar's build to ftp.kde.org because I thought, better this build than no build. The ftp admins have taken the version down due to the many complains about the apt line whatsoever. The result is, if something is provided as-is especially for a beta and everyone complains, the stuff is taken down unfortunately. Nobody had the time to fix this, so here it went. The other thing is what version of Debian users want to run KDE on. I myself would prefer woody, although testing and unstable are fine, too. That's why I think I would like to continue doing those two builds until I've set up yet another system that can handle a testing build. Both of them are moving targets though, much more than woody (obviously). So, a continuous usable KDE build makes sense on woody the most, that's why I would stick to keeping the quality there while at the same time from the packager perspective providing debs for unstable will give us a nice feedback about the status of what we're doing. Just uploading and building requires time and energy that one sometimes better puts into fixing stuff than providing debs for bleeding edge geeks like we are. My idea would be better to create a debian.kde.org website to collect all this information and to host a permanent official build on ftp.kde.org. That can be the releases as they are plus additional applications that are provided for those builds. We can sort those in into ftp if we like to, and that is the easiest way to provide people a one-liner for their sources.list to update regularly. Other than that, after that is done someone is needed to volunteer for rewriting the Debian documentation part in the KDE documentation system, have a look at KHelpCenter yourself :-) Comments ? Ideas ? Or is my proposal just wishful thinking from a KDE developer perspective ? :-) Ralf > On Sat, Oct 12, 2002 at 02:05:38AM -0500, Chris Cheney wrote: > > Feel free to reply to this thread regarding any ideas on cleanups, or > > anything else related to packaging. > > There seems to be a lot of confusion about Debian and KDE3 and I think > most of it stems from not having a standard consistent location were people > can find the Debian KDE3 debs from. While we don't want to pollute > Debian/unstable with non gcc-3.2 KDE3 packages, we also aren't building > and managing the Debian KDE3 packages in a coherent fashion. > > Enter the Debian/experimental distribution, which is a perfect place for > the various Debian KDE3 package maintainers to coordinate their packages: > > The packages with this distribution value are deemed by their > maintainers to be high risk. Oftentimes they represent early > beta or developmental packages from various sources that the > maintainers want people to try, but are not ready to be a part > of the other parts of the Debian distribution tree. Download at > your own risk. > > For example over the last few months if you were on the ball you knew > you could chase up and around the following locations to get a hold > of a 'full' KDE3 suite of Debian packages: > > people.debian.org # Various additional KDE maintainers such as myself > kde3.geniussystems.net# Seems to come and go, but it currently has > some 3.0.8 deb's up! > shakti.ath.cx # Karolina's great but different work with 3.0.8 > download.uk.kde.org # Linked to official KDE release, current best > source for 3.0.4, had some 3.0.8 for a while but > then they went again :-( > > plus there are mirrors of all of the above sites in various states of > completion
Kde 3.0.3 slow
Hi, I've just a problem of speed: yesterday, after upgrading my debian (40 packages), i restarded my computer and kde was blocked at "Initialisizing services". In fact, it was not really blocked: it takes 3 to 4 minutes to boot ! And after, some application like konqueror takes also 2 or 3 minutes to launch. But applicstion based ont gtk works fine. Kmail works fine too. It's very strange. I am thinking about a problem with Qt (because i think that qt have been upgraded by my apt-get upgrade (the version 3.0.5 is installed)) but i tried to downgrade qt to 3.0.4 and it doesn't solve the problem. It's only what I found when reading the archive of the list. Any idea ? thanks, JFL
Re: KDE3 - Debian/experimental distribution proposal (was: yes i am alive ;)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > The other thing is what version of Debian users want to run KDE on. I > myself would prefer woody, although testing and unstable are fine, too. Packages containing the latest stable KDE release should be provided for woody. KDE betareleases should require at least testing because of the newer qt version. > My idea would be better to create a debian.kde.org website to collect all > this information and to host a permanent official build on ftp.kde.org. > That can be the releases as they are plus additional applications that are > provided for those builds. Such a site would be great; but someone has to find to maintain it... > > Other than that, after that is done someone is needed to volunteer for > rewriting the Debian documentation part in the KDE documentation system, > have a look at KHelpCenter yourself :-) Who reads help? Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD4DBQE9qWXghCRFv/hWVnsRAhckAJYhU2LozViuHKW6aCkyqRO2KaAvAKDL0uLW scE3wf6JNHLZAiA+DnqSIQ== =ZuJN -END PGP SIGNATURE-
Re: alsamixer error.
Le Samedi 12 Octobre 2002 20:29, suresh kumar sharma a écrit : > hi, > I Re installed ALSA on my system. > everything went fine. > but when I tried using amixer I got this error. > ### > ALSA lib control.c:601:(snd_ctl_open_noupdate) Invalid > CTL default > amixer: Mixer attach default error: No such file or > directory > ### Did alsaconf worked on your system ? Does running the script /usr/share/doc/alsa-base/examples/snddevices of any help ? -- [EMAIL PROTECTED] http://www.kde-france.org
kmid only crashes on startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I installed kmid 3.0.4 from download.uk.kde.org and it simply crashes on startup: 0x40e7b609 in wait4 () from /lib/libc.so.6 #0 0x40e7b609 in wait4 () from /lib/libc.so.6 #1 0x40ef0dd0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x40d2ceeb in waitpid () from /lib/libpthread.so.0 #3 0x405eaa20 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x40d2aa44 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x40e04518 in sigaction () from /lib/libc.so.6 #6 0x4006beb7 in DeviceManager::setMidiMap () from /usr/lib/libkmid.so.0 #7 0x40043538 in kmidClient::setMidiMapFilename () from /usr/lib/libkmidpart.so.1 #8 0x40040efc in kmidClient::kmidClient () from /usr/lib/libkmidpart.so.1 #9 0x4003cebe in kmidFrame::kmidFrame () from /usr/lib/libkmidpart.so.1 #10 0x08049445 in __register_frame_info () #11 0x40df40bf in __libc_start_main () from /lib/libc.so.6 Any ideas? HS - -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qYoIzvr6q9zCwcERAjUDAJ9i8g3MTW8k7pDuiE41/AHapuULSQCfU8t1 IN/n980/N3wkPbW7003avFU= =XcPa -END PGP SIGNATURE-
Re: Konqueror + Debian + IPv6?
Felix Homann wrote: > As I've told before there has been a complain about this already > somewhere. Unfortunetly I can't remember where (I think at depianplanet, > but can't find it anymore). He made a very detailed analysis of the > problem. (It could have been assigned to DNS lookups vi IPv6 as well. All > I remember is that it had to do with IPv6...) It was on this list: http://lists.debian.org/debian-kde/2002/debian-kde-200207/msg00109.html Very annoying problem. I get the same with, e.g. www.theregister.co.uk, sometimes www.heute.de and others... - Gerrit
Re: KDE3 - Debian/experimental distribution proposal (was: yes i am alive ;)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 13 October 2002 12:25 pm, Ralf Nolden wrote: > > Now, let's please be reasonable about what can be done easily and what is > desireable. Have a quick look at the current state: > Could I just clarify something about objectives. It seems to me that there are two slightly different objectives which should drive the way the effort is organised. It seems to me a desire to handle the gcc 3.2 transition is somehow preventing the second objective being met. The two objectives are 1) From a kde perspective, ensuring the debian community has an up to date version of kde. Given this perspective the idea is to provide debs from kde.org a) To support woody as the primary underlying system but presumably also the other sets of debian systems (ie from debian's testing or unstable sections) with the latest stable version of kde b) Later, providing "bleeding edge" .debs though an automated approach on kde.org Given these two perspectives the current approach of using kde.org seems well founded. Just one minor thing ... Would it be possible to avoid putting the release number in the directory heirarchy - so that the sources.list line has to be edited for each release. Just use the distinction between stable (currently 3.0.4 - presumably in the not too distant future 3.1) and unstable (currently 3.1 beta 2 - but, could be regular snapshots of cvs if the package build could be automated). 2) From a debian perspective of having a full range of kde options (stable, testing and unstable) in a standard debian archive so that anyone building a debian system has a knowledge of where to find what he is looking for. a) Woody remains super stable and at the moment remains kde 2.2 b) Sarge ideally should have a relatively recent but stable kde (ie kde 3.0.3/4). Unfortunately nothing gets into sarge that has not been in unstable for a while is getting into unstable therefore nothing is flowing to testing. c) Sid - unstable. I was looking at the CVS debian/control file for qt earlier this week and it looked as though it was being set up to create separate package names for the gcc 3.2 packages - so that ultimately it would be possible for 2.95 and 3.2 packages to sit side by side in the distribution (although the user would only be able to pick one set because of conflicts) What I don't understand is why qt/kde packages compiled with gcc 2.95 (ie precisely those currently up on kde.org as 3.0.4) could not flow into unstable now whilst the work to create these extra packages gets completed at which point the debian release number gets incremented and a whole new set of packages appear from the same source build. The other question I raise is, is there a way that all the other talent out there who have created these other sites with packages on could join in the work to make the transition to 3.2 more quickly (does it need cvs access or could a mailing list be created where people could post patches). - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qZ4fuFHxcV2FFoIRAhaVAJ9IAt+RRNqtUvubkOqYdKB/1kd5/gCff3WT FL2HM9ChjvoC0nYCq4rIkSU= =EocC -END PGP SIGNATURE-
Re: Konqueror + Debian + IPv6?
Thank you, Gerrit. This was indeed the post i was looking for. In the meantime it's author, Scott Zuk, sent me an email to inform me about the original post and give me some further information. I asked him for permission to put his email here on the list, but since I haven't got a reply by now (it's Sunday, I guess he's got better things to do than reading and replying to email all day!! ) here's an excerpt (I think that's legitimate) telling me how he handles the problem: " I had to fix this myself by recompiling kdelibs. You can download the kdelibs source tarball off the kde mirrors and check the debian/rules file. Look for the place where the option --with-ipv6-lookup=yes is set and change it to no. Recompile kdelibs using dpkg-buildpackage, check the man page for any options you might need and any build depends. You should end up with new debs of kdelibs that you can then install with dpkg. Personally, I have to rebuild kdelibs for every release to get rid of this annoying problem. " I will give this a try. Hopefully this option finds its way into the (semi-)official debs soon. Thank you, Scott. Great help! Felix
Re: Konqueror + Debian + IPv6?
I've just rebuild kdelibs. Now everything is fine. Thank you, Scott, again. Felix
how to turn off konsole beeping?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I use KDE3.0.4 and want to turn konsole beeping off. Sadly, it used the same sound as kmail does for new messages, so I cannot turn it off in kcontrol. I tried: xset -b setterm -blength 0 but it did not help. Any suggestions? HS - -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qegEzvr6q9zCwcERAuTVAJ0WeFSag79I/YNLELbArfWi/nWBGQCeJN/y xBQXTjt4gAxBYY4BOjl5Lno= =BCwx -END PGP SIGNATURE-
Re: how to turn off konsole beeping?
Hi, you can do that thru konsole menu. [Menu]->Settings->Bell->None Hope this help. WBR, Vyacheslav Monday 14 October 2002 00:39, Hendrik Sattler ÑÐÐ: > Hi, > > I use KDE3.0.4 and want to turn konsole beeping off. Sadly, it used the > same sound as kmail does for new messages, so I cannot turn it off in > kcontrol. > > I tried: > xset -b > setterm -blength 0 > but it did not help. > Any suggestions? > > HS > > -- > Mein GPG-Key ist auf meiner Homepage verfÃgbar: > http://www.hendrik-sattler.de oder Ãber pgp.net > > PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org -- With best wishes, Vyacheslav +(380)-67-7049233
Re: [debian-kde] List configuration & usability
On Thu, Oct 10, 2002 at 10:19:56AM +1000, Nigel A. Chapman wrote: > The list does not prefix its postings with the list name, eg. > [debian-kde] (as in my subject line). This makes the postings very > difficult to visually distinguish from the couple of dozen spam messages > in my inbox. I administer a number of yahoogroups and mailman lists, > and believe this to be sufficently 'standard' that I'm surprised not to > find it on the debian lists. AFAIK, it's a deliberate decision by the list admins. A lot of people just find it annoying to waste space in the subject line, given how trivial it is to filter mail from lists into specific folder... I use mutt and adding [debian-kde] to each subject line would take away about a third of the available subject space. I think that space would be much better spent describing the subject of your email:) > It has occurred to me that I could probably set up filtering in Mozilla > to use the X-Loop (or some other) header as a send-to-a-folder criterion > to get around this, but (1) there will be lots and lots of potential > users who wouldn't think of that, (2) no other list I subscribe to > requires this and (3) I'm not yet sure of the value of belonging to this > list, due to this problem, so I'm not too inclined to spend a much time. > looking into that. Maybe that's lazy, yes. :) I've found the Debian lists to be some of the friendliest around. If you ever need help with general Debian issues, debian-user will sort you out, while here is for KDE specific stuff. -rob pgptVgiGL56i7.pgp Description: PGP signature
