The KDE NetworkManager tray icon does not show WiFi signal strength in dark themes like Oxygen and Androbit. In bright thems like Aya the WiFi signal strength indicator is visible.

I read your posts. I don't usually agree with you but I do on this one. Worst come worst you can always revive the old project of porting Netbds's pkgsrc to Slackware. Unfortunately I don't have either the skills or the time.

Is udev setting the correct permissions on /dev/shm at drwxr-xr-x ?

Real time audio, e.g. Jack Audio Connection Kit, doesn't have write permission if started as a user of group, root...

Due to unresolved problems reading optical discs, some of us must constantly reload udev's rules which naturally resets permissions to their defaults so modifying rc.local or fstab isn't a solution unfortunately.

I was using my custom built 3.2.28 kernel and the same blueman as that in RC4 (all other packages from a -current snapshot few months ago). My Sony MW600 headset worked flawlessly. But now in RC4 I cannot connect my headset with blueman. In dmesg I see this strange message:
Seems my headset is recognized as an input device.

When I try to use blueman to connect to the A2DP service of my headset, blueman says

Very minor issue, but in 14.0 when using KDE, by default I end up with two bluetooth applets (kde and blueman-applet). I'm not sure how to disable the blueman-applet when KDE is running and enable it in xfce. It doesn't seem like it's being started by either WM/DE.

Very minor, but kinda annoying.

Look in /etc/xdg//autostart?

Fri Aug 24 20:08:37 UTC 2012
This is Slackware 14.0 release candidate 3, and is hopefully the last stop
on our long road to a stable Slackware release soon. After hearing that
the 3.4.x kernel series will have long term support, I tested 3.4.9 hoping
that it would prove stable enough to use that as the release kernel, but
there are problems with an oops in kernel/time/clocksource.c every few boots.
Given that the 3.2.x series has been very stable, it seems prudent to stick
with that for release, and 3.2.28 is going to be the release kernel. So,
one more round of testing. Let me know if there are any problems. Thanks!

I just think the 3.4 kernel is a good choice

Ok, there is an entry there for blueman.desktop in that directory.

Sorry for noobness, I don't know what to do with it in order for it not to start in KDE and start in other environments.

If you don't want the app to start for any users, you can delete the blueman.desktop file. Or you can add the following:

[Desktop Entry]
Hidden=true

If you want only user control, then for each user who doesn't want the app to run, create the following text file in $HOME/.config/autostart:

blueman.desktop

The contents of which is only:

[Desktop Entry]
Hidden=true

I believe Xfce and KDE provide GUI tool to create the user file. I don't know about other desktops or window managers.

If you don't want it to show up in KDE then copy the file to ~/.config/autostart and add the lineto the file.

Ok beautiful, thank you both.

The first thing I do is remove the NetworkManager icon from the system tray and add the NetworkManager widget to the panel, just to the left of the system tray. Shows up very nicely with the darker themes.

1 members found this post helpful.

The same problem --

Attached Thumbnails

   

Not tried yet, but 3.2.28 + udev-182 is causing a 30s delay on startup here. Very, very annoying!

EDIT:
Searching the web for "udev 30 seconds" redirected me to ArchWiki. I tried the solution from there (to add the problematic module, ipw2200 in my case, to the initrd) and everything is ok now.

1 members found this post helpful.

Here you go. Done with the sima84 desktop theme.

Attached Thumbnails