Reply to topic

Video and HTML wallpaper types

acrimont
Registered Member
Posts
27
Karma
0

Re: Video and HTML wallpaper types

Tue Oct 25, 2016 9:42 am
Amazing! It works wonderfully! Thank you so much Rog131! The shortcut (KDE service) was not working but I made the file with a simple shell command and now I have the aerial videos used for my lockscreen. It looks gorgeous!

I have looked for your link about KDE service but everything looks dated. I was looking for a way to confirm the path you typed (because I had to create the directory `ServiceMenus` So I was not sure it was the correct location but instead, in the documentation, it is referencing a command `kde4-config --path services` which outputs: `~/.kde4/share/kde4/services/`.

And then I finally seen that it was only working for `Konqueror` (and I was using Dolphin). But again thank you for all this stuff!
User avatar Rog131
Registered Member
Posts
828
Karma
10

Re: Video and HTML wallpaper types

Tue Oct 25, 2016 3:49 pm
acrimont wrote:...The shortcut (KDE service) was not working but I made the file with a simple shell command and now I have the aerial videos used for my lockscreen. It looks gorgeous!

I have looked for your link about KDE service but everything looks dated. I was looking for a way to confirm the path you typed (because I had to create the directory `ServiceMenus` So I was not sure it was the correct location but instead, in the documentation, it is referencing a command `kde4-config --path services` which outputs: `~/.kde4/share/kde4/services/`.

And then I finally seen that it was only working for `Konqueror` (and I was using Dolphin). But again thank you for all this stuff!


Current Dolphin is using KDE Frameworks 5 (KF5):
Image

Current Konqueror is using KDE4 libraries:
Image
The next KDE Applications release 16.12 will (probably) have the KF5 based Konqueror.

With the KF5 the service path is:
Code: Select all
kf5-config --path services

So at here the service menus are looked at
~/.local/share/kservices5/ServiceMenus/
and
/usr/share/kservices5/ServiceMenus/


Neon ?

About Dolphin & Service Menus - 'Cobber' wrote at viewtopic.php?f=225&t=135525&hilit=dolphin+service#p362576
...This doesn't work in Neon. Some of the essential packages mentioned are not installed and do not show as available in Synaptic.

The version of Dolphin is also fully ported to KDE 5 and the problem with service menus is a known bug....


I don't use the Neon so I only can tell that at here the service menus are working without problems.
acrimont
Registered Member
Posts
27
Karma
0

Re: Video and HTML wallpaper types

Thu Oct 27, 2016 1:55 pm
In fact, I am using Archlinux and not Neon. So I just have to wait for the next release of KDE applications in order to be able to use these services. It's really the kind of thing which can make me save time.

Code: Select all
➜  ~ kf5-config --path services
~/.local/share/kservices5/:/usr/share/kservices5/


So I think it is the same here. I will just need to wait for the next release. Where did you get all these information? I am just reading kde.org & dot.kde.org and I could never imagine that so much things were possible.
acrimont
Registered Member
Posts
27
Karma
0

Re: Video and HTML wallpaper types

Tue Nov 08, 2016 8:29 am
@Rog131, I have noticed something annoying with the ramdom video player when used in the lock screen. The first time the videos are played everything is fine, but then, once the first videos are finished, the new ones comes and they are played a little less smooth, and then with the new ones after a little less smooth again...
And If I wait something like one hour, the videos are stucked and do not play anymore. And it becomes hard to type the password in order to unlock the session because there is so much latency.
It looks like there is a memory leak or something...

I could look for it this weekend but do you have any idea about what can cause that?
User avatar Rog131
Registered Member
Posts
828
Karma
10

Re: Video and HTML wallpaper types

Tue Nov 08, 2016 12:34 pm
acrimont wrote:@Rog131, I have noticed something annoying with the ramdom video player when used in the lock screen. The first time the videos are played everything is fine, but then, once the first videos are finished, the new ones comes and they are played a little less smooth, and then with the new ones after a little less smooth again...
And If I wait something like one hour, the videos are stucked and do not play anymore. And it becomes hard to type the password in order to unlock the session because there is so much latency.
It looks like there is a memory leak or something...

I could look for it this weekend but do you have any idea about what can cause that?


Earlier - About error messages : viewtopic.php?f=289&t=131783#p362593

At here, with four clips:

Image

Leaving the screen locked for one hour.... Everything seems to work without problems.
Systemd journal is clean.
Memory before:
Code: Select all
$ free -m
              total        used        free      shared  buff/cache   available
Mem:           7965         608        5844           6        1512        7051
Swap:          2000           0        2000


After:
Code: Select all
$ free -m
              total        used        free      shared  buff/cache   available
Mem:           7965         544        5903           5        1518        7117
Swap:          2000           0        2000


How many clips did you have ?
Has the number of clips any impact ?
Are the .xsession-errors, journalctl, etc. clean ?
Have you recorded the memory usage during the screen locking ?
acrimont
Registered Member
Posts
27
Karma
0

Re: Video and HTML wallpaper types

Thu Nov 10, 2016 1:00 pm
Hello,

Thanks for your help!

First, I am using all the videos from Apple Aerial things, so 35 videos.
Then, I have a lot of different messages from my journalctl. I copy them to you here:
Code: Select all
Nov 10 12:27:39 da_computer kdeinit5[3239]: kscreen.kded: Saving current config to file
Nov 10 12:27:39 da_computer kdeinit5[3239]: kscreen.kded: Config saved on:  "/home/ekaradon/.local/share/kscreen/023570d847964fc52dd741558d6e429c"
Nov 10 12:27:39 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 66   "eDP-1" connected enabled QPoint(0,0) QSize(1920, 1080) "71" )
Nov 10 12:27:39 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 68   "HDMI-1" connected disabled QPoint(0,0) QSize(1920, 1080) "" )
Nov 10 12:27:40 da_computer ksmserver[3273]: Unknown toplevel for ConfigureNotify
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRScreenChangeNotify
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Window: 23068676
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Root: 228
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Size ID: 65535
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Size:  3840 1080
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         SizeMM:  1013 285
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRNotify_CrtcChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  64
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  91
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Geometry:  1920 0 1920 1080
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRotify_OutputChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Output:  68
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  64
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  91
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Connection:  "Connected"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Subpixel Order:  0
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: Config applied
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: Monitor for changes:  true
Nov 10 12:27:40 da_computer ksmserver[3273]: CreateNotify: 39848945
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRScreenChangeNotify
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Window: 23068676
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Root: 228
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Size ID: 65535
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Size:  3840 1080
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         SizeMM:  1013 285
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRNotify_CrtcChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  64
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  91
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Geometry:  1920 0 1920 1080
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRotify_OutputChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Output:  68
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  64
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  91
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Connection:  "Connected"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Subpixel Order:  0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRNotify_CrtcChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  63
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  71
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Geometry:  0 0 1920 1080
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRNotify_CrtcChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  64
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  91
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Geometry:  1920 0 1920 1080
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRNotify_CrtcChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  65
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Geometry:  0 0 0 0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRotify_OutputChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Output:  66
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  63
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  71
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Connection:  "Connected"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Subpixel Order:  0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRotify_OutputChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Output:  67
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Connection:  "Disconnected"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Subpixel Order:  0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRotify_OutputChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Output:  68
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  64
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  91
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Connection:  "Connected"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Subpixel Order:  0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRotify_OutputChange
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Output:  69
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  0
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Connection:  "Disconnected"
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Subpixel Order:  0
Nov 10 12:27:40 da_computer org_kde_powerdevil[3318]: kscreen: Requesting missing EDID for outputs (66, 68)
[...]
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: Change detected
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 66   "eDP-1" connected enabled QPoint(0,0) QSize(1920, 1080) "71" )
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 68   "HDMI-1" connected enabled QPoint(1920,0) QSize(1920, 1080) "91" )
Nov 10 12:27:40 da_computer ksmserver[3273]: CreateNotify: 69361821
Nov 10 12:27:40 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 56593, resource id: 69361813, major code: 20 (GetProperty), minor code: 0
Nov 10 12:27:40 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 56604, resource id: 69361813, major code: 20 (GetProperty), minor code: 0
Nov 10 12:27:40 da_computer ksmserver[3273]: CreateNotify: 38032204
Nov 10 12:27:40 da_computer ksmserver[3273]: MapNotify: 38032204
Nov 10 12:27:40 da_computer ksmserver[3273]: CreateNotify: 38032208
Nov 10 12:27:40 da_computer ksmserver[3273]: MapNotify: 38032208
Nov 10 12:27:40 da_computer ksmserver[3273]: CreateNotify: 38032209
Nov 10 12:27:40 da_computer ksmserver[3273]: MapNotify: 38032209
Nov 10 12:27:40 da_computer ksmserver[3273]: UnmapNotify: 38032194
Nov 10 12:27:40 da_computer ksmserver[3273]: UnmapNotify: 38032193
Nov 10 12:27:40 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 56875, resource id: 69361813, major code: 20 (GetProperty), minor code: 0
Nov 10 12:27:40 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 56887, resource id: 69361813, major code: 20 (GetProperty), minor code: 0
Nov 10 12:27:40 da_computer ksmserver[3273]: MapNotify: 69361821
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: Saving current config to file
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: Config saved on:  "/home/ekaradon/.local/share/kscreen/023570d847964fc52dd741558d6e429c"
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 66   "eDP-1" connected enabled QPoint(0,0) QSize(1920, 1080) "71" )
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 68   "HDMI-1" connected enabled QPoint(1920,0) QSize(1920, 1080) "91" )
Nov 10 12:27:40 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: Emitting configChanged()
Nov 10 12:27:40 da_computer org_kde_powerdevil[3318]: kscreen: Requesting missing EDID for outputs (66, 68)
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen: Requesting missing EDID for outputs (66, 68)
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: Change detected
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 66   "eDP-1" connected enabled QPoint(0,0) QSize(1920, 1080) "71" )
Nov 10 12:27:40 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 68   "HDMI-1" connected enabled QPoint(1920,0) QSize(1920, 1080) "91" )
Nov 10 12:27:41 da_computer kdeinit5[3239]: kscreen.kded: Saving current config to file
Nov 10 12:27:41 da_computer kdeinit5[3239]: kscreen.kded: Config saved on:  "/home/ekaradon/.local/share/kscreen/023570d847964fc52dd741558d6e429c"
Nov 10 12:27:41 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 66   "eDP-1" connected enabled QPoint(0,0) QSize(1920, 1080) "71" )
Nov 10 12:27:41 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 68   "HDMI-1" connected enabled QPoint(1920,0) QSize(1920, 1080) "91" )
Nov 10 12:32:27 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:27 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:29 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:29 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:32 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:32 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:33 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:33 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:35 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:35 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:36 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 12:32:36 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
[...]
Nov 10 12:32:38 da_computer org_kde_powerdevil[3318]: kscreen: Requesting missing EDID for outputs (66)
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen: Requesting missing EDID for outputs (66)
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded: resetDisplaySwitch()
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded: outputConnectedChanged(): "HDMI-1"
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded: Change detected
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 66   "eDP-1" connected enabled QPoint(0,0) QSize(1920, 1080) "71" )
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded: Applying config
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded: Applying known config "23b3d8ea714d9eb45d70db2ec995cc27"
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded: Finding a mode for QSize(1920, 1080) @ 60.0962
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded:         Found:  "71"   QSize(1920, 1080) @ 60.0962
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded: doApplyConfig()
Nov 10 12:32:38 da_computer kdeinit5[3239]: kscreen.kded: Monitor for changes:  false
[...]
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: XRandR::setConfig
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: Requested screen size is QSize(1920, 1080)
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: Needed CRTCs:  1
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: Actions to perform:
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         Primary Output: false
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         Change Screen Size: true
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:                 Old: QSize(3840, 1080)
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:                 Intermediate: QSize(3840, 1080)
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:                 New: QSize(1920, 1080)
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         Disable outputs: true
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:                  (68)
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         Change outputs: false
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         Enable outputs: false
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: RRSetCrtcConfig (disable output)
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         CRTC: 64
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         Result: 0
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: XRandROutput 68 update
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         m_connected: 0
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         m_crtc XRandRCrtc(0x16e3a70)
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         CRTC: 0
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         MODE: 0
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         Connection: 0
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         Primary: false
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: Disconnected output 68 from CRTC 64
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: RRSetScreenSize
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         DPI: 96.2526
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         Size: QSize(1920, 1080)
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr:         SizeMM: QSize(506, 285)
Nov 10 12:32:38 da_computer kscreen_backend_launcher[3277]: kscreen.xrandr: XRandR::setConfig done!
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRNotify_CrtcChange
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  64
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  0
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Geometry:  0 0 0 0
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRotify_OutputChange
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Output:  68
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         CRTC:  0
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Mode:  0
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Rotation:  "Rotate_0"
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Connection:  "Connected"
Nov 10 12:32:39 da_computer kscreen_backend_launcher[3277]: kscreen.xcb.helper:         Subpixel Order:  0
Nov 10 12:32:39 da_computer ksmserver[3273]: Unknown toplevel for ConfigureNotify
[...]
Nov 10 12:32:39 da_computer org_kde_powerdevil[3318]: kscreen: Requesting missing EDID for outputs (66, 68)
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen: Requesting missing EDID for outputs (66, 68)
Nov 10 12:32:39 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 61929, resource id: 39848988, major code: 18 (ChangeProperty), minor code: 0
Nov 10 12:32:39 da_computer ksmserver[3273]: UnmapNotify: 39848988
Nov 10 12:32:39 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 61930, resource id: 39848988, major code: 12 (ConfigureWindow), minor code: 0
Nov 10 12:32:39 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 61934, resource id: 39848991, major code: 18 (ChangeProperty), minor code: 0
Nov 10 12:32:39 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 61935, resource id: 39848991, major code: 12 (ConfigureWindow), minor code: 0
Nov 10 12:32:39 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 61939, resource id: 39848988, major code: 3 (GetWindowAttributes), minor code: 0
Nov 10 12:32:39 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 61941, resource id: 39848988, major code: 8 (MapWindow), minor code: 0
Nov 10 12:32:39 da_computer kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 61942, resource id: 39848988, major code: 12 (ConfigureWindow), minor code: 0
[...]
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: resetDisplaySwitch()
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: outputConnectedChanged(): "HDMI-1"
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: Change detected
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 66   "eDP-1" connected enabled QPoint(0,0) QSize(1920, 1080) "71" )
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: KScreen::Output( 68   "HDMI-1" connected disabled QPoint(0,0) QSize(1920, 1080) "" )
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: Applying config
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: Applying known config "023570d847964fc52dd741558d6e429c"
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: Finding a mode for QSize(1920, 1080) @ 60.0962
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded:         Found:  "71"   QSize(1920, 1080) @ 60.0962
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: Finding a mode for QSize(1920, 1080) @ 60
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded:         Found:  "91"   QSize(1920, 1080) @ 60
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: doApplyConfig()
Nov 10 12:32:39 da_computer kdeinit5[3239]: kscreen.kded: Monitor for changes:  false
[...]
Nov 10 13:13:24 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:24 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:31 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:31 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:36 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:36 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:39 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:51 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:51 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:53 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:53 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:13:54 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:06 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:06 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:08 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:08 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:32 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:32 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:37 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:37 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:37 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:59 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:14:59 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:15:08 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:15:08 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:15:34 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:15:34 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:16:38 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:16:38 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:16:54 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:16:54 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:17:26 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:17:28 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:17:28 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:18:09 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:18:09 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:18:22 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:16 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:16 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:24 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:24 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:24 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:30 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:30 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:32 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:32 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:45 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:19:45 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:20:02 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."
Nov 10 13:20:02 da_computer kscreenlocker_greet[19463]: Error: "Internal data stream error."


After looking for the memory usage, I did not find anything.
Before:
Code: Select all
free -m
              total        used        free      shared  buff/cache   available
Mem:          15947        3700        5238         511        7008       11396
Swap:             0           0           0


After:
Code: Select all
free -m
              total        used        free      shared  buff/cache   available
Mem:          15947        4665        3966         600        7315       10342
Swap:             0           0           0


I will investigate again this week-end for the other information (error message on video, x-sessions errors, impact of number of clips, ...). But maybe with these messages you have already an idea?
acrimont
Registered Member
Posts
27
Karma
0

Re: Video and HTML wallpaper types

Thu Dec 15, 2016 12:38 pm
Well, a bit late but I tried running the video with `qmlscene`. I did not get any error output.

So I have no idea why it becomes slow. I just know I have these messages which spawn in the journalctl each time I lock my session for some times:
  • kscreenlocker_greet[24816]: Error: "Internal data stream error."
  • kscreen_backend_launcher[3277]: kscreen.xcb.helper: RRotify_OutputChange
  • kwin_x11[3281]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 56604, resource id: 69361813, major code: 20 (GetProperty), minor code: 0
  • kscreen: Requesting missing EDID for outputs
  • kscreen_backend_launcher[5475]: kscreen.xrandr: Emitting configChanged()
  • kscreenlocker_greet[24816]: QXcbConnection: XCB error: 148 (Unknown), sequence: 65118, resource id: 0, maj

Has someone any idea?
User avatar Rog131
Registered Member
Posts
828
Karma
10

Re: Video and HTML wallpaper types

Thu Dec 15, 2016 7:01 pm
When things get slow:

Can you log in with the virtual terminal / console ?
Is there high CPU load ?
Are there free memory ?

When searching with the 'kscreen: Requesting missing EDID for outputs':
-> https://forums.opensuse.org/showthread. ... lfunctions

=> What kind of hardware do you have ?
GPU ?
Multimonitor ?
Open/Proprietary drivers ?
acrimont
Registered Member
Posts
27
Karma
0

Re: Video and HTML wallpaper types

Fri Dec 16, 2016 1:11 pm
Hello,

The load average is low (1.30), each CPU is under 10%, I still have more than 6Gb memory free (with a total of 16Gb).

Below:
Image

My computer is a laptop connected through HDMI to another screen.

Code: Select all
Screen 15.6" Full HD IPS (1920x1080, antireflet/mate)
CPU Intel Core i7-6700HQ Skylake (2.6 GHz, 4 cœurs)
Storage SSD M.2 de 128 Go + 1 To à 5400 tr/min
GPU NVIDIA Maxwell GeForce GTX 960M 2 Go GDDR5 dédiés, Intel HD 530 intégrée au processeur et Optimus
Wi-Fi ac
Bluetooth 4.0
Card reader SD/SDXC
Video Output HDMI 1.4
USB 3 USB 3.0 + 1 USB 3.1 Type-C (Thunderbolt)
Battery Li-Polymère 4 cells 60Whr


I am using a proprietary driver: extra/nvidia 375.26-1 [installed]
User avatar Rog131
Registered Member
Posts
828
Karma
10

Re: Video and HTML wallpaper types

Sat Dec 17, 2016 9:51 am
acrimont wrote:.
.
.
My computer is a laptop connected through HDMI to another screen.
.
.
.


Any difference if you use only one screen ?
acrimont
Registered Member
Posts
27
Karma
0

Re: Video and HTML wallpaper types

Mon Dec 19, 2016 5:57 pm
Yes indeed, when I am using only one screen, I do not have this issue. It stays smooth...
User avatar Rog131
Registered Member
Posts
828
Karma
10

Re: Video and HTML wallpaper types

Mon Dec 19, 2016 6:36 pm
acrimont wrote:Yes indeed, when I am using only one screen, I do not have this issue. It stays smooth...


Maybe this is (still) the KDE multi-screen woes: https://blog.martin-graesslin.com/blog/ ... lasma-5-7/


Looking KSCreen bug reports from the KDE bug tracker: https://bugs.kde.org/

Hmm - something to try - https://bugs.kde.org/show_bug.cgi?id=354163#c4 :
In >Startup and Shutdown>Background Serivces> untick "KScreen2" and reboot.


Better ?

if worse: https://bugs.kde.org/show_bug.cgi?id=354163#c5
User avatar Rog131
Registered Member
Posts
828
Karma
10

Re: Video and HTML wallpaper types

Mon Dec 19, 2016 6:38 pm
General KDE lock screen testing

Plasma wallpaper plugins can be tested as lock greeters with the command:

Code: Select all
$ /usr/lib/kscreenlocker_greet --help
Usage: /usr/lib/kscreenlocker_greet [options]
Greeter for the KDE Plasma Workspaces Screen locker

Options:
  -h, --help                  Displays this help.
  -v, --version               Displays version information.
  --testing                   Starts the greeter in testing mode
  --theme <theme>             Starts the greeter with the selected theme (only
                              in Testing mode)
  --immediateLock             Lock immediately, ignoring any grace time etc.
  --graceTime <milliseconds>  Delay till the lock user interface gets shown in
                              milliseconds.
  --nolock                    Don't show any lock user interface.
  --switchuser                Default to the switch user UI.
  --ksldfd <fd>               File descriptor for connecting to ksld.
acrimont
Registered Member
Posts
27
Karma
0

Re: Video and HTML wallpaper types

Tue Dec 20, 2016 1:28 pm
Rog131 wrote:
acrimont wrote:Yes indeed, when I am using only one screen, I do not have this issue. It stays smooth...


Maybe this is (still) the KDE multi-screen woes: https://blog.martin-graesslin.com/blog/ ... lasma-5-7/


Looking KSCreen bug reports from the KDE bug tracker: https://bugs.kde.org/

Hmm - something to try - https://bugs.kde.org/show_bug.cgi?id=354163#c4 :
In >Startup and Shutdown>Background Serivces> untick "KScreen2" and reboot.


Better ?

if worse: https://bugs.kde.org/show_bug.cgi?id=354163#c5


It is worst. I was not able to login anymore. I have ticked it again. I will try to test the plugin with kscreenlocker_greet. I am not sure however to see anything noticeable.
User avatar Rog131
Registered Member
Posts
828
Karma
10

Re: Video and HTML wallpaper types

Tue Dec 20, 2016 6:40 pm
acrimont wrote:...I will try to test the plugin with kscreenlocker_greet. I am not sure however to see anything noticeable.


No, it probably doesn't show useful information for you problem. It is for those who want to test KDE lock screen greeter. It will tell if the lock screen greeter is working at all. The other option is to test the greeters with the 'real lock screen' and then, if the greeter is not working, unlock with the locking manager:

Code: Select all
$ loginctl --help
loginctl [OPTIONS...] {COMMAND} ...

Send control commands to or query the login manager.

  -h --help                Show this help
     --version             Show package version
     --no-pager            Do not pipe output into a pager
     --no-legend           Do not show the headers and footers
     --no-ask-password     Don't prompt for password
  -H --host=[[email protected]]HOST    Operate on remote host
  -M --machine=CONTAINER   Operate on local container
  -p --property=NAME       Show only properties by this name
  -a --all                 Show all properties, including empty ones
     --value               When showing properties, only print the value
  -l --full                Do not ellipsize output
     --kill-who=WHO        Who to send signal to
  -s --signal=SIGNAL       Which signal to send
  -n --lines=INTEGER       Number of journal entries to show
  -o --output=STRING       Change journal output mode (short, short-monotonic,
                           verbose, export, json, json-pretty, json-sse, cat)

Session Commands:
  list-sessions            List sessions
  session-status [ID...]   Show session status
  show-session [ID...]     Show properties of sessions or the manager
  activate [ID]            Activate a session
  lock-session [ID...]     Screen lock one or more sessions
  unlock-session [ID...]   Screen unlock one or more sessions
  lock-sessions            Screen lock all current sessions
  unlock-sessions          Screen unlock all current sessions
  terminate-session ID...  Terminate one or more sessions
  kill-session ID...       Send signal to processes of a session

User Commands:
  list-users               List users
  user-status [USER...]    Show user status
  show-user [USER...]      Show properties of users or the manager
  enable-linger [USER...]  Enable linger state of one or more users
  disable-linger [USER...] Disable linger state of one or more users
  terminate-user USER...   Terminate all sessions of one or more users
  kill-user USER...        Send signal to processes of a user
.
.
.


i.e ,with the root powers, unlocking all:
Code: Select all
# loginctl unlock-sessions



The best advice I can give to you problem is to examine the KDE bug reports of the multi display problems...

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], Google [Bot], JesusM, legomaniac, smankowski, YaCy [Bot]