SuSEconfig takes forever with texlive
in [Suse]
|
From: jamesromeongmail.com on 8 Mar 2010 12:41 On 9.2 (64-bit), whenever I make a software change using Yast2, at the end, SuSEconfig stops for many minutes when it runs texlive (or that is the last thing on the progress screen). Texlive has 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
From: Michael Soibelman on 10 Mar 2010 22:24 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 runs texlive (or that is > the last thing on the progress screen). > > Texlive has 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. :-)
From: Paul J Gans on 11 Mar 2010 12:14 Michael Soibelman <can-not-tell-u(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 runs texlive (or that is >> the last thing on the progress screen). >> >> Texlive has 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
From: Paul J Gans on 12 Mar 2010 15:50 houghi <houghi(a)houghi.org.invalid> wrote: >Paul J Gans wrote: >> and then it gets rather humorous: >> >> Warning: cannot find a sans serif Japanese font. Japanese in Java might not work. ><snip> >I get that as well. Probably because I also have not installed those >fonts. I could install them, but those characters are like chinese to >me. :-D I had the same thought... -- --- Paul J. Gans
From: jamesromeongmail.com on 14 Mar 2010 14:17
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? Thanks, Jim |