On Thu, Dec 21, 2006 at 03:10:14PM -0600, Igor Guerrero wrote: > Thanks. so, its working now? > > That work for the sound, but the point is that totem want ./kde dir?... Why? > > Totem is a Gnome app. true, but that doesn't mean that it can't work with kde stuff. I use neither gnome nor kde at this point, so can't really speak intelligently on that. my suggestion was just what occured to me -- why would the app be looking for something in .kde? maybe because it was trying to use a kde service that didn't exist on your system. A > > Is there some package in KDE that take control of your mounting device or > your file association? > > On 12/21/06, Andrew Sackville-West <andrew@farwestbilliards.com> wrote: > > > >On Thu, Dec 21, 2006 at 01:23:50PM -0600, Igor Guerrero wrote: > >> With the new user when I run: > >> > >> totem media.mp3 > >> > >> I get that: > >> > >> .kde/socket do not exist. > >> > >> And totem falls :( > >> > >> Maybe the problem is that I used to have KDE installed? > > > >hmmm.... I haven't used totem in a while, but does it let you select > >the output driver? if so, maybe you have selected the kde sound > >daemons (artsd?), which no longer exists. Try changing that to alsa > >or, since you're in gnome, esd. > > > >A > > > > > >> > >> On 12/21/06, Igor Guerrero <igfgt1@gmail.com> wrote: > >> > > >> >I'd create a new user and the I got the same problem. > >> > > >> >On 12/21/06, Kent West <westk@is.acu.edu> wrote: > >> >> > >> >> > >> >> > >> >> On 12/21/06, Igor Guerrero <igfgt1@gmail.com> wrote: > >> >> > > >> >> > > >> >> > How do I solve the problem? > >> >> > > > >> >> > > > >> >> > > > with my Gnome Desktop, apparently *all* the file associations > >have > >> >> > > > >> >> > > > gone... > >> >> > > > when I try to open an mp3 I can't, I have to choose "Open with" > >> >> > > the > >> >> > > > problem > >> >> > > > >> >> > > >> >> > >> >> Not being a user of Gnome, I don't know the correct answer, but what > >I'd > >> >> try is logging out of Gnome, renaming all your Gnome-related > >directories > >> >in > >> >> your home directory, and then logging back in. If that solves the > >> >problem, > >> >> you're a step closer to knowing which files are the problem. If that > >does > >> >> not solve the problem, you can be fairly confident it's system-wide > >> >rather > >> >> than a user-specific problem (but I'd still create a new user and > >test > >> >with > >> >> that user to make absolutely certain). > >> >> > >> >> Again, this is not a fix necessarily, but it might get you closer to > >> >> one. > >> >> > >> >> -- > >> >> Kent West > >> >> http://kentwest.blogspot.com > >> > > >> > > >> > > >> > > >> >-- > >> >:::lxuser 391715::: > >> >http://igordevlog.blogspot.com/ > >> > > >> > >> > >> > >> -- > >> :::lxuser 391715::: > >> http://igordevlog.blogspot.com/ > > > > > >-----BEGIN PGP SIGNATURE----- > >Version: GnuPG v1.4.6 (GNU/Linux) > > > >iD8DBQFFiuMRaIeIEqwil4YRApwJAJ95aCM8T4F7MXe1Tq2X7mhhOKXK3gCglK5Y > >eaGVrzDPXyTeLXj/bQJPvVQ= > >=Ri9T > >-----END PGP SIGNATURE----- > > > > > > > > > -- > :::lxuser 391715::: > http://igordevlog.blogspot.com/
Attachment:
signature.asc
Description: Digital signature