SuSEconfig takes forever with texlive
in [Suse]
|
From: Paul J Gans on 14 Mar 2010 21:42 jamesromeongmail.com <jamesrome(a)gmail.com> wrote: >On Mar 11, 1:14 pm, Paul J Gans <gan...(a)panix.com> wrote: >> Michael Soibelman <can-not-tel...(a)a-secret-place.org> wrote: >> >On Mon, 08 Mar 2010 09:41:41 -0800, jamesromeongmail.com wrote: >> >> On 9.2 (64-bit), whenever I make a software change using Yast2, at the >> >> end, SuSEconfig stops for many minutes when it runstexlive(or that is >> >> the last thing on the progress screen). >> >> >>Texlivehas just one line that tells it not to delete old fonts, so I do >> >> not understand why the process halts here. glib2 is the next command it >> >> processes. >> >> >> How do I fix this? >> >> >> Thanks, >> >> Jim >> >The process does not stop there. You just aren't seeing the incredible >> >amount of work going on... >> >Just take a look at '/var/log/YaST2/y2log.SuSEconfig' and start at the >> >bottom. Above their you'll see all that is going on as well as a couple >> >of errors and where to look at those... >> >You may need to have root privileges to read this file. Also, my >> >uneducated guess is that all the fonts is the reason it takes so much >> >time. At least that's what the log file seems to indicate.... >> >P.S. You're not the only one waiting a while during SuSEconfig for the >> >Tex part to finish... So you're not alone. :-) >> >> I use TeX quite a bit but I don't seem to have that SuSEconfig problem. >> Just for comparison, my /var/log/YaST2/y2log.SuSEconfig file yields: >> >> Executing /sbin/conf.d/SuSEconfig.fonts... >> Creating fonts.{scale,dir} files .......... >> /etc/fonts/suse-font-dirs.conf unchanged >> /etc/fonts/suse-hinting.conf unchanged >> /etc/fonts/suse-bitmaps.conf unchanged >> Creating cache files for fontconfig ............................. >> Creating 32bit cache files for fontconfig ............................. >> generating java font setup >> >> and then it gets rather humorous: >> >> Warning: cannot find a sans serif Japanese font. Japanese in Java might not work. >> Warning: cannot find a serif Japanese font. Japanese in Java might not work. >> Warning: cannot find a sans serif simplified Chinese font. Simplified Chinese in Java might not work. >> Warning: cannot find a serif simplified Chinese font. Simplified Chinese in Java might not work. >> Warning: cannot find a sans serif traditional Chinese font. Traditional Chinese in Java might not work. >> Warning: cannot find a serif traditional Chinese font. Traditional Chinese in Ja va might not work. >> Warning: cannot find a sans serif Korean font. Korean in Java might not work. >> Warning: cannot find a serif Korean font. Korean in Java might not work. >> Finished. >> >> I've never tried Java in any of those languages, but hey... >> >> All in oll this does not take much time at all on my system (11.1/64). >> >> -- >> --- Paul J. Gans >So how do I install these fonts to avoid this 4-5 minute wait, or how >do I remove the search? No no. The missing fonts only generate those lines, they don't delay the process at all. I'd estimate that this part of SuSE.config takes about 1 second on my system. The rest of the SuSE.config process probably takes 8-10 seconds all told. (All times estimated) -- --- Paul J. Gans
From: jamesromeongmail.com on 15 Mar 2010 09:55 On Mar 14, 9:42 pm, Paul J Gans <gan...(a)panix.com> wrote: > jamesromeongmail.com <jamesr...(a)gmail.com> wrote: > >On Mar 11, 1:14 pm, Paul J Gans <gan...(a)panix.com> wrote: > >> Michael Soibelman <can-not-tel...(a)a-secret-place.org> wrote: > >> >On Mon, 08 Mar 2010 09:41:41 -0800, jamesromeongmail.com wrote: > >> >> On 9.2 (64-bit), whenever I make a software change using Yast2, at the > >> >> end, SuSEconfig stops for many minutes when it runstexlive(or that is > >> >> the last thing on the progress screen). > > >> >>Texlivehas just one line that tells it not to delete old fonts, so I do > >> >> not understand why the process halts here. glib2 is the next command it > >> >> processes. > > >> >> How do I fix this? > > >> >> Thanks, > >> >> Jim > >> >The process does not stop there. You just aren't seeing the incredible > >> >amount of work going on... > >> >Just take a look at '/var/log/YaST2/y2log.SuSEconfig' and start at the > >> >bottom. Above their you'll see all that is going on as well as a couple > >> >of errors and where to look at those... > >> >You may need to have root privileges to read this file. Also, my > >> >uneducated guess is that all the fonts is the reason it takes so much > >> >time. At least that's what the log file seems to indicate.... > >> >P.S. You're not the only one waiting a while during SuSEconfig for the > >> >Tex part to finish... So you're not alone. :-) > > >> I use TeX quite a bit but I don't seem to have that SuSEconfig problem.. > >> Just for comparison, my /var/log/YaST2/y2log.SuSEconfig file yields: > > >> Executing /sbin/conf.d/SuSEconfig.fonts... > >> Creating fonts.{scale,dir} files .......... > >> /etc/fonts/suse-font-dirs.conf unchanged > >> /etc/fonts/suse-hinting.conf unchanged > >> /etc/fonts/suse-bitmaps.conf unchanged > >> Creating cache files for fontconfig ............................. > >> Creating 32bit cache files for fontconfig .............................. > >> generating java font setup > > >> and then it gets rather humorous: > > >> Warning: cannot find a sans serif Japanese font. Japanese in Java might not work. > >> Warning: cannot find a serif Japanese font. Japanese in Java might not work. > >> Warning: cannot find a sans serif simplified Chinese font. Simplified Chinese in Java might not work. > >> Warning: cannot find a serif simplified Chinese font. Simplified Chinese in Java might not work. > >> Warning: cannot find a sans serif traditional Chinese font. Traditional Chinese in Java might not work. > >> Warning: cannot find a serif traditional Chinese font. Traditional Chinese in Ja va might not work. > >> Warning: cannot find a sans serif Korean font. Korean in Java might not work. > >> Warning: cannot find a serif Korean font. Korean in Java might not work. > >> Finished. > > >> I've never tried Java in any of those languages, but hey... > > >> All in oll this does not take much time at all on my system (11.1/64). > > >> -- > >> --- Paul J. Gans > >So how do I install these fonts to avoid this 4-5 minute wait, or how > >do I remove the search? > > No no. The missing fonts only generate those lines, they don't > delay the process at all. I'd estimate that this part of SuSE.config > takes about 1 second on my system. The rest of the SuSE.config > process probably takes 8-10 seconds all told. (All times estimated) > > -- > --- Paul J. Gans Then what is taking so long?
From: Paul J Gans on 15 Mar 2010 12:28 jamesromeongmail.com <jamesrome(a)gmail.com> wrote: >On Mar 14, 9:42 pm, Paul J Gans <gan...(a)panix.com> wrote: >> jamesromeongmail.com <jamesr...(a)gmail.com> wrote: >> >On Mar 11, 1:14 pm, Paul J Gans <gan...(a)panix.com> wrote: >> >> Michael Soibelman <can-not-tel...(a)a-secret-place.org> wrote: >> >> >On Mon, 08 Mar 2010 09:41:41 -0800, jamesromeongmail.com wrote: >> >> >> On 9.2 (64-bit), whenever I make a software change using Yast2, at the >> >> >> end, SuSEconfig stops for many minutes when it runstexlive(or that is >> >> >> the last thing on the progress screen). >> >> >> >>Texlivehas just one line that tells it not to delete old fonts, so I do >> >> >> not understand why the process halts here. glib2 is the next command it >> >> >> processes. >> >> >> >> How do I fix this? >> >> >> >> Thanks, >> >> >> Jim >> >> >The process does not stop there. You just aren't seeing the incredible >> >> >amount of work going on... >> >> >Just take a look at '/var/log/YaST2/y2log.SuSEconfig' and start at the >> >> >bottom. Above their you'll see all that is going on as well as a couple >> >> >of errors and where to look at those... >> >> >You may need to have root privileges to read this file. Also, my >> >> >uneducated guess is that all the fonts is the reason it takes so much >> >> >time. At least that's what the log file seems to indicate.... >> >> >P.S. You're not the only one waiting a while during SuSEconfig for the >> >> >Tex part to finish... So you're not alone. :-) >> >> >> I use TeX quite a bit but I don't seem to have that SuSEconfig problem. >> >> Just for comparison, my /var/log/YaST2/y2log.SuSEconfig file yields: >> >> >> Executing /sbin/conf.d/SuSEconfig.fonts... >> >> Creating fonts.{scale,dir} files .......... >> >> /etc/fonts/suse-font-dirs.conf unchanged >> >> /etc/fonts/suse-hinting.conf unchanged >> >> /etc/fonts/suse-bitmaps.conf unchanged >> >> Creating cache files for fontconfig ............................. >> >> Creating 32bit cache files for fontconfig ............................. >> >> generating java font setup >> >> >> and then it gets rather humorous: >> >> >> Warning: cannot find a sans serif Japanese font. Japanese in Java might not work. >> >> Warning: cannot find a serif Japanese font. Japanese in Java might not work. >> >> Warning: cannot find a sans serif simplified Chinese font. Simplified Chinese in Java might not work. >> >> Warning: cannot find a serif simplified Chinese font. Simplified Chinese in Java might not work. >> >> Warning: cannot find a sans serif traditional Chinese font. Traditional Chinese in Java might not work. >> >> Warning: cannot find a serif traditional Chinese font. Traditional Chinese in Ja va might not work. >> >> Warning: cannot find a sans serif Korean font. Korean in Java might not work. >> >> Warning: cannot find a serif Korean font. Korean in Java might not work. >> >> Finished. >> >> >> I've never tried Java in any of those languages, but hey... >> >> >> All in oll this does not take much time at all on my system (11.1/64). >> >> >> -- >> >> --- Paul J. Gans >> >So how do I install these fonts to avoid this 4-5 minute wait, or how >> >do I remove the search? >> >> No no. The missing fonts only generate those lines, they don't >> delay the process at all. I'd estimate that this part of SuSE.config >> takes about 1 second on my system. The rest of the SuSE.config >> process probably takes 8-10 seconds all told. (All times estimated) >> >> -- >> --- Paul J. Gans >Then what is taking so long? Nothing is taking my system too long. You could watch the log being generated with the "tail" command (check man 1 tail for details which are not hard). That way you could see where it stalls. -- --- Paul J. Gans
From: jamesromeongmail.com on 16 Mar 2010 10:44
On Mar 15, 12:28 pm, Paul J Gans <gan...(a)panix.com> wrote: > > Nothing is taking my system too long. You could watch the log being > generated with the "tail" command (check man 1 tail for details which > are not hard). That way you could see where it stalls. > > -- > --- Paul J. Gans My logfile has: Starting SuSEconfig, the SuSE Configuration Tool... Running in verbose mode. Running module permissions only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.permissions... Finished. Starting SuSEconfig, the SuSE Configuration Tool... Running in verbose mode. Running module gdm only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.gdm... Finished. Starting SuSEconfig, the SuSE Configuration Tool... Running in verbose mode. Running module ispell only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.ispell... Finished. Starting SuSEconfig, the SuSE Configuration Tool... Running in verbose mode. Running module texlive only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.texlive... Finished. Starting SuSEconfig, the SuSE Configuration Tool... Running in verbose mode. Running module glib2 only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.glib2... /sbin/conf.d/SuSEconfig.glib2: line 80: /usr/share/applications/ openoffice.org3-startcenter.desktop: No such file or directory /sbin/conf.d/SuSEconfig.glib2: line 83: read: read error: 0: Bad file descriptor Finished. Starting SuSEconfig, the SuSE Configuration Tool... Running in verbose mode. Running module desktop-file-utils only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.desktop-file-utils... Could not parse file '/usr/share/applications/openoffice.org3- startcenter.desktop': No such file or directory Finished. Starting SuSEconfig, the SuSE Configuration Tool... Running in verbose mode. Running module fonts only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.fonts... Creating fonts.{scale,dir} files ......... /etc/fonts/suse-font-dirs.conf unchanged /etc/fonts/suse-hinting.conf unchanged /etc/fonts/suse-bitmaps.conf unchanged Creating cache files for fontconfig .................................. Creating 32bit cache files for fontconfig .................................. generating java font setup Warning: cannot find a sans serif simplified Chinese font. Simplified Chinese in Java might not work. Warning: cannot find a serif simplified Chinese font. Simplified Chinese in Java might not work. Warning: cannot find a sans serif traditional Chinese font. Traditional Chinese in Java might not work. Warning: cannot find a serif traditional Chinese font. Traditional Chinese in Java might not work. Finished. Starting SuSEconfig, the SuSE Configuration Tool... Running in verbose mode. Running module gtk2 only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.gtk2... Finished. Starting SuSEconfig, the SuSE Configuration Tool... Running in verbose mode. Running in full featured mode. Reading /etc/sysconfig and updating the system... skipping modules Finished. I uninstalled OpenOffice with the Software Manager, and replaced it with the newer version from OpenOffice.org. So maybe it is stuck on that. But there is no OpenOffice entry in /etc/sysconfig. How would I get this check out of /usr/bin/update-desktop-database? Jim |