[yakuake] [Bug 386350] Focus jumps between splits on open/close
https://bugs.kde.org/show_bug.cgi?id=386350 --- Comment #3 from David P. <san...@gmail.com> --- I had this bug long before, since KDE 5.X. With the right configuration, I could workaround the bug. But now, it keeps failing again. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 386350] Focus jumps between splits on open/close
https://bugs.kde.org/show_bug.cgi?id=386350 David P. <san...@gmail.com> changed: What|Removed |Added CC||san...@gmail.com --- Comment #2 from David P. <san...@gmail.com> --- With KDE Neon 5.11.3 this bug keeps happening. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 386935] Discover cannot process when the authentication of a package is asked
https://bugs.kde.org/show_bug.cgi?id=386935 --- Comment #5 from David P. <san...@gmail.com> --- Finally I've been able to capture the error. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 386935] Discover cannot process when the authentication of a package is asked
https://bugs.kde.org/show_bug.cgi?id=386935 --- Comment #4 from David P. <san...@gmail.com> --- Created attachment 108877 --> https://bugs.kde.org/attachment.cgi?id=108877=edit error popup -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 386935] Discover cannot process when the authentication of a package is asked
https://bugs.kde.org/show_bug.cgi?id=386935 --- Comment #3 from David P. <san...@gmail.com> --- I don't have time to write it down. Errors are shown in a popup that disappears in a few seconds. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 386935] Discover cannot process when the authentication of a package is asked
https://bugs.kde.org/show_bug.cgi?id=386935 --- Comment #1 from David P. <san...@gmail.com> --- Rough translation: Install this packet without verification? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 386935] New: Discover cannot process when the authentication of a package is asked
https://bugs.kde.org/show_bug.cgi?id=386935 Bug ID: 386935 Summary: Discover cannot process when the authentication of a package is asked Product: Discover Version: 5.11.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: san...@gmail.com Target Milestone: --- I can upgrade my system with APT, but not with Discover. This is the cause (in German language): # apt dist-upgrade Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Starting pkgProblemResolver with broken count: 010% Starting 2 pkgProblemResolver with broken count: 0 Done Paketaktualisierung (Upgrade) wird berechnet... Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: libkf5purposewidgets5 libkf5xmlrpcclient-data libkf5xmlrpcclient5 libllvm3.8 libudev1:i386 linux-headers-4.4.0-81 linux-headers-4.4.0-81-generic linux-headers-4.4.0-83 linux-headers-4.4.0-83-generic linux-headers-4.4.0-87 linux-headers-4.4.0-87-generic linux-image-4.4.0-81-generic linux-image-4.4.0-83-generic linux-image-4.4.0-87-generic linux-image-extra-4.4.0-81-generic linux-image-extra-4.4.0-83-generic linux-image-extra-4.4.0-87-generic Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. Die folgenden NEUEN Pakete werden installiert: cryfs encfs libcrypto++9v5 libeditorconfig0 libkf5kirigami2-5 libqt5texttospeech5 libtinyxml2-2v5 linux-headers-4.4.0-98 linux-headers-4.4.0-98-generic linux-image-4.4.0-98-generic linux-image-extra-4.4.0-98-generic plasma-vault Die folgenden Pakete werden aktualisiert (Upgrade): akonadi-contacts-data ark baloo-kf5 bluedevil breeze breeze-cursor-theme breeze-icon-theme chromium-codecs-ffmpeg-extra cracklib-runtime distro-info-data dolphin ffmpegthumbs flashplugin-installer frameworkintegration google-chrome-stable grub-common grub-pc grub-pc-bin grub-theme-breeze grub2-common gtk3-engines-breeze gwenview iproute2 kaccounts-providers kactivities-bin kactivitymanagerd kamera kcharselect kde-cli-tools kde-cli-tools-data kde-config-gtk-style kde-config-gtk-style-preview kde-config-plymouth kde-config-screenlocker kde-config-sddm kde-spectacle kde-style-breeze kde-style-breeze-qt4 kded5 kdeplasma-addons-data kdialog kgamma5 khotkeys khotkeys-data kimageformat-plugins kinfocenter kinit kio kio-extras kio-extras-data kmenuedit konsole konsole-kpart kpackagelauncherqml kpackagetool5 krdc kross kscreen ksshaskpass ksysguard ksysguard-data ksysguardd ktexteditor-data ktexteditor-katepart kwalletmanager kwayland-data kwayland-integration kwin kwin-addons kwin-common kwin-data kwin-style-breeze kwin-x11 kwrite kwrited libastro1 libcrack2 libdolphinvcs5 libgnutls-openssl27 libgnutls30 libkaccounts1 libkdecorations2-5v5 libkdecorations2private5v5 libkf5activities5 libkf5activitiesstats1 libkf5akonadicontact5 libkf5akonadicore5 libkf5akonadiprivate5 libkf5akonadiwidgets5 libkf5archive5 libkf5attica5 libkf5auth-data libkf5auth5 libkf5baloo5 libkf5balooengine5 libkf5baloowidgets-bin libkf5baloowidgets5 libkf5bluezqt-data libkf5bluezqt6 libkf5bookmarks-data libkf5bookmarks5 libkf5calendarcore5 libkf5calendarevents5 libkf5codecs-data
[Spectacle] [Bug 368739] dimmed screen much too dark
https://bugs.kde.org/show_bug.cgi?id=368739 David P. <san...@gmail.com> changed: What|Removed |Added CC||san...@gmail.com --- Comment #6 from David P. <san...@gmail.com> --- I agree, with latest KDE Neon, the situation has improved. :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382866] New: Temporizer plasmoid fails when starting
https://bugs.kde.org/show_bug.cgi?id=382866 Bug ID: 382866 Summary: Temporizer plasmoid fails when starting Product: plasmashell Version: 5.10.4 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: megve...@parabola.nu CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.4) (Compiled from sources) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.9.39-gnu-1-lts-apparmor x86_64 Distribution: "Parabola GNU/Linux-libre" -- Information about the crash: - What I was doing when the application crashed: Just put "Initialize" (I've in Spanish) to the temporizer plasmoid without any value and the app crashed. This happened to me once, but the error seemed important. This was in Parabola GNU/Linux-libre, based on Arch Linux, in a x64 machine The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc810a86e40 (LWP 5060))] Thread 9 (Thread 0x7fc73e337700 (LWP 5193)): #0 0x7fc80a0f6e9d in poll () at /usr/lib/libc.so.6 #1 0x7fc804c8dc09 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc804c8dd1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc80aa2b084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc80a9ceffb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc80a7e840e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc740cda18a in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7fc80a7ed15b in () at /usr/lib/libQt5Core.so.5 #8 0x7fc8099b4049 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fc80a100f0f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fc7519a6700 (LWP 5180)): #0 0x7ffdc270fb00 in clock_gettime () #1 0x7fc80a10e546 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7fc80aa2a972 in () at /usr/lib/libQt5Core.so.5 #3 0x7fc80aa2910a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7fc80aa296e6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7fc80aa2adcf in () at /usr/lib/libQt5Core.so.5 #6 0x7fc804c8d148 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #7 0x7fc804c8db3b in () at /usr/lib/libglib-2.0.so.0 #8 0x7fc804c8dd1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #9 0x7fc80aa2b084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7fc80a9ceffb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7fc80a7e840e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #12 0x7fc80e5298d6 in () at /usr/lib/libQt5Quick.so.5 #13 0x7fc80a7ed15b in () at /usr/lib/libQt5Core.so.5 #14 0x7fc8099b4049 in start_thread () at /usr/lib/libpthread.so.0 #15 0x7fc80a100f0f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fc7e8840700 (LWP 5178)): #0 0x7fc8099ba1ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc810244b04 in () at /usr/lib/libQt5Script.so.5 #2 0x7fc810244b49 in () at /usr/lib/libQt5Script.so.5 #3 0x7fc8099b4049 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fc80a100f0f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fc7e9f23700 (LWP 5177)): #0 0x7fc80aa297c2 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #1 0x7fc80aa2adcf in () at /usr/lib/libQt5Core.so.5 #2 0x7fc804c8d148 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7fc804c8db3b in () at /usr/lib/libglib-2.0.so.0 #4 0x7fc804c8dd1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fc80aa2b084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fc80a9ceffb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fc80a7e840e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fc80a7ed15b in () at /usr/lib/libQt5Core.so.5 #9 0x7fc8099b4049 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fc80a100f0f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fc7ebfff700 (LWP 5176)): #0 0x7ffdc270fb00 in clock_gettime () #1 0x7fc80a10e546 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7fc80aa2a972 in () at /usr/lib/libQt5Core.so.5 #3 0x7fc80aa2910a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7fc80aa296e6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7fc80aa2adcf in () at /usr/lib/libQt5Core.so.5 #6 0x7fc804c8d148 in g_main_context_prepare
[kio] [Bug 379515] Hard drive devices not detected
https://bugs.kde.org/show_bug.cgi?id=379515 David P. <megve...@parabola.nu> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from David P. <megve...@parabola.nu> --- For some reason, after an update the issue was solved -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380185] After the programmed inactivity, screen doesn't lock
https://bugs.kde.org/show_bug.cgi?id=380185 --- Comment #2 from David P. <san...@gmail.com> --- If I run as root: # qdbus org.freedesktop.PowerManagement.Inhibit /org/freedesktop/PowerManagement/Inhibit HasInhibit Service 'org.freedesktop.PowerManagement.Inhibit' does not exist If I run as non-root: # qdbus org.freedesktop.PowerManagement.Inhibit /org/freedesktop/PowerManagement/Inhibit HasInhibit false -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380185] New: After the programmed inactivity, screen doesn't lock
https://bugs.kde.org/show_bug.cgi?id=380185 Bug ID: 380185 Summary: After the programmed inactivity, screen doesn't lock Product: plasmashell Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: san...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 105707 --> https://bugs.kde.org/attachment.cgi?id=105707=edit Screen lock settings I've been using this feature for a long time. Plasma 5 doesn't lock automatically the screen after the programmed inactiviy time. As it can be seen in the screenshot (in German language), I've programmed 6 minutes. I can wait hours and the screen doesn't lock. Using KDE Neon 64 bits. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379758] New: Plasma pannel fails suddenly
https://bugs.kde.org/show_bug.cgi?id=379758 Bug ID: 379758 Summary: Plasma pannel fails suddenly Product: plasmashell Version: 5.9.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: megve...@parabola.nu CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) (Compiled from sources) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.9-gnu-1-pck x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Nothing special, just some work and the usual stuff spected in a normal user - Unusual behavior I noticed: For some reason, the pannel stopped working and disappeared, and then reappeared, and then in the message error it sais that there was a problem with plasma shell, but I didn't care, then I restarted my session and the problem repeated but with a more comprehensive log, so I decided to report it. Distro: Parabola GNU/Linux-libre (based on Arch Linux) Architecture: x64 The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1cda1d5d00 (LWP 14266))] Thread 16 (Thread 0x7f1bef7fe700 (LWP 14488)): #0 0x7f1cd2e48756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1cd3f8e58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1c1a5261d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f1c1a52a9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1c1a525263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1c1a52aa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1c1a525263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1c1a528249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1cd3f8d6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f1cd2e422e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f1cd38a054f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f1be700 (LWP 14487)): #0 0x7f1cd2e48756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1cd3f8e58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1c1a5261d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f1c1a52a9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1c1a525263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1c1a52aa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1c1a525263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1c1a528249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1cd3f8d6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f1cd2e422e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f1cd38a054f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f1c04b9f700 (LWP 14486)): #0 0x7f1cd2e48756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1cd3f8e58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f1c1a5261d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f1c1a52a9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f1c1a525263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f1c1a52aa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f1c1a525263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f1c1a528249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f1cd3f8d6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f1cd2e422e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f1cd38a054f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f1c053a0700 (LWP 14485)): #0 0x7f1cd2e48756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1cd3f8e58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2
[kio] [Bug 379515] Hard drive devices not detected
https://bugs.kde.org/show_bug.cgi?id=379515 --- Comment #2 from David P. <megve...@parabola.nu> --- I don't think that a Systemd upgrade would affect if I use OpenRC, because I don't have Systemd :D Plus, this was after an upgrade of KDE's packages. Anyway thanks for saying this is not only of KDE, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 379515] New: Hard drive devices not detected
https://bugs.kde.org/show_bug.cgi?id=379515 Bug ID: 379515 Summary: Hard drive devices not detected Product: kio Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: devices Assignee: jow...@kde.org Reporter: megve...@parabola.nu Target Milestone: --- Hi, after an upgrade in my Arch-based distro (Parabola GNU/Linux-libre) my HDD partitions and USBs were no longer detected. This also happened to a friend, with the same distro. Both of us use OpenRC, I say this because he also tested this with Systemd and didn't happened. Maybe is a service that I didn't enabled? Note that this doesn't happen with MTP at least. Steps to reproduce 1) Connect a pendrive 2) Nothing should appear, Dolphin shouldn't show it and neither other partitions (e.g. /boot) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #16 from David P. <san...@gmail.com> --- Thanks it now works ok after installing new Krusader. And it looks better. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #15 from David P. <san...@gmail.com> --- In https://pkgs.org/download/krusader, it can be seen that for OpenSuse Leap 42.1 we have: openSUSE KDE Extra all krusader-2.5.0-32.8.x86_64.rpm openSUSE Oss all krusader-2.4.0~beta3-7.7.x86_64.rpm -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #13 from David P. <san...@gmail.com> --- Sorry, I thought I had the latest version installed. Only one version of Krusader available. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #11 from David P. <san...@gmail.com> --- Created bug report in OpenSuse: https://bugzilla.opensuse.org/show_bug.cgi?id=1030731 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #10 from David P. <san...@gmail.com> --- # zypper search krusader Loading repository data... Reading installed packages... S | Name | Summary | Type --+--+--+ | Krusader | Twin-Panel File Manager | application | Krusader - root-mode | Twin-Panel File Manager with root-privileges | application | krusader | A File Manager | package | krusader-doc | A File Manager | package -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #9 from David P. <san...@gmail.com> --- # zypper install krusader Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: krusader The following package is suggested, but will not be installed: krusader-doc 1 new package to install. Overall download size: 2.4 MiB. Already cached: 0 B. After the operation, additional 8.3 MiB will be used. Continue? [y/n/? shows all options] (y): Retrieving package krusader-2.4.0~beta3-7.7.x86_64 (1/1), 2.4 MiB ( 8.3 MiB unpacked) Retrieving: krusader-2.4.0~beta3-7.7.x86_64.rpm [done (242.1 KiB/s)] Checking for file conflicts: .[done] (1/1) Installing: krusader-2.4.0~beta3-7.7.x86_64 [done] -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #8 from David P. <san...@gmail.com> --- I had installed package krusader-2.4.0~beta3-7.7.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #7 from David P. <san...@gmail.com> --- I've installed krusader from the standard OpenSuse repositories. I can try uninstall it and install it. I'm using KDE Plasma 5.5.5, Qt version 5.5.51, kernel 4.1.38-50-default. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #5 from David P. <san...@gmail.com> --- Good trick! Here is the output: gdb -batch -ex bt -p `pidof krusader` [New LWP 11312] [New LWP 11313] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7f3c5c846bfd in poll () from /lib64/libc.so.6 #0 0x7f3c5c846bfd in poll () from /lib64/libc.so.6 #1 0x7f3c59be6e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f3c59be6f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f3c5d5c3f7e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #4 0x7f3c5e03e606 in ?? () from /usr/lib64/libQtGui.so.4 #5 0x7f3c5d595d0f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #6 0x7f3c5d596005 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #7 0x7f3c5d59b459 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #8 0x00451a8c in ?? () #9 0x7f3c5c78bb25 in __libc_start_main () from /lib64/libc.so.6 #10 0x0045341b in _start () -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #3 from David P. <san...@gmail.com> --- "krusader --help" does work. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 --- Comment #2 from David P. <san...@gmail.com> --- Already done so, that why I've said: No text is shown in standard output. I should add, no text in standard error either. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377972] New: krusader hangs after startup
https://bugs.kde.org/show_bug.cgi?id=377972 Bug ID: 377972 Summary: krusader hangs after startup Product: krusader Version: 2.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: san...@gmail.com Target Milestone: --- Using OpenSUSE Leap 42.1 KDE edition. After using krusader successfully for very long time, it has stopped working. When starting it, it hangs, only the outer window decoration is shown, with blank contents. All the GUI is not paint, and doesn't process any mouse or keyboard input. No error message is shown. Tried to delete the config by renaming the folder ~/.kde4/share/apps/krusader, but doesn't solve anything. No text is shown in standard output. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 --- Comment #32 from David P. <san...@gmail.com> --- Your workaround also works for me. Kudos :-) Using OpenSuse Leap 42.1 and Plasma 5.5.5 (In reply to unknown32768 from comment #29) > Today it finally occurred to me to just mess with relevant-seeming settings, > looking for a workaround. In the Yakuake configuration under Window, turning > off "Ask the window manager to perform the animation" seemed to prevent the > issue at first, but I could still trigger it occasionally if I spammed the > toggle key as fast as I can (tensing my arm isometrically so it shakes at > around 10 Hz). Note that I had the duration set to 100 or 150 at different > times. Then I set the duration to 0, but that just makes KDE do a fade > effect by default. So I also disabled Fade under Desktop Effects in KDE's > System Settings, and I am now completely unable to trigger the bug. Maybe it > fixes the shortcut problems too, I hadn't ever noticed that one so I > couldn't say. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 --- Comment #33 from David P. <san...@gmail.com> --- It's important to set the duration to 0. (In reply to silentz0r from comment #30) > Doesn't work on my end. I already wasn't using any animations so I turned > Fade on and off again, disabled asking the window manager to animate the > window and it still happens. > > I was hoping that with a stable plasma release this bug would have received > more focus as it is a fairly important bug. I completely agree that it's a > productivity-killer to always have to think if I'm writing on the right > split. I also have highlighting upon focus enabled, but unfortunately the > split does not animate the focus when yakuake is opened/retracted. > > Maybe this means that the wrong split is selected upon retracting the > terminal? If you notice (with any sort of animation on) the split loses > focus as soon as you hit the retract button. I think during retraction no > split is actually focused, which might even be the problem? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 79023] wish: support for Web Archives (.war)
https://bugs.kde.org/show_bug.cgi?id=79023 --- Comment #8 from David P James <davidpja...@yahoo.com> --- Sorry, how is this "INVALID"? It was an actual, real, verifiable bug at the time it was filed. It was subsequently confirmed as a bug. For something to be "invalid" it has to have never been a valid issue to begin with. Somewhere along the way Ark was changed as per your own words: "Ark now detects mimetype by content so it should be able to open *.war archives (which are renamed Zip files)". The key word there is "now". It didn't used to do that. So in other words, Ark was fixed. This bug is FIXED, not INVALID. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356727] Plasma Panel sometimes disappears with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=356727 --- Comment #36 from David P. <san...@gmail.com> --- Executing this: kquitapp plasmashell; sleep 1; plasmashell solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 359928] New: When closing Yakuake and reopening it, the current pane changes
https://bugs.kde.org/show_bug.cgi?id=359928 Bug ID: 359928 Summary: When closing Yakuake and reopening it, the current pane changes Product: yakuake Version: 2.9.9 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: san...@gmail.com Closing and reopening Yakuake with the hot key causes the active pane to change. Reproducible: Always Steps to Reproduce: 1. Split vertically in 2 panes 2. Provide focus to left pane 3. Close Yakuake by pressing F12 4. Open it again, and observe the focus to go to the right pane Actual Results: Focus changes in an uncontrolled way Expected Results: If I don't change the active pane, to keep the active pane -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355988] I have to press twice some keyboard combinations
https://bugs.kde.org/show_bug.cgi?id=355988 --- Comment #2 from David P. <san...@gmail.com> --- I don't use Ctrl+Shift+letter combinations in all apps. I've observed this behaviour in: - Krusader with Ctrl+Shift+C - IntelliJ IDEA with Ctrl+Shift+C, Ctrl+Shift+K, Ctrl+Shift+R. Apps with normal behaviour: - Firefox with Ctrl+Shift+P - Chrome with Ctrl+Shift+N I don't know if it is a OpenSuse specific problem or a KDE one. -- You are receiving this mail because: You are watching all bug changes.
