tvtime kills plasma5

[keellambert]

hi,

with system setup :-
Kernel: 4.0.3-1-desktop x86_64 (64 bit)
Desktop KDE 4.14.7 Distro: openSUSE 20150516 (x86_64) Tumbleweed

if tvtime is started, either from a terminal or program manager,
plasma5 is frozen, pc is dead except for the mouse pointer can still be moved,
the only recourse is to manually switch the power off/on to reboot

with system setup :-
Kernel: 4.0.3-1-desktop x86_64 (64 bit)
Desktop IceWM 1.3.8 Distro: openSUSE 20150516 (x86_64) Tumbleweed

tvtime runs normally

anyone any idea of the possible course?

cheers

Graphics Card: Advanced Micro Devices [AMD/ATI] RS780 [Radeon HD 3200]
X.Org: 1.17.1 drivers: ati,radeon (unloaded: fbdev,vesa)
Resolution: 1680x1050@59.95hz, 1680x1050@59.88hz
GLX Renderer: Gallium 0.4 on AMD RS780 GLX Version: 3.0 Mesa 10.5.4
Direct Rendering: Yes

ps
can only get to Desktop IceWM via kdm, not possible via sddm

[keellambert]

Hi wolfi323,

responding here as it is more appropriate

@wolfi323

I tried Kaffeine with the one DVD (image) I found, and indeed the menus didn’t work. But switching between windowed and fullscreen mode (double-clicking or pressing ‘f’) fixed it.

This has nothing to do with Plasma5/kwin5 though, I see the same in KDE4, and even IceWM.

Kaffeine is just a frontend to libxine though, strange enough xine-ui doesn’t seem to have this problem.
(Actually work started some time ago to port Kaffeine to use libvlc instead, but this never was finished I think, at least it hasn’t been released yet)

thx for the feedback, at least it’s now known not to be the setup on this PC

@wolfi323

And I see the same problem as you describe with tvtime too, it seems to make kwin5 crash/freeze (works fine in KDE4). This might be worth a bug report.
Btw, it’s not necessary to powerdown/up the hardware, just switch to a text mode console (Ctrl+Alt+F1 e.g.) and “killall -KILL kwin_x11” (you can start kwin again afterwards by typing “kwin_x11” into the Alt+F2 dialog).
Without kwin running, tvtime works even.
As a side-note, I never liked or used tvtime anyway. I always preferred xdtv (and still use it), a fork of xawtv which even has recording facilities:
openSUSE Software
I package it myself, I don’t build it for Tumbleweed at the moment but can if you are interested.
This does work fine in Plasma5 too.

thx for the tip about restarting. xdtv has been tried before and rejected. but the offer is appreciated.

a bug report will be raised as soon as the new bugzilla format is understood.

cheers

[wolfi323]

@keellambert

a bug report will be raised as soon as the new bugzilla format is understood.

“New bugzilla format”? I suppose you mean the changes/reorganizations done to Novell/(open)SUSE’s bugzilla some time last year?
This should be reported at KDE’s bugzilla.
openSUSE does not develop KWin nor Plasma. We merely package it and don’t have the man power or knowledge to investigate and fix such bugs.

Sorry, I didn’t find the time to do so during the weekend, but I can do it in the next days.
I did see some output from kwin (when run in a terminal window) when starting tvtime, this might be related but I’m not sure.

Apparently tvtime does something strange/uncommon with its window, that triggers a bug in kwin(5).

[wolfi323]

Bug reported:
https://bugs.kde.org/show_bug.cgi?id=350708

[wolfi323]

Btw, a similar crash has been reported already recently:
https://bugs.kde.org/show_bug.cgi?id=350173

The problem is identified already and a fix is in review.
It seems those applications pass invalid icon data for the window, even xprop reports this for tvtime’s window:

wolfi@amiga:~> xprop
 _NET_WM_ICON_GEOMETRY(CARDINAL) = 634, 992, 210, 32
_NET_WM_NAME(UTF8_STRING) = "tvtime: television without borders"
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 2, 2, 23, 4
_NET_FRAME_EXTENTS(CARDINAL) = 2, 2, 23, 4
_NET_WM_DESKTOP(CARDINAL) = 0
_KDE_NET_WM_ACTIVITIES(STRING) = "ea46316a-56fe-43e8-be04-dd4a6cb1e8f1"
WM_STATE(WM_STATE):
                window state: Normal
                icon window: 0x0
_NET_WM_STATE(ATOM) = 
_KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 22872765
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW
WM_CLASS(STRING) = "TVWindow", "tvtime"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
                program specified size: 768 by 576
WM_ICON_NAME(STRING) = "tvtime"
WM_NAME(STRING) = "tvtime: television without borders"
_NET_WM_ICON(CARDINAL) = xprop: error: Out of memory!

This shouldn’t make kwin crash though of course. It has to ignore such invalid “user” data and/or do sanity checks before trying to use it…

[keellambert]

hi wolfi323

@wolfi323

And I see the same problem as you describe with tvtime too, it seems to make kwin5 crash/freeze (works fine in KDE4). This might be worth a bug report.

you beat me to it, it looks as though a fix is in the pipeline, thx

@wolfi323

Btw, it’s not necessary to powerdown/up the hardware, just switch to a text mode console (Ctrl+Alt+F1 e.g.) and “killall -KILL kwin_x11” (you can start kwin again afterwards by typing “kwin_x11” into the Alt+F2 dialog).
Without kwin running, tvtime works even.

going to a terminal and stopping kwin_x11 worked just fine

on return to the gui tvtime was indeed working

but lots of frame functionality was lost,
restarting kwin_x11 just messed up the desktop

conclusion
on similar events in future,

• Ctrl+Alt+F1
• login
• sudo reboot
  seems the safer/easier way to go

again thx

[keellambert]

PS. the PC with the tv-tuner, has two monitors working as one desktop,

Graphics:  Card: Advanced Micro Devices [AMD/ATI] RS780 [Radeon HD 3200]
           Display Server: X.Org 1.17.1 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1680x1050@59.95hz, 1920x1080@60.00hz
           GLX Renderer: Gallium 0.4 on AMD RS780
           GLX Version: 3.0 Mesa 10.5.7 Direct Rendering: Yes

[wolfi323]

@keellambert

you beat me to it, it looks as though a fix is in the pipeline, thx

Yes, the fix has been submitted meanwhile, and will be in Frameworks 5.13, to be released next Thursday.
It has been added to the openSUSE packages in KDE:Frameworks5 too already, the fixed package is in Tumbleweed review/testing at the moment.

You can install libKF5WindowSystem5 from KDE:Frameworks5 to get the fix immediately.

but lots of frame functionality was lost,
restarting kwin_x11 just messed up the desktop

Should not happen.
But you have to quit tvtime first, otherwise kwin will crash again immediately, which will “break” the desktop.

[keellambert]

hi,

@wolfi323

You can install libKF5WindowSystem5 from KDE:Frameworks5 to get the fix immediately.

as of <15Aug01-10:48> the only file located was from http://www.webmail.mirror.yandex.ru/opensuse/repositories/KDE%3A/Unstable%3A/Frameworks/openSUSE_13.2/x86_64/libKF5WindowSystem5-5.13.0git.20150731T172005~6910233-7.1.x86_64.rpm

trying to install from this repos produced the following response

nothing provides libQt5Core.so.5(Qt_5)(64bit) needed by libKF5WindowSystem5-5.13.0git.20150731T172005~6910233-7.1.x86_64

so will wait till Thursday

@wolfi323

But you have to quit tvtime first, otherwise kwin will crash again immediately, which will “break” the desktop.

yes this worked

cheers

[wolfi323]

@keellambert

as of <15Aug01-10:48> the only file located was from http://www.webmail.mirror.yandex.ru/opensuse/repositories/KDE%3A/Unstable%3A/Frameworks/openSUSE_13.2/x86_64/libKF5WindowSystem5-5.13.0git.20150731T172005~6910233-7.1.x86_64.rpm

That’s an unstable development snapshot. As you can see from the URL it comes from the KDE:Unstable:Frameworks repo.
You cannot install that alongside the stable 5.12 packages, and it even requires Qt 5.5 already as you see in the error you posted.

Again, a stable 5.12 package with the fix is available from KDE:Frameworks5, the devel repo for Factory/Tumbleweed:
http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Factory/

so will wait till Thursday

Well, 5.13 will not be available in Tumbleweed on Thursday. It will have to go through review and testing first, which might take a few weeks in the worst case.

[keellambert]

fwiw

with libKF5WindowSystem5-5.12.0-70.1.x86_64 installed tvtime appears to work ok now.

output was as follows for a short session

A780GM-m1<15Aug01-19:17><~/Updates/13.2/packets/2015-07>.. tvtime &                                                                                                               
[1] 1763
A780GM-m1<15Aug01-19:17><~/Updates/13.2/packets/2015-07>.. Running tvtime 1.0.2.
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /home/michael/.tvtime/tvtime.xml
/home/michael/.tvtime/tvtime.xml:1: parser error : Document is empty

^
/home/michael/.tvtime/tvtime.xml:1: parser error : Start tag expected, '<' not found

^
Error parsing configuration file /home/michael/.tvtime/tvtime.xml.
/home/michael/.tvtime/tvtime.xml:1: parser error : Document is empty

^
/home/michael/.tvtime/tvtime.xml:1: parser error : Start tag expected, '<' not found

^
Config file cannot be parsed. Settings will not be saved.
mixer: Can't open device /dev/mixer, mixer volume and mute unavailable.
Thank you for using tvtime.
^C
[1]+  Done                    tvtime
A780GM-m1<15Aug01-19:20><~/Updates/13.2/packets/2015-07>.. 

however it breaks the video/teletext service, imbedded text in video stream,
using mtt to access it

if tvtime is not running and qv4l2 is used to setup the video input all is ok

cheers

[wolfi323]

@keellambert

with libKF5WindowSystem5-5.12.0-70.1.x86_64 installed tvtime appears to work ok now.

I know, I did test it…

The rest is definitely completely unrelated to Plasma5 though.

Reading configuration from /etc/tvtime/tvtime.xmlReading configuration from /home/michael/.tvtime/tvtime.xml
/home/michael/.tvtime/tvtime.xml:1: parser error : Document is empty

^
/home/michael/.tvtime/tvtime.xml:1: parser error : Start tag expected, ‘<’ not found

^
Error parsing configuration file /home/michael/.tvtime/tvtime.xml.
/home/michael/.tvtime/tvtime.xml:1: parser error : Document is empty

^
/home/michael/.tvtime/tvtime.xml:1: parser error : Start tag expected, ‘<’ not found

^
Config file cannot be parsed. Settings will not be saved.

Your config file seems to be empty, tvtime doesn’t like that.
Removing ~/.tvtime/tvtime.xml should fix that.

mixer: Can’t open device /dev/mixer, mixer volume and mute unavailable.

I see that too. Apparently tvtime only supports an OSS mixer (/dev/mixer).
Loading the snd-oss-mixer kernel module (with modprobe) should fix that, but I don’t whether that will work with PulseAudio (I have it disabled here).

however it breaks the video/teletext service, imbedded text in video stream,
using mtt to access it

Works fine here, with both alevt or mtt.

[wolfi323]

@wolfi323

I see that too. Apparently tvtime only supports an OSS mixer (/dev/mixer).
Loading the snd-oss-mixer kernel module (with modprobe) should fix that, but I don’t whether that will work with PulseAudio (I have it disabled here).

Sorry, typo.
The kernel module is named snd-mixer-oss.

sudo modprobe snd-mixer-oss

If it helps, you can load it automatically on boot by setting LOAD_OSS_EMUL_MODULES=“yes” in /etc/sysconfig/sound (the line should be in there already but set to “no”).
At least that worked in earlier versions, I don’t know if that’s still supported in current Tumbleweed.

[keellambert]

hi wolfi323,

@wolfi323

)

Your config file seems to be empty, tvtime doesn’t like that.
Removing ~/.tvtime/tvtime.xml should fix that.

after de/re-installing tvtime via yast noticed the file

-rw-r–r-- 1 michael users 0 Aug 2 11:58 tvtime.xml

after copying the file from a backup to

-rw-r–r-- 1 michael users 980 Aug 2 11:58 tvtime.xml

(not sure why or when this change occured)

but now all functionality has been restored to both tvtime and mtt

sorry for the distraction

@wolfi323

)

I see that too. Apparently tvtime only supports an OSS mixer (/dev/mixer).
Loading the snd-oss-mixer kernel module (with modprobe) should fix that, but I don’t whether that will work with PulseAudio (I have it disabled here).

the tv-card is only used as a video input card connected to a satellite
receivers. audio output is taken directly to an amp/hdmi so this point went un-noticed

cheers

[wolfi323]

@keellambert

after de/re-installing tvtime via yast noticed the file

-rw-r–r-- 1 michael users 0 Aug 2 11:58 tvtime.xml

after copying the file from a backup to

-rw-r–r-- 1 michael users 980 Aug 2 11:58 tvtime.xml

Yeah, as mentioned just deleting it would have helped as well.
tvtime would have recreated it with the default settings on the next start.
(you would have lost all settings of course, but the channels should have been kept as they are stored in stationlist.xml)

(not sure why or when this change occured)

Well, probably your hard shutdown(s) truncated the file.
tvtime does write to the file, if the filesystem is not properly unmounted, changes might not have been actually written (or written incompletely) to disk.

the tv-card is only used as a video input card connected to a satellite
receivers. audio output is taken directly to an amp/hdmi so this point went un-noticed

Ok, then tvtime’s volume control doesn’t matter anyway I suppose…