I recently installed xfce WM following the CL instructions here:

http://en.pardus-wiki.org/Xfce4#Xfce4

Everything seemed to go fine - except when I booted into my new xfce WM and discovered that there were no fonts, just small rectangular boxes where letters shoild be.

What's worse is now some of the applications on the KDE has also lost fonts and just show indcipherable little boxes.

Any ideas as to what went wrong?

Any ideas as how to fix it?

regrads,
Glas Cymru

For future reference:

The problem turned out to be the battery - once removed the laptop returned to proper functioning.

I've had Pardus installed on my Acer 3003 laptop without problem for some time - but recently a window entitled Kwrite pops up with the following text:


Message from syslogd@localhost at Sun Jul 22 15:01:50 2007 ...
localhost kernel: Oops: 0002 [#1]

Message from syslogd@localhost at Sun Jul 22 15:01:50 2007 ...
localhost kernel: SMP

Message from syslogd@localhost at Sun Jul 22 15:01:50 2007 ...
localhost kernel: CPU:    0

Message from syslogd@localhost at Sun Jul 22 15:01:50 2007 ...
localhost kernel: EIP is at vsnprintf+0x9c/0x49a

Message from syslogd@localhost at Sun Jul 22 15:01:50 2007 ...
localhost kernel: eax: 00000045   ebx: 00000001   ecx: b0399b50   edx: 00000002

Message from syslogd@localhost at Sun Jul 22 15:01:50 2007 ...
localhost kernel: esi: caf69f38   edi: 00000001   ebp: b0399916   esp: caf69ef0

Message from syslogd@localhost at Sun Jul 22 15:01:50 2007 ...
localhost kernel: ds: 007b   es: 007b   ss: 0068

Message from syslogd@localhost at Sun Jul 22 15:01:50 2007 ...
localhost kernel: Process hald (pid: 3049, ti=caf68000 task=cbddd2d0 task.ti=caf68000)

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel: Stack: 000000d8 b0398737 00000286 00000003 00000002 00000001 b0399b50 00000001

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel:        cbcb8340 00000001 b0399916 b017a061 caf69f38 cbc75480 cbcb8340 b02a6277

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel:        cbcb8340 b0399b50 00000000 00000001 cbcb8340 00000001 00000400 b0179ba2

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel: Call Trace:

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel: Code: ff ff ff f7 d0 89 44 24 10 8b 44 24 18 80 38 00 0f 84 eb 03 00 00 8b 44 24 18 0f b6 00 3c 25 74 11 3b 5c 24 0c 0f 83 11 03 00 00 <88> 03 e9 0a 03 00 00 c7 44 24 08 00 00 00 00 8b 44 24 18 8d 48

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel: EIP: [vsnprintf+156/1178] vsnprintf+0x9c/0x49a SS:ESP 0068:caf69ef0

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel: EIP: [<b025bc91>] vsnprintf+0x9c/0x49a SS:ESP 0068:caf69ef0

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel: kernel BUG at mm/slab.c:595!

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel: invalid opcode: 0000 [#2]

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel: SMP

Message from syslogd@localhost at Sun Jul 22 15:01:51 2007 ...
localhost kernel: CPU:    0

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: EIP is at kfree+0x2e/0x65

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: eax: 00000000   ebx: cbcb8340   ecx: cbcb8340   edx: b1a00000

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: esi: 00000001   edi: 00000202   ebp: c1388a4c   esp: caf69db0

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: ds: 007b   es: 007b   ss: 0068

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: Process hald (pid: 3049, ti=caf68000 task=cbddd2d0 task.ti=caf68000)

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: Stack: cbcb8340 c5f028a0 bd81ba40 b0179f88 00000010 b017a1b9 00000010 c1388a4c

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel:        b015ffe9 cbc4e240 bd7c82a0 bd81ba40 b13ff380 00000000 00000001 b015eb33

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel:        00000fff 00000010 b13ff388 b0120335 b13ff380 b13ff380 b13ff380 00000001

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: Call Trace:

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: Code: 56 89 c6 53 74 58 9c 5f fa 8d 90 00 00 00 50 c1 ea 0c c1 e2 05 03 15 90 25 5a b0 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 a8 80 75 08 <0f> 0b 53 02 f2 fb 37 b0 89 e0 8b 4a 18 25 00 e0 ff ff 8b 40 10

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: EIP: [kfree+46/101] kfree+0x2e/0x65 SS:ESP 0068:caf69db0

Message from syslogd@localhost at Sun Jul 22 15:01:52 2007 ...
localhost kernel: EIP: [<b015ce7f>] kfree+0x2e/0x65 SS:ESP 0068:caf69db0
d

Pardus has also been acting oddly with missing stuff and froze once.

I suspect that it is telling me that my Hard Drive has errors and is going down. (The WinXP OS on this laptop has also been behaving oddy and freezing up for no apparent reason.)

Just wondering - does anyone else have an alternative interpretation of the syslogs above?

It would be great if the website creator/editor NVU currently in the repository was replaced with Kompozer.

The NVU project closed some time ago and its successor, Kompozer, is its current and less buggy version.

Keeping up with the Joneses!

When I booted up this morning the usual configuration of a 5 second wait was back in working order.

My conclusion: This is an unstable bug and can't be relied on for consistency.

P.S. Thanks for the fix it tips above but I already knew how do it - I just posted it as a bug report rather than a "I need help" request.

I did a 'sudo pisi up' upgrade to 2007.2 yesterday and so far everything seems ok - although I haven't tested too much, (like the new desktop effects).

One minor annoyance I have noticed is the bootloader. It used to countdown 5 or so seconds and then start booting. Now it just sits there and waits till I press Enter.

Not a big deal, granted, but I suspect this effect of upgrading was unintended.

I run a computer repair shop in Wales and as part of our work we refurbish and sell lots of older computers donated by schools and such. We usually install Linux (for reasons of stability, cost, and freedom) on these computers. The type of Linux depends on the hardware.

As a rule of thumb, we wouldn't install Pardus on anything less than a 750 Mhz processor and 256 RAM. It does work on lesser hardware but performance suffers.

I sold a Pardus installed computer to a chap last month. He came back a couple of days later and I asked him how he was enjoying Pardus. He just said he installed Win XP over it without even giving it a try! Oh well - we're creatures of habit I guess.

The majority of computers we refurbish are Pentium 3 - 500Mhz (or Celeron - 400Mhz) with 128 - 190 RAM. We used to install Vector 5.8 Std. on these types but have recently switched to Puppy because of the excellent wizards that help people to configure their computer with relative ease.

Pardus is now my main OS at home and at work. Before that I was using LinuxMint - an Ubuntu-based operating system designed by a Frenchman living in Ireland. It's an excellent distro but Pardus edged it out due to its better file mounting facilities and easy to configure KDE desktop.

That's my story in a nutshell. I'd be interested to hear other experiences of 1. Pardus on various hardware setups and 2. other Linux distros on old hardware.

Is there any difference / advantage to downloading and installing 2007.2 as opposed to upgrading all packages via PISI? Does anyone know?

I've read lots of posts from Linux/open source advocates that look forward to Great Revolution (i.e the mass conversion to open source software throughout the world once its benefits are realised).

Of course it's human nature to desire popularity. There's strength and security in numbers - right?

But does this apply to computer operating systems that are increasingly intergrated into the Internet?

Or would mass coversion to Linux OSs spell the end of the relatively secure and uncluttered internet experience?

I think it would.

When the majority of surfers / consumers are running Linux - how long before all the advertising cookies, spyware, malicious viruses, etc. would also switch to target Linux? It wouldn't take too long I figure.

The great feature about Linux at present is that it tramples all through this Internet garbage largely unfettered. If Linux were to become the main operating system of the planet (like MS is now) our holiday would soon be over.

So I'm not looking towards the Great Software Revolution - I dread it.

How about you?

After upgrading all packages (presumably mirroring a beta2 installation?) i found that the mplayer firefox plugin would no longer play streaming video from my prefered news channel, http://www.russiatoday.ru/

But i's easy to fix. Right click on the mplayer plugin window, select 'configure', select the dropdown menu on 'Video Output', select 'x11', select 'OK', close plugin window, restart.

Works like it should again.

Here's what works for me:

Open the Konsole (Pardus>Programs>Sysytem>Konsole) and type (or copy/paste):

sudo pisi it http://paketler.pardus.org.tr/contrib-2007/limewire-4.12.6-2-2.pisi

Hit Enter and you will be asked for your password. Type it, hit Enter again, and  Limewire should be downloaded and installed. It can be found on the 'Internet' menu.

I think the lack of activity on this forum is in part an indication of the lack of problems with this distribution. People usually only post when they have problems and are seeking a solution. Perhaps Pardus is too polished to generate alot of forum discussion.

I'm thinking about buying a webcam - but only if it works with Pardus.

I live in the UK, if that makes any difference. (Probably not considering everything is made in China these days.)

So, has anyone had success with a webcam on Pardus? Which make/manufacteurer? Or which ones to avoid?

Thanks in anticipation,

Glasiad, Wales

I started this post because I couldn't get write permission for my usb flash stick.

I gave up and forgot about it.

I later used it without problem - same stick, same laptop. same Pardus.

I only remembered afterwards that I had a problem writing to it previously.

As far as I'm aware nothing changed and I don't have a clue as to why it just started co-operating with me.

For information:

The usb flash stick in question has a vfat file system.

My question is:

If Knoppix Live  and Wndows Xp can read and write to this usb flash stick without problem - why can't Pardus?

With regards to mounting and copying files from one partition to another on the hard disk, Pardus performs very well.