Hi:

I've made a new installation of opensuse 13.2 with Plasma 5. Now. I found it very, very slow. For example, if click to logout widget it takes up to three minutes to appear. In addition, some hotkeys not respond, for example ctrl-esc. KinfoCenter shows the version of Plasma 5.395 although I noticed 5.4 several packages being installed when using zypper up. Is there a simple straightforward way to uninstall/remove all of KDE/Plasma packages and reinstall them fresh.

In addition, I came accross the zypper command zypper packages --orphaned. What is the real purpose thereof. I found some topics in different forums saying that this way one may find useless files left behing a removed package. When I entered this command in my system I got a long list of files/packages but I found many of them are packages I regularly use. So where is the catch.

B.

3 Minutes is an I/O error, possibly some cache is built over-and-over again.
If that's been slightly exaggerated, you may just run some inferior (VESA?) graphics driver (which means OpenGL isn't accelerated)

You can check the latter in /var/log/Xorg.0.log and the "glxinfo" output and the former by opening konsole and call

Code: Select all

pkill plasmashell
plasmashell &


There may be interesting debug outputs (ksycoca rebuild?) on triggering the slow actions.

Hi:
I said up to 3 minutes, and that is true. Often I have to kill machine by a long-pressing the on-off button. Nevertheless, the Xorg.0.log has a section with the following info if it is of any help for you:
...
[ 12.886] (II) LoadModule: "fbdevhw"
[ 12.886] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 12.886] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 12.886] compiled for 1.16.1, module version = 0.0.2
[ 12.886] ABI class: X.Org Video Driver, version 18.0
[ 12.886] (WW) Falling back to old probe method for vesa
[ 12.886] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 12.886] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 12.886] (==) NVIDIA(0): RGB weight 888
[ 12.886] (==) NVIDIA(0): Default visual is TrueColor
[ 12.886] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 12.886] (**) NVIDIA(0): Enabling 2D acceleration
[ 13.626] (II) NVIDIA(0): Display (LGD (DFP-0)) does not support NVIDIA 3D Vision
[ 13.626] (II) NVIDIA(0): stereo.
[ 13.626] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 13.627] (II) NVIDIA(0): NVIDIA GPU Quadro 3000M (GF104GL) at PCI:1:0:0 (GPU-0)
[ 13.627] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 13.627] (--) NVIDIA(0): VideoBIOS: 70.04.3e.00.0b
[ 13.627] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 13.634] (--) NVIDIA(0): Valid display device(s) on Quadro 3000M at PCI:1:0:0
[ 13.634] (--) NVIDIA(0): CRT-0
[ 13.634] (--) NVIDIA(0): LGD (DFP-0) (boot, connected)
[ 13.634] (--) NVIDIA(0): DFP-1
[ 13.634] (--) NVIDIA(0): DFP-2
[ 13.634] (--) NVIDIA(0): DFP-3
[ 13.634] (--) NVIDIA(0): DFP-4
[ 13.634] (--) NVIDIA(0): DFP-5
[ 13.634] (--) NVIDIA(0): DFP-6
[ 13.634] (--) NVIDIA(0): DFP-7
[ 13.634] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 13.634] (--) NVIDIA(0): LGD (DFP-0): Internal LVDS
[ 13.634] (--) NVIDIA(GPU-0): LGD (DFP-0): 330.0 MHz maximum pixel clock
[ 13.634] (--) NVIDIA(0): DFP-1: Internal TMDS
[ 13.634] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 13.634] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 13.634] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 13.634] (--) NVIDIA(0): DFP-3: Internal TMDS
[ 13.634] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[ 13.634] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 13.634] (--) NVIDIA(GPU-0): DFP-4: 480.0 MHz maximum pixel clock
[ 13.635] (--) NVIDIA(0): DFP-5: Internal DisplayPort
[ 13.635] (--) NVIDIA(GPU-0): DFP-5: 480.0 MHz maximum pixel clock
[ 13.635] (--) NVIDIA(0): DFP-6: Internal DisplayPort
[ 13.635] (--) NVIDIA(GPU-0): DFP-6: 480.0 MHz maximum pixel clock
[ 13.635] (--) NVIDIA(0): DFP-7: Internal DisplayPort
[ 13.635] (--) NVIDIA(GPU-0): DFP-7: 480.0 MHz maximum pixel clock
[ 13.635] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 13.635] (**) NVIDIA(0): device LGD (DFP-0) (Using EDID frequencies has been
[ 13.635] (**) NVIDIA(0): enabled on all display devices.)
[ 13.635] (==) NVIDIA(0):
[ 13.635] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 13.635] (==) NVIDIA(0): will be used as the requested mode.
[ 13.635] (==) NVIDIA(0):
[ 13.635] (II) NVIDIA(0): Validated MetaModes:
[ 13.635] (II) NVIDIA(0): "DFP-0:nvidia-auto-select"
[ 13.635] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 14.703] (--) NVIDIA(0): DPI set to (128, 124); computed from "UseEdidDpi" X config
[ 14.703] (--) NVIDIA(0): option
[ 14.703] (II) UnloadModule: "nouveau"
[ 14.703] (II) Unloading nouveau
[ 14.703] (II) UnloadModule: "nv"
[ 14.703] (II) Unloading nv
[ 14.703] (II) UnloadModule: "modesetting"
[ 14.703] (II) Unloading modesetting
[ 14.703] (II) UnloadModule: "fbdev"
[ 14.703] (II) Unloading fbdev
[ 14.703] (II) UnloadSubModule: "fbdevhw"
[ 14.703] (II) Unloading fbdevhw
[ 14.703] (II) UnloadModule: "vesa"
[ 14.703] (II) Unloading vesa
[ 14.703] (--) Depth 24 pixmap format is 32 bpp
[ 14.703] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 14.703] (II) NVIDIA: access.
[ 14.708] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 14.708] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 14.708] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 14.708] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 14.708] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 14.708] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 14.708] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 14.708] (II) NVIDIA(0): Config Options in the README.
[ 14.713] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[ 15.075] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 15.076] (==) NVIDIA(0): Backing store enabled
[ 15.076] (==) NVIDIA(0): Silken mouse enabled
[ 15.076] (==) NVIDIA(0): DPMS enabled
[ 15.076] (II) Loading sub module "dri2"
[ 15.076] (II) LoadModule: "dri2"
[ 15.076] (II) Module "dri2" already built-in
[ 15.076] (II) NVIDIA(0): [DRI2] Setup complete
[ 15.076] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 15.076] (--) RandR disabled

No, that's the nvidia driver which should provide great acceleration.

Also "indeed 3 minutes" can hardly be caused by anything that's not some I/O (network, disk, maybe a broken dbus?)
You'll have to test restarting plasmashell from konsole and hope for some interesting output at the related moments - or gdb attach to the process and check in what function it waits so long.

Random ideas:
To check whether your dbus is usable, just type

Code: Select all

qdbus

into konsole - if it does not instantly print a list of available services, your session dbus is flodded and does not respond - synchronous dbus action will then timeout 25 seconds (each!)

Check "top" and "iotop" on massive CPU and I/O load - a usual suspect would be the baloo indexers.

You may also suffer from a broken installation (mismatch in version info), but unfortunately I cannot give you any help on zypper (but maybe someone else does

qdbus, top and iotop command provide no unusual/strange output. Everything runs flawlessly. Strange enough, immediately on fresh boot and login no "snaily" behaviour is noticed. Even ctrl-esc sequence works, widgets respond immediately (almost). Strange slow behaviour occurs in five to ten minutes. BTW, I have a HP Elitebook with opensuse 13.2 on SSD.
Thank you for all help.

Just to let you know, I managed to sort of solve the problem. What I did is as follows. I switched from kdm to sddm, and what I believe is most important, I disabled kdewallet. Those two things have made my notebook crawling.