[plasmashell] [Bug 359596] Renaming a newly-created file on the desktop causes it to lose position
https://bugs.kde.org/show_bug.cgi?id=359596 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||painless.roas...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Eike Hein --- Based on bug 359457. CC'ing original reporter. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359596] New: Renaming a newly-created file on the desktop causes it to lose position
https://bugs.kde.org/show_bug.cgi?id=359596 Bug ID: 359596 Summary: Renaming a newly-created file on the desktop causes it to lose position Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: h...@kde.org CC: plasma-b...@kde.org 1. Create a new file 2. Drag it into a desired position 3. Rename it 4. See it lose position as if it was new It's possible the "as if it was new" part actually happens in terms of what KDirModel tells us and we lose position because we can't tell it's a rename. To be investigated. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359595] Don't select filename extension when invoking rename for a file
https://bugs.kde.org/show_bug.cgi?id=359595 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||painless.roas...@gmail.com --- Comment #1 from Eike Hein --- Based on bug 359457. CC'ing original reporter. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 220004] Klipper crashes as 'actions' are disabled [QMetaObject::changeGuard, QPointer::operator=, QMenuPrivate::activateAction]
https://bugs.kde.org/show_bug.cgi?id=220004 --- Comment #32 from Michael Zywek --- Hello Martin, thank you for giving me an information about progressing in this case. And thank you for the great work that you and all developers did to change KDE from qt4 to qt5. I remember the changing from KDE 3 to 4; what you did in the last months was very comfortable for me as a normal user. KDE worked everytime, not always perfect, but it stayed steady. I love KDE, and the first reason is the aesthetic and the second is the fact, that I can "create" the "outfit" how I like, and the third reason is, that KDE is really functionable. The new plasma-desktop works fine, the applications are going smooth. There is one exception (Kmail / Kontact [PIM], especially the addressbook with carddav), but so far as I know, you are not appropiate for this. With best regards, Michael Zywek Zywek eMail:m...@zywek.eu Gleißhammerstr. 123d DE-90480 Nürnberg-Mögeldorf Tel.:+49-(0)911-542774 Fax:+49-(0)911-542861 Mobil:+49-(0)152-02946332 erstellt mit und unter Linux: Thunderbird / KMail Am 17.02.2016 um 09:47 schrieb Martin Gräßlin via KDE Bugzilla : > https://bugs.kde.org/show_bug.cgi?id=220004 > > Martin Gräßlin changed: > > What|Removed |Added > > Status|CONFIRMED |RESOLVED > Resolution|--- |UNMAINTAINED > > --- Comment #31 from Martin Gräßlin --- > Thank you for this bug report. Unfortunately the version is no longer > maintained and it's unlikely that the code affects the current version in > Plasma 5 as the code in question changed (e.g. there is no KMenu usage anymore > in klipper). > > I'm very sorry that we didn't get this crash fixed before the software reached > end of life. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359595] New: Don't select filename extension when invoking rename for a file
https://bugs.kde.org/show_bug.cgi?id=359595 Bug ID: 359595 Summary: Don't select filename extension when invoking rename for a file Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: h...@kde.org CC: plasma-b...@kde.org Renaming a file currently pre-selects the entire filename. Dolphin omits the file extension, if any. Folder View's behavior should match. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359457] impossible edit long (multiline) filename in folder widget (or in desktop with folder view)
https://bugs.kde.org/show_bug.cgi?id=359457 Eike Hein changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #3 from Eike Hein --- > enter to rename (rename rectangle shift to right down - why?) That's fixed as of the other day -> https://quickgit.kde.org/?p=plasma-desktop.git&a=commit&h=3882ebb20dbcfb4e49f2813667ca318fab283edc > try press left cursor shift for modify last char - caret skip to begin of filename - why? Normal text editing behavior - Dolphin acts the same. > old filename has complete select with extension - why? - old version kde > (kde4) select only filename for simple modification filename and keep > extension Missing feature. > file (icon) not keep in old position - why? Bug. I don't want more than one issue per ticket so I will make two new tickets and CC you there. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 359594] New: Akregator frequently loses history after restart
https://bugs.kde.org/show_bug.cgi?id=359594 Bug ID: 359594 Summary: Akregator frequently loses history after restart Product: akregator Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: d...@xtra.co.nz Application: akregator (5.0.2) Qt Version: 5.5.1 Operating System: Linux 4.2.0-27-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Full Shutdown, or Restart. On restart, an error dialog will fequently (but not always) appear saying "standard feedlist is corrupted, a backup is created". This is useless, being a 'fresh-install' file with only the standard Kubuntu and KDE feeds - Import of a saved opml file will be required for a useful restore. My system exhibits other errors on re-start: Applications running at closedown may not re-start at startup, or if they do they are likely to not appear in their former Virtual Desktop(s). Akregator is the worst offender, but Dolphin is next worst. I suspect closedown to be too precipitous, not allowing full saving of Desktop and open window(s) per application before shutdown/power-off. (Windows that do appear will do so at correct size and position on screen, but all are likely to appear on the Desktop active at shutdown). This behaviour began with Plasma 5. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbebaa32880 (LWP 1656))] Thread 2 (Thread 0x7fbeaf128700 (LWP 1666)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbeb25194da in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fbeb2518c17 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fbed022b6aa in start_thread (arg=0x7fbeaf128700) at pthread_create.c:333 #4 0x7fbed74fee9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fbebaa32880 (LWP 1656)): [KCrash Handler] #6 QString::QString (other=..., this=this@entry=0x7fffe3527a20) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:811 #7 Akregator::SearchBar::text (this=0x1ac9620) at ../../../akregator/src/searchbar.cpp:125 #8 0x7fbeae4a6f4f in Akregator::MainWidget::saveProperties (this=0x1acb8e0, config=...) at ../../../akregator/src/mainwidget.cpp:1183 #9 0x7fbeae4a10b4 in Akregator::Part::autoSaveProperties (this=this@entry=0x13264e0) at ../../../akregator/src/akregator_part.cpp:871 #10 0x7fbeae4a1149 in Akregator::Part::slotOnShutdown (this=this@entry=0x13264e0) at ../../../akregator/src/akregator_part.cpp:349 #11 0x7fbeae4a17a8 in Akregator::Part::~Part (this=this@entry=0x13264e0, __in_chrg=, __vtt_parm=) at ../../../akregator/src/akregator_part.cpp:422 #12 0x7fbeae4a17f9 in Akregator::Part::~Part (this=0x13264e0, __in_chrg=, __vtt_parm=) at ../../../akregator/src/akregator_part.cpp:426 #13 0x7fbed80117d0 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fbed90129dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fbed9017ea6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fbed7fe1d7b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fbed7fe4176 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fbed80380e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fbecfd0bff7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fbecfd0c250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fbecfd0c2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fbed80384ef in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fbed7fdf50a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fbed7fe75ec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00409630 in main (argc=1, argv=0x7fffe3528438) at ../../../akregator/src/main.cpp:113 Possible duplicates by query: bug 354832, bug 353509, bug 352512. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 194922] Zoom in-out when CTRL-Mousewheel
https://bugs.kde.org/show_bug.cgi?id=194922 --- Comment #8 from Dave Andrews --- @Pascal (In reply to Pascal d'Hermilly from comment #7) > @Draciron why do you hold down the CTRL key when you scroll? > You will get the same behaviour in almost all other programs, such as a > browser, dolphin, libreoffice. > When you are holding down the Control key you can expect to get a different > behaviour. The issue is that mouse interactions are often unreliable on touch-input devices -- especially in more complicated KDE apps that are based on Kate. Right now I just pulled the latest version of KDevelop, which makes heavy use of the Ctrl+ modifier during mouse operations (particularly when ctrl+clicking on variables to follow them!) On touch-input devices, when trying to do precision touch events -- scrolling is often applied incorrectly when: -Performing precision single-finger gestures. -Moving into the edge regions of touchpads. -Dirty, Abused, or Disfunctional touchpads. -Owning a larger touch pad (i.e. gaming laptops / touch devices) The problem is compounded with synthetic touchpad driver events (someone trying to workaround this here -> https://git.reviewboard.kde.org/r/120319/), which give the gesture acceleration + deceleration long after the user tries to stop the incorrect input. This leads to having your Kate/KDevelop document look like anything from the size of a breadcrumb -- to the size of Texas! =) You're right that this deserves a central way of controlling this for editor zooming, but in the absence of that, I'm going to have to patch this out of my machine's kate binaries while using an otherwise perfect editor -- because it's incredibly hard to use on touch devices without this! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 194922] Zoom in-out when CTRL-Mousewheel
https://bugs.kde.org/show_bug.cgi?id=194922 Dave Andrews changed: What|Removed |Added CC||jetdog...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 359593] New: annoying monits about lost connection
https://bugs.kde.org/show_bug.cgi?id=359593 Bug ID: 359593 Summary: annoying monits about lost connection Product: trojita Version: 0.6 Platform: Other OS: All Status: UNCONFIRMED Severity: grave Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: msjasin...@gmail.com If you keep the application running in the background when you do other things, it often pops up messages telling that it can't connect, and less often, that a certificate expired and you need to renew it. This is very annoying, as it interferes with normal workflow, making this application practically unusable. Please disable these monits/messages (or make them optional) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 359592] New: remember window state // or: start maximized
https://bugs.kde.org/show_bug.cgi?id=359592 Bug ID: 359592 Summary: remember window state // or: start maximized Product: trojita Version: 0.6 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: msjasin...@gmail.com The application does not remember its window state and often starts unmaximized (part of the window going out of the visible screen). This happens even if I tick Preferences: Start Maximized. Reproducible: Sometimes -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 334080] kdeconnect,some sent photo are uncomplete
https://bugs.kde.org/show_bug.cgi?id=334080 --- Comment #33 from Stéphane Guillou --- ... however, I just realised that, on my computer, I have kdeconnect 0.8-0ppa3+pkg7~ubuntu14.04.1 from the following ppa: https://code.launchpad.net/~vikoadi/+archive/ubuntu/ppa/ Therefore, I can't say how 0.9 behaves. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 334080] kdeconnect,some sent photo are uncomplete
https://bugs.kde.org/show_bug.cgi?id=334080 Stéphane Guillou changed: What|Removed |Added CC||stephane.guil...@gmail.com --- Comment #32 from Stéphane Guillou --- Hi all Sorry, but it is still happening for me (today with an epub file from phone to computer) with the following: - KDE Connect 0.9g from F-Droid - Android 4.2.2 on a Fairphone 1 - KDE 4.13.3 on KXStudio 14.04 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 358887] Plasma crash while removing cache files
https://bugs.kde.org/show_bug.cgi?id=358887 Michael Pyne changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |INVALID --- Comment #3 from Michael Pyne --- Bleachbit overwrites the cache instead of simply unlinking it, which is what causes the crash. There's not much I can do here because the cache is persistent so it must save its accounting data within the file itself, which Bleachbit then corrupts, leading to crashes almost instantly. This type of bug has been reported before, my understanding was that the Bleachbit devs had configured the software to leave things like /var/tmp/kdecache* alone by default but I'm not sure (and I'm sure it's still possible for user to override). See Martin's blog post from nearly 4 years ago now to see how long this has been going on https://blog.martin-graesslin.com/blog/2012/07/do-not-use-bleachbit/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359591] New: Plasma Crash when turning on external TV
https://bugs.kde.org/show_bug.cgi?id=359591 Bug ID: 359591 Summary: Plasma Crash when turning on external TV Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@cock.li CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Have a TV connected as a second monitor via HDMI. It's off when I don't need it. When turning it on Plasma will crash and require restart. This happens each time the TV is turned on. Everything goes blank for a few moments before the TV activates. This is consistent across all graphical environments I've tried. Thought it might be info on possibly a different way it connects. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc038ef8800 (LWP 28543))] Thread 20 (Thread 0x7fc020f0f700 (LWP 28548)): #0 0x7fc032439bbd in poll () at /lib64/libc.so.6 #1 0x7fc037366422 in () at /usr/lib64/libxcb.so.1 #2 0x7fc03736800f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fc0236973c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fc032b3232f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fc031c430a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fc032441fed in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7fc019dd5700 (LWP 28553)): #0 0x7fc032435c8d in read () at /lib64/libc.so.6 #1 0x7fc02a5a8f45 in () at /usr/lib64/tls/libnvidia-tls.so.340.96 #2 0x7fc02eb5cb60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc02eb1b999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc02eb1bdf8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fc02eb1bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fc032d64d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fc032d0bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fc032b2d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7fc035e18df8 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7fc032b3232f in () at /usr/lib64/libQt5Core.so.5 #11 0x7fc031c430a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7fc032441fed in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fc00df38700 (LWP 28610)): #0 0x7fc032439bbd in poll () at /lib64/libc.so.6 #1 0x7fc02eb1be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc02eb1bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc032d64d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc032d0bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc032b2d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc035e18df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc032b3232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc031c430a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc032441fed in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fc007fff700 (LWP 28615)): #0 0x7fc02eb19259 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7fc02eb1b83f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc02eb1bdf8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc02eb1bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc032d64d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc032d0bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fc032b2d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fc035e18df8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fc032b3232f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fc031c430a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fc032441fed in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fc0069c2700 (LWP 28622)): #0 0x7fc031c4703f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc0385cd86b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fc0385cd899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fc031c430a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fc032441fed in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fbf7fdf9700 (LWP 28627)): #0 0x7fc02eb5dd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fc02eb1bf86 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc032d64d8b in QEventDispatcherGlib::proce
[plasmashell] [Bug 348123] Some processes are left running after exiting KDE
https://bugs.kde.org/show_bug.cgi?id=348123 Serhiy Zahoriya changed: What|Removed |Added CC||serhiy@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 359357] Amarok skips tracks
https://bugs.kde.org/show_bug.cgi?id=359357 --- Comment #12 from sedrubal --- Is there a reliable way to find out the version? konsole and kate --version says: Qt: 5.5.1 KDE Frameworks: 5.18.0 Konsole: 15.12.1 kded5 --version kded5 5.18.0 kded4 --version Qt: 4.8.7 KDE Development Platform: 4.14.16 KDE Daemon: 4.14.16 amarok --version Qt: 4.8.7 KDE Development Platform: 4.14.16 Amarok: 2.8.0 (For me it looks like that amarok has some problems when changing the track and refreshing all infos: On almost every track change, my HDD starts rotating which needs some time and the GUI of amarok is not running smoothly... or maybe there are problems with dbus/mpris?) -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 359357] Amarok skips tracks
https://bugs.kde.org/show_bug.cgi?id=359357 --- Comment #11 from Myriam Schweingruber --- Interesting. Which exact KDE release are you using? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 154839] Allow alternate shortcuts in list of global shortcuts
https://bugs.kde.org/show_bug.cgi?id=154839 Andreas Hartmetz changed: What|Removed |Added CC||ahartm...@gmail.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #19 from Andreas Hartmetz --- Fixed with a48cdc289c054934c5d04c525c5687c9b49f7df6 on April 20th 2015. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 359590] New: KDevelop crashes when running all tests
https://bugs.kde.org/show_bug.cgi?id=359590 Bug ID: 359590 Summary: KDevelop crashes when running all tests Product: kdevelop Version: 4.7.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: ysang...@gmail.com Application: kdevelop (4.7.1) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: "Run all tests" from KWayland. It is a CMake project. I don't think the tests are meant to run concurrently as I think KDevelop tried. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3e88535840 (LWP 10459))] Thread 10 (Thread 0x7f3e6c024700 (LWP 10460)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3e81336b5a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7f3e81336b89 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7f3e83f8e6aa in start_thread (arg=0x7f3e6c024700) at pthread_create.c:333 #4 0x7f3e84c4beed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f3dea76a700 (LWP 10484)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7f3e8530c264 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f3e81da5526 in ?? () from /usr/lib/libkdevplatformlanguage.so.8 #3 0x7f3e8530bd1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f3e83f8e6aa in start_thread (arg=0x7f3dea76a700) at pthread_create.c:333 #5 0x7f3e84c4beed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f3ddbcf4700 (LWP 10485)): #0 __libc_disable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:98 #1 0x7f3e84c3c4a9 in read () at ../sysdeps/unix/syscall-template.S:81 #2 0x7f3e7ecf84e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3e7ecb4cd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3e7ecb5190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3e7ecb52fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f3e8544c20e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f3e8541a0d1 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f3e8541a445 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f3e853094f9 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7f3e8530bd1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7f3e83f8e6aa in start_thread (arg=0x7f3ddbcf4700) at pthread_create.c:333 #12 0x7f3e84c4beed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f3dc62d9700 (LWP 10497)): #0 0x7f3e84c408dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f3e7ecb51ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3e7ecb52fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3e8544c20e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f3e8541a0d1 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f3e8541a445 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f3e853094f9 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f3e853fa133 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f3e8530bd1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f3e83f8e6aa in start_thread (arg=0x7f3dc62d9700) at pthread_create.c:333 #10 0x7f3e84c4beed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f3dc6ada700 (LWP 10773)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f3e8530c286 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f3e7ceedcfc in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f3e7cef0a03 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f3e7ceef55f in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #5 0x7f3e8530bd1c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 Valorie Zimmerman changed: What|Removed |Added CC||valorie.zimmer...@gmail.com --- Comment #93 from Valorie Zimmerman --- Hello to all participants in this bug report. People on both sides of the issue have asked me to look at it. While things have been very emotional in the debate, I hope all of us agree that we all want what is best for the KDE community and the software we produce. The level of heat here shows that all of us care about that a great deal. The fact remains that those who do the work get to decide, and working *with* maintainers to get your wishes granted works better than antagonizing them. If you have further input, please write to the Community Working Group at community...@kde.org. Valorie, for the CWG --- Comment #94 from Valorie Zimmerman --- Hello to all participants in this bug report. People on both sides of the issue have asked me to look at it. While things have been very emotional in the debate, I hope all of us agree that we all want what is best for the KDE community and the software we produce. The level of heat here shows that all of us care about that a great deal. The fact remains that those who do the work get to decide, and working *with* maintainers to get your wishes granted works better than antagonizing them. If you have further input, please write to the Community Working Group at community...@kde.org. Valorie, for the CWG -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359558] System tray creating ghost entries
https://bugs.kde.org/show_bug.cgi?id=359558 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu --- Comment #3 from Rex Dieter --- If you'd upgraded to kf5-5.19 recently, this may be a dup of bug #359388 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 359589] New: Configuracao do Sistema falhou apos mudar a navegacao para modo arvore e navegar item a item
https://bugs.kde.org/show_bug.cgi?id=359589 Bug ID: 359589 Summary: Configuracao do Sistema falhou apos mudar a navegacao para modo arvore e navegar item a item Product: systemsettings Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ricdefrei...@hotmail.com Application: systemsettings5 (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: 1 - I change the panel view from icon to tree 2 - I resize the panel to better view the right side 3 - I navegate through the menu (left side) item by item only to see how it looks 4 - crash -- Backtrace: Application: Configurações do Sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0768660780 (LWP 1820))] Thread 4 (Thread 0x7f0754ea0700 (LWP 1821)): #0 0x7f07643bcbbd in poll () from /lib64/libc.so.6 #1 0x7f0761197422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f076119900f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f07578273c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f0764ab532f in QThreadPrivate::start (arg=0xc4d920) at thread/qthread_unix.cpp:331 #5 0x7f075fa93754 in ?? () from /usr/X11R6/lib64/libGL.so.1 #6 0x7f07609210a4 in start_thread () from /lib64/libpthread.so.0 #7 0x7f07643c4fed in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f073ce04700 (LWP 1837)): #0 0x7f0760446cf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f07604048fc in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7f0760404df8 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f0760404f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f0764ce7d8b in QEventDispatcherGlib::processEvents (this=0x7f07380008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f0764c8ed53 in QEventLoop::exec (this=this@entry=0x7f073ce03d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f0764ab061a in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f0763037df8 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f0764ab532f in QThreadPrivate::start (arg=0x441b730) at thread/qthread_unix.cpp:331 #9 0x7f075fa93754 in ?? () from /usr/X11R6/lib64/libGL.so.1 #10 0x7f07609210a4 in start_thread () from /lib64/libpthread.so.0 #11 0x7f07643c4fed in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f0735926700 (LWP 1840)): #0 0x7f07643bcbbd in poll () from /lib64/libc.so.6 #1 0x7f0760404e64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f0760404f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f0764ce7d8b in QEventDispatcherGlib::processEvents (this=0x7f07300c4570, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f0764c8ed53 in QEventLoop::exec (this=this@entry=0x7f0735925d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f0764ab061a in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f0763037df8 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7f0764ab532f in QThreadPrivate::start (arg=0xbf9cd0) at thread/qthread_unix.cpp:331 #8 0x7f075fa93754 in ?? () from /usr/X11R6/lib64/libGL.so.1 #9 0x7f07609210a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f07643c4fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0768660780 (LWP 1820)): [KCrash Handler] #6 0x0060 in ?? () #7 0x7f0764cc334b in QObject::disconnect (sender=0x100be20, signal=0x1698f79 "destroyed()", signal@entry=0x7f0742cb0c72 "2destroyed()", receiver=receiver@entry=0x10215b0, method=0x169cb59 "slotManagedTopLevelWidgetDestroyed()", method@entry=0x7f0742cb1af0 "1slotManagedTopLevelWidgetDestroyed()") at kernel/qobject.cpp:2932 #8 0x7f0742c96485 in KParts::PartManager::~PartManager (this=0x10215b0, __in_chrg=) at /usr/src/debug/kparts-5.16.0/src/partmanager.cpp:136 #9 0x7f0742c96629 in KParts::PartManager::~PartManager (this=0x10215b0, __in_chrg=) at /usr/src/debug/kparts-5.16.0/src/partmanager.cpp:146 #10 0x7f0764cbf63c in QObjectPrivate::deleteChildren (this=this@entry=0x12fdde0) at kernel/qobject.cpp:1946 #11 0x7f0764cc92cc in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1024 #12 0x7f07433d64a6 in KHTMLPart::~KHTMLPart (this=this@entry=0x12fdd50, __in_chrg=, __vtt_parm=) at /usr/src/debug/khtml-5.16.0/src/khtml_part.cpp:559 #13 0x7f07433d6659 in KHTMLPart::~KHTMLPart (this=0x12fdd50, __in_chrg=, __vtt_parm=) at /usr/src/debug/khtml-5.16.0/src/khtml_part.cpp:607 #14 0x7f0
[kmenuedit] [Bug 359588] New: KMenu editor crashes
https://bugs.kde.org/show_bug.cgi?id=359588 Bug ID: 359588 Summary: KMenu editor crashes Product: kmenuedit Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kevin.coo...@gmail.com Application: kmenuedit (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.1.17-4.g9550abf-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Trying to restore the categories (submenus) by hand which are missing w/ KF5. -- Backtrace: Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7fa622da1df7 in KSycocaEntry::entryPath() const () at /usr/lib64/libKF5Service.so.5 #7 0x7fa6244bb24c in () at /usr/lib64/libkdeinit5_kmenuedit.so #8 0x7fa6244a8526 in () at /usr/lib64/libkdeinit5_kmenuedit.so #9 0x7fa6244c1b0c in () at /usr/lib64/libkdeinit5_kmenuedit.so #10 0x7fa6201aacc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #11 0x7fa6244c1512 in () at /usr/lib64/libkdeinit5_kmenuedit.so #12 0x7fa6244c1844 in () at /usr/lib64/libkdeinit5_kmenuedit.so #13 0x7fa6201aacc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #14 0x7fa62111928b in QTreeWidget::currentItemChanged(QTreeWidgetItem*, QTreeWidgetItem*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7fa621121d91 in () at /usr/lib64/libQt5Widgets.so.5 #16 0x7fa6201aacc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #17 0x7fa62012f8fa in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () at /usr/lib64/libQt5Core.so.5 #18 0x7fa62012face in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () at /usr/lib64/libQt5Core.so.5 #19 0x7fa6210adbf4 in QAbstractItemView::mousePressEvent(QMouseEvent*) () at /usr/lib64/libQt5Widgets.so.5 #20 0x7fa6210f1f0a in QTreeView::mousePressEvent(QMouseEvent*) () at /usr/lib64/libQt5Widgets.so.5 #21 0x7fa620e9f3ba in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #22 0x7fa620f9943e in QFrame::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #23 0x7fa6210b494b in QAbstractItemView::viewportEvent(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #24 0x7fa6210f1870 in QTreeView::viewportEvent(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #25 0x7fa62017b0d3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #26 0x7fa620e5ee5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #27 0x7fa620e642cb in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #28 0x7fa62017ae95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #29 0x7fa620e63191 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib64/libQt5Widgets.so.5 #30 0x7fa620eb813b in () at /usr/lib64/libQt5Widgets.so.5 #31 0x7fa620eba353 in () at /usr/lib64/libQt5Widgets.so.5 #32 0x7fa620e5ee7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #33 0x7fa620e63cc8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #34 0x7fa62017ae95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #35 0x7fa6206cc8d4 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib64/libQt5Gui.so.5 #36 0x7fa6206ce0e5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib64/libQt5Gui.so.5 #37 0x7fa6206b31c8 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #38 0x7fa611940200 in () at /usr/lib64/libQt5XcbQpa.so.5 #39 0x7fa61b597c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #40 0x7fa61b597ed8 in () at /usr/lib64/libglib-2.0.so.0 #41 0x7fa61b597f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #42 0x7fa6201d1d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #43 0x7fa620178d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #44 0x7fa6201808f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #45 0x7fa6244a4958 in kdemain () at /usr/lib64/libkdeinit5_kmenuedit.so #46 0x7fa624105b05 in __libc_start_main () at /lib64/libc.so.6 #47 0x004007ee in _start () Reported using DrKonqi
[kmail2] [Bug 359587] New: akonadi server hangs and needs continual rebooting, email address autosuggest not working, using the "TO" column to select causes akonadi resource to crash
https://bugs.kde.org/show_bug.cgi?id=359587 Bug ID: 359587 Summary: akonadi server hangs and needs continual rebooting, email address autosuggest not working, using the "TO" column to select causes akonadi resource to crash Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: contact completion Assignee: m...@vhanda.in Reporter: diogenesqu...@gmail.com CC: dvra...@kde.org, mon...@kde.org For some months I have noticed that akonadi server freezes and has to be restarted. More recently I notice that autosuggest email addresses is not working for the vast majority of the email addresses in my address books. Now the solution I have used in the past, selecting from the "TO" column, causes akonadi resource to crash. Reproducible: Always Steps to Reproduce: 1.start Personal Information Manager (kmail) 2.open "new message" blank 3.attempt to type in start of email address (no response from autosuggest) 4. Click on "TO" which brings up my address books. Actual Results: At this point, sometimes even before I can enter anything into the search bar, I get the dismal error report "Akonadi resource has crashed" Expected Results: should be able to choose an email address by searching Application: kontact (5.0.2) Qt Version: 5.4.2 Operating System: Linux 4.2.0-27-generic i686 Distribution: Ubuntu 15.10 -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xad93d7c0 (LWP 6333))] Thread 7 (Thread 0xac12fb40 (LWP 6335)): #0 0xb77cabe8 in __kernel_vsyscall () #1 0xb2a4425c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb6098d46 in __pthread_cond_wait (cond=0xb5e2ed34, mutex=0xb5e2ed1c) at forward.c:149 #3 0xb519211a in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #4 0xb519216c in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #5 0xb2a3f1aa in start_thread (arg=0xac12fb40) at pthread_create.c:333 #6 0xb608c02e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 6 (Thread 0xab19ab40 (LWP 6336)): #0 0xb77cabe8 in __kernel_vsyscall () #1 0xb608142b in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0xb278e980 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb277ff1c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb2780054 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb65ab7e4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb654e2b3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb654e702 in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb637723d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb6377318 in QThread::run() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb637c65b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb2a3f1aa in start_thread (arg=0xab19ab40) at pthread_create.c:333 #12 0xb608c02e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 5 (Thread 0xa9fd2b40 (LWP 6337)): #0 0xb77cabe8 in __kernel_vsyscall () #1 0xb2a4425c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb6098d46 in __pthread_cond_wait (cond=0xab872138, mutex=0xab872120) at forward.c:149 #3 0xb51c0cec in WTF::ThreadCondition::wait(WTF::Mutex&) () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #4 0xb4e7f4c6 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #5 0xb51a92e2 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #6 0xb51c06f1 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #7 0xb2a3f1aa in start_thread (arg=0xa9fd2b40) at pthread_create.c:333 #8 0xb608c02e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122 Thread 4 (Thread 0xa95e0b40 (LWP 6338)): #0 0xb77cabe8 in __kernel_vsyscall () #1 0xb2a4425c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb6098d46 in __pthread_cond_wait (cond=0xab876734, mutex=0xab87671c) at forward.c:149 #3 0xb51c0cec in WTF::ThreadCondition::wait(WTF::Mutex&) () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #4 0xb4e805f5 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #5 0xb51a92e2 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #6 0xb51c06f1 in ?? () from /usr/lib/i386-linux-gnu/libQt5WebKit.so.5 #7 0xb2a3f1aa in start_thread (arg=0xa95e0b40) at pthread_create.c:333 #8 0xb608c02e in clone (
[kwin] [Bug 338999] [unspecific] Desktop freezes time to time on plasma 5 (collection of various unrelated problems, WONTFIX)
https://bugs.kde.org/show_bug.cgi?id=338999 Shkarlat Andrey changed: What|Removed |Added CC|andshkar...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 Ken Freeland changed: What|Removed |Added CC||diogenesqu...@gmail.com --- Comment #17 from Ken Freeland --- selecting from "TO" button crashes akonodi resource 9 times out of ten for me...it's not much of a solution to this dreadful issue -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 359316] do not show the documentation of k3b even I have looked for a package.
https://bugs.kde.org/show_bug.cgi?id=359316 Luigi Toscano changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED CC||luigi.tosc...@tiscali.it --- Comment #7 from Luigi Toscano --- I checked the state on Mint 12.3. This distribution is based on Ubuntu 14.04, with some extra packages. The packages which provide k3b (k3b, k3b-data and k3b-i18n) are taken directly from Ubuntu repositories. Unfortunately that specific version (2.0.2-7ubuntu1) does not provide translated documentation, and moreover the Ubuntu package does not ship even the English documentation (which was otherwise part of the sources available for packagers). The newer versions of k3b packages on Ubuntu contain the English documentation, but it is unlikely that they will be backported to that version of Ubuntu (and then available for Mint 12.3). Also, even those newer packages on Ubuntu do not contain translated documentation (which is not available). In any case, this is not something that it is possible to fix on our side (kde.org). You can still access the documentation online also from our website: http://docs.kde.org and specifically, the English version here: https://docs.kde.org/index.php?application=k3b and the German one here: https://docs.kde.org/index.php?application=k3b&language=de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359586] Effects dialog crashes when clicking the 'movie icon'
https://bugs.kde.org/show_bug.cgi?id=359586
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|UNCONFIRMED |NEEDSINFO
--- Comment #1 from Thomas Lübking ---
Can you provide a backtrace ("developer information" from the crash dialog)?
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 359583] Contrast effect collides with inversion effect
https://bugs.kde.org/show_bug.cgi?id=359583 Thomas Lübking changed: What|Removed |Added Summary|Transparency of menu during |Contrast effect collides |invert effect does not |with inversion effect |match the one with invert | |effect off | --- Comment #4 from Thomas Lübking --- Can you try whether "xcalib -a -i" works for you (same command will invert the inversion ;-) - you may have to install xcalib. @Martin https://bugs.kde.org/show_bug.cgi?id=337355#c8 Shall I add a "remove contrast effect (seriously)" review request? Afaics, it presently does nothing but waste resources and cause trouble. I'd frankly at least like to understand what it *wants* to do. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359558] System tray creating ghost entries
https://bugs.kde.org/show_bug.cgi?id=359558 --- Comment #2 from hector acosta --- I believe I've found a way to reproduce this. Using plasmashell 5.5.4 Connect an external monitor. Run kquitapp plasmashell Run plasmashell Connect a montior Run kequitapp plasmashell Run plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kshisen] [Bug 358773] kshisen shows as stuck when obvious moves remain
https://bugs.kde.org/show_bug.cgi?id=358773 --- Comment #6 from Frederik Schwarzer --- I am sorry but the situation here is unfortunate. 1. since that version, I changed quite some things in KShisen 2. I just started ripping it all apart because many parts of the code are old and not written by me (so I sometimes do not know how they are supposed to work) 3. KDevelop refuses to parse the 15.08 version so it does not help me at all while browsing the code 4. I tried to reproduce today again and failed with around 20 games. So, I believe you that there is a problem, but cannot reproduce it, have a hard time checking the related code for several reasons and also have problems wrapping my head around that specific code, which made me start a complete rewrite. Do you have any chance to install version 15.12? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359586] New: Effects dialog crashes when clicking the 'movie icon'
https://bugs.kde.org/show_bug.cgi?id=359586 Bug ID: 359586 Summary: Effects dialog crashes when clicking the 'movie icon' Product: kwin Version: 5.5.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: tho...@mitterfellner.at Running kcmshell5 kwineffects and clicking on one of the movie icons leads to a segfault. Unfortunately, I don't even know what that icon should do, supposedly a preview? Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 359404] Problem viewing graphic output in Windows
https://bugs.kde.org/show_bug.cgi?id=359404 --- Comment #5 from Thomas Friedrichsmeier --- Git commit 8b44b7547bb0d26b3d47cf39c12d35c6127b4975 by Thomas Friedrichsmeier. Committed on 19/02/2016 at 21:10. Pushed by tfry into branch 'releases/0.6.4'. Help webkit understand local file paths to images on Windows. NOTE: Bug ticket will be closed, once updates Windows binaries are available. M +12 -4rkward/rbackend/rpackages/rkward/R/public_graphics.R http://commits.kde.org/rkward/8b44b7547bb0d26b3d47cf39c12d35c6127b4975 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359583] Transparency of menu during invert effect does not match the one with invert effect off
https://bugs.kde.org/show_bug.cgi?id=359583 --- Comment #3 from Thomas Mitterfellner --- Indeed, disabling the contrast effect solves that problem. And yes, it's a full screen inversion. But I sometimes also use the window inversion. Thanks for the quick response! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #15 from Thomas Lübking --- The detection will be fine. The client simply does not set a WM_CLASS hint, so it's kinda "indetectable" :-( This patch may hunk but should apply to 5.4 (otherwise please ask back) If CEF is *not* violating the spec, your hyperactive rule should not apply to spotify anymore. But if it's this https://aur.archlinux.org/packages/spotify/ , I could just test it myself (the CEF thingy is somehow statically linked? I don't see relevant deps) - diff --git a/manage.cpp b/manage.cpp index 4198e60..41636be 100644 --- a/manage.cpp +++ b/manage.cpp @@ -627,6 +627,10 @@ bool Client::manage(xcb_window_t w, bool isMapped) } else updateVisibility(); assert(mapping_state != Withdrawn); + +xcb_connection_t *c = connection(); +free(xcb_get_input_focus_reply(c, xcb_get_input_focus(c), nullptr)); + m_managed = true; blockGeometryUpdates(false); -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225
Bob Wya changed:
What|Removed |Added
CC||bob.mt@gmail.com
--- Comment #21 from Bob Wya ---
I purposely don't unplug my external whilst using Plasma 5 - because of this
annoying bug!!
Playing fullscreen games (which alter xrandr settings) also will makes your
Plasma 5 panel(s) disappear... Logging out and logging back in brings it back -
but that is not exactly super-convenient!!
grep -B 6 -A 2 panel "${HOME}/.config/plasma-org.kde.plasma.desktop-appletsrc"
[Containments][1]
activityId=
formfactor=3
immutability=1
lastScreen=1
location=5
plugin=org.kde.panel
wallpaperplugin=org.kde.image
xrandr -q
Screen 0: minimum 8 x 8, current 4480 x 1630, maximum 16384 x 16384
VGA-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 1920x1080+2560+550 (normal left inverted right x axis y
axis) 382mm x 215mm
1920x1080 60.02*+
HDMI-0 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm
x 336mm
2560x1440 59.95*+
1920x1200 59.9559.88
1920x1080 60.0059.9450.0029.9760.0560.0050.04
1680x1050 59.95
1600x1200 60.00
1600x900 60.00
1280x1024 75.0260.02
1280x720 60.0059.9450.00
1152x864 75.00
1024x768 75.0360.00
800x600 75.0060.32
720x576 50.00
720x480 59.94
640x480 75.0059.9459.93
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 359584] W: kde-spectacle: desktop-mime-but-no-exec-code usr/share/applications/org.kde.spectacle.desktop
https://bugs.kde.org/show_bug.cgi?id=359584 --- Comment #1 from Boudhayan Gupta --- In the .desktop file, the MimeType field is empty. Could you try removing that line and see if Lintian stops crying? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing
https://bugs.kde.org/show_bug.cgi?id=359157 --- Comment #11 from Thomas Lübking --- Nope, it's (most likely just) focus stealing prevention. The dialog has no WM_CLASS nor any other relation to it's main window (the game) So not only is it NOT a transient (ie. marked to always stay above the game what's likely desired) nor can kwin determine that it's a related window. So it denies activation (and raising) This patch may resolve this (at least let it raise above) https://git.reviewboard.kde.org/r/124130/ The actual problem though is the complete lack of hints on the dialog, notably not being a transient as could be expected. You can confirm the above by setting the focus stealing prevention to "none" in "kcmshell5 kwinoptions", first tab. That however doesn't explain the inability to successfully focus the dialog. It neither provides WM_HINTS, but should be considered to take focus by default. What's suspicious is that the game window denies focus resp. relies on the wonky WM_TAKE_FOCUS protocol (*sigh*, I thought Java was the last remainder) to handle the focus assignment itself. => Can you activate any (other) window when alt+tabbing away from the game window and if so, what happens when you try to alt+tab to the dialog (not! the game) from that 3rd (eg. kwrite or dolphin) window? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 359585] New: plasma crashed
https://bugs.kde.org/show_bug.cgi?id=359585 Bug ID: 359585 Summary: plasma crashed Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fio_roj...@i.ua Application: plasma-desktop (4.11.16) KDE Platform Version: 4.14.5 Qt Version: 4.8.6 Operating System: Linux 4.1.15-desktop-2.mga5 i686 Distribution: "Mageia 5" -- Information about the crash: - Unusual behavior I noticed:2 panel create and vidget panel crached when 1st delete. thx - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: Оболочка Plasma (plasma-desktop), signal: Segmentation fault Using host libthread_db library "/lib/i686/libthread_db.so.1". [Current thread is 1 (Thread 0xb5035740 (LWP 2617))] Thread 7 (Thread 0xa2e66b40 (LWP 2618)): #0 0xb7745bc0 in __kernel_vsyscall () #1 0xb6aa8fab in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb05be07f in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib/libQtScript.so.4 #3 0xb05be0bc in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib/libQtScript.so.4 #4 0xb6aa4386 in start_thread () from /lib/i686/libpthread.so.0 #5 0xb5e0385e in clone () from /lib/i686/libc.so.6 Thread 6 (Thread 0xa123fb40 (LWP 2622)): #0 0xb7745bc0 in __kernel_vsyscall () #1 0xb5e11962 in clock_gettime () from /lib/i686/libc.so.6 #2 0xb6b7a949 in qt_gettime() () from /lib/libQtCore.so.4 #3 0xb6c63b83 in QTimerInfoList::timerWait(timeval&) () from /lib/libQtCore.so.4 #4 0xb6c62391 in timerSourcePrepareHelper(GTimerSource*, int*) () from /lib/libQtCore.so.4 #5 0xb6c6242d in timerSourcePrepare(_GSource*, int*) () from /lib/libQtCore.so.4 #6 0xb575632e in g_main_context_prepare () from /lib/libglib-2.0.so.0 #7 0xb5756d1c in g_main_context_iterate.isra () from /lib/libglib-2.0.so.0 #8 0xb5756f56 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #9 0xb6c62ca4 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/libQtCore.so.4 #10 0xb6c31883 in QEventLoop::processEvents(QFlags) () from /lib/libQtCore.so.4 #11 0xb6c31bbe in QEventLoop::exec(QFlags) () from /lib/libQtCore.so.4 #12 0xb6b1e760 in QThread::exec() () from /lib/libQtCore.so.4 #13 0xb6c1248b in QInotifyFileSystemWatcherEngine::run() () from /lib/libQtCore.so.4 #14 0xb6b21253 in QThreadPrivate::start(void*) () from /lib/libQtCore.so.4 #15 0xb6aa4386 in start_thread () from /lib/i686/libpthread.so.0 #16 0xb5e0385e in clone () from /lib/i686/libc.so.6 Thread 5 (Thread 0x9eda9b40 (LWP 11224)): #0 0xb7745bc0 in __kernel_vsyscall () #1 0xb6aa8fab in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb6b217bb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/libQtCore.so.4 #3 0xb0028170 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () from /lib/libthreadweaver.so.4 #4 0xb002b094 in ThreadWeaver::WorkingHardState::waitForAvailableJob(ThreadWeaver::Thread*) () from /lib/libthreadweaver.so.4 #5 0xb00280c4 in ThreadWeaver::WeaverImpl::waitForAvailableJob(ThreadWeaver::Thread*) () from /lib/libthreadweaver.so.4 #6 0xb002b16a in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () from /lib/libthreadweaver.so.4 #7 0xb0026f28 in ThreadWeaver::WeaverImpl::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () from /lib/libthreadweaver.so.4 #8 0xb0029b1d in ThreadWeaver::Thread::run() () from /lib/libthreadweaver.so.4 #9 0xb6b21253 in QThreadPrivate::start(void*) () from /lib/libQtCore.so.4 #10 0xb6aa4386 in start_thread () from /lib/i686/libpthread.so.0 #11 0xb5e0385e in clone () from /lib/i686/libc.so.6 Thread 4 (Thread 0x9bd2ab40 (LWP 11225)): #0 0xb7745bc0 in __kernel_vsyscall () #1 0xb6aa8fab in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0 #2 0xb6b217bb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/libQtCore.so.4 #3 0xb0028170 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () from /lib/libthreadweaver.so.4 #4 0xb002b094 in ThreadWeaver::WorkingHardState::waitForAvailableJob(ThreadWeaver::Thread*) () from /lib/libthreadweaver.so.4 #5 0xb00280c4 in ThreadWeaver::WeaverImpl::waitForAvailableJob(ThreadWeaver::Thread*) () from /lib/libthreadweaver.so.4 #6 0xb002b16a in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () from /lib/libthreadweaver.so.4 #7 0xb0026f28 in ThreadWeaver::WeaverImpl::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () from /lib/libthreadweaver.so.4 #8 0xb0029b1d in ThreadWeaver::Thread::run() () from /lib/libthreadweaver.so.4 #9 0xb6b21253 in QThreadPrivate::start(void*) () from /lib/libQtCore.so.4 #1
[krita] [Bug 359578] I can not set a tag for permanent display (many sessions of Krita) on Brush Presets Doker
https://bugs.kde.org/show_bug.cgi?id=359578 wolthera changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC||griffinval...@gmail.com --- Comment #1 from wolthera --- This is fixed in 3.0. It was an issue with the order of how resources are loaded. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 359584] New: W: kde-spectacle: desktop-mime-but-no-exec-code usr/share/applications/org.kde.spectacle.desktop
https://bugs.kde.org/show_bug.cgi?id=359584 Bug ID: 359584 Summary: W: kde-spectacle: desktop-mime-but-no-exec-code usr/share/applications/org.kde.spectacle.desktop Product: Spectacle Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: sgcl...@kubuntu.org W: kde-spectacle: desktop-mime-but-no-exec-code usr/share/applications/org.kde.spectacle.desktop Lintain error, please see: https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html Reproducible: Always Steps to Reproduce: 1. Package 2. compile 3. Lintian cries. Actual Results: Lintain error Expected Results: No error %f, %F, %u or %U for the Exec key -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359583] Transparency of menu during invert effect does not match the one with invert effect off
https://bugs.kde.org/show_bug.cgi?id=359583 --- Comment #2 from Thomas Lübking --- Can you please try to disable the contrast effect in "kcmshell5 kwineffects" Also, the screenshot looks like this is a fullscreen inversion? This should not run on the shaders at all (but on gamma ramps, which unlike the shaders is for free) => No xrandr or explicit invocation of the inversion effect? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 359357] Amarok skips tracks
https://bugs.kde.org/show_bug.cgi?id=359357 --- Comment #10 from sedrubal --- Ok it seems to appear with vlc and gstreamer phonon backend. But only when I start KDE; when I start i3wm and then amarok it doesn't happen... -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #49 from Andreas Hartmetz --- Git commit a08befeac43647e222f48dfd7bed067be81573c4 by Andreas Hartmetz. Committed on 19/02/2016 at 19:08. Pushed by ahartmetz into branch 'master'. KNotes: fix session save / restore. Requires Qt >= 5.6.0 or recent 5.6 branch. M +3-0knotes/src/apps/knotesapp.cpp http://commits.kde.org/kdepim/a08befeac43647e222f48dfd7bed067be81573c4 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #47 from Andreas Hartmetz --- Git commit 58e49487aece3de19aae90bbb9b80cd5aab94d04 by Andreas Hartmetz. Committed on 19/02/2016 at 18:55. Pushed by ahartmetz into branch 'master'. Fix session management for KApplication based applications. - Call QGuiApplication::setFallbackSessionManagementEnabled(false) to prevent premature application exit - Wire up the saveStateRequest() and commitDataRequest() signals to the appropriate methods that had to be turned into slots first. Those methods were never even called, they were not ported properly. - Cancel logout when the user decides to do that. A comment in the code was not sufficient to do that. (?!?!) M +16 -1src/kdeui/kapplication.cpp M +15 -14 src/kdeui/kapplication.h http://commits.kde.org/kdelibs4support/58e49487aece3de19aae90bbb9b80cd5aab94d04 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow different payees on splits
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #11 from Thomas Baumgart --- No, unfortunately it is not that easy. Additional code needs to be written in an area that is not maintained anymore. Means, I am currently planning to rewrite it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359583] Transparency of menu during invert effect does not match the one with invert effect off
https://bugs.kde.org/show_bug.cgi?id=359583 Thomas Mitterfellner changed: What|Removed |Added CC||tho...@mitterfellner.at --- Comment #1 from Thomas Mitterfellner --- Created attachment 97307 --> https://bugs.kde.org/attachment.cgi?id=97307&action=edit Picture demonstrating the problem -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 Andreas Hartmetz changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kxml ||gui/f7cbcc77722256db084d3b0 ||ab6ce76173e959f0e Status|REOPENED|RESOLVED --- Comment #47 from Andreas Hartmetz --- Git commit 58e49487aece3de19aae90bbb9b80cd5aab94d04 by Andreas Hartmetz. Committed on 19/02/2016 at 18:55. Pushed by ahartmetz into branch 'master'. Fix session management for KApplication based applications. - Call QGuiApplication::setFallbackSessionManagementEnabled(false) to prevent premature application exit - Wire up the saveStateRequest() and commitDataRequest() signals to the appropriate methods that had to be turned into slots first. Those methods were never even called, they were not ported properly. - Cancel logout when the user decides to do that. A comment in the code was not sufficient to do that. (?!?!) M +16 -1src/kdeui/kapplication.cpp M +15 -14 src/kdeui/kapplication.h http://commits.kde.org/kdelibs4support/58e49487aece3de19aae90bbb9b80cd5aab94d04 --- Comment #48 from Andreas Hartmetz --- Git commit f7cbcc77722256db084d3b0ab6ce76173e959f0e by Andreas Hartmetz. Committed on 19/02/2016 at 18:49. Pushed by ahartmetz into branch 'master'. Fix session management broken since KF5 / Qt5. Requires Qt 5.6 branch not more than a few days old, or >= 5.6.0 when it is released. Parts of the fix are: - Call QGuiApplication::setFallbackSessionManagementEnabled(false) to prevent application suicide through a mechanism that tries to help applications without any proper session management support, but badly interferes with applications that do implement proper session management, such as KDE applications. - Add back commitData[Request] handling. For some reason it was removed during porting. - Change the returned types of saveState() and commitData() to void. The return values were unused. M +41 -3src/kmainwindow.cpp M +2-1src/kmainwindow_p.h http://commits.kde.org/kxmlgui/f7cbcc77722256db084d3b0ab6ce76173e959f0e -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 Andreas Hartmetz changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kxml ||gui/f7cbcc77722256db084d3b0 ||ab6ce76173e959f0e Status|REOPENED|RESOLVED --- Comment #48 from Andreas Hartmetz --- Git commit f7cbcc77722256db084d3b0ab6ce76173e959f0e by Andreas Hartmetz. Committed on 19/02/2016 at 18:49. Pushed by ahartmetz into branch 'master'. Fix session management broken since KF5 / Qt5. Requires Qt 5.6 branch not more than a few days old, or >= 5.6.0 when it is released. Parts of the fix are: - Call QGuiApplication::setFallbackSessionManagementEnabled(false) to prevent application suicide through a mechanism that tries to help applications without any proper session management support, but badly interferes with applications that do implement proper session management, such as KDE applications. - Add back commitData[Request] handling. For some reason it was removed during porting. - Change the returned types of saveState() and commitData() to void. The return values were unused. M +41 -3src/kmainwindow.cpp M +2-1src/kmainwindow_p.h http://commits.kde.org/kxmlgui/f7cbcc77722256db084d3b0ab6ce76173e959f0e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359583] New: Transparency of menu during invert effect does not match the one with invert effect off
https://bugs.kde.org/show_bug.cgi?id=359583 Bug ID: 359583 Summary: Transparency of menu during invert effect does not match the one with invert effect off Product: kwin Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: tho...@mitterfellner.at When I invert screen colors, the start menu has too high a transparency making it hard to read if there's text behind it. Also, the entries on the panel including the systray are barely readable due to lacking contrast. I'try to attach a picture demonstrating that. The interesting thing is: I *think* it wasn't like that from the start but I'm not 100% sure. I think it became like this at some point when I was using the Show Mouse effect. Unfortunately. I cannot confirm this as it seems to be persistent also after rebooting (which is why I'm unsure whether it hasn't been like that from the beginning). Reproducible: Always I added kwin support info here: https://paste.kde.org/pqim8h9pk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #14 from Kiril Vladimiroff --- > a) Does that "Football Manager 2016" client never sport (pun intended) > a WM_CLASS hint, or did you set it empty manually (because it also > adds WM_CLASS late)? It doesn't detect it. Even now when I try to create a new rule for it, I get these lines via the "Detect window properties" button: wmclass= wmclasscomplete=false wmclassmatch=1 > b) The pretty much means CEF is setting WM_CLASS after the map > request, what's rather an icccm violation > > Strictly spoken though, it must be set as long as the window is > withdrawn, maybe they keep it that state until it gets actually mapped > (while that's not helpful ;-) > > => We might have to sync after mapping the window and before applying > the rules? Can you try a patch (for kwin) - doesn't make sense to > relax things here if the client sets WM_CLASS some seconds later. I'm currently running a KWin from an offical Arch Linux package, but I could try applying a patch and compiling kwin, as long as I can apply it on top of the 5.5.4 tag. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 357001] Font management tool does not render preview properly
https://bugs.kde.org/show_bug.cgi?id=357001 St Weiss changed: What|Removed |Added CC||x@autopray.com --- Comment #1 from St Weiss --- Duplicate, see #336089 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps
https://bugs.kde.org/show_bug.cgi?id=340267 --- Comment #34 from Aleix Pol --- @Thiago: Update to Qt 5.6 when it's available -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349519] plasmashell occasionally crashes
https://bugs.kde.org/show_bug.cgi?id=349519 David Edmundson changed: What|Removed |Added CC||p...@free.fr --- Comment #116 from David Edmundson --- *** Bug 359582 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359582] plasma desktop crashes
https://bugs.kde.org/show_bug.cgi?id=359582 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- brw_meta_fast_clear https://bugs.freedesktop.org/show_bug.cgi?id=86281 This is crashing in your graphic driver which we can't do much about. Please upgrade/downgrade your version of mesa. See information (including a workaround) in the linked report. *** This bug has been marked as a duplicate of bug 349519 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359582] New: plasma desktop crashes
https://bugs.kde.org/show_bug.cgi?id=359582 Bug ID: 359582 Summary: plasma desktop crashes Product: plasmashell Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: p...@free.fr CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.2.0-27-lowlatency x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I was just hovering the mouse over the weather widget and the thermal monitor in the taskbar from the dragon player window which was playing a video - Unusual behavior I noticed: as soon as i hover on theses widget plasma crashed, maybe trying to pop up an information window -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa5831d2800 (LWP 2532))] Thread 9 (Thread 0x7fa56e6fd700 (LWP 2534)): #0 0x7fa57d8e488d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa5819b2bd2 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa5819b474f in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa5708467e9 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fa57dfdaa6e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa57d0c66aa in start_thread (arg=0x7fa56e6fd700) at pthread_create.c:333 #6 0x7fa57d8efe9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fa567dfa700 (LWP 2574)): #0 0x7fa57d8e488d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fa57a67a1ec in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7fa560003070, timeout=, context=0x7fa56990) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:4135 #2 0x7fa57a67a1ec in g_main_context_iterate (context=context@entry=0x7fa56990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3835 #3 0x7fa57a67a2fc in g_main_context_iteration (context=0x7fa56990, may_block=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3901 #4 0x7fa57e21250b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa57e1b950a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa57dfd5ac4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa580883c35 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fa57dfdaa6e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa57d0c66aa in start_thread (arg=0x7fa567dfa700) at pthread_create.c:333 #10 0x7fa57d8efe9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fa55c85a700 (LWP 2586)): #0 0x7fa57a6be869 in g_mutex_lock (mutex=mutex@entry=0x7fa558000990) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gthread-posix.c:1338 #1 0x7fa57a679657 in g_main_context_prepare (context=context@entry=0x7fa558000990, priority=priority@entry=0x7fa55c859c70) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3382 #2 0x7fa57a67a11b in g_main_context_iterate (context=context@entry=0x7fa558000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3820 #3 0x7fa57a67a2fc in g_main_context_iteration (context=0x7fa558000990, may_block=1) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3901 #4 0x7fa57e21250b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa57e1b950a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa57dfd5ac4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa580883c35 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fa57dfdaa6e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa57d0c66aa in start_thread (arg=0x7fa55c85a700) at pthread_create.c:333 #10 0x7fa57d8efe9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fa5569da700 (LWP 2597)): #0 0x7fa57a6be884 in g_mutex_unlock (mutex=0x7fa55990) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gthread-posix.c:1350 #1 0x7fa57a679770 in g_main_context_prepare (context=context@entry=0x7fa55990, priority=priority@entry=0x7fa5569d9c70) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gmain.c:3440 #2 0x7fa57a67a11b in g_main_context_iterate (context=context@entry=0x7fa55990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-ajuDY6/glib2.0-2.46
[kwin] [Bug 359188] kwin_x11 crashes if Minecraft 1.6.4 (Modded) starts and finishing loading
https://bugs.kde.org/show_bug.cgi?id=359188 Thomas Lübking changed: What|Removed |Added Status|VERIFIED|RESOLVED --- Comment #10 from Thomas Lübking --- crashes on randr events are a common bug in qt5, see bug #341497 on details - that doesn't indicate anything and is not related to the VBO transfer problem (which is probably the cause for the screen distortion and *may* crash kwin as well, but on different stack positions) So again: you added the blocking rule to mitigate the distortion? -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 358392] Key could not be certified. Certificate expired, but NOT!
https://bugs.kde.org/show_bug.cgi?id=358392 Andre Heinecke changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/3059055775c4921db3d56de9 ||f6b0a12579a15f3b Status|CONFIRMED |RESOLVED --- Comment #4 from Andre Heinecke --- Git commit 3059055775c4921db3d56de9f6b0a12579a15f3b by Andre Heinecke. Committed on 19/02/2016 at 17:59. Pushed by aheinecke into branch 'master'. Do not show unusable certificates for certify Trying to certify a UID with a revoked or expired certificate fails in GnuPG. So Kleopatra should not even offer that. M +8-6kleopatra/commands/certifycertificatecommand.cpp http://commits.kde.org/kdepim/3059055775c4921db3d56de9f6b0a12579a15f3b -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 358392] Key could not be certified. Certificate expired, but NOT!
https://bugs.kde.org/show_bug.cgi?id=358392 Andre Heinecke changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Andre Heinecke --- The error indicates that the Certificate you want to use is expired and not that the certificate you are trying to sign is expired. So check that your own certificate that you want to use to certifiy facebooks certificate is not expired. Kleopatra should not offer to use an expired certificate for certification. I've just checked that it does and this leads to exactly your error (the error comes from gnupg so nothing we can do about that). I'll fix that you can't select expired or revoked certificates for certification anymore. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 226630] kwatchgnupg appends invalid options to ~/.gnupg/gpg.conf
https://bugs.kde.org/show_bug.cgi?id=226630 Nick changed: What|Removed |Added CC||futurepi...@gmx.us -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359498] crash at login of new user
https://bugs.kde.org/show_bug.cgi?id=359498 31i73h4c...@mail.ru changed: What|Removed |Added CC||31i73h4c...@mail.ru --- Comment #1 from 31i73h4c...@mail.ru --- *** Bug 359510 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing
https://bugs.kde.org/show_bug.cgi?id=359157 --- Comment #10 from antti --- Added xwininfo and xprop outputs and a new list. What do you mean by updating the tree? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359510] Plasma crashes right after entering password on new user
https://bugs.kde.org/show_bug.cgi?id=359510 31i73h4c...@mail.ru changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |DUPLICATE --- Comment #2 from 31i73h4c...@mail.ru --- Thanks, geolele. This seems to be a duplicate. *** This bug has been marked as a duplicate of bug 359498 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing
https://bugs.kde.org/show_bug.cgi?id=359157 --- Comment #9 from antti --- Created attachment 97306 --> https://bugs.kde.org/attachment.cgi?id=97306&action=edit xprop for the dialog -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing
https://bugs.kde.org/show_bug.cgi?id=359157 --- Comment #8 from antti --- Created attachment 97305 --> https://bugs.kde.org/attachment.cgi?id=97305&action=edit xprop for UT4 main window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing
https://bugs.kde.org/show_bug.cgi?id=359157 --- Comment #7 from antti --- Created attachment 97304 --> https://bugs.kde.org/attachment.cgi?id=97304&action=edit xwininfo for the dialog -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing
https://bugs.kde.org/show_bug.cgi?id=359157 --- Comment #6 from antti --- Created attachment 97303 --> https://bugs.kde.org/attachment.cgi?id=97303&action=edit xwininfo for UT4 main window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359157] Unreal Tournament 4 first startup causes partial freezing
https://bugs.kde.org/show_bug.cgi?id=359157 antti changed: What|Removed |Added Attachment #97267|0 |1 is obsolete|| --- Comment #5 from antti --- Created attachment 97302 --> https://bugs.kde.org/attachment.cgi?id=97302&action=edit xwininfo -root -tree (2) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359510] Plasma crashes right after entering password on new user
https://bugs.kde.org/show_bug.cgi?id=359510 31i73h4c...@mail.ru changed: What|Removed |Added Platform|Compiled Sources|Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359188] kwin_x11 crashes if Minecraft 1.6.4 (Modded) starts and finishing loading
https://bugs.kde.org/show_bug.cgi?id=359188 Linus changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #9 from Linus --- I think yes, because I had a similar bug a long time ago with Plasma where Kwin mostly crashing everytime, I adding/removing/activating/deactivating a monitor. Currently I have two Monitors: DVI (BenQ): Primary Monitor [1920x1080] VGA (Samsung TFT): Secondary Monitor [1024x768] HDMI (Samung SmartTV): Gaming Monitor (uses when play Steam-Games with Controller) [1920x1080; Mirror of BenQ] Screenshot of KDE's Monitor-Settings: http://i.epvpimg.com/pkvcd.png Everytime I starting my SmartTV (if not at current boot), kwin crashes. My Laptop which I using in School and which is running ArchLinux with latest Updates, crashes often when I unplug a Monitor. But then kwin restarts and shows me a Crash-Dialog. It seems that kwin has mayor problems with multiple Monitors or screen resolutions. I think that it isn't a fault of my Nvidia GTX 750 Ti because my Laptop only has a Intel i3 with HD Graphics 2000 which should work fine on Linux. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 359581] New: wrong file permissions (umask 000) when using right click -> create new file
https://bugs.kde.org/show_bug.cgi?id=359581 Bug ID: 359581 Summary: wrong file permissions (umask 000) when using right click -> create new file Product: dolphin Version: 15.12.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ndcunli...@gmail.com If new text or html document is created using the right click menu, then ALL permissions are set to read and write (my default umask is 022). Have tested touch from shell, kwrite (from shell and menu) etc and they give the correct permissions. Reproducible: Always Steps to Reproduce: 1. start dolphin 2. right click in any home folder -> create new text file 3. right click - view properties/permissions Actual Results: mask 000 Expected Results: mask 022 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359580] New: High CPU usage
https://bugs.kde.org/show_bug.cgi?id=359580 Bug ID: 359580 Summary: High CPU usage Product: plasmashell Version: 5.5.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kdde@porcupinefactory.org CC: bhus...@gmail.com, plasma-b...@kde.org Plasma shell CPU usage is high for no apparent reason. It starts at about 5% at restartand increases at least up to 90% over the course of a few hours. It takes about the amount of time to write this bug report to cross the 7% threshold and stay there. Reproducible: Always Steps to Reproduce: 1. (re)Start plasma: kbuildsycoca5 && kquitapp5 plasmashell && kstart5 plasmashell 2. Use the desktop Actual Results: CPU usage increases. Expected Results: CPU usage stays around initial level. Plasmoids: clock, task switcher, CPU/RAM/net monitors, desktop switcher, activity switcher, icons, system tray, launchers, folder view. Standard Fedora panel items: battery, GTK systray, clipboard, mixer etc. All plasmoids on the panel only. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 341293] Kleopatra self-test should not expect gpg-agent to be running for GnuPG >= 2.1
https://bugs.kde.org/show_bug.cgi?id=341293 Andre Heinecke changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/cf2d87748a9204552f9e52e2 ||6743f8fa651e9f05 Status|CONFIRMED |RESOLVED --- Comment #3 from Andre Heinecke --- Git commit cf2d87748a9204552f9e52e26743f8fa651e9f05 by Andre Heinecke. Committed on 19/02/2016 at 17:25. Pushed by aheinecke into branch 'master'. Assume we have a gpg-agent for 2.1.x gnupg With 2.1 the gpg-agent is no longer optional. It's also started by GnuPG itself so we no longer have to check for installation / configuration problems regarding the gpg-agent. M +6-0kleopatra/selftest/gpgagentcheck.cpp http://commits.kde.org/kdepim/cf2d87748a9204552f9e52e26743f8fa651e9f05 -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 341293] Kleopatra self-test should not expect gpg-agent to be running for GnuPG >= 2.1
https://bugs.kde.org/show_bug.cgi?id=341293 Andre Heinecke changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||aheine...@intevation.de Ever confirmed|0 |1 --- Comment #2 from Andre Heinecke --- Sorry for the delay, I'm still autostarting gpg-agent on my system (as I use gpg-agent for SSH) and so I have not noticed this. But you are right. I'll fix it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 359512] xx.jpg2614 files
https://bugs.kde.org/show_bug.cgi?id=359512 --- Comment #4 from caulier.gil...@gmail.com --- Exiv2 0.25. 0.24 is full of bugs... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 359512] xx.jpg2614 files
https://bugs.kde.org/show_bug.cgi?id=359512 --- Comment #3 from Martin Zahnd --- problem is, I can write just one Comment (Beschreibung) in the picture. When I edis this comment later, nothing happen and then, I get the temp exiv file. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 359579] New: Add account function doesn't work
https://bugs.kde.org/show_bug.cgi?id=359579 Bug ID: 359579 Summary: Add account function doesn't work Product: choqok Version: 1.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: mehrdad.mom...@gmail.com Reporter: jsg...@systemli.org CC: scarp...@kde.org When I go to "Settings" - "Configure Choqok" - "Accounts" and then click on "Add Account", nothing happens and the "Add account" wIndow doesn't appear. The "add account" button stays pressed nonetheless. It is not possible to add any account. Reproducible: Always Steps to Reproduce: 1. Click on Settings 2. Click on Configure Choqok 3. Click on Accounts 4. Click on Add Account Actual Results: Nothing. It was not possible to add an account. Expected Results: The "Add Account" window should have appeared so I can add an account and actually use the application. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336570] Task list not updated in multiscreen setup
https://bugs.kde.org/show_bug.cgi?id=336570 --- Comment #19 from Bernd Steinhauser --- Ok, was a bit fast there. I missed, that you have to come from the side of showing only tasks from the current screen on all screens featuring a task list. It does work if you let one stay with the feature deactivated and only activate for one of them. As soon as you activate it for both (or all of them) and then change it back, it starts to go wrong. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 359512] xx.jpg2614 files
https://bugs.kde.org/show_bug.cgi?id=359512 --- Comment #2 from Martin Zahnd --- ou shit, since 13.12.2015 exiv comments are wrong in my picture. 12.12 I installed the new Opensuse leap. shit! whitch is the right exiv2 version do you recommend? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 154839] Allow alternate shortcuts in list of global shortcuts
https://bugs.kde.org/show_bug.cgi?id=154839 --- Comment #18 from Bernd Steinhauser --- In Plasma 5 at least this feature is present, so I guess this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359510] Plasma crashes right after entering password on new user
https://bugs.kde.org/show_bug.cgi?id=359510 geol...@gmail.com changed: What|Removed |Added CC||geol...@gmail.com --- Comment #1 from geol...@gmail.com --- Hi, I think this is the same bug listed here: https://bugs.kde.org/show_bug.cgi?id=359498 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359578] New: I can not set a tag for permanent display (many sessions of Krita) on Brush Presets Doker
https://bugs.kde.org/show_bug.cgi?id=359578 Bug ID: 359578 Summary: I can not set a tag for permanent display (many sessions of Krita) on Brush Presets Doker Product: krita Version: 2.9.11 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: avelinodesabb...@alice.it Hi, I do not know if this is a bug or is there a setting that I not find: I hold Doker "Brush presets" always open on the second monitor and I want them to be displayed all the brush (All) or the brush with a tag of my choice. For some time now, however, the Doker opens with a selected tag (Smudge) and even if I change it (or I select "All") on the next restart of Krita the Doker reopen with the Smudge selected tag. The problem is not critical but annoying: it is fixable? Thank you. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 359576] Connection to icewarp imap server broken on each incoming message
https://bugs.kde.org/show_bug.cgi?id=359576 --- Comment #2 from Marcel Šebek --- Created attachment 97301 --> https://bugs.kde.org/attachment.cgi?id=97301&action=edit connection log Here is the log. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359457] impossible edit long (multiline) filename in folder widget (or in desktop with folder view)
https://bugs.kde.org/show_bug.cgi?id=359457 --- Comment #2 from painless roaster --- try: example 1: - create file with too long filename - find file in folder widget - enter to rename (rename rectangle shift to right down - why?) - old filename has complete select and caret blink after last char - try press left cursor shift for modify last char - caret skip to begin of filename - why? example 2: - create file with filename contain name and extension - find file in folder widget - enter to rename - old filename has complete select with extension - why? - old version kde (kde4) select only filename for simple modification filename and keep extension example 3: - create new file on desktop in folder view mode - move file to needed position - rename file - file (icon) not keep in old position - why? It all worked well in the old version (kde4). --- (sorry for my bad english) -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 359576] Connection to icewarp imap server broken on each incoming message
https://bugs.kde.org/show_bug.cgi?id=359576 Jan Kundrát changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Jan Kundrát --- Could you please attach a full log from the IMAP session? You can find it in IMAP -> Debugging -> Show IMAP Protocol Log, and copy the content of the tab which matches that failing connection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341674] High CPU load when using second panel in multiscreen setup
https://bugs.kde.org/show_bug.cgi?id=341674 Bernd Steinhauser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #29 from Bernd Steinhauser --- Retested with 5.5.5 and things look much better now. CPU load is still a tad higher with multiple panels, but it doesn't raise over time and doesn't consume 100% of a cpu core. Thus closing with worksforme. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 357933] Kleopatra 15.12.1 (2.2): load certifications (pgp) - segfault after infinite recursion
https://bugs.kde.org/show_bug.cgi?id=357933 --- Comment #6 from Till Schäfer --- neat, thx -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358161] kdenlive-git HEAD shows black clip when using GPU/movit and GLES2
https://bugs.kde.org/show_bug.cgi?id=358161 Paul Konecny changed: What|Removed |Added CC||p...@konecny.at --- Comment #22 from Paul Konecny --- I'm not sure if this is related but this sounds an awful lot like the glitches I encountered here: https://bugs.kde.org/show_bug.cgi?id=355398 Rendering of /home/paul/Unbenannt12.mp4 crashed medium: [ ref=1, _mlt_properties_load=medium, __mlt_properties_load=medium ] Movit system requirements: Needs at least GLSL version 1.30 (has version 1,0) [consumer qglsl] OpenGL Shading Language rendering is not supported on this machine. [filter avcolor_space] Invalid format glsl [filter avcolor_space] Invalid format glsl GL error 502 at /home/paul/rebuild/4/src/kdenlive/src/monitor/glwidget.cpp : 406 [filter avcolor_space] Invalid format glsl -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 359568] If password checking takes too long, password appears to have been rejected
https://bugs.kde.org/show_bug.cgi?id=359568 --- Comment #3 from Martin Gräßlin --- sorry, but this looks like intended behavior: https://quickgit.kde.org/?p=plasma-workspace.git&a=blob&h=03ac02149ca8c7db133c42aa39fd7f9d946dda51&hb=a56f6c9d98197541663713978d5a754fa667a15a&f=lookandfeel%2Fcontents%2Flockscreen%2FMainBlock.qml#l99 While the password gets verified the input field is disabled and after a timeout of 3 sec the password field is cleared and enabled again. I don't see a bug there. The better question is: why does checking the password takes so long in your case that it hits the boundaries of the safe guards? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 359577] New: 15.13 git master: end keyframe lost on transition move or project upgrade
https://bugs.kde.org/show_bug.cgi?id=359577 Bug ID: 359577 Summary: 15.13 git master: end keyframe lost on transition move or project upgrade Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: wegwerf-1-...@gmx.de I've seen this problem with two projects I'm currently working on. In both cases I've copied over two different existing Kdenlive 15.13 project created just before the advent of the new keyframe code. Both projects contain an SVG title clip with a composite transition. In both cases this composite transition "lost" the keyframe at its end. In fact it appears as if the last keyframe is still present, yet out of reach: when moving on the timeline the fade out set on the final keyframe is present, yet this keyframe isn't shown and cannot be edited or deleted. When adding a new final keyframe another bug kicks in: instead of taking over the settings from its immediately preceeding keyframe, keyframe parameters get reset. When deleting this final keyframe and immediately recreating it again, then the keyframe parameters correctly get taken over from the preceeding keyframe. Reproducible: Always Expected Results: Keyframe at end of transition should not get lost or moved out of reach. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 290186] Add keyboard shortcut to assign a face tag
https://bugs.kde.org/show_bug.cgi?id=290186 --- Comment #8 from jat...@gmail.com --- Hi GIlles, It's suitable for me, but I didn't open the initial bug, so I can't speak for everyone. If it is not incredibly difficult, having the ability to use a keyboard shortcut to initiate the process would be helpful. I could picture a faster workflow where a keyboard shortcut initiates a face tag of predefined size at the current cursor position. That would eliminate the slowest part of the process, which is dragging the mouse to make the box a certain size. Usually in one group of photos (at least for me), most faces are about the same size, so this could certainly speed up the process. - Josh -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 290186] Add keyboard shortcut to assign a face tag
https://bugs.kde.org/show_bug.cgi?id=290186 --- Comment #7 from jat...@gmail.com --- Hi GIlles, It's suitable for me, but I didn't open the initial bug, so I can't speak for everyone. If it is not incredibly difficult, having the ability to use a keyboard shortcut to initiate the process would be helpful. I could picture a faster workflow where a keyboard shortcut initiates a face tag of predefined size at the current cursor position. That would eliminate the slowest part of the process, which is dragging the mouse to make the box a certain size. Usually in one group of photos (at least for me), most faces are about the same size, so this could certainly speed up the process. - Josh -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 357933] Kleopatra 15.12.1 (2.2): load certifications (pgp) - segfault after infinite recursion
https://bugs.kde.org/show_bug.cgi?id=357933 Andre Heinecke changed: What|Removed |Added Version Fixed In||16.04 --- Comment #5 from Andre Heinecke --- I've reworked the model for this so that it is more usable in the future. In the long term I have in mind that I also want to show certifications better in the treeview. Now at least it does not crash anymore. I've also changed that you no longer have to click "load certifications" as I this is very quick in my experience even for extremely large keys. And saving a click if a user already navigated into the details is good. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 357933] Kleopatra 15.12.1 (2.2): load certifications (pgp) - segfault after infinite recursion
https://bugs.kde.org/show_bug.cgi?id=357933 Andre Heinecke changed: What|Removed |Added Latest Commit||http://commits.kde.org/kdep ||im/35bbcb687537628e0c7facc8 ||3ca2c175e3d22d3b Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Andre Heinecke --- Git commit 35bbcb687537628e0c7facc83ca2c175e3d22d3b by Andre Heinecke. Committed on 19/02/2016 at 14:22. Pushed by aheinecke into branch 'master'. Refactor UserID Certificate details The old code was obscurely optimized to avoid copying data for the useridmodel. The userID model is fairly small as it only works with the Signatures of the UIDs of a single key. In most cases this is not much data. Keys with more then a thousand signatures are rare and even those modern Systems handle easily. Reflecting this the option to specifically load certifications is gone. Even for keys with lots of signatures liek 0xE3EDFAE3 or 0xD21739E9 this feels like instant. So no need to hassle a user that explicitly selects UserID and Certification details with yet another click to load them. This also changes the UserIDListModel API to a Qt API. REVIEW: 127059 M +14 -32 kleopatra/dialogs/certificatedetailsdialog.cpp M +0-1kleopatra/dialogs/certificatedetailsdialog.h M +0-10 kleopatra/dialogs/certificatedetailsdialog.ui M +185 -239 kleopatra/models/useridlistmodel.cpp M +10 -32 kleopatra/models/useridlistmodel.h http://commits.kde.org/kdepim/35bbcb687537628e0c7facc83ca2c175e3d22d3b -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356315] 15.13 git master: support split view in project monitor similar to split view in clip monitor
https://bugs.kde.org/show_bug.cgi?id=356315 --- Comment #4 from wegwerf-1-...@gmx.de --- Jean-Baptiste, this way too cool! Works like a charm. Just tried it on an existing project and this is really a great Kdenlive improvement. Thank you very much for implementing this! -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 359576] New: Connection to icewarp imap server broken on each incoming message
https://bugs.kde.org/show_bug.cgi?id=359576 Bug ID: 359576 Summary: Connection to icewarp imap server broken on each incoming message Product: trojita Version: 0.6 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP Assignee: trojita-b...@kde.org Reporter: sebe...@post.cz When a message is received, the following error dialogs are shown: The IMAP server sent us a reply which we could not parse. This might either mean that there's a bug in Trojitá's code, or that the IMAP server you are connected to is broken. Please report this as a bug anyway. Here are the details: UnknownMessageIndex: Got FETCH that is out of bounds -- got 0 messages FETCH 1 ( FLAGS "\Recent") Opening mailbox "INBOX" failed with the following message: The connection is being killed for unspecified reason Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356315] 15.13 git master: support split view in project monitor similar to split view in clip monitor
https://bugs.kde.org/show_bug.cgi?id=356315 --- Comment #3 from Jean-Baptiste Mardelle --- Git commit 061d6b2a34f1df054e8373bb2db227f5527a3e99 by Jean-Baptiste Mardelle. Committed on 19/02/2016 at 13:48. Pushed by mardelle into branch 'master'. Move split effect feature from monitor to effect stack, now also works in timeline M +34 -1src/effectstack/effectstackview2.cpp M +9-6src/effectstack/effectstackview2.h M +17 -0src/mainwindow.cpp M +3-0src/mainwindow.h M +72 -73 src/monitor/monitor.cpp M +8-6src/monitor/monitor.h M +11 -2src/project/effectsettings.cpp M +2-0src/project/effectsettings.h M +4-0src/project/projectmanager.cpp M +14 -0src/timeline/customtrackview.cpp M +3-0src/timeline/customtrackview.h M +68 -8src/timeline/timeline.cpp M +8-0src/timeline/timeline.h http://commits.kde.org/kdenlive/061d6b2a34f1df054e8373bb2db227f5527a3e99 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359171] paint strokes with tablet less fluent than in 2.9.6
https://bugs.kde.org/show_bug.cgi?id=359171 wolthera changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #7 from wolthera --- Thanks guys! Considering there's two of you now, I'll set this to confirmed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 342401] allow different payees on splits
https://bugs.kde.org/show_bug.cgi?id=342401 --- Comment #10 from harry bennett --- Are you implying that it may be as simple as just 'enabling' it? -- You are receiving this mail because: You are watching all bug changes.
