Welcome, Guest. Please login or register.
April 21, 2014, 01:43:24 AM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

  Show Posts
Pages: 1 ... 6 7 [8] 9
106  Assistance / Software / Re: LyX 1.6.4 on: November 27, 2009, 21:25:37 PM
Hi, Ronald,

Sorry I haven't been able to help you very well. I hope that a knowledgeable LyX user from one of those forums will be able to point you in the direction of a solution.

Here are a few more pieces of evidence which might help you with troubleshooting. I also have LyX installed in Ubuntu 8.04 LTS and in PCLinuxOS 2009, and I looked at their settings:

LyX ver. 1.5.3
DVI display works: with Evince (although the viewer is configured as "xdg-open")
PDF display works: with Evince (although configured as "xdg-open")
TeX encoding = T1

LyX ver.
DVI display works: with xdvik (viewer configured as "xdvi")
PDF display does not work: Produces error message about "File [X] does not exist".  (Current viewer configuration is "kpdf")
TeX encoding = T1

(I will attach screenshots of those configuration settings).

As a last resort, another thing you might try (you may have done this already) is to completely uninstall LyX and then reinstall the program. This technique has sometimes worked for me when an application is behaving strangely and I haven't been able to figure out what's causing the problem.

If you solve the problem, please post back and let us know how you did it. Good luck,
107  Assistance / Software / Re: LyX 1.6.4 on: November 26, 2009, 23:31:26 PM
Hi, Ronald,

Just another thought ... If your problem is possibly related to missing fonts, it occurred to me that it might be helpful for you to see which fonts I have installed on my system. (I did a PiSi search from the command line; with luck, this lists everything).

david-pardus david # pisi search lyx                                                                                                        
lyx - Graphical frontend for LaTeX                                                                                                            
gv - Standard ghostscript frontend used by programs like LyX

david-pardus david # pisi search fonts
Nafees-Naskh-fonts - Nafees Naskh font for Urdu language                                                                                      
ecofont - Eco friendly and cost reducing printing fonts                                                                                        
texlive-fontsrecommended - TeXLive Recommended fonts                                                                                          
fontforge - Font editor and converter
libXfont - X.Org Xfont library
dejavu-fonts - DejaVu fonts
texlive-fontsextra - TeXLive Extra fonts
Gentium-basic-fonts - Gentium Basic TTF font
gbdfed - Bitmap font editor
Charis-compact-fonts - A version of Charis SIL with tighter line spacing
Nafees-Web-Naskh-fonts - Nafees Web Naskh font for Urdu language
Inconsolata-fonts - A font similar to the TheSansMono
graphviz - Open source graph drawing software
urw-fonts - Free versions of the 35 standard PostScript fonts
Bitstream-Vera-fonts - Bitstream Vera TTF Fonts
droid-fonts - Droid is a TrueType font family intended for use on the small screens of mobile handsets
Gentium-fonts - Unicode enabled TTF font
MgOpen-fonts - MgOpen TTF Fonts
Libertine-fonts - A font similar to Times New Roman
liberation-fonts - Font collection similar to ones found in Microsoft Windows
t1utils - Type 1 Font utilities
ftgl - Font rendering library for OpenGL
freefont - Free UCS Outline Fonts
arkpandora-fonts - Arkpandora MS-TTF replacement font pack
Tiresias-fonts - Tiresias TTF Fonts
gnu-gs-fonts-std - Ghostscript standard fonts
Doulos-fonts - A font similar to Times/Times New Roman with only regular face
xorg-font - XOrg font files
ttf2pt1 - TrueType to Type1 font converter
ttmkfdir - A utility to create a fonts.scale file from a set of TrueType fonts
Nafees-Riqa-fonts - Nafees Riqa font for Urdu language
scheherazade-fonts - An Arabic true type font
Nafees-Pakistani-Naskh-fonts - Nafees Pakistani Naskh font Urdu language
Nafees-Nastaleeq-fonts - Nafees Nastaleeq font for Urdu languages
tv-fonts - TV Fonts for Xawtv
t1lib - A Type 1 Font Rasterizer Library for UNIX/X11
Stix-fonts - Stix Fonts
xorg-font-extra - XOrg font files
lcdf-typetools - Font utilities for eg manipulating OTF
Charis-fonts - A font similar to Bitstream Charter
graphviz-docs - Open source graph drawing software
aquafont - Far East fonts

Also, I noticed that the default TeX encoding is for T1 fonts (under Preferences > Output > LaTeX > TeX encoding: ), so here's what a PiSi search for "T1" turned up on my system:

david-pardus david # pisi search T1
twolame - An optimised MPEG Audio Layer 2
t1utils - Type 1 Font utilities
terminus-font - Fixed point font
xterm - Terminal emulator for the X Window System
ttf2pt1 - TrueType to Type1 font converter
t1lib - A Type 1 Font Rasterizer Library for UNIX/X11
minicom - Text-based modem control and terminal emulation program

Maybe you are missing t1utils and/or ttf2pt1? Just a stab in the dark ...

HTH, =david
108  Assistance / Software / Re: LyX 1.6.4 on: November 26, 2009, 22:54:20 PM
Hi, Ronald,

You're very welcome. Hmm ... I agree that those results look strange. I think that James T's hunch about missing fonts may be correct.

I will try investigating further this evening to see if I stumble upon something. However, since my LyX knowledge is extremely basic, in the meantime I suggest that you try asking in two LyX-specific user forums. Hopefully, someone more familiar with LyX can tell you what's going wrong:

LyX Forum

LaTeX Community Forum -- LyX Subforum

(You'll first need to register with the LaTeX Community Forum [which is a pretty friendly place, I've used it before]. I'm not sure about the LyX Forum, as I haven't ever tried it).

I've seen occasional LyX-related questions posted to the comp.text.tex Usenet newgroup, but I think you would have better luck with the Web-based forums.

With best wishes,
109  Assistance / Software / Re: LyX 1.6.4 on: November 26, 2009, 21:28:34 PM
Hi, superleste (Ronald),

Welcome to the Pardus Forums! I am not a LyX user (I use LaTeX instead), so I only know enough about LyX to get myself in trouble. However, I might have found a workaround for you to try.

I just installed LyX on my Pardus 2009, and it brought along the following dependencies with it: libXp; openmotif; aiksaurus; and xdvik. < Edit: > (I should mention that I had previously installed TeX Live, which includes base components such as tex, latex, etc. I suspect that LyX also requires these as dependencies, so it's likely that your download of LyX and related packages would have been larger than mine).

I created a brief test document and tried to produce both a DVI and a PDF file. I included a few foreign-language diacritics (accute accent, circumflex accent, cedille, tilde).

The results: Pressing the "View DVI" button on the toolbar did produce output, but xdvik was very slow in appearing on the screen (it took maybe 1-1.5 minutes). Also, the foreign diacritics were missing from the DVI (I'm not sure why).

Pressing the "View PDF" button worked better for me. The file was displayed by Okular (which started up quickly) and all of the foreign diacritics displayed correctly.

You might try this suggestion and see if it will fix your problem. It will reconfigure LyX's preferences to use Okular to display DVIs:

Start up LyX and go to Tools > Preferences. A new window will open; in its left-hand pane, look for File Handling and then choose File formats. Then, in the right-hand window pane, look for the Format: box at the top of the window. It has a drop-down menu beside it; from there, choose DVI. In the Viewer: box, change the default xdvik to okular. Then click on the Save button.

In order to complete the configuration change, in LyX's main GUI window, go to Tools > Reconfigure. After doing this, you will see a dialog box that says your setup has been reconfigured and that you must close LyX and restart it for the changes to take effect.

I am attaching two screenshots which will show the configuration preferences better (I hope).

Interestingly enough, the default configuration for viewing PDFs is to use "xdg-open" rather than Okular. (I have not changed this in any way, and Okular opens with no problem).

Hope this helps and Good luck,

P.S. to waf:

If I understand correctly, LyX is a stand-alone environment which uses LaTeX as its typesetting engine. The LyX GUI has its own built-in editor, so users do not need to install a separate editor such as Kile or Texmaker.  
110  Assistance / Pardus for beginners / Re: PiSi Package Manager GUI vs. command-line PiSi on: November 15, 2009, 20:19:02 PM
Hi, Michiel,

Wow, thanks for building a .pisi package for Abiword. That was very kind of you. I had looked at the Wiki's instructions for building .pisi packages ( http://en.pardus-wiki.org/Pisi_Package ) but I didn't understand much of it. I have no previous experience with packaging and I believe this is above my skill level. In reality, it might not be that complex but it sure looks complicated.

I also like OOo Writer, but sometimes I prefer to use Abiword because it starts up faster on my (older) hardware and is more lightweight. If I try out your package, I'll report back on how it works on my system.

Thanks again.

< Edit: >

Michiel, many thanks for your time and expertise! I just installed your Abiword package and it seems to be working fine (although I obviously haven't had time to test it in depth). I'm attaching two screenshots of how it looks on my system. I'll let you know if I run into problems -- but don't worry, I won't expect you to fix them.  Smiley

Dank u wel,
111  Assistance / Pardus for beginners / Re: PiSi Package Manager GUI vs. command-line PiSi on: November 15, 2009, 18:06:34 PM
Hi, Andreas and Michiel,

Thanks for both your replies!


Thank you for clarifying that sudo pisi up -c system.base is not necessary after performing your very first update. (I thought I understood that correctly, and then when this PiSi problem occurred, I wasn't so sure anymore ...)


Thank you for the comments about your experience(s) with PiSi's GUI vs. the CLI. This helps confirm that to avoid update errors, it's probably better to use the CLI.

Actually, what I'm considering is a compromise: to let the Package Manager's GUI notify me of pending updates and to read the package descriptions provided (I write down a list of package updates and their version numbers in a small spiral notebook, in case something causes a major problem); then to perform the update from the CLI.

I'm still enjoying Pardus 2009 very much, and spent about 90% of my computing time last week booted into it. Currently the two applications I miss are Abiword (a little bit) and KMyMoney (a lot). The KMyMoney developers are working on a KDE 4.x version of the program, but they don't yet have a firm release date. Meanwhile I have installed HomeBank and taken a look at it, but have not created an account and begun entering checkbook transactions. I've read in another forum that Skrooge is a good alternative to KMM, but I didn't find it in the Pardus repos.
112  Assistance / Pardus for beginners / Re: fixing corrupt packages? on: November 15, 2009, 07:12:45 AM
Hi, trixon,

Thanks for your prompt reply and the quoted explanation. I'm relieved to hear that this is a non-problem. I will leave my "corrupt" packages alone, and wait to see what happens with the next round of updates.

With best wishes,
113  Assistance / Pardus for beginners / Re: PiSi Package Manager GUI vs. command-line PiSi on: November 15, 2009, 07:01:47 AM
Hi, Andreas,

Thank you for your reply. I'm sorry I forgot to mention that I did issue that command sudo pisi up -c system.base after I finished with my new installation, and before I made the very first update. (atolboo warned me that I needed to do that).

Must I issue the command sudo pisi up -c system.base before every update? Or is it required only before the very first update performed on a freshly installed system?

Thanks for any clarification.
114  Assistance / Pardus for beginners / PiSi Package Manager GUI vs. command-line PiSi on: November 15, 2009, 06:29:47 AM

To make a long story short, the past two days I've been trying to fix what I think is a PiSi-GUI-related problem. I solved the problem by using pisi from the command line, but I am confused as to why the GUI failed but the Terminal worked.

I had done two previous updates without any problem. Then PiSi notified me that there were 79 upgradable packages (ca. 138 MB in size). The largest was the qt-doc package (79.5 MB); I was using the default Turkish repositories. I made 4-5 attempts with the package manager's GUI to do the update; every time, the download would reach the 75-76% completion range, and then freeze.

I tried the steps suggested here in the forum of using #pisi clean, #pisi delete-cache and #pisi rebuild-db before I would try updating via the GUI again. But that didn't help.

Next, I decided to remove the Turkish repos and add the two Dutch (.nl) repositories in their place. Twice I tried peforming the update via PiSi's GUI, and both times it froze at exactly the same 75-76% download stage.

Finally, I was frustrated enough to experiment with using pisi from the command line. I found #pisi upgrade mentioned in the Wiki. To my surprise, the update worked this time! No freezing, no stalling. (I am still using the Dutch repos).

Does anyone have an idea about why this happened? Might the PiSi GUI have frozen because of the large package size? Is this a fairly common occurrence, or was this a fluke? Do most of you use PiSi via its GUI, or from the Terminal?

Thanks for any advice / suggestions,
115  Assistance / Pardus for beginners / fixing corrupt packages? on: November 15, 2009, 05:53:48 AM

While attempting to solve a PiSi-related problem last night, I tried several suggestions which I saw here in the User Forum. One suggestion involved using the command # pisi check. When I ran that command (which took some time to finish), PiSi reported that I have 10 corrupt packages.

I have searched the forum but I could not find any mention of how to solve this situation. Is the correct solution to uninstall the corrupt packages and then immediately reinstall them?

The reason I'm asking is that 5 of the corrupt packages are components of TeX Live (yet TeX Live is currently working fine for me). If I uninstall these packages, won't they pull along other TeX Live dependencies with them?

TeX Live was a large download and I would like to avoid uninstalling / reinstalling it, if possible ...

Thanks for any advice you might have.

116  General / General topics / Re: How did you hear about Pardus? on: November 09, 2009, 23:58:48 PM
I first heard about Pardus via the PCLinuxOS User Forums; it has a subsection on "Software Discussion." A couple of people mentioned their positive experience with Pardus and noted that it has one of the best KDE 4 implementations they had seen.

I went to DistroWatch and searched for reviews on Pardus. The linked reviews at DW -- and Caitlyn's article in particular -- convinced me to try it myself. Had it not been for DW, I would not likely have installed Pardus.

Pardus has surprised the heck out of me; I hope it will continue to improve and become more widely known. Based on my experience so far, it is on a par with some of the larger distros known for being "newb-friendly," such as Ubuntu, PCLinuxOS, Mint and Mepis.
117  General / Introduce yourself / Re: howdy from Texas on: November 09, 2009, 19:11:04 PM
Thanks to everyone for their advice and suggestions about RAM usage! I'm currently following atolboo's tip about KInfoCenter and am keeping an eye on how much RAM is being used in different situations.

I think I'm worrying about something I don't need to -- especially since the computer is responsive / quick enough for my taste. I will keep Michiel's suggestion about XFCE in mind for the future, if necessary. (I've used XFCE a tiny bit, but don't know my way around it very well).

My Pardus 2009 is still working well for me, and continues to impress me. I allowed the Package Manager to perform a large auto-update (approx. 250 MB) yesterday and it went fine. It even included a kernel update. I was slightly surprised that after the update completed, the system did not prompt me to reboot the computer. I did it anyway, and the GRUB menu list showed an entry for the new kernel (which had been added automatically). I booted into the new kernel without any problems.

If there are kernel updates, does PiSi usually prompt you in some way that you must reboot?

I'm starting to feel a bit more comfortable with KDE 4, but still have lots to learn. Pardus is making the experience more pleasant.  Smiley

118  Assistance / Software / Re: is TeX Live available in the Pardus repos? on: November 09, 2009, 18:47:36 PM
Hi, James,

Thanks for the heads-up. I installed a bundle of TeX Live [TL] packages last night; I opted for more rather than less, so it was a big download: approx. 540 MB. It took a while to download and install, but everything seems to be OK. (IIRC, installing the complete TeX Live setup takes up ca. 1 GB of hard disk space).

It's nice that Pardus's TL is so current: 2008. I also installed Kile 2.1 (which has made some changes to its toolbar and menus) and Texmaker. I didn't have much time to experiment with them but I'll test them more thoroughly in the next few days.

It looks like KBibTeX and pybliographic are not in the 2009 repos, so I was glad to see JabRef and installed it. I've never used it before, so that's something else new to learn ...

Thanks again,

119  General / Introduce yourself / Re: howdy from Texas on: November 07, 2009, 21:35:21 PM
Hi, trixon and atolboo,

Thanks to both of you for the tip about the first update. I've just done that and it went fine (or so it appears). But I am going to wait before I install a bunch of new applications until I can read some more and get more comfortable with KDE 4's layout.

I successfully installed Pardus 2009 last night and wrote a brief post about my experience:


Hi, Lisa,

Thanks to you, too. The cat in your avatar looks a lot like our cat Eeyore. She was a good cat who, unfortunately, died unexpectedly on Aug. 1 (probably from a heart attack or massive stroke). It was a shock and we still miss her very much. We adopted her from a shelter, so we don't know her exact age -- she was likely around 6 or 6.5 years old. She was probably about 1 year old when she came home with us.

We got her as a birthday present for our son when he turned 5. He was going through a Winnie the Pooh phase, and had already decided that her name would be Eeyore -- even though she was called "Taffy" at the animal shelter (because of her color). We tried to reason with him by explaining that Eeyore is a boy's name, and she was a girl cat and that name wouldn't fit ... but he was determined to stick with "Eeyore." So she became Eeyore.  Smiley  

I'm impressed with Pardus so far. One area of concern I have now is with RAM use; I have 1 GB of RAM (the maximum this old mobo allows) and according to the Sysinfo panel, only 27 MB of RAM are free. (And only Firefox is running). I have disabled Desktop Effects, so I'm not sure if this amount of RAM usage is typical for KDE 4 ... Have others noticed that KDE 4 is more RAM-hungry than 3.5.x?

I have not seen jerkiness with the video or extremely slow scrolling; I'd say that so far, the system is not snappy, but has been fairly responsive.

120  Assistance / Pardus for beginners / Re: Pardus 2009, GRUB2 and multibooting Linux on: November 07, 2009, 08:48:39 AM
Hi, everyone,

Yippee! I'm posting this message from my fresh Pardus install.

Tonight I was able to successfully install Pardus 2009 in some empty space on my /sdb. (I deleted Fedora 9 Sulphur, which reached its End of Life [EOL] in July or August, in order to make room). The installation process took about 40 minutes on this hardware; the YALI installer is very user-friendly and made it a pleasant experience. I chose to manually partition and basically followed the installation instructions given in the Wiki.

I followed the installer's recommendation and put GRUB on the MBR of /sda. Pardus auto-detected my Ubuntu setup on /sda (and I've just verified that I can boot into it OK), but for some reason it did not detect my PCLinuxOS installation on /sdb, so it does not appear in GRUB's menu list at bootup. (I will work on trying to fix that tomorrow).

< Edit: My bad.  Embarrassed Pardus did correctly auto-detect my PCLinuxOS installation, and I can boot into it. The entry was in the menu list all along; due to the way the list was displayed, the entries appeared to stop with my Ubuntu setup (with entries for the 3 most recent kernels and their recovery mode). It was late and I didn't realize that pressing the [Down Arrow] key would take me to the PCLOS entries further down the screen.

So atolboo was correct when he said that Pardus would detect the other installed systems. Again, my apologies for not realizing this. >

I had to do some very minor configuration in order to activate my wired Ethernet connection. Other than that, I think almost everything else was automatically set up. (Tomorrow I will test out more peripherals, such as printer, flatbed scanner, etc.).  

The "Kaptan" Welcome Wizard at first login is a nice feature, and I give it five stars. Right now, I'm at the stage of "Wow, I can't believe it was that easy to install" and also "Wow, why did the KDE 4 developers move everything to a different place? Lots of stuff is not where I expect it to be*!#!" I will hope that the learning curve is not too steep ...

I obviously need more time to reach a conclusion, but I think Pardus deserves wider attention and more praise. Congratulations again to Pardus's developers and everyone else who has helped with it! I am impressed with how polished it seems to be. Thanks to everyone on the forum who has helped me thus far,


Pages: 1 ... 6 7 [8] 9

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!