Re: non-starting browsers - the whole sad history

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > The only fix I've found that lets my machine stay up for a few days,
> > (uptime is 7+ days atm) is to find the .conf files in /etc, and direct
> > all that error output to /dev/null. That leaves one line of errors still
> > going to syslog about every 20 seconds as something in systemd.d keeps
> > looking for the speech dispatcher over blue tooth, and there isn't any of
> > that except the keyboad and mouse.
>
> Sounds like you need to kill the service(s) involved using whatever
> systemd's equivalent of rc-update is (or overwrite the service files
> with no-ops and then make them unwritable so they can't be changed),
> blacklist any kernel modules involved, and possibly write some udev
> rules to force the problem device to be properly identified.  Rather a
> tedious process that would have to start with identifying the problem
> device and its USB ID.
>
> E. Liddell

I take it that this answer is directed more towards Gene than myself. 

:-)

Bill
____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx



[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux