[plasmashell] [Bug 369565] Grouping "Only when the task manager is full" never groups
https://bugs.kde.org/show_bug.cgi?id=369565 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Eike Hein --- This will be gone when you upgrade, see https://blogs.kde.org/2016/05/31/new-plasma-task-manager-backend-faster-better-wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369579] Expand Tasks to fit the Complete Task Manager
https://bugs.kde.org/show_bug.cgi?id=369579 Eike Hein changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Eike Hein --- I think this is a pretty bad idea because it makes where to click less predictable, but if you want to do it for personal use, see layout.js in the Task Manager applet's source in plasma-desktop.git. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369579] Expand Tasks to fit the Complete Task Manager
https://bugs.kde.org/show_bug.cgi?id=369579 --- Comment #2 from Jayesh Badwaik --- Thank You. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369579] Expand Tasks to fit the Complete Task Manager
https://bugs.kde.org/show_bug.cgi?id=369579 --- Comment #3 from Eike Hein --- Sorry for the negative reply :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369579] Expand Tasks to fit the Complete Task Manager
https://bugs.kde.org/show_bug.cgi?id=369579 --- Comment #4 from Jayesh Badwaik --- It's fine. :-) I looked at layout.js and I can already do what I wanted. This is cool, I had to change like just two lines. And hence, nice!! I perfectly understand why that's a bad UI design in general. :-) -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 369535] Extracting files from .rpm via drag-and-drop makes wrong paths
https://bugs.kde.org/show_bug.cgi?id=369535 Elvis Angelaccio changed: What|Removed |Added Version Fixed In||16.08.2 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/ark/ ||94d8567d46b5529e65805ba8d95 ||611bcc53d8aa2 --- Comment #3 from Elvis Angelaccio --- Git commit 94d8567d46b5529e65805ba8d95611bcc53d8aa2 by Elvis Angelaccio. Committed on 01/10/2016 at 08:17. Pushed by elvisangelaccio into branch 'Applications/16.08'. Fix drag-and-drop with RPM archives RPM paths start with ./ so removing the rootNode substring starting from index 0 is wrong. FIXED-IN: 16.08.2 Differential Revision: D2895 M +11 -0autotests/kerfuffle/archivetest.cpp A +--- autotests/kerfuffle/data/firmware-pine64-20160329-6.1.aarch64.rpm M +7-8plugins/libarchive/libarchiveplugin.cpp http://commits.kde.org/ark/94d8567d46b5529e65805ba8d95611bcc53d8aa2 -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369592] New: KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML
https://bugs.kde.org/show_bug.cgi?id=369592 Bug ID: 369592 Summary: KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML Product: ksplash Version: 5.7.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: vishal...@gmail.com I wanted to edit the default ksplashqml theme to include a background image. Adding the image was easy enough to the existing Splash.qml in /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/splash but of course whenever there's is an update it gets overwritten to the default again. So I tried copying just the splash folder contents to vishal@skybird:~/.local/share/plasma/look-and-feel/org.kde.vishal.desktop/contents/splash and also modified the metadata.desktop file (to name it org.kde.vishal.desktop to avoid clashing with breeze) and while that seems to work for the splash screen theme, but it also creates a new item under "look and feel" settings. I guess this bug report might be a wishlist to move the theme config load/save away from the overall "look and feel" package/KCM config group so that it's easy for people to create new QML splash themes and configure it in the Splash Screen KCM separate from the selected (default Breeze) Look and Feel options. Looking around the code I couldn't figure out where the "splashmainscript" string literal is being used (loaded/saved) but I guess the code in ksplash QML and KCM portions would need to be updated: https://github.com/KDE/plasma-workspace/blob/master/ksplash/ksplashqml/splashwindow.cpp#L117 https://github.com/KDE/plasma-desktop/blob/master/kcms/ksplash/kcm.cpp#L108 Searching the code for "splashmainscript" found these other places: https://github.com/KDE/plasma-desktop/blob/master/kcms/lookandfeel/kcm.cpp#L194 https://github.com/KDE/plasma-framework/blob/master/src/plasmaquick/private/packages.cpp#L71 https://github.com/KDE/plasma-workspace/blob/master/shell/packageplugins/lookandfeel/lookandfeel.cpp#L71 Although I'm reporting this for 5.7.95 I guess this is too late for the LTS and I hope this might be addressed for 5.9 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369592] KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML
https://bugs.kde.org/show_bug.cgi?id=369592 Vishal Rao changed: What|Removed |Added CC||vishal...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Active] [Bug 369593] New: <><><><>GIRLS<1.800<681
https://bugs.kde.org/show_bug.cgi?id=369593 Bug ID: 369593 Summary: <><><><>GIRLS<1.800<681
[ksplash] [Bug 369592] KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML
https://bugs.kde.org/show_bug.cgi?id=369592 Vishal Rao changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=358839 --- Comment #1 from Vishal Rao --- Added bug # 358839 to the "see also" field, that looks like a more effort wishlist. This bug is intended to ask for getting things started for ability to add/customise splash qmls. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369594] New: Crash when add color clip with "composite" transition + "Rotoscoping" effect
https://bugs.kde.org/show_bug.cgi?id=369594 Bug ID: 369594 Summary: Crash when add color clip with "composite" transition + "Rotoscoping" effect Product: kdenlive Version: 16.08.1 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: d...@live.it Put a movie clip in timeline. Add color clip in timeline above movie clip. Add "composite" transition on color clip. Add "Alpha manipulation -> Rotoscoping". Kdenlive crash! It happen (without error message) with "Alpha manipulation -> Chromakey" too. I trying with .xmf and .mp4 clip, same results. Reproducible: Always Steps to Reproduce: 1. Put a movie clip in timeline. 2. Add color clip in timeline above movie clip. 3. Add "composite" transition on color clip. 4. Add "Alpha manipulation -> Rotoscoping". -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369594] Crash when add color clip with "composite" transition + "Rotoscoping" effect
https://bugs.kde.org/show_bug.cgi?id=369594 Dany changed: What|Removed |Added CC||d...@live.it -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 288141] Kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=288141 --- Comment #37 from Stephan Menzel --- (In reply to Denis Kurz from comment #36) > This bug has only been reported for versions before 4.14, which have been > unsupported for at least two years now. Can anyone tell if this bug still > present? > > If noone confirms this bug for a Framework-based version of kontact (version > 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in > about three months. I remember this bug from back then. It used to hit me hard for many months and then it somehow disappeared. I guess you can safely consider it fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369594] Crash when add color clip with "composite" transition + "Rotoscoping" effect
https://bugs.kde.org/show_bug.cgi?id=369594 Dany changed: What|Removed |Added CC||vpi...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 342141] Export filters should warn if the image contains unsupported features.
https://bugs.kde.org/show_bug.cgi?id=342141 --- Comment #8 from Boudewijn Rempt --- This is now implemented in the rempt/impex refactoring branch. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355982] Sobel filter gives strange result
https://bugs.kde.org/show_bug.cgi?id=355982 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 367988] kio-gdrive requires re-OAUTH if don't wait for for a folder to completely load.
https://bugs.kde.org/show_bug.cgi?id=367988 --- Comment #4 from deonix --- Strange, it occurs every time in any subfolder of the main folder for me. Is there a debug log that might help? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369594] Crash when add color clip with "composite" transition + "Rotoscoping" effect
https://bugs.kde.org/show_bug.cgi?id=369594 Dany changed: What|Removed |Added Version|16.08.1 |16.04.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 358260] Drkonqi crashed during bugreport filling process
https://bugs.kde.org/show_bug.cgi?id=358260 Wolfgang Bauer changed: What|Removed |Added Version Fixed In||5.27.0 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kwal ||let/48ec969bcf36fde17de0275 ||76859c98bae609c73 --- Comment #7 from Wolfgang Bauer --- Git commit 48ec969bcf36fde17de027576859c98bae609c73 by Wolfgang Bauer. Committed on 01/10/2016 at 09:43. Pushed by wbauer into branch 'master'. Check whether kwallet is enabled in Wallet::isOpen(name) If kwallet is disabled, walletlauncher() fails to start the service and walletLauncher()->getInterface().isOpen(name) causes a crash. This affects e.g. drkonqi, but probably also other applications. Return false in this case, if kwallet is disabled a wallet cannot be open either. FIXED-IN: 5.27.0 REVIEW: 128831 M +9-7src/api/KWallet/kwallet.cpp http://commits.kde.org/kwallet/48ec969bcf36fde17de027576859c98bae609c73 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369594] Crash when add color clip with "composite" transition + "Rotoscoping" effect
https://bugs.kde.org/show_bug.cgi?id=369594 Dany changed: What|Removed |Added Version|16.04.0 |16.08.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #4 from John Salatas --- Just an update: it seems that it is fixed in KDE neon developer unstable (as of Octber 1, 1016) -- You are receiving this mail because: You are watching all bug changes.
[kapman] [Bug 368217] Error while eating treats causes massive increase of score
https://bugs.kde.org/show_bug.cgi?id=368217 --- Comment #3 from veralee --- Created attachment 101366 --> https://bugs.kde.org/attachment.cgi?id=101366&action=edit My scores. The ones with an asterisk (*) were with this bug The top two scores were achieved with this bug. It's not something I can predict. It doesn't happen all the time but when it does and there aren't any ghosts to eat me, I can run the score into the stratosphere. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369595] New: Crash on startup with segmentation vault
https://bugs.kde.org/show_bug.cgi?id=369595 Bug ID: 369595 Summary: Crash on startup with segmentation vault Product: digikam Version: 5.2.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: misztal.a...@googlemail.com Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb4436af880 (LWP 6829))] Thread 5 (Thread 0x7fb40963b700 (LWP 6843)): #0 0x7fb43b1eb03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb433d0e733 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fb433d0e759 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fb43b1e70a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb43ea9602d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb41cb76700 (LWP 6836)): #0 0x7fb43b1eb03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb43f3a034b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb44200b931 in Digikam::ParkingThread::run() (this=0x24ed220) at /usr/src/debug/digikam-5.2.0/core/libs/threads/threadmanager.cpp:115 #3 0x7fb43f39f32f in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb43b1e70a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb43ea9602d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb41d377700 (LWP 6831)): #0 0x7fb43b1eb03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb43f3a034b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb442c10f00 in Digikam::ScanController::run() (this=0x7fb443522a60 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at /usr/src/debug/digikam-5.2.0/core/libs/database/utils/scancontroller.cpp:677 #3 0x7fb43f39f32f in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb43b1e70a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb43ea9602d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fb41ef4c700 (LWP 6830)): #0 0x7fb43ea8dbfd in poll () at /lib64/libc.so.6 #1 0x7fb430078422 in () at /usr/lib64/libxcb.so.1 #2 0x7fb43007a00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fb4210803c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fb43f39f32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fb43b1e70a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fb43ea9602d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fb4436af880 (LWP 6829)): [KCrash Handler] #6 0x7fb40b13f414 in QGstreamerBusHelper::installMessageFilter(QObject*) () at /usr/lib64/libqgsttools_p.so.1 #7 0x7fb40b3af37b in () at /usr/lib64/qt5/plugins/mediaservice/libgstmediaplayer.so #8 0x7fb40b3adbda in () at /usr/lib64/qt5/plugins/mediaservice/libgstmediaplayer.so #9 0x7fb43e32fa51 in () at /usr/lib64/libQt5MultimediaWidgets.so.5 #10 0x7fb43e32fd28 in QVideoWidget::setMediaObject(QMediaObject*) () at /usr/lib64/libQt5MultimediaWidgets.so.5 #11 0x7fb43d1adc41 in QMediaPlayer::setVideoOutput(QVideoWidget*) () at /usr/lib64/libQt5Multimedia.so.5 #12 0x7fb442d01168 in Digikam::MediaPlayerView::MediaPlayerView(QWidget*) (this=0x25f2910, parent=) at /usr/src/debug/digikam-5.2.0/core/app/views/mediaplayerview.cpp:168 #13 0x7fb442cffdb6 in Digikam::StackedView::StackedView(QWidget*) (this=0x25079d0, parent=) at /usr/src/debug/digikam-5.2.0/core/app/views/stackedview.cpp:146 #14 0x7fb442cfa969 in Digikam::DigikamView::DigikamView(QWidget*, Digikam::DigikamModelCollection*) (this=0x24a4880, parent=, modelCollection=0x2476df0) at /usr/src/debug/digikam-5.2.0/core/app/views/digikamview.cpp:272 #15 0x7fb442c4330a in Digikam::DigikamApp::setupView() (this=this@entry=0x21c1190) at /usr/src/debug/digikam-5.2.0/core/app/main/digikamapp.cpp:550 #16 0x7fb442c5e8a8 in Digikam::DigikamApp::DigikamApp() (this=0x21c1190, __in_chrg=, __vtt_parm=) at /usr/src/debug/digikam-5.2.0/core/app/main/digikamapp.cpp:234 #17 0x0040876a in main(int, char**) (argc=1, argv=) at /usr/src/debug/digikam-5.2.0/core/app/main/main.cpp:199 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 369581] Gdrive asking to re-authenticate after a few file accesses
https://bugs.kde.org/show_bug.cgi?id=369581 Víctor changed: What|Removed |Added CC||vmorenoma...@gmail.com --- Comment #2 from Víctor --- When I try to access to another folder inside, appears a dialog window for a new authentication. After fill this new authentication, when I try to access to a contained folder, appears again the dialog requesting a new login. :/ -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 369597] New: Cannot control volume of spotify
https://bugs.kde.org/show_bug.cgi?id=369597 Bug ID: 369597 Summary: Cannot control volume of spotify Product: kdeconnect Version: 1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: simg...@gmail.com Volume control works for VLC but not for spotify. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 367988] kio-gdrive requires re-OAUTH if don't wait for for a folder to completely load.
https://bugs.kde.org/show_bug.cgi?id=367988 --- Comment #5 from Elvis Angelaccio --- Created attachment 101367 --> https://bugs.kde.org/attachment.cgi?id=101367&action=edit Possible fix This patch should fix the bug, please test. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 369599] New: Use multimedia style notification when multimedia player is active
https://bugs.kde.org/show_bug.cgi?id=369599 Bug ID: 369599 Summary: Use multimedia style notification when multimedia player is active Product: kdeconnect Version: 1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: simg...@gmail.com It would be nice to have the multimedia controls in the notification area of Android when a multimedia player is active on the PC. In particular I suggest the following behaviour (I take VLC as an example): - VLC is started on the PC - No multimedia notification - User access KDE Connect/Multimedia on Android > Notification is shown - Notification remains in place until VLC is open ..or until the user closes it with the X (this should not cause the closing of VLC on the PC). Possibly a second behaviour can be added (but a setting to switch between the two must be added in the app) Behaviour 2: - Notification is shown as soon as VLC is started on the PC - The X in the multimedia notification closes VLC on the PC and removes the notification Finally if more than one multimedia player is active on the PC, the previous behaviour should apply only for the multimedia player selected in the combobox of the kdeconnect app. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 369599] Show multimedia style notification when multimedia player is active
https://bugs.kde.org/show_bug.cgi?id=369599 Simone Gaiarin changed: What|Removed |Added Summary|Use multimedia style|Show multimedia style |notification when |notification when |multimedia player is active |multimedia player is active -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 369597] Cannot control volume of spotify
https://bugs.kde.org/show_bug.cgi?id=369597 Albert Vaca changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Albert Vaca --- Spotify doesn't expose that feature in MPRIS (the protocol we use to control media players), so we can't do it. It would be nice if you could reach out to them and ask for better MPRIS support: the more people who complain the higher chances to get it :) -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 369274] "expert" button on key generation dialog doesn't bring up Konsole
https://bugs.kde.org/show_bug.cgi?id=369274 --- Comment #2 from Rolf Eike Beer --- It works for me even without the patch, what is your setup? Konsole version etc.? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.
https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #9 from Mark Wielaard --- (In reply to Ivo Raisr from comment #8) > the new test case works ok (I am able to simulate the problem on Solaris) > with 'make one component inaccessible'. Thanks for testing. Lets go with this then. > Please include "string[s].h" for proper strlen declaration. Added. > My apologies it took so long to verify it. I'm a bit overwhelmed these > days... No need to apologize. We are all busy all the time :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 270808] KDE should spin-down external hard disks when 'safely removed'
https://bugs.kde.org/show_bug.cgi?id=270808 dubvulture1...@gmail.com changed: What|Removed |Added CC||dubvulture1...@gmail.com --- Comment #38 from dubvulture1...@gmail.com --- 5 years and this is still not fixed?! We're talking about users' hard disks undermining here, not just some random crash or arguable behiaviour. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369600] New: Brush scaling mode should be proportional to zoom mode
https://bugs.kde.org/show_bug.cgi?id=369600 Bug ID: 369600 Summary: Brush scaling mode should be proportional to zoom mode Product: krita Version: 3.0.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: phoenix.en...@gmail.com Having to Shift-drag over long distances just to change brush sizes in low zoom can be very annoying when working with large files. I propose that brush scaling should be proportional to current zoom, so that shift-dragging has consistent brush scaling over different zoom levels. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 369597] Cannot control volume of spotify
https://bugs.kde.org/show_bug.cgi?id=369597 --- Comment #2 from Simone Gaiarin --- I imagined that. I'll try to reach them. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369446] valgrind crashes on unknown fcntl command
https://bugs.kde.org/show_bug.cgi?id=369446 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Mark Wielaard --- valgrind svn r15998 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369441] bad lvec argument crashes process_vm_readv/writev syscall wrappers
https://bugs.kde.org/show_bug.cgi?id=369441 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Mark Wielaard --- valgrind svn r15997 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369402] Bad set/get_thread_area pointer crashes valgrind
https://bugs.kde.org/show_bug.cgi?id=369402 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Mark Wielaard --- valgrind svn r15996 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369383] x86 sys_modify_ldt wrapper crashes on bad ptr
https://bugs.kde.org/show_bug.cgi?id=369383 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Mark Wielaard --- valgrind svn r15995 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369361] vmsplice syscall wrapper crashes on bad iovec
https://bugs.kde.org/show_bug.cgi?id=369361 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Mark Wielaard --- valgrind svn r15993 -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 369274] "expert" button on key generation dialog doesn't bring up Konsole
https://bugs.kde.org/show_bug.cgi?id=369274 --- Comment #3 from Steven Noonan --- $ konsole --version konsole 16.08.1 Example of how kgpg currently invokes konsole: $ konsole -e gpg --gen-key --expert Unknown options: gen-key, expert. How it should be quoting: $ konsole -e "gpg --gen-key --expert" -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369362] Bad sigaction arguments crash valgrind
https://bugs.kde.org/show_bug.cgi?id=369362 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Mark Wielaard --- valgrind svn r15994 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369360] Bad sigprocmask old or new sets can crash valgrind
https://bugs.kde.org/show_bug.cgi?id=369360 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Mark Wielaard --- valgrind svn r15992 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369359] msghdr_foreachfield can crash when handling bad iovec
https://bugs.kde.org/show_bug.cgi?id=369359 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Mark Wielaard --- valgrind svn r15991 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369356] pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr
https://bugs.kde.org/show_bug.cgi?id=369356 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369356] pre_mem_read_sockaddr syscall wrapper can crash with bad sockaddr
https://bugs.kde.org/show_bug.cgi?id=369356 --- Comment #2 from Mark Wielaard --- valgrind svn r15990 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.
https://bugs.kde.org/show_bug.cgi?id=369209 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #10 from Mark Wielaard --- valgrind svn r15989 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369601] New: the pressure doesn't work, it's full lines
https://bugs.kde.org/show_bug.cgi?id=369601 Bug ID: 369601 Summary: the pressure doesn't work, it's full lines Product: krita Version: 3.0 Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: grave Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: astrothew...@gmail.com well whenever i do a line it's thick without changing any options Reproducible: Always Steps to Reproduce: 1.open krita 2.do a line 3. Actual Results: there's a thick line Expected Results: it should be thin at the edges then thick it never happened before it's like that until this morning and i don't know why, the thin/thick thing works on other programs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368818] Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 Adam changed: What|Removed |Added CC||k...@xibo.at --- Comment #5 from Adam --- Created attachment 101368 --> https://bugs.kde.org/attachment.cgi?id=101368&action=edit same issue. red areas are virtual i can confirm on kde 5.7.95 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368818] Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 --- Comment #6 from Adam --- Created attachment 101369 --> https://bugs.kde.org/attachment.cgi?id=101369&action=edit in addition, the panel is missing after i unplug the second monitor i can get it back by rotating the the primary display (laptop screen) in "system settings" -> "display and monitor" by 90 degrees and back. if it matters, my laptop is a macbook air with intel gpu and thunderbolt (Mini DisplayPort). -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 368462] Add support for ECC keys (primary and subkeys)
https://bugs.kde.org/show_bug.cgi?id=368462 Andrius Štikonas changed: What|Removed |Added Latest Commit||http://commits.kde.org/kgpg ||/65514177e6b9d096b5f6a822a1 ||699e474d791f03 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #8 from Andrius Štikonas --- Git commit 65514177e6b9d096b5f6a822a1699e474d791f03 by Andrius Štikonas. Committed on 01/10/2016 at 12:36. Pushed by stikonas into branch 'frameworks'. Fix compilation with older versions of gpgme. M +8-0core/convert.cpp http://commits.kde.org/kgpg/65514177e6b9d096b5f6a822a1699e474d791f03 -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 368462] Add support for ECC keys (primary and subkeys)
https://bugs.kde.org/show_bug.cgi?id=368462 --- Comment #9 from Steven Noonan --- Andrius, that commit isn't right. You can't use #ifdef on an enum value. It would only be guaranteed to work properly with preprocessor macros. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 368462] Add support for ECC keys (primary and subkeys)
https://bugs.kde.org/show_bug.cgi?id=368462 --- Comment #10 from Steven Noonan --- Something like this would work though: diff --git a/core/convert.cpp b/core/convert.cpp index 1f30739..2939767 100644 --- a/core/convert.cpp +++ b/core/convert.cpp @@ -28,10 +28,10 @@ #include "kgpgsettings.h" // Backport of gpgme enums from version 1.7.0 -#ifndef GPGME_PK_EDDSA +#if GPGME_VERSION_NUMBER < 0x010700 #define GPGME_PK_EDDSA 303 #endif -#ifndef GPGME_PK_ECC +#if GPGME_VERSION_NUMBER < 0x010500 #define GPGME_PK_ECC 18 #endif -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpty] [Bug 364779] libutempter as used in KPty makes applications hang if child process exits immediately
https://bugs.kde.org/show_bug.cgi?id=364779 Martin Sandsmark changed: What|Removed |Added Latest Commit||http://commits.kde.org/kpty ||/65a688be0b2deaf58414e1f196 ||01a15554beb143 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #11 from Martin Sandsmark --- Git commit 65a688be0b2deaf58414e1f19601a15554beb143 by Martin T. H. Sandsmark. Committed on 01/10/2016 at 10:42. Pushed by sandsmark into branch 'master'. Call the utempter helper executable manually According to the investigation in https://bugs.kde.org/show_bug.cgi?id=364779 utempter does stuff in a way that isn't compatible with QProcess/KProcess/KPtyProcess (calling sigaction() before launching its child process). So instead we invoke it manually with QProcess. REVIEW: 128790 M +12 -5cmake/FindUTEMPTER.cmake M +0-5src/CMakeLists.txt M +43 -8src/kpty.cpp M +1-0src/kpty_p.h http://commits.kde.org/kpty/65a688be0b2deaf58414e1f19601a15554beb143 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 369602] New: Crash on close channel or private query
https://bugs.kde.org/show_bug.cgi?id=369602 Bug ID: 369602 Summary: Crash on close channel or private query Product: konversation Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: laysrodriguessi...@gmail.com Application: konversation (1.6-branch #4910) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.7.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Crash after close a channel, and again after close a private query The crash can be reproduced every time. -- Backtrace: Application: Konversation (konversation), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f13bced0800 (LWP 8011))] Thread 5 (Thread 0x7f139d54a700 (LWP 8564)): #0 0x7f13b3ef14b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f13b65c3b66 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f13b65bf274 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f13b65c2d78 in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f13b3eeb454 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f13b5bd47df in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f139700 (LWP 8015)): #0 0x7f13b0374070 in ?? () from /usr/lib/libglib-2.0.so.0 #1 0x7f13b03769b4 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f13b0377004 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f13b037717c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f13b67f159b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f13b679b0da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f13b65be0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f13b65c2d78 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f13b3eeb454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f13b5bd47df in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f13a5b69700 (LWP 8014)): #0 0x7f13b5bcb48d in poll () from /usr/lib/libc.so.6 #1 0x7f13b0377066 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f13b037717c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f13b67f159b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f13b679b0da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f13b65be0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f13b6c02e75 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f13b65c2d78 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f13b3eeb454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f13b5bd47df in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f13a791b700 (LWP 8013)): #0 0x7f13b5bcb48d in poll () from /usr/lib/libc.so.6 #1 0x7f13b22898e0 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f13b228b679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f13a985c469 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f13b65c2d78 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f13b3eeb454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f13b5bd47df in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f13bced0800 (LWP 8011)): [KCrash Handler] #5 0x7f1392b54b74 in ?? () from /usr/lib/libQtGui.so.4 #6 0x7f13bcdcd4fa in call_init.part () from /lib64/ld-linux-x86-64.so.2 #7 0x7f13bcdcd60b in _dl_init () from /lib64/ld-linux-x86-64.so.2 #8 0x7f13bcdd1b38 in dl_open_worker () from /lib64/ld-linux-x86-64.so.2 #9 0x7f13bcdcd3a4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2 #10 0x7f13bcdd12d9 in _dl_open () from /lib64/ld-linux-x86-64.so.2 #11 0x7f13b063cee9 in ?? () from /usr/lib/libdl.so.2 #12 0x7f13bcdcd3a4 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2 #13 0x7f13b063d521 in ?? () from /usr/lib/libdl.so.2 #14 0x7f13b063cf82 in dlopen () from /usr/lib/libdl.so.2 #15 0x7f139c1d1b90 in ?? () from /usr/lib/libvlccore.so.8 #16 0x7f139c1b5eeb in ?? () from /usr/lib/libvlccore.so.8 #17 0x7f139c1b6218 in ?? () from /usr/lib/libvlccore.so.8 #18 0x7f139c1b6174 in ?? () from /usr/lib/libvlccore.so.8 #19 0x7f139c1b66f4 in ?? () from /usr/lib/libvlccore.so.8 #20 0x7f139c1b6cfa in ?? () from /usr/lib/libvlccore.so.8 #21 0x7f139c13ce91 in libvlc_InternalInit () from /usr/lib/libvlccore.so.8 #22 0x7f1393de6d0e in libvlc_new () from /usr/lib/libvlc.so.5 #23 0x7f139c46e2c8 in ?? () from /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #24 0x7f139c443586 in ?? () from /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so #25
[konversation] [Bug 369602] Crash on close channel or private query
https://bugs.kde.org/show_bug.cgi?id=369602 Lays Rodrigues changed: What|Removed |Added Version|unspecified |1.6 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 368588] Okular preview of certain PDF documents shows empty pages with Okular logo only
https://bugs.kde.org/show_bug.cgi?id=368588 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||aa...@kde.org --- Comment #5 from Albert Astals Cid --- Which gs and libspectre versions do you guys have? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 223034] cannot send mail to distribution list
https://bugs.kde.org/show_bug.cgi?id=223034 karaluh changed: What|Removed |Added CC|kara...@karaluh.pl | -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 369603] New: Desktop not detected since update to 1.0
https://bugs.kde.org/show_bug.cgi?id=369603 Bug ID: 369603 Summary: Desktop not detected since update to 1.0 Product: kdeconnect Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: schueller...@gmail.com Tested with desktop versions: 1.0, 1.0.1 and current master; android apk : 1.4.4 from Playstore, and current master. Desktop OS : gentoo with plasma5 Smartphone: OnePlus 3 with stock ROM I'm not sure if this is a bug in the app or the desktop application, but the error is reported from the app, so I hope this is the correct place to put it. Since the update to >=kdeconnect-1.0 the phone can't detect the desktop and vice versa. Compiling the app and running it over adb shows an exception during the ssl handshake: I/KDE/LanLinkProvider: Identity package received from a TCP connection from sebas@SirVimes I/KDE/LanLinkProvider: Starting SSL handshake with sebas@SirVimes trusted:false E/KDE/LanLinkProvider: Handshake failed with sebas@SirVimes W/System.err: javax.net.ssl.SSLHandshakeException: Connection closed by peer W/System.err: at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method) W/System.err: at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:324) W/System.err: at org.kde.kdeconnect.Backends.LanBackend.LanLinkProvider$4.run(LanLinkProvider.java:246) W/System.err: at java.lang.Thread.run(Thread.java:818) Supported ciphers for the phone (according to the apps debug output): I/SupportedCiphers: cipher: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 I/SupportedCiphers: cipher: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 I/SupportedCiphers: cipher: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 I/SupportedCiphers: cipher: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 I/SupportedCiphers: cipher: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 I/SupportedCiphers: cipher: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 I/SupportedCiphers: cipher: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA I/SupportedCiphers: cipher: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 I/SupportedCiphers: cipher: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA I/SupportedCiphers: cipher: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 I/SupportedCiphers: cipher: TLS_ECDHE_PSK_WITH_AES_256_CBC_SHA I/SupportedCiphers: cipher: TLS_DHE_RSA_WITH_AES_256_CBC_SHA I/SupportedCiphers: cipher: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 I/SupportedCiphers: cipher: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA I/SupportedCiphers: cipher: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 I/SupportedCiphers: cipher: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA I/SupportedCiphers: cipher: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 I/SupportedCiphers: cipher: TLS_ECDHE_PSK_WITH_AES_128_CBC_SHA I/SupportedCiphers: cipher: TLS_DHE_RSA_WITH_AES_128_CBC_SHA I/SupportedCiphers: cipher: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 I/SupportedCiphers: cipher: TLS_ECDHE_ECDSA_WITH_RC4_128_SHA I/SupportedCiphers: cipher: TLS_ECDHE_RSA_WITH_RC4_128_SHA I/SupportedCiphers: cipher: TLS_RSA_WITH_AES_256_GCM_SHA384 I/SupportedCiphers: cipher: TLS_RSA_WITH_AES_128_GCM_SHA256 I/SupportedCiphers: cipher: TLS_RSA_WITH_AES_256_CBC_SHA I/SupportedCiphers: cipher: TLS_RSA_WITH_AES_256_CBC_SHA256 I/SupportedCiphers: cipher: TLS_PSK_WITH_AES_256_CBC_SHA I/SupportedCiphers: cipher: TLS_RSA_WITH_AES_128_CBC_SHA I/SupportedCiphers: cipher: TLS_RSA_WITH_AES_128_CBC_SHA256 I/SupportedCiphers: cipher: TLS_PSK_WITH_AES_128_CBC_SHA I/SupportedCiphers: cipher: SSL_RSA_WITH_RC4_128_SHA I/SupportedCiphers: cipher: TLS_PSK_WITH_RC4_128_SHA I/SupportedCiphers: cipher: SSL_RSA_WITH_RC4_128_MD5 I/SupportedCiphers: cipher: SSL_RSA_WITH_3DES_EDE_CBC_SHA I/SupportedCiphers: cipher: TLS_EMPTY_RENEGOTIATION_INFO_SCSV I/SupportedCiphers: cipher: TLS_FALLBACK_SCSV -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369604] New: Add autotype in clipboard applet
https://bugs.kde.org/show_bug.cgi?id=369604 Bug ID: 369604 Summary: Add autotype in clipboard applet Product: plasmashell Version: 5.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: res...@patuck.net Add an autotype button which types out the contents of a clipboard. Usefull where copy works but paste does not (some VNC sessions) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 369078] okular cannot open a cbr comic file
https://bugs.kde.org/show_bug.cgi?id=369078 Albert Astals Cid changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/okul ||ar/f2b2d94897cfedcec91b82a6 ||bed0450546686b51 Resolution|--- |FIXED --- Comment #7 from Albert Astals Cid --- Git commit f2b2d94897cfedcec91b82a6bed0450546686b51 by Albert Astals Cid. Committed on 01/10/2016 at 13:39. Pushed by aacid into branch 'Applications/16.08'. Open CBR files with shared-mime-info >= 1.7 Not ideal fix surely but it'll do for the moment M +1-1generators/comicbook/document.cpp http://commits.kde.org/okular/f2b2d94897cfedcec91b82a6bed0450546686b51 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369605] New: Presets are not marked dirty is the modification is done via the brush-settings.
https://bugs.kde.org/show_bug.cgi?id=369605 Bug ID: 369605 Summary: Presets are not marked dirty is the modification is done via the brush-settings. Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com They ARE marked dirty when using the on-canvas HUD or keys. Reproducible: Always This might be a fluke again, like how reloading suddenly stopped working for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369606] New: Calender: PIM events no longer shown
https://bugs.kde.org/show_bug.cgi?id=369606 Bug ID: 369606 Summary: Calender: PIM events no longer shown Product: plasmashell Version: 5.7.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: deve...@fuchsnet.ch The PIM events plugin is loaded and the list of calendars is shown correctly, however, in the pop-up calendar itself no events are shown. On the console I get a "log_akonadicore: Job error: "Collection does not exist" for collection: QVector() " error message. Reproducible: Always Steps to Reproduce: 1. Enable PIM support in the settings 2. Enable and of your calendars Actual Results: Events are not shown Expected Results: Events are shown KDEPIM-addons is 16.08.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 223034] cannot send mail to distribution list
https://bugs.kde.org/show_bug.cgi?id=223034 --- Comment #62 from H.H. --- I don't use kmail anymore, how can I unsubscribe as reporter of this bug? -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 369592] KSplashQML configuration seems to be tied to Breeze Look and Feel - cannot edit or separately add new QML
https://bugs.kde.org/show_bug.cgi?id=369592 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369607] New: Launcher quickstart icon for an app disappears when app is launched
https://bugs.kde.org/show_bug.cgi?id=369607 Bug ID: 369607 Summary: Launcher quickstart icon for an app disappears when app is launched Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: afac...@gmx.de In the panel, I have quickstart icons for firefox, doplhin and konsole. When I start one of the programs (either from the K menu or the launcher itself) the quickstart icon disappears. This prevents me from opening new browser, dolphin or konsole windows just from the quickstart. The icon disappears when I close the last corresponding application window, so this must be on purpose? I understand that this bug has first been introduced in windows but why does KDE needs to copy this inconsistent behaviour? Reproducible: Always Steps to Reproduce: 1. close all konsole windows 2. add konsole as quickstart launcher icon to the panel 3. open a konsole window Actual Results: 4. quickstart launcher icon disappears Expected Results: 4. quickstart launcher icon is still visible and usable to open new konsole windows -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 369608] New: Payments to credit cards Decrease checking acct balance but increase the credit card amount owed.
https://bugs.kde.org/show_bug.cgi?id=369608 Bug ID: 369608 Summary: Payments to credit cards Decrease checking acct balance but increase the credit card amount owed. Product: kmymoney Version: unspecified Platform: Archlinux Packages URL: https://github.com/BacksSlash092/kmymoneyi OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: General Assignee: kmymoney-de...@kde.org Reporter: gregborre...@gmail.com Hello, I would like to start out saying that I tried several personal financial tools, and Kmymoney is by far the best. I'm having an issue in which when I make a payment the amount on the checking decreases(that's correct) but then my credit card balance increases. The account set up is as follows liability credit card asset checking account and the transaction looks like from : Transfer from: Checking amount : x I added a link with pictures, and thank you for your hard work. Reproducible: Always Steps to Reproduce: 1.Click on new transaction 2. Fill payment information 3.check ledgers Actual Results: checking account decreases but credit card also increasing. Expected Results: checking account decreases and credit card balance decrease. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 368967] Outdated links at utilities/Krusader
https://bugs.kde.org/show_bug.cgi?id=368967 --- Comment #2 from Alex Bikadorov --- > The framework we use to create those pages doesn't have a phabricator entry, > if you know enough php maybe you can help with that? Sorry, non at all. But thanks again. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 369581] Gdrive asking to re-authenticate after a few file accesses
https://bugs.kde.org/show_bug.cgi?id=369581 Elvis Angelaccio changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||1.0.1 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kio- ||gdrive/beb01773c0d297e59717 ||f8c060866e07db09a265 --- Comment #3 from Elvis Angelaccio --- Git commit beb01773c0d297e59717f8c060866e07db09a265 by Elvis Angelaccio. Committed on 01/10/2016 at 14:32. Pushed by elvisangelaccio into branch '1.0'. Fix broken QUrl construction This fixes a regression caused by the KUrl -> QUrl port. QUrl::fromUserInput results in an URL with the http:// scheme, while we need to gdrive:// one. Related: bug 367988 FIXED-IN: 1.0.1 M +4-2src/kio_gdrive.cpp http://commits.kde.org/kio-gdrive/beb01773c0d297e59717f8c060866e07db09a265 -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 367988] kio-gdrive requires re-OAUTH if don't wait for for a folder to completely load.
https://bugs.kde.org/show_bug.cgi?id=367988 Elvis Angelaccio changed: What|Removed |Added Version Fixed In||1.0.1 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kio- ||gdrive/beb01773c0d297e59717 ||f8c060866e07db09a265 Status|CONFIRMED |RESOLVED --- Comment #6 from Elvis Angelaccio --- Git commit beb01773c0d297e59717f8c060866e07db09a265 by Elvis Angelaccio. Committed on 01/10/2016 at 14:32. Pushed by elvisangelaccio into branch '1.0'. Fix broken QUrl construction This fixes a regression caused by the KUrl -> QUrl port. QUrl::fromUserInput results in an URL with the http:// scheme, while we need to gdrive:// one. Related: bug 369581 FIXED-IN: 1.0.1 M +4-2src/kio_gdrive.cpp http://commits.kde.org/kio-gdrive/beb01773c0d297e59717f8c060866e07db09a265 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368244] some PGP messages show: Not enough information to check signature validity
https://bugs.kde.org/show_bug.cgi?id=368244 tony den haan changed: What|Removed |Added CC||kdeb...@tuxick.net --- Comment #2 from tony den haan --- The message/warning only disappears when i set the certificate trust to "ultimately". The message is very unclear: it should at least mention trust level, and maybe link to kgpg. IMO "ultimate" trust ievel is a bit much to demand anyway. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 369609] New: shows only white and blue for trust levels
https://bugs.kde.org/show_bug.cgi?id=369609 Bug ID: 369609 Summary: shows only white and blue for trust levels Product: kgpg Version: 2.17.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: kdeb...@tuxick.net It shows blue for ultimate trust only, white for all others. Shouldn't there be more colours? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 367988] kio-gdrive requires re-OAUTH if don't wait for for a folder to completely load.
https://bugs.kde.org/show_bug.cgi?id=367988 --- Comment #7 from Elvis Angelaccio --- (In reply to Elvis Angelaccio from comment #5) > Created attachment 101367 [details] > Possible fix > > This patch should fix the bug, please test. Got confirmation that the patch works, so I pushed it. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 368541] crash at every shutdown
https://bugs.kde.org/show_bug.cgi?id=368541 Mebuntu changed: What|Removed |Added CC||salsa_te...@yahoo.com --- Comment #4 from Mebuntu --- happens for me on every installation I've done. I've installed fresh Kubuntu on three machines and knotes crashes on shutdown. Can't take a backtrace because the machine is shutting down. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365968] scrolling is unusable slow with libinput in dolphin places and folders panel
https://bugs.kde.org/show_bug.cgi?id=365968 --- Comment #8 from Jake --- This bug seems similar: https://bugs.kde.org/show_bug.cgi?id=369286 He found out that commit "8d61c9c7b6f5a97803bf154529b413ee69bc2a1c" causes the problem and i can also confirm this! (last working commit 4fad4405a719a43968f0ff5e99b169cd5a81df5c) Apparently it was the fix for BUG: 357618, which was already mentioned by the OP. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369585] Timeline corruption due to speed effect
https://bugs.kde.org/show_bug.cgi?id=369585 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kapman] [Bug 368217] Error while eating treats causes massive increase of score
https://bugs.kde.org/show_bug.cgi?id=368217 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 333652] Search does not find anything
https://bugs.kde.org/show_bug.cgi?id=333652 Scott Moore changed: What|Removed |Added CC||sc...@scottbomb.com --- Comment #36 from Scott Moore --- I've seen this bug for at least the past two or three years I've been using Kubuntu. Michael Murphy's workaround (comment #12) works until this bug is fixed. Dolphin can't find anything with desktop search enabled (which is ironic but I'm guessing they use different backends). -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 323323] korganizer crashes when restarting the akonadi server
https://bugs.kde.org/show_bug.cgi?id=323323 --- Comment #4 from Jan Binder --- This does not happen anymore on korgac 5.2.3/Qt 5.6.1/Frameworks 5.25.0. As a replacement, it now crashes differently, see #369452. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 340397] Add --newpassword option
https://bugs.kde.org/show_bug.cgi?id=340397 --- Comment #14 from Christoph Feck --- Why are you asking for help _in a bug tracker_? Please read our guides for correct places to ask for help. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 369545] unable to connect to Pi running real vnc
https://bugs.kde.org/show_bug.cgi?id=369545 Ignat Awwit changed: What|Removed |Added CC||aw...@yandex.by --- Comment #2 from Ignat Awwit --- Same problem. Raspberri Pi 2 Model B: realvnc-vnc-server-5.3.2.22164 My Computer: x86_64 openSUSE 42.1 Leap krdc 15.12.3-17.1 (in the "about KRDC" info: 4.14.18) libvncclient0 0.9.9-13.1 libvncserver0 0.9.9-13.1 Same console output. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369610] New: Background Service "Free Space Notifier" could also warn on low root disk space
https://bugs.kde.org/show_bug.cgi?id=369610 Bug ID: 369610 Summary: Background Service "Free Space Notifier" could also warn on low root disk space Product: plasmashell Version: 5.7.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: codestr...@posteo.org CC: bhus...@gmail.com, plasma-b...@kde.org Recently, a software installation failed because of no disk space left in the root partition. In the "Background Services" Plasma System Settings module there is the "Free Space Notifier" service which "Warns when running out of space on your home folder". Wish: Not only the home folder but also the system partition could be monitored. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 340582] "Free Space Notifier" should also report full root
https://bugs.kde.org/show_bug.cgi?id=340582 --- Comment #2 from Gregor Mi --- *** Bug 369610 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369610] Background Service "Free Space Notifier" could also warn on low root disk space
https://bugs.kde.org/show_bug.cgi?id=369610 Gregor Mi changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Gregor Mi --- Sorry, duplicate of my own bug report. *** This bug has been marked as a duplicate of bug 340582 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 340582] "Free Space Notifier" should also report full root
https://bugs.kde.org/show_bug.cgi?id=340582 Gregor Mi changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 343562] Cannot remove a wrong user/password after it was stored
https://bugs.kde.org/show_bug.cgi?id=343562 Gregor Mi changed: What|Removed |Added CC||codestr...@posteo.org --- Comment #4 from Gregor Mi --- > The same problem just happened to me. Git push, believed that username is the > password I ran into the same problem. The reason why I confused username with password was because the dialog prompt is wrong. On top it says something with "username" but the string next to the textbox says "Password:". -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369611] New: Dolphin cannot create symbol link to file
https://bugs.kde.org/show_bug.cgi?id=369611 Bug ID: 369611 Summary: Dolphin cannot create symbol link to file Product: dolphin Version: 16.08.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: guoyunhebr...@gmail.com Screenshot http://imgur.com/Ze1GYVz Reproducible: Always Steps to Reproduce: 1. Write click, open context menu. choose create symbol link to file or directory, open the dialog. 2. Choose New --> Create symbol link to file or directory. Open input dialog. 3. Click the "open" icon, open file dialog. 4. Select file in file dialog. Actual Results: Can only select directory in file dialog. Cannot select not file. So cannot create file link. Expected Results: The file dialog should allows to choose both files and folders. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369612] New: Default SDDM avatars do not work with the theme
https://bugs.kde.org/show_bug.cgi?id=369612 Bug ID: 369612 Summary: Default SDDM avatars do not work with the theme Product: plasmashell Version: 5.7.95 Platform: openSUSE RPMs URL: https://openqa.opensuse.org/tests/273998#step/first_bo ot/5 OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: fab...@ritter-vogt.de CC: plasma-b...@kde.org The default SDDM avatars (.face.icon/root.face.icon) are dark transparent pngs and thus do not work on dark backgrounds. So far the fallback to the "user-identity" icon worked only because of a bug in sddm 0.14.0: https://github.com/sddm/sddm/pull/684 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 369613] New: wallet manager stops responding
https://bugs.kde.org/show_bug.cgi?id=369613
Bug ID: 369613
Summary: wallet manager stops responding
Product: kwalletmanager
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: va...@kde.org
Reporter: giecr...@stegny.2a.pl
I disabled the wallet using the wallet manager dialogue box and closed the
manager. When I open the wallet manager, it shows the menu bar but menus do
not open. It does not respond to pressing the window close control.
Reproducible: Always
Steps to Reproduce:
1. Tell the wallet manager to open Settings.
Actual Results:
1. No way.
Expected Results:
1. Wallet settings.
Workaround: { kcmshell4 kwalletconfig; }. Enabling the wallet unlocks the user
interface of the wallet manager.
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 369614] New: Inkscape Icons are hard to distinguish and break common standards
https://bugs.kde.org/show_bug.cgi?id=369614 Bug ID: 369614 Summary: Inkscape Icons are hard to distinguish and break common standards Product: Breeze Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: unf...@gmail.com CC: kain...@gmail.com I'm using Mint 18 KDE 5 64-bit. 1. The Color Picker icon resembles a Blur Tool icon from GIMP - why break the convention of using an eyedropper symbol? 2. Layer stack - layer visibility icon - the standard for this is an open/closed eye symbol. The current icon represents stack of layers, and become crossed over when a layer is hidden - please get back to eye symbol. 3. Spiral tool icon - it has a strange double edged path drawn there? Why not a single-edged but maybe a wider stroke instead? 4. Path corners and endings icons - again, the double-edge of the drawn curvers make it unreadable, also the knee is very small, I can hardly see any difference between the corner type icons. The differences are hardly visible. 5. Bounding box snapping modes icons - they are readable, but also the differences are minute and very hard to notice at first glance. The green square is so tiny and the color blends with the bright background making it difficult to spot. (that's also a problem I have with Synaptic icons used for package state (Installed/Updatable/Install/Update/Remove etc. - they differ so slightly I need to stare for 2 seconds each time to know if a package is already installed or not.) I have many years of experience working with Inkscape and it's an essential part of my daily job but this icon set makes me feel like I'm just making my first steps. The usability was sacrificed for aesthetics in my opinion, and my productivity is badly reduced because I can't recognize the tools and buttons that were always there. For example GIMP installed and is using it's own icon set - and I have no problem with that. But I can't force Inkscape to fall back to the default icon set and that's really frustrating, especially when some tools have been given icons that break standards so baldy like the eyedropper replaced with an ink droplet. I know it looks cool, but it makes me work 5 times slower. Reproducible: Always Actual Results: An experienced user feels lost in the Inkscape GUI, becasue of the new icon set, not resembling the standard set. Expected Results: The Inkscape icons may be stylized t fit the overall system theme, but without altering them beyond recognition. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369614] Inkscape Icons are hard to distinguish and break common standards
https://bugs.kde.org/show_bug.cgi?id=369614 unfa changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 369615] New: Archiving a project doesn't work without compression
https://bugs.kde.org/show_bug.cgi?id=369615 Bug ID: 369615 Summary: Archiving a project doesn't work without compression Product: kdenlive Version: 16.08.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: snd.no...@gmail.com If you try to archive a project by checking the "Compressed archive" option all works well, but if you leave it unchecked it fails to archive the project reporting that it fails to create directory /home/$user/videos. Maybe disabling this option fixes the issue. A bonus would be to be able to choose the name of the project to be saved, if not at least change he name from the default "untitled" to something like "kdenlive-project". Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 367538] ERR-8 Nombre de colonnes non valable en ligne 22 : attendu 8 trouvé 1 Boobank 1.0 ING Direct
https://bugs.kde.org/show_bug.cgi?id=367538 Stephane MANKOWSKI changed: What|Removed |Added Resolution|--- |WONTFIX Status|ASSIGNED|RESOLVED --- Comment #10 from Stephane MANKOWSKI --- Fixed by migrating on Mint 18 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 365724] Driver not loaded Driver not loaded
https://bugs.kde.org/show_bug.cgi?id=365724 Stephane MANKOWSKI changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369286] dolphin 16.08.1's Mousewheel scrolling is very small at all settings in non-Plasma5-desktops (regression from 16.04)
https://bugs.kde.org/show_bug.cgi?id=369286 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 330536] Bluetooth device link
https://bugs.kde.org/show_bug.cgi?id=330536 Garland_Key changed: What|Removed |Added CC||david.garland@gmail.com --- Comment #9 from Garland_Key --- Albert, Would it help if I put a small bounty on bluetooth support? I don't have a lot of money, but I'd be willing to pay 15 USD if this were implemented - maybe there are others willing to donate as well. Let me know. Best, Garland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365968] scrolling is unusable slow with libinput in dolphin places and folders panel
https://bugs.kde.org/show_bug.cgi?id=365968 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357618] scrolling with xf86-input-libinput is unusable slow - only in dolphin
https://bugs.kde.org/show_bug.cgi?id=357618 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368019] Resolution selection box not wide enough with scrollbars
https://bugs.kde.org/show_bug.cgi?id=368019 --- Comment #3 from Fabian Vogt --- (In reply to Hugo Pereira Da Costa from comment #2) > In any case, the easyway to see if this is > a style issue is to run > > systemsettings5 -style fusion > > look for the same configuration panel, and see if the problem persists. > @Fabian: can you test/check ? > In the meanwhile I'll try setup a test case. With the fusion style the combobox seems to use up the available space: https://i.imgur.com/rsEuMKc.png -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 369616] New: Korganizer and Kaddressbok crashes, Debug packages for download not found
https://bugs.kde.org/show_bug.cgi?id=369616 Bug ID: 369616 Summary: Korganizer and Kaddressbok crashes, Debug packages for download not found Product: korganizer Version: 5.1.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: korganizer-de...@kde.org Reporter: fr.teichm...@aon.at Application: korganizer (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-38-generic i686 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Kaddressbook crashes with every Start; Korganizer crashes with "neuer Termin". Fehlersuche with gdb results in: no debugging symbols found. - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xa9e90840 (LWP 2942))] Thread 11 (Thread 0xa17fdb40 (LWP 2979)): #0 0xb7734c31 in __kernel_vsyscall () #1 0xb5ae2f8f in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0xb3bbab10 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb3bac10c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb3bac244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb600cb14 in QEventDispatcherGlib::processEvents (this=0xa5e03088, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0xb5fb1953 in QEventLoop::processEvents (this=0xa17fd194, flags=...) at kernel/qeventloop.cpp:128 #7 0xb5fb1daa in QEventLoop::exec (this=0xa17fd194, flags=...) at kernel/qeventloop.cpp:204 #8 0xb5dd7f1d in QThread::exec (this=0xb1557e0) at thread/qthread.cpp:503 #9 0xb5dd7ff8 in QThread::run (this=0xb1557e0) at thread/qthread.cpp:570 #10 0xb5ddd43b in QThreadPrivate::start (arg=0xb1557e0) at thread/qthread_unix.cpp:331 #11 0xb3cf32b5 in start_thread (arg=0xa17fdb40) at pthread_create.c:333 #12 0xb5aed16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 10 (Thread 0xa1ffeb40 (LWP 2977)): #0 0xb3bf24b8 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb3bac007 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb3bac244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb600cb14 in QEventDispatcherGlib::processEvents (this=0xa5003288, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0xb5fb1953 in QEventLoop::processEvents (this=0xa1ffe194, flags=...) at kernel/qeventloop.cpp:128 #5 0xb5fb1daa in QEventLoop::exec (this=0xa1ffe194, flags=...) at kernel/qeventloop.cpp:204 #6 0xb5dd7f1d in QThread::exec (this=0xb152a30) at thread/qthread.cpp:503 #7 0xb5dd7ff8 in QThread::run (this=0xb152a30) at thread/qthread.cpp:570 #8 0xb5ddd43b in QThreadPrivate::start (arg=0xb152a30) at thread/qthread_unix.cpp:331 #9 0xb3cf32b5 in start_thread (arg=0xa1ffeb40) at pthread_create.c:333 #10 0xb5aed16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 9 (Thread 0xa28ffb40 (LWP 2976)): #0 0xb7734c31 in __kernel_vsyscall () #1 0xb3cf8a8c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187 #2 0xb5af98cd in __pthread_cond_wait (cond=0xab2c38d0, mutex=0xab2c38b8) at forward.c:149 #3 0xab18ba2c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5 #4 0xab18ba6c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5 #5 0xb3cf32b5 in start_thread (arg=0xa28ffb40) at pthread_create.c:333 #6 0xb5aed16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 8 (Thread 0xa45ffb40 (LWP 2964)): #0 0xb3bf24b8 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb3baaf63 in g_main_context_acquire () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb3babfa8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb3bac244 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb600cb14 in QEventDispatcherGlib::processEvents (this=0xa4603368, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0xb5fb1953 in QEventLoop::processEvents (this=0xa45ff194, flags=...) at kernel/qeventloop.cpp:128 #6 0xb5fb1daa in QEventLoop::exec (this=0xa45ff194, flags=...) at kernel/qeventloop.cpp:204 #7 0xb5dd7f1d in QThread::exec (this=0x9e63910) at thread/qthread.cpp:503 #8 0xb5dd7ff8 in QThread::run (this=0x9e63910) at thread/qthread.cpp:570 #9 0xb5ddd43b in QThreadPrivate::start (arg=0x9e63910) at thread/qthread_unix.cpp:331 #10 0xb3cf32b5 in start_thread (arg=0xa45ffb40) at pthread_create.c:333 #11 0xb5aed16e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 7 (Thread 0xa4fffb40 (LWP 2962)): #0 0xb3bf248d in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb3bac22f in g_main_context_i
[gwenview] [Bug 369617] New: "Close" leaves the program (Gwenview) ready to appear with the next reboot.
https://bugs.kde.org/show_bug.cgi?id=369617 Bug ID: 369617 Summary: "Close" leaves the program (Gwenview) ready to appear with the next reboot. Product: gwenview Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: bill...@earthlink.net CC: myr...@kde.org I have looked at a number of pictures and I am finished. Other things to do. I went to "Windows Menu" "Close" and Gwenview closed. If I reboot, or shutdown and start up later, Gwenview appears as a minimized window. I can click on it and see what I was looking at when I closed. If I "ps -e |grep gwenview" and kill the gwenview pid, it usually doesn't return. I am using Slackware Linux, the latest version, on a Dell computer with 2 Pentiums 500 MB RAM and 1/2 TB hard drive. Gwenview was part of the Slackware KDE package. I have been using Slackware since it was slakware (8 character names with messy DOS!). Reproducible: Always Steps to Reproduce: 1. look at a picture 2. exit Gwenview and reboot. 3. look at the bar under the screen. A much dimmed Gwenview will be there. click on it and return to whatever it was you were looking at. Actual Results: I can't reboot in this widget. In the past, the Gwenview name and the file being observed (days ago) are visible, and clicking on the name will bring it up. Expected Results: Nothing! No mention of Gwenview. I am looking for a "QUIT! Cease And Desist! Go Back to the disc and stay there!" button. Pretty much what most programs do when closed. -- You are receiving this mail because: You are watching all bug changes.
