Dyslexic

I just installed Thac's packages on Cooker. I had several missing menu items for configuration tools in Cooker's KDE 3.3. Now they've magically reappeared! Installation notes: - Akregator 1.0.1 conflicts and must be uninstalled prior to installing KDE 3.4 - Mandrake's KDE-style-pulse package also conflicts (truth be told, I was happy to delete that) Problems: - KDM is broken. It restarts X when I try to login. I had to use GDM. - most KDE applications have messed up menus. Especially the help menu. (see attachment) - Konqueror has a messed up toolbar. (see attachment) - Akregator gives a "Can't find kfmclient" error when a URL is clicked - Kontact complains that it can't find knodepart.so upon startup. Clicking "OK" doesn't make the dialog box go away, but the KWin close button does. - KMenu side graphic is missing - Right-clicking on the desktop and choosing "configure desktop" does nothing. Observations: - Overall, great packaging. Much smaller bug list than I expected. - I haven't noticed the dramatic speedup everyone has been talking about, but it's not like KDE 3.3 was slow for me. - Sad to see icon zooming gone, but the new tool tips are slick. Too bad Kweather still uses the old Windows style tool tip. - Image viewing Kparts are very handy - KPDF is exellent, and incredibly fast. Mandrakesoft has backported it to KDE 3.3. - Trash applet is very handy

You can change that in the KDE Control Center under System/Login Manager, assuming you're you're using KDM/MdkKDM (which is the default). If you're using GDM, you can change it with the GDM Configurator.

See attachment. I'm not sure what the path to the attachment is, so I don't know how to link it. It's not showing up in the preview, so I hope it works.

It looks more like Daffy Duck as depicted by Stephen King. Mandrake 2005 Limited Edition (why would you ever put "limited" in the name of an OS?) may become the first OS to require a "frightening content" advisory for children. The folks at Mandrakesoft must be overworked and not thinking straight. You can get rid of it by installing the bootsplash-themes package and choosing a new theme in the Mandrake Control Center's "Boot" section, or simply disabling graphical boot entirely.

Are you sure it's a Mandrake packaging error and not a problem that ncurses developers need to fix?

Nvidia drivers aren't open source, so they don't belong in an open source distribution. End of story. I'm an Nvidia user; woe is me. RPMdrake is easy to use if you already understand how Linux package management works. If you're used to Windows or Mac OS, RPMdrake looks like something sent to us by the Klingons. If someone new to Linux tries to install KOffice, he's going to see a damn lot of KOffice packages and not know which one to choose. A new Linux user won't know what i18n packages are, or libs, or devel packages. Just look at the problems people on this board have. RPMdrake is a good start on making an easy to use installer, but it has a long way to go. Red Carpet is the closest thing I've seen to a user-friendly installer. It was open source, wasn't it?

I don't think it matters how big the change was from 9.2 to 10.0 compared to 10.0 to 10.1. Mandrake 10.0 broke compatibily with the 9.x series in several areas. When you break compatibility, a new major release is justified. Also, I'd hardly call switching to entirely different kernel generation a minor change. Kernel 2.6 added a lot of new features. A lot of the new stuff goes unnoticed because of the nature of a kernel. Users aren't going to fire up KDE and say, "Wow, Morton did a great job with the new scheduler!" Also, a lot of people don't use many of the new features because they're aimed at scalability on big iron, but that doesn't mean they're not there. And don't tell me it doesn't matter since Mandrake doesn't get deployed on big iron. It's not like Mandrakesoft can say, "We're going to include new stuff, but downplay it because no one will use it." As for the new release schedule, having the latest KDE/Gnome/whatever isn't what I'm worried about. Let's say I buy a laptop in June 2006. Am I really going to install a distribution from 8 or 9 months ago? How many ACPI releases ago was that? Will my Intel 802.11n be supported? The same applies to desktops with newer hardware. Intel's dual core chips are coming soon. As it turns out, it will likely be before Mandrake 2006, but if Intel magically pushes the release back and the appropriate kernel misses the freeze for Mandrake 2006, dual core owners have to wait a year before they can use Mandrake. Yes, I'm aware kernel devs have had specs for a while already. I'm not saying dual core specifically will be an issue, I'm just using it as an example. It seems like Mandrake is trying to be like RHEL, but with a totally different user base. I guess the logic is that if they have a longer release cycle, they'll attract more enterprise clients, but where does that leave soho users? How will Mandrake fare while other desktop distros try to be cutting edge in time for the Longhorn release?

That happened to me a few times. Cleaning out my /etc/fstab and /etc/mtab files fixes it temporarily. USB mass storage handling has improved a lot in Cooker.

I don't see your cam listed in the hardware list for that driver, but I'll take you at your word that this is the right driver. Yes, you need to build the driver. The instructions for doing so are included with the source code. Basically, you'll have to install the kernel-sources-2.6 package, download the experimental version of the driver, compile it according to the instructions, and load the driver.

Try the following commands: rpm -e --nodeps libgtk+2.0_0-devel urpmi libgtk+2.0_0-devel

Can you install other packages, or is this the only one giving trouble?

I won't claim any expertise in this. I build my kernels from Mandrake sources just to avoid such problems. I would wildly speculate that something from initscripts is calling a module that is not in your kernel.

Try installing the libgtk+2.0_0-devel package with urpmi/RPMdrake.

In each of these cases, you appear to be missing dependencies that can be solved by installing the appropriate devel packages. If you don't want to use RPMs, you can compile each dependency as it's reported missing. In this case, atk is the next one to try. You'll also need headers for Freetype and Xorg.

You can try pressing esc at the lilo boot menu, then type linux noapic at the prompt.

When compiling software, you need to specify the installation path, or a default will be used. You do this with the command ./configure --prefix=/usr. If you don't give the prefix, your files will install to /usr/local. Having said that, you shouldn't install a new version of glib from source unless you really know what you're doing. Otherwise, you can break your system. The most common cause of the error you're getting is from not having the libglib2.0_0-devel package installed.

VNC can be a bit tricky to run if you're not used to the Linux version. If you try to run it more than once without shutting it down properly, you'll have a bunch of stale lock files lying around. Each lock file causes the screen number to increase by one, which also increases the connection port by one. My advice is to use the KDE Control Center desktop sharing (krfb), or the Mandrake Control Center desktop sharing (rfbdrake). Both are compatible with the Windows VNC/TightVNC clients.

I think a better analogy would be "Warning: some people are allergic to this dish." For example, a few of the XMMS packages depend on OpenGL, which can be unstable if you don't have solid OpenGL hardware, and OpenGL drivers correctly installed. Take a look at the Windows world. There's even greater choice in terms of available software, but the free ones will often give you tape worms. Would you rather have to monitor your allergies, or have tape worms? As aforementioned, the choice is yours. A few years ago I decided I liked Linux enough to only buy compatible hardware. Consequently, pretty much everything in the official distribution works for me without any issues.

1.) Mandrake package selection is rather quirky. If you choose "individual package selection" when you're installing, Mandrake automatically selects more of the basic packages, even if you don't actually change the default selections. I don't know why you couldn't find g++ and gpp. They're both part of the main distribution. Did you use urpmi -y g++ to search? Or even use the GUI the Mandrake Control Center? 2.) I've never actually tried compiling MySQL, so I don't know if it requires kernel headers. If you're in the practice of compiling software to bring your system up to date, you should probably have them installed. 3.) The Official distribution doesn't change, so the mirrors should all be the same. The update sources are generally in sync within a few hours. Some servers are faster than others, but they should all work.

Here's a problem I've been having with Mandrake for years. I think I must be missing something. If Mandrake allows multiple kernels to be installed, why does it not allow the matching source to be installed for each kernel? It's driving me nuts. I would MUCH rather change a symlink instead of having to reinstall the kernel sources every time I switch kernels. Also, if I forget to keep a copy of all the kernel-source RPMs lying around, I'm pretty much screwed since Mandrake only makes the latest kernel-source package available. Can anyone show me the error of my ways?

I had the exact same problem as you with an AIW Pro 128 card using XawTV. I can't explain why it happens, but I remember that several other people had the same problem. AVview worked perfectly. You can get AVview from contrib or the Gatos site. I don't know if the AIW 9600 works or not. Mdk 10.1 uses Xorg 6.7.

You may have installed the wrong kernel-source package. If you have the default Mandrake kernel, you want the kernel-source-2.6 package. If you're using the command line, type urpmi -y kernel-source to list available kernel source packages.

Digikam's hardware support depends on gPhoto2. Try updating to the latest version of gPhoto2. Alternatively, you can put your camera in PTP transfer mode.

I'm running Cooker 10.2, and KDevelop is there.

Are you writing new files/dirs with the same user who created the dirs you're trying to write to?