Advertisement
Inexpensive and reliable 750+ MB/s storage
Fast storage & processing: iSCSI, NFS, SMB/CIFS, clusters for financial, media, HPC, research, virtualization
Weekly Edition
Return to the Press pageSponsored link
Vyatta –
Linux & Open Source
Alternative to Cisco –
Advanced Routing,
Firewall, VPN, QoS..
Free Download ->
| |||||||||||
KDE 4 developers look toward new desktop possibilities (NewsForge)
Stephen Feller
discusses the changes coming to KDE 4 in a NewsForge article.
"Developers on the projects expected to make up the next major version of the K Desktop Environment (KDE) want KDE 4 to offer features and software interaction beyond what is available now, and better, easier access for users to their files and information. Among the ideas are universally available personal information and a desktop that is tailored for and responds to the things users do most. Ian Geiser, a KDE developer and official US representative for the KDE project, says KDE 4 will most likely be released in late 2006, though internal debate could push the release back to early 2007. Developer Till Adam says developers are still trying to figure out the combined vision for KDE 4, and how everything fits together."
(Log in to post comments)
Question: Posted Feb 17, 2006 0:16 UTC (Fri) by hummassa (subscriber, #307) [Link] Where do I post the following:""" I use two kdm sessions at once, one for me and the other for my wife. When I insert a removable media, both sessions try to automount it, and hilarity ensues (actually, it's not funny). I would like very much if only the "foreground" (shown vt) session got the events -- or, better yet, if we could program the "routing" of the events for the sessions (like, camera inserted, try H's session, then I's session; CD inserted, try "foreground" session, etc. etc.) """ ???
Question: Posted Feb 17, 2006 1:26 UTC (Fri) by Richard_J_Neill (subscriber, #23093) [Link] I don't know how to fix this properly, but you could always turn off the automounting alltogether. Which program is responsible? Is it KDE? (I think only KDE3.5 does this). Is it hotplug? Is it gnome-removeable-storage (used by Mandriva for KDE <= 3.4)? It could even be automount as a system service, or, for CDs, supermount.
Personally, I think automounting is a nice feature in simple setups, but for complex setups, or for advanced users, I'd disable it. My guess is that this is a distro bug, not really a KDE bug.
if it's a KDE bug... Posted Feb 17, 2006 7:34 UTC (Fri) by niner (subscriber, #26151) [Link] ...then http://bugs.kde.org would be the right place to post it with your questions answered.
Stopping automount Posted Feb 18, 2006 23:52 UTC (Sat) by hummassa (subscriber, #307) [Link] Yes, that's what I do... but I really would like a more elegant solution.
Question: Posted Feb 17, 2006 10:19 UTC (Fri) by raf (guest, #35151) [Link] Not to be outdone... GNOME has the same feature.
Question: Posted Feb 19, 2006 23:35 UTC (Sun) by Ross (subscriber, #4065) [Link] This really bothers me. Why is the GUI so tightly intertwined into the hotplug event handling? This seems like an unnatural way to handle things, and the proposed solution is only slightly better. What if you want the background session to get the event? What if you have a dual-headed system with two sets of keyboards, mice, and monitors?
The auto-mounting support should be handled either in-kernel or through a daemon, with an API for applications to receive notifications, and not directly handled through the windowing system.
Question: Posted Feb 24, 2006 1:57 UTC (Fri) by zlynx (subscriber, #2285) [Link] It is handled through daemons and messaging, Ross.
HAL has a daemon called hald. This little guy hooks into the kernel hotplug service and then uses DBUS to send messages about hardware events to anyone that cares to listen. Right now, that is the KDE and Gnome GUIs, mostly.
The problem is: Posted Feb 24, 2006 15:16 UTC (Fri) by hummassa (subscriber, #307) [Link] HAL is sending the wrong DBUS/DCOP messages to the wrong recipients... ANDthe recipients aren't acting right on the messages. In my case, I would like HAL to send the messages only to the "foreground" guy; and the "foreground" guy should receive just a minor visual notification (tray area) and/or an update if one of his file managers point to /media/cdrom... This thing is the only thing in KDE I consider "crude". The rest of KDE, to me, is Just Perfect (tm).
The problem is: Posted Feb 24, 2006 16:50 UTC (Fri) by zlynx (subscriber, #2285) [Link] DBUS doesn't decide who to send things to. It sends them to any program that wants to listen to those messages.
It should be the responsibility of KDE to notice that it isn't running on the active terminal, and not mount the CD.
I'm positive that you can change KDE options so it doesn't auto-mount your CDs, if you don't want it to. I'm not sure about providing visual notification but what would be the point, since you would know you had just plugged in a CD or USB drive.
The problem is: Posted Feb 26, 2006 14:35 UTC (Sun) by job (subscriber, #670) [Link] If that's true that represents a serious security hole. Only the processed with the right privileges should receive these events. And the right privileges in this case should be set by the login program (the display manager).
|
|||||||||||