14 Mar
2011
14 Mar
'11
12:26 a.m.
Hi!
At last I made the transition to trinity + squeeze with the last of my boxes,
the infamous office box. I saw my desktop go down in flames (which actually
was the falt of som weired xorg problem) and raise from the ashes 2 days
later. After all I am very satisfied, I didn't loose my kwallet nor my kmail
settings and date - in fact I didn't loose anything important :-)
There is only one issue left, that I was not able to correct: the medium
application autostart does not work as I exect it.
What I got so far:
After I log in, plug in a DVD or USB storage device. Usually there should pop
up a dialog asdking me what medium was found and what to do next. Now that
dialog does not show up.
But when I open konqueror and go to media:/ I see the plugged in device (not
mounted). I can open it from there. I unplug the USB device, the icon
disappears as expected.
I start kcontol, go to "Peripherials/Storage Media", there select
"Defaults"
and "Apply", close kcontrol, plug in the USB storage device and the famouse
dialogbox shows up!
When I log out and log in again the dialogbox does not show up until I open
kcontrol and do these steps.
Now I cannot find what kcontrol does at this stage to make things work. I
tried strace, but kcontol does not change the contents of any file
in .trinity. It opens and reads these files, but nothing is written:
.trinity/share/apps/konqueror/servicemenus
.trinity/share/apps/konqueror/servicemenus/xine-dvd.desktop
.trinity/share/config/kcontrolrc
.trinity/share/config/kdeglobals
.trinity/share/config/khtmlrc
.trinity/share/config/kio_httprc
.trinity/share/config/kioslaverc
.trinity/share/config/medianotifierrc
xine-dvd.desktop plays DVDs, if inserted. At least when I first start
kcontrol ;-)
I made a diff from the ~/.trinity tree befor and after running kcontrol, but
there are no changes.
So, is there a way how I can get the medium autoplay to work?
Nik
14 Mar
14 Mar
4:11 a.m.
New subject: [trinity-users] Problem with medium application autostart
On Sun, Mar 13, 2011 at 4:26 PM, Mag. Dr. Nikolaus Klepp
<office(a)klepp.biz> wrote:
My guess is that your permissions for .trinity got messed up somehow.
You'll need read and write permissions for everything in .trinity (you
should have read and write for your user for everything in his home
anyway). From a terminal (Konsole or whatever you prefer)
ls -l ~/.trinity/share/config
The permissions (rwx) are what matter. You should have rw on them, I
don't think the x should matter for config files since you can't
execute them. If you have rw, then I don't know what's wrong. If you
don't have rw, then you'll need to get them:
chmod -R u+rw ~/.trinity
(don't include the x because not everything needs it and i don't know
what binaries and non-binaries are there that could be affected and
messed up)
(don't include the full path to the files, we want to make sure you
don't run into any other permissions problems by setting rw for
everything to make sure your user can save settings)
*If* it complains that you can't do that, then you'll need root or
sudo to try to give yourself permission:
sudo chmod -R u+rw /home/username/.trinity
(if you don't have sudo priveleges for your user, you'll need root)
(if you are root, you don't need sudo)
Let us know if this helps or not.
--
Kris
"Piki"
Ark Linux Webmaster
Trinity Desktop Environment Packager
12:44 p.m.
New subject: [trinity-users] Problem with medium application autostart
Sorry to say, it's not a permission issue. (.trinity is u+rw and I should see
an error in the strace output if otherwise)
I cannot figure out kcontrol does or does not when I do "Peripherials/Storage
Media", there select "Defaults" and "Apply":
- It does not write any config file.
- It does nothing that shows up in the hal log
- It does nothing that shows up in the dbus log
I'm a bit stuck here :-/
Nik
Am Montag, 14. März 2011 schrieb Kristopher Gamrat:
12:59 p.m.
New subject: [trinity-users] Problem with medium application autostart
On 14/03/11 08:44, Mag. Dr. Nikolaus Klepp wrote:
Maybe you're looking in the wrong place....
I think, it's kcontrol > KDE Components > Service Manager
The "Media Notifier Daemon" needs to be checked
Please say if this fixes it, and what file in ~/.trinity (if any) gets
changed
Regards,
David
1:52 p.m.
New subject: [trinity-users] Problem with medium application autostart
On Mon, Mar 14, 2011 at 4:59 AM, David Hare <davidahare(a)gmail.com> wrote:
<snip>
Unless it's the one specific module in kcontrol, I doubt it will save
that after logout. I doubt that's the problem either, I think it's
just not a setting that was set correctly, hence the need for setting
the defaults anyway.
--
Kris
"Piki"
Ark Linux Webmaster
Trinity Desktop Environment Packager
1:54 p.m.
New subject: [trinity-users] Problem with medium application autostart
Now that's a poit:
"Media Notifier Daemon" is checked, but not running.
I can start, but no config files are changed. There are also no new processes
visible.
Can I get some debug output from the DCOP server?
Nik
Am Montag, 14. März 2011 schrieb David Hare:
--
Mag. Dr. Nikolaus Klepp
Einnehmerstraße 14
A-4810 Gmunden
Tel.: +43 650 82 11 724
email: office(a)klepp.biz
3:16 p.m.
New subject: [trinity-users] Problem with medium application autostart
Strange, I run squeeze also, notification daemon works fine here, I can
toggle it on and off at will (sometimes for me it can be a nuisance)
The file in question seems to be ~/.trinity/share/config/kdedrc
Here is mine:
[$Version]
update_info=kded.upd:kde3.0
[Module-homedirnotify]
autoload=true
[Module-knemod]
autoload=true
[Module-kwrited]
autoload=true
[Module-mediamanager]
autoload=true
[Module-medianotifier]
autoload=true
[Module-remotedirnotify]
autoload=true
[Module-systemdirnotify]
autoload=true
Are other files in .trinity getting updated normally? You can tell by
the date stamps using ls or konq in detailed list mode
4:23 p.m.
New subject: [trinity-users] Problem with medium application autostart
Well, yes, my file is basicly the same. It represents the state of the
checkmarks. But it looks like the "Module-medianotifier" does not start, or it
ignores that it should do something.
Nik
Am Montag, 14. März 2011 schrieb David Hare:
--
Mag. Dr. Nikolaus Klepp
Einnehmerstraße 14
A-4810 Gmunden
Tel.: +43 650 82 11 724
email: office(a)klepp.biz
15 Mar
15 Mar
12:26 a.m.
New subject: [trinity-users] Problem with medium application autostart
OK folks, I found it :-)
The mediumautostart does not work, if this section exists in
~/.trinity/share/config/kdesktoprc:
[Media]
enabled=false
Steps to reproduce:
That section is not there from the beginning, it's introduced by kcontrol.
Start kcontrol, go to "Desktop/Behaviour/Device Icons". Unselect any
(e.g. "My Computer"), "Apply". (I'm not sure it "Apply"
is necessary).
Next time you log in, the mediumautomounter does not start.
Putting a checkmark in front of "My Computer" does not revert this setting,
you'll have to edit ~/.trinity/share/config/kdesktoprc and change it to:
[Media]
enabled=true
Now that was a funny day ;-)
Could somebody please try to reproduce?
Nik
Am Montag, 14. März 2011 schrieb Mag. Dr. Nikolaus Klepp:
--
Mag. Dr. Nikolaus Klepp
Einnehmerstraße 14
A-4810 Gmunden
Tel.: +43 650 82 11 724
email: office(a)klepp.biz
5136
days inactive
5137
days old
8 comments
3 participants
participants (3)
-
David Hare -
Kristopher Gamrat -
Mag. Dr. Nikolaus Klepp