[lug] Tracing Permission Problems

Thu Dec 10 10:26:39 MST 2015

Testing using an alternate user revealed some very interesting and unexpected results! I've never seen this before, and I've been using Linux since kernel 1.0.9 was new and Wayde Allen hosted BLUG...

As it turns out, no user (under KDE) can display tool tip text with correct colors if logged in to their own desktop. Using either "su - username" or "su username" and then running kicad allows the text to display correctly. But this isn't just for other users on the original login desktop, this is includes a user logged in to their own desktop. Meaning if I log in with any user name under KDE, then no tool tip text works correctly on kicad...but if I use su in any way, original user or alternate user, then tool tip text appears with correct colors!

The basic workaround for now is to always run kicad as "su" using the login I'm already using. Why a user can't use his/her own desktop unless using su as him/herself is extremely odd. It's almost like KDE and kicad got together and said "I don't know who I am...I'd better look at my own driver's license and ask myself who I am". I have a workaround now ([sarcasm]"use su to have a conversation with myself"[/sarcasm]), and no way to know how to report this bug...the list of possible packages is extreme. I'm very glad you suggested testing other users.

Incidentally, I did look at MATE as a substitute, and saw mention of gtk2+ versus gtk3+ compatibility. Looks like Cinnamon is the gtk3+ variant of MATE...or at least a similar idea. Have you tried both MATE and Cinnamon? If so, what was the reason to pick MATE over Cinnamon?

Thanks!

----- Original Message -----From: Davide Del Vento <davide.del.vento at gmail.com>To: Boulder (Colorado) Linux Users Group -- General Mailing List <lug at lug.boulder.co.us>Sent: Thu, 10 Dec 2015 16:37:28 -0000 (UTC)Subject: Re: [lug] Tracing Permission Problems

Since it works for root, I doubt you can easily track it down withgdb. I suspect it's a setting somewhere, the trick is finding wherethat somewhere is. Is it application-specific or is it user-specific?Try creating another user and see if it works ok like it does for root.Try deleting not only all the cache entries, but also all the KDE andapplication specific setting. Then, do not rebuild them from scratch,but copy them from root. If it fixes it, nail it down with a bisectionsearch to one file.

[saracasm mode on]Or try running MATE, instead of KDE, like I started doing after beingfrustrated by the KDE and GNOME attempts to convince me that my screenmade of two 24" monitors is just a cell phone and that I should put itin my pocket.[sarcasm mode off]

On Thu, Dec 10, 2015 at 9:28 AM, <stimits at comcast.net> wrote:> Hi,>> I recently installed Fedora 23 with the KDE spin. One of the applications> I've added and would like to use is kicad. Unfortunately, there seems to be> a package install permissions issue, or else a system permissions issue. The> gist is that when the mouse hovers over an icon in kicad, the tool tip text> appears...but unless I'm running as root, the color is white on white. It> isn't readable.>> I noticed that if I run OpenBox without KDE, there is no issue. Running> Plasma or OpenBox on KDE causes the tool tips of kicad to ignore KDE tool> tip settings. Running as root fixes the issue and tool tip colors are> normal. Other applications display tool tips correctly on KDE, so I'm> inclined to believe something about the kicad package installed with invalid> permissions.>> I tried to delete and rebuild all possible cache entries, including deleting> my entire KDE desktop setup and starting from scratch, along with> customizing specific tool tip color settings in KDE. No difference. I> figured if it was a file permission, then strace might point it out.> Unfortunately, after going through a LOT of log text, I never found a> permission denied.>> What I did notice under strace while moving the mouse over icons to pop up> tool tip text that there were a lot of "EAGAIN" returns (resource> temporarily unavailable via recvmsg calls). I did this as root as well, but> never saw anything obviously limited to my non-root user. The actual data on> the recvmsg calls is binary, and not visible text (perhaps it is UTF8 or> UTF16 encoding), so I can't be sure any of the "resource temporarily> unavailable" messages had anything to do with tool tip color.>> I am convinced that since this only happens with kicad that KDE itself is> installed with correct permissions...but how would I trace the source of> kicad tool tip text color failing? Would I need to actually run a debug> version of kicad in gdb? It seems like there should be something more> obvious and simple to test before going to that length.>> Thanks!>> _______________________________________________> Web Page: http://lug.boulder.co.us> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety_______________________________________________Web Page: http://lug.boulder.co.usMailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lugJoin us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20151210/706489ec/attachment.html>