tux99

I have never had problems importing MIDI files with it, I haven't tried exporting though.

try to run the following command in a console as root user: urpmi --replacepkgs libxulrunner1.9

Just curious to find out how many of you upgrade all the time versus how many prefer to stick with one version for a longer period of time (according to the principle: if it ain't broken don't fix it). Please indicate only what version of Mandriva you are using as day to day OS, not whatever secondary experimental installs you might have. I'm currently using mdv 2008.1 on my main PC and my Libretto laptop and I expect to stick with it still for quite a while, as it's next to perfect, everything just works great! [moved from Talk-Talk by spinynorman]

Hi, For anyone who cares, I have packaged up the latest version of Rosegarden (1.7.3), a great audio and MIDI sequencer application, for Mandriva Linux 2008.1. It's available from my website at: http://www.linuxtech.net/downloads/rosegar...ndriva_rpm.html Any feedback about this rpm (positive and negative ;) ) is welcome! [moved from Software by spinynorman]

Try to comment out the 'Option "DPMS"' line, to do that put a hash (#) at the beginning of the line and then reboot or restart X.

Oh well, it can happen to anyone ;) Well after the support (i.e. the security relevant updates) stops, I generally do it for myself (that's what I did last time with mdk 9.2), ultimately for a personal desktop machine all I care about is updating internet facing apps (like the browser), so it's not much hassle, as it's not that many packages. And also having a supported distro doesn't necessarily mean being safe, just think of the openssl fiasco on debian... With regards to distro upgrades, I generally don't do them, it's much less hassle to keep the home and data filesystems separate from the OS and just reinstall the OS. Ultimately it takes less time and you can be sure that no legacy config files cause unexpected problems, even if it means some things have to be reconfigured from scratch. Even on a rolling distro like PCLinuxOS upgrades are often trouble, as far as I could tell by reading their forum for a while...

Duh, just noticed the original post is 5 years old, Praxis is this some kind of practical joke or did you not realize it either?? :huh: Whatever, I guess my ATI xorg.conf might still be of help to someone.

Who says you have to always upgrade to the latest version? I'm still running mdv 2008.1 on my main desktop and I very much doubt I will upgrade to 2009.1 when that comes out, mdv 2008.1 still does all I need it to do and it still has got the best desktop environment: KDE 3.5! (before I upgraded to 2008.1 I used mdk 9.2 for 4 years, I tested all the versions in between, but they all had some fatal flaws that made me stay with 9.2 until 2008.1). Anyway with regards to the dual screen problem I might be able to help as I used to have a radeon 9200 with a dual screen setup and I still have the xorg.conf for it (it's for the ATI binary driver fglrx), I don't think it will work as-is for you, but it might be a starting point for you to adapt yours (make a backup copy of your current config file first!): Section "ServerLayout" Identifier "Simple Layout" Screen 0 "aticonfig-Screen[0]" 0 0 Screen 1 "aticonfig-Screen[1]" RightOf "aticonfig-Screen[0]" InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" Option "Xinerama" "On" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:-1" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/mdk/" FontPath "/usr/X11R6/lib/X11/fonts/TTF/" FontPath "/usr/X11R6/lib/X11/fonts/encodings" EndSection Section "Module" SubSection "extmod" Option "omit xfree86-dga" # don't initialise the DGA extension EndSubSection Load "dbe" Load "type1" Load "speedo" Load "freetype" Load "glx" Load "dri" EndSection Section "InputDevice" Identifier "Keyboard1" Driver "Keyboard" Option "XkbModel" "logiitc" Option "XkbLayout" "gb" Option "XkbRules" "xfree86" Option "AutoRepeat" "500 30" EndSection Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "MouseManPlusPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "aticonfig-Monitor[0]" Option "DPMS" "true" EndSection Section "Monitor" Identifier "aticonfig-Monitor[1]" Option "DPMS" "true" EndSection Section "Device" Identifier "aticonfig-Device[0]" Driver "fglrx" Option "ForceMonitors" "crt1,tmds1,notv" Option "VideoOverlay" "on" Option "OpenGLOverlay" "off" BusID "PCI:1:0:0" Screen 0 EndSection Section "Device" Identifier "aticonfig-Device[1]" Driver "fglrx" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier "aticonfig-Screen[0]" Device "aticonfig-Device[0]" Monitor "aticonfig-Monitor[0]" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1280x1024" EndSubSection EndSection Section "Screen" Identifier "aticonfig-Screen[1]" Device "aticonfig-Device[1]" Monitor "aticonfig-Monitor[1]" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1280x1024" EndSubSection EndSection The sections of interest for you are: Screen (x2), Device (x2) and ServerLayout

Very useful post, if you could update this post once you have finished your testing this could go in the 'tips and tricks' section of this forum and surely be of much help to others wanting to do the same!

Interestiing report, my experience so far with earlier versions of MDV (up to 2008.1) and the mandriva nvidia binary drivers have been positive, I only had to change the xorg.conf manually for my dual screen setup (Mandriva, when will you finally add dual screen setup to the MCC tools??!!) With regards to pulseaudio, it's pointless, it's the first thing I always disable on a new install (unfortunately it's a hasssle to disable too, as so many apps have it as their default, that need reconfiguring). ALSA supports natively playback from multiple programs at the same time, and has been for quite a while, therefore I don't see the point of any 'audio server' anymore (apart from Jack for Pro-Audio use).

seems a bug, see here were someone else encountered the same issue: http://www.mandrivauser.de/viewtopic.php?id=24850 (in German) the workaround seems to be (according to the linke above): urpmi --replacepkgs glibc-2.8-1.20080520.5.2mnb2.i586

su => switches to root but keeps the current user's environment and current path su - => switches to root with root user evironment and changes to root user home dir (normally /root) it is generally advisable to always use 'su -', using 'su' without the minus can have strange effects as you will be root but still be using your own environment settings (sometime you want that, but if in doubt 'su -' is the better choice) I'm not sure about the drakboot problem but the file the error refers to seems to be: /boot/grub/device.map What does that file contain on your system, is a hd1 entry in there?

In your home directory should be a file called '.xsession-errors' which contains messages,warnings and errors from applications started from when running applications under X (at least this is on my KDE installation, not sure if it's the same with gnome but I think yes). Have you tried installing any more gnome packages as I suggested previously? If I were you, I would probably wait for 2009.1, but then better install it from scratch after having backed up your data and home directory.

But you said until recently the drive was working flawlessly and you haven't done any hardware changes recently in your PC, not even unrelated ones? If all that is correct and from the above test results, I would think it's most likely a hardware issue with the drive, CD/DVD burners fail eventually, I had already 3 die on me in the last 12 years. Even just for the sake of the long term reliability of the data you are burning, I would replace the drive, burners costs so little these days, it's not worth risking your data to a potentially defective drive.

I'm a KDE3 user so I can't help much with Gnome, but what I would do if I were you is, in the Mandriva 'install & remove software' tool (while using KDE4 or any other DE), open up the 'graphical desktop'->'gnome' section and install any package that sounds like it could be useful to make gnome work. Installing to much normally isn't a problem, but chances are this will also reinstall what's currently missing to make gnome work properly.

And with the recent upgrate to Firefox 3.0.X from 2.0.X they broke Seamonkey's totem plugin support (and have no intention of fixing it), see here: https://qa.mandriva.com/show_bug.cgi?id=48212 http://forum.mandriva.com/viewtopic.php?t=106196 I had to switch to the mplayer plugin for Seamonkey.

I can't tell what the problem is from the error log, but to help diagnosing it, I would try to boot off an older Live distro (ideally from USB so your CD drive is not tied up) and see if you get the same problem when attempting to burn a CD from that older distro too. (that would point to a hardware issue if you still get it with the older distro).

Have you tried the very latest Mandriva 2009.1 RC1? http://wiki.mandriva.com/en/2009.1_RC_1 Maybe it comes with a more up to date SIS driver

totem or mplayer should be able to play rm files, at least they do it as firefox/seamonkey plugins. With regards to the rpm package problem, try doing rpm -ql <package name> to see what files it should have installed and then check if those files really exist on your filesystem, or also try (verify).

I mentioned a while ago in some other thread, that IMHO KDE 3.5 was next to perfect, all they needed to do, is continue perfecting it (porting it to qt4.x for example) rather than starting from scratch. But I guess (and this is speculation!) that (understandably) wasn't fun enough for the coders, so they decided to start something completely different from scratch. What irritates me is that they called it KDE4, they should have called it KDENB 1.0 (KDE new beginning) or anything else to make clear in the name, that this is something entirely different than KDE3, not just a major upgrade. It's a bit like if Linus Torvalds decided to throw away the entire current kernel code and start again from scratch, but calling it Linux 2.8. I will, I'm giving every new major release a go (primarily by trying the latest Mandriva releases), but at the moment KDE4 is so far from my liking that I fear it will take a quite a while to become usable for me (if ever). No problem, but I really think we are off topic here in this thread, just to get back on topic, I must say that I'm glad that there are still distros like the latest PCLinuxOS who keep KDE 3.5 alive! :)

While this is getting a bit off topic in this thread, I'm speaking for myself and that's my opinion, I haven't bashed stability (as I never used the early versions of KDE4) or anything else, it's not about bashing, it's my opinion based on my experience with it so far (certainly NOT speculation!). If the KDE developers (or any developers) don't like criticism then they shouldn't publish their code, they are free to ignore my (and that of many other formerly happy KDE 3.x users) criticism, but then they shouldn't be surprised if they loose users. And explain me one thing, why should I spend considerable effort in getting used to a 'new way' of doing things if the 'new way' is actually by far not as good as the 'old way' (there needs to be a benefit that is worth the effort!)? It's for similar reasons that Vista is turning out to be a failure...

I agree with viking777, the problem with KDE 4.x is not so much the missing bits (which will eventually disappear) but the fact that they have made it very unintuitive and frustrating to use, it's not even in it self logical, it uses different ways to do the same things in different places, in other words, IMHO it's a usability nightmare. Yes I know it's possible to get used to everything, but I refuse to try to get used to an irrational desktop evironment, a desktop environment is supposed to help you make efficient use of your computer, ideally a perfect desktop environment should not require any time to be accustomed to by being completly logical and intuitive, not force you to almost do a training course for it's usage first. I think the KDE4.x developers got off the right track with KDE4.x creating a self-celebrating desktop, with the idea in mind that the user should spend more time playing around with the desktop environment than actually using real programs.

I'm not sure if you have 2008.1 or 2009.0 but on my 2008.1 I have the following (got updated a few days ago): # rpm -qa|grep -i openoffice openoffice.org-java-common-2.4.1.10-1.3mdv2008.1 openoffice.org-calc-2.4.1.10-1.3mdv2008.1 openoffice.org-writer-2.4.1.10-1.3mdv2008.1 openoffice.org-filter-binfilter-2.4.1.10-1.3mdv2008.1 openoffice.org-core-2.4.1.10-1.3mdv2008.1 openoffice.org-2.4.1.10-1.3mdv2008.1 openoffice.org-impress-2.4.1.10-1.3mdv2008.1 openoffice.org-kde-2.4.1.10-1.3mdv2008.1 openoffice.org-gnome-2.4.1.10-1.3mdv2008.1 openoffice.org-openclipart-2.4.1.10-1.3mdv2008.1 openoffice.org-common-2.4.1.10-1.3mdv2008.1 openoffice.org-l10n-en_GB-2.4.1.10-1.3mdv2008.1 openoffice.org-style-tango-2.4.1.10-1.3mdv2008.1 openoffice.org-dtd-officedocument1.0-2.4.1.10-1.3mdv2008.1 openoffice.org-math-2.4.1.10-1.3mdv2008.1 openoffice.org-draw-2.4.1.10-1.3mdv2008.1 openoffice.org-style-crystal-2.4.1.10-1.3mdv2008.1 openoffice.org-base-2.4.1.10-1.3mdv2008.1 openoffice.org-style-andromeda-2.4.1.10-1.3mdv2008.1

I guess it depends what you mean by 'productivity'... :D

Ian, you are right with 1GB RAM, but this laptop seems to have 3GB so I wouldn't worry about it, even if the graphics card takes away 1GB (and it won't normally), the 2GB left are still more than plenty with Linux! Of course dedicated RAM is better, but usually also more expensive. kili, the laptop hardware specs sound ok, it's impossible to say if all the hardware is 100% supported by Linux (but you can never be sure with any, unless you know from someone who has already tested it), but it doesn't ring any obvious alarm bells to me.