I got openSuse installed alongside my Windows 7 installation.
the first user is “Joe” and linux opens up immediately with Joe as user–no questions asked by the system, such as “would you like to login as root or joe?”
Logging out of Joe and into that login window is cumbersome because Joe is unable to use the mouse except on the lower tool bar of KDE. Why?
The machine said that libusb was found but could not be used because of “Permissions”.
I understand permission : read, write, execute but where is libusb? Using the find command yields nothing. Do I chmod him into %377 from root? but where is this libusb?
That’s normal. By default, Auto-Login is enabled. You can disable that in YaST->Security and Users->User and Group Management->Expert Options (bottom right corner)->Login Settings, if you want to.
Logging out of Joe and into that login window is cumbersome because Joe is unable to use the mouse except on the lower tool bar of KDE. Why?
No idea. It doesn’t seem to be a problem with the mouse itself, as you can use it on the panel. Btw, could you elaborate that a bit, please?
Do you mean you cannot move the mouse to a different area? Or does the mouse pointer disappear if you do so? Or what else is the exact problem?
Maybe a graphics problem?
Try to disable compositing/desktop effects by pressing Shift+Alt+F12. Does this help?
And what openSUSE version are you using?
What graphics card/driver?
Please install the package “Mesa-demo-x” and post the output of:
glxinfo | grep render
Btw, you can reach the “start menu” via Alt+F1, you can open KRunner (a small dialog to start applications) via Alt+F2, and you can switch windows via Alt+TAB (just like in Windows).
The machine said that libusb was found but could not be used because of “Permissions”.
Where/when does the machine say that?
I understand permission : read, write, execute but where is libusb? Using the find command yields nothing. Do I chmod him into %377 from root? but where is this libusb?
In /usr/lib/ and /usr/lib64/.
But you shouldn’t change its permissions, and it wouldn’t help anyway.
Better post the exact error message to get further help.
But this is rather not related at all to your mouse problem IMO.
While the Graphical login screen asks you to enter a user (and it normaly appears after a boot when you do not have automaltic login switched on and after a logout), you should never use it for root. Read this please: https://en.opensuse.org/SDB%3ALogin_as_root
You know Henk, it’s hard for a beginner like me to categorize his current activities as “normal”, “root-normal”, “user normal” or “abnormal”
With all these acronyms and unclear terminology flying about in all directions, it is disheartening to read an article that warns me “Danger, don’t do normal things!!!”
Speaking in riddles does not realy help anybody IMHO. When you have difficulties to understand things, please quote them, explain where you hesitate about their meaning and as for more explanation. Only so can we help you and it could lead to better formulating the documentation.
This is a technical help forum. Not everybody is good in English. Both ask for being precise and exact.
Sure. The mouse moves and never disappears. The selfish mouse mode that I have means that I can move the mouse everywhere but only under very limited circumstances does a click do anything. I can start the app launcher with a click but within (!) the app launcher only keyboard arrows and tabs work to select a program. Then I must use return key to start it. I can start KWrite in 5 different windows, but each must be terminated with Alt+F4. Clicking on the X doesn’t work.
But here’s something. When I can call up the login window and login to Joe* from (!) *Joe then the selfish mouse mode is off and I can click again ***within ***app launcher.
Does that make sense? From Boot into KDE with user Joe something is missing.
Maybe a graphics problem?
Try to disable compositing/desktop effects by pressing Shift+Alt+F12. Does this help?
Sorry but Shift+Alt+F12 doesn’t have any effect.
And what openSUSE version are you using?
openSuse 13_2 i586
What graphics card/driver?
Graphics card as described in Windows is AMD760G, an onboard thing in the motherboard.
In the 10 or 20 times I’ve installed this before I never had problems with Joe and the mouse.
In /usr/lib/ and /usr/lib64/.
But you shouldn’t change its permissions, and it wouldn’t help anyway.
Sounds right to me.
Please install the package “Mesa-demo-x”
Today I’ve been installing updates. So now my disc space is drying up so that business about Mesa-demo-x will have to wait.
The whole screen was black when I left linux so I’ll see if I can do some partition stretching before contining with the selfish mouse mode.
Thanks for explaining further. So it’s basically mouse clicks that don’t work, right?
But here’s something. When I can call up the login window and login to Joe* from (!) *Joe then the selfish mouse mode is off and I can click again ***within ***app launcher.
Does that make sense? From Boot into KDE with user Joe something is missing.
You mean the problem exists only if you boot and get logged in automatically?
And everything works fine when you logout and login again?
Do I understand you correctly?
This rings a bell. Are you using autofs, i.e. do you have autofs.service activated?
This can cause logind to start too late and cause all sorts of permission related problems because your user session cannot be registered and you don’t get necessary privileges.
Today I’ve been installing updates. So now my disc space is drying up so that business about Mesa-demo-x will have to wait.
The whole screen was black when I left linux so I’ll see if I can do some partition stretching before contining with the selfish mouse mode.
Probably caused by btrfs snapshots.
Try to delete some in YaST->Snapper, or with snapper on the command line.
If you provided less then 40 gig for root you should turn off snapper or reinstall and use ext4 rather then BTRFS
Have you installed other Linux and using the same home partition?
Have you tried another user? This is truly an odd problem What method did you use to install?? Did you test the ISO’s checksums and if installed from DVD did you test the media?
This rings a bell. Are you using autofs, i.e. do you have autofs.service activated?
This can cause logind to start too late and cause all sorts of permission related problems because your user session cannot be registered and you don’t get necessary privileges.
Now I have to find how to deactivate this service. Sounds really interesting.
Probably caused by btrfs snapshots.
Try to delete some in YaST->Snapper, or with snapper on the command line.
For me Snapper is a fish. And yes root partition has BtrFS.
the root partition has 90 GB and /home has 100 GB.
I did do one kind of checkeroo on the DVD but it didn’t involve checksums. I burned the DVD myself from an ISO file I downloaded.
This installation of linux is alone.
On the menu on the DVD there is an option to test the media. this check to be sure that the check summons are good ie no error on download or on the DVD burn. A corrupted file in the iso may cause these problems.
autofs should not be used by default if you did nothing to change the default all should be ok in that regard. But does no harm to check
On the subject of turning off Snapper, whatever that is, and turning off autofs, whatever that is :
This problem comes into being during the starting process. How can I stick my fist into this booting and autologin process and say “hey you guys, no autofs and no snapping!”
Well with 90 gig to root you should not need to turn off snapper. BTW snapper is a process that takes periodic snap shots of the dirctory and allows you to roll back if needed.
Did you try booting into recovery mode?? at grub boot screen select advanced then recovery. This boots with more primitive settings that should always work and allows you to get too yast to fix/install things
There are ways to boot to a terminal mode also but it is more complex so try the recovery mode first
Graphics card as described in Windows is AMD760G, an onboard thing in the motherboard.
even build-in graphic cards need drivers, I think that’s amd ati radeon 3000 (or so google says) and it still needs drivers, I don’t have much experience with amd video chips but why not install the drivers from amd/ati.
goto yast -> repository management, click add repo, select comunity repo’s check the amd/ati repo, then goto software management and install the driver, yast usually preselects the driver (it does for nvidia) install it and reboot.
see if there is a difference.
about snapper, btrfs is a cool new file system that does automatic low-level backups, so on a partition with limited space you might have issues, I’ve never used btrfs for that reason still using ext4, by disabeling snapper you disable automatic backups (snapper is kind of like system restore on windows but better)
Right, but the (open source) drivers are included in the distribution.
And AMD’s proprietary driver doesn’t support a Radeon 3000. There’s a legacy driver that would support it, but that doesn’t work with any recent Xorg or Kernel any more (since years), so it’s useless to even try…
That said, it doesn’t seem to be a graphics driver problem anyway, if it works as root (in which case the same drivers are used obviously ) and it works after logging out and in again…
wow no ati drivers for pre 5000 cards, that sucks, there are working nvidia drivers for ancient gforce 2 chips (I know I ran 13.1 on a celeron with geforce 2) but back to the problem at hand, if the drivers are working it could be a kde setting he tweaked plus kde4 is way too heavy for such an old rig (gnome 3 is even more resource intensive), he should try a lighter DE like lxde or lxqt with openbox (kwin is too much for that pc).
Or he could install kde3 that should run smooth on old machines. (still think lxqt+openbox is the way to go)
Wolfi323, I looked into system services and autofs is disabled and inactive. There was no snapper in the list.
The link from one of you gents got me to the script for snapper and it makes no hourly snapshots.
I’ll check the installation DVD now for integrity and if that is okay then I’ll switch the root file system from BtrFS
to the other kind you suggested and go through another installation after some sleep.
just a note kde4 and gnome3 are resource intensive especially in regard to graphics, if you’re reinstalling go for a lighter desktop environment like LXDE or Xfce.
No, there aren’t.
At least not the proprietary driver(s).
Of course there are open source drivers (you probably used nouveau ), and the radeon one is ages better in any way, because AMD does support the open source driver development actively since years.
but back to the problem at hand, if the drivers are working it could be a kde setting he tweaked plus kde4 is way too heavy for such an old rig (gnome 3 is even more resource intensive)
I disagree there, it should work fine.
I am running KDE4, Plasma 5, and even GNOME3 (although I don’t really use that), on an even older card: a Radeon 9600.
And it works just great!
Anyway, even a KDE setting wouldn’t explain why it would work after logging out and back in…
he should try a lighter DE like lxde or lxqt with openbox (kwin is too much for that pc).
Or he could install kde3 that should run smooth on old machines. (still think lxqt+openbox is the way to go)
Would be an alternative, but KDE should work just fine, see above.
And it does for him anyway, when logged in as root.
) and it works after logging out and in again…