View Full Version : for the Linux experts, WINE problem
Well, I tried to install some older games in Linux(Ubuntu 9.10) today (Locomotion and Act of War) and both installers give me an error code "0x8002000E" at startup and then when i get to chosing an installation directory, i can only select C:\windows, changing it has no effect, trying to go on always says it's an unacceptable directory.
Couldn't find anything using google, so does anyone have an idea?
Oh and no suggestion to use Windows please, I got a Windows PC next to me but I am trying to get this to work in Ubuntu, ok...
Have you run 'winecfg' yet? Part of what that program does is create a directory structure inside of a .wine folder that you'll find in your home directory.
Also, use Windows. :smash:
Yes, I have, created a drive in my folder, but whenever I select it in the installer and click OK, it says C\Windows again.
Did you download the latest wine or did you install the one from the repos?
Did you install i386 or amd64 distro?
Tellos Athenaios
04-03-2010, 02:55
Are you on Wine 1.1.41? There is a regression that prevents installers from running properly: http://bugs.winehq.org/show_bug.cgi?id=22066
According to a bug report there should be a new version (1.1.42) out in “two weeks”:
It's a development release, things are often broken. 1.1.42 should be out in
two weeks, so either use 1.1.40, patch 1.1.41 manually, or wait for 1.1.42
(assuming this patch makes it in).
Patch:
Patch sent: http://www.winehq.org/pipermail/wine-patches/2010-March/086074.html
Which is reported to fix the issue; if you can't wait, can't downgrade but are up to compiling from git...
Tellos Athenaios
04-03-2010, 02:56
Did you download the latest wine or did you install the one from the repos?
Did you install i386 or amd64 distro?
Should not be relevant as Wine is i386 exclusively and pulls in ia32libs and so on.
Tellos Athenaios
04-03-2010, 03:00
Also, use Windows ReactOS. :smash: http://www.reactos.org/en/index.html
Be pretty interesting to see how that works out if and when it matures a bit. :smash:
Tellos Athenaios
04-03-2010, 09:07
FWIW: If you hadn't already and you want to have the most current wine; you can add the Wine deb repository to your APT sources (lists). If you have a recent Ubuntu (like 9.10 or newer) it is a simple:
sudo apt-add-repository ppa:ubuntu-wine/ppa
Which will import the archive PGP key and source list. Then you can update your software sources (sudo aptitude update) and your system should know about the latest wine versions available as debian packages.
Thanks Tellos Athenaios, I already added the upgrade path but not via console, did it in the software repositories window, that's how I got 1.1.41 in the first place.
Wouldn't know how to downgrade or apply that fix, just had a look at Linux for about a week and it wasn't a very deep look either, google provided a bit of help and fortunately it's very automatic by now, the console gives me nightmares, I'd need a course to learn how it works ( I know, you type things into it, but I mean how the commands work, yesterday I learned "cd home" doesn't work, has to be "cd /home", my luck that it was "cd" at all :laugh4: ). Sudo, judo, budo, ppa, etc. doesn't tell me anything(yet). :sweatdrop:
Tellos Athenaios
04-03-2010, 12:09
If you need to know how a command works there is usually a help screen for it; or better yet a manual or info page. You can type man <man_page> to access a manual page; and info <info_page> to access an info page (for some programs there is a difference between the two, apparently). Typically <man_page> or <info_page> is the same name as the program you want to read up on; e.g.
man sudo.
For a start try reading
man builtins; which details the standard commands the bash shell recognizes without additional programs.
EDIT: If you are really interested a Bash scripting guide such as this: http://tldp.org/LDP/abs/html/ should prove useful.
PPA is quite specific to Ubuntu and means Personal Package Archive. Canonical (the company behind Ubuntu) have this project site called Launchpad (which is similar to SourceForge) and PPA's are essentially the archives of projects hosted on Launchpad. The program add-apt-repository knows how to obtain PGP keys from the Launchpad server and how to resolve the name of a PPA archive to something that can be used by the other software package management tools on the system.
And sudo is a program which is used to temporarily grant you administrative powers which is required if you want to fiddle with system software and system wide configuration settings.
Thanks for the help, Tellos!
Just got the update for Wine and all the installers seem to be working now, even got Steam to work, which feels kinda surreal in Linux. :laugh4:
...Linux(Ubuntu 9.10)...
Seriously... please try a real distro - in fact anything but that thing.
:2cents:
Seriously... please try a real distro - in fact anything but that thing.
:2cents:
You mean one that only consists of a DOS-like console environment?
The university offers a course to prepare to get the LPIC-1 certificate (http://en.wikipedia.org/wiki/LPIC), I'm planning to do that.
You mean one that only consists of a DOS-like console environment?
Not what I meant, but there are some far better distros than Ubuntu around. e.g. Debian, Fedora, Arch, Gentoo, etc, to name but a few. You will probably have to discover what's 'wrong' with Ubuntu yourself though - but IMHO you're better off with Debian Squeeze (testing) every time. The upcoming Ubuntu release is based on Squeeze anyway - where previous releases, including the current, were based on Sid (unstable).
Ubuntu is, in a nutshell, Debian unstable with a brown theme (purple nowadays!), easy access to proprietary software and plenty of dodgy marketing thrown in. Anything you can do with Ubuntu can be done with Debian, the difference being that with Debian it will take a bit more effort on your part, but the results will be solid, lasting and you will learn something in the process.
Also the terminal is a fact of life with Linux and it won't be going away - once you get into it you won't look back, first you have to realise why it's necessary. The only reason it's thought of as "DOS-like" is because people from a mainly windows background associate a command line with DOS - which is 'old'.
Tellos Athenaios
04-27-2010, 18:19
Ubuntu *is* a real distro. It's not a distro aimed at the same audience as Fedora is, or Debian is, or Arch/Gentoo are.
I'd define the intended audiences as follows:
Ubuntu: for those who want to run a Debian installation but do not wish to spend the time administrating it. Essentially what Windows XP was to the NT range of Microsoft's OS. It is, understandably, similarly popular. It has very much the same approach to the technical side of things as Debian, except it wants to run a considerably more recent crop of software than Debian does (generally speaking it is halfway between Debian sid [unstable] and Debian testing on release). Also it does not mind proprietary software (including drivers) as much; as long as it is freely redistributable. Users that run pre-release versions of the distribution run essentially the Fedora equivalent of a Debian based system. Users that run LTS (long-term-support, is extra stable) releases are essentially Windows XP users who want a Linux.
For those who want & expect to run (much) the latest software found in Linux land: Fedora. These people must have some of the skills, persuasion & perseverance to run Debian but in addition are supposed to file bugs on their software, too.
For those who want & expect to control their software through manual configuration after installation: Debian. There is a strong emphasis on “it just works”, if not before configuration to make it work the way you want to. In addition you had better drop your proprietary ways if you want an easy time on Debian. You are expected to read man pages, /usr/share/docs/ and the various other documentation of the packages you seek to tame. It's not so hard, just time consuming. Essentially this is a system administrator's distribution with its emphasis on stability, wide range of software: installing Debian is best done once, and the resulting OS imaged and copied to other machines.
For those who like & expect to control their software from building it to configuring it after installation: Arch & Gentoo. It is essentially a BSD approach to a free OS.
Now personally I am of the opinion you can save yourself a *lot* of time, brain cells, and money otherwise spent on various substances to kill or appease aforementioned brain cells in frustration, if you chose a Debian based installation. Package management that just works is a godsent. Building from source means you either have faaaar too much time on your hands or you cannot upgrade nearly as often as the binary distributions allow you to.
And if you do chose a Debian based system; and if you do want to run much of the latest software (not to mention hardware)... Ubuntu is not such a bad choice after all. Although, I must admit that I run Kubuntu (KDE 4.4.2) myself because I find Gnome to be an inflexible, unwieldy, eye sore in general. It is however true that Ubuntu adds things in their Gnome'd flavour, of questionable value such as a compositing window manager (desktop effects are sweet, and you might have chosen to install one anyway, but one can certainly question the wisdom of including it by default).
So if I understand that correctly, KDE and Gnome are two different graphical user interfaces for Linux and Ubuntu uses Gnome while Kubuntu and SuSe for example use KDE?
And yes, I know the console is an important part of Linux.
And I made my Ubuntu theme look dark grey and added my own wallpaper, why is that important, I thought you Linux/Win XP people don't care about graphics at all? ~;)
And there are some instabilities but those seem to be mostly related to the Flash/Opera combo and the programs itself, the OS seems to run pretty fine most of the time.
Fiddling around with it myself might just as well mean that I would break things myself and not know how to fix them, not get a single program to run for a month etc.
It's nice when it finally works etc. but I'd rather learn the basics properly through that course for example and then add to it myself, don't want to turn my Linux notebook into a day job.
Tellos Athenaios
04-27-2010, 22:10
You can think of both as a suite of applications and a desktop environment for your Linux machine, yes. EDIT: Although, you can run KDE on your Windows machine as well. There's a Windows port (which does not have feature parity with the main Linux product) and IIRC a Mac OSX port in the works, too.
And it is certainly not true that Linux people don't care about graphics. I'd say many might care quite a bit more than do Mac OS X users. If you care about making your OS work the way you want it to, you probably would not stop short of making it look how you want it to.
Ubuntu *is* a real distro. It's not a distro aimed at the same audience as Fedora is, or Debian is, or Arch/Gentoo are.
<etc>
I'm afraid I disagree strongly with your overall definition.
With respect to the first point, this is somewhat of an oversimplification. Windows XP and Windows NT are not the best analogy for this. Ubuntu does not run a "more recent crop" of software to Debian. It's based on Sid and always has been. This myth comes from the fact that Ubuntu's repositories are more up to date than the stable (currently Lenny) repositories - of course it they are, but that's because they've been based on Sid's. I find it roughly equivalent to a mixed Testing/Unstable system.
Debian also allows proprietary drivers. The difference again is that Ubuntu provides a GUI tool for their installation. All of the proprietary drivers in Ubuntu are from upstream - Ubuntu simply provides the GUI. I'm afraid LTS are not "stable" either. The latest is Squeeze based (not stable) The only "stable" Debian based distro is Lenny. This is why Lenny is so "out of date" (though the average Ubuntu user could get what they want running on Lenny pretty easily with backports). The definition of a stable system is probably arguable, but in general it's a system that is pretty much guaranteed not to receive updates that will break it. Ubuntu LTS and non LTS regularly receive such updates due to their being based on the Sid or Testing branches.
On your second point. Fedora is no more up to date than Debian Sid - in fact Sid is usually ahead in terms of updates. Debian Sid or Testing users are also supposed to file bug reports. So I'm not sure I get your point?
Third point: I'm a long term Debian user. I run a mixed Sid/Testing setup. I have no idea where you get the "proprietary ways" idea from? My system is full of binary blobs - out of necessity. fglrx (latest pre-release), firmware-nonfree, wireless adaptor microcode running under ndiswrapper to name but a few. I didn't need a degree to install them. So this idea that it's for "sysadmins" just doesn't cut it with me.
Man pages? I hardly have to read them - but when I do it's for bash commands that I would need to understand regardless of distribution. Debian has some of the best wikis and howtos as well. Far better than the Ubuntu ones and more up to date. With Ubuntu a lot of the dependence for support is on the 'community', which is not ideal for reasons I won't go into.
As to Kubuntu, it's now pretty well known for it's poor KDE implimentation. OpenSUSE or Mandriva's is superior.
So if I understand that correctly, KDE and Gnome are two different graphical user interfaces for Linux and Ubuntu uses Gnome while Kubuntu and SuSe for example use KDE?
gnome and KDE are "desktop environments". You can install whichever you prefer. KDE, gnome, XFCE etc. There are also a wide range of "window managers" such as fluxbox, openbox, icewm etc. Window managers are less bloated than full blown desktop environments but not as fully featured (to start with).
And I made my Ubuntu theme look dark grey and added my own wallpaper, why is that important, I thought you Linux/Win XP people don't care about graphics at all? ~;)
Not important at all, "the brown one" is a nickname.
And there are some instabilities but those seem to be mostly related to the Flash/Opera combo and the programs itself, the OS seems to run pretty fine most of the time.
I'm afraid flashplugin-nonfree "sucks" and always has as far as I can remember - (blame adobe). It "works for me" at the moment, but in general it uses tons of memory and does have stability issues. You might want to try an open source alternative (such as gnash), but bear in mind that they lag behind adobe flash. I have found that the plugin works better in firefox than opera anyway.
Fiddling around with it myself might just as well mean that I would break things myself and not know how to fix them, not get a single program to run for a month etc.
Part of the learning process. I remember fiddling around with windows and breaking it back in the day. Then I went through the process of fiddling around with and breaking Linux. in all honestly though if you're just installing packages, and if you know what you're doing, then you shouldn't break anything.
It's nice when it finally works etc. but I'd rather learn the basics properly through that course for example and then add to it myself, don't want to turn my Linux notebook into a day job.
:bow:
Tellos Athenaios
04-28-2010, 17:14
First of all I am comparing release versions. Thus the unstable branch of Debian is somewhat irrelevant; yes: Debian Sid is usually more up to date than anything. It's closest analogy is Fedora Rawhide. And more or less famously: the question of “how do you run it?”, is answered with “you don't” [that is the Debian wiki, not me]. These are not real distributions: these are dumping grounds for new code to be tested.
Now, when it comes to *release* (supposedly: *stable*) versions: Ubuntu, or at least, Kubuntu is certainly more up to date than Debian Squeeze is. When I had KDE 4.4.2 on Kubuntu, I'd have KDE 4.3.4 on Squeeze (testing). KDE 4.3.4 was 9.10 material for Ubuntu. As I said: Ubuntu is in between Squeeze (testing) and Sid (unstable), with the early alpha being mostly Sid and the release being closer to Debian testing.
The proprietary ways bit comes from a lot of `fun' with ndiswrapper & fglrx, including but not limited to unrecoverable installations. YMMV. The bit about manpages is probably clarified with a simple `man xorg.conf'. Similarly, polkit/policykit have man page entries for their configuration as well IIRC. Of course, you do not have to configure your system. But my point is: if you don't want to do the configuration dance then maybe Ubuntu is not such a bad option -- it comes with mostly sensible defaults and a considerable later crop of software out-of-the-box.
Ubuntu (LTS or not) does not intentionally receive any update that `breaks' the system in the way you mention it. Have you actually *used* Ubuntu? I ask because if you had used it you would know that the Ubuntu repositories are most definitely not the Debian repositories, that you should not even attempt to mix the two (barring some very specific apt.get wizardry), and that there is such a thing as a “Debian Import Freeze” and it is before the first alpha is released. You will, therefore, never get your updates directly from Debian Sid or testing if you run a release version of Ubuntu; and Ubuntu LTS means that you get updates on your software for a longer period. Also LTS releases are based on LTS kernels which typically means the kernel of (next) RHEL. In casu 10.04 ships with 2.6.32 for that reason.
First of all I am comparing release versions. Thus the unstable branch of Debian is somewhat irrelevant; yes: Debian Sid is usually more up to date than anything. It's closest analogy is Fedora Rawhide. And more or less famously: the question of “how do you run it?”, is answered with “you don't” [that is the Debian wiki, not me]. These are not real distributions: these are dumping grounds for new code to be tested.
Sorry but no, Sid is actually a working, downloadable distro (http://www.debian.org/releases/unstable/) that is actually surprisingly stable. You may need to actually install and use a Sid system before you can make a fair assessment. I would guess from the above that perhaps you haven't? If not then I highly recommend it. In Debian terms "releases" are when the "freeze" occurs and the current testing branch goes stable and the previous stable is move to old-stable. most Debian users don't actually use stable on their desktops - they use either Sid or Squeeze or a combination of the two (this is where a part of the concept of Ubuntu originally came from).
Now, when it comes to *release* (supposedly: *stable*) versions: Ubuntu, or at least, Kubuntu is certainly more up to date than Debian Squeeze is. When I had KDE 4.4.2 on Kubuntu, I'd have KDE 4.3.4 on Squeeze (testing). KDE 4.3.4 was 9.10 material for Ubuntu. As I said: Ubuntu is in between Squeeze (testing) and Sid (unstable), with the early alpha being mostly Sid and the release being closer to Debian testing.
The reason Kubuntu is more 'up to date', is because it's not stable, thoroughly tested software and Ubuntu are known for pushing through untested software before it's ready (believe me I know). Yes you're getting something 'newer', but you're also getting something that's far more likely to break - and break it does.
KDE 4.4 should be in Sid soon - it wasn't last time I checked (still 4.3.5 I think?). Last I heard they were holding off due to the problems most other distros were having with it. Most of those problems have been ironed out now. It gets released "when it's ready".
Debian Stable is used extensively for servers, including webservers of course where security patching and stability is a must. If you've ever tried Stable, you'll know that as a desktop it's also rock solid and dependable. As I've touched on before, backports are the best thing about Lenny. You can get most of the latest packages from Sid and Squeeze and put together a decent desktop with most if not all of the packages that you want. Mrs Asai's PC runs Lenny with backports and is nothing but dependable. I'm toying with the idea of upgrading it to squeeze though.
The proprietary ways bit comes from a lot of `fun' with ndiswrapper & fglrx, including but not limited to unrecoverable installations. YMMV. The bit about manpages is probably clarified with a simple `man xorg.conf'. Similarly, polkit/policykit have man page entries for their configuration as well IIRC. Of course, you do not have to configure your system. But my point is: if you don't want to do the configuration dance then maybe Ubuntu is not such a bad option -- it comes with mostly sensible defaults and a considerable later crop of software out-of-the-box.
I've never had an "unrecoverable installation" from either fglrx and certainly not ndiswrapper either. If fglrx causes hard lock up, it's usually because you installed an fglrx module that wasn't built for your specific kernel. This is actually the circus that has happened a few times with Ubuntu at dist-upgrade time. In fact with any proprietary closed source drivers it's pretty much unavoidable.
The man page for xorg.conf is called 'documentation'. It's a config file and thus the man page needs to be extensive. These days in most cases you can get away without an xorg.conf anyway.
Ubuntu (LTS or not) does not intentionally receive any update that `breaks' the system in the way you mention it. Have you actually *used* Ubuntu? I ask because if you had used it you would know that the Ubuntu repositories are most definitely not the Debian repositories, that you should not even attempt to mix the two (barring some very specific apt.get wizardry), and that there is such a thing as a “Debian Import Freeze” and it is before the first alpha is released. You will, therefore, never get your updates directly from Debian Sid or testing if you run a release version of Ubuntu; and Ubuntu LTS means that you get updates on your software for a longer period. Also LTS releases are based on LTS kernels which typically means the kernel of (next) RHEL. In casu 10.04 ships with 2.6.32 for that reason.
I've used Ubuntu on and off since 6.06LTS right up to 9.04 where I gave up and moved on to better things. 6.06 was the one I stuck with for the longest. That was a decent distro back in it's day. It's later on that it all went very pear shaped.
Yes I'm aware that the Ubuntu and Debian repos are not the same - but thanks for the info. :laugh4: I did not suggest mixing Ubuntu repos, that would be insane, I was talking strictly about Debian. You would not need "apt-get" wizardry" (or aptitude wizardry even) to mix repositories in Debian by the way. Mostly it depends on how you set up your sources.list. Though there are more elaborate ways to go about it yes.
The latest 'stable' kernel is 2.6.33-3 according to kernel.org. Sid and Squeeze uses a stock 2.6.32, but there is a 2.6.33-1 currently in the experimental repo which has some advantanges where the xorg radeon driver, DRI and KMS are concerned - among others. 'buntu 10.04 LTS also uses a build of 2.6.32. So kernel wise they're the same.
I think the main problem here is the myth "debian is difficult" or "debian is out of date" or "debian does not play well with proprietary software". You need to actually try it out properly before coming to those conclusions. If then you still think "tried Debian preferred Ubuntu", that's up to you of course.
:bow:
Tellos Athenaios
04-28-2010, 23:01
The reason Kubuntu is more 'up to date', is because it's not stable, thoroughly tested software and Ubuntu are known for pushing through untested software before it's ready (believe me I know). Yes you're getting something 'newer', but you're also getting something that's far more likely to break - and break it does.
KDE 4.4 should be in Sid soon - it wasn't last time I checked (still 4.3.5 I think?). Last I heard they were holding off due to the problems most other distros were having with it. Most of those problems have been ironed out now. It gets released "when it's ready".
IIRC the reason why KDE 4.4 is not in Sid yet is probably because of the fact that Debian has far more architectures for which a package must build correctly in order to be included; and at least one of those builds didn't make it to the finish line. And yes there *were* some annoying bugs in KDE 4.4 but those have been resolved. The other issues were in fact the Qt 4.6 threading bugs (segfaults). That too, is resolved, the version you'd need is 4.6.2 I think. Or at least it is resolved in Kubuntu 10.04 updated on 28 April 2010. ~;)
And no, having had KDE 4.4 I'd rather not go back to KDE 4.3.4. I guess I am just not patient to wait for 4.4. in Debian; knowing that by that time I can get a decent working 4.5 on Ubuntu. I run a simple AMD64 architecture; I couldn't care less about failing-to-build-on- alpha|mips|itanium|other-processor-I-do-not-own. :shrug:
Debian Stable is used extensively for servers, including webservers of course where security patching and stability is a must. If you've ever tried Stable, you'll know that as a desktop it's also rock solid and dependable. As I've touched on before, backports are the best thing about Lenny. You can get most of the latest packages from Sid and Squeeze and put together a decent desktop with most if not all of the packages that you want. Mrs Asai's PC runs Lenny with backports and is nothing but dependable. I'm toying with the idea of upgrading it to squeeze though.
I have. Debian Etch (stable) was my very first Linux desktop. I thought it best to play it safe and get myself something ... “stable”. Stuff should work when it's stable, right? ~:) I found out quite quickly that just about every bit of useful documentation/guides I really needed to make things actually work (wireless, codecs, dvd menu systems) involved the ubuntu forums, particularly the posts made by more seasoned contributors. ... It was one of those things.
Oh yes, I knew of (and from time to time still use) the Debian wiki. It is useful for very specific driver related stuff. (Here is firmware blob x_y_z it works with kernel A_B-15 thru A_B-27, but for later kernels you need firmware u_v_w instead) It is much less useful for “I am new to this, help me with a guide” type of problems.
I've never had an "unrecoverable installation" from either fglrx and certainly not ndiswrapper either. If fglrx causes hard lock up, it's usually because you installed an fglrx module that wasn't built for your specific kernel. This is actually the circus that has happened a few times with Ubuntu at dist-upgrade time. In fact with any proprietary closed source drivers it's pretty much unavoidable.
Certainly it is. The entirely closed drivers are the very worst. But Debian does nothing to aid you with such drivers at all. This is a good thing from the “freedom” side of things: it provides an incentive to use & improve open source drivers. This is fine. But the bad side is that open source drivers do *not* always have feature parity with the closed ones. You still don't get proper power management with your ATI card if you do not use fglrx, for one thing. 3D acceleration is another such issue. For someone new to the entire circus, unaware of many of these issues I think the better offering is to accept closed source drivers if freely redistributable.
But it is not just those drivers themselves; it is also firmware. For instance to make your wirelss card work chances are you *will* need to install proprietary firmware. Where do you get this firmware, you ask? Well from the internet. It is certainly not part of a default installation. Which means that by default you end up with... incomplete drivers. That is a less than an ideal situation.
I found out more about that when I decided to quit Ubuntu for a while after a harddisk failure (aging, cheap laptop quality thing) and tried Debian Squeeze: you can't run the iwlwifi/iwlagn driver by default because... firmware is missing. When I tried to set up Squeeze on my grandma's laptop after similar failure I found out the same holds true for the p54pci/p54usb drivers (prism54): you need to download firmware in order to get it working. On Ubuntu: you don't. It's all part of the stock Linux kernel distribution (linux-firmware) but Debian takes it out because it isn't FOSS software. It is a purely “political” choice. At that time I certainly considered it the worse choice, too at least from the technical P.O.V..
So to me that statement that “if you want an easy time on Debian, renounce & lose your proprietary ways” is still very much valid. It is *not* trivial to find out about the right wiki page; it is *not* trivial to find out exactly what driver you need. The first depends on the latter; and the latter depends on quite a bit of knowledge about your hardware: such as the original manufacturer of the controller chips... With cheap commodity hardware that is not at all obvious.
The man page for xorg.conf is called 'documentation'. It's a config file and thus the man page needs to be extensive. These days in most cases you can get away without an xorg.conf anyway.
I've used Ubuntu on and off since 6.06LTS right up to 9.04 where I gave up and moved on to better things. 6.06 was the one I stuck with for the longest. That was a decent distro back in it's day. It's later on that it all went very pear shaped.
Yes I'm aware that the Ubuntu and Debian repos are not the same - but thanks for the info. :laugh4: I did not suggest mixing Ubuntu repos, that would be insane, I was talking strictly about Debian. You would not need "apt-get" wizardry" (or aptitude wizardry even) to mix repositories in Debian by the way. Mostly it depends on how you set up your sources.list. Though there are more elaborate ways to go about it yes.
In order for you to use a specific distribution version of a package you must either pin or set the preference 'scores' of that package; as well as enabling any additional repositories required. Otherwise you would simply end up with a newer version of *everything*. The usual reason for doing this kind of thing is to run a modern system; *except* for a specific subset of functions. For instance running PHP 5.1 on Ubuntu 10.04.
Now I sincerely do not understand where your updates to wreck the LTS come from, anymore? I've been using 8.04 until 9.04 and never had any upgrade wreck anything. I've used 9.04, quickly upgrade to 9.10 to 10.04 because of the X + ati driver issues. Currently looking forward to getting proper power management in the driver with 10.10, plus KDE 4.5.
The latest 'stable' kernel is 2.6.33-3 according to kernel.org. Sid and Squeeze uses a stock 2.6.32, but there is a 2.6.33-1 currently in the experimental repo which has some advantanges where the xorg radeon driver, DRI and KMS are concerned. 'buntu 10.04 LTS also uses a build of 2.6.32. So kernel wise they're the same.
I think the main problem here is the myth "debian is difficult" or "debian is out of date" or "debian does not play well with proprietary software". You need to actually try it out properly before coming to those conclusions. If then you still think "tried Debian preferred Ubuntu", that's up to you of course.
:bow:
I am not saying Debian is difficult. Quite specifically it isn't any more difficult than Ubuntu is. But in order to run the same software you'd run in an Ubuntu release you have to do a lot more hand holding than you would have to do on Ubuntu. So it is a matter of time & effort more than arcane skills.
I'm not a KDE user so I won't get into the whole KDE debate. I don't think the issue has anything to do with arch. though as some packages are relesed for a certain arch. and not available in others. I don't see it as an issue if a package is not released as soon as possible. Different distros have different ways of doing things.
I have. Debian Etch (stable) was my very first Linux desktop. I thought it best to play it safe and get myself something ... “stable”. Stuff should work when it's stable, right? ~:) I found out quite quickly that just about every bit of useful documentation/guides I really needed to make things actually work (wireless, codecs, dvd menu systems) involved the ubuntu forums, particularly the posts made by more seasoned contributors. ... It was one of those things.
No it does not involve the Ubuntuforums. You're actually looking in the wrong places. Sadly, anything you google for related to Linux in general these days will lead you to a mostly useless thread at Ubuntuforums. That does not mean that UF has all the answers - it clearly does not.
But Debian does nothing to aid you with such drivers at all. This is a good thing from the “freedom” side of things: it provides an incentive to use & improve open source drivers. This is fine. But the bad side is that open source drivers do *not* always have feature parity with the closed ones. You still don't get proper power management with your ATI card if you do not use fglrx, for one thing. 3D acceleration is another such issue. For someone new to the entire circus, unaware of many of these issues I think the better offering is to accept closed source drivers if freely redistributable.
Yes and no, the latest fglrx for the latest X server is available in the squeeze repos (and in the Ubuntu ones). The installation is very simple (via module assistant). I don't see the problem?
As to fglrx - unless you're gaming you don't need it. the foss driver is superior to fglrx in every respect expect for full screen OpenGL apps (games). If you just want 3D for compiz-fusion then the foss radeon driver is your best option - and it supports KMS, which fglrx does not. 2D acceleration on fglrx is also crap. Nvidia is another matter, they are the problem, but the Nouveau should be a solution to this. (or you can use the proprietary drivers which work well).
But it is not just those drivers themselves; it is also firmware. For instance to make your wirelss card work chances are you *will* need to install proprietary firmware. Where do you get this firmware, you ask? Well from the internet. It is certainly not part of a default installation. Which means that by default you end up with... incomplete drivers. That is a less than an ideal situation.
Sorry, but that's actually wrong as well. Proprietary Firmware was removed from the Linux kernel, not from Debian. To install it in Debian it's a simple matter of adding the non-free and contrib repos to your sources, then update package listings, and fetch the firmware-nonfree package and that's it.
I found out more about that when I decided to quit Ubuntu for a while after a harddisk failure (aging, cheap laptop quality thing) and tried Debian Squeeze: you can't run the iwlwifi/iwlagn driver by default because... firmware is missing. When I tried to set up Squeeze on my grandma's laptop after similar failure I found out the same holds true for the p54pci/p54usb drivers (prism54): you need to download firmware in order to get it working. On Ubuntu: you don't. It's all part of the stock Linux kernel distribution (linux-firmware) but Debian takes it out because it isn't FOSS software. It is a purely “political” choice. At that time I certainly considered it the worse choice, too at least from the technical P.O.V..
No, the nonfree firmware for most wireless chipsets is also available in the repos. It's a 10 second job to install it. Again - what's the problem?
Heh, it's not "political". You seem to be labouring under the misapprehension that Debian is a gNewSense type distro? It's not. It's actually more "legal" than political.
So to me that statement that “if you want an easy time on Debian, renounce & lose your proprietary ways” is still very much valid. It is *not* trivial to find out about the right wiki page; it is *not* trivial to find out exactly what driver you need. The first depends on the latter; and the latter depends on quite a bit of knowledge about your hardware: such as the original manufacturer of the controller chips... With cheap commodity hardware that is not at all obvious.
I don't mean to be harsh but, you can keep quoting that but it's not going to get any truer. It's actually as easy as hell to install proprietary packages in Debian (in fact Debian have been criticised for it by the Stallman brigade) - but I don't actually understand your point. It's also relatively easy to identify most hardware using lspci or lsusb. Personally I only have one troublesome piece of hardware in my entire system, and I had trouble with that regardless of distribution anyway. That being an rtl8185 based wireless adaptor. It actually works using the in built driver but not with WPA2. I got around his by simply setting it up with Ndiswrapper.
In order for you to use a specific distribution version of a package you must either pin or set the preference 'scores' of that package; as well as enabling any additional repositories required. Otherwise you would simply end up with a newer version of *everything*. The usual reason for doing this kind of thing is to run a modern system; *except* for a specific subset of functions. For instance running PHP 5.1 on Ubuntu 10.04.
I know... as I had stated in the previous post.
Now I sincerely do not understand where your updates to wreck the LTS come from, anymore? I've been using 8.04 until 9.04 and never had any upgrade wreck anything. I've used 9.04, quickly upgrade to 9.10 to 10.04 because of the X + ati driver issues. Currently looking forward to getting proper power management in the driver with 10.10, plus KDE 4.5.
9.04 was not an LTS. I wasn't talking about updates breaking the LTS in particular, I was referring mainly to dist-upgrades which are actually offered to all Ubuntu users on a plate via UpdateManager. This is usually when mayhem hits. Expect to read the usual "complaints" at UF when 10.04 is released to the masses. Though admittedly they'll probably get away without broken X servers this time around due to 10.04 being Squeeze based. The 8.10 to 9.04 upgrade was a disaster. I actually fell foul of that one myself because I was messing about with an Ubuntu 8.10 box at the time and decided to dist-upgrade. Now I'm not saying dist-upgrade works in Debian, in my experience it doesn't - not without a lot of hassle anyway, but in Debian you don't get "offered" it in updatemanager. Anyway the long and short of it is, that I had fglrx installed and when I rebooted - hard lock up. (i.e. "magic" key sequences were required to sync, unmount and reboot). That fact is, that myself and some other moderately experienced users will know the pitfalls, but the " 'buntu n00b" that installs fglrx from "restricted drivers" (or "hardware drivers" as I think it's called these days) will not know this.
I am not saying Debian is difficult. Quite specifically it isn't any more difficult than Ubuntu is. But in order to run the same software you'd run in an Ubuntu release you have to do a lot more hand holding than you would have to do on Ubuntu. So it is a matter of time & effort more than arcane skills.
No idea what you mean by "hand holding". I'm just not entirely sure you've run Debian for an extended period of time - certainly not enough time to get into it and appreciate it fully. I'm making no claims that Debian is user friendly - but neither is Ubuntu. To me Ubuntu is someone elses Debian set up, whereas Debian is the blank canvas. It runs everything I want and only what I want and is less bloated than Ubuntu. It's also not simply a matter of "time and effort", Debian (especially Squeeze or Sid) does require that you have a clue about what you're doing - Ubuntu is really a "beginners distro" and that's not a bad thing. Really it's all apples and oranges.
I will now respectfully bow out of this thread as I feel we're moving in circles. Sometimes it's best to "agree to disagree".
:bow:
And this whole discussion is supposed to make it easier for someone new to Linux to decide on a distro? :inquisitive:
I'll stick with Ubuntu for now anyway but it's no wonder that people avoid this version jungle and just go with the newest Windows instead. ~;)
Well it looks like even the Ubuntuforums Admin is not impressed with the latest "offering": http://ubuntuforums.org/showthread.php?t=1470633
I have been with Ubuntu since day one and this is the first time I have been annoyed to the point of posting a thread like this and it saddens me a lot.
I believe that 10.4 should not have been released. It is not ready , not by a long shot. The version they have released is worse than the Beta.
It's simply canonical being canonical: Releasing software before it's ready. Software that Debian and other distros would not put in a mainstream release until it's been properly tested. This is where the commercially oriented Ubuntu development/release cycle falls down.
That's interesting, at first I noticed that the new version fixed a few problems and added some good options, but a few minutes ago I had to restart it after booting because it was a bit messed up, icons showing up twice with one non-functional etc. Otherwise it seems to run fine so far now, but then I'm not a professional superduperuser... :shrug:
It's what's known as the "Ubuntu: It works for me" fallacy. It's shocking to see the actual board admin fall victim to it, but there you go. The whole idea of "it works for me" is entirely flawed. Let's be honest, none of us keep the same PC forever and none of us use our computer for the same things. So one man's "stable" is another mans:
I believe that 10.4 should not have been released. It is not ready , not by a long shot. The version they have released is worse than the Beta.
Now this chap is a superduperuser, the UF board admin and a long term Ubuntu fanboy, so you really have to ask yourself "what went wrong?" - when he seems to have only just realised this. Yet sadly it does feel as though he gets his just deserts in those responses ("it works for me" etc - "Oh dear lord... my creations are behaving in exactly the way in which I had programmed them... back fiends! STOP I say!... **frantically presses all the buttons on the remote** ). The attitude that the UF staff has fostered comes back to slap him in the face.
IMHO it's utterly naive and unhelpful for an experienced user to adopt the "it works for me" approach when other users are having serious trouble - more disturbing yet is that this is the attitude that has been fostered over at UF in the last few years. There has been no policy put in place against it, like there has against "sudo passwd root" or "gksu nautilus &" (or criticising the staff).
I'm off to feed the camels.
:book:
Well, but it does work for me so far, if it stops working for me I will look for alternatives but until then or until i get a new PC I don't see why I should go through the hassle of setting up another OS today just because other persons have trouble with it? Maybe tomorrow... :shrug:
I decided to give RTW another go with Wine 1.1.42. The result is a lot better than the last time I tried it under an earlier version of wine.
The game is actually very playable and stable.
No issues at all with the campaign map. Bump scrolling doesn't work properly (even with the option to prevent the mouse pointer leaving the window enabled), I got around this, in a fashion, by stretching the virtual desktop slightly. - though I use the cursor keys to move around anyway. All that's needed is a virtual desktop setup through winecfg and ensure that both battles and campaign are set to this same resolution in 32 bit colour. (I found that 16 bit crashes the battles)
https://img413.imageshack.us/img413/1204/screenshotm.th.jpg (https://img413.imageshack.us/i/screenshotm.jpg/)
Battles are ok apart from a few minor glitches. This one was with the higher quality shadows enabled, which don't seem to render properly. Disabling these fixed it.
https://img146.imageshack.us/img146/8321/screenshot1wd.th.jpg (https://img146.imageshack.us/i/screenshot1wd.jpg/)
All in all the battles are fine, though a little bit chuggy when lots of units are on screen and grass needed to be turned off as it caused artifacts. Also the terrain disappears at the start of a battle. Rotating the viewport 360 degrees seems to fix this. Apart from that it's a vast improvement though - and as I said, it's actually playable now.
https://img406.imageshack.us/img406/1902/screenshot2vt.th.jpg (https://img406.imageshack.us/i/screenshot2vt.jpg/)
I haven't tried M2TW yet.
:bow:
Tellos Athenaios
05-06-2010, 00:24
That's very nice indeed. What kind of hardware + drivers is that on? The only thing I can see is that apparently your CPU is pretty much maxed out at 2.7GHz.
It's on a fairly humble Athlon 64 X2 (2.7GHz) with 2GB of RAM a Radeon HD 3650 and the latest fglrx. CPU always scales up to maximum clock speed when you launch a game.
:bow:
Tellos Athenaios
05-06-2010, 11:11
Hmm. That might mean I could play EB on my desktop & new laptop (2.13Ghz Core i3, but more RAM and probably slightly faster graphics from the 4570) too ... :juggle:
Hmm. That might mean I could play EB on my desktop & new laptop (2.13Ghz Core i3, but more RAM and probably slightly faster graphics from the 4570) too ... :juggle:
Yes, I think you should give it a go.
:bow:
Ok, yesterday my notebook overheated I think(well, it just turned itself off) and today Ubuntu won't boot anymore, it just shows the boot screen but doesn't go any further, my USB stick with an old Ubuntu version somehow drops me in a Bash console on both computers instead of starting as it used to. Is there any way I can repair it or would you advise me to reinstall everything (again....)?
Might try a different distro in the latter case, but one that doesn't require me to use the console to get the basics working and install programs might be useful(unless the commands are simple.
Oh yeah, not going to that Linux "course" because it would take too much time, unfortunately, I have more important subjects that have to be a priority now.
Ok, yesterday my notebook overheated I think(well, it just turned itself off) and today Ubuntu won't boot anymore, it just shows the boot screen but doesn't go any further, my USB stick with an old Ubuntu version somehow drops me in a Bash console on both computers instead of starting as it used to. Is there any way I can repair it or would you advise me to reinstall everything (again....)?
I'm not sure I follow you... You also have a previous version on bootable removable media and that won't load X either? Have you tried booting a live session from the livecd? If that doesn't load up X then you may have some hardware problems. If it's not a hardware issue and you can get to a terminal then it can be fixed. I'm not really willing to go into great detail because:
Might try a different distro in the latter case, but one that doesn't require me to use the console to get the basics working and install programs might be useful(unless the commands are simple.
That's up to you, but you won't get anywhere fast if you are unwilling to use the terminal from the start.
Assuming it's not hardware, you should be able to find help on this at ubuntuforums.org
Yes, I have Ubuntu 9.04 or so, the last before 9.10, on a USB stick and that only gets me to a terminal when I use it as a live "CD", but it does the same on my Windows computer which is still working otherwise so I suspect something is wrong with the Ubuntu on that stick.
I'm willing to use the terminal but it never got me anywhere fast so far because it usually takes me hours of searching the internet to find the right commands to do something, if I find them at all, if not it's just one more thing I can't get to work but spent an hour trying. :shrug:
If I wanted to fix the installation using the terminal that my live "CD" always gets me to I guess that would be a nightmare, starting with figuring out why exactly it's not booting in the first place(although, maybe there is a way to tell, Linux used to show this list of things it did on startup after all). I was just thinking maybe there is a self-check or something that repairs possibly corrupted files or entries.
Can you boot from an actual livecd of karmic or whatever version you intend to use?
Re: the OS installed on your hard disk, what happens exactly when it tries to boot? Do you see any error messages? If it hangs on the bootsplash (I think Ubuntu uses usplash or similar be default since karmic), can you CTRL+ALT+F1 to a tty? If you cannot then the "recovery mode" from the grub boot loader will be your next step. This should (if my memory serves me correctly) drop you to a root terminal (great security!) from which you can check logs and run fsck etc.
Yes, it hangs on that splash screen, fills five dots with red colour, then hangs.
The key combo does absolutely nothing, do I get to the bootloader via a live CD or an earlier key combo?
And by the way, when i press the power button it does the normal shutdown splash screen which seems to work just fine, but the power button is apparently the only button it shows a reaction to.
When booting up keep hitting escape, this should show the kernels list (of the grub2 boot menu). Select the topmost kernel and hit 'e', edit the line ending with "ro quiet splash" to just remove "quiet" and "splash", then CTRL+X to boot that kernel. This will give you more detailed output, have a look and see where it's hanging. i.e. write down any errors. The grub2 boot menu will also get you into the recovery mode as I think it's called. That should boot you into a tty. See if either of those work first.
Tellos Athenaios
05-11-2010, 21:18
In addition to what Asai wrote:
(1) You may need to use Shift instead of Esc for bringing up the Grub 2 menu.
(2) The problem is likely to be a file system marked as `unclean' due to the abrupt shut down of the machine when it overheated. If that is the problem you can likely fix it with a file system check. The recovery boot option should offer that choice halfway through the booting process.
(3) If you are unable to use/select the recovery boot option because you can't get the Grub 2 menu to show and you boot to a (busybox) prompt you can do that manually (after logging on) using something like this:
umount -a -f # force all mounted file systems to unmount
nodes=`find /dev -iregex '/dev/sd[a-z][0-9]'`; # enumerate all disk partitions
for $node in $nodes; do fsck -y -p -f $node; done; # force fsck on the partitions found, repair damage without asking and assume yes if prompted anyway
fsck and umount require root privileges, so depending on how you are logged on (as root or ordinary user) you may need to run these via sudo. (E.g.: "sudo fsck"). Before you copy these commands blindly, do please read the man page synopsis and section on options of umount and fsck. (Type: "man umount" or "man fsck" to bring up these pages.)
EDIT: Note that option (3) uses a bit of a "blanket" approach to ensure that the file systems found are checked. In particular, an external (e.g. USB) harddisk will be found & checked as well, so be sure to disconnect these devices before booting & attempting this (saves you a lot of time if the external disk is anything large-ish; and if it is an USB flash drive it is ill-advisable to run fsck on it often).
Good post.
Yes I wasn't sure about the key for bringing up the grub2 menu. I've never used the hidden menu (or boot splash or quiet boot) myself so couldn't remember (I had a vague idea it was escape though).
I think fsck should run after an unclean shutdown anyway? As Ubuntu uses usplash (or whatever splash it uses), is it at all possible that fsck is running anyway in the background - which is why it appears to hang? (hard disk activity would be a big give away though).
:bow:
Tellos Athenaios
05-11-2010, 22:56
Cheers. And fsck certainly *should* run, yes. It is quite possible that everything is working as advertised, fsck is doing its system-wholeness-rite but our Hussar is simply too impatient for the progress messages to appear and smothers it with a power button. :shrug:
However in case that it does not and the system mounts everything read-only (i.e. pretty much unusable except for busybox shells) manually prodding it like that is usually a simple enough fix. I've had to do that on a few occasions with Debian installation on grandma's laptop (I don't know what she gets up to with that thing, but the number of counts she managed to trip up something ... !)
Thanks guys, if it is running something in the background, maybe it would help to indicate that somehow, I let it sit like that for a few minutes but my impression was that it did nothing, no indication of harddrive usage either.
Esc was indeed the key to get into the bootloader, the only problem was after pressing "e" to edit the start command for the first kernel I got 4 lines I could edit, I took the last one thinking maybe it's one command over 4 lines, put the options behind it and then booted using "b" as the help at the bottom said (Ctrl + X didn't work), it booted just normal(as in didn't boot and hung at the splash screen) so I guess I made a mistake somewhere. ~D
Will try the fsck method tomorrow.
I pretty much doubt it's a hardware failure, the notebook doesn't overheat often but when it does, it could so far always be restarted somehow(usually after taking the battery out for a minute or two).
Tellos Athenaios
05-11-2010, 23:56
Well it seems you did do something wrong: Asai mentions the removal of options not adding them. (To be removed: "quiet" and "splash"). The Ctrl+X key combination boots the edited stanza whereas b boots the original one IIRC.
Well it seems you did do something wrong: Asai mentions the removal of options not adding them. (To be removed: "quiet" and "splash"). The Ctrl+X key combination boots the edited stanza whereas b boots the original one IIRC.
Yes, I got that, but I thought "ro quiet splash" was the phrase I should add in order to remove the two options. Ctrl + X, as I said, did absolutely nothing though :shrug:
I'd imagine CTRL+X wouldn't work if the syntax was wrong. Try again and use the right arrow key to move to the end of the line* and remove the "quiet splash" bit. Then CTRL+X to boot it. This will give a verbose startup. Take note of where it hangs and especially any errrors.
*If you use up down arrows it will jump from line to line - one line often wraps over two lines, so to to get to the second part of a line you need to use the right arrow key to move to the end (not the up/down arrow keys).
I managed it, I basically had to edit the second line of the first kernel, removed the "ro quiet splash", then had to press "b" to boot (Ctrl + X still didn't work, maybe they changed that).
Now the error it stops with reads as follows:
"fsck from util-linux-ng 2.17.2
udevd[248]: can not read '/etc/udev/rules.d/45-huawei1550.rules'
/dev/sda1 has been mounted 33 times without being checked, check forced."
I think that rules file was created by me trying to get some huawei UMTS stick to work, since I didn't get it to ....
ok, now it completed the check and shows me the following error on startup:
(EE)Problem parsing the config file
(EE)Error parsing the config file
and something in german about running on low graphics settings, restarting the x-server didn't help so I'm now deleting the NVidia driver and trying to reinstall...
edit: Seems to run pretty normal now, should I check my HDD somehow, just in case?
And thanks a lot you two.
I guess it was running the test in the background as you said, but this way at least I learned something about how to disable the splash screen, get into the bootloader etc. :sweatdrop:
Ok a few points:
You needed to remove "quiet" and "splash" - not "ro" as well, but anyway.
If you don't need the rules file, delete it, also unplug/remove the device if you're not using it.
The errors are coming from xorg yes, probably due to some syntax errors in xorg.conf. Did you try some manual editing of that file before things went wrong?
fsck was running "under" the boot splash screen (this is why on the whole I dislike boot splash screens). You shouldn't need to run it again.
The splash screen and quiet boot can both be disabled permanently if desired.
Glad to hear you got it working, but how did you install the Nvidia driver - from the repos or did you download it from Nvidia?
:bow:
Edit: Next time you get any problems with freeze ups (to be clear: what you encountered was not a freeze up though), don't just hit the power button, instead do:
ALT+SysRq+s
ALT+SysRq+u
ALT+SysRq+b
This will tell the kernel to sync all mounted filesystems, unmount them and remount them read only and then reboot the system.
Thanks, thought so about the ro but apparently it didn't hurt to delete it. :sweatdrop:
I didn't do anything to the xorg config except when I plugged and unplugged my other monitor to the notebook for dual-screen usage but that was all in the x-server settings menu of the nvidia driver.
I "reinstalled" the NVidia driver by telling Ubuntu to remove it and then to Activate it again using the Hardware drivers menu, probably not the best way to do it but seems to have fixed the wrong config file.
And what exactly is SysRq? The linux name for the windows-key?
ro = read only, as it's a one off it should be ok.
Reinstalling like that should work ok. It's basically a front end for fetching the driver via apt and installing/configuring.
SysRq is the "printscreen" key. "Windows" key is known as "super".
I just tried KDE, there was some installer in the software center that made it possible to select KDE in the login screen.
KDE was pretty nice actually, fiddled around a bit, found some wird things, like you can duplicate your desktop or your desktop is just some application or whatever, then I tried getting rid of that little symbol in the lower right corner but turns out deleting it deletes the entire bar at the bottom and it seemed impossible to create a new one in the lower right corner (all new ones appear in the other three corners and seem immovable). So now my KDE is completely ruined... :shrug:
Guess xfce is next...
edit: Forget that, looks boring, maybe I'll just make a clean install of Kubuntu when I have the time since it looked pretty nice...
I just tried KDE, there was some installer in the software center that made it possible to select KDE in the login screen.
Just so you know, you didn't need the "software center" to do that. I think the package is called "kubuntu-desktop" in the 'buntu distributions. In Debian you just install the KDE metapackage.
deleting it deletes the entire bar at the bottom and it seemed impossible to create a new one in the lower right corner (all new ones appear in the other three corners and seem immovable). So now my KDE is completely ruined... :shrug:
You need to try googling for help or going to the kubuntu or ubuntu forums. The best solution in your case is to rename the KDE userpace configuration directory, to force it's recreation (non-root terminal).
mv .kde .kdebak
Log out and log in again.
Tellos Athenaios
05-25-2010, 17:05
There's no need to Google for that. `Lock widgets' locks your current configuration against changes, and it will removed the cashews on panels and the like (you need to `unlock' them to get the cashews back). There will remain only a single cashew on your desktop which refers to something KDE calls the Zooming User Interface. Apparently there is a widget/plasmoid that visually removes this (google for i-hate-the-cashew).
Further there is no need to move/rename .kde (~/.kde) to .kdebak (~/.kdebak):
If you want to start from scratch with your desktop layout/configuration there is no need to (re)move all configuration settings form KDE.
Simply remove (rm) two files: ~/.kde/share/config/plasma-desktop* (removes: ~/.kde/share/config/plasma-desktoprc and ~/.kde/share/config/plasma-desktop-appletsrc). You can do this using Dolphin (the file manager), too: simply type Alt + F2 (now you no longer have a menu to click on, time to find out about the goodness that is krunner), type dolphin and select it from the list of options you will be presented. In the bar which represents your current location (it will read Home or the equivalent in your language of choice), click and type .kde. It should read something like /home/user/.kde now. (E.g.: /home/hussar/.kde) Hit enter to go there, and navigate to share/config. Manually delete the two files (plasma-desktoprc and plasma-desktop-appletsrc).
Log out and log back in.
To move a panel like you wanted to (from edge to edge) use the button called `Screen Edge' and drag the panel to the desired edge. It will snap to its new position. Resizing along the screen edge is done with the 3 little arrow markers (two that fix the extent of the panel, and one to anchor it.) Resizing perpendicular to the screen edge is done with the button next to `Screen Edge' (called `Screen Height' in case of horizontal panels) and dragging; similar to `Screen Edge').
Thanks, already renamed/moved the kde folder but restoring the settings wasn't too hard. I wanted to try locking the panels but went with the deletion first, bad idea I guess. ~D
I already noticed that some programs from gnome do not work at all or not as well with KDE, Rythmbox for example seems to have to be replaced by Amarok, but then that also crashed when I quit it without stopping the music first and there was no way for me to remove the icon from the system bar except to restart. And on the topic of restarting, how is that done in KDE without pressing the power button or is that just the default way to go about it? I noticed deep sleep turns the computer completely off but apparently saves the session on your HDD and then restores it, I haven't found a power off/shut down option in the exit menu?? Or am I perhaps supposed to log out and then shut down from the ubuntu login menu?
Tellos Athenaios
05-25-2010, 20:39
I already noticed that some programs from gnome do not work at all or not as well with KDE, Rythmbox for example seems to have to be replaced by Amarok, but then that also crashed when I quit it without stopping the music first and there was no way for me to remove the icon from the system bar except to restart. And on the topic of restarting, how is that done in KDE without pressing the power button or is that just the default way to go about it? I noticed deep sleep turns the computer completely off but apparently saves the session on your HDD and then restores it, I haven't found a power off/shut down option in the exit menu?? Or am I perhaps supposed to log out and then shut down from the ubuntu login menu?
The KDE menu (K icon) has a category called `Leave'. It offers Lock, Logout, Sleep, Hibernate, Shutdown, Restart. Any of those can be accessed trough krunner (Alt+F2) too: type reboot and it will find you the Restart option. I take it you didn't restore the menu to your new panel?
It is actually possible to use Rhythmbox in KDE. It's just that KDE offers its own media players which integrate (much) better with KDE as whole. For instance there is a little plugin to control Amarok using krunner (Alt+F2). As a result nobody is going to bother to set up a KDE installation so as to use Rhythmbox by default, hence it isn't installed by default: if you really want Rhythmbox you need to install that manually after installing KDE. The reverse holds true on Gnome as well.
The KDE menu (K icon) has a category called `Leave'. It offers Lock, Logout, Sleep, Hibernate, Shutdown, Restart. Any of those can be accessed trough krunner (Alt+F2) too: type reboot and it will find you the Restart option. I take it you didn't restore the menu to your new panel?
That's the thing, for me the menu only offers Logout, Lock, Change User, Sleep, Hibernate, and that's it, nothing else in there. :shrug: And I didn't restore anything.
edit: Get the button/option if I use krunner and type the german word for shut down ("herunterfahren"), but it's still not in the menu.
It is actually possible to use Rhythmbox in KDE. It's just that KDE offers its own media players which integrate (much) better with KDE as whole. For instance there is a little plugin to control Amarok using krunner (Alt+F2). As a result nobody is going to bother to set up a KDE installation so as to use Rhythmbox by default, hence it isn't installed by default: if you really want Rhythmbox you need to install that manually after installing KDE. The reverse holds true on Gnome as well.
Yes, I was aware of that(except for the plugin part), just wanted to know whether there could be any other problems, for example if I use Rythmbox to buy music from the Ubuntu music store (don't want to use iTunes anymore for that and that Ubuntu music store looks nice).
Tellos Athenaios
05-26-2010, 00:08
No the example you give should not pose any additional problems with KDE; just make sure that the packages rhythmbox (Rhythmbox application) and rhythmbox-ubuntuone-music-store (plugin to buy music from the Ubuntu music store) are both installed.
Thanks, I was a bit unsure since the whole Ubuntu One thing is used for the music store and seems only really integrated with Gnome, but you can access it via browser so I guess it's not a big problem.
The shut down thing still got me to a logout button that just logged me out and sent me to the user selection menu though. This is the weirdest thing together with the fact KDE always starts Kopete when it loads as if it were always restoring the last session, which I don't really want either. Kopete isn't in Autostart either.
Tellos Athenaios
05-26-2010, 16:18
It probably *is* restoring last sessions by default. To turn that off: go to System Settings -> Advanced tab -> Session Manager.
It probably *is* restoring last sessions by default. To turn that off: go to System Settings -> Advanced tab -> Session Manager.
Yeah, already found that but no solution for the shutdown problem, there are some settings to enable shutdown options, turn the power button into a shutdown button etc. etc. but none of it works, either nothing happens or I just get to log out and land at the login screen again. :shrug:
No problem if you don't have a solution, it's just really weird.
Tellos Athenaios
05-26-2010, 22:29
I've just Googled it and there seems to be a pattern: http://ubuntu-virginia.ubuntuforums.org/showthread.php?p=4197245 The fix seems to be to install KDM, and possibly purge GDM. Can be done with Software Center, I imagine; but if not then the good old aptitude will work:
# install KDM
sudo aptitude install -y kdm
# optionally uninstall and purge system configuration of GDM
sudo aptitude purge -y gdm
# optionally add GDM compatibility in case it messes up your GNOME
sudo aptitude install -y kdm-gdmcompat
As another way of shutting down; have you tried to right click on the desktop/walpaper, selecte Leave from the context menu? That should popup a dialog with 3 options: Logout, Restart and Shutdown.
At least, for me it does; but then again, for me the Leave menu in the Application Launcher (KDE Menu) also contains those options (whereas yours apparently does not).
I don't think plasma can shut down through GDM (at the moment anyway). Setting KDM as the desktop manager seems the best option.
Sure KDM isn't already installed? Maybe not, though if so:
sudo dpkg-reconfigure gdm
KDM was already installed so I did the reconfigure thing and it worked, thanks.
vBulletin® v3.7.1, Copyright ©2000-2025, Jelsoft Enterprises Ltd.