Image 01


Marcel Hasler Cologne, Germany
Audio Apps
Plasma 5 Multimedia
System Software
KDE CDEmu Manager

System Software 56 comments

Score 71.7%
Nov 24 2017
I'll update CDEmu Manager once I've switched to Plasma 5 myself. - Jan 06 2015
Added, thanks. - Feb 12 2012
Fixed. Thanks! - Sep 04 2010
Thanks for the hint. I've fixed it for the next release. - Dec 11 2009
Sorry I didn't notice your post before. Can you reupload the translations or just send them to my email address?

Thanks. - Dec 04 2009

I originally planned to call it KCDEmu but as it turned out, the name was already taken. There's a KDE3 frontend that goes by that name, although it apparently hasn't been maintained for years. I thought it would be better to chose a new name rather than just stealing the name and causing confusion.

Btw, it's nice to see this in Portage:-) - Dec 04 2009
Added. Thanks for your contribution. - Feb 22 2009
Try this:

cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` -DCMAKE_MODULE_PATH=`kde4-config --prefix`/share/apps/cmake/modules . - Feb 22 2009
Your translations will be included in the next release.
Could you also have a look at the kde_cdemu.desktop and kde_cdemu_mount.desktop files and translate those? It's only three lines so you can just post them here.
Thanks. - Feb 22 2009

Email 148 comments

Score 70.0%
Jul 09 2012
I can reproduce this behavior when Konqueror is set as default browser and KGmailNotifier is configured to use the default. It should work if you configure KGmailNotifier to use Konqueror explicitly. I'll try to fix this in the next release. - Mar 11 2013
Thanks for the report. I just uploaded a small update. Does this fix your problem? - Jul 09 2012
The instructions are correct. Most likely you don't have all the development files installed that are required for building KDE software. You should post the output of your failed compilation attempt so other people can help you. - Dec 20 2009

Storing passwords in plain text is a really bad idea and I have no plans on reintroducing that "feature".

Sorry. - Dec 14 2009

Please do so. I'll be happy to include your translations in the next release.

Thanks. - Dec 09 2009
I rewrote and simplified the wallet handling code and released the update. If you have a chance to compile it yourself, please test it and let me know whether it works for you. Thanks. - Dec 03 2009
After further review I realized that the code responsible for handling the KDE wallet does gives room for potential race conditions. I've (hopefully) fixed that problem and will release an update shortly. Although the crash you are having also seems to be triggered by the same code (judging by the backtrace you posted), I doubt the two issues are related, since it would require KGmailNotifier to try and access the wallet the same moment it is terminated by KDE's logout routines. However KGmailNotifier only accesses the wallet once when it is started or whenever it's configuration is changed through the settings dialog. There should be no access to the wallet on termination.

Anyway, unless other people, using other distributions, encounter the same crash, I have no other choice but to consider this an Ubuntu-specific bug for now and leave it up to them to dig deeper (and possibly prove me wrong).

Best regards
Marcel - Dec 02 2009
The backtrace you've posted points to a bug in KDE/Qt. Whether it is an upstream bug or whether it is caused by a patch by the Ubuntu people I cannot tell, but I'm afraid I cannot do anything about it. Sorry. - Dec 01 2009
I just saw that I misread your comment. Filing a bug at Ubuntu probably won't help much if you compiled KGmailNotifier yourself (although it still could be a bug in Ubuntu's KDE packages).

Either way, the output and core dump would be helpful to find the cause of the crash. - Nov 30 2009

I'll need a some more information, since I can't reproduce that crash myself. You can try and run it from the command line and redirect the output to a file. That way the output could be analyzed on next login. Try running it e.g. like this:

kgmailnotifier --nocrashhandler --nofork > kgnout.txt

The --nocrashhandler option should cause a core dump file to be created which can then also be analyzed with gdb.

Since you're using a precompiled package you should also file a bug report for your distribution. It should be up to them to determine whether it's a distro-specific bug or an upstream bug.

Thanks. - Nov 30 2009
Upgrade to KDE 4.3 if possible.
KDE 4.2 is just too buggy, I'm afraid I really can't provide support for it. - Sep 11 2009
I have been considering all this already when KGmailNotifier was still in it's infancy and even had support for multiple accounts implemented once, but then decided to drop the idea.

When you write an application you always have to decide who your targeted users should be. When it comes to email there are people who just have one personal account for sending and receiving mail and who just like to have a simple, little tool to tell them whether they have new mail or not (so they don't have to check themselves all the time). Personally, I belong to that group. Then there's the other extreme, that is people who would probably like to completely administer all there 20 accounts from 20 different providers from their system tray (well, that might be a bit exaggerated but you get the point). And of course, there are also all gradients in between.

So the point is, that I decided to write an application for the first group of people and I'm sticking with that decision. After all, no matter how many features you include in an application, some people will always want more and eventually you will have to draw the line at some point, anyway.

Besides, there already is a fantastic tool available for KDE that provides just the features you are asking for, and that tool is called "Akregator"!

Best regards
Marcel - Sep 11 2009
It worked for me when I tried it on Kubuntu just now. Just make sure you have GNU msgfmt installed (apt-get install gettext) otherwise the translation files won't be built. - Jun 04 2008
Hmm, apparently the polish string is too wide for the space available and therefore is split on two rows. This can also depend on the main font used on the system (some use wider and some more narrow fonts). I'll see if I can find a way to have the popup window adjust the overall font size automatically depending on the font width and string length.

Thanks for bringing this to my attention. - May 26 2008

Utilities 129 comments

Score 79.3%
Nov 19 2011

This sounds like a bug within KDE's power management. I don't see how KOSD could produce such an error. Try running qdbusviewer (should be installed as part of Qt), select org.kde.Solid.PowerManagement on the left and navigate to org/kde/Solid/PowerManagement/org.kde.Solid.PowerManagement on the right. Click on 'Method: brightness' after changing the brightness with your keys. Does this produce the same error? If so, you should file a bug report for KDE.

Best regards. - Sep 21 2012
You need to specify the SVG elements you want to show.

If you want multiple lines, you can use <br> for a line break.

The progress bar is always visible.

Here's an example:
qdbus org.kde.kded /modules/kosd showSvgOsd icons/battery "(" "Battery" "Fill60" ")" "Hello<br>World" 50 - Jan 31 2011
The methods for showing the OSD are exposed via D-Bus. See org.kde.kded -> /modules/kosd. - Jan 29 2011
Thanks for the hint. This should be fixed in 0.6.2. - Jan 29 2011
You'll need KDE SC 4.5 for KOSD 0.6.0 and 4.6 for KOSD 0.6.1. You should really upgrade your KDE installation. - Jan 27 2011
Try again with KOSD 0.6.1. - Jan 27 2011
You can already do that.
'kosd --configure' -> Appearance - Aug 07 2009
You may need to unbind the keys from KMix first. After that it should work. - Jul 20 2009
Should work correctly now in 0.4.1.
Thanks for the hint. - Feb 19 2009
I believe you need to install kdebase-workspace-dev. - Feb 19 2009
I'm afraid building KOSD inside a build directory doesn't work because some files are generated automatically on-the-fly and these files have to be in the same directory as the other source files. You'll have to build KOSD as shown in the description above.
Hope that helps. - Feb 19 2009
Ok. I think I know what causes this. Some sound cards provide a finer-grained control over the volume than others. For example my sound card provides absolute volumes from 0-127. Other cards provide less.

You can find out which range your sound card provides by running this command:

qdbus org.kde.kmix /Mixer0 org.kde.KMix.absoluteVolumeMax Master:0

What does this give you?

The point is that when your sound card doesn't provide small enough volume steps then changing the volume by a small percentage (such as 1-3%) doesn't change anything.

I'll see if I can find a way to set the smallest volume step KOSD allows to the smallest step supported by individual sound cards. - Feb 19 2009
That's strange. I can't reproduce the problem here. Can you tell me what distribution and KDE version you are using? - Feb 19 2009
Thanks for the feedback.
Can you tell me what the meter/progressbar displays? Does it show the right volume? Or the wrong volume or nothing? - Feb 19 2009
Should be fixed in 0.2.3.
Apparently your smaller screen is set as primary screen. I of course don't know your screen arrangement, but I would consider making the bigger screen the primary one.
Best regards. - Jul 31 2008
Hi. I've been able to reproduce this. It looks like KOSD crashes when you try to open the configuration dialog before KMix is running (or fully initialized). I'll fix this problem for the next release.
Thanks. - Jun 07 2008
1) Does manually changing the volume via DCOP work correctly? E.g. if you run this:
dcop kmix Mixer0 setVolume 0 50
dcop kmix Mixer0 volume 0

I know that changing the volume through KMix via DCOP doesn't work for all channels on all mixers, but that's something that's out the scope of what I can fix.
Does changing the volume step not have any effect at all? Or just the wrong effect?

2) If all necessary kernel modules are loaded and your hardware supports reporting the battery status (which probably should be the case) then the information will be available somewhere in the /sys directory. However the exact location and names of the virtual files containing the information can depend strongly on the drivers used by your system. The default path should work with the default battery driver but your system may need a more hardware-specific driver (such as acer_acpi or asus_acpi). These drivers may report the battery status through different files. See if you find a directory called BAT, BAT0 or similar in /sys and see which of the files in that directory look most appropriate. I'm afraid that's all the help I can give on this matter.

3) You can use KOSD on KDE4 as long as you have the KDE3 libraries installed. I will start porting KOSD to KDE4 once 4.1 is out (maybe earlier). I guess it shouldn't take to long to port. - Jun 06 2008
What shortcuts are you using?
Did you set up your shortcuts in the KOSD configuration dialog? - Jun 04 2008
This is partly a problem with KOSD. KOSD allow you to select your mixer device (basically your sound card, if you have more than one) but you cannot select which channel to use on the selected device. The problem is that KMix doesn't provide any information concerning the output channels to other apps and so KOSD currently always controls the first channel, which on most (but unfortunately not all) cards is the 'Master' channel.

I've been thinking about adding an option allowing users to manually select a channel, however since KMix doesn't provide any information about which channels are available or how they are called ('Master', 'PCM', etc.) it's not so easy to provide a selection box in KOSD's configuration dialog. So all that's possible would be for KOSD to find out which channels are available and let the user select one. However the channels could only be identified as 'Channel 0', 'Channel 1' etc. which isn't really very user friendly.

Anyway, I'll see what can be done about this. I'll try to come up with at least some kind of solution for the next release. - May 30 2008
Probably the line 'brightness=$(xbacklight -get)' is wrong in the script. Since xbacklight doesn't work on my system, I don't know what 'xbacklight -get' usually returns exactly. You might have to filter the output somehow to get only the brightness in percent. - May 30 2008
This is a general limitation of KDE/Qt/X11. I'm having the same problem. When a XF86* event is mapped to two or more keys, then KDE will only report one of them (on my system it's always the one with the smaller keycode). I worked around this problem by assigning my brightness keys to two different and otherwise unused XF86* codes (in my case XF86Launch0/1) and then setting those in the KOSD configuration dialog.

This is a bug in 0.1.3 (although not everyone is affected by it). It should be fixed in 0.2 (which I will release soon). - May 29 2008
* It doesn't react at all if a kicker menu is open.
This is a general problem and not specific to KOSD (you can test it with Amarok or just Ctrl+F1/F2 etc. None will work as long as a menu is open.)

* being able to alter the displayed text
i18n support will be added later, other than that, you'll just have to make your changes in the source files. I'm not planning to make strings configurable ("configurability" is a good thing but that's just overkill)

* being able to alter the font of the displayed text
I'll change it to use the standard system font. I might add a font chooser in a future version

* being able to change the displayed icons via gui
I'm planning to add icon theme support for the next version

* a preview button to check on the changes made to the appearance
I'll think about it, but it's really a lot more complicated than it sounds.

* being able to alter the displayed box (edgy/round corners, frame thickness)
Maybe in a future version.

* being able to alter the steps by which the volume is increased or decreased
That I have planned for the next version.

About the OSD placement, it's currently only displayed on the primary screen, I'll see how that can be improved in a future version. - May 27 2008
Did you run 'make -f Makefile.cvs'? - May 27 2008
Hi. Thanks for the kudos:-)

Just a few comments:

* Dualscreen
I'm planing to add support for this in a coming release

* Placement
This could be a bug. I'll have a closer look on this.

* Brightness & Battery
There just isn't a single solution that will work on every imaginable system, but the DCOP interface added in 0.1.2 should help on systems that don't provide this information the usual ways

* Missing events
I'll be adding more actions/events in future versions

* Customization
You can of course replace the icons with your own before installing. I'll try to make KOSD a bit more themeable in a coming release

* Internationalization
I'll add i18n support soon (I'll also provide the German translations myself)
- May 26 2008
It's supposed to show up when you press a button on your laptop or keyboard. You just have to configure which button or key you want to do what.
Also read some of the other posts. Some common problems have already been explained there.

BTW, I only just added the 'make -f Makefile.cvs' line to the description a few hours ago, so it's not your fault:-) It's only necessary on systems which only provide automake 1.10 (but also doesn't harm on such with automake 1.9). - May 26 2008
MPD Now Playing

Plasma 5 Multimedia 7 comments

Score 62.5%
Nov 19 2017
Thanks! I'll include them in the next release. - Sep 12 2010
No. But a "now playing" plasmoid for Amarok is already included in KDE SC. This one is really meant as an equivalent for MPD users. - Sep 10 2010