Hello there…
I have a problem with KDE…
I go to Main Menu > Leave > Shutdown OR Restart OR Log Off
I press
nothing happens…
This started a few days ago when I disabled some services…
Don’t know what service is associated… 
I tried using command line and everything works…
init 0
shutdown 0
shutdown -r 0
all work and bring down the system but my settings and open applications are not saved.
Any ideas?
Thanks Aris
some info…
opensuse 11.2
Linux linux-sgah 2.6.31.12-0.1-desktop #1 SMP PREEMPT
2010-01-27 08:20:11 +0100 x86_64 x86_64 x86_64 GNU/Linux
Module Size Used by
nfs 405152 0
lockd 95636 1 nfs
fscache 52048 1 nfs
nfs_acl 4072 1 nfs
auth_rpcgss 56928 1 nfs
sunrpc 267144 5 nfs,lockd,nfs_acl,auth_rpcgss
af_packet 28680 4
ip6t_LOG 7980 12
xt_pkttype 2248 7
xt_TCPMSS 5448 1
xt_tcpudp 4104 7
ipt_LOG 7660 12
xt_limit 4076 24
snd_pcm_oss 60032 0
snd_mixer_oss 22728 1 snd_pcm_oss
snd_seq 78560 0
snd_seq_device 10460 1 snd_seq
edd 13232 0
vboxnetadp 8448 0
vboxnetflt 19184 0
vboxdrv 1811500 2 vboxnetadp,vboxnetflt
cpufreq_conservative 10360 0
cpufreq_userspace 4364 0
cpufreq_powersave 2152 0
acpi_cpufreq 11544 0
ip6t_REJECT 6856 3
nf_conntrack_ipv6 26632 16
ip6table_raw 3720 1
xt_NOTRACK 2248 4
ipt_REJECT 4136 3
xt_state 2920 38
iptable_raw 3560 1
iptable_filter 4520 1
ip6table_mangle 5000 0
nf_conntrack_netbios_ns 3400 0
nf_conntrack_ipv4 14232 22
nf_conntrack 101952 5 nf_conntrack_ipv6,xt_NOTRACK,xt_state,nf_conntrack_netbios_ns,nf_conntrack_ipv4
nf_defrag_ipv4 2856 1 nf_conntrack_ipv4
ip_tables 24536 2 iptable_raw,iptable_filter
ip6table_filter 4552 1
ip6_tables 26072 4 ip6t_LOG,ip6table_raw,ip6table_mangle,ip6table_filter
x_tables 30768 12 ip6t_LOG,xt_pkttype,xt_TCPMSS,xt_tcpudp,ipt_LOG,xt_limit,ip6t_REJECT,xt_NOTRACK,ipt_REJECT,xt_state,ip_tables,ip6_tables
fuse 87984 1
loop 22292 0
dm_mod 101544 0
arc4 2568 2
ecb 4168 2
cryptomgr 109904 0
aead 10792 1 cryptomgr
pcompress 3560 1 cryptomgr
crypto_blkcipher 18028 2 ecb,cryptomgr
crypto_hash 17416 1 cryptomgr
crypto_algapi 25904 7 arc4,ecb,cryptomgr,aead,pcompress,crypto_blkcipher,crypto_hash
snd_hda_codec_atihdmi 5352 1
iwlagn 206760 0
snd_hda_codec_idt 73152 1
iwlcore 240172 1 iwlagn
mac80211 257120 2 iwlagn,iwlcore
uvcvideo 74196 0
videodev 46848 1 uvcvideo
sdhci_pci 11048 0
v4l1_compat 19020 2 uvcvideo,videodev
sdhci 27628 1 sdhci_pci
cfg80211 123296 3 iwlagn,iwlcore,mac80211
dell_laptop 5568 0
sr_mod 20964 0
iTCO_wdt 15056 0
snd_hda_intel 37184 6
ohci1394 38340 0
iTCO_vendor_support 4908 1 iTCO_wdt
snd_hda_codec 111112 3 snd_hda_codec_atihdmi,snd_hda_codec_idt,snd_hda_intel
sg 40128 0
ricoh_mmc 5288 0
ieee1394 121024 1 ohci1394
cdrom 48232 1 sr_mod
mmc_core 83616 1 sdhci
snd_hwdep 11216 1 snd_hda_codec
v4l2_compat_ioctl32 12776 1 videodev
joydev 14400 0
pcspkr 3720 0
dcdbas 13464 1 dell_laptop
i2c_i801 15656 0
video 29156 0
ac 6416 0
rfkill 28176 2 cfg80211,dell_laptop
battery 15824 0
wmi 9600 0
tg3 141100 0
fglrx 2324024 29
snd_pcm 117808 4 snd_pcm_oss,snd_hda_intel,snd_hda_codec
button 8360 0
snd_timer 32152 3 snd_seq,snd_pcm
snd 97608 20 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
snd_page_alloc 12600 2 snd_hda_intel,snd_pcm
intel_agp 37584 0
ext4 426008 1
jbd2 115712 1 ext4
crc16 2504 1 ext4
fan 6352 0
thermal 25160 0
processor 56932 3 acpi_cpufreq
thermal_sys 21888 4 video,fan,thermal,processor
come on people… .
anybody? at least tell me what to post …
system info?
services?
how?
please respond
arimaniac wrote:
> This started a few days ago when I disabled some services…
>
> Don’t know what service is associated…
enable all the services you disabled
test to see if you can then shut down KDE normally
a. if you can shut down normally
-disable the services you know you do not need one at a time
-until you disable the one that you didn’t know you need (and
normal shut down ceases)
-then enable the one you should have never turned off
-next time make SURE you know what you are doing before you do it,
and have a backup you can use to recover from a broken system
b. if after enabling the previously shutdown services you cannot shut
down normally you will then know the problem is not with disabled
services and you can seek other potential problems…since there are
many i would suggest you use the forums advanced search function to
seek them out…
one thing that might have happened is you knowingly or not installed
an update which broke you system…do you have more than the
recommended basic four repos enabled???
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
*
arimaniac wrote:
> come on people… .
come on arimaniac!
you don’t tell us the very basic minimum we might need to help you!
like, what operating system are you using? what version? what version
of KDE? what is the patch update status of your system (there was a
kernel update not so long ago that broke everyone’s (who installed it)
ability to shut down normally…
we can NOT see what you have there…so, how could we possibly help you…
see my sig for a big hint hint!!
here is another hint: before you start experimenting with shutting
down services do a good full system backup–then if you system is
damaged it is easy to restore to what was working…
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
I have the main non oss, main oss, update, and pacman.
Ok I ll try to do that with services…
Anyway to see the yast log of activities?
arimaniac wrote:
> I have the main non oss, main oss, update, and pacman.
this good!
> Ok I ll try to do that with services…
only way i know to proceed…
> Anyway to see the yast log of activities?
YaST is a GUI frontend for several different modules…i suppose you
want to try to track down what updates might have been
processed…for software management, the thing that does all the
‘work’ is named Zypper…and, what it has been doing lately is in
/var/log/zypper.log
if you have your logrotate set to compact and store logs occasionally
there may be some named zypper.log-[YYYYMMDD].bz2 where inside the
brackets is the date the archive was formed…
good luck
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio