linux-8n67:/home/flavio/Documenti # kde4-config --version
Qt: 4.7.4
Piattaforma di sviluppo KDE: 4.7.2 (4.7.2) "release 5"
kde4-config: 1.0
linux-8n67:/home/flavio/Documenti # sudo /sbin/service dbus status
redirecting to systemctl
dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static)
Active: active (running) since Wed, 25 Jul 2012 06:04:31 +0200; 15h ago
Process: 1009 ExecStartPre=/bin/rm -f /var/run/dbus/pid (code=exited, status=0/SUCCESS)
Process: 937 ExecStartPre=/bin/dbus-uuidgen --ensure (code=exited, status=0/SUCCESS)
Main PID: 1058 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
├ 1058 /bin/dbus-daemon --system --address=systemd: --nof...
├ 1856 /usr/lib/polkit-1/polkitd --no-debug
├ 2085 /usr/lib/upower/upowerd
├ 2113 /usr/lib/udisks/udisks-daemon
├ 2121 udisks-daemon: not polling any devices
└ 2276 /usr/lib/rtkit/rtkit-daemon
linux-8n67:/home/flavio/Documenti # rpm -q dolphin
dolphin-4.7.2-4.4.1.x86_64
linux-8n67:/home/flavio/Documenti # rpm -q konsole
konsole-4.7.2-2.3.1.x86_64
linux-8n67:/home/flavio/Documenti # $(dbus-launch) dolphin
bash: DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-xZxvnVb45Y,guid=b0d8e8ae1d78cdc33a099f820000d499: File o directory non esistente
linux-8n67:/home/flavio/Documenti #
Am 25.07.2012 21:16, schrieb Flavioweb:
> linux-8n67:/home/flavio/Documenti # $(dbus-launch) dolphin
> bash: DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-xZxvnVb45Y,guid=b0d8e8ae1d78cdc33a099f820000d499: File o directory non esistente
Everything looks good except that of course.
To narrow the problem, create a new user for example “dummy” with yast
and then logout and login again as dummy.
Does everything in KDE work as expected as “dummy”?
–
PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
linux-8n67:/home/dummy/Documenti # kde4-config --version
Qt: 4.7.4
Piattaforma di sviluppo KDE: 4.7.2 (4.7.2) "release 5"
kde4-config: 1.0
linux-8n67:/home/dummy/Documenti # /sbin/service dbus status
redirecting to systemctl
dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static)
Active: active (running) since Thu, 26 Jul 2012 05:28:43 +0200; 4min 41s ago
Process: 917 ExecStartPre=/bin/rm -f /var/run/dbus/pid (code=exited, status=0/SUCCESS)
Process: 909 ExecStartPre=/bin/dbus-uuidgen --ensure (code=exited, status=0/SUCCESS)
Main PID: 935 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
├ 935 /bin/dbus-daemon --system --address=systemd: --nof...
├ 1838 /usr/lib/polkit-1/polkitd --no-debug
├ 2163 /usr/lib/upower/upowerd
├ 2191 /usr/lib/udisks/udisks-daemon
├ 2202 udisks-daemon: not polling any devices
└ 2348 /usr/lib/rtkit/rtkit-daemon
linux-8n67:/home/dummy/Documenti # rpm -q dolphin
dolphin-4.7.2-4.4.1.x86_64
linux-8n67:/home/dummy/Documenti # rpm -q konsole
konsole-4.7.2-2.3.1.x86_64
linux-8n67:/home/dummy/Documenti # $(dbus-launch) dolphin
bash: DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-yPtf4M1Fyf,guid=a17a491d2481bcee426ef5370000015f: File o directory non esistente
linux-8n67:/home/dummy/Documenti #
The “graphic login screen” don’t work. I can’t “log out” and select for new user: to switch user i need to set autologin and reboot.
If i logout, system goes to “terminal login” (as in init 3), but if i login here as “Dummy”, startx don’t work (as to be expected?).
So… also kdm isn’t work?
…following your steps:
linux-8n67:/home/dummy/Documenti # rpm -q kdm
kdm-4.7.2-6.4.1.i586
…mmmhhh… i586… may help?
…mmmhhh… i586… may help?
So are you supposed to _64?
I see some of the other packages you listed are
So if yes… Then you seem to have a right mess
So, what is the “rock solid” procedure to fix all?
by hands via yast2 or i need to use some shell commands?
What do you get from
su -
zypper ve
On 07/26/2012 09:06 AM, Flavioweb wrote:
> So, what is the “rock solid” procedure to fix all?
until you can fix these kinds of problems without assistance i’d suggest
(from #6 above)
really really need to follow the excellent advice in the paragraph
beginning with “IMPORTANT” in this posting http://tinyurl.com/33qc9vu
and, if the problem persists you may need to follow this advice (to
return to a stable system)
http://tinyurl.com/boqsodw
it has worked before to solve the actual problem (which is not KDE won’t
work, but rather) the installation of conflicting software)
ymmv, and therefore i encourage you to read the caveat below and listen
to other advice also.
Am 26.07.2012 09:06, schrieb Flavioweb:
>
> So, what is the “rock solid” procedure to fix all?
> by hands via yast2 or i need to use some shell commands?
>
>
If you have a separate root and a separate home partition I would do a
fresh install formatting / and leaving /home intact (if you go for that
make a backup of your /home before).
Unless caf4926 has a better idea.
Since you have not much to loose you can also try brute force a
zypper dist-upgrade
and hope for the very best (I have not much hope, since obviously the
previous “zypper verify” I gave you did not help and even the
dist-upgrade does not guarantee to switch all packages to the consistent
architecture).
For sure you could also fire up a few commands retrieving the names of
all your installed packages ending with i586 and i686 and automatically
invoke corresponding zypper commands to install the right x86_64
package, but nobody knows if that is all which is screwed.
To do a quick check retrieve the list
rpm -qa | grep 'i[56]86'
maybe you have luck and there are not that many so that you can change
them one by one with yast.
–
PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
the “rock solid” procedure to fix all?
I’m incline to agree with Martin and do a clean install.
You somehow hosed your install, probably when making a choice on dependency conflicts on a update
I found a solution:
started yast2 and searched for all “i586” packages, then changed architecture to “x86_64”.
It was necessary to re-install some packages from DVD but, at the end, all goes fine.
Deleted again /tmp and /var/tmp contents and…
now my system is full working again !
Thanks a lot for your support !!!
I’m please to hear that
even if it was a little tedious, you did well.
Glad to hear you solved it.
Keep an eye on the changes the system proposes when you do an update or
install new software if there are architecture changes involved so that
the problem does not come back.
–
PC: oS 12.1 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.8.4 | GeForce GT 420
ThinkPad E320: oS 12.1 x86_64 | i3@2.30GHz | 8GB | KDE 4.8.4 | HD 3000
eCAFE 800: oS 12.1 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10