3 ms·
Yup, latest version. I tried clearing the cache and no change. Since I was in console, I just checked syslog and I'm getting a dbus DENIED. I'll poke at it when
by CaptSpify 10y ago
Yup, latest version. I tried clearing the cache and no change. Since I was in console, I just checked syslog and I'm getting a dbus DENIED. I'll poke at it when I have more time, but I wonder if they need to fix up their apparmor perms.
Curious as to why your getting a different result though.
EDIT: I'd also be curious as to your opinion of Touch in general?
My opinion: I love it. I'm not a huge fan of Unity, or Ubuntu, and it's definitely in the beta stage. I like that most of the problems that I have were solvable on my own via shell-script or whatever hacks I come up with.
- notspanishflu 10y agoOh sh*t I'm just remembering now a problem some people had with lock files. I thought it was fixed [0]. In that thread someone said deleting .config/com.ubuntu.telegram/<number>/auth.lock solved the problem with Telegram not starting [1]. So look for .lock file/s and delete it/them. I still love Debian way more than Ubuntu, but I think they're doing a great work with Touch. [0] https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1576989/ https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-... [1] https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1576989/comments/5 https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-...
- CaptSpify 10y agoHmmm.... I don't have any lock files. I'll dig into it when I get more time. thanks