LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-16-2018, 04:59 AM   #61
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu
Posts: 282

Original Poster
Rep: Reputation: 39

@kjhambrick, @chrisretusn:

The /.cache directory will be created at a reboot when it does not exist yet. You might remove that directory and reboot to verify this.

It seems you both rebooted on Apr 9 and when you did so it was the first time after installing/upgrading the "culprit" package(s). In other words: the "culprit" package(s) are not from Apr 9 and later, but from Apr 9 and before. If you remember when you rebooted the last time before Apr 9 the search window would shrink considerably.

For the record: the NetworkManager package was rebuilt on Apr 1. However, as I said in my post #50 any other "systemd" package(s) might be the culprit now.

Last edited by burdi01; 04-16-2018 at 05:05 AM.
 
Old 04-16-2018, 07:03 AM   #62
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 864

Rep: Reputation: 319Reputation: 319Reputation: 319Reputation: 319
To clarify.
Quote:
Originally Posted by burdi01 View Post
@kjhambrick, @chrisretusn:

The /.cache directory will be created at a reboot when it does not exist yet. You might remove that directory and reboot to verify this.
This is known. I have verified this. The /.cache directory did not exist before the reboot on Apr 9, the date shows this. Removing it, brings it back after a reboot, with the date of the reboot. The directory date does not change over time, stays at creation date.

Quote:
It seems you both rebooted on Apr 9 and when you did so it was the first time after installing/upgrading the "culprit" package(s). In other words: the "culprit" package(s) are not from Apr 9 and later, but from Apr 9 and before. If you remember when you rebooted the last time before Apr 9 the search window would shrink considerably.
Again from my perspective, a known factor, packages upgraded after Apr 9 could not be suspect. Not sure were you got that impression. My list only included Apr 9. I could have included the packages from before that too, my last reboot was April 4 after upgrading ktown and a fairly healthy update of Slackware, so there is a boat load of packages that could be suspect. Though I will exclude ktown as a possible suspect. Included in those packages was NetworkManager-1.10.6-x86_64-2.txz (2018-03-31 6:26). I don't suspect NetworkManager because I rebooted with it turn off, the /.cache directory was created after deleting and rebooting. It's something else I suspect.
 
Old 04-16-2018, 07:49 AM   #63
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,294
Blog Entries: 4

Rep: Reputation: Disabled
It's glib-compile-schemas (which correlates with #30 and #31 in this thread)
 
2 members found this post helpful.
Old 04-16-2018, 08:42 AM   #64
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,426

Rep: Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832
Quote:
Originally Posted by burdi01 View Post
@kjhambrick, @chrisretusn:

The /.cache directory will be created at a reboot when it does not exist yet. You might remove that directory and reboot to verify this.

For the record: the NetworkManager package was rebuilt on Apr 1. However, as I said in my post #50 any other "systemd" package(s) might be the culprit now.
Quote:
Originally Posted by 55020 View Post
It's glib-compile-schemas (which correlates with #30 and #31 in this thread)
Thanks 55020 and burdi01

Code:
$ man glib-compile-schemas

<<SNIP>>
       At runtime, GSettings looks for schemas in the glib-2.0/schemas
       subdirectories of all directories specified in the XDG_DATA_DIRS
       environment variable. The usual location to install schema files is
       /usr/share/glib-2.0/schemas.
<<SNIP>>
Yikes ! Sounds like a Wac-a-Mole game then ...

I wonder if the XDG_* Variables need to be set and exported in /etc/rc.d/rc.M rather than trying to find and fix all the rc.scripts that need them ?

-- kjh

P.S. burdi01 --

I did `upgradepkg glib2` on Apr 8, the day before the reboot that created /.cache/
Code:
# ls -la /var/log/packages/glib2*

-rw-r--r-- 1 root root 45142 Apr  8 05:52 /var/log/packages/glib2-2.56.1-x86_64-1
April Reboots
Code:
# last reboot |grep ' Apr '

reboot   system boot  4.14.34          Fri Apr 13 13:26 - 07:47 (2+18:21)   
reboot   system boot  4.14.33          Thu Apr 12 07:20 - 13:25 (1+06:04)   
reboot   system boot  4.14.33          Mon Apr  9 04:56 - 07:20 (3+02:23)   
reboot   system boot  4.14.32          Wed Apr  4 03:31 - 04:55 (5+01:24)   
reboot   system boot  4.14.32          Mon Apr  2 04:50 - 03:30 (1+22:39)

Last edited by kjhambrick; 04-16-2018 at 09:11 AM. Reason: add P.S. ; just before -> the day before the reboot ...
 
Old 04-16-2018, 09:48 AM   #65
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,028

Rep: Reputation: 1762Reputation: 1762Reputation: 1762Reputation: 1762Reputation: 1762Reputation: 1762Reputation: 1762Reputation: 1762Reputation: 1762Reputation: 1762Reputation: 1762
According to my testing, the creation of the /.cache directory is triggered by this section in rc.M
Code:
if [ -x /usr/bin/update-gdk-pixbuf-loaders ]; then
  echo "Updating gdk-pixbuf.loaders:"
  echo "  /usr/bin/update-gdk-pixbuf-loaders &"
  /usr/bin/update-gdk-pixbuf-loaders > /dev/null 2>&1 &
fi
A temporary fix would be to add a line at the end of the /usr/bin/update-gdk-pixbuf-loaders script to remove the /.cache directory.
Code:
[ -d /.cache ] && rm -rf /.cache
Seems to work here.

Last edited by allend; 04-16-2018 at 10:05 AM.
 
Old 04-16-2018, 11:54 AM   #66
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 864

Rep: Reputation: 319Reputation: 319Reputation: 319Reputation: 319
Thanks 55020 and allend. Knowing the cause is better than not knowing.
 
Old 04-16-2018, 12:37 PM   #67
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 864

Rep: Reputation: 319Reputation: 319Reputation: 319Reputation: 319
Quote:
Originally Posted by allend View Post
According to my testing, the creation of the /.cache directory is triggered by this section in rc.M
Code:
if [ -x /usr/bin/update-gdk-pixbuf-loaders ]; then
  echo "Updating gdk-pixbuf.loaders:"
  echo "  /usr/bin/update-gdk-pixbuf-loaders &"
  /usr/bin/update-gdk-pixbuf-loaders > /dev/null 2>&1 &
fi
Confirmed here too.
 
Old 04-17-2018, 04:05 AM   #68
GazL
Senior Member
 
Registered: May 2008
Posts: 4,769
Blog Entries: 14

Rep: Reputation: Disabled
Adding HOME=/root to the invocation means it gets created in root's home directory instead, which is still annoying but not as bad as littering in the root directory itself.
 
Old 04-22-2018, 06:58 PM   #69
upnort
Member
 
Registered: Oct 2014
Distribution: Slackware, Proxmox, Debian, CentOS, Ubuntu MATE
Posts: 739

Rep: Reputation: Disabled
Confirmed in my neck of the woods that the cause is /usr/bin/update-gdk-pixbuf-loaders.

Quote:
[ -d /.cache ] && rm -rf /.cache
Sure, but why do we have to do nonsense like this?

Is there a way to patch this and submit upstream?

Last edited by upnort; 04-23-2018 at 11:59 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] latest hplip on current64 Launfal Slackware 34 06-10-2016 07:27 PM
[SOLVED] Current64 sound has a mind of its own Gordie Slackware 20 02-22-2016 07:32 AM
[SOLVED] Pdfshuffler and poppler in current64 aszabo Slackware 3 02-01-2016 12:01 PM
[SOLVED] -current64 aclocal segfault KaMii Slackware 8 11-07-2015 01:46 AM
Autokey and current64 charlie_lab Slackware 4 03-20-2010 04:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:30 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration