Author Topic: SOLVED:gtk2+ theme caused problem with LOManager  (Read 564 times)

Offline djohnston

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6227
  • I don't do Windows
SOLVED:gtk2+ theme caused problem with LOManager
« on: May 07, 2012, 11:44:21 PM »
Okay, this one is weird. A gtk theme caused a problem with LOManager running on LXDE desktop. Not sure where to put this. I started with running LOManager from the menu. I get a popup error after entering root's password.



Opened a terminal and checked for the referenced file "/tmp/xsulomanager".

darrel@AMD64:  52 items 508Kb -> su -
Password:
[root@AMD64 ~]# updatedb
[root@AMD64 ~]# ls /tmp/xsulomanager
ls: cannot access /tmp/xsulomanager: No such file or directory
[root@AMD64 ~]# pwd
/root
[root@AMD64 ~]# ls tmp/xsulomanager
ls: cannot access tmp/xsulomanager: No such file or directory
[root@AMD64 ~]# locate xsulomanager
[root@AMD64 ~]#


I had already checked to make sure I was up to date and no testing repositories were enabled. So, I started lomanager in debug mode. After supplying root's password in the popup dialog window, I saw the same error window again.

darrel@AMD64:  52 items 508Kb -> lomanager --debug

Tue May  8 12:15:46 AM CDT 2012
~
darrel@AMD64:  52 items 508Kb -> /usr/share/themes/MurrinaBlue/gtk-2.0/gtkrc:83: Murrine configuration option "scrollbar_color" is no longer supported and will be ignored.



^C

Tue May  8 12:16:25 AM CDT 2012
~
darrel@AMD64:  52 items 508Kb ->



I changed from the offending Murrina Blue gtk2 theme to elegant-aurora. Started lomanager in debug mode from a terminal again. This time, it ran normally and updated LibreOffice. Don't know what to make of this. Still have the Murrina themes enabled if someone thinks that was the problem.
« Last Edit: May 08, 2012, 12:48:50 AM by djohnston »
Bare metal                           VBox
AMD Athlon 7750 Dual-Core    Single core
4GiB RAM                              1GiB RAM
nVidia GeForce FX 5200          64MB video
LXDE 32bit                            KDE 64bit

Registered Linux User #416378

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15845
  • LXDE! Coffee, Bacon and Cheesecake!
Re: gtk2+ theme caused problem with LOManager
« Reply #1 on: May 08, 2012, 12:23:54 AM »
The message about MurrinaBlue is a null message, not an error. In relation to lomanager, it can be ignored.     

Menu > File Tools > Root PCManFM     
In the PCManFM address field, type /tmp > type <Enter> key.     
Look for the file/folder "xsulomanager." Delete it. Exit Root PCManFM. Run lomanager.     

Offline djohnston

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6227
  • I don't do Windows
Re: gtk2+ theme caused problem with LOManager
« Reply #2 on: May 08, 2012, 12:41:29 AM »
No file or folder by that name, Neal. I've already updated LibreOffice.



Bare metal                           VBox
AMD Athlon 7750 Dual-Core    Single core
4GiB RAM                              1GiB RAM
nVidia GeForce FX 5200          64MB video
LXDE 32bit                            KDE 64bit

Registered Linux User #416378

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15845
  • LXDE! Coffee, Bacon and Cheesecake!
Re: gtk2+ theme caused problem with LOManager
« Reply #3 on: May 08, 2012, 12:44:19 AM »
No file or folder by that name, Neal. I've already updated LibreOffice.
     
Okay then. /tmp/xsulomanager was removed on completion of / exiting of lomanager, as it should be.     

Offline pinoc

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2839
    • other projects...
Re: gtk2+ theme caused problem with LOManager
« Reply #4 on: May 08, 2012, 12:45:58 AM »
Hi djohnston,

this lomanager message appears if a previous interrupted lomanager run is detected. In this case, there will be a file /tmp/xsulomanager left in the system. However, this temporary file should not be there before lomanager is invoked. Now, if lomanager finds that file, and this file is older than 12 secs, then it assumes that this file is from a previous incomplete run and it will remove it. And you see, that's what happened. After that running lomanager as normal user should work fine.
Don't think this should have something to do with a gtk theme.
best!
-p.

Offline djohnston

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6227
  • I don't do Windows
Re: gtk2+ theme caused problem with LOManager
« Reply #5 on: May 08, 2012, 12:48:21 AM »
Thanks, Neal and Pinoc. Just wanted to report it because I've never seen it before. Will mark as solved.
Bare metal                           VBox
AMD Athlon 7750 Dual-Core    Single core
4GiB RAM                              1GiB RAM
nVidia GeForce FX 5200          64MB video
LXDE 32bit                            KDE 64bit

Registered Linux User #416378