[Discover] [Bug 385704] New: All categories missing
https://bugs.kde.org/show_bug.cgi?id=385704 Bug ID: 385704 Summary: All categories missing Product: Discover Version: 5.11.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Updater Assignee: aleix...@kde.org Reporter: m...@krake.one Target Milestone: --- Created attachment 108331 --> https://bugs.kde.org/attachment.cgi?id=108331&action=edit Screenshot ¯\_(ツ)_/¯ -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 385622] Please add Back Button to Gwenview
https://bugs.kde.org/show_bug.cgi?id=385622 --- Comment #2 from Bobby --- Itsn't it a little insane to change every single handler has to be programmed to do the same thing as a back button... instead of just including a back button? Also, krusader HAS a back button. Meaning the behavior is correct for if your wanting to go up instead of back inside of krusaders windows. It would dolphin trying to emulate the back behavior inside of the up behavior that is the problem. -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 382291] System settings GTK apps configurations resets.
https://bugs.kde.org/show_bug.cgi?id=382291
--- Comment #8 from Rik Mills ---
(In reply to Fabian Vogt from comment #7)
> Likely a regression introduced by 34357f74ee2d98128ff423b0ec6ddcbf4232c475
> ("Make the kde-gtk-config kcm better at checking global gtk settings").
Seems likely, though need to test behaviour on reverting to see if so, and if
that is viable as a last resort. Obviously fixing would be better, so hopefully
Aleix Pol can chime in.
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 384176] QObject: Cannot create children for a parent that is in a different thread.
https://bugs.kde.org/show_bug.cgi?id=384176 --- Comment #10 from Hugo Pereira Da Costa --- So Compiled Qt 5.9 (5.9.3) Compiled breeze from master. Modified QT_PLUGIN_PATH to get the proper breeze, ran Krita (version 3.2.1), and I cannot reproduce. Nor can I reproduce with dolphin, gwenview, kate ... @wolthera can you confirm that you see the error with other applications than krita, and if yes, which one ? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385703] New: QtWebengine documentatio viewer causes KDevelop crash on exit
https://bugs.kde.org/show_bug.cgi?id=385703
Bug ID: 385703
Summary: QtWebengine documentatio viewer causes KDevelop crash
on exit
Product: kdevelop
Version: 5.1.80
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Documentation viewer
Assignee: kdevelop-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
Target Milestone: ---
The QtWebengine docviewer backend causes a systematic crash on exit on Mac (Qt
5.8.0).
1- launch a KDevelop session
2- click on the "Documentation" toolbar button
3- open the proposed (QtHelp) documentation section
4- repeat 2) to close the view
4- exit
After step 3) I see this on the calling terminal:
js: Not allowed to load local resource:
file:///var/folders/j1/1439ppj08xj8h6006s6drbq0gs/T/kdevelop.N13700
(NB: that's the simple CSS the plugin tries to use)
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
QObject::startTimer: Timers can only be used with threads started with QThread
js: Uncaught ReferenceError: mw is not defined
js: Uncaught ReferenceError: mw is not defined
QObject::startTimer: Timers can only be used with threads started with QThread
backtrace below. The crash is deep in Qt but I haven't seen it with any other
applications that use QWE.
* thread #1, name = 'CrBrowserMain', queue = 'com.apple.main-thread', stop
reason = EXC_BAD_ACCESS (code=1, address=0x8)
frame #0: QtWidgets`QWidget::~QWidget() [inlined]
QScopedPointer >::data() const
at qscopedpointer.h:140 [opt]
137
138 T *data() const Q_DECL_NOTHROW
139 {
-> 140 return d;
141 }
142
143 bool isNull() const Q_DECL_NOTHROW
(lldb) bt
* thread #1, name = 'CrBrowserMain', queue = 'com.apple.main-thread', stop
reason = EXC_BAD_ACCESS (code=1, address=0x8)
* frame #0: QtWidgets`QWidget::~QWidget() [inlined]
QScopedPointer >::data() const
at qscopedpointer.h:140 [opt]
frame #1: QtWidgets`QWidget::~QWidget() [inlined]
QScopedPointer >::pointer
qGetPtrHelper >
>(QScopedPointer > const&) at
qglobal.h:971 [opt]
frame #2: QtWidgets`QWidget::~QWidget() [inlined]
QWidget::d_func(this=0x) at qwidget.h:131 [opt]
frame #3: QtWidgets`QWidget::~QWidget(this=0x7fe35dc3abb0) at
qwidget.cpp:1602 [opt]
frame #4: QtWidgets`QWidget::~QWidget() [inlined]
QWidget::~QWidget(this=0x7fe35dc3abb0) at qwidget.cpp:1556 [opt]
frame #5: QtWidgets`QWidget::~QWidget(this=0x7fe35dc3abb0) at
qwidget.cpp:1556 [opt]
frame #6: QtCore`QObject::event(QEvent*) [inlined]
qDeleteInEventHandler(o=0x7fe35dc3abb0) at qobject.cpp:4557 [opt]
frame #7: QtCore`QObject::event(this=0x7fe35dc3abb0, e=)
at qobject.cpp:1254 [opt]
frame #8: QtWidgets`QWidget::event(this=0x7fe35dc3abb0,
event=0x7fe35945b110) at qwidget.cpp:9220 [opt]
frame #9: QtWidgets`QApplicationPrivate::notify_helper(this=,
receiver=0x7fe35dc3abb0, e=0x7fe35945b110) at qapplication.cpp:3745
[opt]
frame #10: QtWidgets`QApplication::notify(this=,
receiver=, e=) at qapplication.cpp:3708 [opt]
frame #11:
QtCore`QCoreApplication::notifyInternal2(receiver=0x7fe35dc3abb0,
event=0x7fe35945b110) at qcoreapplication.cpp:995 [opt]
frame #12:
QtCore`QCoreApplicationPrivate::sendPostedEvents(receiver=0x,
event_type=0, data=0x7fe352515d40) at qcoreapplication.h:231 [opt]
frame #13: QtQuick`QQuickRenderControl::~QQuickRenderControl() [inlined]
QQuickRenderControlPrivate::windowDestroyed() at qquickrendercontrol.cpp:190
[opt]
frame #14:
QtQuick`QQuickRenderControl::~QQuickRenderControl(this=0x7fe35b5465a0) at
qquickrendercontrol.
[kate] [Bug 371235] vi-mode: ":tabe anything" crashed KDevelop
https://bugs.kde.org/show_bug.cgi?id=371235 Diego Garcia changed: What|Removed |Added CC||dnico...@gmail.com --- Comment #2 from Diego Garcia --- I can make it crash with ":tabe anything" and ":tabe /file/that/doesn't/exist", but not with ":tabe /some/file/that/exists.py" or an empty ":tabe". It doesn't crash but it doesn't do anything either though. Seems the issue is when it can't find the file passed. -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 385701] rekonq crashes 5 minutes after loading js
https://bugs.kde.org/show_bug.cgi?id=385701 --- Comment #2 from romain.ni...@laposte.net --- I am using lxqt gui. top - 16:45:55 up 2:39, 6 users, load average: 3,31, 2,95, 2,05 Tasks: 154 total, 3 running, 151 sleeping, 0 stopped, 0 zombie %Cpu(s): 72,6 us, 27,4 sy, 0,0 ni, 0,0 id, 0,0 wa, 0,0 hi, 0,0 si, 0,0 st KiB Mem : 1545144 total, 454380 free, 556292 used, 534472 buff/cache KiB Swap: 4508784 total, 4488256 free,20528 used. 942356 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 19364 lubuntu 20 0 646544 273520 128968 R 17,4 17,7 3:14.28 rekonq 20132 lubuntu 20 0 88720 19480 15344 S 12,3 1,3 1:08.50 kio_file 20131 lubuntu 20 0 87452 18224 15344 S 10,1 1,2 0:23.05 kio_file 19466 lubuntu 20 0 102236 23748 20392 S 9,5 1,5 1:00.23 kio_http 19476 lubuntu 20 0 102064 23628 20392 S 9,2 1,5 0:57.31 kio_http 3121 root -51 0 0 0 0 S 7,3 0,0 1:52.92 irq/52-b43 20130 lubuntu 20 0 87956 18680 15344 S 7,3 1,2 0:36.68 kio_file 3348 root 20 0 21776 6392 5740 R 6,6 0,4 3:25.04 pbbuttonsd 3217 root 20 0 158728 61964 34324 S 4,7 4,0 4:29.53 Xorg -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 385701] rekonq crashes 5 minutes after loading js
https://bugs.kde.org/show_bug.cgi?id=385701 --- Comment #1 from romain.ni...@laposte.net --- Created attachment 108330 --> https://bugs.kde.org/attachment.cgi?id=108330&action=edit the saved big web page with kate 5 minutes after loading this page. Rekonq still does not show anything and consummes 80% cpu. But i haven't reproduce the crash yet. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 385549] The information on the recorded size does not appear to match
https://bugs.kde.org/show_bug.cgi?id=385549 --- Comment #3 from Cristian Aravena Romero --- Hello Leslie Zhai, What I do? Regards, -- Cristian -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 350299] Kate with vi mode, near end of file causes crash
https://bugs.kde.org/show_bug.cgi?id=350299 Diego Garcia changed: What|Removed |Added CC||dnico...@gmail.com --- Comment #3 from Diego Garcia --- Cannot reproduce on 17.08.2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 360558] Repeat character in vi mode doesn't work in Centos 7.2
https://bugs.kde.org/show_bug.cgi?id=360558 Diego Garcia changed: What|Removed |Added CC||dnico...@gmail.com --- Comment #1 from Diego Garcia --- Can't reproduce here on version 17.08.2 The characters are always repeated when going back to normal mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385681] Plasma crash when editing plasma layout (panel)
https://bugs.kde.org/show_bug.cgi?id=385681 Dominik Klementowski changed: What|Removed |Added CC||dominik...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385681] Plasma crash when editing plasma layout (panel)
https://bugs.kde.org/show_bug.cgi?id=385681 --- Comment #1 from Dominik Klementowski --- Created attachment 108329 --> https://bugs.kde.org/attachment.cgi?id=108329&action=edit New crash information added by DrKonqi plasmashell (5.11.0) using Qt 5.9.2 - What I was doing when the application crashed: Finished adjusting panel height then hidden popups with single click on desktop wallpaper. -- Backtrace (Reduced): #5 0x7f9a5143ec81 in wl_proxy_create_wrapper () at /usr/lib/libwayland-client.so.0 #6 0x7f99afbe27ea in () at /usr/lib/libEGL_mesa.so.0 #7 0x7f99afbcf70f in () at /usr/lib/libEGL_mesa.so.0 #8 0x7f9a3888e722 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so #9 0x7f9a3888cbce in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 375687] Kmail Not Deleting Email From Server
https://bugs.kde.org/show_bug.cgi?id=375687 Fab Stz changed: What|Removed |Added CC||fabstz...@yahoo.fr --- Comment #1 from Fab Stz --- Same problem here with a delay of 30days (POP account) Debian 9 (stretch) : kmail 5.2.3 & akonadi 5.2.2 Maybe this is a duplicate of bug 381631 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381631] KMail does not delete e-mails on POP3 server.
https://bugs.kde.org/show_bug.cgi?id=381631 Fab Stz changed: What|Removed |Added CC||fabstz...@yahoo.fr --- Comment #2 from Fab Stz --- Same problem here with a delay of 30days (POP account) Debian 9 (stretch) : kmail 5.2.3 & akonadi 5.2.2 Maybe this is a duplicate of #375687 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385695] "switch user" from screen lock shows blank screen
https://bugs.kde.org/show_bug.cgi?id=385695 --- Comment #2 from Märt Bakhoff --- Patch fixed the issue for me. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385702] New: System Monitor does not have an icon under wayland
https://bugs.kde.org/show_bug.cgi?id=385702 Bug ID: 385702 Summary: System Monitor does not have an icon under wayland Product: plasmashell Version: 5.10.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: andr...@stikonas.eu Target Milestone: 1.0 systemmontor is showing a generic Wayland icon. It's resourceName is systemmonitor but there is no corresponding desktop file, so no Icon is shown. Under X11 it shows the same icon as ksysguard. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385647] Revision Tools : no color
https://bugs.kde.org/show_bug.cgi?id=385647 --- Comment #5 from Bear --- (In reply to Nate Graham from comment #4) > Yes, I'm afraid there will not be a solution for Debian 8. By design, > Debian's packaging model results in extremely old, out-of-date packages > being used for years, and we just don't have the manpower to maintain so > many versions of our software. If you can't upgrade to Debian 9, you might > try seeing if there is a backported newer version of Okular that will run on > Debian 8: https://backports.debian.org/ I understand, thanks a lot for your comments and patience. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385595] KWin::WorkspaceWrapper signal clientAdded(KWin::Client *client) doesn't trigger on Wayland
https://bugs.kde.org/show_bug.cgi?id=385595 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 385701] New: rekonq crashes 5 minutes after loading js
https://bugs.kde.org/show_bug.cgi?id=385701 Bug ID: 385701 Summary: rekonq crashes 5 minutes after loading js Product: rekonq Version: 2.4.2 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: adj...@gmail.com Reporter: romain.ni...@laposte.net Target Milestone: --- Application: rekonq (2.4.2) KDE Platform Version: 4.14.36 Qt Version: 4.8.7 Operating System: Linux 4.9.0-0.bpo.2-powerpc ppc Distribution: Debian GNU/Linux 8.9 (jessie) -- Information about the crash: - What I was doing when the application crashed: Opened a bug web page with a lot of js. Cancelled the crypto mining in this page. Then Ctrl+u to open the source of the page. Kate opened and eats 80% cpu. Rekonq eats 20% cpu but is not in the foreground because i use Kate. 5 minutes after it crashes without any user input. - Unusual behavior I noticed: the system is unresponsive because of Kate consumming a lot. -- Backtrace: Application: rekonq (rekonq), signal: Aborted Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb79d1000 (LWP 13154))] Thread 9 (Thread 0xaa0d6320 (LWP 13447)): #0 0x0fdb8cc0 in syscall () at ../sysdeps/unix/sysv/linux/powerpc/syscall.S:30 #1 0x0acfd8cc in g_cond_wait () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #2 0x0aee4564 in () at /usr/lib/powerpc-linux-gnu/libgstreamer-1.0.so.0 #3 0x0aee598c in () at /usr/lib/powerpc-linux-gnu/libgstreamer-1.0.so.0 #4 0x0acd4a3c in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #5 0x0acd3a00 in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #6 0x0aa4b500 in start_thread (arg=0xaa0d6320) at pthread_create.c:335 Thread 8 (Thread 0xaa8d6320 (LWP 13446)): #0 0x0acfd6e0 in g_mutex_unlock () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #1 0x0ac9dd80 in g_main_context_dispatch () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #2 0x0ac9e388 in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #3 0x0ac9e930 in g_main_loop_run () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #4 0x04791cf8 in () at /usr/lib/powerpc-linux-gnu/libgio-2.0.so.0 #5 0x0acd3a00 in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #6 0x0aa4b500 in start_thread (arg=0xaa8d6320) at pthread_create.c:335 Thread 7 (Thread 0xab0d6320 (LWP 13445)): #0 0x0ac998c0 in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #1 0x0ac9d3ac in g_main_context_prepare () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #2 0x0ac9d3ac in g_main_context_prepare () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #3 0x0ac9e1f0 in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #4 0x0ac9e480 in g_main_context_iteration () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #5 0x0ac9e4fc in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #6 0x0acd3a00 in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #7 0x0aa4b500 in start_thread (arg=0xab0d6320) at pthread_create.c:335 Thread 6 (Thread 0xb55e5320 (LWP 13443)): #0 0x0fdb8cc0 in syscall () at ../sysdeps/unix/sysv/linux/powerpc/syscall.S:30 #1 0x0acfdac0 in g_cond_wait_until () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #2 0x0ac61d38 in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #3 0x0ac62858 in g_async_queue_timeout_pop () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #4 0xafe5f868 in () at /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so #5 0xafe5fb38 in () at /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so #6 0xafe41ac8 in () at /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so #7 0x0aa4b500 in start_thread (arg=0xb55e5320) at pthread_create.c:335 Thread 5 (Thread 0xb2cff320 (LWP 13180)): #0 0x0ac9d270 in g_main_context_prepare () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #1 0x0ac9e1f0 in () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #2 0x0ac9e480 in g_main_context_iteration () at /lib/powerpc-linux-gnu/libglib-2.0.so.0 #3 0x0b88eb0c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #4 0x0b84f520 in QEventLoop::processEvents(QFlags) () at /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #5 0x0b84f9f8 in QEventLoop::exec(QFlags) () at /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #6 0x0b7093fc in QThread::exec() () at /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #7 0x0b7095f4 in QThread::run() () at /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #8 0x0b70cd84 in () at /usr/lib/powerpc-linux-gnu/libQtCore.so.4 #9 0x0aa4b500 in start_thread (arg=0xb2cff320) at pthread_create.c:335 #10 0x0fdbd930 in clone () at ../sysdeps/unix/sysv/linux/powerpc/powerpc32/clone.S:82 Thread 4 (Thread 0xb3dff320 (LWP 13177)): #0 0x0aa53b58 in __pthread_cond_wait (cond=0xb5a5fc00, mutex=0xb5a5fbe4) at pthread_cond_wait.c:186 #1 0x0fdcf698 in __pthread_cond_wait (cond=, mutex=) at forward.c:149 #2 0x0f4b2974 in
[plasmashell] [Bug 385644] Memory leak freed by *starting* plasmashell
https://bugs.kde.org/show_bug.cgi?id=385644 --- Comment #4 from David Edmundson --- I'm more than happy to believe that you get memory back when you kill plasmashell. That's generic memory leak, search on here for the one about slideshow, if you're on Qt5.9.1 it's probably that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385644] Memory leak freed by *starting* plasmashell
https://bugs.kde.org/show_bug.cgi?id=385644 --- Comment #3 from Roland Vet --- Not exactly proof, but this is a before and after a restart. $ free -h totalusedfree shared buff/cache available Mem:15G9.1G158M5.7G6.3G344M Swap: 15G1.9G 13G $ killall plasmashell && kstart plasmashell $ free -h totalusedfree shared buff/cache available Mem:15G7.1G7.5G128M996M7.9G Swap: 15G7.0M 15G ~9G of memory freed by performing the restart, and all I can do is promise that just the killing of plasmashell doesn't give this result. Do not know what else I can provide to confirm. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 385675] KStars 2.7.10: Mouse cursor not visible on Wayland
https://bugs.kde.org/show_bug.cgi?id=385675 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |LATER Status|UNCONFIRMED |RESOLVED --- Comment #5 from Jasem Mutlaq --- KDE Neon Wayland doesn't even work so I can't test this. I'll mark this as Later. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381442] SVG starter icons not displayed in application menues/laumchers
https://bugs.kde.org/show_bug.cgi?id=381442 --- Comment #7 from Sefa Eyeoglu --- Are there any updates on this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385700] New: KWin Crash on aborted logout
https://bugs.kde.org/show_bug.cgi?id=385700 Bug ID: 385700 Summary: KWin Crash on aborted logout Product: plasmashell Version: 5.11.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bhol...@interactive.com.au CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.0) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.6-1.g5a88d59-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Click logout from the K Menu and then do not actually log out (click cancel) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe2f2733900 (LWP 11690))] Thread 15 (Thread 0x7fe1e2bdf700 (LWP 12536)): #0 0x7fe2eb657b5c in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe2ec49ef18 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe2ec49a3ac in () at /usr/lib64/libQt5Core.so.5 #3 0x7fe2ec49dd2e in () at /usr/lib64/libQt5Core.so.5 #4 0x7fe2eb651558 in start_thread () at /lib64/libpthread.so.0 #5 0x7fe2ebda245f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fe1e23de700 (LWP 12535)): #0 0x7fe2eb657b5c in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe2ec49ef18 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe2ec49a3ac in () at /usr/lib64/libQt5Core.so.5 #3 0x7fe2ec49dd2e in () at /usr/lib64/libQt5Core.so.5 #4 0x7fe2eb651558 in start_thread () at /lib64/libpthread.so.0 #5 0x7fe2ebda245f in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fe1e35ef700 (LWP 12514)): #0 0x7fe2eb65782d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe2ec49f04b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe2f01f0958 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fe2f01f0d8a in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fe2ec49dd2e in () at /usr/lib64/libQt5Core.so.5 #5 0x7fe2eb651558 in start_thread () at /lib64/libpthread.so.0 #6 0x7fe2ebda245f in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fe1f9c1b700 (LWP 12060)): #0 0x7fe2eb65782d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe2ec49f04b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe2f01f0958 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fe2f01f0d8a in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fe2ec49dd2e in () at /usr/lib64/libQt5Core.so.5 #5 0x7fe2eb651558 in start_thread () at /lib64/libpthread.so.0 #6 0x7fe2ebda245f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fe1fa597700 (LWP 11968)): #0 0x7fe2eb65782d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe2ec49f04b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe2f01f0958 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fe2f01f0d8a in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fe2ec49dd2e in () at /usr/lib64/libQt5Core.so.5 #5 0x7fe2eb651558 in start_thread () at /lib64/libpthread.so.0 #6 0x7fe2ebda245f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fe200deb700 (LWP 11957)): #0 0x7fe2eb65782d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe2ec49f04b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe2f01f0958 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fe2f01f0d8a in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fe2ec49dd2e in () at /usr/lib64/libQt5Core.so.5 #5 0x7fe2eb651558 in start_thread () at /lib64/libpthread.so.0 #6 0x7fe2ebda245f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fe204418700 (LWP 11943)): #0 0x7fe2ebd93808 in read () at /lib64/libc.so.6 #1 0x7fe2e6dd13c0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe2e6d8cc2b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe2e6d8d0f0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe2e6d8d25c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe2ec6c069b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe2ec66934a in QEventLoop::exec(QFla
[okular] [Bug 385647] Revision Tools : no color
https://bugs.kde.org/show_bug.cgi?id=385647 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Nate Graham --- Yes, I'm afraid there will not be a solution for Debian 8. By design, Debian's packaging model results in extremely old, out-of-date packages being used for years, and we just don't have the manpower to maintain so many versions of our software. If you can't upgrade to Debian 9, you might try seeing if there is a backported newer version of Okular that will run on Debian 8: https://backports.debian.org/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385699] Major lag cannot use Krita
https://bugs.kde.org/show_bug.cgi?id=385699 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- Hi Kim, If it worked fine until last night, something must have changed on your system. Maybe some other process is taking a lot of CPU, maybe you got a Windows update? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385699] New: Major lag cannot use Krita
https://bugs.kde.org/show_bug.cgi?id=385699 Bug ID: 385699 Summary: Major lag cannot use Krita Product: krita Version: 3.3.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: kimberlyd...@gmail.com Target Milestone: --- Hello, Krita was working great until last night. Then when trying to paint strokes with any brush on canvas it just lags (sits there really) and is not usable. I can click on file and the action I was attempting works,and go back to canvas, but this is impossible to use Krita this way, still a huge lag. Any thoughts? Thanks Kim -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 385697] New session in split view
https://bugs.kde.org/show_bug.cgi?id=385697 Daniel changed: What|Removed |Added CC||d...@s-base.eu --- Comment #2 from Daniel --- Thank you for explanation, so yea, I want option to add new terminal session to right/down like in Terminator :) I hope it will be possible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around
https://bugs.kde.org/show_bug.cgi?id=385594 Nikolay Zlatev changed: What|Removed |Added CC||n...@astrapaging.com --- Comment #22 from Nikolay Zlatev --- (In reply to Kai Uwe Broulik from comment #18) > Please give a try to > https://phabricator.kde.org/D8257 > and more importantly > https://phabricator.kde.org/D8258 After recompiling libtaskmanager patched with D8257 and D8258 everything seem's to work fine (arch). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 385697] New session in split view
https://bugs.kde.org/show_bug.cgi?id=385697 Egmont Koblinger changed: What|Removed |Added CC||egm...@gmail.com --- Comment #1 from Egmont Koblinger --- Indeed what Konsole and Terminator do are two completely different things. What Konsole has is called "split view" because it indeed splits the _view_ of the given terminal emulator session. Note that Terminator doesn't call its feature "split view", it avoids using the word "view" exactly because it does not offer multiple "views" to the same terminal. The feature it provides is simply called "split" in the menu, or "split terminals" in the manual page. Another popular choice for the so-called "paned" interface (what you're asking for) is Tilix, which calls the same feature "Add terminal right/down". (On the other hand, Terminator, Tilix and other VTE-based emulators cannot do a konsole-like "split view" because the underlying VTE terminal emulation widget doesn't support this.) (I'm not a konsole developer so I cannot comment on whether this feature will be implemented.) -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 385396] Latest Valgrind Results (tons of errors) and displayOnStart=false crashes
https://bugs.kde.org/show_bug.cgi?id=385396 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #5 from Emmanuel Lepage Vallée --- Done -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 385698] New: Splitter in places
https://bugs.kde.org/show_bug.cgi?id=385698 Bug ID: 385698 Summary: Splitter in places Product: dolphin Version: 17.08.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: d...@s-base.eu Target Milestone: --- Hello, i would like to have option to add a splitter into places, for example: Home Network Root Trash - - SPLITTER - - Documents Images Music Videos -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 385588] Sorting and groupping items by rating, tags, comments causes invalid selection when navigating back to folder
https://bugs.kde.org/show_bug.cgi?id=385588 Sebastian Arndt changed: What|Removed |Added CC||sebastian.arnd...@gmail.com --- Comment #2 from Sebastian Arndt --- (In reply to aldo.mateli from comment #1) > Apparently this also happens without groupping as well. Hello Aldo, I was able to reproduce this issue. Maybe I'll find the time to take a look into this. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 385697] New: New session in split view
https://bugs.kde.org/show_bug.cgi?id=385697 Bug ID: 385697 Summary: New session in split view Product: konsole Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: split-view Assignee: konsole-de...@kde.org Reporter: tomsk.slo...@gmail.com Target Milestone: --- Hello, if I split view in Konsole, it just split view in same session. I would like to see split view functionality in Konsole like in Terminator. This split view functionality in Konsole is useless, because if I want a new session I need to open a new tab, but I dont want to open new tabs, I hate tabs. So for now Im going to use Terminator. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385695] "switch user" from screen lock shows blank screen
https://bugs.kde.org/show_bug.cgi?id=385695 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://cgit.kde.org/plasma ||-workspace.git/commit/?id=a ||c40f7dec47df9c48fa55d90be67 ||ea4cbebcb09d Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||k...@privat.broulik.de Version Fixed In||5.11.1 --- Comment #1 from Kai Uwe Broulik --- Should be fixed by [1] which affected the User Switcher and probably affected the lock screen in the same fasion. [1] https://cgit.kde.org/plasma-workspace.git/commit/?id=ac40f7dec47df9c48fa55d90be67ea4cbebcb09d -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 385354] New folder has > symbol
https://bugs.kde.org/show_bug.cgi?id=385354 --- Comment #2 from Germano Massullo --- 17.04.1 here. I will again try as soon we get a new Dolphin version on Fedora 26 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 385354] New folder has > symbol
https://bugs.kde.org/show_bug.cgi?id=385354 Sebastian Arndt changed: What|Removed |Added CC||sebastian.arnd...@gmail.com --- Comment #1 from Sebastian Arndt --- Hello Germano, I tried as you said, but I was'nt able to reproduce this behavior. If I add a new folder in detailed few it will not have that symbol. Maybe this is already fixed? I'm on "Version 17.08.1" (see in Settings->Help->About Dolphin), what are you using? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385696] add the ability to create a virtual sound ouput device made of selected sound output devices
https://bugs.kde.org/show_bug.cgi?id=385696 Harald Sitter changed: What|Removed |Added Product|Phonon |plasma-pa Target Milestone|4.8 |--- Assignee|sit...@kde.org |now...@gmail.com CC||plasma-b...@kde.org Version|4.9.0 |unspecified Component|Pulsesupport|general -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 385696] New: add the ability to create a virtual sound ouput device made of selected sound output devices
https://bugs.kde.org/show_bug.cgi?id=385696 Bug ID: 385696 Summary: add the ability to create a virtual sound ouput device made of selected sound output devices Product: Phonon Version: 4.9.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Pulsesupport Assignee: sit...@kde.org Reporter: philippe.roub...@free.fr CC: co...@mageia.org, myr...@kde.org Target Milestone: 4.8 i want to connect 2 headsets for me and my friend to see a video. i plug 2 bluetooth dongles then i paired a headset to one dongle i paired the other headset to the other dongle then i created a virtual output of all outputs with audio volume settings tool great it works well but i don't need speakers output. please supply the ability to select only the 2 headset and more generally supply the ability to create a virtual sound ouput device made of selected sound output devices i know that pa supply this feature with module-combine-sink https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#index11h3 thanks -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385080] Crash while picking mail recipient list
https://bugs.kde.org/show_bug.cgi?id=385080
--- Comment #2 from Peter ---
Hello,
Am Donnerstag, 12. Oktober 2017, 20:02:20 CEST schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=385080
>
> --- Comment #1 from Christoph Feck ---
> Please add the backtrace for this crash to this bug report. You can find it
> on the 'Developer Information' tab in the crash dialog window.
>
I am deeply sorry:
I have installed kdepimlibs-debuginfo and kontact-debuginfo,
the crash is reproducable, but all the information I get is
"Application: Kontact (kontact), signal: Segmentation fault"
under a headline saying the debug informations are useless.
Using gdb, gdb demands to install about a hundred debug libraries after having
cought the segfault.
"Thread 1 "kontact" received signal SIGSEGV, Segmentation fault.
0x7545d634 in QSortFilterProxyModel::sibling(int, int, QModelIndex
const&) const() from /usr/lib64/libQt5Core.so.5
Missing separate debuginfos, use: zypper install Mesa-
debuginfo-17.0.5-176.1.x86_64 Mesa-libGL1-debuginfo-17.0.5-176.1.x86_64 ... "
I hesitate to do that as it will probably clutter my system.
Peter Willadt
fon +49 72 31 10 24 30
fax +49 72 31 13 95 43
%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-
\def\hackerspiel{\message{User:}
\read-1to\nam\message{Password:}
\read-1to\pwd\message{Sorry, invalid. Try again:}
\next}\let\next\hackerspiel\hackerspiel
%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-%-
--
You are receiving this mail because:
You are watching all bug changes.
[colord-kde] [Bug 378407] no more monitor settings
https://bugs.kde.org/show_bug.cgi?id=378407 Philippe ROUBACH changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385695] New: "switch user" from screen lock shows blank screen
https://bugs.kde.org/show_bug.cgi?id=385695 Bug ID: 385695 Summary: "switch user" from screen lock shows blank screen Product: plasmashell Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: a...@sigil.red CC: plasma-b...@kde.org Target Milestone: 1.0 Steps: 1) Log in to plasma desktop from SDDM 2) Press Ctrl+Alt+L, screen lock appears 3) Click the button "Switch user", session picker appears 4) Choose "new session", click button "switch session" Expected results: Login dialog appears on a new tty. Actual results: Animation hides all controls. Blank screen with solid background color remains visible. Blindly typing in the current user's password and pressing enter unlocks the screen for the current user. Broken on plasma 5.11. Works on plasma 5.10. Pressing ALT+F2 and choosing "New session" from the desktop sessions plugin in plasma 5.11 works - tty is switched and the login dialog becomes visible. Reproduced with plasma 5.11, frameworks 5.38, qt 5.9.2, gentoo/systemd ~amd64. Please let me know if I can help with anything. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385694] New: Backspace deletes the wrong character in Arabic text
https://bugs.kde.org/show_bug.cgi?id=385694 Bug ID: 385694 Summary: Backspace deletes the wrong character in Arabic text Product: kate Version: 17.08.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: fahad.alsa...@gmail.com Target Milestone: --- In Arabic text, If you have only one line, things looks fine but if you have multi-lines and you enabled dynamic word warp, if you click in the middle line and press backspace button, the forward character will be deleted instead of the backward letter. This bug is very annoyed. It makes using kate for text editing in Arabic frustrating experience. Steps to reproduce: 1- make sure that you enabled dynamic word warp. 2- enter any Arabic text, that get warped, such as: السلام السلام السلام السلام السلام السلامالسلام السلام السلامالسلام السلام السلام السلام السلام السلامالسلام السلام السلام السلام السلام السلامالسلام السلام السلامالسلام السلام السلام السلام السلام السلام 3- choose any word and try to delete a letter. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 385693] New: krunner text input broken with wayland
https://bugs.kde.org/show_bug.cgi?id=385693 Bug ID: 385693 Summary: krunner text input broken with wayland Product: krunner Version: 5.11.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: a...@sigil.red Target Milestone: --- Steps: 1) start plasma wayland session from sddm 2) press alt+f2, krunner appears, text field has focus 3) type "dolphin" Expected result: Krunner text field contains "dolphin". Actual result: Each typed character replaces the previous character: "" -> "d" -> "o" -> "l" etc. Backspace does not work. Reproduced with plasma 5.11, frameworks 5.38, qt 5.9.2 on gentoo/systemd ~amd64. Krunner was working in plasma 5.10 wayland. Krunner works with plasma 5.11 + x11. Other applications, such as konsole, accept input normally with wayland. Let me know if I can help in any way. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385692] Application windows (such as scrolling in kate) on EGL flickers.
https://bugs.kde.org/show_bug.cgi?id=385692 David Edmundson changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385692] New: Application windows (such as scrolling in kate) on EGL flickers.
https://bugs.kde.org/show_bug.cgi?id=385692 Bug ID: 385692 Summary: Application windows (such as scrolling in kate) on EGL flickers. Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@davidedmundson.co.uk Target Milestone: --- I have the issue Marco described on the mailing list. Symptoms: - open a big file in kate - scroll quickly - flickers like crazy This happens on kate, but never gedit Marco says this doesn't happen in Weston This does happen on neseted wayland sessions It doesn't happen on testRenderingServer in kwayland (which is SHM based) I'm pretty confident the real bug is in the QPA, but I'll track it here. We can see in wayland debug: [2180114.022] -> wl_surface@40.frame(new id wl_callback@226) [2180114.066] -> wl_surface@40.attach(wl_buffer@160, 0, 0) [2180114.208] -> wl_surface@40.damage(529, 40, 2, 438) [2180114.255] -> wl_surface@40.damage(33, 478, 498, 2) [2180114.303] -> wl_surface@40.commit() [2180114.324] -> wl_surface@40.frame(new id wl_callback@139) [2180114.360] -> wl_surface@40.attach(wl_buffer@160, 0, 0) [2180114.405] -> wl_surface@40.damage(33, 38, 498, 2) [2180114.442] -> wl_surface@40.damage(33, 40, 2, 438) [2180114.492] -> wl_surface@40.damage(529, 40, 2, 438) [2180114.538] -> wl_surface@40.damage(33, 478, 498, 2) [2180114.585] -> wl_surface@40.commit() ... [2180120.358] wl_buffer@160.release() [2180120.378] wl_buffer@160.release() This looks to me like it's attaching the same buffer twice (and in some cases 4/5 times) before getting the release of the buffer We could be reading those pixels after the first commit; hence flicker -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable
https://bugs.kde.org/show_bug.cgi?id=332512 stefanpro...@kolabnow.com changed: What|Removed |Added CC||stefanpro...@kolabnow.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385640] KDevelop: DocumentationView causing crash on exit [DocumentationView::initialize]
https://bugs.kde.org/show_bug.cgi?id=385640 --- Comment #8 from RJVB --- > What's the problem with running it under GDB? Nothing, except that it takes minutes just to get the app to start (lldb is a bit faster on my Mac) and it takes up gobs of additional RAM. That's OK when I need actual debugger functionality like stepping through code or examining variables. It's not feasible as a general runtime environment just to obtain a backtrace. Esp. when you're rebuilding and restarting the app over an over again to test tweaks like the standalone dockwidget (= how I spent much of my yesterday). My main reason for contributing is that I use the application (which is what I try to do between patch revision procedures), and that it's a priori more efficient to get my modifications upstreamed instead of maintaining a fork that will inevitably become too much to handle. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 385691] New: Remove all non-basetype C Style casts
https://bugs.kde.org/show_bug.cgi?id=385691 Bug ID: 385691 Summary: Remove all non-basetype C Style casts Product: ring-kde Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elv1...@gmail.com Reporter: elv1...@gmail.com Target Milestone: --- I found at least 2 that are (hardly) exploitable already, my guess is that there is a few more that shift the ((T*)this) by a few bytes. There is a Clang Tidy plugin for this. The latest git version of ASAN also catch them. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385640] KDevelop: DocumentationView causing crash on exit [DocumentationView::initialize]
https://bugs.kde.org/show_bug.cgi?id=385640 --- Comment #7 from RJVB --- (In reply to Kevin Funk from comment #6) > Yes. It told me you haven't fully understood the problem I've understood (accepted) that the complexity of the plugin/toolview architecture is in large part beyond me, just like you yourself have accepted that the itemrepository issue is beyond you. I may be wrong about that, but I've been looking on and off at the seemingly random aspect of the documentation toolview for probably more than a year now (and I've been putting up with it since v4.x). And so what if we figure out where the creation comes from. We put the "don't do this when shutting down" check there? > hacks which inevitably may cause other crashes (i.e. when DocumentationView > is being destructed again, trying to cleanup resources which were never > initialized properly). Seriously? There's only a default dtor, which doesn't know about anything allocated dynamically through the ctor after the early return. > > Nothing done in that ctor is crucial unless you use the instance, and > > that's not going to happen. > > And you know that it isn't used based on...? How can you know it's not being > used if you don't know where/when the class is being instantiated? Ok, can you explain how a toolview could use the stuff it sets up for letting the user interact with it after the program exit, if it cannot stop that process? I'll give it to you that the return was maybe a bit too early and should rather exclude only the invocation of the initialisation method. In practice I've seen the warning print a few times without any further crashing. I wouldn't have committed this without testing. > https://woboq.com/blog/nice-debug-output-with-qt.html -- grep for > "backtrace" -- you can enable them for e.g. warnings exclusively. That might be useful for critical messages, but still, Linux only apparently, and I don't think you have this kind of control in the code just before a specific log output. Or is there a way to do that? > Please note that "drawn-out" review procedures are only necessary in > "special cases". They tend to get drawn out for other reasons too, ultimately leading to a core dev "remote controlling" what boils down to one of his clones to write a piece of code. It's just more efficient to skip the remote clone bit in those cases. > Yes, or the original author could have at least committed that hunk > separately, with a proper commit message explaining what this change does. I am the original author ... can I take that as a green light to commit it? (I kind of expected that Friedrich would commit this, as it's a fix for something he introduced.) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 385690] New: yakuake keeps open after focus los
https://bugs.kde.org/show_bug.cgi?id=385690 Bug ID: 385690 Summary: yakuake keeps open after focus los Product: yakuake Version: 3.0.4 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: spikyatli...@gmail.com Target Milestone: --- Yesterday after plasma system update yakuake stops to hide after focus lost. I don´t know why. I´ve reinstalled yakuake without success. regards -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385640] KDevelop: DocumentationView causing crash on exit [DocumentationView::initialize]
https://bugs.kde.org/show_bug.cgi?id=385640 --- Comment #6 from Kevin Funk --- > Have you read the ticket and commit message? I cannot reproduce the issue at > will either. It happens and *will* (always?) provoke a crash, but it does so > seemingly randomly. Yes. It told me you haven't fully understood the problem and you're adding hacks which inevitably may cause other crashes (i.e. when DocumentationView is being destructed again, trying to cleanup resources which were never initialized properly). > If you want to run each and every KDevelop session under a debugger with a > breakpoint set, be our guest (our as in everyone using the app). I don't have > the resources for that. What's the problem with running it under GDB? Not having the resources for that is not an excuse if you want to actively develop and file patches for a project. > I don't agree with your analysis in this case. There's no point in setting up > a DocumentationView when the application is exitting. I don't or didn't concur with that. > Nothing done in that ctor is crucial unless you use the instance, and that's > not going to happen. And you know that it isn't used based on...? How can you know it's not being used if you don't know where/when the class is being instantiated? > Alternatively, please provide a utility to print a backtrace in ICore or > wherever appropriate if there isn't already. I'll use that to determine where > the call comes from. https://woboq.com/blog/nice-debug-output-with-qt.html -- grep for "backtrace" -- you can enable them for e.g. warnings exclusively. > (Yes, I could write such a utility class myself but this time I'm going to > leave it to some of the powers that be who don't need drawn-out review > procedures.) I see what you're hinting at. Please note that "drawn-out" review procedures are only necessary in "special cases". It's definitely not happing for the majority of incoming reviews for KDevelop. The key point in not ending up with lengthy discussions in reviews is a) having a good understanding of the problem at hand before even trying put up patches for review, b) focusing on one issue at a time during discussions, c) posting a patch where you have good confidence that it is the right fix to begin with and not a series of obvious work-arounds. > Oh, and you could have left the secondary fix in that commit. Yes, or the original author could have at least committed that hunk separately, with a proper commit message explaining what this change does. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354227] kcm_kscreen is too high
https://bugs.kde.org/show_bug.cgi?id=354227 Christoph Feck changed: What|Removed |Added CC||woodguy552...@gmail.com --- Comment #34 from Christoph Feck --- *** Bug 385680 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 385680] Dialog box too large for 768 pixel high display. Clunky design needs to be setup every time external display is added!
https://bugs.kde.org/show_bug.cgi?id=385680 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 354227 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385689] Task manager icons reorder
https://bugs.kde.org/show_bug.cgi?id=385689 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 385594 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around
https://bugs.kde.org/show_bug.cgi?id=385594 Kai Uwe Broulik changed: What|Removed |Added CC||m...@krake.one --- Comment #21 from Kai Uwe Broulik --- *** Bug 385689 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385640] KDevelop: DocumentationView causing crash on exit [DocumentationView::initialize]
https://bugs.kde.org/show_bug.cgi?id=385640 --- Comment #5 from RJVB --- Created attachment 108328 --> https://bugs.kde.org/attachment.cgi?id=108328&action=edit debugging patch I'll be running with this myself (in hope it's safe to call KMessageBox when this issue occurs). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385689] New: Task manager icons reorder
https://bugs.kde.org/show_bug.cgi?id=385689 Bug ID: 385689 Summary: Task manager icons reorder Product: plasmashell Version: 5.11.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: m...@krake.one CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 108327 --> https://bugs.kde.org/attachment.cgi?id=108327&action=edit Video of the glitch In Plasma 5.11, launched pinned icons jump to the end of the icon list instead of staying in their usual position. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 315482] gwenview should follow symlinks on the "copy to..." operation.
https://bugs.kde.org/show_bug.cgi?id=315482 --- Comment #4 from Shlomi Fish --- (In reply to Nate Graham from comment #3) > Thanks for the patch, Shlomi! Sadly, reviewboard is gone now, recently > replaced with phabricator. If your patch was never accepted, I encourage you > to submit it again to http://phabricator.kde.org/! I will make sure folks > see it. Hi Nate! Please see https://phabricator.kde.org/D8274 - note that I have problems with my right hand. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 385161] Can't send file from Android to PC
https://bugs.kde.org/show_bug.cgi?id=385161 --- Comment #1 from sun...@hotmail.ru --- Ok its strange. I was able to successfully exchange files with the same phone but different systems(notebooks with the same Manjaro x64 and x32) but not with my PC. Creating new user on PC doesn't help, clearing kdeconnect data on the phone doesn't help. Is there anything else i can look at? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385640] KDevelop: DocumentationView causing crash on exit [DocumentationView::initialize]
https://bugs.kde.org/show_bug.cgi?id=385640
--- Comment #4 from RJVB ---
(In reply to Kevin Funk from comment #2)
> Note: I can't reproduce your problem.
Could you please add something like this, at least? (Or use an ASSERT if you
run with those in place.)
--- a/kdevplatform/documentation/documentationview.cpp
+++ b/kdevplatform/documentation/documentationview.cpp
@@ -62,6 +62,10 @@ DocumentationView::DocumentationView(QWidget* parent,
ProvidersModel* model)
mCurrent = mHistory.end();
+if (ICore::self()->shuttingDown()) {
+qFatal("DocumentationView created during shutdown");
+}
+
setFocusProxy(mIdentifiers);
QMetaObject::invokeMethod(this, "initialize", Qt::QueuedConnection);
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 384176] QObject: Cannot create children for a parent that is in a different thread.
https://bugs.kde.org/show_bug.cgi?id=384176 --- Comment #9 from Boudewijn Rempt --- Hm... Yes, we started using Qt Quick, but not QtQuickControls, afaik, but... Wolthera's report was from before that! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355935] Font kerning is incorrect
https://bugs.kde.org/show_bug.cgi?id=355935 --- Comment #25 from beojan --- In fact, it turns out the Aurorae KWin theme uses QML components from Plasma (specifically Plasma core), so this probably *is* a Plasma bug, rather than a Qt bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385640] KDevelop: DocumentationView causing crash on exit [DocumentationView::initialize]
https://bugs.kde.org/show_bug.cgi?id=385640 --- Comment #3 from RJVB --- Have you read the ticket and commit message? I cannot reproduce the issue at will either. It happens and *will* (always?) provoke a crash, but it does so seemingly randomly. If you want to run each and every KDevelop session under a debugger with a breakpoint set, be our guest (our as in everyone using the app). I don't have the resources for that. I don't agree with your analysis in this case. There's no point in setting up a DocumentationView when the application is exitting. Nothing done in that ctor is crucial unless you use the instance, and that's not going to happen. Alternatively, please provide a utility to print a backtrace in ICore or wherever appropriate if there isn't already. I'll use that to determine where the call comes from. (Yes, I could write such a utility class myself but this time I'm going to leave it to some of the powers that be who don't need drawn-out review procedures.) Oh, and you could have left the secondary fix in that commit. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 384658] Line indented automatically when entering one of the letters i,u,e,n,d,f in python code
https://bugs.kde.org/show_bug.cgi?id=384658 --- Comment #6 from Koichi Akabe --- At least, this bug is not happened with ktexteditor-5.37.0, and happened with ktexteditor-5.38.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385468] "Missing \"Version=5\", file '/usr/share/kconf_update/okular.upd' will be skipped."
https://bugs.kde.org/show_bug.cgi?id=385468 Achim Bohnet changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Achim Bohnet --- At least in the log kconf_update claims that it skips the conf file if a verison=5 is not at the right place ( locking at the upd files it looks like Version=5 has to be the first entry): $ journalctl --user | grep -i version=5 Okt 07 17:30:15 lap-allee plasma[10450]: "Missing \"Version=5\", file '/usr/share/kconf_update/krdb_libpathwipe.upd' will be skipped." Okt 07 17:30:15 lap-allee plasma[10450]: "Missing \"Version=5\", file '/usr/share/kconf_update/okular.upd' will be skipped." Okt 13 09:21:13 lap-allee plasma[1596]: "Missing \"Version=5\", file '/usr/share/kconf_update/krdb_libpathwipe.upd' will be skipped." Okt 13 09:21:13 lap-allee plasma[1596]: "Missing \"Version=5\", file '/usr/share/kconf_update/okular.upd' will be skipped." Okt 13 09:23:46 lap-allee plasma[2704]: "Missing \"Version=5\", file '/usr/share/kconf_update/krdb_libpathwipe.upd' will be skipped." Okt 13 09:23:46 lap-allee plasma[2704]: "Missing \"Version=5\", file '/usr/share/kconf_update/okular.upd' will be skipped." -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385647] Revision Tools : no color
https://bugs.kde.org/show_bug.cgi?id=385647 --- Comment #3 from Bear --- (In reply to Nate Graham from comment #1) > That's a really, really old version of Okular. I've been able to change > annotation colors in various newer versions of Okular for a long time. This > is almost certainly resolved in a newer version. If you can upgrade to > Debian 9, that has Okular from the KDE Applications 16.08.2 release, which > is much newer, and that should solve your problem Thanks for your comment; what's surprising is that with Debian Wheezy which probably had an older version of Okular than the on with Jessie I never met that problem. Since I do not intend to upgrade to Debian 9 by now, are we to understand that there is no solution with Debian 8 Jessie ? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385647] Revision Tools : no color
https://bugs.kde.org/show_bug.cgi?id=385647 Bear changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from Bear --- Thanks for your comment; what's surprising is that with Debian Wheezy which probably had an older version of Okular than the on with Jessie I never met that problem. Since I do not intend to upgrade to Debian 9 by now, are we to understand that there is no solution with Debian 8 Jessie ? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385640] KDevelop: DocumentationView causing crash on exit [DocumentationView::initialize]
https://bugs.kde.org/show_bug.cgi?id=385640 Kevin Funk changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #2 from Kevin Funk --- Note: I can't reproduce your problem. Tips to solve this correctly: Please put a breakpoint on "DocumentationView::DocumentationView(QWidget* parent, ProvidersModel* model)" and check where/when it is being called during shutdown. Post the backtrace, please. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 384176] QObject: Cannot create children for a parent that is in a different thread.
https://bugs.kde.org/show_bug.cgi?id=384176 --- Comment #8 from Hugo Pereira Da Costa --- (In reply to Boudewijn Rempt from comment #7) > Hm... We probably also should debug this inside Krita, because it only > happens in master, not in 3.3. Hi Boud, I'm compiling Qt 5.9 as we speak to try reproduce. My impression is that the warning is (among other things) a side effect of using QtQuickControls. Did you by any chance introduce some in Krita in recent versions ? If yes that would explain. Hugo -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 384176] QObject: Cannot create children for a parent that is in a different thread.
https://bugs.kde.org/show_bug.cgi?id=384176 --- Comment #7 from Boudewijn Rempt --- Hm... We probably also should debug this inside Krita, because it only happens in master, not in 3.3. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 384658] Line indented automatically when entering one of the letters i,u,e,n,d,f in python code
https://bugs.kde.org/show_bug.cgi?id=384658 --- Comment #5 from Koichi Akabe --- This bug is not happened with ktexteditor-5.28.0 + kate-17.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 380123] Documentation browser history ignores followed links
https://bugs.kde.org/show_bug.cgi?id=380123 Kevin Funk changed: What|Removed |Added CC||aleix...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385644] Memory leak freed by *starting* plasmashell
https://bugs.kde.org/show_bug.cgi?id=385644 --- Comment #2 from Roland Vet --- (In reply to David Edmundson from comment #1) > That's not how Linux memory works. This is just what I observe. My guess is that in the process of starting plasmashell something else gets restarted which clears the leak. I can't pinpoint what the memory is being used for. All I know is that over the duration of a few hours the used memory pages increases to the point where swapping starts and eventually the entire system slows down to an unbearable crawl. If you could help me pinpoint the source I might be able to be more descriptive. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around
https://bugs.kde.org/show_bug.cgi?id=385594 stephane changed: What|Removed |Added CC||steph...@scachemaille.ch --- Comment #20 from stephane --- (In reply to Kai Uwe Broulik from comment #18) > Please give a try to > https://phabricator.kde.org/D8257 > and more importantly > https://phabricator.kde.org/D8258 I rebuilt the archlinux package (I'm on manjaro) using the 2 patch above and all the icons on my icon only task manager works like as before. they are not jumping around anymore. I use only 1 desktop and 1 activity I can't test other weird comportment that was seen by Michail Vourlakos. if some other test is needed. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 384658] Line indented automatically when entering one of the letters i,u,e,n,d,f in python code
https://bugs.kde.org/show_bug.cgi?id=384658 Koichi Akabe changed: What|Removed |Added CC||vbkaise...@gmail.com --- Comment #4 from Koichi Akabe --- I also confirmed with 17.04.3 (Ubuntu package version: 4:17.04.3-0ubuntu1) -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 385688] New: Dragon player crashes after successfully playing a music video.
https://bugs.kde.org/show_bug.cgi?id=385688 Bug ID: 385688 Summary: Dragon player crashes after successfully playing a music video. Product: dragonplayer Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: staka...@freenet.de CC: myr...@kde.org Target Milestone: --- Application: dragon (17.04.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.87-25-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Playing a music video of the format webm. The video played correctly the crash happens after reprodution. The reproduction was not full screen but to a default size fixed to the left border of a 12" screen covering 1/3 of display. At the time of the crash non related programms (calibre and dolphin) were in use. The player played in the background. -- Backtrace: Application: Dragon Player (dragon), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fae1dcf8900 (LWP 8160))] Thread 3 (Thread 0x7fae03774700 (LWP 8162)): #0 0x7fae190a820d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fae1588b314 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7fadfc00fdf0, timeout=-1, context=0x7fadfc000990) at gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7fadfc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7fae1588b42c in g_main_context_iteration (context=0x7fadfc000990, may_block=1) at gmain.c:3901 #4 0x7fae19cb21ab in QEventDispatcherGlib::processEvents (this=0x7fadfc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7fae19c5fbfb in QEventLoop::exec (this=this@entry=0x7fae03773ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #6 0x7fae19a9af5a in QThread::exec (this=this@entry=0x7fae1a32fce0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #7 0x7fae1a0c6295 in QDBusConnectionManager::run (this=0x7fae1a32fce0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:189 #8 0x7fae19a9fa29 in QThreadPrivate::start (arg=0x7fae1a32fce0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:365 #9 0x7fae16835744 in start_thread (arg=0x7fae03774700) at pthread_create.c:334 #10 0x7fae190b0aad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fae09a08700 (LWP 8161)): #0 0x7fae190a820d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fae164013e2 in poll (__timeout=-1, __nfds=1, __fds=0x7fae09a07bc0) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x1dfb240, cond=cond@entry=0x1dfb280, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x7fae16402fcf in xcb_wait_for_event (c=0x1dfb240) at xcb_in.c:693 #4 0x7fae0bf630d9 in QXcbEventReader::run (this=0x1e05410) at qxcbconnection.cpp:1331 #5 0x7fae19a9fa29 in QThreadPrivate::start (arg=0x1e05410) at thread/qthread_unix.cpp:365 #6 0x7fae16835744 in start_thread (arg=0x7fae09a08700) at pthread_create.c:334 #7 0x7fae190b0aad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fae1dcf8900 (LWP 8160)): [KCrash Handler] #6 0x7fae18ffb8d7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x7fae18ffccaa in __GI_abort () at abort.c:78 #8 0x7fae1202d29d in flush (f=f@entry=0x262d800) at pulsecore/fdsem.c:170 #9 0x7fae1202dca3 in pa_fdsem_after_poll (f=0x262d800) at pulsecore/fdsem.c:314 #10 0x7fae1204586d in semread_cb (m=, e=, fd=, events=, userdata=0x263ab20) at pulsecore/srbchannel.c:209 #11 0x7fae15da1ba7 in dispatch_func (source=0x21e2e80, callback=, userdata=) at pulse/glib-mainloop.c:584 #12 0x7fae1588b134 in g_main_dispatch (context=0x7fae040016f0) at gmain.c:3154 #13 g_main_context_dispatch (context=context@entry=0x7fae040016f0) at gmain.c:3769 #14 0x7fae1588b388 in g_main_context_iterate (context=context@entry=0x7fae040016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3840 #15 0x7fae1588b42c in g_main_context_iteration (context=0x7fae040016f0, may_block=1) at gmain.c:3901 #16 0x7fae19cb218c in QEventDispatcherGlib::processEvents (this=0x1e288c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #17 0x7fae19c5fbfb in QEventLoop::exec (this=this@entry=0x7ffeb61a8fe0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #18 0x7fae19c67ae6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1285 #19 0x7fae1a4268ec
[Breeze] [Bug 384176] QObject: Cannot create children for a parent that is in a different thread.
https://bugs.kde.org/show_bug.cgi?id=384176 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #6 from Boudewijn Rempt --- Any progress here? I'm getting this all the time as well, now that I've moved on from using my own Qt 5.6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385684] JPEG Export Improvement [Feature Request]
https://bugs.kde.org/show_bug.cgi?id=385684 Boudewijn Rempt changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/e18081132943dedfde852dcd ||5d46460080a73725 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- Git commit e18081132943dedfde852dcd5d46460080a73725 by Boudewijn Rempt. Committed on 13/10/2017 at 07:06. Pushed by rempt into branch 'master'. Rename the compression slider to quality It used to be call "Quality" before, but was renamed to compression without changing the logic in response to CCBUG:328073 , which only tried to fix the precision. The slider, however, does not indicate compression at all. M +1-1plugins/impex/jpeg/kis_wdg_options_jpeg.ui https://commits.kde.org/krita/e18081132943dedfde852dcd5d46460080a73725 -- You are receiving this mail because: You are watching all bug changes.
