[ksysguard] [Bug 414036] ksgrd_network_helper uses a lot of CPU on high network load
https://bugs.kde.org/show_bug.cgi?id=414036 --- Comment #14 from José JORGE --- (In reply to iamashwin99 from comment #12) > Can someone find out if this works for them? This can't be the solution : the CPU load happens when a lot of small packets are travelling in the network, and ksysguard looks inside them to know which program is using them. The fact that chromium network service generates more packets when running is only a side effect. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 420177] keyboard is qwerty
https://bugs.kde.org/show_bug.cgi?id=420177 José JORGE changed: What|Removed |Added Platform|Other |Mageia RPMs CC||lists.jjo...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 420177] New: keyboard is qwerty
https://bugs.kde.org/show_bug.cgi?id=420177 Bug ID: 420177 Summary: keyboard is qwerty Product: krdc Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: VNC Assignee: uwol...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- SUMMARY When I connect to a system running Krfb, the keyboard is qwerty, while both systems are azerty. STEPS TO REPRODUCE 1. Configure 2 systems with french keyboard. 2. Launch Krfb in the first one 3. Launch Krdc in the second one and connect OBSERVED RESULT Typing 'a' gives 'q'. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 414036] ksgrd_network_helper uses a lot of CPU on high network load
https://bugs.kde.org/show_bug.cgi?id=414036 --- Comment #3 from José JORGE --- (In reply to Jan Przybylak from comment #2) > After some testing it seems to me that this is caused by having the columns > "Upload" and/or "Download" activated in the list of all processes. I removed > these columns and ksgrd_network_helper disappered entirely. YEs, this bug is against the new helper for this two columns. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 414036] New: ksgrd_network_helper uses a lot of CPU on high network load
https://bugs.kde.org/show_bug.cgi?id=414036 Bug ID: 414036 Summary: ksgrd_network_helper uses a lot of CPU on high network load Product: ksysguard Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- Created attachment 123844 --> https://bugs.kde.org/attachment.cgi?id=123844=edit helper launched with --stats show more than 500 packets per second New helper for ksysguard shows very high CPU usage when it processes a lot of packets STEPS TO REPRODUCE 1. launch ksysguard in the first tab 2. wget http://ftp.free.fr/mirrors/mageia.org/iso/7.1/Mageia-7.1-i586/Mageia-7.1-i586.iso 3. watch CPU usage OBSERVED RESULT Very high usage EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 285544] Per-application network monitoring similar to IO Read/Write columns
https://bugs.kde.org/show_bug.cgi?id=285544 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from José JORGE --- This was implemented with ksysguard 5.17.2, thanks to Jan Kusanagi -- You are receiving this mail because: You are watching all bug changes.
[kblocks] [Bug 406272] kblocks does not play the theme sounds
https://bugs.kde.org/show_bug.cgi?id=406272 --- Comment #2 from José JORGE --- (In reply to Albert Astals Cid from comment #1) > Yeah by looking at the existing themes it seems like at some point the sound > files where customizable (or at least that was the plan), but looking at the > code it isn't, it just plays the three hardcoded files in the code. Thanks for the bootstrap : I did that crazy thing which is trying to contribute my first code to KDE, while I use it since 1998 ;-) D21472 and D21477 in Phabricator waiting to be reviewed. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 407116] Identity : Username is required to reset password
https://bugs.kde.org/show_bug.cgi?id=407116 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 407116] New: Identity : Username is required to reset password
https://bugs.kde.org/show_bug.cgi?id=407116 Bug ID: 407116 Summary: Identity : Username is required to reset password Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- This is a bug about the website https://identity.kde.org/index.php?r=registration/index I have created a user account years ago. Now I come back, and do not remember the username or the password. Only the email. It should be possible to reset password only with the email. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kblocks] [Bug 406272] New: kblocks does not play the theme sounds
https://bugs.kde.org/show_bug.cgi?id=406272 Bug ID: 406272 Summary: kblocks does not play the theme sounds Product: kblocks Version: unspecified Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: squall.leonhart@gmail.com Reporter: lists.jjo...@free.fr CC: kde-games-b...@kde.org Target Milestone: --- I have created an Europe theme for kblocks, and added it to opendesktop.org so that it can be installed from kblocks theme configuration. Unfortunately, the modified sounds are not played, it still plays the defaults sounds. HOW TO REPRODUCE - open kblocks - config -> theme -> get more theme - install europe theme - select it - play, listen the sounds Compare to the sound you hear with : vlc ~/.local/share/kblocks/themes/europe/*ogg -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 405508] powerdevil is not clever when the battery is very big
https://bugs.kde.org/show_bug.cgi?id=405508 --- Comment #5 from José JORGE --- (In reply to Kai Uwe Broulik from comment #4) > So, percent doesn't work for large batteries, Watt-hours is "unfriendly", > remaining time is unreliable and constantly changing... Maybe a solution would be to allow to write manually a smaller number : - keep the scroll with mouse for 1% steps - allow to write manually a 0.1% value? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 405508] powerdevil is not clever when the battery is very big
https://bugs.kde.org/show_bug.cgi?id=405508 --- Comment #3 from José JORGE --- (In reply to Nate Graham from comment #2) > Not sure that would be very user-friendly, at least not for the common case. > Most people don't think of their battery's remaining charge in watt-hours. Yes, it is not user friendly. And I have an old Asus EeePC 901 which only reports it's charge in percentage steps, nothing else appears in upower. Another idea could be the way percentage are rounded : for me, it is fine to keep current way, but the 0% battery level should not happen when we have 0.9%, but a real 0%? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 405508] New: powerdevil is not clever when the battery is very big
https://bugs.kde.org/show_bug.cgi?id=405508 Bug ID: 405508 Summary: powerdevil is not clever when the battery is very big Product: Powerdevil Version: 5.15.1 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- SUMMARY I have a laptop with a secondary big battery : it gives me more than 50 hours usable time. As I can only configure critical level to 0%, it happens when I still have 2 hours of battery remaining. Maybe powerdevil could ignore the percentage as long as upower indicates more than 15 minutes remaining? ADDITIONAL INFORMATION Here is my upower with the big battery empty, and the internal one almost full. Note the percentage lower than 5% while I still have 3,6 hours. [jose@burro tc]$ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: sáb 16 mar 2019 07:15:54 CET (391 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Hewlett-Packard model:Primary serial: 02908 2010/10/14 power supply: yes updated: sáb 16 mar 2019 07:22:03 CET (22 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 44,1891 Wh energy-empty:0 Wh energy-full: 44,8884 Wh energy-full-design: 44,3889 Wh energy-rate: 12,2433 W voltage: 12,432 V time to empty: 3,6 hours percentage: 98% capacity:100% technology: lithium-ion icon-name: 'battery-full-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT1 native-path: BAT1 vendor: Hewlett-Packard model:Travel serial: 09255 2010/05/23 power supply: yes updated: sáb 16 mar 2019 07:22:01 CET (24 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: action energy: 0 Wh energy-empty:0 Wh energy-full: 964,161 Wh energy-full-design: 0,0148 Wh energy-rate: 0 W voltage: 13,289 V percentage: 0% capacity:100% technology: lithium-ion icon-name: 'battery-caution-symbolic' History (charge): 1552717237 0,000 discharging History (rate): 1552717237 0,000 discharging Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: sáb 16 mar 2019 07:20:37 CET (108 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: low energy: 44,1891 Wh energy-full: 1009,05 Wh energy-rate: 12,2433 W time to empty: 3,6 hours percentage: 4,37928% icon-name: 'battery-caution-symbolic' Daemon: daemon-version: 0.99.9 on-battery: yes lid-is-closed: no lid-is-present: yes critical-action: HybridSleep -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403760] New: Don't suspend system on button event if the screen is in DPMS mode
https://bugs.kde.org/show_bug.cgi?id=403760 Bug ID: 403760 Summary: Don't suspend system on button event if the screen is in DPMS mode Product: Powerdevil Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- If a user configures the power button to suspend the system, it works as expected. But there is a use case where it should not : when the screen is black. An average user press the power button when the screen is black to poweron the system. In this case it suspends the system. Windows systems only awake the screen in this case, which seems more ergonomic. STEPS TO REPRODUCE 1. Configure suspend to RAM when power button is used. 2. Put the screen in energy save (ex. "xset dpms force off") 3. Press the power button OBSERVED RESULT The system awakes the monitor and suspends. EXPECTED RESULT The system only awakes the monitor. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392703] crash importing directly from firefox, no crash importing from file menu
https://bugs.kde.org/show_bug.cgi?id=392703 José JORGE changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #7 from José JORGE --- (In reply to Thomas Baumgart from comment #6) > Does this still happen with newer versions of the project? You might want to > try a recent AppImage file if your distro does not have a newer version > available. Fixed with 5.0.2 version in my Mageia distro, thanks. -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 401318] Shift-Tab segfaults
https://bugs.kde.org/show_bug.cgi?id=401318 --- Comment #1 from José JORGE --- It shows version 4.0, which is not in the version list here. -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 401318] Shift-Tab segfaults
https://bugs.kde.org/show_bug.cgi?id=401318 José JORGE changed: What|Removed |Added Version|unspecified |3.0 Platform|Other |Mageia RPMs -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 401318] New: Shift-Tab segfaults
https://bugs.kde.org/show_bug.cgi?id=401318 Bug ID: 401318 Summary: Shift-Tab segfaults Product: katomic Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dim...@gmail.com Reporter: lists.jjo...@free.fr CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Shift-Tab segfaults STEPS TO REPRODUCE 1. Launch 2. Press Shift +Tab 3. Erreur de segmentation (core dumped) Mageia 6 KDE Frameworks 5.42.0 Qt 5.9.4 (construit sur 5.9.3) Le système de fenêtres xcb EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 196558] KTurtle Crash when opening new sample while other sample was running
https://bugs.kde.org/show_bug.cgi?id=196558 José JORGE changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #3 from José JORGE --- Was this code reworked? Or maybe this is related to bug 270031? -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 270031] Kturtle crashes sometimes when lauching a script
https://bugs.kde.org/show_bug.cgi?id=270031 José JORGE changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #7 from José JORGE --- Still reproductible :open in khotnewstuff 2 scripts, it always crash with "Hole or summit" opened in second place. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392703] crash importing directly from firefox, no crash importing from file menu
https://bugs.kde.org/show_bug.cgi?id=392703 --- Comment #4 from José JORGE <lists.jjo...@free.fr> --- Created attachment 111840 --> https://bugs.kde.org/attachment.cgi?id=111840=edit anonymised ofx file that triggers the bug I can trigger the bug opening this file with xdg-open -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384764] Proxy clips on time line play slower than original clips
https://bugs.kde.org/show_bug.cgi?id=384764 José JORGE <lists.jjo...@free.fr> changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #9 from José JORGE <lists.jjo...@free.fr> --- (In reply to mikko.rapeli from comment #8) > And that's why proxy clips are slower to play than originals, though the > different code does impact too. h264 original is tougher to decode than > mpeg2video proxy. I've just upgraded my Kdenlive from 16.x to 17.12.2 and I can see the same bug : the proxy clip is used when playing the single clip, but not used anymore when the clip is in the timeline. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378832] use of vaapi in transcoding and rendering
https://bugs.kde.org/show_bug.cgi?id=378832 --- Comment #7 from José JORGE <lists.jjo...@free.fr> --- (In reply to Anton Gubarkov from comment #6) > I use the following line for decode with subsequent encode to DNxHD > Thanks, I was able to get fast proxy file with this setting. Now I have another problem : the proxy clip is used when reading directly the clip, but is not used anymore when the clip is in the timeline. I think I will open a bug report about that. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392703] crash importing directly from firefox, no crash importing from file menu
https://bugs.kde.org/show_bug.cgi?id=392703 --- Comment #2 from José JORGE <lists.jjo...@free.fr> --- (In reply to Thomas Baumgart from comment #1) > Can you provide a sample file (without personal data) that causes the crash > to happen? Also, can you provide a backtrace of the crash? I think the file is not the problem, as I have no segfault if I open it from the file import menu... Well, it did not segfault when I tried to xdg-open the ofxfile under gdb the first 2 tries, but the third segfaulted : (gdb) backtrace #0 0x719002f4 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #1 0x718040b1 in QIODevice::channelReadyRead(int) () from /lib64/libQt5Core.so.5 #2 0x71c8525c in QAbstractSocketPrivate::canReadNotification() () from /lib64/libQt5Network.so.5 #3 0x71c94fc1 in QReadNotifier::event(QEvent*) () from /lib64/libQt5Network.so.5 #4 0x723b951c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #5 0x723c09c7 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #6 0x718d5c68 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x719293cd in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #8 0x7fffe7867ac7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #9 0x7fffe7867cf8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #10 0x7fffe7867d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #11 0x71928776 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #12 0x718d3e0a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #13 0x718dc9c8 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #14 0x00471182 in runKMyMoney(QApplication&, std::unique_ptr<QSplashScreen, std::default_delete >, QUrl const&, bool) () #15 0x0046fc5e in main () Is this enough? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392703] New: crash importing directly from firefox, no crash importing from file menu
https://bugs.kde.org/show_bug.cgi?id=392703 Bug ID: 392703 Summary: crash importing directly from firefox, no crash importing from file menu Product: kmymoney Version: 5.0.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: lists.jjo...@free.fr Target Milestone: --- I have associated kmymoney with ofx files in firefox. With version 4.x I had no problem with this. Now with kmymoney 5.0.1, it crashes at the end of the import, after the resume screen saying import was done with success. If instead I open the ofx file from the menu import ofx, I get no crash. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378832] use of vaapi in transcoding and rendering
https://bugs.kde.org/show_bug.cgi?id=378832 José JORGE <lists.jjo...@free.fr> changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #5 from José JORGE <lists.jjo...@free.fr> --- (In reply to Anton Gubarkov from comment #4) > I was able to patch manually. I confirm this is working for me. Thanks a lot! Can you please paste the proxy clip line you are using. I got no success with adding "-vaapi_device /dev/dri/renderD128 -hwaccel vaapi -hwaccel_output_format vaapi -i" before the existing parameters in default MPEG2 proxy clips. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378190] Xdebug support for PHP debugging (port from kdelibs/Qt4 -> KF5/Qt5)
https://bugs.kde.org/show_bug.cgi?id=378190 --- Comment #2 from José JORGE <lists.jjo...@free.fr> --- It is a pity no one with C++ skills needs this one... I just discovered upgrading from Mageia 5 to 6 that I have lost Kdevelop PHP debug... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378190] Xdebug support for PHP debugging (port from kdelibs/Qt4 -> KF5/Qt5)
https://bugs.kde.org/show_bug.cgi?id=378190 José JORGE <lists.jjo...@free.fr> changed: What|Removed |Added CC||lists.jjo...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #46 from José JORGE <lists.jjo...@free.fr> --- Yes a big thanks for all, it was beyond my abilities... For an end user, is there an idea when an official release will bring this fix? -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #21 from José JORGE <lists.jjo...@free.fr> --- (In reply to Mauro Carvalho Chehab from comment #18) > Bug #371579 was fixed upstream. Could you please test if this solved the > issue for you? Issue not solved as of today's GIT. I could get one time kaffeine to only use ~25% CPU after lots of play/stop on DVB. But 99% of the time, CPU is at 125% (dual-core system) when playing, and at 100% when playback is stopped. Any hint on how to dump tasks load welcome... -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #19 from José JORGE <lists.jjo...@free.fr> --- (In reply to Mauro Carvalho Chehab from comment #18) > Bug #371579 was fixed upstream. Could you please test if this solved the > issue for you? Thanks, but I suppose I have to checkout form git? Or can I try a tarball? -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 371909] No image or sound on TNT
https://bugs.kde.org/show_bug.cgi?id=371909 José JORGE <lists.jjo...@free.fr> changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #6 from José JORGE <lists.jjo...@free.fr> --- Looks like this bug could be closed. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 358045] Kdialog display nothing with --progressbar
https://bugs.kde.org/show_bug.cgi?id=358045 José JORGE <lists.jjo...@free.fr> changed: What|Removed |Added CC||lists.jjo...@free.fr --- Comment #3 from José JORGE <lists.jjo...@free.fr> --- I can confirm this is a recent bug, as for Plasma 5.8.0 it did work. I observe it with Mageia Cauldron for at most one month. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #17 from José JORGE <lists.jjo...@free.fr> --- (In reply to Mauro Carvalho Chehab from comment #16) > If any of this task happens as often as the scheduler is called, it will > show 100% CPU usage. It is hard to discover what task is taking more time > without profiling it. One could run a profiler to check what task is > consuming more time, in order to identify the culprit. Any hint on how to profile? Thanks. > > Maybe this could be a reflex of EPG parsing, as reported on this bug: >https://bugs.kde.org/show_bug.cgi?id=371579 I don't think so, as the 100% CPU sometimes stops only by clicking on stop, then play again. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #12 from José JORGE <lists.jjo...@free.fr> --- (In reply to Mauro Carvalho Chehab from comment #11) > option is accepted there. You could try those: > --no-video-title-show -V xcb_glx > or: > --no-video-title-show -V xcb_xv > > and re-start Kaffeine. > > Please test if changing to one of the above will affect the CPU usage. None of those affect the CPU usage. The bug still triggers after watching one channel, either by clicking on stop, or by clicking on another channel. Is there a way to debug the libvlc usage by kaffeine? -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #8 from José JORGE <lists.jjo...@free.fr> --- (In reply to knossos456 from comment #7) > If you dont use virtual adapters, please notice also that kaffeine 2.0x use > vlc as dvb core, and perhaps your version of Vlc is not correct, version > > 2.22 is requested. > This is explained on VLC forum, VDPAU did not work on old VLC versions. I use vlc 2.2.4. It is important to understand that the 100% CPU does not stop if I stop the player. I have to close it. So it seems a Kaffeine interface bug, not a vlc one. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #3 from José JORGE <lists.jjo...@free.fr> --- (In reply to knossos456 from comment #2) > Have you same problem with VLC (because newest Kaffeine is based on VLC > core) ? > For me and ATI 5450, all is OK (VLC and Kaffeine) for VDPAU and ubuntu 16.04 > ( under 3% cpu usage > Please post your graphical card model It is an ATI HD3200 (R600 GPU integrated in the motherbord). I have no problems when using directly VLC. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] New: kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 Bug ID: 368907 Summary: kaffeine sometimes uses 100% CPU Product: kaffeine Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mchehab+...@kernel.org Reporter: lists.jjo...@free.fr I use kaffeine for DVB-T, and it uses nicely VDPAU, as the CPU used is less than 20% like other players with VDPAU. But sometimes, it starts using 100% CPU, and then it keeps at this level even when channels are stopped. This happens sometimes directly when I start playing the first channel, or when changing the channel. It never starts happening when simply playing a channel. I tried to run with debug log (-d), but I saw nothing different with between sessions with this bug or without. Reproducible: Sometimes Steps to Reproduce: 1. play dvb-t 2. it is in the french TNT system Actual Results: 100% CPU Expected Results: At least the CPU should not be used if I stop playing/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365091] hotkeys daemon start at login button does nothing
https://bugs.kde.org/show_bug.cgi?id=365091 --- Comment #1 from José JORGE <lists.jjo...@free.fr> --- Created attachment 99853 --> https://bugs.kde.org/attachment.cgi?id=99853=edit screenshot of the bug It is in french... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365091] New: hotkeys daemon start at login button does nothing
https://bugs.kde.org/show_bug.cgi?id=365091 Bug ID: 365091 Summary: hotkeys daemon start at login button does nothing Product: systemsettings Version: 5.6.5 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: lists.jjo...@free.fr In systemsettings, whether I check or uncheck in personalized shortcuts->launch daemon at session start the apply button is not activated. I join a screenshot to better explain, the buggy button has a yellow circle. Reproducible: Always Steps to Reproduce: 1.systemsettings 2.shortcuts 3.personalized 4.activate daemon Actual Results: the button toggles checked unchecked, but I can't save Expected Results: apply button activated to save the change -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364959] I wish Kaffeine could use VAAPI and VDPAU hardware decoding for h264 streams
https://bugs.kde.org/show_bug.cgi?id=364959 José JORGE <jjo...@free.fr> changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED --- Comment #3 from José JORGE <jjo...@free.fr> --- (In reply to Mauro Carvalho Chehab from comment #2) > When image is paused, there won't be any mpeg decoding. Instead, it will be Sorry, bad english. I meant most of the frames are lost, so I see only one image every second. I know CPU usage is not the good indicator, and am also getting terminal info to ensure it works. For the message "libvdpau_va_gl.so: cannot open shared object file: No such file or directory" I see it when trying to use VDPAU on intel hardware, without the translation layer libvdpau_va_gl. I just see VAAPI use is not automatic with vlc 2.2.4 : no message if I leave the setting at auto. It works only with --avcodec-hw vaapi parameter : vlc --avcodec-hw vaapi Vidéos/bbb/bbb_sunflower_1080p_30fps_normal.mp4 VLC media player 2.2.4 Weatherwax (revision 2.2.3-37-g888b7e89) [020ee118] core libvlc: Lancement de vlc avec l'interface par défaut. Utilisez « cvlc » pour démarrer VLC sans interface. [021e8c88] qt4 interface error: Unable to load extensions module libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_36 libva info: va_openDriver() returns 0 [7f0c34d222c8] avcodec decoder: Using Intel i965 driver for Intel(R) Haswell Desktop - 1.4.1 for hardware decoding. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364959] New: I wish Kaffeine could use VAAPI and VDPAU hardware decoding for h264 streams
https://bugs.kde.org/show_bug.cgi?id=364959 Bug ID: 364959 Summary: I wish Kaffeine could use VAAPI and VDPAU hardware decoding for h264 streams Product: kaffeine Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: mchehab+...@kernel.org Reporter: jjo...@free.fr The bug #192490 says VDPAU works from 1.0.2 version, but it seems it was lost going to 2.x versions... as I could not find any option for that, and CPU use at 100% with image pauses shows that it is not used. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 364387] kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so
https://bugs.kde.org/show_bug.cgi?id=364387 --- Comment #9 from José JORGE <jjo...@free.fr> --- (In reply to Christian David from comment #8) > libkmm_payeeidentifier.so should be build and installed by KMyMoney. It > works on my system and KDE's CI (there are several tests which depend on > kmm_payeeidentifier). Thank you, now I think I found the problem : the file is not built as libkmm_payeeidentifier.so.4.14.21 with a symlink for libkmm_payeeidentifier.so.4 and libkmm_payeeidentifier.so. I am a nuts with libs, but I see all other kmymoney libs built and installed this way, so I suppose something was forgotten in cmake for this lib? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 364387] kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so
https://bugs.kde.org/show_bug.cgi?id=364387 José JORGE <jjo...@free.fr> changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|UNCONFIRMED --- Comment #7 from José JORGE <jjo...@free.fr> --- Sorry to insist, but the build error was not the initial bug here. The libpayee was what this bug is about. I explained it badly, lets restart : kmymoney build installed me this libs : /usr/lib64/libpayeeidentifier_iban_bic.so.4 /usr/lib64/libpayeeidentifier_iban_bic_widgets.so.4.14.5 /usr/lib64/libpayeeidentifier_iban_bic.so.4.14.5 /usr/lib64/libpayeeidentifier_nationalAccount.so.4 /usr/lib64/libpayeeidentifier_iban_bic_widgets.so.4 /usr/lib64/libpayeeidentifier_nationalAccount.so.4.14.5 And it complains about another missing lib : kmymoney: error while loading shared libraries: libkmm_payeeidentifier.so: cannot open shared object file: No such file or directory Should this lib be built by kmymoney? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 364387] kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so
https://bugs.kde.org/show_bug.cgi?id=364387 --- Comment #5 from José JORGE <jjo...@free.fr> --- (In reply to Thomas Baumgart from comment #4) > I can confirm that it builds with -j9 so it does not seem to be a general > parallel build problem, though it could be if run with more cores (how many > do you have?) Yes the build log shows much more cores : 24 ! /usr/bin/make -O -j24 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 364387] kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so
https://bugs.kde.org/show_bug.cgi?id=364387 --- Comment #3 from José JORGE <jjo...@free.fr> --- (In reply to Christian David from comment #2) > > Can you post your cmake call with all manually set variables? Maybe even better : here is the build log from our build system available for some days. It has a build error because of a make -j24 I think, as it builds well with make -j1 http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20160616215849.tmb.duvel.37274/log/kmymoney-4.8.0-1.mga6/build.0.20160616215909.log Please tell me if this is not the information you need. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 364387] kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so
https://bugs.kde.org/show_bug.cgi?id=364387 --- Comment #1 from José JORGE <jjo...@free.fr> --- I wonder where the problem is : cat build/install_manifest.txt | grep kmm_p /usr/lib64/libkmm_payeeidentifier.so /usr/lib64/libkmm_plugin.so.4.14.5 /usr/lib64/libkmm_plugin.so.4 /usr/lib64/libkmm_plugin.so But the first file is not installed! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 364387] New: kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so
https://bugs.kde.org/show_bug.cgi?id=364387 Bug ID: 364387 Summary: kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so Product: kmymoney4 Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: jjo...@free.fr I am packaging kmymoney for Mageia for some years. I am stuck with a naming problem : lib64kmm_mymoney4.so needs libkmm_payeeidentifier.so but the build provides libpayeeidentifier.so . Is there a renaming problem in this libs? Reproducible: Always Steps to Reproduce: At build -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 362923] New: Kdenlive 16.04.1 segfaults when stopping webcam record
https://bugs.kde.org/show_bug.cgi?id=362923 Bug ID: 362923 Summary: Kdenlive 16.04.1 segfaults when stopping webcam record Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jjo...@free.fr Application: kdenlive (16.04.1) Qt Version: 5.6.0 Frameworks Version: 5.21.0 Operating System: Linux 4.6.0-desktop-0.rc6.2.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: 1. open kdenlive 2. record video through USB camera at 640x480 30fps 3. click again in record button to stop the record 4. it segfaults the 3 times I have tried The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f1dd010c800 (LWP 28704))] Thread 8 (Thread 0x7f1d8cac6700 (LWP 28717)): #0 0x7ffe66a94c3f in clock_gettime () #1 0x7f1dc99e2b66 in __GI___clock_gettime (clock_id=1, tp=tp@entry=0x7f1d8cac5b70) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f1dca461926 in qt_clock_gettime (ts=0x7f1d8cac5b70, clock=) at tools/qelapsedtimer_unix.cpp:105 #3 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #5 0x7f1dca5cd379 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7928b90) at kernel/qtimerinfo_unix.cpp:84 #6 0x7f1dca5cd8c5 in QTimerInfoList::timerWait (this=0x7928b90, tm=...) at kernel/qtimerinfo_unix.cpp:381 #7 0x7f1dca5cec3e in timerSourcePrepareHelper (timeout=0x7f1d8cac5c24, src=) at kernel/qeventdispatcher_glib.cpp:126 #8 timerSourcePrepare (source=, timeout=timeout@entry=0x7f1d8cac5c24) at kernel/qeventdispatcher_glib.cpp:159 #9 0x7f1dc68a49dd in g_main_context_prepare (context=context@entry=0x7926930, priority=priority@entry=0x7f1d8cac5ca8) at gmain.c:3442 #10 0x7f1dc68a52e3 in g_main_context_iterate (context=context@entry=0x7926930, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3820 #11 0x7f1dc68a54bc in g_main_context_iteration (context=0x7926930, may_block=may_block@entry=1) at gmain.c:3901 #12 0x7f1dca5cf70b in QEventDispatcherGlib::processEvents (this=0x64e6b70, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #13 0x7f1dca57b08a in QEventLoop::exec (this=this@entry=0x7f1d8cac5dd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #14 0x7f1dca3b597c in QThread::exec (this=) at thread/qthread.cpp:503 #15 0x7f1dca3ba589 in QThreadPrivate::start (arg=0x64d4820) at thread/qthread_unix.cpp:340 #16 0x7f1dc82d565d in start_thread (arg=0x7f1d8cac6700) at pthread_create.c:334 #17 0x7f1dc99d4fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f1d8dac8700 (LWP 28715)): #0 g_mutex_unlock (mutex=0x7f1d8990) at gthread-posix.c:1347 #1 0x7f1dc68a49d0 in g_main_context_prepare (context=context@entry=0x7f1d8990, priority=priority@entry=0x7f1d8dac7ca8) at gmain.c:3440 #2 0x7f1dc68a52e3 in g_main_context_iterate (context=context@entry=0x7f1d8990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3820 #3 0x7f1dc68a54bc in g_main_context_iteration (context=0x7f1d8990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f1dca5cf70b in QEventDispatcherGlib::processEvents (this=0x7f1d88c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f1dca57b08a in QEventLoop::exec (this=this@entry=0x7f1d8dac7dd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f1dca3b597c in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f1dca3ba589 in QThreadPrivate::start (arg=0x50a4dc0) at thread/qthread_unix.cpp:340 #8 0x7f1dc82d565d in start_thread (arg=0x7f1d8dac8700) at pthread_create.c:334 #9 0x7f1dc99d4fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f1d8700 (LWP 28711)): #0 0x7ffe66a94c3f in clock_gettime () #1 0x7f1dc99e2b66 in __GI___clock_gettime (clock_id=1, tp=tp@entry=0x7f1d8fffeb50) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f1dca461926 in qt_clock_gettime (ts=0x7f1d8fffeb50, clock=) at tools/qelapsedtimer_unix.cpp:105 #3 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:156 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:165 #5 0x7f1dca5cd379 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f1d84002ed0) at kernel/qtimerinfo_unix.cpp:84 #6 0x7f1dca5cd8c5 in QTimerInfoList::timerWait (this=0x7f1d84002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:381 #7 0x7f1dca5cec3e in timerSourcePrepareHelper (timeout=0x7f1d8fffec04,
