[audiotube] [Bug 489297] New: Audiotube fails to load playlists
https://bugs.kde.org/show_bug.cgi?id=489297 Bug ID: 489297 Summary: Audiotube fails to load playlists Classification: Applications Product: audiotube Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: aseq...@gmail.com Target Milestone: --- SUMMARY When clicking on a playlist there's always a message saying KeyError: 'thumbnails', and the playlist doesn't load at all (no songs no images) STEPS TO REPRODUCE 1. Search for a playist (I tried this one https://music.youtube.com/playlist?list=PLMOYAXYg65ZDjHq3TrJU-7SKfMkfjMaSh but others did the same) 2. See error 3. Nothing OBSERVED RESULT PLaylist is empty EXPECTED RESULT Playlist should be loaded SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 24.04 KDE Plasma Version: KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION ytmusicapi 1.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469955] Problemes instalación de Kmymoney en Windows 11Pro
https://bugs.kde.org/show_bug.cgi?id=469955 --- Comment #4 from Joan Carles --- Hi Jack (Google Translate) I re-downloaded the windows executable and installed it again. The error continued it was impossible to execute the Kmymoney. Then, from the old computer, I copied the entire Kmymoney folder to a pen and copied it entirely to the Kmymoney installation directory in Windows 11 Pro. And surprise, it ran correctly again, finally being able to open the *.KYM data file. In short, the Win/64 executable *.EXE on 2022-09-09 is missing some component of the program that causes it to fail to run under Windows. Best Regards Joan C. Franch -Missatge original- De: joancfra...@gmail.com Enviat: dijous, 18 de maig de 2023 21:38 Per a: bug-cont...@kde.org Tema: RE: [kmymoney] [Bug 469955] Problemes instalación de Kmymoney en Windows 11Pro Hi Jack (Google Translate) When Kmymoney starts, the presentation screen opens, then it closes and the screen of the advice of the day appears and then it closes and ends here, it does not load. If I try to open the xxx.kmy file by clicking directly on it, the Tip of the Day screen opens and the same thing here doesn't happen anymore, absolutely nothing happens, kmymoney doesn't load. Kmymoney: 5.1.3 Windows 11 Pro Version: 22H2 SO: 22621.702 I wait your answer. Thank you so much Joan C Franch -Missatge original- De: Jack Enviat: dijous, 18 de maig de 2023 18:25 Per a: joancfra...@gmail.com Tema: [kmymoney] [Bug 469955] Problemes instalación de Kmymoney en Windows 11Pro https://bugs.kde.org/show_bug.cgi?id=469955 --- Comment #1 from Jack --- KMyMoney should work fine with Win11. What version are you using, and where did you download it from? (Writing in Spanish is OK - I use Google Translate) Also, do you get any error message, or it just does not start? If you can start the program from a command line, you might see more useful information about what is wrong. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469955] Problemes instalación de Kmymoney en Windows 11Pro
https://bugs.kde.org/show_bug.cgi?id=469955 --- Comment #2 from Joan Carles --- Hi Jack (Google Translate) When Kmymoney starts, the presentation screen opens, then it closes and the screen of the advice of the day appears and then it closes and ends here, it does not load. If I try to open the xxx.kmy file by clicking directly on it, the Tip of the Day screen opens and the same thing here doesn't happen anymore, absolutely nothing happens, kmymoney doesn't load. Kmymoney: 5.1.3 Windows 11 Pro Version: 22H2 SO: 22621.702 I wait your answer. Thank you so much Joan C Franch -Missatge original- De: Jack Enviat: dijous, 18 de maig de 2023 18:25 Per a: joancfra...@gmail.com Tema: [kmymoney] [Bug 469955] Problemes instalación de Kmymoney en Windows 11Pro https://bugs.kde.org/show_bug.cgi?id=469955 --- Comment #1 from Jack --- KMyMoney should work fine with Win11. What version are you using, and where did you download it from? (Writing in Spanish is OK - I use Google Translate) Also, do you get any error message, or it just does not start? If you can start the program from a command line, you might see more useful information about what is wrong. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469955] New: Problemes instalación de Kmymoney en Windows 11Pro
https://bugs.kde.org/show_bug.cgi?id=469955 Bug ID: 469955 Summary: Problemes instalación de Kmymoney en Windows 11Pro Classification: Applications Product: kmymoney Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: joancfra...@gmail.com Target Milestone: --- Buenas tardes. Perdonen que no escriba un inglés ya que no es mi fuerte. Hasta ayer mi Kmymoney funcionaba perfectamente bajo Windows 10 Enterprise pero al actualitzar a Windows 11 Pro éste ha dejado de funcionar. Lo he reinstalado unas 5 veces y sigue igual. Quisiera saber si el problema es mio o bién es un problema de compatibilidad con Win 11. Si es este último caso para cuando una versión o un parche para que funcione en Win 11. Espero su respuesta, gracias y un saludo. Atentament Joan C. Franch -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 464367] New: filelight doen't start
https://bugs.kde.org/show_bug.cgi?id=464367 Bug ID: 464367 Summary: filelight doen't start Classification: Applications Product: filelight Version: 19.12 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: joangilvent...@gmail.com CC: martin.sandsm...@kde.org Target Milestone: --- Created attachment 155345 --> https://bugs.kde.org/attachment.cgi?id=155345=edit gbb bactrace SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. start filelight in terminal 2. qt5ct: using qt5ct plugin 3. qt5ct: D-Bus global menu: no OBSERVED RESULT segmentation fault (core dumped) EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: filelight 19.12.3 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Usnig XFCE Ubuntu version -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 --- Comment #10 from Joan Aluja Oraá --- (In reply to Michail Vourlakos from comment #9) > (In reply to Joan Aluja Oraá from comment #3) > > I've gathered more info about the crash and have attached it. It doesn't > > crash with the default layout, it crashes when I have a System Tray applet > > on my Latte Dock panel and I try to close Steam through the system tray. > > Otherwise, it doesn't crash. > > > > I'm attaching my .latterc configuration as it seems to have relation with my > > configuration of the panel. > > I use OpenSuse TumbleWeed + Latte git version. I can not make Latte crash by > closing Steam from the systray. So I can not reproduce this in my system. If > you use Latte git version, do you still have that issue? Yes, it still crashes even with Latte-dock git version -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 Joan Aluja Oraá changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 --- Comment #7 from Joan Aluja Oraá --- Created attachment 150037 --> https://bugs.kde.org/attachment.cgi?id=150037=edit LatteRC -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 --- Comment #6 from Joan Aluja Oraá --- Created attachment 150036 --> https://bugs.kde.org/attachment.cgi?id=150036=edit QML Interpreter DDD backtrace -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 --- Comment #5 from Joan Aluja Oraá --- Created attachment 150035 --> https://bugs.kde.org/attachment.cgi?id=150035=edit QML Interpreter backtrace -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 --- Comment #4 from Joan Aluja Oraá --- Created attachment 150034 --> https://bugs.kde.org/attachment.cgi?id=150034=edit ddd latte-dock -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 --- Comment #3 from Joan Aluja Oraá --- I've gathered more info about the crash and have attached it. It doesn't crash with the default layout, it crashes when I have a System Tray applet on my Latte Dock panel and I try to close Steam through the system tray. Otherwise, it doesn't crash. I'm attaching my .latterc configuration as it seems to have relation with my configuration of the panel. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455649] New: Latte Dock crashes when closing Steam
https://bugs.kde.org/show_bug.cgi?id=455649 Bug ID: 455649 Summary: Latte Dock crashes when closing Steam Product: lattedock Version: 0.10.8 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: joanalujaor...@gmail.com Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.4 Frameworks Version: 5.95.0 Operating System: Linux 5.18.5-zen1-1-zen x86_64 Windowing System: Wayland Distribution: Artix Linux DrKonqi: 5.25.0 [KCrashBackend] -- Information about the crash: I'm using Artix Linux OpenRC linux-5.18.5-zen, Plasma 5.25 on Wayland, Latte Dock 0.10.8 Latte dock crashes when closing Steam through the context menu in the system tray (Exit Steam button) The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f8f1568f0c4 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f8f156befd0 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f8f156a80ce in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f8f156abaa6 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f8f156b02f1 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7f8f15697e85 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7f8f15698324 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #11 0x7f8f156f02b5 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #12 0x7f8f1574c851 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #13 0x7f8f156fb446 in () at /usr/lib/libQt5Quick.so.5 #14 0x7f8f156ffdc4 in () at /usr/lib/libQt5Quick.so.5 #15 0x7f8f137be36a in () at /usr/lib/libQt5Core.so.5 #16 0x7f8f1323a54d in () at /usr/lib/libc.so.6 #17 0x7f8f132bf874 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f8e8b7fe640 (LWP 2796) "latte-do:gdrv0"): #1 0x7f8f13239920 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f8efe6bd8cc in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f8efe6b705c in () at /usr/lib/dri/radeonsi_dri.so #4 0x7f8f1323a54d in () at /usr/lib/libc.so.6 #5 0x7f8f132bf874 in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f8e8bfff640 (LWP 2795) "latte-do:gdrv0"): #1 0x7f8f13239920 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f8efe6bd8cc in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f8efe6b705c in () at /usr/lib/dri/radeonsi_dri.so #4 0x7f8f1323a54d in () at /usr/lib/libc.so.6 #5 0x7f8f132bf874 in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f8ea8ff9640 (LWP 2787) "latte-dock"): #1 0x7f8f0f264524 in () at /usr/lib/libusbmuxd-2.0.so.6 #2 0x7f8f0f2658a9 in () at /usr/lib/libusbmuxd-2.0.so.6 #3 0x7f8f1323a54d in () at /usr/lib/libc.so.6 #4 0x7f8f132bf874 in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f8ed5dfb640 (LWP 2754) "QQmlThread"): #1 0x7f8f11ec42d3 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f8f11f19e5e in () at /usr/lib/libglib-2.0.so.0 #3 0x7f8f11ec1392 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f8f139b24bf in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f8f139604ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f8f137c126f in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f8f153be420 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f8f137be36a in () at /usr/lib/libQt5Core.so.5 #9 0x7f8f1323a54d in () at /usr/lib/libc.so.6 #10 0x7f8f132bf874 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f8ed67fc640 (LWP 2721) "latte-do:shlo3"): #1 0x7f8f13239920 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f8efe6bd8cc in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f8efe6b705c in () at /usr/lib/dri/radeonsi_dri.so #4 0x7f8f1323a54d in () at /usr/lib/libc.so.6 #5 0x7f8f132bf874 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f8ed6ffd640 (LWP 2720) "latte-do:shlo2"): #1 0x7f8f13239920 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7f8efe6bd8cc in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f8efe6b705c in () at /usr/lib/dri/radeonsi_dri.so #4 0x7f8f1323a54d in () at /usr/lib/libc.so.6 #5 0x7f8f132bf874 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f8ed77fe640 (LWP 2719) "latte-do:shlo1"): #1
[Phonon] [Bug 430198] New: Cannot play mov files through phonon
https://bugs.kde.org/show_bug.cgi?id=430198 Bug ID: 430198 Summary: Cannot play mov files through phonon Product: Phonon Version: 4.11.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aseq...@gmail.com CC: myr...@kde.org, romain.per...@gmail.com, sit...@kde.org Target Milestone: --- Created attachment 133959 --> https://bugs.kde.org/attachment.cgi?id=133959=edit Media information SUMMARY I have a vide in mov format recorded from a Canon DSLR (EOS 550D), that can't be played with phonon (neither gstreamer nor vlc), in both cases when playing the file (with either dragon or gwenview) I only get a black screen with no sound. On the console there are several of these messages: WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::VideoWidget ( no objectName ). STEPS TO REPRODUCE 1. Remove phonon-backend-gstreamer 2. Try to play mov file in any program using phonon 3. Black screen with no sound 4. Install again phonon-backend-gstreamer and remove phonon-backend-vlc 5. Try to play mov file in any program using phonon 6. Black screen with no sound The same file can be played both without problemes with: - gst-launch-1.0 filesrc location=MVI_6781.mov ! queue ! decodebin ! autovideosink - vlc MVI_6781.mov SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Frameworks Version: Frameworks 5.76.0 Qt Version: Qt 5.15.1 Plasma Neon -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 430097] New: Crash when viewing videos
https://bugs.kde.org/show_bug.cgi?id=430097 Bug ID: 430097 Summary: Crash when viewing videos Product: kphotoalbum Version: 5.7.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: aseq...@gmail.com Target Milestone: --- Application: kphotoalbum (5.7.0) Qt Version: 5.15.1 Frameworks Version: 5.76.0 Operating System: Linux 5.4.0-56-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: I opened one of the videos of my collection, kphotoalbum just crashed, there still seem to be issues with the video integration. The crash can be reproduced sometimes. -- Backtrace: Application: KPhotoAlbum (kphotoalbum), signal: Aborted [New LWP 58667] [New LWP 58668] [New LWP 58669] [New LWP 58670] [New LWP 58671] [New LWP 58685] [New LWP 58686] [New LWP 58687] [New LWP 59271] [New LWP 59279] [New LWP 59281] [New LWP 59284] [New LWP 59287] [New LWP 59288] [New LWP 59289] [New LWP 59290] [New LWP 59291] [New LWP 59292] [New LWP 59294] [New LWP 59318] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f69ff30baff in __GI___poll (fds=0x7ffe33504728, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f69ec64d1c0 (LWP 58665))] Thread 21 (Thread 0x7f69357fa700 (LWP 59318)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f69357f92f8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f69357f92a8, cond=0x7f69357f92d0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f69357f92d0, mutex=0x7f69357f92a8) at pthread_cond_wait.c:638 #3 0x7f69f8e4494e in base::ConditionVariable::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x in ?? () Thread 20 (Thread 0x7f6937fff700 (LWP 59294)): #0 0x7f69ff23f0c0 in __GI_getenv (name=0x7f69ff3ad434 "NGUAGE", name@entry=0x7f69ff3ad432 "LANGUAGE") at getenv.c:75 #1 0x7f69ff22f05c in guess_category_value (categoryname=0x7f69ff393493 <_nl_category_names+51> "LC_MESSAGES", category=5) at dcigettext.c:1565 #2 __dcigettext (domainname=0x7f69ff3ad405 <_libc_intl_domainname> "libc", msgid1=0x7f69ff3ad8ac "Bad file descriptor", msgid2=msgid2@entry=0x0, plural=plural@entry=0, n=n@entry=0, category=category@entry=5) at dcigettext.c:647 #3 0x7f69ff22d993 in __GI___dcgettext (domainname=, msgid=, category=category@entry=5) at dcgettext.c:47 #4 0x7f69ff298672 in __GI___strerror_r (errnum=errnum@entry=9, buf=buf@entry=0x0, buflen=buflen@entry=0) at _strerror.c:71 #5 0x7f69ff298593 in strerror (errnum=9) at strerror.c:31 #6 0x7f69f3d3dcf6 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.7 #7 0x7f69f3d3f768 in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.7 #8 0x7f69f3d35625 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.7 #9 0x7f69f8e512b3 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x0100 in ?? () #11 0x7f6930001d19 in ?? () #12 0x7f6930001d18 in ?? () #13 0x7f6937ffe250 in ?? () #14 0x7f6937ffe248 in ?? () #15 0x7f69300027a0 in ?? () #16 0x0008 in ?? () #17 0x01833c76 in ?? () #18 0x0019 in ?? () #19 0x0005c436 in ?? () #20 0x7f6937ffe318 in ?? () #21 0x7f696006b920 in ?? () #22 0x7fff in ?? () #23 0x7f696006b9c8 in ?? () #24 0x7fff in ?? () #25 0x0001 in ?? () #26 0x7f6937ffe2d0 in ?? () #27 0x7f69f8df4f89 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, base::TimeDelta) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #28 0x7f6937ffe318 in ?? () #29 0x7f6937ffe3b0 in ?? () #30 0x7f6937ffe310 in ?? () #31 0x7f6937ffe3b0 in ?? () #32 0x in ?? () Thread 19 (Thread 0x7f696cff9700 (LWP 59292)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f696cff82f8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f696cff82a8, cond=0x7f696cff82d0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f696cff82d0, mutex=0x7f696cff82a8) at pthread_cond_wait.c:638 #3 0x7f69f8e4494e in base::ConditionVariable::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x in ?? () Thread 18 (Thread 0x7f696d7fa700 (LWP 59291)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f696d7f91a8) at ../sysdeps/nptl/futex-internal.h:183 #1
[kphotoalbum] [Bug 427780] Crash when tagging images (not videos)
https://bugs.kde.org/show_bug.cgi?id=427780 --- Comment #4 from Joan --- Hi, I finally find time to organize the pictures again, about your questions (today I haven't experienced any crashes so far) - Job queue is empty (I remember that back in time there where more items in queue and it was blinking all the time) - Maybe the importing queue was finally processed or might be some improvements in video in current Neon version If more errors appear I'll let you know Missatge de Johannes Zarl-Zierl del dia ds., 21 de nov. 2020 a les 1:44: > https://bugs.kde.org/show_bug.cgi?id=427780 > > Johannes Zarl-Zierl changed: > >What|Removed |Added > > > CC||johan...@zarl-zierl.at > > --- Comment #3 from Johannes Zarl-Zierl --- > Hi Joan, > > Thanks for your patience and for keeping the crash reports coming. > > The backtraces all seem related to the video thumbnailer. > > Summarizing your reports so far, it seems that the crashes occur during > random > times and do not seem related to a specific task that you are doing. > > If you start kphotoalbum and take a look at the background job queue > (press the > "LED-like" thing in the status bar) - is it mostly empty? Does it show > failed > jobs (red status). > > Did you try just opening kphotoalbum and not doing anything? Does it crash > after a while? > > Thanks, > Johannes > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 427780] Crash when tagging images (not videos)
https://bugs.kde.org/show_bug.cgi?id=427780 --- Comment #2 from Joan --- Created attachment 133510 --> https://bugs.kde.org/attachment.cgi?id=133510=edit New crash information added by DrKonqi kphotoalbum (5.7.0) using Qt 5.15.1 - What I was doing when the application crashed: After tagging some photos I tried to delete some of them. -- Backtrace (Reduced): #4 0x55c3fb3638d0 in BackgroundJobs::HandleVideoThumbnailRequestJob::sendResult (this=0x55c4078ab780, image=...) at ./BackgroundJobs/HandleVideoThumbnailRequestJob.cpp:106 #5 0x55c3fb363ac7 in BackgroundJobs::HandleVideoThumbnailRequestJob::frameLoaded (this=this@entry=0x55c4078ab780, image=...) at ./BackgroundJobs/HandleVideoThumbnailRequestJob.cpp:72 #6 0x55c3fb1655ad in BackgroundJobs::HandleVideoThumbnailRequestJob::qt_static_metacall (_o=0x55c4078ab780, _c=, _id=, _a=) at ./obj-x86_64-linux-gnu/kphotoalbum_autogen/UHUIEV64BD/moc_HandleVideoThumbnailRequestJob.cpp:73 #7 0x7fea7b28d980 in doActivate (sender=0x55c403206190, signal_index=3, argv=0x7ffc24bb99a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 [...] #9 0x55c3fb15ad56 in ImageManager::ExtractOneVideoFrame::result (this=this@entry=0x55c403206190, _t1=...) at ./obj-x86_64-linux-gnu/kphotoalbum_autogen/NAEE7Z5ID4/moc_ExtractOneVideoFrame.cpp:144 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 427780] Crash when tagging images (not videos)
https://bugs.kde.org/show_bug.cgi?id=427780 Joan changed: What|Removed |Added CC||aseq...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 428701] New: When returning after doing a donation the page gives a 404
https://bugs.kde.org/show_bug.cgi?id=428701 Bug ID: 428701 Summary: When returning after doing a donation the page gives a 404 Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: aseq...@gmail.com Target Milestone: --- I just did a donation to kde using the page at https://kde.org/community/donations/, after confirming the donation I got a 404. I imagine that the confirmation page is where I could customize the donation message. When looking at the page at https://kde.org/community/donations/previousdonations/ it doesn't show any messages customized by the users since August -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 427780] New: Crash when tagging images (not videos)
https://bugs.kde.org/show_bug.cgi?id=427780 Bug ID: 427780 Summary: Crash when tagging images (not videos) Product: kphotoalbum Version: 5.7.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: aseq...@gmail.com Target Milestone: --- Application: kphotoalbum (5.7.0) Qt Version: 5.15.0 Frameworks Version: 5.75.0 Operating System: Linux 5.4.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.20 -- Information about the crash: - What I was doing when the application crashed: I have reported some crashes when browsing videos, this time the crash happened when opening an image qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 9014, resource id: 14680208, major code: 40 (TranslateCoords), minor code: 0 Warning: Directory NikonPreview has an unexpected next pointer; ignored. Warning: Directory NikonPreview, entry 0x0201: Data area exceeds data buffer, ignoring it. Warning: Directory NikonPreview, entry 0x has unknown Exif (TIFF) type 0; setting type size 1. Warning: Directory Minolta, entry 0x0088: Data area exceeds data buffer, ignoring it. Warning: Directory Minolta, entry 0x0088: Data area exceeds data buffer, ignoring it. Warning: Directory Canon has an unexpected next pointer; ignored. Warning: Directory Canon has an unexpected next pointer; ignored. Warning: Directory Canon has an unexpected next pointer; ignored. Warning: Directory Canon has an unexpected next pointer; ignored. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kphotoalbum path = /usr/bin pid = 1905 The crash can be reproduced sometimes. -- Backtrace: Application: KPhotoAlbum (kphotoalbum), signal: Segmentation fault [New LWP 1907] [New LWP 1908] [New LWP 1909] [New LWP 1910] [New LWP 1911] [New LWP 1940] [New LWP 1941] [New LWP 1942] [New LWP 2214] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7ff7aeac1aff in __GI___poll (fds=0x7ffeaee97528, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7ff79bfa4180 (LWP 1905))] Thread 10 (Thread 0x7ff7697fc700 (LWP 2214)): #0 __GI___libc_read (nbytes=10, buf=0x7ff7697fb25e, fd=21) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=21, buf=0x7ff7697fb25e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7ff7a579c955 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7ff7ade85416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7ff7ade85eb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7ff7ade85f70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7ff7ade9411d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7ff7a57cb67c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7ff7ae948609 in start_thread (arg=) at pthread_create.c:477 #9 0x7ff7aeace293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7ff7723fd700 (LWP 1942)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c5d34eeba0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c5d34eeb50, cond=0x55c5d34eeb78) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c5d34eeb78, mutex=0x55c5d34eeb50) at pthread_cond_wait.c:638 #3 0x7ff7aefbf10b in QWaitConditionPrivate::wait (deadline=..., this=0x55c5d34eeb50) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55c5d36af880, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7ff7aefbf1d1 in QWaitCondition::wait (this=this@entry=0x55c5d36af878, mutex=mutex@entry=0x55c5d36af880, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #6 0x55c5cc6e9f5a in ImageManager::AsyncLoader::next (this=0x55c5d36af850) at ./ImageManager/AsyncLoader.cpp:186 #7 0x55c5cc6e9656 in ImageManager::ImageLoaderThread::run (this=0x55c5d3670030) at ./ImageManager/ImageLoaderThread.cpp:59 #8 0x7ff7aefb920c in QThreadPrivate::start (arg=0x55c5d3670030) at thread/qthread_unix.cpp:342 #9 0x7ff7ae948609 in start_thread (arg=) at pthread_create.c:477 #10 0x7ff7aeace293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7ff773fff700 (LWP 1941)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c5d34eeba0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c5d34eeb50, cond=0x55c5d34eeb78) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c5d34eeb78,
[kphotoalbum] [Bug 423811] Crash during kphotoalbum usage
https://bugs.kde.org/show_bug.cgi?id=423811 --- Comment #5 from Joan --- I have been trying kphotoalbum 5.7.0 and I haven't experienced any crash so far. The environment has change because I'm using neon (so packages have been updated) and also the release has been upgraded to release 20.04 (instead of 18.04). For me the ticket could be closed. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 423811] Crash during kphotoalbum usage
https://bugs.kde.org/show_bug.cgi?id=423811 --- Comment #3 from Joan --- > Can you run the demo database, copy this file into the demo database (should > be > directory /tmp/kphotoalbum-demo-jjuvan), search for new images, and > browse to > thumbnail view? Ok up to this point Does this trigger the crash? Does it trigger the crash with the stock version 5.6.1 of kphotoalbum? I could no longer reproduce this crash (at least with this file), my feeling is that two things happened in current neon version: - vlc / ffmpeg received fixes so I can now reproduce the file without issues (in the version from a couple weeks ago it was crashing after starting to reproduce the video) - phonon backend is broken now and I can't reproduce videos neither in 5.6.1 nor v5.6.1-333-g8f858c09 So I guess that the bug might be there, but I can't reproduce it now. What do you suggest? $ WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioOutput ( no objectName ). WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::VideoWidget ( no objectName ). WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 423811] New: Crash during kphotoalbum usage
https://bugs.kde.org/show_bug.cgi?id=423811 Bug ID: 423811 Summary: Crash during kphotoalbum usage Product: kphotoalbum Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: aseq...@gmail.com Target Milestone: --- Application: kphotoalbum (v5.6.1-333-g8f858c09) Qt Version: 5.14.2 Frameworks Version: 5.71.0 Operating System: Linux 5.3.0-61-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: I was scrolling through my list of pictures, the error might be related to the thumbnail creation. Might be related to #412409 but it's not the same bug because I'm using a version after the fix. I'm using commit 8f858c093199c4af8ed82ab59c198a8b472567e4 over a neon system. The crash can be reproduced sometimes. -- Backtrace: Application: KPhotoAlbum (kphotoalbum), signal: Segmentation fault [KCrash Handler] #4 0x562f72834990 in BackgroundJobs::HandleVideoThumbnailRequestJob::sendResult (this=this@entry=0x562f7f2ebed0, image=...) at /home/jjuvan/src/kphotoalbum/BackgroundJobs/HandleVideoThumbnailRequestJob.cpp:106 #5 0x562f72834ba3 in BackgroundJobs::HandleVideoThumbnailRequestJob::frameLoaded (this=this@entry=0x562f7f2ebed0, image=...) at /home/jjuvan/src/kphotoalbum/BackgroundJobs/HandleVideoThumbnailRequestJob.cpp:72 #6 0x562f728572b5 in BackgroundJobs::HandleVideoThumbnailRequestJob::qt_static_metacall (_o=0x562f7f2ebed0, _c=, _id=, _a=) at /home/jjuvan/src/kphotoalbum/build/kphotoalbum_autogen/UHUIEV64BD/moc_HandleVideoThumbnailRequestJob.cpp:73 #7 0x7fe32d6c44b9 in doActivate (sender=0x562f7f024d80, signal_index=3, argv=0x7ffd769816a0) at kernel/qobject.cpp:3882 #8 0x7fe32d6bef92 in QMetaObject::activate (sender=sender@entry=0x562f7f024d80, m=m@entry=0x562f72afaa20 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd769816a0) at kernel/qobject.cpp:3930 #9 0x562f7284d032 in ImageManager::ExtractOneVideoFrame::result (this=this@entry=0x562f7f024d80, _t1=...) at /home/jjuvan/src/kphotoalbum/build/kphotoalbum_autogen/NAEE7Z5ID4/moc_ExtractOneVideoFrame.cpp:144 #10 0x562f72766811 in ImageManager::ExtractOneVideoFrame::frameFetched (this=0x562f7f024d80) at /home/jjuvan/src/kphotoalbum/ImageManager/ExtractOneVideoFrame.cpp:98 #11 0x7fe32d6c46d7 in QtPrivate::QSlotObjectBase::call (a=0x7ffd76981860, r=0x562f7f024d80, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x562f7aa15a10, signal_index=11, argv=0x7ffd76981860) at kernel/qobject.cpp:3870 #13 0x7fe32d6bef92 in QMetaObject::activate (sender=sender@entry=0x562f7aa15a10, m=m@entry=0x7fe32db557c0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd76981860) at kernel/qobject.cpp:3930 #14 0x7fe32d5f7a0f in QProcess::finished (this=this@entry=0x562f7aa15a10, _t1=, _t2=) at .moc/moc_qprocess.cpp:339 #15 0x7fe32d5fe3d2 in QProcessPrivate::_q_processDied (this=0x562f7a979fa0) at io/qprocess.cpp:1184 #16 0x7fe32d5fe4f9 in QProcess::qt_static_metacall (_o=, _c=, _id=, _a=0x7ffd769819e0) at .moc/moc_qprocess.cpp:216 #17 0x7fe32d6c44b9 in doActivate (sender=0x562f7e826930, signal_index=3, argv=0x7ffd769819e0) at kernel/qobject.cpp:3882 #18 0x7fe32d6bef92 in QMetaObject::activate (sender=sender@entry=0x562f7e826930, m=m@entry=0x7fe32db57ba0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd769819e0) at kernel/qobject.cpp:3930 #19 0x7fe32d6c7cb8 in QSocketNotifier::activated (this=this@entry=0x562f7e826930, _t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:141 #20 0x7fe32d6c8072 in QSocketNotifier::event (this=0x562f7e826930, e=0x7ffd76981cb0) at kernel/qsocketnotifier.cpp:266 #21 0x7fe32e5789ac in QApplicationPrivate::notify_helper (this=this@entry=0x562f745f2740, receiver=receiver@entry=0x562f7e826930, e=e@entry=0x7ffd76981cb0) at kernel/qapplication.cpp:3685 #22 0x7fe32e57fbb0 in QApplication::notify (this=0x7ffd76981fb0, receiver=0x562f7e826930, e=0x7ffd76981cb0) at kernel/qapplication.cpp:3431 #23 0x7fe32d6894a8 in QCoreApplication::notifyInternal2 (receiver=0x562f7e826930, event=0x7ffd76981cb0) at kernel/qcoreapplication.cpp:1075 #24 0x7fe32d68967e in QCoreApplication::sendEvent (receiver=, event=event@entry=0x7ffd76981cb0) at kernel/qcoreapplication.cpp:1470 #25 0x7fe32d6e9378 in socketNotifierSourceDispatch (source=0x562f7465b460) at kernel/qeventdispatcher_glib.cpp:107 #26 0x7fe326090417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7fe326090650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7fe3260906dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #29
[kphotoalbum] [Bug 423811] Crash during kphotoalbum usage
https://bugs.kde.org/show_bug.cgi?id=423811 Joan changed: What|Removed |Added Version|unspecified |GIT master -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #15 from Joan --- Hi Johannes, I was waiting for the fix until you say that it wasn't comming yet. I tried compiling and ti works perfectly (I see warnings about thumbnails not being generated, but kphotoalbum is not crashing). On thing only, on the backup part tells us to use kpa-backup.sh, but it doesn't work: $ ~/.local/bin/kpa-backup.sh --backup qtpaths: could not find a Qt installation of '' QStandardPaths command line client (qtpaths) not usable! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 412409] Crash when scrolling photos
https://bugs.kde.org/show_bug.cgi?id=412409 Joan changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Joan --- I'm the reporter for this and the other bug, I can't reproduce it anymore, for the symptoms, the cause seems to be the same *** This bug has been marked as a duplicate of bug 422555 *** -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #9 from Joan --- *** Bug 412409 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #8 from Joan --- Great, I'll check it out when the version is updated. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #5 from Joan --- I just tried with one of the files (see attached the logs of your script), and the errors are the following: cvlc /media/jjuvan/TOSHIBA_FOTOS/Fotos/2019/agost/YDXJ0002.MP4 VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) [55a73b72d800] dummy interface: using the dummy interface module... Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory [7fc2b0d823b0] main decoder error: Timestamp conversion failed for 21354667: no reference clock [7fc2b0d823b0] main decoder error: Could not convert timestamp 0 for faad [7fc2b0cc1ae0] main decoder error: Timestamp conversion failed for 21390701: no reference clock [7fc2b0cc1ae0] main decoder error: Could not convert timestamp 0 for FFmpeg [7fc2b0cc1ae0] main decoder error: buffer deadlock prevented [7fc2b0d823b0] main decoder error: buffer deadlock prevented -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #4 from Joan --- Created attachment 129147 --> https://bugs.kde.org/attachment.cgi?id=129147=edit ffmpeg logs Relevant part of the logs generated with Johannes's script. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #2 from Joan --- It can be at any moment, sometimes I see I when scrolling photos for example, but since it was consistent this time when tagging I thought it was the cause. Might be related to background tasks as you say. If you need any more information I'd be glad to help. Joan El dg., 7 juny 2020, 0.41, Johannes Zarl-Zierl va escriure: > https://bugs.kde.org/show_bug.cgi?id=422555 > > Johannes Zarl-Zierl changed: > >What|Removed |Added > > > CC||johan...@zarl-zierl.at > > --- Comment #1 from Johannes Zarl-Zierl --- > Hello Joan, > > Thanks for the bug report! > > The backtrace seems to indicate a problem with video thumbnail generation. > Does the crash also happen if you simply wait (without tagging any images)? > > Johannes > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 422556] Neon should be detected by drkonqui as the platform
https://bugs.kde.org/show_bug.cgi?id=422556 Joan changed: What|Removed |Added CC||aseq...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 422556] New: Neon should be detected by drkonqui as the platform
https://bugs.kde.org/show_bug.cgi?id=422556 Bug ID: 422556 Summary: Neon should be detected by drkonqui as the platform Product: drkonqi Version: 5.18.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aseq...@gmail.com Target Milestone: --- SUMMARY Many of the testers reporting bugs on most fresh packages are using neon as their system. After reporting any bug via drkonqui, one has to got on the website to edit the platform and modify it accordingly. STEPS TO REPRODUCE 1. Report a bug via drkonqui OBSERVED RESULT Bug is reported without platform EXPECTED RESULT Platform should be shown as "Neon Packages" Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-53-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i7-3517U CPU @ 1.90GHz Memory: 7,6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 Joan changed: What|Removed |Added Platform|unspecified |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] New: Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 Bug ID: 422555 Summary: Crash when tagging images in kphotoalbum Product: kphotoalbum Version: 5.6.1 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: aseq...@gmail.com Target Milestone: --- Application: kphotoalbum (5.6.1) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-53-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I was tagging multiple pictures in kophotoalbum, I can consistently trigger the bug. I've been tagging pictures before without the same issue, but I can consistently reproduce it now. The crash can be reproduced every time. -- Backtrace: Application: KPhotoAlbum (kphotoalbum), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f26bcafdc00 (LWP 21854))] Thread 6 (Thread 0x7f2666bfe700 (LWP 21862)): #0 0x7f26b5d539f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557edf7b63f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x557edf7b63a0, cond=0x557edf7b63c8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x557edf7b63c8, mutex=0x557edf7b63a0) at pthread_cond_wait.c:655 #3 0x7f26b719d1db in QWaitConditionPrivate::wait (deadline=..., this=0x557edf7b63a0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x557edf7b8b20, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f26b719d359 in QWaitCondition::wait (this=this@entry=0x557edf7b8b18, mutex=mutex@entry=0x557edf7b8b20, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x557ed9f42732 in ImageManager::AsyncLoader::next (this=0x557edf7b8af0) at ./ImageManager/AsyncLoader.cpp:180 #7 0x557ed9f42294 in ImageManager::ImageLoaderThread::run (this=0x557edf7b0fb0) at ./ImageManager/ImageLoaderThread.cpp:69 #8 0x7f26b7196c2c in QThreadPrivate::start (arg=0x557edf7b0fb0) at thread/qthread_unix.cpp:342 #9 0x7f26b5d4d6db in start_thread (arg=0x7f2666bfe700) at pthread_create.c:463 #10 0x7f26b64d588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f266cffc700 (LWP 21861)): #0 0x7f26b5d539f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557edf7b63f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x557edf7b63a0, cond=0x557edf7b63c8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x557edf7b63c8, mutex=0x557edf7b63a0) at pthread_cond_wait.c:655 #3 0x7f26b719d1db in QWaitConditionPrivate::wait (deadline=..., this=0x557edf7b63a0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x557edf7b8b20, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f26b719d359 in QWaitCondition::wait (this=this@entry=0x557edf7b8b18, mutex=mutex@entry=0x557edf7b8b20, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x557ed9f42732 in ImageManager::AsyncLoader::next (this=0x557edf7b8af0) at ./ImageManager/AsyncLoader.cpp:180 #7 0x557ed9f42294 in ImageManager::ImageLoaderThread::run (this=0x557edf7b8870) at ./ImageManager/ImageLoaderThread.cpp:69 #8 0x7f26b7196c2c in QThreadPrivate::start (arg=0x557edf7b8870) at thread/qthread_unix.cpp:342 #9 0x7f26b5d4d6db in start_thread (arg=0x7f266cffc700) at pthread_create.c:463 #10 0x7f26b64d588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f266700 (LWP 21860)): #0 0x7f26b5d539f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557edf7b63f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x557edf7b63a0, cond=0x557edf7b63c8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x557edf7b63c8, mutex=0x557edf7b63a0) at pthread_cond_wait.c:655 #3 0x7f26b719d1db in QWaitConditionPrivate::wait (deadline=..., this=0x557edf7b63a0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x557edf7b8b20, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f26b719d359 in QWaitCondition::wait (this=this@entry=0x557edf7b8b18, mutex=mutex@entry=0x557edf7b8b20, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x557ed9f42732 in ImageManager::AsyncLoader::next (this=0x557edf7b8af0) at ./ImageManager/AsyncLoader.cpp:180 #7 0x557ed9f42294 in ImageManager::ImageLoaderThread::run (this=0x557edf7b87e0) at ./ImageManager/ImageLoaderThread.cpp:69 #8 0x7f26b7196c2c in
[KBibTeX] [Bug 416647] KBibTex unable to save files on a remote server via sftp
https://bugs.kde.org/show_bug.cgi?id=416647 --- Comment #13 from Joan --- (In reply to Thomas Fischer from comment #12) > I think I found and fixed the problem this time. Please test the latest > incarnation of the code in the 'bugs/kde416647' branch, the commit hash > should be 46e34341514442da9208f367055c135bb9e6d5d9. Sorry, same behavior as before: 1- Save: I get a "Moving file" notification from KDE environment and the ORIGINAL remote file is kept 2- Save As: I get the notification again and a new remote file is created (with a different name) and the contents of the ORIGINAL file 3- Save Copy As: No notification from KDE and a new remote file is created with the contents of the (locally) MODIFIED (in kbibtex) file Please also note that at the end of compilation I got an error (which didn't happen last time): /tmp/root-kbibtex-usr/bin/kbibtex: error while loading shared libraries: libkbibtexprocessing.so.0: cannot open shared object file: No such file or directory I fixed it by adding /tmp/root-kbibtex-build-46be55653125cd1d93901531a3ff131d/bin/ to the dynamic library default path. In doing so, I realized that the commit hash might be (?) 46be55653125cd1d93901531a3ff131d, different from what it should be (46e34341514442da9208f367055c135bb9e6d5d9) according to your message. I executed : bash run-kbibtex.sh https://anongit.kde.org/clones/kbibtex/thomasfischer/kbibtex.git bugs/kde416647 both as normal user and root (same result) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419691] Menu to add language hides after click on plasma neon, language can't be added
https://bugs.kde.org/show_bug.cgi?id=419691 Joan changed: What|Removed |Added CC||aseq...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419691] New: Menu to add language hides after click on plasma neon, language can't be added
https://bugs.kde.org/show_bug.cgi?id=419691 Bug ID: 419691 Summary: Menu to add language hides after click on plasma neon, language can't be added Product: systemsettings Version: 5.18.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_language Assignee: h...@kde.org Reporter: aseq...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 127307 --> https://bugs.kde.org/attachment.cgi?id=127307=edit Menu where language should be choosen SUMMARY On kde neon when I try to add a new language (result is the same for all languages) in the menu at systemsettings -> Personalization -> Languages -> Add Languages STEPS TO REPRODUCE 1. Go to systemsettings -> Personalization -> Languages -> Add Languages 2. Try to pick any of the languages 3. List of languages hides immediately (for a brief moment the Add buttons seems to be clickable) 4. No language can't be added OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-45-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i7-3517U CPU @ 1.90GHz Memory: 7,6 GiB of RAM Graphics: Card: Intel 3rd Gen Core processor Graphics Controller Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1366x768@59.84hz OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile version: 4.2 Mesa 19.2.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 416647] KBibTex unable to save files on a remote server via sftp
https://bugs.kde.org/show_bug.cgi?id=416647 --- Comment #11 from Joan --- (In reply to Thomas Fischer from comment #10) > Can you please test the lastest code? Also, is my summary from comment 9 > correct? > > (In reply to Thomas Fischer from comment #9) > > If I understand it correctly, if you in KBibTeX: > > 1. Open a remote file > > 2. Modify the file > > 3. Save it to the same remote location under same name ... > > ... the file saved in step three is not containing the modifications made in > > step 2 but is still the old one as it was in step 1? > > And by concurrently modifying the remote file in Kate, you know that KBibTeX > > actually writes something to the remote location in step 3? I can confirm your summary is correct. I'm working now in a different hardware, same system+DEnv (KDE/Plasma 5.18.3). I have downloaded, compiled and executed kbibtex from git as explained in #2. I get the same previous anomalous behavior when trying to save the modified .bib file to a remote system via sftp. I have however spotted two small differences with respect to the previous tests: a) Now both the "Save" and the "Save As" commands fail to replace the original (remote) file by the modified one. However, the "Save Copy As" command works, it saves the modified version of the file into the remote system (as a new file, different name). b) When performing either the "Save" or the "Save As" operations described above, I get now a system notification of: "Moving (Finished)", followed by the corresponding sftp command (in correct syntax, I would say). However, when I perform the "Save Copy As", I get no such a notification. That is, somehow the two first commands (that fail to replace the file) trigger a file-moving operation in the KDE environment whereas the latter command (that is working as supposed) does not. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 416647] KBibTex unable to save files on a remote server via sftp
https://bugs.kde.org/show_bug.cgi?id=416647 --- Comment #8 from Joan --- I am attaching 3 text files; the total output from console is splitted between the second and third files; in the first file there is the part of console output which I guess might be more relevant, after kbibtex execution started. Let me explain how the last seven output lines appeared: kbibtex.parts: watchableFilename is Empty kbibtex.io: Don't know how to encode Unicode char "0x0301" kbibtex.io: Don't know how to encode Unicode char "0x2010" kbibtex.parts: watchableFilename is Empty qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14661, resource id: 55074827, major code: 40 (TranslateCoords), minor code: 0 kbibtex.io: Don't know how to encode Unicode char "0x0301" kbibtex.io: Don't know how to encode Unicode char "0x2010" Each time I try to "Save", I get (almost immediately) these four lines on output: kbibtex.parts: watchableFilename is Empty kbibtex.io: Don't know how to encode Unicode char "0x0301" kbibtex.io: Don't know how to encode Unicode char "0x2010" kbibtex.parts: watchableFilename is Empty and after a few seconds the floppy icon vanishes, meaning that the modified file should have been rewritten in the remote directory (but it is not, even though its time stamp is updated). The last 3 lines, qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 14661, resource id: 55074827, major code: 40 (TranslateCoords), minor code: 0 kbibtex.io: Don't know how to encode Unicode char "0x0301" kbibtex.io: Don't know how to encode Unicode char "0x2010" appear instead during the "Save as" alternative, i.e, when (successfully) saving the modified file into the remote directory with a different name. I guess the "XCB error" is unrelated to the current issue, it seems has something to do with a small window shown during the "Save as" process. Thus I would say that the relevant difference in ouptut between a failed and a successful remote save operation is, kbibtex.parts: watchableFilename is Empty showing twice per failed try. Let me also explain the results from an additional little test: this time I modified the remote file, while keeping kbibtex open (I know, a sensible user should never do this), not 'directly' (using a konsole on the server) but locally (using Kate); this is the summary (scheme) of the file update history: #1 original remote file opened locally both in kbibtex and kate #2 version modified internally in kbibtex, but cannot be updated into remote directory #3, #4, #5 subsequently modified versions in Kate, successfully updated each time in the remote directory At this point, the original (#1) file only 'lives' as a temporary file (somewhere). If now I try a "Save" in bibtex, #1 reappears again in the remote directory (it overwrites the newer version #5, previosly saved by Kate). -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 416647] KBibTex unable to save files on a remote server via sftp
https://bugs.kde.org/show_bug.cgi?id=416647 --- Comment #7 from Joan --- Created attachment 125736 --> https://bugs.kde.org/attachment.cgi?id=125736=edit Console output + compiler warnings -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 416647] KBibTex unable to save files on a remote server via sftp
https://bugs.kde.org/show_bug.cgi?id=416647 --- Comment #6 from Joan --- Created attachment 125735 --> https://bugs.kde.org/attachment.cgi?id=125735=edit Compiler output (clog?) except warnings -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 416647] KBibTex unable to save files on a remote server via sftp
https://bugs.kde.org/show_bug.cgi?id=416647 --- Comment #5 from Joan --- Created attachment 125734 --> https://bugs.kde.org/attachment.cgi?id=125734=edit Console output during kbibtex execution -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 416647] KBibTex unable to save files on a remote server via sftp
https://bugs.kde.org/show_bug.cgi?id=416647 --- Comment #3 from Joan --- (In reply to Thomas Fischer from comment #2) > I think I was able to fix this problem. Please have a look at the following > patch and report back if it fixed your problem: > https://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/ > 5040708c6486e075c7048ebd371ab6ccdd9262ed > > You can test this code without interfering with your default KBibTeX > installation by following the "quick start" instructions: > https://userbase.kde.org/KBibTeX/ > Development#Quick_Start_to_Run_KBibTeX_from_Git > > To test the Git version containing the fix for your bug, please run the > following command: > bash run-kbibtex.sh > https://anongit.kde.org/clones/kbibtex/thomasfischer/kbibtex.git > bugs/kde416647 Downloaded and compiled the new version as indicated. The patch did not work here, same behaviour as before. Let me add some additional information (tests): 1- To discard that I made something stupid with file permissions or sftp connection settings, I opened the remote (.bib) file with Kate and it worked as supposed, modifications were incorporated into the remote file after saving. 2- In kbibtex, the "save as" (new file) operation works well: I can succesfully save the modified contents into a new file in the remote directory. 3- After opening the remote file in kbibtex, I removed (externally, via cli) the remote file. After modifying the file (in kbibtex) and saving it, the OLD (unmodified) version 'reappeared' in the remote directory. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 416647] New: KBibTex unable to save files on a remote server via sftp
https://bugs.kde.org/show_bug.cgi?id=416647 Bug ID: 416647 Summary: KBibTex unable to save files on a remote server via sftp Product: KBibTeX Version: 0.9 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Loading/saving files Assignee: fisc...@unix-ag.uni-kl.de Reporter: joan.herr...@urv.cat Target Milestone: --- SUMMARY Remote access to a server via sftp. Remote .bib files are loaded and, apparently, can be modified and then saved. However, the remote file is not modified. Checked that the remote file has read-write permissions for all users enabled. STEPS TO REPRODUCE 1. Open .bib file on remote server 2. Modify the contents of the file 3. Save the file, either click to the icon or use Ctrl + S shortcut 4. Apparently the modified file has been saved. OBSERVED RESULT The time stamp of the file in the server directory has been updated. However, a check on the contents of the remote file (via terminal+vim editor) shows that the file was not modified, it keeps the original contents. EXPECTED RESULT A modified file with the contents as visualized in KBibTeX SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.17 User Edition (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION When KBibTeX is started from terminal, as a result of the Save action (on the remote file) the following message appears in the terminal: kbibtex.parts: watchableFilename is Empty kbibtex.io: Don't know how to encode Unicode char "0x0301" kbibtex.io: Don't know how to encode Unicode char "0x2010" kbibtex.parts: watchableFilename is Empty -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 412409] Crash when scrolling photos
https://bugs.kde.org/show_bug.cgi?id=412409 --- Comment #2 from Joan --- I could get another crash after scrolling around the pictures, this is what was printed on the console (I couldn't get the crash file this time tough: -- $ ~/.local/bin/kphotoalbum kphotoalbum.ImageManager: "Unable to convert string \"\"to double (for file /media/aseques/TOSHIBA_FOTOS/$RECYCLE.BIN/S-1-5-21-3952020594-3068430305-2178502575-1001/$IKRH22R.MOV)" kphotoalbum.ImageManager: "Unable to convert string \"\"to double (for file /media/aseques/TOSHIBA_FOTOS/$RECYCLE.BIN/S-1-5-21-3952020594-3068430305-2178502575-1001/$IID61AG.MOV)" QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image Aborting aboutToFinish handling. QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 33252, resource id: 37752474, major code: 40 (TranslateCoords), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 35004, resource id: 37752697, major code: 40 (TranslateCoords), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36901, resource id: 37752948, major code: 40 (TranslateCoords), minor code: 0 QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QIma
[kphotoalbum] [Bug 412409] New: Crash when scrolling photos
https://bugs.kde.org/show_bug.cgi?id=412409 Bug ID: 412409 Summary: Crash when scrolling photos Product: kphotoalbum Version: GIT master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Thumbnail Viewer Assignee: kpab...@willden.org Reporter: aseq...@gmail.com Target Milestone: --- Created attachment 122910 --> https://bugs.kde.org/attachment.cgi?id=122910=edit Crash generated by dr konqui SUMMARY STEPS TO REPRODUCE 1. I was just scrolling through the photos and videos indexed by kphotoalbum 2. I tested the issue both with 5.4.2 and 5.5 (master as of 27/9/19) OBSERVED RESULT Crash on the program. EXPECTED RESULT Scrolling of pictures SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 Ksnapshot version: v5.5-142-g22c3236b KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION See attached the crash (supposedly useful) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412131] baloo_file crashes after system startup
https://bugs.kde.org/show_bug.cgi?id=412131 Joan changed: What|Removed |Added Resolution|DOWNSTREAM |FIXED --- Comment #2 from Joan --- Fixed! I just installed devel_basis. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412131] New: baloo_file crashes after system startup
https://bugs.kde.org/show_bug.cgi?id=412131 Bug ID: 412131 Summary: baloo_file crashes after system startup Product: frameworks-baloo Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: joan.herm...@pricetravel.com Target Milestone: --- Created attachment 122769 --> https://bugs.kde.org/attachment.cgi?id=122769=edit Debugger Output SUMMARY It happens on every system startup after boot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.0 KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 ADDITIONAL INFORMATION Kernel Version: 4.12.14-lp150.12.70-default -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394577] Panel / Task bar / Task Manager shows stub icon for Firefox when Firefox is running; unable to customize Firefox's icon
https://bugs.kde.org/show_bug.cgi?id=394577 Chad Joan changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #3 from Chad Joan --- Problem seems fixed after removing the ~/.local/share/applications/firefox.desktop file. Specifically, I moved it to a backup file like so: cd ~/.local/share/applications mv firefox.desktop firefox.desktop.bak-2018.11.19 It took me a while to revisit this problem, but inspiration hit: I think Eike's mention of /opt being odd and an incorrect .desktop file were the hint I needed. The contents of the firefox.desktop file looked like this: [Desktop Entry] Exec=/opt/firefox/firefox Icon=application-x-executable Name=firefox Type=Application This seems a likely candidate for explaining why plasma was looking for the /opt/firefox/firefox file that did not exist (the /opt/firefox directory also doesn't exist). I'm not sure I understand specifics about the mechanisms involved, but I can see how telling KDE/plasma to open a non-existent executable might confuse it. Or perhaps the .desktop was outdated and accidentally overrode metadata from more well-updated system files. Whatever the possibilities, that file seemed like a source of problems, and removing it fixed this problem. I'm also not sure how I ended up with the state in the first place. Maybe Firefox really did live in /opt/firefox/firefox at one point in history, and then an upgrade at some point moved it elsewhere, but without updating the .desktop file (and it's hard to expect a package manager or install script to always perfectly handle updates to user configuration). Maybe these are remnants of some workaround from days past. I'm not too worried about it because of how isolated this seems. Thanks for the help Eike Hein! -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 385510] Cannot add address book folder to Personal contacts resource
https://bugs.kde.org/show_bug.cgi?id=385510 Joan changed: What|Removed |Added Platform|Compiled Sources|Kubuntu Packages Version|5.6.0 |5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 385510] Cannot add address book folder to Personal contacts resource
https://bugs.kde.org/show_bug.cgi?id=385510 --- Comment #4 from Joan --- I am using kubuntu 18.10, with version 5.8.3, and the error is still happening. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 385510] Cannot add address book folder to Personal contacts resource
https://bugs.kde.org/show_bug.cgi?id=385510 --- Comment #3 from Joan --- Created attachment 115914 --> https://bugs.kde.org/attachment.cgi?id=115914=edit Error shown on screen -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 385510] Cannot add address book folder to Personal contacts resource
https://bugs.kde.org/show_bug.cgi?id=385510 Joan changed: What|Removed |Added CC||aseq...@gmail.com --- Comment #2 from Joan --- Created attachment 115913 --> https://bugs.kde.org/attachment.cgi?id=115913=edit Triggerring the issue -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370003] Performance issues (laggy animations, stuttering keyboard input handling, severe frame drops in videos) after using plasmashell for a few days
https://bugs.kde.org/show_bug.cgi?id=370003 --- Comment #11 from Joan --- I followed this bug because I was having exact the same symptoms, I could track the issue to some applications both are using java: - Pycharm community edition - Soap UI Both apps work normally when launched, but if they are left overnight, system becomes unusable. I would say that's the problem appears when the memory available is low (I've 8G and usually around 6G used). The exact same issue happens when I open chromium (huge memory consumer) o when I have more than two firefox instances running (with two it's fine). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336134] Plasma-applet disappear immediatly with focus follows mouse and focus stealing prevention = high
https://bugs.kde.org/show_bug.cgi?id=336134 --- Comment #15 from Joan --- (In reply to lestofante88 from comment #14) > I can confirm this issue and i DONT use focus follows mouse. > > If i set focus stealing prevention > high laucher and caledar does not open. > I can see some frame of the animation sometimes. Same here -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Application Launcher from opening when using focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=377914 Joan changed: What|Removed |Added CC||aseq...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336134] Plasma-applet disappear immediatly with focus follows mouse and focus stealing prevention = high
https://bugs.kde.org/show_bug.cgi?id=336134 Joan changed: What|Removed |Added CC||aseq...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394577] Panel / Task bar / Task Manager shows stub icon for Firefox when Firefox is running; unable to customize Firefox's icon
https://bugs.kde.org/show_bug.cgi?id=394577 --- Comment #2 from Chad Joan <chadj...@gmail.com> --- Thanks! That process overview is excellent, and it's good to know about those fallback heuristics. I will use that information to investigate more. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 353733] Firefox icon is missing in Plasma 5.4.2
https://bugs.kde.org/show_bug.cgi?id=353733 Chad Joan <chadj...@gmail.com> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=394577 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 394577] New: Panel / Task bar / Task Manager shows stub icon for Firefox when Firefox is running; unable to customize Firefox's icon
https://bugs.kde.org/show_bug.cgi?id=394577 Bug ID: 394577 Summary: Panel / Task bar / Task Manager shows stub icon for Firefox when Firefox is running; unable to customize Firefox's icon Product: frameworks-plasma Version: 5.43.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: chadj...@gmail.com Target Milestone: --- Created attachment 112819 --> https://bugs.kde.org/attachment.cgi?id=112819=edit Plasma 5 panel/taskbar showing stub icon for running Firefox Hello, When I start Firefox, the following happens in the panel/taskbar/task manager: - A tab (task?) appears for Firefox. - The Firefox icon appears on the tab for a few frames. - There is a very brief stutter, as if Firefox closed and reopened. - The Firefox icon is immediately replaced with what appears to be a stub icon. - The stub icon will remain until I close Firefox or otherwise dismiss that tab/task. It looks like this: https://photos.app.goo.gl/jPdQWi2crItDioED3 (This image is also attached.) (The icon I see looks to me like a dark gray piece of paper with a folded corner and a light gray iconified app window in the middle, with an exclamation point in the middle of the window.) This is very frustrating because the stub icon is non-distinct, so it kept looking like I couldn't bring Firefox up by clicking on it in the panel/taskbar, yet Firefox was there all along, hiding in the sea of gray. I try various hocus pocus from bug reports and forum posts across the internet. For example, I used kmenuedit to set Firefox's icon to firefox again, because some users seemed to experience success with that and infer that the assignment of that icon must do more than merely change the icon that appears in the application launcher. None of those cute tricks worked. Then I found this bug: https://bugs.kde.org/show_bug.cgi?id=353733 which told me that the Firefox icon was removed from the Breeze theme due to some kind of legal fears. That was back in *2015*, so I was slightly disappointed that a KDE dude hasn't talked to a Mozilla dude and reached an agreement to solve the problem sometime before 2018. It seems like something that would be on the right side of cost-benefit: sure this may seem minor, but it probably affects an enormous amount of users in a very prominent way, and it might be very easy to fix. But that's OK. The rest of my Plasma 5 experiences is going very well, and I have a Firefox icon on my computer. Probably more than one, even! Firefox comes with its own icon(s), after all. So I set about injecting the Firefox icon back into its place. I learned that there are various firefox.png instances in the /usr/share/icons/hicolor/NNxNN/apps directories. I also learn that icons can be added to the stack without disturbing the root system by building corresponding directories in ~/.local/share/icons/*. I'm using the Breeze icon theme, so I figure I need ~/.local/share/icons/breeze to contain at least the firefox.png's from the hicolor theme (whatever that is). The first experiment involves me creating a symlink... /usr/share/icons/hicolor -> ~/.local/share/icons/breeze ... so that, per my naive understanding at the time, the icon set available would essentially be the union of the two, with the .local ones overriding the /usr ones in the event of conflict. And it works!... almost. The Firefox icon reappeared, but then all of the other icons (Dolphin folder icons, system settings icons, many things in the application launcher and settings menus, and so on) went completely invisible. Not even a stub graphic remains. So that's no good either, but it's encouraging at least. Next I try to be more surgical. I delete that symlink and manually create the ~/.local/share/icons/breeze folder and subfolders, then I create individual symlinks for every firefox.png file. Maybe there were a bunch in ~/.local that were overriding /usr icons, but couldn't be rendered for some reason. Well, that didn't work at all, and the system went back to the original condition where most icons were fine and Firefox had a stub graphic for an icon. I then start trying to figure out what made the one directory display the icon I wanted when the other directory did not. This involved learning about the Icon Theme layout; this site was my primary reference: https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html Things I tried: - Create an index.theme file in ~/.local/share/icons/breeze folder. - Iterate on the index.theme file and occasionally bounce back-and-forth between having a working Firefox icon and having working system icons. I run 'gtk-update-icon-cache' after any and all changes. - Rename ~/.local/share/icons/breeze to
[ksirk] [Bug 390111] The url to download skins url is not working
https://bugs.kde.org/show_bug.cgi?id=390111 --- Comment #1 from Joan <aseq...@gmail.com> --- The version found in kubuntu artful is 4.14.34 -- You are receiving this mail because: You are watching all bug changes.
[ksirk] [Bug 390111] New: The url to download skins url is not working
https://bugs.kde.org/show_bug.cgi?id=390111 Bug ID: 390111 Summary: The url to download skins url is not working Product: ksirk Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: nemhi...@gmail.com Reporter: aseq...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 110457 --> https://bugs.kde.org/attachment.cgi?id=110457=edit error message When clicking on the 'Download new skins' button, nothing gets download. There's a message saying 'Loading of providers from file http:... failed' -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 370370] "Copy to ..." won't work for an sftp connection
https://bugs.kde.org/show_bug.cgi?id=370370 Joan <aseq...@gmail.com> changed: What|Removed |Added CC||aseq...@gmail.com --- Comment #4 from Joan <aseq...@gmail.com> --- It happens to mee, altought killing all the sftp processes doesn't make any difference. KF 5.31 / Dolphin 16.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370003] Performance issues (laggy animations, stuttering keyboard input handling, severe frame drops in videos) after using plasmashell for a few days
https://bugs.kde.org/show_bug.cgi?id=370003 Joan <aseq...@gmail.com> changed: What|Removed |Added CC||aseq...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375602] New: Debug and run should save the current file when working in python
https://bugs.kde.org/show_bug.cgi?id=375602 Bug ID: 375602 Summary: Debug and run should save the current file when working in python Product: kdevelop Version: 5.0.80 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: aseq...@gmail.com Target Milestone: --- I found that when working with python scripts, I have to manually save my files before debug or execute. This is a bit annoying because when I forget to save the file, an old version is launched giving unexpected results. It would be nice to have an option (or a default in python) that would save the file on the moment I press any of those buttons (or at least a warning telling that an old version of the file will be launched) For some background on this, and some workarounds, there is a thread in the forum here (https://forum.kde.org/viewtopic.php?f=218=138642) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375588] When a script can't be run because of syntax errors, run tool view should be shown
https://bugs.kde.org/show_bug.cgi?id=375588 Joan <aseq...@gmail.com> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375588] When a script can't be run because of syntax errors, run tool view should be shown
https://bugs.kde.org/show_bug.cgi?id=375588 --- Comment #1 from Joan <aseq...@gmail.com> --- Forget about it, the views I saw were from an old execution. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375588] New: When a script can't be run because of syntax errors, run tool view should be shown
https://bugs.kde.org/show_bug.cgi?id=375588 Bug ID: 375588 Summary: When a script can't be run because of syntax errors, run tool view should be shown Product: kdevelop Version: 5.0.80 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: aseq...@gmail.com Target Milestone: --- I am running a python script, on the last code change I added a syntax error, so it won't run. I launch the script with Debug, and I get to see the debug tool view with no content. Until I manually go to Run, there are no indicators of something not working (other than the debug buttons greyed out) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 374068] New: There is no user / password management for git
https://bugs.kde.org/show_bug.cgi?id=374068 Bug ID: 374068 Summary: There is no user / password management for git Product: kdevelop Version: 5.0.3 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: VCS: git Assignee: kdevelop-bugs-n...@kde.org Reporter: aseq...@gmail.com Target Milestone: --- Created attachment 102953 --> https://bugs.kde.org/attachment.cgi?id=102953=edit current view Currently I can configure my own repository in kdevelop, but the only way to add a user and a password is in the url itself (thank scummos for the tip). It would be very nice to have a proper user/password field and kwallet integration to store the credentials. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 345750] The currency conversion doesn't show proper values
https://bugs.kde.org/show_bug.cgi?id=345750 --- Comment #12 from Joan <aseq...@gmail.com> --- Thanks a lot for this fix, it just landed on my kubuntu :D -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349778] The escape sequences to terminate a telnet session don't work
https://bugs.kde.org/show_bug.cgi?id=349778 Joan <aseq...@gmail.com> changed: What|Removed |Added Severity|grave |normal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359696] New: Plasma crashed when moving cursor to second screen (dual screen setup)
https://bugs.kde.org/show_bug.cgi?id=359696 Bug ID: 359696 Summary: Plasma crashed when moving cursor to second screen (dual screen setup) Product: plasmashell Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: aseq...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.2.0-27-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Plasma crashed when moving cursor to second screen (dual screen setup), nothing extraordinary in my configuration, just an instance of firefox at each screen. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fce8d779800 (LWP 4424))] Thread 16 (Thread 0x7fce78b39700 (LWP 4427)): #0 0x7fce87e8088d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fce8bf4ebd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fce8bf5074f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fce7ac827e9 in QXcbEventReader::run (this=0xef2850) at qxcbconnection.cpp:1229 #4 0x7fce88576a6e in QThreadPrivate::start (arg=0xef2850) at thread/qthread_unix.cpp:331 #5 0x7fce876626aa in start_thread (arg=0x7fce78b39700) at pthread_create.c:333 #6 0x7fce87e8be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7fce721fb700 (LWP 4429)): #0 0x7fce84c5a869 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fce84c159a1 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fce84c16167 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fce84c162fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fce887ae50b in QEventDispatcherGlib::processEvents (this=0x7fce6c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fce8875550a in QEventLoop::exec (this=this@entry=0x7fce721fada0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fce88571ac4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fce8ae1fc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fce88576a6e in QThreadPrivate::start (arg=0xfc3d30) at thread/qthread_unix.cpp:331 #9 0x7fce876626aa in start_thread (arg=0x7fce721fb700) at pthread_create.c:333 #10 0x7fce87e8be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7fce66e4b700 (LWP 4430)): #0 0x7fce87e8088d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fce84c161ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fce84c162fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fce887ae50b in QEventDispatcherGlib::processEvents (this=0x7fce68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fce8875550a in QEventLoop::exec (this=this@entry=0x7fce66e4ada0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fce88571ac4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fce8ae1fc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fce88576a6e in QThreadPrivate::start (arg=0x1297290) at thread/qthread_unix.cpp:331 #8 0x7fce876626aa in start_thread (arg=0x7fce66e4b700) at pthread_create.c:333 #9 0x7fce87e8be9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fce64fa7700 (LWP 4431)): #0 0x7fce87e7c44d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fce84c594e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fce84c15cd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fce84c16190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fce84c162fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fce887ae50b in QEventDispatcherGlib::processEvents (this=0x7fce580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7fce8875550a in QEventLoop::exec (this=this@entry=0x7fce64fa6da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7fce88571ac4 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7fce8ae1fc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fce88576a6e in QThreadPrivate::start (arg=0x13da830) at thread/qthread_unix.cpp:331 #10 0x7fce876626aa in start_thread (arg=0x7fce64fa7700) at pthread_create.c:333 #11 0x7fce87e8be9d in clone () at
[gwenview] [Bug 351431] Many menu items are missing in 15.08
https://bugs.kde.org/show_bug.cgi?id=351431 Joan <aseq...@gmail.com> changed: What|Removed |Added CC||aseq...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 351431] Many menu items are missing in 15.08
https://bugs.kde.org/show_bug.cgi?id=351431 Joan <aseq...@gmail.com> changed: What|Removed |Added CC|aseq...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 359420] New: Krunner crash when moving from secondary to main screen
https://bugs.kde.org/show_bug.cgi?id=359420 Bug ID: 359420 Summary: Krunner crash when moving from secondary to main screen Product: krunner Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: aseq...@gmail.com Application: krunner (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.2.0-27-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: I am having quite a few crashes of krunner, normally when trying to start a program, but strangely this time it crashed before typing anything after having just changed the screen from the secondary to the main and then pressed alt+space. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f18f1161800 (LWP 2615))] Thread 11 (Thread 0x7f18dd35b700 (LWP 2621)): #0 0x7f18edbae8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f18ed09ebd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f18ed0a074f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f18df4a47e9 in QXcbEventReader::run (this=0x233ce20) at qxcbconnection.cpp:1229 #4 0x7f18ee2a4a6e in QThreadPrivate::start (arg=0x233ce20) at thread/qthread_unix.cpp:331 #5 0x7f18ebdfe6aa in start_thread (arg=0x7f18dd35b700) at pthread_create.c:333 #6 0x7f18edbb9eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f18d2a9e700 (LWP 2653)): #0 0x7f18eb2c3884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f18eb27f1e1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f18eb27f2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f18ee4dc50b in QEventDispatcherGlib::processEvents (this=0x7f18cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f18ee48350a in QEventLoop::exec (this=this@entry=0x7f18d2a9dda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f18ee29fac4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f18f011dc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f18ee2a4a6e in QThreadPrivate::start (arg=0x25cbc60) at thread/qthread_unix.cpp:331 #8 0x7f18ebdfe6aa in start_thread (arg=0x7f18d2a9e700) at pthread_create.c:333 #9 0x7f18edbb9eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f18c3717700 (LWP 3440)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f18ee2a5d0b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x2b4b390) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x238ab00, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f18cb9b455b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x2769980, th=) at ../../src/weaver.cpp:594 #4 0x7f18cb9b530f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x2769980, th=th@entry=0x4236180, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7f18cb9b9568 in ThreadWeaver::WorkingHardState::applyForWork (this=0x2b3ba10, th=0x4236180, wasBusy=) at ../../src/workinghardstate.cpp:66 #6 0x7f18cb9b44bd in ThreadWeaver::Weaver::applyForWork (this=, th=0x4236180, wasBusy=) at ../../src/weaver.cpp:568 #7 0x7f18cb9b95c2 in ThreadWeaver::WorkingHardState::applyForWork (this=0x2b3ba10, th=0x4236180, wasBusy=) at ../../src/workinghardstate.cpp:73 #8 0x7f18cb9b44bd in ThreadWeaver::Weaver::applyForWork (this=, th=0x4236180, wasBusy=) at ../../src/weaver.cpp:568 #9 0x7f18cb9b73d3 in ThreadWeaver::Thread::run (this=0x4236180) at ../../src/thread.cpp:103 #10 0x7f18ee2a4a6e in QThreadPrivate::start (arg=0x4236180) at thread/qthread_unix.cpp:331 #11 0x7f18ebdfe6aa in start_thread (arg=0x7f18c3717700) at pthread_create.c:333 #12 0x7f18edbb9eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f18c2f16700 (LWP 3441)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f18ee2a5d0b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x2b4b390) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x238ab00, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f18cb9b455b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
[systemsettings] [Bug 351057] custom shortcuts disappear
https://bugs.kde.org/show_bug.cgi?id=351057 Joan <aseq...@gmail.com> changed: What|Removed |Added CC||aseq...@gmail.com --- Comment #8 from Joan <aseq...@gmail.com> --- I can confirm that it's an issue still on 5.5.3 (kubuntu willy backports) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358976] New: Plasma crashed just after login
https://bugs.kde.org/show_bug.cgi?id=358976 Bug ID: 358976 Summary: Plasma crashed just after login Product: plasmashell Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: aseq...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.2.0-27-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: I suspect it might be related to having a multiple screen setup, because there are continuous messages of kscreen The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". QMetaObject::ConnectionListsRef::~ConnectionListsRef (this=0x7ffd631e8c30, __in_chrg=) at kernel/qobject.cpp:3623 [Current thread is 1 (Thread 0x7f9bd22c4800 (LWP 2640))] Thread 16 (Thread 0x7f9bbd682700 (LWP 2642)): #0 0x7f9bcc9cd8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f9bd0a9bbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f9bd0a9d74f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f9bbf7cb7e9 in QXcbEventReader::run (this=0x1dd0850) at qxcbconnection.cpp:1229 #4 0x7f9bcd0c3a6e in QThreadPrivate::start (arg=0x1dd0850) at thread/qthread_unix.cpp:331 #5 0x7f9bcc1af6aa in start_thread (arg=0x7f9bbd682700) at pthread_create.c:333 #6 0x7f9bcc9d8eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f9bb6dbf700 (LWP 2704)): #0 0x7f9bcc9cd8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f9bc97631ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9bc97632fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9bcd2fb50b in QEventDispatcherGlib::processEvents (this=0x7f9bb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f9bcd2a250a in QEventLoop::exec (this=this@entry=0x7f9bb6dbeda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f9bcd0beac4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f9bcf96cc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f9bcd0c3a6e in QThreadPrivate::start (arg=0x1ea26a0) at thread/qthread_unix.cpp:331 #8 0x7f9bcc1af6aa in start_thread (arg=0x7f9bb6dbf700) at pthread_create.c:333 #9 0x7f9bcc9d8eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f9bab986700 (LWP 2705)): #0 0x7f9bcc9cd8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f9bc97631ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9bc97632fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9bcd2fb50b in QEventDispatcherGlib::processEvents (this=0x7f9ba40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f9bcd2a250a in QEventLoop::exec (this=this@entry=0x7f9bab985da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f9bcd0beac4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f9bcf96cc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f9bcd0c3a6e in QThreadPrivate::start (arg=0x21df8a0) at thread/qthread_unix.cpp:331 #8 0x7f9bcc1af6aa in start_thread (arg=0x7f9bab986700) at pthread_create.c:333 #9 0x7f9bcc9d8eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f9ba9ae6700 (LWP 2706)): #0 0x7f9bcc9cd8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f9bc97631ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9bc97632fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9bcd2fb50b in QEventDispatcherGlib::processEvents (this=0x7f9b9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f9bcd2a250a in QEventLoop::exec (this=this@entry=0x7f9ba9ae5da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f9bcd0beac4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f9bcf96cc35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f9bcd0c3a6e in QThreadPrivate::start (arg=0x227d6d0) at thread/qthread_unix.cpp:331 #8 0x7f9bcc1af6aa in start_thread (arg=0x7f9ba9ae6700) at pthread_create.c:333 #9 0x7f9bcc9d8eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f9ba3fff700 (LWP 2713)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9bd1d15194 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f9bd1d151d9 in ??
[dolphin] [Bug 164405] Dbus property to get current url for Dolphin
https://bugs.kde.org/show_bug.cgi?id=164405 Joan <joansanz...@gmail.com> changed: What|Removed |Added CC||joansanz...@gmail.com --- Comment #2 from Joan <joansanz...@gmail.com> --- I voted for this bug (maybe it should be called a feature request) because it would be very useful to be able to get that information to be used in CLI or scripts. It would allow to make some useful decisions depending on what the current url is. For instance, this information could be used to prevent local dolphin and/or system unwanted hangings when dealing with shared remote filesystem (un)mounts (for example, on unexpected NFS server shutdowns). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 356101] Spectacle not capturing any image
https://bugs.kde.org/show_bug.cgi?id=356101 --- Comment #2 from Joan <aseq...@gmail.com> --- You were right, just compile again fullfilling all the deps and it's working perfectly now, a message telling me that no backend was installed would have been helpful, if it interests you, this is the summary of packages I had I had all this related packages: libx11-xcb-dev:amd64 libxcb-dri2-0-dev:amd64 libxcb-dri3-dev:amd64 libxcb-glx0-dev:amd64 libxcb-present-dev:amd64 libxcb-randr0-dev:amd64 libxcb-render0-dev:amd64 libxcb-shape0-dev:amd64 libxcb-sync-dev:amd64 libxcb-xfixes0-dev:amd64 libxcb1-dev:amd64 And hat to install: libxcb-cursor-dev:amd64 libxcb-image0-dev:amd64 libxcb-render-util0-dev:amd64 libxcb-shm0-dev:amd64 libxcb-util-dev:amd64 Now that it's working, it's really a neat software, already replaced ksnapshot on my system -- You are receiving this mail because: You are watching all bug changes.
