I have a Vbox 5.0.6 VM running on 13.2/KDE host.
The host machine is from the openSUSE Virtualization Repo
The guest gets its Guest add-on functionality from the Leap RC1 repository.
I realize this could be Leap or VM, for now it feels like a VM config issue so I post here.
I have these repos installed on the guest from a DVD iso.
I have the LeapRC1 Oss and non-oss on-line repos available as well.
I don’t really understand why host packages insist on loading with some of the Guest packages, but I let YAST do it’s dependency thing for now.
On the host, VM Machine settings include Paravirtualization = None and Display with 2D and 3D Acceleration NOT checked.
My issue - application Dolphin will not open from the GUI (single click in the Desktop folder). The Bouncing icon goes for a bit then nothing.
If I open dolphin from a konsole I get
Leap141RC1VM:~> dolphin
pci id for fd 12: 80ee:beef, driver (null)
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
"Trying to convert empty KLocalizedString to QString."
And I get the Dolphin GUI interface which seems to have full functionality.
I am somewhat suspicious that the package virtualbox-guest-x11-5.0.6-2.2.x86_64 is not being properly set up, as I see
it provides
/usr/lib64/dri/vboxvideo_dri.so
and
/usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
Any suggestions on what to look for are appreciated.
You can ignore that message.
That just means that the vboxvideo driver doesn’t support 3D acceleration (or DRI in particular).
As dolphin runs fine from the shell, there shouldn’t be a setup problem regarding the video driver/guest additions.
Does the “bouncing icon” really show dolphin? Or is it actually trying to start something else?
Does dolphin start when you run it from the application menu?
If not, what’s in ~/.xsession-errors-:0 afterwards?
Sorry, bouncing icons seem to have been a 13.2 phenomenon.
In this RC1 case, a new entry appears on the Task bar with a rotating pair of arcs.
Rotates for perhaps 10 sec then disappears.
Other application launch ok from Desktop (konsole, ksysgard, even Dolphin-Super User Mode)
Dolphin does open quickly when selected from the Application Menu.
After Dolphin opened from the Application menu, I navigated to and opened ~/.xsession-errors-:0.
I set the cursor to the bottom of the log file, then tried launching Dolphin again from the GUI.
Same spinning result on the task bar, no additional entries in ~/.xsession-errors-:0.
So I played a bit after my previous post
I dragged the Dolphin icon from the Application launch menu to the Desktop folder and selected the “copy” option.
My first surprise was that the file just copied, did not ask for guidance to overwrite the dolphin desktop file already in the Desktop folder.
Dolphin opens OK from the Desktop Folder when I click the “new” (from Launcher) icon.
Here is the difference. The file dolphin.desktop is in the default startup Desktop folder
Application Launcher launches org.kde.dolphin.desktop
No, it is not.
Plasma5 in Leap still supports the bouncing icons, and they are enabled by default. But the maximum time span has been lowered to 5 seconds, and if (as in your case) the application quits immediately, you won’t see it at all (just like in KDE4).
In this RC1 case, a new entry appears on the Task bar with a rotating pair of arcs.
Rotates nor perhaps 10 sec then disappears.
Yes, that’s an additional indication that an application is starting (by the task manager).
This was also done in KDE4 btw, i.e. in openSUSE 13.2 and earlier.
Nothing new really.
There is no “dolphin desktop file” in the Desktop folder in a default installation.
There’s one for the home folder and the trash, those are added on first login.
Here is the difference. The file dolphin.desktop is in the default startup Desktop folder
Application Launcher launches org.kde.dolphin.desktop
Yes. KF5 applications don’t support the “-caption” parameter any more.
Removing it is fine, or you can replace it with “-qwindowtitle”.
Is this normal WIP getting ready for final release, or do I need to post a bug?
This is an oversight.
That “super user mode” icon is an openSUSE addition.
Dolphin has been ported to KF5 in 15.08, but that openSUSE addition has been forgotten to be adapted.
Or do you mean the .desktop file for the default icons on the desktop folderview (Home and Trash) have the wrong entry too?
I submitted a fix for the “File Manager - Super-user mode” menu entry now, but those should be fixed as well of course if necessary.
openSUSE does not change those, so this should even be reported to KDE at http://bugs.kde.org/.
PS, those icons do not even have an Exec= line.
So KDE should just use what’s set as default file manager in “Configure Desktop”.
Maybe this is not set to dolphin but something else (that doesn’t work)?
That’s actually why I asked if you really see a dolphin icon bouncing when you open it.
I logged in to the KDE Plasma workspace, not the Plasma 5 workspace
On the desktop there was a pre-setup folder view widget, which I believe was the Desktop Folder as it contained folder icons for Home and Trash as well as a few application icons, including one for Dolphin and one for File-Manager - Super User Mode and a couple others.
As I type this I am realizing that when I installed RC1, I did so reusing my /home from my initial install of Beta1
So my ~/Desktop folder may have been a mashup of Beta1 and RC1 (?).
To answer your most recent query, No, I do not get the “bouncing Dolphin” icon, just the spinning on the task bar.
To be honest, I have not seen any “bouncing Icons” yet, say when I open the Application Launcher version of Dolphin from the Desktop folder (I copied it there)…
Perhaps RC1 is just too fast and gets past bouncing; in this specific case the Dolphin GUI displays Very Quickly.
This is my first dive into Plasma5, so I realize I need to wipe a lot of legacy terminology
KInfoCenter ( I like the updated layout) tells me I am running KDE Plasma Version 5.4.2, Qt version 5.5.0.
Yet I see KDE specific settings are still in ~/.kde4
So my host machine (13.2) is running "KDE Platform Version 4.14.9.
I guess in the Leap world I should say I am running Leap 14.1 with KDE 5.4.2 version of KF5?
I was sort of expecting to find my setting specifics in ~/.kde5/…
I almost hate to ask, when you say
Dolphin has been ported to KF5 in 15.08, but that openSUSE addition has been forgotten to be adapted.
what does the 15.08 refer to?
I know that somewhere in KDE space there is a lot of documentation on the future versioning structure.
Since the future is now, I need to go back and read it again.
That’s exactly the same, Plasma 5.
KDE4 (the “KDE Plasma workspace” in 13.2 and before) is not available at all any more.
“KDE Plasma workspace” is mainly there for compatibility reasons, so that people who upgrade from earlier versions do get logged in to Plasma5 and not into a fallback twm session.
On the desktop there was a pre-setup folder view widget, which I believe was the Desktop Folder as it contained folder icons for Home and Trash
Yes. And those icons don’t contain a Exec= line, they just start what is set as default file manager (with the corresponding directory).
as well as a few application icons, including one for Dolphin and one for File-Manager - Super User Mode and a couple others.
Those are in the desktop folderview?
That shouldn’t be IMHO.
As I type this I am realizing that when I installed RC1, I did so reusing my /home from my initial install of Beta1
So my ~/Desktop folder may have been a mashup of Beta1 and RC1 (?).
Maybe. And maybe you added those icons yourself?
A dolphin icon from Beta1 will definitely not work any more, as that was the KDE4 version. The KF5 one doesn’t support the “-caption” option as mentioned and will not start when it’s present, and the .desktop file is even called differently and located in a different place (so even a link will not work).
There’s not much we as a distribution can do about things that have been copied to ~/Desktop manually.
To answer your most recent query, No, I do not get the “bouncing Dolphin” icon, just the spinning on the task bar.
You originally mentioned a bouncing icon, but no application showing up.
But as Dolphin is actually started and quits immediately, that’s probably why you don’t see it.
These “bouncing icon” is only displayed while the application is loaded…
To be honest, I have not seen any “bouncing Icons” yet, say when I open the Application Launcher version of Dolphin from the Desktop folder (I copied it there)…
Perhaps RC1 is just too fast and gets past bouncing; in this specific case the Dolphin GUI displays Very Quickly.
Maybe.
Or it might also be disabled in the settings.
See “Configure Desktop”->Applications->Startup notification.
This is my first dive into Plasma5, so I realize I need to wipe a lot of legacy terminology
The terminology hasn’t really changed though since KDE4.
KInfoCenter ( I like the updated layout) tells me I am running KDE Plasma Version 5.4.2, Qt version 5.5.0.
Yet I see KDE specific settings are still in ~/.kde4
KDE4 applications still store their things in ~/.kde4. And an upgrade also doesn’t clean up ~/.kde4 (or any other user folder for that matter).
Plasma5 and other KF5 applications only use ~/.config and ~/local/share though (and ~/.cache for cache files), except that some of them migrate the KDE4 config on first start.
So my host machine (13.2) is running "KDE Platform Version 4.14.9.
I guess in the Leap world I should say I am running Leap 14.1 with KDE 5.4.2 version of KF5?
No.
You are running Plasma 5.4.2 as desktop, using KDE Frameworks 5.15.
You can run any set of applications in there, be it KF5 based, KDE4 based, or even GTK based.
That’s why something like “I’m using KDE5” doesn’t really make sense.
I was sort of expecting to find my setting specifics in ~/.kde5/…
See above.
KF5 uses the freedesktop.org standard directories.
KDE4 only used ~/.kde4 on openSUSE to make it co-exist with KDE3, and it was first released before that (then) new standard was established.
GNOME3 did already use ~/.config and ~/.local since it’s first release years ago, although GNOME2 used ~/.gnome2 (similar to KDE3/4, as that was the de-facto standard then)
I almost hate to ask, when you say
what does the 15.08 refer to?
The August (08) 2015 release of “KDE Applications”.
It’s a time-based versioning scheme. 15.08.0 is the first release in August 2015, 15.08.1 and so on are further bugfix releases.
And 15.12.0 will be the next feature release in December.
They decided to use a version number like this, as it contains both KDE4 and KF5 based applications (not all have been ported yet).
Having a, say, “KDE 5.4” with half of the applications still using KDE4’s libraries actually wouldn’t make much sense either.
Even though KDE Applications is released as a whole bundle, in the end it’s only the version number of the application you use that matters.
E.g. you are using Dolphin 15.08.1. It’s irrelevant what version Ark has if you have a problem with Dolphin, isn’t it?
As mentioned already, it also doesn’t matter which desktop/workspace you use (or which version) if you have a problem with Dolphin. And you can use Dolphin on any desktop, you don’t have to install/run KDE’s desktop.
The libraries (frameworks) are used by dolphin, but they are upward compatible. I.e. you can use the same dolphin with Frameworks 5.14 and 5.15.
And they are also used by applications that are not part of KDE itself (and the desktop of course). So why should they be bundled with the applications and follow the same versioning scheme and release cycle?
I now suspect the root of my ‘Dolphin issue’ is that I reused /home when upgrading from Beta1 to RC1.
So most/all of my ~/Desktop may have been Beta1 entries
I don’t think I added the Dolphin icon to the Desktop folder, since .desktop files are sort of hard to find or or no longer in /usr/share/Applications where I looked.
I assume that is just a transition thing.
The Launcher menu seems much richer than in 13.2, easy to drag applications (and their .desktops) from there to Desktop folder if desired.
Fact is, I’ll probably use Application Launcher more for “core stuff” going forward.
It might be a good enhancement, for transition understanding, to have the “KDE Frameworks 5.15” info added to the new KInfoCenter.
I’ll post an enhancement suggestion.
Is there a CLI query that returns the KF version?
Definitely not. Beta1 only created the two icons as mentioned: Home and Trash.
You must have created them yourself.
I don’t think I added the Dolphin icon to the Desktop folder, since .desktop files are sort of hard to find or or no longer in /usr/share/Applications where I looked.
Of course they are in /usr/share/applications/, that’s the canonical place for application launcher .desktop files.
The Launcher menu seems much richer than in 13.2, easy to drag applications (and their .desktops) from there to Desktop folder if desired.
Fact is, I’ll probably use Application Launcher more for “core stuff” going forward.
Dragging icons from the launcher to the desktop was possible in KDE4 already.
It might be a good enhancement, for transition understanding, to have the “KDE Frameworks 5.15” info added to the new KInfoCenter.
I’ll post an enhancement suggestion.
See Help->About (“Version” tab) in any KF5 application, including KInfocenter.
The Frameworks5 version is not really a part of the “system information”, as it is only used by KF5 applications.
Other applications (including KDE4 based ones) use other toolkits, the KF5 version is irrelevant.
Is there a CLI query that returns the KF version?
Run any KF5 application with the “-v” switch, e.g. “kf5-config -v”.
Or something like “rpm -q libKF5WindowSystem5”
Ahhh, yes they are, if you are not in a hurry and look for your favourites under,
for example, org.kde.dolphin.desktop rather than just dolphin.desktop
Hello! I have another problem. When I login in Plasma4/5 the desktop shows, but everything (only the “burger” icon and the wallpaper stay) disappears immediately if I click something (or just launch anything). IceWM and Gnome work perfectly. Someone suggested checking “journalctl -u xorg.service”, but it doesn’t exist. Host: windows 7
VirtualBox’s 3D support is just not up to the task to running KDE (4 or 5) without problems.
There is a reason why it’s still labelled as “experimental” in the manual, I suppose…
Someone suggested checking “journalctl -u xorg.service”, but it doesn’t exist.
Who and where?
There is no “xorg.service” in openSUSE, and never was.
And only gdm forwards the logs to the journal.
A KDE installation either uses KDM (upto 13.2) or SDDM (in Leap and Tumbleweed, but if you upgraded it won’t be changed either), in which case the Xorg log goes to /var/log/Xorg.0.log as always.
