[plasmashell] [Bug 381048] MEMORY LEAK
https://bugs.kde.org/show_bug.cgi?id=381048 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Those backtraces only cover the definitely lost which amounts to a whopping 3,168 bytes. Not really worth looking at. The ==4325==still reachable: 2,529,068 bytes in 53,866 blocks is more relevant, but your traces don't cover that. I did fix a huge leak in frameworks 5.35. Please confirm if you have this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381090] New: use of a tablett
https://bugs.kde.org/show_bug.cgi?id=381090 Bug ID: 381090 Summary: use of a tablett Product: krita Version: 3.1.3 Platform: unspecified OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: wilhelmhk...@aol.com Target Milestone: --- Hello! I've installed a grafiik Tablett huuion G10T at my Windows 7 -64bit PC. Drivers are installed and the Control program for the Tablett works (with the mouse) If i choose the nmenu Point"Einstellungen - Krita einrichten - Tablett Einstellungen" The Input Pressure Global Curve appears. How can i activate my Graqfiktablett under Krita that Krita works with the Tablett and not with the mouse? br Wilhelm Koen -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 379739] insane baloo_file (and plasmashell) 256 GB virtual memory size
https://bugs.kde.org/show_bug.cgi?id=379739 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #5 from David Edmundson --- Virtual memory is just that, virtual. You don't need that size mapping in a VM. You don't need any more actual memory. It's not a relevant number of anything. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 381087] Newly ported KF5 .desktop Exec line contains an invalid -caption option preventing ksudoku from launching via the icon menu.
https://bugs.kde.org/show_bug.cgi?id=381087 Rik Mills changed: What|Removed |Added CC||rikmi...@kubuntu.org --- Comment #2 from Rik Mills --- -qwindowtitle should be used in place of -caption AFAIK, for Qt5/KF5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372384] Memory leak in plasmashell
https://bugs.kde.org/show_bug.cgi?id=372384 --- Comment #12 from David Edmundson --- There was a significant memory leak fix in frameworks 5.35 Please let us know if that had any impact. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 381091] New: Default setting in pulseaudio KCM overrule priority settings
https://bugs.kde.org/show_bug.cgi?id=381091 Bug ID: 381091 Summary: Default setting in pulseaudio KCM overrule priority settings Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_phonon Assignee: sit...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- hi there with recent changes, the multimedia KCM act differently: http://funkyimg.com/i/2u7hX.png there is now a default setting for the sound in and output, which was not there before and it seems to overrule the priority setting: http://funkyimg.com/i/2u7i3.png is there any way to reverse this? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 381091] Default setting in pulseaudio KCM overrule priority settings
https://bugs.kde.org/show_bug.cgi?id=381091 Harald Sitter changed: What|Removed |Added Version|unspecified |5.10.0 CC||plasma-b...@kde.org Component|kcm_phonon |kcm Assignee|sit...@kde.org |now...@gmail.com Product|systemsettings |plasma-pa -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 380414] Plasma pa breaks automatic device selection
https://bugs.kde.org/show_bug.cgi?id=380414 David Rosca changed: What|Removed |Added CC||shaloksha...@protonmail.ch --- Comment #3 from David Rosca --- *** Bug 381091 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 381091] Default setting in pulseaudio KCM overrule priority settings
https://bugs.kde.org/show_bug.cgi?id=381091 David Rosca changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Rosca --- *** This bug has been marked as a duplicate of bug 380414 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 381092] New: interfaces displayed not the ones selected
https://bugs.kde.org/show_bug.cgi?id=381092 Bug ID: 381092 Summary: interfaces displayed not the ones selected Product: plasma-nm Version: 5.9.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: kol...@aon.at Target Milestone: --- My "ifconfig" shows 3 interfaces: eth1 lo usb0 The settings dialog of the applet shows these: usb0 wlan1 eth1 When I enable all of the 3 in the dialog, clicking OK shows in the applet now FIVE interfaces: eth0 wlan0 eth1 usb0 wlan1 Right-click on the applet -> Network Monitor Settings now shows again usb0 wlan1 eth1 but NONE of these 3 is checked now, although I checked all of them before. Checking usb0 leads to suddenly ALL of the three being checked. Very strange things happen here... Note that my laptop has a wlan device, but in the nm-settings I disabled wlan. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381085] Use of SXTX in a memory address is treated as an illegal instruction on Aarch64
https://bugs.kde.org/show_bug.cgi?id=381085 isaacos...@hotmail.com changed: What|Removed |Added Version|3.11.0 |3.12.0 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 381068] There are two actions (Ausschneiden, Löschen) that want to use the same shortcut (Umschalt+Entf). This is most probably a bug. Please report it in bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=381068 Burkhard Lueck changed: What|Removed |Added Resolution|--- |DUPLICATE CC||lu...@hube-lueck.de Status|UNCONFIRMED |RESOLVED --- Comment #1 from Burkhard Lueck --- *** This bug has been marked as a duplicate of bug 377880 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 377880] Gwenview There are two actions (Cut, Delete)
https://bugs.kde.org/show_bug.cgi?id=377880 Burkhard Lueck changed: What|Removed |Added CC||fritz.ruess...@gmail.com --- Comment #12 from Burkhard Lueck --- *** Bug 381068 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381093] New: Error during vcdxrip
https://bugs.kde.org/show_bug.cgi?id=381093 Bug ID: 381093 Summary: Error during vcdxrip Product: k3b Version: 2.0.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video CD project Assignee: k...@kde.org Reporter: ganesh...@gmail.com CC: ch...@ckvsoft.at, mich...@jabster.pl, tr...@kde.org Target Milestone: --- Devices --- HL-DT-ST DVDRAM GH24NS72 WM00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] System --- K3b Version: 2.0.3 KDE Version: 4.14.16 QT Version: 4.8.7 Kernel: 4.4.0-79-generic vcdxrip --- **ERROR: psd offset out of range in extended PSD (try --no-ext-psd option) vcdxrip command: --- --gui --progress -i /dev/sr0 -o /dev/null -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 338672] Can't create folder on IMAP server
https://bugs.kde.org/show_bug.cgi?id=338672 --- Comment #8 from Tom Chiverton --- Fixed in latest KDE Neon release (5.5.2) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379189] Delete does not work for multiselection
https://bugs.kde.org/show_bug.cgi?id=379189 Tom Chiverton changed: What|Removed |Added CC||bugs.kde@falkensweb.com --- Comment #2 from Tom Chiverton --- Still present in latest KDE Neon (v5.5.2). Single delete on messages in my IMAP inbox works. Shift-select many and press delete, none of them are removed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380182] deleting several messages doesn't remove them from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 David Faure changed: What|Removed |Added CC||fa...@kde.org, ||kol...@etm.at --- Comment #5 from David Faure --- The new if (with early return) from commit 2edac82af (https://phabricator.kde.org/D5552, Martin Koller) is the reason for this bug. When moving (not deleting) multiple messages from a folder (including moving to trash, or archiving), the early return hits and the ETM doesn't notify of the removal. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 349904] Colgado cargando en Onedrive
https://bugs.kde.org/show_bug.cgi?id=349904 ralfgesellensetter changed: What|Removed |Added CC||r...@skolelinux.de --- Comment #1 from ralfgesellensetter --- If my Spanish is good enough, I am facing exactly the same problem: Observed: 1. Download a folder from MS OneDrive as ZIP archive. 2. Try to open ZIP file with ARK Expected Result: Ark opens archive. Observed Result: ARK says: not a valid archive. (Testet with 5 different archives). Workaround: Uncompress using "unzip" in console or using "mc". Possibly, character encoding is the issue, here, as well. Any idea? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 349904] Colgado cargando en Onedrive
https://bugs.kde.org/show_bug.cgi?id=349904 --- Comment #2 from ralfgesellensetter --- ark version: 4:15.12.3 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381094] New: Error during vcdxrip
https://bugs.kde.org/show_bug.cgi?id=381094 Bug ID: 381094 Summary: Error during vcdxrip Product: k3b Version: 2.0.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video CD project Assignee: k...@kde.org Reporter: ganesh...@gmail.com CC: ch...@ckvsoft.at, mich...@jabster.pl, tr...@kde.org Target Milestone: --- Devices --- HL-DT-ST DVDRAM GH24NS72 WM00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] System --- K3b Version: 2.0.3 KDE Version: 4.14.16 QT Version: 4.8.7 Kernel: 4.4.0-79-generic vcdxrip --- ++ WARN: mpeg scan: pack header code (0x01ba) expected, but 0xa1ba found (buflen = 2324) ++ WARN: packet not recognized as either version 1 or 2 (13) -- assuming v1 ++ WARN: mpeg scan: pack header code (0x01ba) expected, but 0x409c found (buflen = 2324) **ERROR: Error in ISO11172 PES header vcdxrip command: --- --gui --progress --no-ext-psd -i /dev/sr0 -o NEW (vcd 2.0).xml -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 381087] Newly ported KF5 .desktop Exec line contains an invalid -caption option preventing ksudoku from launching via the icon menu.
https://bugs.kde.org/show_bug.cgi?id=381087 Burkhard Lueck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/ksu ||doku/672b4e39f22f840034a8e6 ||6e1311175639bff3e3 Resolution|--- |FIXED --- Comment #3 from Burkhard Lueck --- Git commit 672b4e39f22f840034a8e66e1311175639bff3e3 by Burkhard Lück. Committed on 11/06/2017 at 09:03. Pushed by lueck into branch 'Applications/17.04'. Fix .desktop: Qt5 apps accept qwindowtitle, not caption M +1-1src/gui/org.kde.ksudoku.desktop https://commits.kde.org/ksudoku/672b4e39f22f840034a8e66e1311175639bff3e3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380182] deleting several messages doesn't remove them from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 Martin Koller changed: What|Removed |Added CC||kol...@aon.at --- Comment #6 from Martin Koller --- Which I fixed with this https://phabricator.kde.org/D5711 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381095] New: Cannot query modifiers within wheelEvent() functions
https://bugs.kde.org/show_bug.cgi?id=381095
Bug ID: 381095
Summary: Cannot query modifiers within wheelEvent() functions
Product: kwin
Version: 5.10.1
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: input
Assignee: kwin-bugs-n...@kde.org
Reporter: elvis.angelac...@kde.org
Target Milestone: ---
Flags: Wayland+, Intel+, Mesa+
Applications like okular or dolphin implement browser-like zoom in/out via
CTRL+mouse wheel. This does not work in kwin_wayland because
QWheelEvent::modifiers() always returns NoModifier, even if I'm pressing the
CTRL key while moving the mouse wheel. For the record, this is what both okular
and dolphin do:
void wheelEvent(QWheelEvent* event)
{
if (event->modifiers().testFlag(Qt::ControlModifier)) {
// zoom
} else {
// no zoom
}
}
Even if I call QGuiApplication::queryKeyboardModifiers() from wheelEvent(), I
also get NoModifier as return value.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 372384] Memory leak in plasmashell
https://bugs.kde.org/show_bug.cgi?id=372384 --- Comment #13 from Lastique --- Since this bug report, I have upgraded to Kubuntu 17.04 (Qt 5.7.1, plasma-framework 5.31, plasma-workspace 5.9.4) and nvidia 381.22 with the rest setup mostly intact. I don't see plasmashell leak with this setup, after ~2 days of uptime plasmashell consumes ~250 Mb RAM, which is significantly less than it did before. I didn't do any long term monitoring to see if the growth still exists, but if it does, its severity is certainly reduced. Whoever fixed this, many thanks to you. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 381096] New: __sync_fetch_and_add reported as read instead of as write
https://bugs.kde.org/show_bug.cgi?id=381096
Bug ID: 381096
Summary: __sync_fetch_and_add reported as read instead of as
write
Product: valgrind
Version: 3.12.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: meph...@gmail.com
Target Milestone: ---
For the following test program:
#include
int main() {
int *p = malloc(4);
if (!p) { return 1; }
*p = 0;
free(p);
__sync_fetch_and_add(p, -1);
}
valgrind reports the following:
==81== Invalid read of size 4
==81==at 0x4005BE: main (test.c:7)
==81== Address 0x51f8040 is 0 bytes inside a block of size 4 free'd
==81==at 0x4C2BCDD: free (vg_replace_malloc.c:530)
==81==by 0x4005B9: main (test.c:6)
==81== Block was alloc'd at
==81==at 0x4C2ABE3: malloc (vg_replace_malloc.c:299)
==81==by 0x400591: main (test.c:3)
I believe this problem should be reported as an invalid write or an invalid
read followed by an invalid write, but not simply as an invalid read.
--
You are receiving this mail because:
You are watching all bug changes.
[kronometer] [Bug 371865] Exporting laps to CSV or JSON doesn’t work
https://bugs.kde.org/show_bug.cgi?id=371865 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||2.2.0 Latest Commit||https://commits.kde.org/kro ||nometer/6cc662646a3165f94a4 ||66bc086fe3c21ef4d704a Status|CONFIRMED |RESOLVED --- Comment #2 from Elvis Angelaccio --- Git commit 6cc662646a3165f94a466bc086fe3c21ef4d704a by Elvis Angelaccio. Committed on 11/06/2017 at 10:24. Pushed by elvisangelaccio into branch 'master'. Fix laps export QFileDialog::selectedNameFilter() is broken in the Plasma file dialog. Port to Qt 5.9's selectedMimeTypeFilter() which will work with plasma-integration >= 5.10. FIXED-IN: 2.2.0 M +1-1CMakeLists.txt M +4-4src/gui/mainwindow.cpp M +2-2src/gui/mainwindow.h https://commits.kde.org/kronometer/6cc662646a3165f94a466bc086fe3c21ef4d704a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381097] New: Conversion crash
https://bugs.kde.org/show_bug.cgi?id=381097 Bug ID: 381097 Summary: Conversion crash Product: krita Version: 2.9.7 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: parasite.u...@gmail.com Target Milestone: --- Application: krita (2.9.7) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-79-lowlatency x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: trying to adjust an RGB image to different format to save as jpeg -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8552b4940 (LWP 3819))] Thread 5 (Thread 0x7fb829be5700 (LWP 3833)): #0 0x7fb852756b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb84cd7b38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb84cd7b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb8531782ce in QEventDispatcherGlib::processEvents (this=0x7fb81c007fa0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7fb85314618f in QEventLoop::processEvents (this=this@entry=0x7fb829be4c40, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fb8531464f5 in QEventLoop::exec (this=this@entry=0x7fb829be4c40, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fb853035549 in QThread::exec (this=this@entry=0x29ff4d0) at thread/qthread.cpp:538 #7 0x7fb853126223 in QInotifyFileSystemWatcherEngine::run (this=0x29ff4d0) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7fb853037e3c in QThreadPrivate::start (arg=0x29ff4d0) at thread/qthread_unix.cpp:352 #9 0x7fb84d2626ba in start_thread (arg=0x7fb829be5700) at pthread_create.c:333 #10 0x7fb85276282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb8293e4700 (LWP 3832)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb8530383a6 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x29ff230) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x29fed98, mutex=mutex@entry=0x29fed90, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7fb8540769ac in QFileInfoGatherer::run (this=0x29fed80) at dialogs/qfileinfogatherer.cpp:214 #4 0x7fb853037e3c in QThreadPrivate::start (arg=0x29fed80) at thread/qthread_unix.cpp:352 #5 0x7fb84d2626ba in start_thread (arg=0x7fb8293e4700) at pthread_create.c:333 #6 0x7fb85276282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb82a3e6700 (LWP 3830)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb8530383a6 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x2375c60) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=, mutex=mutex@entry=0x2375c10, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7fb8530344c3 in QSemaphore::tryAcquire (this=0x2375920, n=n@entry=1, timeout=timeout@entry=-1) at thread/qsemaphore.cpp:221 #4 0x7fb84ff931f3 in KisTileDataSwapper::waitForWork (this=this@entry=0x23755b0) at /build/calligra-ZNsRv2/calligra-2.9.7/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #5 0x7fb84ff934aa in KisTileDataSwapper::run (this=0x23755b0) at /build/calligra-ZNsRv2/calligra-2.9.7/krita/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #6 0x7fb853037e3c in QThreadPrivate::start (arg=0x23755b0) at thread/qthread_unix.cpp:352 #7 0x7fb84d2626ba in start_thread (arg=0x7fb82a3e6700) at pthread_create.c:333 #8 0x7fb85276282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb834b1b700 (LWP 3829)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb8530383a6 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x23758b0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=, mutex=mutex@entry=0x2375860, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7fb8530340a3 in QSemaphore::acquire (this=this@entry=0x2375580, n=n@entry=1) at thread/qsemaphore.cpp:144 #4 0x7fb84ff7704e in KisTileDataPooler::waitForWork (this=0x2375570) at /build/calligra-ZNsRv2/calligra-2.9.7/krita/image/tiles3/kis_tile_data_pooler.cc:165 #5 0x7fb84ff77530 in KisTileDataPooler::run (this=0x2375570) at /build/calligra-ZNsRv2/calligra-2.9.7/krita/image/tiles3/kis_tile_data_pooler.cc:187 #6 0x7fb853037e3c in QThreadPrivate::start (arg=0x23
[krita] [Bug 381097] Conversion crash
https://bugs.kde.org/show_bug.cgi?id=381097 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi, Thanks for your report. Unfortunately, the version of Krita you are using is very old. We're at 3.1.4 now, so it would be best to update: we won't be bringing out new bugfix releases for 2.9. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381090] use of a tablett
https://bugs.kde.org/show_bug.cgi?id=381090 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- Dear Wilhelm, Krita should work out of the box with Huion tablets if the driver is configured correctly. There's nothing to configure about it in Krita. If you have problems, please contact Huion: http://huion.deviantart.com/journal/Problem-with-Krita-Come-On-In-439442607 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371199] Dragging windows on my left screen causes them to jump down to the bottom
https://bugs.kde.org/show_bug.cgi?id=371199 Daniel Lichtenberger changed: What|Removed |Added CC||daniel.lichtenber...@gmx.ne ||t --- Comment #21 from Daniel Lichtenberger --- AFAIUI the problematic code is in AbstractClient::handleMoveResize (geometry.cpp) of kwin. As described in the blog post mentioned above, putting a panel in the middle of the screen covers the entire left screen internally. The code in AbstractClient doesn't seem to handle this: the entire left screen is removed from the "available" area for moving, which causes issues down the line. For example, with my setup (1280x1024 left-of 1680x1050), a panel on the left-hand side of the right monitor has a "strut" of (0,0 1330x1049). Removing this area from the available area will cause issues. Setting the left edge of the strut to 1280 (the width of the left monitor) seemed to fix the issue for me but probably isn't a solution if this scenario is essentially not covered by the spec. Pressing "Alt" while moving triggers an unrestricted move mode that just uses the entire (virtual) screen for moving and ignores the panel altogether, thus avoiding the issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 380805] Generating Gallery: "Could not load XSL file"
https://bugs.kde.org/show_bug.cgi?id=380805 --- Comment #13 from caulier.gil...@gmail.com --- The patch is already included in source code and Windows installer re-build : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 381098] New: test-case KStandarddirsTest::testFindResourceDir does not initialize properly
https://bugs.kde.org/show_bug.cgi?id=381098 Bug ID: 381098 Summary: test-case KStandarddirsTest::testFindResourceDir does not initialize properly Product: frameworks-kdelibs4support Version: 5.35.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: h.goe...@crazy-compilers.com Target Milestone: --- The test-case KStandarddirsTest::testFindResourceDir does not initialize the test-data correctly: rm -rf ~/.kde-unit-test/ ./autotests/kstandarddirstest testFindResourceDir -> FAIL rm -rf ~/.kde-unit-test/ mkdir -p ~/.kde-unit-test/xdg/config/ touch ~/.kde-unit-test/xdg/config/foorc ./autotests/kstandarddirstest testFindResourceDir -> PASS -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 378227] KDialog scans all fonts directory before showing dialog box making it super slow
https://bugs.kde.org/show_bug.cgi?id=378227
Rex Dieter changed:
What|Removed |Added
CC||rdie...@gmail.com
--- Comment #5 from Rex Dieter ---
In contrast, for me:
% time seconds usecs/call callserrors syscall
-- --- --- - -
20.560.004742 3 1678 298 stat
11.910.002747 2 1144 480 access
10.590.002444 3 790 657 recvmsg
9.940.002294 2 110130 lstat
7.840.001809 4 46433 open
For me, the only fonts that get opened are the ones actually *used* in the
dialog.
Otherwise, I also see lots of hits for stuff like:
open("/var/cache/fontconfig//711dae798b6bff4224ea2776edcb5c93-le64.cache-7",
O_RDONLY|O_CLOEXEC) = 6
which is obviously a fontconfig cache.
If I had to speculate, one possibility is your fontconfig cache either doesn't
exist or is invalidated (old?). Maybe try running (as root):
fc-cache -sf
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 381082] System Settings crashed when changing from one color scheme to another
https://bugs.kde.org/show_bug.cgi?id=381082 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 377312 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377312] Colosing of Plasma settings
https://bugs.kde.org/show_bug.cgi?id=377312 Christoph Feck changed: What|Removed |Added CC||pointedst...@zoho.com --- Comment #7 from Christoph Feck --- *** Bug 381082 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381021] Hotkeys have no effect in the Kwin window management modes
https://bugs.kde.org/show_bug.cgi?id=381021 Kamil changed: What|Removed |Added Severity|wishlist|normal --- Comment #11 from Kamil --- I'm changing the importance of the bug back to "normal" as the bug is clearly not a wish against any intended resolution to remove that functionality. However, I'll leave the status of the bug to the KDE developers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381099] New: KWin crashes during window ALT+TAB window changing
https://bugs.kde.org/show_bug.cgi?id=381099 Bug ID: 381099 Summary: KWin crashes during window ALT+TAB window changing Product: kwin Version: 5.10.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: eckl...@gmail.com Target Milestone: --- Application: kwin_x11 (5.10.1) Qt Version: 5.9.0 Frameworks Version: 5.34.0 Operating System: Linux 4.11.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was trying to change window using the ALT+TAB hotkey. - Unusual behavior I noticed: KWin crashed and then restarted. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcbe6414840 (LWP 734))] Thread 7 (Thread 0x7fcbc3fff700 (LWP 1297)): #0 0x7fcbe5e06396 in ppoll () at /usr/lib/libc.so.6 #1 0x7fcbe33f4471 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fcbe33f5b5e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fcbe339f21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fcbe31c140a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fcbddc52645 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fcbe31c5cbd in () at /usr/lib/libQt5Core.so.5 #7 0x7fcbdef42297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fcbe5e1025f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fcba978d700 (LWP 851)): #0 0x7fcbdef4839d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcbe230bac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fcbe230bb09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fcbdef42297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcbe5e1025f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fcbaaa9a700 (LWP 844)): #0 0x7fcbdef4839d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcbaf4d971b in () at /usr/lib/xorg/modules/dri/r600_dri.so #2 0x7fcbaf4d9447 in () at /usr/lib/xorg/modules/dri/r600_dri.so #3 0x7fcbdef42297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcbe5e1025f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fcbab3e2700 (LWP 843)): #0 0x7fcbdef4839d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcbaf4d971b in () at /usr/lib/xorg/modules/dri/r600_dri.so #2 0x7fcbaf4d9447 in () at /usr/lib/xorg/modules/dri/r600_dri.so #3 0x7fcbdef42297 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcbe5e1025f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fcbc35da700 (LWP 841)): #0 0x7fcbe33a2e50 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #1 0x7fcbe33f5974 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #2 0x7fcbe339f21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fcbe31c140a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #4 0x7fcbddc52645 in () at /usr/lib/libQt5Qml.so.5 #5 0x7fcbe31c5cbd in () at /usr/lib/libQt5Core.so.5 #6 0x7fcbdef42297 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fcbe5e1025f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fcbca382700 (LWP 779)): #0 0x7fcbe5e06396 in ppoll () at /usr/lib/libc.so.6 #1 0x7fcbe33f4471 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fcbe33f5b5e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fcbe339f21a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fcbe31c140a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fcbdcde8d45 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fcbe31c5cbd in () at /usr/lib/libQt5Core.so.5 #7 0x7fcbdef42297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fcbe5e1025f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fcbe6414840 (LWP 734)): [KCrash Handler] #6 0x7fcbaf82ab22 in () at /usr/lib/xorg/modules/dri/r600_dri.so #7 0x7fcbaf608f25 in () at /usr/lib/xorg/modules/dri/r600_dri.so #8 0x7fcbaf3e4940 in () at /usr/lib/xorg/modules/dri/r600_dri.so #9 0x7fcbaf3a4b30 in () at /usr/lib/xorg/modules/dri/r600_dri.so #10 0x7fcbaf3a4fb9 in () at /usr/lib/xorg/modules/dri/r600_dri.so #11 0x7fcbde30827f in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #12 0x7fcbde3094c5 in QSGBatchRenderer::Renderer::renderBa
[plasmashell] [Bug 381100] New: Crash with redraw desktop with mouse and window motion
https://bugs.kde.org/show_bug.cgi?id=381100
Bug ID: 381100
Summary: Crash with redraw desktop with mouse and window motion
Product: plasmashell
Version: 5.10.1
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: search_termi...@mail.ru
Target Milestone: 1.0
Crash with redraw desktop with mouse and window motion.
+bug:Hang / crash when cleaning the basket with confirmation (dialog) in the
dolphin.
+critical:Crash of the system when the composer(opengl 2.0, opengl 3.0) is on
and when the mouse moves any window, including the default file manager.
Hardware: Raspberry 3, ram 1Gb (300mb using by KDE), armv 7hf hardened.
VIDEO: videocore 4, using official raspberry's gpu's binaries and include in
mesa (USEFLAG/VIDEO_DEVICES: vc4).
USE="bindist -mudflap -sanitize"
USE="${USE} lzo -lz4 evdev -llvm"
USE="${USE} lock jpeg"
USE="${USE} dbus bluetooth lock udev -eudev usb udisks cdr dvd"
USE="${USE} X egl gles1 gles2 ffmpeg glamor wayland dmx dri dri2"
USE="${USE} alsa pulseaudio bluetooth -gnome -kde"
CFLAGS="-O2 -pipe -march=armv7-a -mtune=cortex-a53 -mfpu=neon-vfpv4
WAYLAND DONT USING! CRASH IN X11.
IF I USING WAYLAND DONT HELP ME. PROBLEM IS GENERAL
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 381100] Crash with redraw desktop with mouse and window motion
https://bugs.kde.org/show_bug.cgi?id=381100 --- Comment #1 from Andrew --- problem IN 5.6 -5.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380902] kwin effects like "present windows" can't be exited with the keyboard
https://bugs.kde.org/show_bug.cgi?id=380902 kishor...@gmail.com changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381021] Hotkeys have no effect in the Kwin window management modes
https://bugs.kde.org/show_bug.cgi?id=381021 Bastian Beischer changed: What|Removed |Added CC||bastian.beischer@rwth-aache ||n.de -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 203042] Option to display image count while browsing.
https://bugs.kde.org/show_bug.cgi?id=203042 Stephane Couturier changed: What|Removed |Added CC||cont...@symbioxy.com --- Comment #7 from Stephane Couturier --- Hi, I would really enjoy this feature too. Is there any plan/progress about it ? It would be nice to have it on the usually main screen first, maybe later when in full screen as an option. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #25 from Cristian Aravena Romero --- (In reply to Thomas Schmitt from comment #24) [...] > Did the pacifier messages of growisofs report speeds around "@2.0x" > or did it burn with the speed 4x which growisofs demands and which the > drive in the beginning reports to have set ? I do not understand Regards, -- Cristian -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #26 from Thomas Schmitt --- Hi, i wrote: > > Did the pacifier messages of growisofs report speeds around "@2.0x" > > or did it burn with the speed 4x [...] ? Cristian Aravena Romero wrote: > I do not understand In the logs before the firmware upgrade, we have the growisofs announcement of 4.1x: /dev/sr0: "Current Write Speed" is 4.1x4390KBps. but during the write run it reports mostly 2.0x or slightly lower 2406088704/20729948160 (11.6%) @2.0x, remaining 36:02 RBU 100.0% UBU 96.9% 2431909888/20729948160 (11.7%) @1.7x, remaining 36:06 RBU 100.0% UBU 96.9% 2462121984/20729948160 (11.9%) @2.0x, remaining 35:59 RBU 100.0% UBU 96.9% See e.g. https://bugsfiles.kde.org/attachment.cgi?id=106040 My question is whether it now reports something like 462121984/20729948160 (11.9%) @4.0x, remaining 18:00 RBU 100.0% UBU 96.9% and is done in half the time than before upgrade. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #27 from Thomas Schmitt --- Hi, when doing copy+paste i left out a digit "2". My made-up pacifier line should have looked like 2462121984/20729948160 (11.9%) @4.0x, remaining 18:00 RBU 100.0% UBU 96.9% not 462121984/20729948160 (11.9%) @4.0x, remaining 18:00 RBU 100.0% UBU 96.9% Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 381101] New: Crash van kontact when editing group in addresses
https://bugs.kde.org/show_bug.cgi?id=381101 Bug ID: 381101 Summary: Crash van kontact when editing group in addresses Product: kontact Version: 5.5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: freekdekru...@kde.nl Target Milestone: --- Application: kontact (5.5.1) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.11.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: The only solution I could think off to solve a problem with kmail was to delete the folder ~/.local/share/akonadi . After that restarting kontact rebuilds this folder, but apparently some information is lost. An example are the pointers in accounts in the tab Advanced pointing to Send, Drafts and Templates. These pointer seem to point to rather random folders. But these can be repaired. Anyway the accounts are still there and the messages are restored from the IMAP servers. Also Addresses in Kontact are all there. However the content of a group (of addresses) shows addresses, but these are not the previously added addresses, but look more a random set of the normal addresses. The crash occurs when trying to edit the group. Selecting a group is possible, also selecting the Edit button is OK, however going to the start of the group causes the crash of Kontact. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f86a901d8c0 (LWP 9210))] Thread 28 (Thread 0x7f855c3b5700 (LWP 9332)): #0 0x7f869f78db34 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f869f748218 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f869f748c1b in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f869f748dfc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f86a6583afb in QEventDispatcherGlib::processEvents (this=0x7f85540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f86a652ad5a in QEventLoop::exec (this=this@entry=0x7f855c3b4cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f86a634dafa in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f86a63527cc in QThreadPrivate::start (arg=0x55f48eb7dff0) at thread/qthread_unix.cpp:368 #8 0x7f86a199a4e7 in start_thread () from /lib64/libpthread.so.0 #9 0x7f86a5a49a2f in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f85661b5700 (LWP 9308)): #0 0x7f86a19a05ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8698b065f5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f8698b06a09 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f8698b06bb1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f8698b037f5 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f86a199a4e7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f86a5a49a2f in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f8577fff700 (LWP 9251)): #0 0x7f869f748150 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f869f748c1b in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f869f748dfc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f86a6583afb in QEventDispatcherGlib::processEvents (this=0x7f856c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f86a652ad5a in QEventLoop::exec (this=this@entry=0x7f8577ffecf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f86a634dafa in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f86a63527cc in QThreadPrivate::start (arg=0x55f48d859820) at thread/qthread_unix.cpp:368 #7 0x7f86a199a4e7 in start_thread () from /lib64/libpthread.so.0 #8 0x7f86a5a49a2f in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f857cfa4700 (LWP 9249)): #0 0x7ffe302a5949 in ?? () #1 0x7ffe302a5bdb in clock_gettime () #2 0x7f86a5a56f86 in clock_gettime () from /lib64/libc.so.6 #3 0x7f86a63fbdf1 in qt_clock_gettime (ts=0x7f857cfa3a60, clock=) at tools/qelapsedtimer_unix.cpp:109 #4 do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:164 #5 qt_gettime () at tools/qelapsedtimer_unix.cpp:173 #6 0x7f86a6581809 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f8570002ed0) at kernel/qtimerinfo_unix.cpp:91 #7 0x7f86a6581de5 in QTimerInfoList::timerWait (this=0x7f8570002ed0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #8 0x7f86a65830de in timerSourcePrepareHelper (timeout=0x7f857cfa3b24, src=) at kernel/qeventdispatcher_glib.cpp:132 #9 timerSourcePrepare (source=, timeout=0x7f857cfa3b24) at kernel/qeventdispatcher_glib.cpp:165 #10
[clazy] [Bug 381102] New: [PATCH] Inaccurate README.md
https://bugs.kde.org/show_bug.cgi?id=381102 Bug ID: 381102 Summary: [PATCH] Inaccurate README.md Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jo...@vitu.org CC: smart...@kde.org Target Milestone: --- Created attachment 106045 --> https://bugs.kde.org/attachment.cgi?id=106045&action=edit patch The list of dependencies for building clazy on Ubuntu in README.md is incomplete, as building fails because of missing header files when the llvm-dev (or to be more precise a llvm-3.*-dev) package isn't installed. The attached patch suggests just replacing llvm with llvm-dev, as it depends on the llvm package anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380902] kwin effects like "present windows" can't be exited with the keyboard
https://bugs.kde.org/show_bug.cgi?id=380902 --- Comment #5 from kishor...@gmail.com --- Downgrading all qt packages to 5.8 but leaving kwin and plasma-related packages at 5.10 fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 381103] New: releaseme should use kdoctools_install
https://bugs.kde.org/show_bug.cgi?id=381103 Bug ID: 381103 Summary: releaseme should use kdoctools_install Product: releaseme Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: sit...@kde.org Reporter: elvis.angelac...@kde.org Target Milestone: --- kdoctools_install() is the equivalent of ki18n_install() for documentation translations. It enables simpler tarballs with a single po folder containing all the translations (code + documentation). This would also make releaseme's tarballs consistent with the Applications and Frameworks tarballs. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 381103] releaseme should use kdoctools_install
https://bugs.kde.org/show_bug.cgi?id=381103 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org, ||luigi.tosc...@tiscali.it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381021] Hotkeys have no effect in the Kwin window management modes
https://bugs.kde.org/show_bug.cgi?id=381021 kishor...@gmail.com changed: What|Removed |Added CC||kishor...@gmail.com --- Comment #12 from kishor...@gmail.com --- As mentioned here [https://bugs.kde.org/show_bug.cgi?id=380902#c5] in the other related bug, the hotkeys work as expected when downgrading the Qt packages alone to 5.8. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355190] copy current date/time into clipboard
https://bugs.kde.org/show_bug.cgi?id=355190 Bernhard Schiffner changed: What|Removed |Added CC||bernhard.schiff...@gmx.net --- Comment #26 from Bernhard Schiffner --- Some progress made: https://phabricator.kde.org/D6183 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381104] New: Plasma crash when change panel settings
https://bugs.kde.org/show_bug.cgi?id=381104 Bug ID: 381104 Summary: Plasma crash when change panel settings Product: plasmashell Version: 5.10.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: i...@daniel-ionatan.org CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.0) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.11.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Plasma crash when i'm change panel settings. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4509c7ad40 (LWP 27007))] Thread 25 (Thread 0x7f03db7fe700 (LWP 4476)): #0 0x7f450331808d in poll () from /lib64/libc.so.6 #1 0x7f44fe10cce9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f44fe10cdfc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4503c44afb in QEventDispatcherGlib::processEvents (this=0x7f03dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4503bebd5a in QEventLoop::exec (this=this@entry=0x7f03db7fdcd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f4503a0eafa in QThread::exec (this=this@entry=0x55810c1b1f40) at thread/qthread.cpp:507 #6 0x7f4506b13165 in QQmlThreadPrivate::run (this=0x55810c1b1f40) at /usr/src/debug/qtdeclarative-opensource-src-5.7.1/src/qml/qml/ftw/qqmlthread.cpp:147 #7 0x7f4503a137cc in QThreadPrivate::start (arg=0x55810c1b1f40) at thread/qthread_unix.cpp:368 #8 0x7f4502bdb4e7 in start_thread () from /lib64/libpthread.so.0 #9 0x7f4503321a2f in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f03fa40a700 (LWP 4474)): #0 0x7f45032632d0 in __dcigettext () from /lib64/libc.so.6 #1 0x7f45032b7288 in strerror_r () from /lib64/libc.so.6 #2 0x7f45032b71af in strerror () from /lib64/libc.so.6 #3 0x7f4406b3ac88 in ?? () from /usr/lib64/gstreamer-1.0/libgstalsa.so #4 0x7f440689846f in ?? () from /usr/lib64/libasound.so.2 #5 0x7f4406888d30 in snd_pcm_prepare () from /usr/lib64/libasound.so.2 #6 0x7f4406b3b848 in ?? () from /usr/lib64/gstreamer-1.0/libgstalsa.so #7 0x7f4406fca091 in ?? () from /usr/lib64/libgstaudio-1.0.so.0 #8 0x7f44fe133bb5 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x7f4502bdb4e7 in start_thread () from /lib64/libpthread.so.0 #10 0x7f4503321a2f in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f03fac0b700 (LWP 4473)): #0 0x7f450331cb89 in syscall () from /lib64/libc.so.6 #1 0x7f44fe151c4f in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4420157a6b in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #3 0x7f44fe134580 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f44fe133bb5 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f4502bdb4e7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f4503321a2f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f03fb7fe700 (LWP 4472)): #0 0x7f450331cb89 in syscall () from /lib64/libc.so.6 #1 0x7f44fe151c4f in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4420157a6b in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #3 0x7f44fe134580 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f44fe133bb5 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f4502bdb4e7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f4503321a2f in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f4405266700 (LWP 4471)): #0 0x7f450331cb89 in syscall () from /lib64/libc.so.6 #1 0x7f44fe151c4f in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4420157a6b in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #3 0x7f44fe134580 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f44fe133bb5 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f4502bdb4e7 in start_thread () from /lib64/libpthread.so.0 #6 0x7f4503321a2f in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f03fbfff700 (LWP 4470)): #0 0x7f450331cb89 in syscall () from /lib64/libc.so.6 #1 0x7f44fe151c4f in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7f44074b753b in ?? () from /usr/lib64/libgstbase-1.0.so.0 #3 0x7f44074b8878 in gst_data_queue_pop () from /usr/lib64/libgstbase-1.0.so.0 #4 0x7f4405721331 in ?? () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so #5 0x7f4420157889 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #6 0x7f44fe134580 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7f44fe133bb5 in ?? ()
[kio-extras] [Bug 369850] Can't browse samba workgroups
https://bugs.kde.org/show_bug.cgi?id=369850 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365055] Does not seem to be able to properly resolve host names to addresses, or even get host names at all
https://bugs.kde.org/show_bug.cgi?id=365055 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373589] unable to drag and drop file to smb shares
https://bugs.kde.org/show_bug.cgi?id=373589 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356651] Moving files onto a smb network share sets the files' access/modify times to the current date/time.
https://bugs.kde.org/show_bug.cgi?id=356651 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 355164] access is denied error when accessing smb share
https://bugs.kde.org/show_bug.cgi?id=355164 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 352064] Dolphin v15.08.0 doesn't show network shares (remote:/ on Network folder)
https://bugs.kde.org/show_bug.cgi?id=352064 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 348937] can't navigate inside sambashare through clicking if the workgroup name is equal the server name
https://bugs.kde.org/show_bug.cgi?id=348937 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 259079] Feature request: Make dolphin use network shares as convenient as nautilus does
https://bugs.kde.org/show_bug.cgi?id=259079 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 309841] Can't browse work groups in samba shares
https://bugs.kde.org/show_bug.cgi?id=309841 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380182] deleting several messages doesn't remove them from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #7 from Laurent Montel --- Which is not in 17.04 so the fix is not in 17.04 branch => the bug is still here indeed. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 321949] GNU screen breaks konsole scrollback
https://bugs.kde.org/show_bug.cgi?id=321949 --- Comment #2 from azr...@googlemail.com --- maybe related to https://bugs.kde.org/show_bug.cgi?id=185582 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #28 from Cristian Aravena Romero --- what do I do now? -- Cristian -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"
https://bugs.kde.org/show_bug.cgi?id=362856 Oskar Kirmis changed: What|Removed |Added CC||oskar.kir...@t-online.de --- Comment #30 from Oskar Kirmis --- I am having the same issue as in #374207 (which has been marked as a dup) with okular but the behavior is quiete strange: - ScaleFactor=1.0, start okular -> ok - Scale up to 1.5, start okular -> ok, correctly scaled up and looking sharp - Log out, log in again, start okular -> blurry Hope it helps tracking down the bug. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #29 from Thomas Schmitt --- Hi, most important is to find out whether the drive now burns BD-R reliably. If you experience failure, please post the growisofs log. If half a dozen successes in a row happen, then you can expect to have solved the problem. Please give us a short note in this case. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381105] New: Plasma crash while selecting and changing wallpaper positioning.
https://bugs.kde.org/show_bug.cgi?id=381105 Bug ID: 381105 Summary: Plasma crash while selecting and changing wallpaper positioning. Product: plasmashell Version: 5.10.1 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: wcc...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.1) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.10.9-1 x86_64 Distribution: "KaOS" -- Information about the crash: - What I was doing when the application crashed: I selected the beach-seascape-lu wallpaper (in Desktop Settings - Plasma) and then changed the positioning and then selected Apply. I am using KaOS and it is up to date. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc4aa997d80 (LWP 725))] Thread 18 (Thread 0x7fc3a6a3a700 (LWP 3856)): #0 0x7fc4a519fffd in poll () at /lib/libc.so.6 #1 0x7fc49ed02cf4 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc49ed02dfc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc4a5aa6a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc4a5a5371a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc4a5887ddc in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc4a588c58a in () at /usr/lib/libQt5Core.so.5 #7 0x7fc4a4740494 in start_thread () at /lib/libpthread.so.0 #8 0x7fc4a51a96ff in clone () at /lib/libc.so.6 Thread 17 (Thread 0x7fc3a7a3c700 (LWP 3854)): #0 0x7fc4a5aa4aff in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #1 0x7fc4a5aa62dc in () at /usr/lib/libQt5Core.so.5 #2 0x7fc49ed022ad in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7fc49ed02c23 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fc49ed02dfc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fc4a5aa6a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fc4a5a5371a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fc4a5887ddc in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fc4a588c58a in () at /usr/lib/libQt5Core.so.5 #9 0x7fc4a4740494 in start_thread () at /lib/libpthread.so.0 #10 0x7fc4a51a96ff in clone () at /lib/libc.so.6 Thread 16 (Thread 0x7fc3acd20700 (LWP 3853)): #0 0x7fc4a519fffd in poll () at /lib/libc.so.6 #1 0x7fc49ed02cf4 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc49ed02dfc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc4a5aa6a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc4a5a5371a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc4a5887ddc in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc4a588c58a in () at /usr/lib/libQt5Core.so.5 #7 0x7fc4a4740494 in start_thread () at /lib/libpthread.so.0 #8 0x7fc4a51a96ff in clone () at /lib/libc.so.6 Thread 15 (Thread 0x7fc3aec9c700 (LWP 3837)): #0 0x7fc4a519fffd in poll () at /lib/libc.so.6 #1 0x7fc49ed02cf4 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc49ed02dfc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc4a5aa6a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc4a5a5371a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc4a5887ddc in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc4a7f62135 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fc4a588c58a in () at /usr/lib/libQt5Core.so.5 #8 0x7fc4a4740494 in start_thread () at /lib/libpthread.so.0 #9 0x7fc4a51a96ff in clone () at /lib/libc.so.6 Thread 14 (Thread 0x7fc3c1e20700 (LWP 877)): #0 0x7fc4a519fffd in poll () at /lib/libc.so.6 #1 0x7fc49ed02cf4 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc49ed02dfc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc4a5aa6a6b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc4a5a5371a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc4a5887ddc in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc3c8c122d7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7fc4a588c58a in () at /usr/lib/libQt5Core.so.5 #8 0x7fc4a4740494 in start_thread () at /lib/libpthread.so.0 #9 0x7fc4a51a96ff in clone () at /lib/libc.so.6 Thread 13 (Thread 0x7fc3edc80700 (LWP 869)): #0 0x7fc49ecffe70 in () at /usr/lib/l
[clazy] [Bug 381102] [PATCH] Inaccurate README.md
https://bugs.kde.org/show_bug.cgi?id=381102 Sergio Martins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |smart...@kde.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373005] Dolphin crashes when dragging unused device somewhere
https://bugs.kde.org/show_bug.cgi?id=373005 Elvis Angelaccio changed: What|Removed |Added Version Fixed In||17.04.3 Latest Commit||https://commits.kde.org/dol ||phin/c85ca114553c198af79eed ||acdb6b40ac4cab20e0 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Elvis Angelaccio --- Git commit c85ca114553c198af79eedacdb6b40ac4cab20e0 by Elvis Angelaccio. Committed on 11/06/2017 at 17:11. Pushed by elvisangelaccio into branch 'Applications/17.04'. Ignore drops-onto-items from invalid places items If the QMimeData object created by PlacesItemModel doesn't have any url set (e.g. when dragging unmounted devices), it is detected by the resulting DropJob as "drop raw data" because the mimeData has one format set (the internalMimeType() used for dragging between places items). This results in a crash because the DropJob schedules a PasteJob, but in the meantime the QDrag from Dolphin ends and deletes the mimeData object that was passed to the paste job. The fix is to prevent the DropJob in the first place. We can introduce a new internal mimetype that we use to blacklist drops-onto-items (while still allowing drops-between-items). This way PlacesItemModel can set the blacklist flag if the mimeData is being created without urls. FIXED-IN: 17.04.3 Test Plan: Drag and drop an unmounted device to another place item or the DolphinView, doesn't crash anymore. Dropping the unmounted device between two places item still works. Differential Revision: https://phabricator.kde.org/D5535 M +1-1src/kitemviews/kitemlistcontroller.cpp M +5-0src/kitemviews/kitemmodelbase.cpp M +10 -0src/kitemviews/kitemmodelbase.h M +3-0src/panels/places/placesitemmodel.cpp https://commits.kde.org/dolphin/c85ca114553c198af79eedacdb6b40ac4cab20e0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 380881] Bash interprets COMMAND {folder}/.* as COMMAND {folder}/..
https://bugs.kde.org/show_bug.cgi?id=380881
Egmont Koblinger changed:
What|Removed |Added
CC||egm...@gmail.com
--- Comment #1 from Egmont Koblinger ---
> That means, {folder}/.* is interpreted also as {folder}/..
This is intentional and as far as I remember has always been the case. I have
no clue why it didn't work like this for you in Trusty.
Anyway, please search the Internet for "what's the difference between terminal
emulator and shell" to learn and understand why your observation has absolutely
nothing to with konsole or kde, thanks!
--
You are receiving this mail because:
You are watching all bug changes.
[ark] [Bug 364976] Cannot extract rar file
https://bugs.kde.org/show_bug.cgi?id=364976 Elvis Angelaccio changed: What|Removed |Added CC||p...@7gods.org --- Comment #6 from Elvis Angelaccio --- *** Bug 380984 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 380984] Ark crashed while opening rar file from Dolphin
https://bugs.kde.org/show_bug.cgi?id=380984 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 364976 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381012] bug in popup palette color
https://bugs.kde.org/show_bug.cgi?id=381012 --- Comment #3 from Tomasz --- Ok I checked and there wasn`t so I add this line, no effect. 2017-06-09 13:43 GMT+02:00 Boudewijn Rempt : > https://bugs.kde.org/show_bug.cgi?id=381012 > > Boudewijn Rempt changed: > >What|Removed |Added > > > CC||b...@valdyas.org > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #1 from Boudewijn Rempt --- > Check whether your kritarc contains a line > > popuppalette/usevisualcolorselector=true > > Because this sounds like you've got the new color selector, not the default > one. Also, please attach a screenshot to the bug so I can verify which > color > selector is enabled. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 381102] [PATCH] Inaccurate README.md
https://bugs.kde.org/show_bug.cgi?id=381102 Sergio Martins changed: What|Removed |Added Latest Commit||https://commits.kde.org/cla ||zy/66e90a826a477852fb13 ||450c2c64f44f56ff Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Sergio Martins --- Git commit 66e90a826a477852fb13450c2c64f44f56ff by Sergio Martins, on behalf of Josef Vitu. Committed on 11/06/2017 at 17:55. Pushed by smartins into branch '1.2'. README: Fix llvm dependencies for Ubuntu Needs to be llvm-dev instead of llvm M +1-1README.md https://commits.kde.org/clazy/66e90a826a477852fb13450c2c64f44f56ff -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 381102] [PATCH] Inaccurate README.md
https://bugs.kde.org/show_bug.cgi?id=381102 --- Comment #2 from Sergio Martins --- Done. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381106] New: Effects: windowGeometryShapeChanged not triggered when window moved
https://bugs.kde.org/show_bug.cgi?id=381106 Bug ID: 381106 Summary: Effects: windowGeometryShapeChanged not triggered when window moved Product: kwin Version: 5.10.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: t...@r.je Target Milestone: --- Using the javascript scripting engine, there seems to be no way to detect when a window has been moved grammatically. Using ``` effects.windowGeometryShapeChanged.connect() ``` This is triggered as expected when the shape is changed, however, if the X/Y co-ordinates change (e.g. by a kwin script) this method is not triggered. There appears to be no method to trigger an animation from a kwin script to move windows around. As a workaround, I've used the same effect and done this: ``` var geo = client.geometry; geo.x += 100; //Add 1 to the width to trigger the effect geo.width = geo.width + 1; client.geometry = geo; //now put the window back to its original size geo.width = geo.width = geo.width -1; client.geometry = geo; ``` But this is a horrible hack! Either windowGeometryShapeChanged should be triggered when the x/y co-ordinates change or windowGeometryChanged should be implemented. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 344326] Buffer objects (VBO, FBO) need remapping after suspend/vt switch with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=344326 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 381107] New: Discover crashed on search
https://bugs.kde.org/show_bug.cgi?id=381107 Bug ID: 381107 Summary: Discover crashed on search Product: Discover Version: 5.10.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: paulmontaq...@gmail.com Target Milestone: --- Application: plasma-discover (5.10.1) Qt Version: 5.8.0 Frameworks Version: 5.34.0 Operating System: Linux 4.11.4-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Launched Discover, entered "Velours" and waited... The next thing to occur was this crash! -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f39950e07c0 (LWP 7103))] Thread 12 (Thread 0x7f39525f2700 (LWP 7255)): #0 0x003de8e0d39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x003df12ae21b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x003df12a6fbb in QSemaphore::acquire(int) () at /usr/lib/libQt5Core.so.5 #3 0x003df14bfa00 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #4 0x003df52957cb in () at /usr/lib/libQt5Network.so.5 #5 0x003df53291ed in () at /usr/lib/libQt5Network.so.5 #6 0x003df14bf693 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #7 0x003df52581bd in () at /usr/lib/libQt5Network.so.5 #8 0x003df52586f5 in () at /usr/lib/libQt5Network.so.5 #9 0x003df14bf693 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #10 0x003df531e54b in () at /usr/lib/libQt5Network.so.5 #11 0x003df5322a50 in () at /usr/lib/libQt5Network.so.5 #12 0x003df5322dfa in () at /usr/lib/libQt5Network.so.5 #13 0x003df530e7a1 in () at /usr/lib/libQt5Network.so.5 #14 0x003df14bf693 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #15 0x003df52e3483 in () at /usr/lib/libQt5Network.so.5 #16 0x003df52e3534 in () at /usr/lib/libQt5Network.so.5 #17 0x003df52eea41 in () at /usr/lib/libQt5Network.so.5 #18 0x7f3995996d7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7f399599e494 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x003df1491d38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x003df14e93cd in () at /usr/lib/libQt5Core.so.5 #22 0x003deca4a7b7 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #23 0x003deca4aa20 in () at /usr/lib/libglib-2.0.so.0 #24 0x003deca4aacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #25 0x003df14e8f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #26 0x003df14903aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #27 0x003df12a844a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #28 0x003df12ace9c in () at /usr/lib/libQt5Core.so.5 #29 0x003de8e07297 in start_thread () at /usr/lib/libpthread.so.0 #30 0x003de8aed25f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f396b062700 (LWP 7217)): #0 0x003de8ae32bd in poll () at /usr/lib/libc.so.6 #1 0x003deca4a9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x003deca4aacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x003df14e8f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x003df14903aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x003df12a844a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x003df12ace9c in () at /usr/lib/libQt5Core.so.5 #7 0x003de8e07297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x003de8aed25f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f39736b2700 (LWP 7212)): #0 0x003df12a4d4c in QMutex::lock() () at /usr/lib/libQt5Core.so.5 #1 0x003df14e86bd in () at /usr/lib/libQt5Core.so.5 #2 0x003deca49e8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x003deca4a8db in () at /usr/lib/libglib-2.0.so.0 #4 0x003deca4aacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x003df14e8f2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x003df14903aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x003df12a844a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f3996f77fd6 in () at /usr/lib/libQt5Quick.so.5 #9 0x003df12ace9c in () at /usr/lib/libQt5Core.so.5 #10 0x003de8e07297 in start_thread () at /usr/lib
[clazy] [Bug 380929] Failed to make by clang-5.0svn
https://bugs.kde.org/show_bug.cgi?id=380929 Sergio Martins changed: What|Removed |Added Assignee|unassigned-b...@kde.org |smart...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 380929] Failed to make by clang-5.0svn
https://bugs.kde.org/show_bug.cgi?id=380929 --- Comment #4 from Sergio Martins --- Git commit 754fdceae7de7cbf737af919e28f1a1ec8270189 by Sergio Martins. Committed on 11/06/2017 at 18:54. Pushed by smartins into branch '1.2'. Fix fedora 25 build Don't link to LLVMSupport if not needed. Respect LLVM_LIBS_LIST. Might also fix another bug: M +8-5CMakeLists.txt https://commits.kde.org/clazy/754fdceae7de7cbf737af919e28f1a1ec8270189 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381108] New: KWin crashed right after login
https://bugs.kde.org/show_bug.cgi?id=381108 Bug ID: 381108 Summary: KWin crashed right after login Product: kwin Version: 5.10.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: kwin_x11 (5.10.1) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.11.4-gentoo x86_64 Distribution: "Gentoo Base System release 2.4.1" -- Information about the crash: - What I was doing when the application crashed: I logged in and as soon as I saw the desktop, I also saw the DrKonqi dialogue reporting that KWin had crashed. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f08a7a49e40 (LWP 5250))] Thread 4 (Thread 0x7f0886de9700 (LWP 5392)): #0 0x7f08a75404f9 in ppoll () from /lib64/libc.so.6 #1 0x7f08a5492e99 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f0874000ac8) at kernel/qcore_unix.cpp:81 #3 qt_safe_poll (fds=0x7f0874000ac8, nfds=nfds@entry=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:102 #4 0x7f08a5494343 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f08a544964a in QEventLoop::exec (this=this@entry=0x7f0886de8d60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f08a52b4f4b in QThread::exec (this=this@entry=0x2262de0) at thread/qthread.cpp:507 #7 0x7f08a015f135 in QQmlThreadPrivate::run (this=0x2262de0) at qml/ftw/qqmlthread.cpp:147 #8 0x7f08a52b914b in QThreadPrivate::start (arg=0x2262de0) at thread/qthread_unix.cpp:368 #9 0x7f08a1232384 in start_thread () from /lib64/libpthread.so.0 #10 0x7f08a75496af in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f08875ea700 (LWP 5351)): #0 0x7f08a1238348 in pthread_cond_timedwait () from /lib64/libpthread.so.0 #1 0x7f08a52b9768 in QWaitConditionPrivate::wait_relative (time=3, this=0x2099b30) at thread/qwaitcondition_unix.cpp:133 #2 QWaitConditionPrivate::wait (time=3, this=0x2099b30) at thread/qwaitcondition_unix.cpp:141 #3 QWaitCondition::wait (this=this@entry=0x2094780, mutex=mutex@entry=0x209df30, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f08a52b62bd in QThreadPoolThread::run (this=0x2094770) at thread/qthreadpool.cpp:133 #5 0x7f08a52b914b in QThreadPrivate::start (arg=0x2094770) at thread/qthread_unix.cpp:368 #6 0x7f08a1232384 in start_thread () from /lib64/libpthread.so.0 #7 0x7f08a75496af in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f088dc82700 (LWP 5317)): #0 0x7f08a75404f9 in ppoll () from /lib64/libc.so.6 #1 0x7f08a5492e99 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f088000aad8) at kernel/qcore_unix.cpp:81 #3 qt_safe_poll (fds=0x7f088000aad8, nfds=nfds@entry=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:102 #4 0x7f08a5494343 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7f08a544964a in QEventLoop::exec (this=this@entry=0x7f088dc81d50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f08a52b4f4b in QThread::exec (this=this@entry=0x7f08a7b9cd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #7 0x7f08a7b28635 in QDBusConnectionManager::run (this=0x7f08a7b9cd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f08a52b914b in QThreadPrivate::start (arg=0x7f08a7b9cd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #9 0x7f08a1232384 in start_thread () from /lib64/libpthread.so.0 #10 0x7f08a75496af in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f08a7a49e40 (LWP 5250)): [KCrash Handler] #6 QtPrivate::QStringList_contains (that=that@entry=0x7f0880007760, str=..., cs=cs@entry=Qt::CaseSensitive) at tools/qstringlist.cpp:317 #7 0x7f08a7b3241a in QStringList::contains (cs=Qt::CaseSensitive, str=..., this=0x7f0880007760) at ../../include/QtCore/../../src/corelib/tools/qstringlist.h:214 #8 QDBusConnectionPrivate::isServiceRegisteredByThread (this=0x7f08800076d0, serviceName=...) at qdbusintegrator.cpp:2607 #9 0x7f08a7b3a4b8 in QDBusConnectionPrivate::sendWithReplyAsync (this=0x7f08800076d0, message=..., receiver=receiver@entry=0x0, returnMethod=returnMethod@entry=0x0, errorMethod=errorMethod@entry=0x0, timeout=timeout@entry=-1) at qdbusintegrator.cpp:2108 #10 0x7f08a7b29248 in QDBusConnectio
[krusader] [Bug 380878] fish protocol: Show user when logged in
https://bugs.kde.org/show_bug.cgi?id=380878 --- Comment #5 from Alex Bikadorov --- The full URL (with username and file path) in the panel tooltip is already implemented and will be in the next release. Suggestions 1 and 2 are difficult to implement because the widget used here (KUrlNavigator) is part of KF5-KIO and not directly included in Krusader. Another whish for the frameworks-kio would be better (the widget is also used e.g. in Dolphin). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380182] deleting several messages doesn't remove them from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #8 from David Faure --- Fix backported to https://commits.kde.org/akonadi/2dc7fbf569ba3f7eeef98fb818d7af0820caf7a3. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 380853] Opening file from within .zip creates two directories in /~
https://bugs.kde.org/show_bug.cgi?id=380853 Alex Bikadorov changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Alex Bikadorov --- The default setting is "/tmp/krusader.tmp" so the dot is not the problem. In fact this works fine on my system. Maybe some invalid/old setting was not applied - hard to say. But if everything works now, I close this. There are ~140 other bug reports to investigate .) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 343240] display bold folder name
https://bugs.kde.org/show_bug.cgi?id=343240 Alex Bikadorov changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from Alex Bikadorov --- Ok. Request is another font style option only for the folder names. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 381109] New: Duplicate Actions
https://bugs.kde.org/show_bug.cgi?id=381109 Bug ID: 381109 Summary: Duplicate Actions Product: kdenlive Version: 17.04.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: paul.ne...@gmx.at Target Milestone: --- There are two actions (Auswahlwerkzeug, Abstandwerkzeug) that want to use the same shortcut (). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 381110] New: Consistent Crashing in Kdenlive when using Custom Wipe Transition
https://bugs.kde.org/show_bug.cgi?id=381110 Bug ID: 381110 Summary: Consistent Crashing in Kdenlive when using Custom Wipe Transition Product: kdenlive Version: 17.04.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: m...@michaeltunnell.com Target Milestone: --- Created attachment 106047 --> https://bugs.kde.org/attachment.cgi?id=106047&action=edit backtrace data This bug occurs with Kdenlive 17.04.2 on KDE Neon with Plasma 5.10.1 I created a custom pgm wipe for the clock wipe to be started at 3 (right side) rather that from 12 (top). When selecting the wipe, Kdenlive crashes every time just from the selection of the wipe. I created a video to dmeonstrate the issue: https://youtu.be/G4H5Wy0Spl4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 380805] Generating Gallery: "Could not load XSL file"
https://bugs.kde.org/show_bug.cgi?id=380805 --- Comment #14 from Kurpfaelzer --- @all: THX a lot. The creation of a HTML Gallery is currently working without deleting any other directories or files within the target directory. Thank you for your great work. Just for you as an information: if you're creating a second or more additional gallery in the same target directory, the "index.html" file will point only to the last created gallery. The galleries created before are hard to access afterwards. Perhaps, this might be a good idea for the improvement of this great feature. Kind greetings, Stephan -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381111] New: Plasma crash - yet again
https://bugs.kde.org/show_bug.cgi?id=38 Bug ID: 38 Summary: Plasma crash - yet again Product: plasmashell Version: 5.9.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: manfred.kitzbich...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.33.0 Operating System: Linux 4.11.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I had Firefox open but wasn't actively browsing. I worked remotely using x2go on a server and left the computer for a few minutes. When I came back the screen was in power save mode and Firefox as well as Plasma had crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8cea6538c0 (LWP 4799))] Thread 22 (Thread 0x7f8bcc756700 (LWP 17300)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f8bf9376700 (LWP 1000)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f8bfb254700 (LWP 25728)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f8bfd75f700 (LWP 25076)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f8bfe060700 (LWP 9606)): #0 0x7f8ce32d39a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8ce441d37b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8ce810a2a5 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f8ce810ab9a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f8ce441c4c8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f8c0bbc6700 (LWP 9605)): #0 0x7f8cd9948b98 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #1 0x7f8cd9949d68 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #2 0x7f8cd994a089 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #3 0x7f8cd994a90a in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #4 0x7f8cda8fb43c in pa_mainloop_dispatch () at /usr/lib64/libpulse.so.0 #5 0x7f8cda8fb83c in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #6 0x7f8cda8fb8e0 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #7 0x7f8cda9098c9 in () at /usr/lib64/libpulse.so.0 #8 0x7f8cd995a258 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #9 0x7f8ce32cd537 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8ce3d2704f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f8c1728d700 (LWP 9604)): #0 0x7f8cdeb422d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8cdeafc454 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8cdeafca
[kpat] [Bug 380962] Cards shown to small
https://bugs.kde.org/show_bug.cgi?id=380962 --- Comment #3 from Enno Hillmer --- After it happens closed and restarted kpat and it happens again. Just retried it but it did not happen again Am 08.06.2017 um 22:19 schrieb Albert Astals Cid: > https://bugs.kde.org/show_bug.cgi?id=380962 > > Albert Astals Cid changed: > > What|Removed |Added > > CC||aa...@kde.org > > --- Comment #1 from Albert Astals Cid --- > So only happened once? > -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 380936] to compress a kexi db provides a crash
https://bugs.kde.org/show_bug.cgi?id=380936 Jarosław Staniek changed: What|Removed |Added CC||stan...@kde.org Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Jarosław Staniek --- Thanks Albrecht. Does Kexi crash or display error message? I'd like to make sure it is not an Kexi AppImage version but Arch package from 3.0.1. I've sent you file I compressed with Kexi 3.0.1. I have problems to reproduce crash. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 380937] Exporting a DB with Images into csv provides an unstructured file
https://bugs.kde.org/show_bug.cgi?id=380937 Jarosław Staniek changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||stan...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Jarosław Staniek --- Hello Albrecht, thanks for the report. Tested with Kexi 3.0.2, I'll send you the exported file Lehrertabelle_neu_2.csv. It can be even imported back into Kexi, I will send it too (table Lehrertabelle_neu_21), the only issue we have is from bug #349706 - we don't support importing columns of Object types. Any further comments from you are welcome, maybe I should go back to 3.0.1 exactly. Can you try the AppImage version? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380476] Kwin draws 1px overlay on the left screen border
https://bugs.kde.org/show_bug.cgi?id=380476 Andrius Štikonas changed: What|Removed |Added CC||andr...@stikonas.eu -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 344466] GIT integration context menu not present in GIT submodules
https://bugs.kde.org/show_bug.cgi?id=344466 Filzmaier Josef changed: What|Removed |Added CC||j.filzma...@gmx.at -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380902] kwin effects like "present windows" can't be exited with the keyboard
https://bugs.kde.org/show_bug.cgi?id=380902 --- Comment #6 from Xavion --- Cool, thanks for confirming my suspicion. It looks like something (minor) has changed in Qt v5.9.0 and KWin will need to accommodate. Let's hope one of the developers can get moving on this soon. I don't want to have to spend time rebuilding/downgrading my 19 Qt5 packages! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 344466] GIT integration context menu not present in GIT submodules
https://bugs.kde.org/show_bug.cgi?id=344466 --- Comment #4 from Filzmaier Josef --- I can confirm this bug/missing feature on more recent versions of kdevelop. System: Arch Linux Kdevelop Version: 5.1.1 Frameworks Version: 5.34.0 Qt Version 5.9.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381021] Hotkeys have no effect in the Kwin window management modes
https://bugs.kde.org/show_bug.cgi?id=381021 --- Comment #13 from Xavion --- Cool, thanks for confirming my suspicion. It looks like something (minor) has changed in Qt v5.9.0 and KWin will need to accommodate. Let's hope one of the developers can get moving on this soon. I don't want to have to spend time rebuilding/downgrading my 19 Qt5 packages! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381099] KWin crashes during window ALT+TAB window changing
https://bugs.kde.org/show_bug.cgi?id=381099 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Crash is in radeonsi_dri.so OpenGL drivers. Please report directly to radeonsi_dri developers via https://bugs.freedesktop.org/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379862] KWin crashed during login
https://bugs.kde.org/show_bug.cgi?id=379862 Christoph Feck changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #2 from Christoph Feck --- *** Bug 381108 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
