adamw

well, a conditional was added to the spec for it in 2003, disabled by default. I'm not quite sure why. I could ask Goetz if he remembers, but it's unlikely. =) possibly id3lib wasn't a dependency he wanted to introduce at the time. I can probably turn it on for Cooker, but it's in /main so it'd be kind of a pain to ship an update for it.

Why aren't you using the packaged driver in Cooker?

For undefined references, try just adding:

%define _disable_ld_no_undefined 1

to the top of the spec file. It's a workaround not a fix, but that's not actually that important in this case.

edit: none of the %*dir macros are at issue here, this is simply a code bug. But for reference, they're defined in /etc/rpm/macros.d/kde3.macros .

jmo: well, that's odd. You could try switching the Phonon output plugin from Gstreamer to Xine (install phonon-xine package first) in KDE Control Center (not Mandriva Control Center). It may help.

"driver 'sr' needs updating please use bus type methods"

Whatever your problem is, it's not that. That's a harmless kernel message that gets printed on every single boot of Mandriva, working or not.

What else is printed at the console? Have you checked if it's not just this known issue:

http://wiki.mandriva.com/en/2009.0_Errata#..._not_created.29

? Thanks.

I don't think anyone within MDV has time to do it, no. The official KDE team has to work on KDE 4 for 2009 Spring and fixing bugs in 2009, and they're only a very few people. As dexter said, you could try rebuilding it yourself.

tux: fvwm is a single package that's very easy to build and has little in the way of external dependencies. KDE is...not. It's organizationally messy to include both KDE 3 and KDE 4 and it results in some compromises, it's not a sustainable situation for multiple releases.

Yes, there are big organizations stuck on KDE 3 so any security issues will likely be patched, and maybe any bugs that some sufficiently big organization considers important enough to pay to have fixed. But that's about it. None of the core KDE devs who get to choose what they work on, are working on KDE 3 any more. Just check the SVN commit logs, if you want to see. KDE 4 is where all the effort is focused now.

Can you try just running:

modprobe pata_marvell

as root, right after booting the system, before putting a disk in the drive? Then put a disk in, and see if it works.

Do other operations give you sound output? Does the system have more than one sound output device? thanks!

It's just because your ATI card is more powerful. The 5200 is a five-generation old, entry level card.

"and from what I read KDE 3.5 will still be supported for several years by the developers."

This is not the case. KDE 3 is already essentially unmaintained upstream.

2009 Spring will not include KDE 3 as a usable desktop (some KDE 3 packages remain so we can build critical apps that haven't been updated yet, but you can't log in to the desktop).

.ogg ought to work out of the box...can you check if gstreamer0.10-decoders-audio is installed? Thanks.

"nvidia and kde4 are also a bit problematic still"

whereas everyone's entirely happy with the performance of the latest ATI proprietary driver? :)

auto-orphans is a new feature of 2009, it won't be in anything based on an earlier release of Mandriva.

So, wait, you have a router which provides a connection via cellular data, but your PC just connects to the router via regular Ethernet?

In that case, as far as Mandriva's concerned, it's just a perfectly standard Ethernet connection. It doesn't matter at all to Mandriva and your laptop how the router ultimately handles the Internet connection - that's the router's problem. All your laptop cares about is talking to router, which is done as a standard ethernet connection.

If I read your post wrong and this is not actually your situation, please clarify :)

So, further: in no case will the purchased version of Mandriva work better than the One edition for networking. The things that are unique to the purchased version are commercial software, and there's no commercial hardware drivers included, so as far as hardware support goes, One and Powerpack are basically identical.

Free has slightly worse hardware support out of the box than One or Powerpack, simply because it only contains free software; it doesn't contain any non-free-but-redistributable software, like the NVIDIA and ATI graphics card drivers, or the firmware for Intel wireless adapters. These are included in One and Powerpack. You can add them to Free easily once you have an Internet connection, but they're not there out of the box.

2009 does work with some hardware that didn't work with 2008 Spring, but we really need some more details on exactly how your network is set up and what the problem is before we can be sure what it is you need. But definitely don't go out and buy a Powerpack, yet - it's not the answer to this problem.

Note that you will lose quality each time you decompress and recompress, so try to do all your edits in one operation - don't forget to edit something in one section and then have to decompress and recompress that section again :)

You should definitely use at least WPA. WEP is so easily breakable at this point that it's virtually indistinguishable from running no encryption at all; you can download point-and-click GUI tools for Windows and OS X that will break into any WEP network in about 20 seconds.

Using WPA-PSK is just as easy as using WEP, it works pretty much the same as far as you the user is concerned: you just set a key on the router and set the same key on all the clients.

Can you file a bug on this at http://qa.mandriva.com/ , and send me the URL when you're done? I'll make sure the maintainer takes a look at it. Thanks!

Right. It's OK for quite a lot of things to show up as 'unknown'; it's not the case that you need to 'fix' each one. It would be best for you to identify exactly what pieces of hardware you're actually having problems with, and we'll try to help you with that. Thanks.

Also, run this command as root:

grep -10 touchkitusb /var/log/messages

and paste the output here. thanks!

See, this is why I hate duplicate threads - I just posted more or less the same info as coverup in your other thread. :) Please don't post the same thing in multiple threads. Thanks.

If 1920x1200 is the native resolution of the panel, you really should use it (except perhaps for games it's not capable of running smoothly at that high a resolution). Running an LCD display at anything less than its native resolution (or an exact, integer multiple of it) inevitably looks bad, because LCD displays actually have physical 'pixels' - your display has 1920 horizontal elements and 1200 vertical ones. Trying to display 1440 pixels on 1920 LCD elements inevitably results in a loss of quality because you can't do it perfectly - something is going to come out distorted. That's why you should always stick to the native resolution.

If you find fonts too small at the native resolution, you should set the display DPI correctly: to find the correct DPI, measure the actual screen area horizontally in inches and divide 1920 into that number, and that's the DPI of your screen.

If you're running KDE 4, there isn't an easy way to set an arbitrary DPI. However, you can set it to 120, which would likely be pretty close to correct for a 1920x1200, 15.4" monitor. Run the KDE Control Center (not the Mandriva Control Center, they're different), double click Appearance, single click Fonts, and change the 'Force fonts DPI' box to 120 DPI.

I believe KDE 3 is similar to KDE 4.

If you're running GNOME, you can set an arbitrary DPI in the GNOME font config tool: System / Preferences / Appearance, click on the Fonts tab, click on Details, and change the Resolution value to whatever you calculated.

That should make fonts look the right size on your screen. Note that even if you're in KDE, GTK+ apps - like Firefox - will respect GNOME's setting.

You could've just read the Errata ;)

http://wiki.mandriva.com/en/2009.0_Errata#...in_One_editions

urpmi task-kde4 will probably restore the stuff you need. Package removals are logged to /var/log/messages :

grep removed /var/log/messages

will find 'em for you.

Look in the official forums, there's several threads on this there.

yer0: thanks for confirming. It won't be uploaded to the official repositories as it may cause trouble for other Chrome hardware, upstream don't consider the code clean enough for general use yet; it's just a quick way for me to provide a working package for you (happyassassin.net is my own site). Once 0.2.904 final comes out, I will put it in /main/backports .