The only thing I see that differs from usual install is that in the two situations it was an update from 12.2, changing the repos and making zypper dup.
Almost all worked nicely (one of the computer didn’t like nvidia proprietary, the other didn’t like nouveau, but as the other worked, no fuss).
But on the two, There no notification icon. The notification is here, I can clic on it, but it’s only shown as an empty grey square, exactly of the underground color like this: http://cjoint.com/13ma/CCDkxhMiKAI.htm
On 03/29/2013 10:16 AM, jdd wrote:
>
> changing the repos and making zypper dup.
i guess if you use YaST to create a new testUser, and then log out
and log into that new user the icon will be visible…which will
only point out that something in your old user’s /home is slightly
corrupt…how to find it and fix it is likely to be difficult…
in my experience, it is always quite difficult to correct those kinds
of little problems that so often come with upgrading using the method
you describe…
next time consider using one of the recommended/supported,
step-by-step how-tos, rather than simply change repos and dup:
i do not know where/how so many folks get the idea that “change repo
and dup” is all there is to it–rumor i guess…
of course, even the three recommended/supported ways can also fail to
be 100% smiles (which is why i never move to a new version in that
way–but, i know plenty do and are happy with it!)
I use SuSE nearly since the beginning, and openSUSE from the beginning, and this method was not possible initially, but it is like this that wagon works and it’s more and more usable.
I may say it’s the first time I do this on fully running systems (but I know of many people that do) and I plan to do this much more often. Only jumps like the one to systemd should makes it necessary to make a fresh install. I even will certainly update my server like this next time, I still have 11.4 and updating from 11.4 is pretty hard (and installing ubuntu LTS I can’t do :-().
On 03/29/2013 03:16 PM, jdd wrote:
> well… zypper dup is what your second link says.
correct, but “zypper dup” is neither the first, second nor last step
in the process…and skipping any step can later bring a frown
(like maybe a notification icon does not live through the process)…
but, as said even when every step is carefully followed, one might
still have to face:
“Depending on your customizations, some steps (or the entire upgrade
procedure) may fail…”
or
“…due to some third-party packages and the myriad of possible
configurations, it is possible for some combinations to cause failure
upon upgrade.”
or
“…it is to be considered a “best effort”: it should work, but it
can also fail.”
apparently you only had a very small failure–but, one that i have no
idea how to repair–other than maybe the new user will work and you
can use it, with your data…
then again, you might change to the new user and later find another
“little problem” somewhere else in the system which is caused by
leftover from the last version software or config…or maybe not.
Am 29.03.2013 15:42, schrieb Martin Helm:
> Your notification is set to visibility “automatic” just change it to
> always visible.
>
How to do it http://userbase.kde.org/Plasma/SystemTray/en
–
PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500
Martin: thanks, but it’s not the problem. As you can see in my image, there is no icon either in the naked view (and I tried your proposal before writing this :-).
Denver: you are right, something can always be wrong, but this is always true, even a security update can go wrong :-(. But openSUSE is getting better with each new version. I didn’t mind to update in place 5 years ago. I never had recently problem to boot init 3, the remaining problems are Xorg ones, but I can manage them in my desktop and have no X on my servers.
And, really, I tried to use ubuntu LTS, but from openSUSE, using any ubuntu server version id a nightmare :-))
I will have to reboot to trie some options, but can’t do this right now. I will report.
For me, the notification icon is usually hidden. If I click the little triangle to show hidden icons, it shows up.
When there is a notification, the icon still remains hidden, but a number (usually 1) shows up in the tray. It is the number of notices. If I click that number, I can see the notices.
I rather like this. I think it a lot better than the way notifications worked for prior versions.
I’m guessing that DenverD has it right. Your KDE settings are a kind of hybrid between the old and the new version.
My practice, on going to a new release, is to:
Login to a simple desktop, usually “icewm” or “twm” or “failsafe” (really twm);
rename “.kde4”. I typically create OLD as a directory, and “mv .kde4 OLD/.”
similarly rename startup files for other desktop stuff
logout, then login to KDE, and have a fresh set of settings.
move a few settings files from the OLD to the new (probably while back in “icewm”)
reconfigure the desktop to my liking.
That allows me to experience the new desktop as it was designed, and without it being a mess of old and new.
And a word of praise for the Mozilla folk. I have never had to do this reconfiguration with firefox. They do a great job of handling old firefox profiles and updating them to the new version.
if you look at the screenshot I gave, there is room for the icon, but no icon (or icon with the same color as background). Same when there are (upper left) notifications. In this case, I can clic on the empty space and display the notifications.
I will try bugzilla.
I already tried to completely remove .kde4, with no change on this issue.