just re-installed opensuse 11.0. it boots fine into shell, but entering startx to start x11 (kde 4) freezes as the progress bar
reaches halfway mark.
runs fine without kde, tho i haven’t thoroughly tested.
log files don’t exactly match:
root> tail /var/log/Xorg.0.log
(**) Mouse[1]: Sensitivity: 1
(II) evaluating device (Mouse[1])
(II) XINPUT: Adding extended input device “Mouse[1]” (type: MOUSE)
(II) evaluating device (Keyboard[0])
(II) XINPUT: Adding extended input device “Keyboard[0]” (type: KEYBOARD)
(II) Mouse[1]: ps2EnableDataReporting: succeeded
Could not init font path element /usr/share/fonts/TTF/, removing from list!
Could not init font path element /usr/share/fonts/OTF, removing from list!
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
and
root> tail /var/log/Xorg.0.log.old
() Mouse[1]: ZAxisMapping: buttons 4 and 5
() Mouse[1]: Buttons: 9
(**) Mouse[1]: Sensitivity: 1
(II) evaluating device (Mouse[1])
(II) XINPUT: Adding extended input device “Mouse[1]” (type: MOUSE)
(II) evaluating device (Keyboard[0])
(II) XINPUT: Adding extended input device “Keyboard[0]” (type: KEYBOARD)
(II) Mouse[1]: ps2EnableDataReporting: succeeded
Could not init font path element /usr/share/fonts/TTF/, removing from list!
Could not init font path element /usr/share/fonts/OTF, removing from list!
================================================
all else is still running - i run a watchdog script before startx that will eventually reset (sleep 500; reboot;)
running on amd abit va20 (if it matters
menu.lst line is
kernel /vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-label/suse11_root resume=/dev/sda9 splash=silent showopts vga=0x317
however, if i boot, then login as root, then startx, it comes up. maybe a permissions problem?
but then, even after i run kde as root, if i change something like window appearance or behavior, as soon as i click ‘apply’, it freezes. (this is actually the behavior that caused me to re-install)
still, the watchdog in the bkground runs and closes down gracefully.
does ctl-alt-bs shutdown the OS 11.0 X server? doesn’t for me, altho i’m using a kbd that maps DEL -> BS, so maybe i can’t get around that mapping.
i think there may be some confusion - booting up to init lvl 3 is what i have been doing all along. then i log in as the user i created during installation, su to root, background the watchdog script, log out of root, run startx as regular user 1. kde freezes mid-load.
running X as root was done only as an experiment.
per your request, i created a user user2. su to root, background the watchdog, log out as root, startx. for some reason, user2 can run X11. the behavior of X/kde is the same for user2 and root.
i’m confused - how is a user created during installation diff from a user created under yast? both belong to the same groups: dialup, video, users.
but even tho user2 can get X11/kde up, clicking ‘apply’ freezes the screen (the mouse and kbd, at least) - i’m not doing anything fancy with the video when i click ‘apply’. it can be anything from change the presentation scheme to remap the kbd to change the meaning of ‘ctl-left-arrow’.
oh, sorry -
in ‘control center’, if i change something like window appearance or behavior, or change a kbd mapping or mouse button actions, as soon as i click ‘apply’, it freezes (no response to mouse or kbd).
suse 10 (et al) works just fine.
as i mentioned earlier, i fire off a script (as root) that is nothing more than “sleep 500; reboot” to prevent having to power cycle the box after a freeze.
so the cycle goes like this: boot, log in as user2, su, background the script (watchdog&), exit back to user1, startx, bring up (for example) window behavior config, change (for example) focus follows mouse, click apply, freeze.
logging in as user1, same behavior except it locks up as the progress bar gets to the halfway point as kde is loading.
so, any idea why user1 can’t even get X/kde running but user2 can? and why user2’s desktop gets locked up applying changes?
Now when you login you get a green login screen.
At the login screen (lower left corner) you can select the login option there.
Once you have selected kde3 it will remain default unless you change it at the login screen.
didn’t get a chance to try it yesterday -had to go outta town.
today, i installed kde3 from dvd.
> At the login screen (lower left corner) you can select the login option there.
nope, nothing new in the lower left.
can i select which is the default somewhere else in yast?
still get lockup - tried to change mouse focus; chgd to follow mouse, delay 100ms, apply, freeze. altho i did use control panel/yast to config ntwk intf and wifi. that worked ok. who knows…
i think i’ll try to update kde4. id like to default to kde3 for testing a bit before that tho. can i change default wm somewhere else?
If you did install kde3-base and kde3-desktop and you don’t have a login option in the list at login (lower left)
Then you did something wrong.
Check in Yast - Software Management
Filter by patterns
Make sure both kde3-base and desktop are checked
yes, both checked. 29 of 29 base, 70-ish of 113 desktop.
still nothing new in the green screen.
one interesting note tho:
rpm -qa|grep -i kde3
opensuse-kde3user_en-11.0-7.1
i would think other pkgs would be installed.
1- is there a cmd line command to change which kde comes up?
2- is there a file somewhere which shows which pkgs yast installed (other than the rpm db)?
thanks for the continued indulgence.
edit:
i also notice that even tho the grub menu.lst line contains a param vga=0x317, and i get a complaint from grub about that now.
kernel /vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-label/suse11_root resume=/dev/sda9 splash=silent showopts vga=0x317
something kinda interesting tho - if i click down in the left corner kde seems to come up instantly as opposed to taking 15-20 seconds. may be just a timing (mine) fluke tho.
you are talking about the green screen with the progress icon in the center? the one that displays when i type startx ?
not sure what i could have done incorrectly (not impugning your suggestion) - all i did was click kde3 desktop and it sucked in kde3 base as a dependency.
is the rpm -qa|grep kde3 output reasonable?
edit:
one thing i noted when config’ing ntwk intfs, it wanted to install a couple pkgs, kpppmd and, uh, forget the other, but when i said ok, it went to suse.org to get 'em. then popped up an error saying,
<I>file /repodata/repomd.xml not found on http://download.opensusse.org/distribution/11.0/repo/oss
now it complains loading yast about that.
not related to the kde problem tho, i think.
edit:
make that 23/113 (regarding prev post about how many pkgs installed for desktop)
unless i don’t know what ‘auto login’ is, it’s never been enabled. i’m assuming you mean the ckbox as indicated in your tutorial (yast->users->options)
it’s always booted to console. i use <I>startx</I> to get X up and running. you use somethin’ else?
