Suse 9.1, KDE 3.3, Sound card SB Live 5.1, using ALSA.
Since i've updated my 9.1 to KDE 3.3 from the Suse DTP site, I have to "su"
and run "alsactl restore 0" to get sound. Prior to this update to KDE it
always worked fine.
I've placed this command in the "/etc/init.d/boot.local" but that does not
seem to do the trick.
What i have done:-
Run "alsamixer" to get the sound as I want it.
Run "alsactl store 0" (as "su")
Run "alsactl restore 0" (as "su") and the settings are restored
The "asound.state" file is -
-rw-r--r-- 1 root root 42230 2004-08-27 22:43 /etc/asound.state
I've also tried using "kamix" - i can set the sound for the session ok but on
reboot, the settings are back to zero
Any pointers would be welcome.
> weird, I had this problem *before* I upgraded to kde3.3
>Try kmix instead of kamix. That seems to have solved it for me.
That worked a treat. Thanks.
But can you control/mute the volume from the system tray icon? I can't seem
to do it. The slider moves but no change, the button pressed crosses out the
icon but volume is unchanged.
On Friday 27 August 2004 13:01, suse-kde-help(a)suse.com wrote:
> Hi! This is the ezmlm program. I'm managing the
> suse-kde(a)suse.com mailing list.
> I'm working for my owner, who can be reached
> at suse-kde-owner(a)suse.com.
> To confirm that you would like
> removed from the suse-kde mailing list, please send an empty reply
> to this address:
> Usually, this happens when you just hit the "reply" button.
> If this does not work, simply copy the address and paste it into
> the "To:" field of a new message.
> or click here:
> I haven't checked whether your address is currently on the mailing list.
> To see what address you used to subscribe, look at the messages you are
> receiving from the mailing list. Each message has your address hidden
> inside its return path; for example, mary(a)xdd.ff.com receives messages
> with return path: <suse-kde-return-<number>-mary=xdd.ff.com(a)suse.com.
> --- Administrative commands for the suse-kde list ---
> I can handle administrative requests automatically. Please
> do not send them to the list address! Instead, send
> your message to the correct command address:
> For help and a description of available commands, send a message to:
> To subscribe to the list, send a message to:
> To remove your address from the list, just send a message to
> the address in the ``List-Unsubscribe'' header of any list
> message. If you haven't changed addresses since subscribing,
> you can also send a message to:
> For addition or removal of addresses, I'll send a confirmation
> message to that address. When you receive it, simply reply to it
> to complete the transaction.
> If you need to get in touch with the human owner of this list,
> please send a message to:
> Please include a FORWARDED list message with ALL HEADERS intact
> to make it easier to help you.
> --- Enclosed is a copy of the request I received.
> Return-Path: <michael(a)weblore.com>
> Received: (qmail 18127 invoked from network); 27 Aug 2004 18:01:13 -0000
> Received: from unknown (HELO hermes.suse.de) (126.96.36.199)
> by 0 with SMTP; 27 Aug 2004 18:01:13 -0000
> Received: from scanhost.suse.de (scanhost.suse.de [188.8.131.52])
> by hermes.suse.de (Postfix) with ESMTP id 0002968E26
> for <suse-kde-unsubscribe(a)lists.suse.com>; Fri, 27 Aug 2004 20:01:12 +0200
> (CEST) Received: from hermes.suse.de ([184.108.40.206])
> by scanhost.suse.de (scanhost [220.127.116.11]) (amavisd-new, port 10025)
> with ESMTP id 04264-08 for <suse-kde-unsubscribe(a)lists.suse.com>;
> Fri, 27 Aug 2004 20:01:10 +0200 (CEST)
> Received: from Cantor.suse.de (cantor.suse.de [18.104.22.168])
> (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
> (No client certificate requested)
> by hermes.suse.de (Postfix) with ESMTP id 4D98F694CC
> for <suse-kde-unsubscribe(a)suse.com>; Fri, 27 Aug 2004 20:01:10 +0200
> (CEST) Received: from ms-smtp-05-eri0.texas.rr.com (ms-smtp-05.texas.rr.com
> [22.214.171.124]) by Cantor.suse.de (Postfix) with ESMTP id D2CF4B1B5DC
> for <suse-kde-unsubscribe(a)suse.com>; Fri, 27 Aug 2004 20:01:09 +0200
> (CEST) Received: from photon.local (cs241749-55.houston.rr.com
> [126.96.36.199]) by ms-smtp-05-eri0.texas.rr.com (8.12.10/8.12.7) with ESMTP
> id i7RI16Bu014229 for <suse-kde-unsubscribe(a)suse.com>; Fri, 27 Aug 2004
> 13:01:07 -0500 (CDT) From: Michael Satterwhite <michael(a)weblore.com>
> To: suse-kde-unsubscribe(a)suse.com
> Subject: Unsubscribe
> Date: Fri, 27 Aug 2004 13:01:06 -0500
> User-Agent: KMail/1.6.2
> MIME-Version: 1.0
> Content-Disposition: inline
> Content-Type: text/plain;
> Content-Transfer-Encoding: 7bit
> Message-Id: <200408271301.06589.michael(a)weblore.com>
> X-Virus-Scanned: by amavisd-new at scanhost.suse.de
> X-Spam-Status: No, hits=-1.4 tagged_above=-20.0 required=5.0 tests=BAYES_20
Yesterday (17/8) I updated KDE to supplementary/KDE/update_for_9.1/. That is
KDE-3.3.0, presumably a prerelease because KDE did not release 3.3.0
officially. From that moment on I have problems with kicker.
1) Upon startup only a few icons appear in the System Tray.
This problem disappears temporarily after executing 'dcop kicker kicker
If I start another application that would put an icon in the System Tray, I
see it only after restarting kicker.
2) If I start an application (e.g. Konqueror, Knode), the Taskbar remains
empty. No application button.
Also this problem disappears temporarily after executing 'dcop kicker kicker
If I start a new application, the application's Taskbar button does not appear
until kicker is restarted.
If I close an application, the application's Taskbar button does not
disappear, but another button gets the focus.
Please note that I had no problems with the prerelease KDE-3.3.0 before 17/8.
Does anybody else have these problems?
With kde 3.3, OpenOffice doesn't work :(
soffice.bin: kdecore/kcmdlineargs.cpp:159: static void KCmdLineArgs::init(int,
char**, const KAboutData*, bool): l'assertion « argsList == 0 » a échoué.
Suse need to rebuild it for kde 3.3 and put it in kde directory!
After upgrading to KDE 3.3.0 via apt dist-upgrade, I can no longer use accents
in Lyx (neither in KOffice): they're now treated as letters. Instead of
accents in French or Spanish words, KMail now shows two empty boxes in
incoming e-mails. However, I can still type accents in OOffice and Abiword. I
have not touched the keyboard settings, neither in Yast nor in KDE's Control
Help will be greatly appreciated.
After update KDE to 3.3, Kopete won't connect, I'm using dante socks cllient.
After downgrade to old version kopete works fine, newest version not working.
Maybe anyone has any suggestions?
No one have any ideas for this problem? I suppose just running a
script when I login to KDE would do it but is there something built in
to handle this?
>I run KDE. Everything looks great but Mozilla and Evolution. The
>font sizes do not line up with the rest of my applications. I ran
>gnome-font-properties and they start to look fine. I have to run this
>after everytime I restart. How can I make whatever
>gnome-font-properties does permanent?
I've upgraded from SuSE 9.0 to 9.1 using an ftp-server.
How can I upgrade from KDE 3.2 to 3.3 using the same ftp-server from within
I've tried to change the installation source to the ftp-server but YaST does
not accept the server (or maybe it is the directory on the server that is
wrong, I've tried many different choices).
I get the message "ERROR(Inst Src:E_noinstsrc_on_media)".
Does anyone know what I have to do?
If it is not possible to do what I want, could someone please tell me what is
the most convenient way to keep an up to date kde installation in SuSE?
I am unable to get Konsole to retain my setting for how to deal with the
Bell (CTRL-G). Every time Konsole is restarted (upon login as part of my
remembered session), the Bell setting reverts to "System Bell" and I have
to manually change it, on a tab-by-tab basis, to "System Notification".
I found I had the same problem with the history setting reverting from the
5000 I'd set to 1000 (possibly a default, possibly a change I had made
earlier) but by editing the Konsole "rc" file
("$HOME/.kde/share/config/konsolerc"), but that technique does not seem
to be working with the Bell problem.
Can anyone shed some light on this? Is there a known work-around?