Amarok, KMix: how to set sound volume for external audio adapter?
After quite some time I've looked at Amarok again now that 2.3 has made it into unstable. Somehow, I'm missing a way to set the sound volume. I didn't find a volume slider in Amarok itself and KMix, too, doesn't show any controls for my external Edirol UA-1EX sound adapter. Phonon does recognize the external adapter, it happily plays sound through it and it is displayed in the Multimedia System Settings. KMix does show tabs for the internal "HDA Intel" adapter and for my external webcam (Logitech QuickCam Pro 9000). However, the tab for the webcam contains no controls, older version of KMix/KDE did have controls there. I have already deleted ~/.kde/share/config/kmix*, but that didn't make a difference. Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003151816.23491.mich...@schuerig.de
Re: Akonadi-MySQL Issues
On Monday 15 March 2010, George Kiagiadakis wrote: > On Sun, Mar 14, 2010 at 2:28 PM, Dominik Schulz wrote: > > 2.) Akonadi backup > > Another issue is also related to MySQL. Since MySQL/InnoDB is used > > as an Akonadi backend, it troubles me how to properly backup user > > profiles in a multi-user setup. Right now I'm just backing up the > > users homedirs which covers most personal data and applicatin > > profiles, but with InnoDB this becomes difficult w/o LVM Snapshots > > (which aren't available on all systems right now). How is the > > akonadi db supposed to be backed up? Or is the information in the > > db no vital to akonadi and shouldn't backed up at all? The akonadi > > documentation seems to point this way, but I'm not sure. > > Well, since akonadi's database is stored in ~/.local, if you backup > the whole home dir, akonadi's db should be backed up too. That, unfortunately, is a misconception. If you just copy the database files while akonadi is running, you're in no way guaranteed to get a consistent snapshot. The clean way to backup a database is to transactionally dump its contents. > The only > problem is that the database is huge; it's at least 100MB (!!!) when > it's created for the first time and keeps growing (On my > university's lab the admins have disabled akonadi just because of > that, to save space) On a personal computer, I don't see the size itself as a problem. However, regarding backups, there's no way to make small, incremental backups. Tools such as rsnapshot (that keep hardlinks to unchanged files in a snapshot) are thwarted, too. BTW, it's not just akonadi that's affected by this problem, amarok has started to use an embedded MySQL engine, too. Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201003151308.18875.mich...@schuerig.de
Re: Akonadi-MySQL Issues
On Sun, Mar 14, 2010 at 2:28 PM, Dominik Schulz wrote: > 2.) Akonadi backup > Another issue is also related to MySQL. Since MySQL/InnoDB is used as an > Akonadi backend, it troubles me how to properly backup user profiles in a > multi-user setup. Right now I'm just backing up the users homedirs which > covers most personal data and applicatin profiles, but with InnoDB this > becomes > difficult w/o LVM Snapshots (which aren't available on all systems right now). > How is the akonadi db supposed to be backed up? Or is the information in the > db no vital to akonadi and shouldn't backed up at all? The akonadi > documentation seems to point this way, but I'm not sure. Well, since akonadi's database is stored in ~/.local, if you backup the whole home dir, akonadi's db should be backed up too. The only problem is that the database is huge; it's at least 100MB (!!!) when it's created for the first time and keeps growing (On my university's lab the admins have disabled akonadi just because of that, to save space) -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ba4a6e221003150247k6bd933b9i595d2f51fac12...@mail.gmail.com
Re: Akonadi-MySQL Issues
On 2010-03-14, Sune Vuorela wrote: > On 2010-03-14, Dominik Schulz wrote: >> 2.) Akonadi backup >> Another issue is also related to MySQL. Since MySQL/InnoDB is used as an=20 >> Akonadi backend, it troubles me how to properly backup user profiles in a=20 >> multi-user setup. Right now I'm just backing up the users homedirs which=20 >> covers most personal data and applicatin profiles, but with InnoDB this bec= >> omes=20 >> difficult w/o LVM Snapshots (which aren't available on all systems right no= >> w).=20 >> How is the akonadi db supposed to be backed up? Or is the information in th= >> e=20 >> db no vital to akonadi and shouldn't backed up at all? The akonadi=20 >> documentation seems to point this way, but I'm not sure. > > Akonadi is a data cache, not a data store, so by nuking the DB you are > only losing the bandwidth spent fetching it in the first place. Or well. it is also containing data changed that still haven't been replayed to the real storage. E.g. some offline imap handling. It shouldn't be needed to backup the db. /Sune -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnhpru58.nfa.nos...@sshway.ssh.pusling.com