[ksmserver] [Bug 383638] Lock/Unlock Widget - suspend button broken
https://bugs.kde.org/show_bug.cgi?id=383638 --- Comment #3 from Swipe --- These are the packages that went on to stop it working. I can double check this on my other 2 arch PCs too: https://pastebin.com/eSA6puz6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 383848] KSyntaxHighlighting 5.37 detects normal text files as poweshell script
https://bugs.kde.org/show_bug.cgi?id=383848 Till Schäfer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Till Schäfer --- fixed in master: https://phabricator.kde.org/R216:26daf7ee5b4a4534d918ed7d9e66d64cb30b0c26 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383860] New: [Kate] Regular .txt files are recognized as PowerShell files
https://bugs.kde.org/show_bug.cgi?id=383860 Bug ID: 383860 Summary: [Kate] Regular .txt files are recognized as PowerShell files Product: kate Version: 17.08.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Currently Kate highlights syntax in simple text files without any code recognizing them as 'PowerShell' files. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 383758] Report unreadable because element outlines are to thick
https://bugs.kde.org/show_bug.cgi?id=383758 --- Comment #6 from Stephane MANKOWSKI --- I am not able to reproduce the bug for points. I did a correction but didn't test it. Could you tell me if this is correct? -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 383758] Report unreadable because element outlines are to thick
https://bugs.kde.org/show_bug.cgi?id=383758 Stephane MANKOWSKI changed: What|Removed |Added Latest Commit|https://commits.kde.org/skr |https://commits.kde.org/skr |ooge/d24e70abac40b323dbb857 |ooge/a61bcbd8da6ef71074c45e |7e8bccbe0e6a7a7f28 |b17a64f0eff247edf2 --- Comment #5 from Stephane MANKOWSKI --- Git commit a61bcbd8da6ef71074c45eb17a64f0eff247edf2 by Stephane Mankowski. Committed on 22/08/2017 at 16:38. Pushed by smankowski into branch 'master'. Report unreadable because element outlines are to thick M +12 -9skgbasegui/skgtablewithgraph.cpp https://commits.kde.org/skrooge/a61bcbd8da6ef71074c45eb17a64f0eff247edf2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 383859] New: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault - QUrl::path(QFlags) const ()
https://bugs.kde.org/show_bug.cgi?id=383859 Bug ID: 383859 Summary: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault - QUrl::path(QFlags) const () Product: Akonadi Version: 5.3.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Archive Mail Agent Assignee: kdepim-b...@kde.org Reporter: bugrprt21...@online.de Target Milestone: --- Application: akonadi_archivemail_agent (5.3.2) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.79-18.26-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Waiting for the archive of a mail folder with 646 MB of e-Mails to complete. The crash can be reproduced sometimes. -- Backtrace: Application: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff7fce3c940 (LWP 28420))] Thread 10 (Thread 0x7ff7a3f3d700 (LWP 28445)): #0 0x7ff7f1a3b7e0 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff7f19f9d4b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff7f19fa2a8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff7f19fa42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff7f8bc833b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff7f8b75feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff7f89b0f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7ff7f89b59e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff7f2686744 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff7f809faad in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7ff7c1b68700 (LWP 28432)): #0 0x7ff7f809328d in read () at /lib64/libc.so.6 #1 0x7ff7f1a3a670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff7f19f9e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff7f19fa2a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff7f19fa42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff7f8bc833b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff7f8b75feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7ff7f89b0f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7ff7f89b59e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7ff7f2686744 in start_thread () at /lib64/libpthread.so.0 #10 0x7ff7f809faad in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7ff7c2369700 (LWP 28430)): #0 0x7ff7f1a3b7b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff7f19f9390 in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff7f19fa1d5 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff7f19fa42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff7f8bc833b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff7f8b75feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff7f89b0f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7ff7f89b59e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff7f2686744 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff7f809faad in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7ff7c2b6a700 (LWP 28428)): #0 0x7ff7f1a3b7b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff7f19f9390 in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff7f19fa1d5 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff7f19fa42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff7f8bc833b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff7f8b75feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff7f89b0f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7ff7f89b59e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff7f2686744 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff7f809faad in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7ff7c336b700 (LWP 28425)): #0 0x7ff7f1a3b7b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff7f19f9837 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff7f19fa230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff7f19fa42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff7f8bc833b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff7f8b75feb in QEventLoop::exec(QFlags) () at /u
[plasmashell] [Bug 381006] Crash after switching activities (QSortFilterProxyModelPrivate::updateChildrenMapping)
https://bugs.kde.org/show_bug.cgi?id=381006 David Edmundson changed: What|Removed |Added Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-workspace/3990ec2358106 |sma-workspace/d2f722a82ebeb |875bd1d58ad65bd2a55ff4f1d73 |213a89efc209ec726a8188de6f0 --- Comment #18 from David Edmundson --- Git commit d2f722a82ebeb213a89efc209ec726a8188de6f0 by David Edmundson, on behalf of Eike Hein. Committed on 22/08/2017 at 16:36. Pushed by davidedmundson into branch 'Plasma/5.8'. Fix QSortFilterProxyModelPrivate::updateChildrenMapping crash in libtaskmanager Summary: TaskGroupingProxyModel uses a simple QVector> populated with source model row indices to represent the task group tree. To implement QAbstractItemModel::parent(), its implementation of index() encodes row indices of the top-level vector into the internal ids of child item model indices. This allows parent() to produce the parent model index by simply decoding the parent row from the passed-in child index and call index() with that row. Top-level row indices shift up and down as the list of top-level items changes, invalidating those internal ids. QModelIndex is not meant to be stored, and the proxy model does take care of updating any persis- tent model indexes with new ids, so this should be fine. However, where it falls apart is that as internal ids are invalidated, a QSortFilterProxyModel on top of this proxy (i.e. TasksModel) may end up with multiple indexes with identical internal ids in its mappings, causing it to mess up its mappings as it uses them (e.g. taking things from them). This causes the often-reported crash/assert there. The fix is to refactor index()/parent() not to rely on row indices as internal ids, but instead use pointers to internal data structures instead. This patch achieves this by changing the map to QVector *>. This screams fugly, but the alternative would basically just be to create some wrapper struct to hide the fugly appeareance a little, which I don't think is worth it. On the flip side, it saves a QVector::replace() call as a multable vector iterator can work directly on a vector without making a copy, and it's now no longer necessary to manually update the persistent model indices beyond what endRemoveRows() does implicitly. Reviewers: #plasma, davidedmundson Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D7139 M +54 -73 libtaskmanager/taskgroupingproxymodel.cpp https://commits.kde.org/plasma-workspace/d2f722a82ebeb213a89efc209ec726a8188de6f0 -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 316195] Auto-hidden panel is unable to unhide at some point
https://bugs.kde.org/show_bug.cgi?id=316195 Heinrich Schuchardt changed: What|Removed |Added CC||xypron.g...@gmx.de --- Comment #2 from Heinrich Schuchardt --- I have identified one situation that reproducably leads to the behavior: When thunderbird is opened it displays a dialogue to ask for the email account password. While this popup is shown in thunderbird the panel does not autohide when changing to another application. Best regards Heinrich Schuchardt -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 378560] Reports show digits and not the fields when sub-tables are used
https://bugs.kde.org/show_bug.cgi?id=378560 --- Comment #12 from Jarosław Staniek --- Thanks but I mean not data but design window. Right side of your window. https://bugsfiles.kde.org/attachment.cgi?id=106123 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 382902] KDE showing afterimages on text lines after applying 1.3x scale
https://bugs.kde.org/show_bug.cgi?id=382902 Christoph Feck changed: What|Removed |Added Assignee|elvis.angelac...@kde.org|kwrite-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 378560] Reports show digits and not the fields when sub-tables are used
https://bugs.kde.org/show_bug.cgi?id=378560 --- Comment #11 from Albrecht Will --- Created attachment 107445 --> https://bugs.kde.org/attachment.cgi?id=107445&action=edit Bild1 -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 378560] Reports show digits and not the fields when sub-tables are used
https://bugs.kde.org/show_bug.cgi?id=378560 --- Comment #10 from Albrecht Will --- Am Dienstag, 22. August 2017, 12:21:08 CEST schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=378560 > > --- Comment #9 from Jarosław Staniek --- > @Albrecht could you please show screenshot of your table designer's property > pane? > > You can't find the lookup column tab or? Here is the basic table and a subtable -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383858] New: Crash when showing/hiding layer.
https://bugs.kde.org/show_bug.cgi?id=383858 Bug ID: 383858 Summary: Crash when showing/hiding layer. Product: krita Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- Application: krita (4.0.0-pre-alpha (git 96835a0)) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.10.0-32-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: I was animating. Then, I wondered whether another layer looked better. So I tried to show it... Crash. -- 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 0x7ff532fec8c0 (LWP 1575))] Thread 6 (Thread 0x7ff48ce15700 (LWP 12316)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7ff5431d5826 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ff5431d0e9a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff5431d4989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff53d0126ba in start_thread (arg=0x7ff48ce15700) at pthread_create.c:333 #5 0x7ff5428cb3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7ff4fcc7b700 (LWP 1594)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ff5431d58eb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ff543f31d8a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #3 0x7ff5431d4989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff53d0126ba in start_thread (arg=0x7ff4fcc7b700) at pthread_create.c:333 #5 0x7ff5428cb3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7ff4fc47a700 (LWP 1592)): #0 0x7ff54289030d in nanosleep () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ff5433fd2ad in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ff5431d3d18 in QThread::msleep(unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff54084742a in KisTileDataSwapper::run (this=0x7ff540d17b00 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>) at /home/wolthera/krita/src/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:97 #4 0x7ff5431d4989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff53d0126ba in start_thread (arg=0x7ff4fc47a700) at pthread_create.c:333 #6 0x7ff5428cb3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7ff525363700 (LWP 1577)): #0 0x7ff53ba177c0 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff53ba182bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff53ba1849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff5433fd94b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff5433a67ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff5431cfcd4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff53d23db75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7ff5431d4989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff53d0126ba in start_thread (arg=0x7ff525363700) at pthread_create.c:333 #9 0x7ff5428cb3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7ff530b72700 (LWP 1576)): #0 0x7ff5428bf70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ff540f74c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff540f768d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ff532eba329 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7ff5431d4989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff53d0126ba in start_thread (arg=0x7ff530b72700) at pthread_create.c:333 #6 0x7ff5428cb3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7ff532fec8c0 (LWP 1575)): [KCrash Handler] #6 KisSharedPtr::operator-> (this=0x50) at /home/wolthera/krita/src/libs/global/kis_shared_ptr.h:181 #7 KisPaintDevice::Private::currentStrategy (this=0x30) at /home/wolthera/krita/src/libs/image/kis_paint_device.cc:555 #8 0x7ff540970e9d in KisPaintDevice::extent (this=) at /home/wolthera/krita/src/libs/image/kis_paint_device.cc:1127 #9 0x7ff54097351b
[amarok] [Bug 374670] AAC transcoding is broken due to deprecated libfaac
https://bugs.kde.org/show_bug.cgi?id=374670 --- Comment #22 from rdragonr...@gmail.com --- Thank you. I have already installed google-mock and libgtest-dev, at very least. Would you know what package might provide the missing service? It also lists them as present but in need of building? -- Found gmock and gtest but need to build both: /usr/include/gmock;/usr/src/gmock;GOOGLEMOCK_DEP_GTEST_SOURCES-NOTFOUND/gtest/include, GOOGLEMOCK_DEP_GTEST_SOURCES-NOTFOUND Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383805] [regression] Title bar is using main font when FreeSans is used
https://bugs.kde.org/show_bug.cgi?id=383805 --- Comment #4 from Hugo Pereira Da Costa --- (I have breeze from master, but older kdecoration, kwin) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383805] [regression] Title bar is using main font when FreeSans is used
https://bugs.kde.org/show_bug.cgi?id=383805 --- Comment #3 from Hugo Pereira Da Costa --- Also, I cannot reproduce the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383805] [regression] Title bar is using main font when FreeSans is used
https://bugs.kde.org/show_bug.cgi?id=383805 Hugo Pereira Da Costa changed: What|Removed |Added Assignee|hugo.pereira.da.costa@gmail |kwin-bugs-n...@kde.org |.com| Component|window decoration |decorations Product|Breeze |kwin -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383805] [regression] Title bar is using main font when FreeSans is used
https://bugs.kde.org/show_bug.cgi?id=383805 --- Comment #2 from Hugo Pereira Da Costa --- @Martin, but aren't decoration font set in kdecoration2 ? I do nothing about fonts in breeze ... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383805] [regression] Title bar is using main font when FreeSans is used
https://bugs.kde.org/show_bug.cgi?id=383805 Hugo Pereira Da Costa changed: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com, ||kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 370339] When resizing windows the cursor switches to one icon only
https://bugs.kde.org/show_bug.cgi?id=370339 Martin Flöser changed: What|Removed |Added CC||notux...@gmail.com --- Comment #3 from Martin Flöser --- *** Bug 383838 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383838] [Wayland] Incorrect cursor direction upon window change size
https://bugs.kde.org/show_bug.cgi?id=383838 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 370339 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383839] [Wayland] 'Delay' and 'Rate' settings from 'Keyboard Hardware and Layout' are not applying
https://bugs.kde.org/show_bug.cgi?id=383839 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Martin Flöser --- Please see https://bugreports.qt.io/browse/QTBUG-55615 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383845] [Wayland KWin] Position of Dolphin window isn't remembered after reopening
https://bugs.kde.org/show_bug.cgi?id=383845 Martin Flöser changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- There is no support for remembering the position of a window. I'm sorry this is out of scope both on X11 and Wayland. Windows in KWin are placed based on the placement policy, but not on the last position. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383844] [Wayland KWin] Windows aren't remembering previous maximized state after reopening
https://bugs.kde.org/show_bug.cgi?id=383844 Martin Flöser changed: What|Removed |Added Resolution|--- |LATER Status|UNCONFIRMED |RESOLVED --- Comment #2 from Martin Flöser --- This is currently impossible to handle as wl_shell which is used for Qt windows is lacking functionality. We will soon get support for xdg_shell in qt windows where this might work better. For the moment there is nothing we can do -> resolved later. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383833] [proposal] expose kwinrc BorderlessMaximizedWindows parameter to GUI
https://bugs.kde.org/show_bug.cgi?id=383833 Martin Flöser changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Martin Flöser --- Patches welcome. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377901] Window movement breaks after 49 days
https://bugs.kde.org/show_bug.cgi?id=377901 --- Comment #19 from Martin Flöser --- The copy but is a different issue and sounds a lot like a bug in Qt. Please report there. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383805] [regression] Title bar is using main font when FreeSans is used
https://bugs.kde.org/show_bug.cgi?id=383805 Martin Flöser changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |hugo.pereira.da.costa@gmail ||.com Product|kwin|Breeze Component|decorations |window decoration -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383827] Arrow keys do not work in Qemu and Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=383827 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Martin Flöser --- Please ensure that you have all required runtime dependencies such as libinput installed and working. I'm sorry, but this is not a task for us to handle. This is integration work which the distribution has to take care of. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383837] Krita crashing when I switch colours
https://bugs.kde.org/show_bug.cgi?id=383837 --- Comment #3 from myccisem...@gmail.com --- Is this good info? Based on the website you sent me I am supposed to give you the crash report but what do I do with this info? On Aug 22, 2017 6:32 PM, "Boudewijn Rempt" wrote: > https://bugs.kde.org/show_bug.cgi?id=383837 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||b...@valdyas.org > > --- Comment #1 from Boudewijn Rempt --- > How could I tell without more information? Please make a crash log: > > https://docs.krita.org/Dr._Mingw_debugger > > And attach it to the bug report. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383837] Krita crashing when I switch colours
https://bugs.kde.org/show_bug.cgi?id=383837 --- Comment #4 from myccisem...@gmail.com --- Created attachment 107443 --> https://bugs.kde.org/attachment.cgi?id=107443&action=edit _20170822_223518.JPG -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 383824] [proposal] make colord-kde xiccd dependent instead of gnome-color-manager
https://bugs.kde.org/show_bug.cgi?id=383824 --- Comment #2 from Alex --- But without gnome-color-manager or xiccd it will not enumerate displays. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 383843] Spawning insane amounts of DBus messages while copying files
https://bugs.kde.org/show_bug.cgi?id=383843 Kevin Funk changed: What|Removed |Added Version Fixed In||5.38 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kio ||/801f58e7e76acd4bcb23d6e809 ||2825cdda203a81 --- Comment #3 from Kevin Funk --- Git commit 801f58e7e76acd4bcb23d6e8092825cdda203a81 by Kevin Funk. Committed on 22/08/2017 at 14:43. Pushed by kfunk into branch 'master'. Really rate-limit INF_PROCESSED_SIZE messages Summary: Fixing an ancient porting bug which popped up when porting from Qt4 to Qt5. FIXED-IN: 5.38 Reviewers: dfaure Reviewed By: dfaure Subscribers: dfaure, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D7463 M +1-1src/core/slavebase.cpp https://commits.kde.org/kio/801f58e7e76acd4bcb23d6e8092825cdda203a81 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 337079] sddm theme doesn't focus password field
https://bugs.kde.org/show_bug.cgi?id=337079 csbugs changed: What|Removed |Added CC||b...@clearingstelle-eeg.de -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 383824] [proposal] make colord-kde xiccd dependent instead of gnome-color-manager
https://bugs.kde.org/show_bug.cgi?id=383824 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com --- Comment #1 from Rex Dieter --- colord-kde should only depend on colord, in my experience -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383837] Krita crashing when I switch colours
https://bugs.kde.org/show_bug.cgi?id=383837 --- Comment #2 from myccisem...@gmail.com --- What information should I provide you? And does the debugging package work with krita 3.2? On Aug 22, 2017 6:32 PM, "Boudewijn Rempt" wrote: > https://bugs.kde.org/show_bug.cgi?id=383837 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||b...@valdyas.org > > --- Comment #1 from Boudewijn Rempt --- > How could I tell without more information? Please make a crash log: > > https://docs.krita.org/Dr._Mingw_debugger > > And attach it to the bug report. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 383857] New: [support] Creating groups of certificates
https://bugs.kde.org/show_bug.cgi?id=383857 Bug ID: 383857 Summary: [support] Creating groups of certificates Product: kleopatra Version: 2.2.0 Platform: Windows CE OS: Windows CE Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: elena.mayan...@gs-labs.ru CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- Usually we use the same set of certificates for typical tasks: task 1 - group 1, task 2 - group 2 etc Could you, please, specify if it is possible to create groups and to use them while encryption not to waste time adding certificates one-by-one each time? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 383848] KSyntaxHighlighting 5.37 detects normal text files as poweshell script
https://bugs.kde.org/show_bug.cgi?id=383848 Till Schäfer changed: What|Removed |Added URL||https://phabricator.kde.org ||/D7464 --- Comment #4 from Till Schäfer --- created a path: https://phabricator.kde.org/D7464 -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 383856] New: Hang on opening odt file [infinite? loop in RunAroundHelper::fit] [testcase]
https://bugs.kde.org/show_bug.cgi?id=383856 Bug ID: 383856 Summary: Hang on opening odt file [infinite? loop in RunAroundHelper::fit] [testcase] Product: calligrawords Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: opendocument Assignee: calligra-words-bugs-n...@kde.org Reporter: rasas...@gmail.com Target Milestone: --- Created attachment 107440 --> https://bugs.kde.org/attachment.cgi?id=107440&action=edit Test document that always reproduce the bug. I'm using the debian experimental 3.0.1 package rebuilt for stretch. When opening the attached file I get it looks like an infinite loop at RunAroundHelper::fit. #0 RunAroundHelper::fit (this=this@entry=0x7ffd79884a80, resetHorizontalPosition=resetHorizontalPosition@entry=false, isRightToLeft=, position=...) at ./libs/textlayout/RunAroundHelper.cpp:106 #1 0x7f64111318fc in KoTextLayoutArea::layoutBlock (this=this@entry=0x559f6942f300, cursor=cursor@entry=0x559f6941c4b0) at ./libs/textlayout/KoTextLayoutArea.cpp:1350 #2 0x7f6411134b53 in KoTextLayoutArea::layout (this=this@entry=0x559f6942f300, cursor=cursor@entry=0x559f6941c4b0) at ./libs/textlayout/KoTextLayoutArea.cpp:689 #3 0x7f641114bdbd in KoTextLayoutRootArea::layoutRoot (this=this@entry=0x559f6942f300, cursor=cursor@entry=0x559f6941c4b0) at ./libs/textlayout/KoTextLayoutRootArea.cpp:69 #4 0x7f641114ed8d in KoTextDocumentLayout::doLayout (this=this@entry=0x559f69404ad0) at ./libs/textlayout/KoTextDocumentLayout.cpp:819 #5 0x7f641114f618 in KoTextDocumentLayout::layout (this=0x559f69404ad0) at ./libs/textlayout/KoTextDocumentLayout.cpp:703 #6 0x7f6411cd3499 in QObject::event (this=0x559f69404ad0, e=) at kernel/qobject.cpp:1263 #7 0x7f6412050b8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f6412058341 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f6412a8d3a7 in KoApplication::notify (this=, receiver=0x559f69404ad0, event=0x559f68ea3da0) at ./libs/main/KoApplication.cpp:657 #10 0x7f6411ca69e0 in QCoreApplication::notifyInternal2 (receiver=0x559f69404ad0, event=event@entry=0x559f68ea3da0) at kernel/qcoreapplication.cpp:988 #11 0x7f6411ca916d in QCoreApplication::sendEvent (event=0x559f68ea3da0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #12 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x559f68e2da00) at kernel/qcoreapplication.cpp:1649 #13 0x7f6411ca95d8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #14 0x7f6411cfac43 in postEventSourceDispatch (s=0x559f68e80030) at kernel/qeventdispatcher_glib.cpp:276 #15 0x7f640b3b97f7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f640b3b9a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f640b3b9b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f6411cfb04f in QEventDispatcherGlib::processEvents (this=0x559f68e958c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #19 0x7f640fe34cdb in KoProgressUpdater::update (this=) at ./libs/widgetutils/KoProgressUpdater.cpp:166 #20 0x7f6411cd25e9 in QMetaObject::activate (sender=0x559f6932b2a0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3740 #21 0x7f6411cd25e9 in QMetaObject::activate (sender=sender@entry=0x559f693297e0, signalOffset=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd798854b0) at kernel/qobject.cpp:3740 #22 0x7f6411cd2f07 in QMetaObject::activate (sender=sender@entry=0x559f693297e0, m=m@entry=0x7f6410042be0 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffd798854b0) at kernel/qobject.cpp:3602 #23 0x7f640fe3edc1 in KoUpdater::sigProgress (this=this@entry=0x559f693297e0, _t1=, _t1@entry=100) at ./obj-x86_64-linux-gnu/libs/widgetutils/kowidgetutils_automoc.dir/moc_KoUpdater_S7VTS5GQ4NKEZV.cpp:158 #24 0x7f640fe36274 in KoUpdater::setProgress (this=0x559f693297e0, percent=percent@entry=100) at ./libs/widgetutils/KoUpdater.cpp:56 #25 0x7f6412a96d7c in KoDocument::openFile (this=0x559f68e8b100) at ./libs/main/KoDocument.cpp:1610 #26 0x7f6412a9e632 in KoDocument::Private::openFile (this=0x559f68f1a580) at ./libs/main/KoDocument.cpp:271 #27 KoDocument::Private::openLocalFile (this=0x559f68f1a580) at ./libs/main/KoDocument.cpp:293 #28 0x7f6412a9cd0d in KoDocument::openUrlInternal (this=this@entry=0x559f68e8b100, url=file:///home/raul/debs/calligra/testdocs/t5/t5d.odt) at ./libs/main/KoDocument.cpp:2675 #29 0x7f
[digikam] [Bug 383855] Digikam crash when stacking 5 images
https://bugs.kde.org/show_bug.cgi?id=383855 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Export-ExpoBlending Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- It crash in Exiv2 shared library. update to last stable Exiv2 0.26 and problem must be fixed. Report this problem to opensuse team to update the dependency. You can use the digiKam Linux AppImage bundle which use the right Exiv2 version internally : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Spurious XCB Events causing high CPU
https://bugs.kde.org/show_bug.cgi?id=373368 Kevin Funk changed: What|Removed |Added CC||kf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383855] New: Digikam crash when stacking 5 images
https://bugs.kde.org/show_bug.cgi?id=383855 Bug ID: 383855 Summary: Digikam crash when stacking 5 images Product: digikam Version: 5.2.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: jcarricksm...@gmail.com Target Milestone: --- Application: digikam (5.2.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.79-18.26-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: I had processed one stack of 5 images to blend exposure. When I tried a second set of 5 images Digikam crashed. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4ad6c629c0 (LWP 2564))] Thread 13 (Thread 0x7f4a3b1c7700 (LWP 3255)): [KCrash Handler] #6 0x0025 in () #7 0x7f4acdc5c8bb in Exiv2::Exifdatum::operator=(Exiv2::Exifdatum const&) () at /usr/lib64/libexiv2.so.14 #8 0x7f4ad54f795d in std::list >::operator=(std::list > const&) () at /usr/lib64/libdigikamcore.so.5.2.0 #9 0x7f4ad54f67fc in Digikam::MetaEngine::load(QString const&) const () at /usr/lib64/libdigikamcore.so.5.2.0 #10 0x7f4ad5844b45 in () at /usr/lib64/libdigikamcore.so.5.2.0 #11 0x7f4ad5849691 in () at /usr/lib64/libdigikamcore.so.5.2.0 #12 0x7f4ad53a1b4b in () at /usr/lib64/libdigikamcore.so.5.2.0 #13 0x7f4ad293c81e in () at /usr/lib64/libQt5Core.so.5 #14 0x7f4ad293f9e9 in () at /usr/lib64/libQt5Core.so.5 #15 0x7f4ace739744 in start_thread () at /lib64/libpthread.so.0 #16 0x7f4ad2036aad in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f4a3a9c6700 (LWP 3238)): #0 0x7f4ace73e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ad294065b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f4ad2934fe4 in QFutureInterfaceBase::waitForFinished() () at /usr/lib64/libQt5Core.so.5 #3 0x7f4ad58454d8 in () at /usr/lib64/libdigikamcore.so.5.2.0 #4 0x7f4ad584860b in () at /usr/lib64/libdigikamcore.so.5.2.0 #5 0x7f4ad293f9e9 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f4ace739744 in start_thread () at /lib64/libpthread.so.0 #7 0x7f4ad2036aad in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f49db7fe700 (LWP 3187)): #0 0x7f4ad202e20d in poll () at /lib64/libc.so.6 #1 0x7f4ac9386314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4ac938642c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4ad2b5233b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4ad2afffeb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4ad55afeda in () at /usr/lib64/libdigikamcore.so.5.2.0 #6 0x7f4ad293c81e in () at /usr/lib64/libQt5Core.so.5 #7 0x7f4ad293f9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f4ace739744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f4ad2036aad in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f4a4d625700 (LWP 2581)): #0 0x7f4ace73e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ac72a06e3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f4ac75c2341 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f4ace739744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4ad2036aad in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f4a4de26700 (LWP 2580)): #0 0x7f4ace73e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ac72a06e3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f4ac75c2341 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f4ace739744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4ad2036aad in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f4a4e627700 (LWP 2579)): #0 0x7f4ace73e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ac72a06e3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f4ac75c2341 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f4ace739744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4ad2036aad in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f4a4ee28700 (LWP 2578)): #0 0x7f4ace73e0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ac729f70d in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f4ac75c2341 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f4ace739744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4ad2036aad in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f4a4fdf3700 (LWP 2577)): #0 0x7f4ac93c77b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f4ac9385390 in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #2 0x000
[k3b] [Bug 383819] Text ilegible in darker themes/colour scheme
https://bugs.kde.org/show_bug.cgi?id=383819 --- Comment #3 from Gustavo Alvarez --- Created attachment 107439 --> https://bugs.kde.org/attachment.cgi?id=107439&action=edit screenshot with quant theme -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 383819] Text ilegible in darker themes/colour scheme
https://bugs.kde.org/show_bug.cgi?id=383819 --- Comment #2 from Gustavo Alvarez --- > Change the internal k3b theme do nothing (tested all) but if you insist.. xd -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 383795] Allow enabling/disabling modules via DBus
https://bugs.kde.org/show_bug.cgi?id=383795 Albert Vaca changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Albert Vaca --- Fixed in https://commits.kde.org/kdeconnect-kde/239f7f68304b9537ec7609a2157bffc47b285e6e -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376577] filenamesearch crashes when started from root folder
https://bugs.kde.org/show_bug.cgi?id=376577 Alex changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Alex --- It seems to work under Neon Dev stable 5.10.4. Searching / for svg doesn't crash anymore. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383854] [Wayland Yakuake] Incorrect calculating of window size at 100% width
https://bugs.kde.org/show_bug.cgi?id=383854 --- Comment #1 from Alexander Mentyu --- Possibly related/duplicate of https://bugs.kde.org/show_bug.cgi?id=378872 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383792] New tool to export Nikon Image Space (https://www.nikonimagespace.com)
https://bugs.kde.org/show_bug.cgi?id=383792 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #4 from caulier.gil...@gmail.com --- As expected, coming from Nikon. So, we close this file as WONTFIX. Thanks Nikon to play the game in the real world... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 383848] KSyntaxHighlighting 5.37 detects normal text files as poweshell script
https://bugs.kde.org/show_bug.cgi?id=383848 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 383821] Allow applications to disconnect device via DBus
https://bugs.kde.org/show_bug.cgi?id=383821 --- Comment #2 from rugk <7429c...@opayq.com> --- At least when using the button on Android, it does not happen. And at least the GNOME extension runs the device discovery only for a limited time and only if you click on a button. So when implemented a disconnect would mean "disconnect until I click the button to reconnect again". Reasons for disconnecting a device are diverse, e.g. saving power or so. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383854] New: [Wayland Yakuake] Incorrect calculating of window size at 100% width
https://bugs.kde.org/show_bug.cgi?id=383854 Bug ID: 383854 Summary: [Wayland Yakuake] Incorrect calculating of window size at 100% width Product: yakuake Version: Git (Frameworks 5) Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Created attachment 107438 --> https://bugs.kde.org/attachment.cgi?id=107438&action=edit incorrect-width-yakuake-100 Prerequisite: Place main Panel on the left or right side. Steps to reproduce: 1. Start Yakuake and. 2. Set Yakuake width to 100%. Actual result: Part of Yakuake window is overlapped by the Panel or isn't visible. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383851] Digikam installed from Ubuntu Software; does not start
https://bugs.kde.org/show_bug.cgi?id=383851 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED Component|Setup-Misc |Portability -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 383848] KSyntaxHighlighting 5.37 detects normal text files as poweshell script
https://bugs.kde.org/show_bug.cgi?id=383848 --- Comment #3 from Till Schäfer --- /s/I guess this is implemented as an AND and the author of the PowerShell file interpreted it as an OR./I guess this is implemented as an OR and the author of the PowerShell file interpreted it as an AND./ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383851] Digikam installed from Ubuntu Software; does not start
https://bugs.kde.org/show_bug.cgi?id=383851 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- It crash in KDE4 image plugin to handle XCF file with QImage. This problem have been fixed in more recent KDE4 release. I recommend to use Qt5 based digiKam, especially the AppImage version that we provide : https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM In all case this crash is not relevant of digiKam code. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 383848] KSyntaxHighlighting 5.37 detects normal text files as poweshell script
https://bugs.kde.org/show_bug.cgi?id=383848 --- Comment #2 from Till Schäfer --- some more observations: settings -> Open/Save -> Modes & Filetypes - I can see correctly specified file extensions "*.ps1;*.ps1m;*.ps1d". - I have noticed that the other entries contain extra mime-types for the specific type (e.g. "application/x-python;text/x-python" for python) type or no mime type (i.e., the empty string). PowerShell does contain the mimetype "text/plain" instead. -> replacing the mime type "text/plain" with the empty string "" fixes the problem. The mimetype and extension is somewhat ambiguous (as the mime type can declare their own filename pattern (and thus extension)). https://docs.kde.org/stable5/en/applications/katepart/highlight.html does not clearly state how this two properties behave in combination. I guess this is implemented as an AND and the author of the PowerShell file interpreted it as an OR. => Thus, the relation of this attributes should be clearly specified in https://docs.kde.org/stable5/en/applications/katepart/highlight.html and the mime-type should be set to empty in PowerShell.xml -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 383815] Running "konqueror" should open a new window
https://bugs.kde.org/show_bug.cgi?id=383815 Christoph Feck changed: What|Removed |Added Severity|wishlist|normal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383832] [proposal] option for opening kicker/kickoff via mouse over
https://bugs.kde.org/show_bug.cgi?id=383832 --- Comment #5 from Alex --- @Kai: it indeed works nice, haven't noticed that. But you have to move mouse further away deliberately. That solves problem with "keyless" quick menu activation. @David: It will also eliminate clicking on tooltip which I caught myself couple of times. I move cursor on top of button, get tooltip. Tooltip shows, so I move cursor over tooltip and click instead of clicking menu button. Try yourself. If this solution would need delay and not speed up work it would nicely eliminate such accidental clicks. But when task switcher is set not to show windows previews and highlight windows it works instantly - it's so great. As I remember this solution (without delay) is available in Cinnamon desktop, so it's possible to test. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 355443] Can't select / as directory in "open directory dialog"
https://bugs.kde.org/show_bug.cgi?id=355443 Fabian Vogt changed: What|Removed |Added Assignee|kdelibs-b...@kde.org|fa...@kde.org Version|unspecified |5.37.0 CC||kdelibs-b...@kde.org Component|general |general Product|frameworks-frameworkintegra |frameworks-kio |tion| --- Comment #1 from Fabian Vogt --- The reason seems to be that KDirModel starts the tree at the first layer and not at the root. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 319398] IMAP resource fetches messages from older to newer, demanding a lot of time to usable Kmail
https://bugs.kde.org/show_bug.cgi?id=319398 Erik Quaeghebeur changed: What|Removed |Added CC||kdebugs@equaeghe.nospammail ||.net --- Comment #4 from Erik Quaeghebeur --- (In reply to Christian Mollekopf from comment #3) > This would require downloading the messages in batches, starting with the > highest UID first. >From the IMAP-perspective, only (part of) the headers and MIME structure of the mails need to be fetched first; the MIME payloads can be fetched later, even as-needed (this is how pure IMAP clients such as Trojita do it). For that the akonadi database needs to be able to store such partial fetches. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382944] krita-3.1.4-x86_64.appimage fails to run with 'could not find or load the Qt platform plugin "xcb"'
https://bugs.kde.org/show_bug.cgi?id=382944 Camille Scholtz changed: What|Removed |Added CC||cami...@airmail.cc --- Comment #1 from Camille Scholtz --- I'm running into the same issue, and I can confirm that libpng.so is the offending library. By downgrading my system libpng from 1.16.31 to 1.16.27 I am able to launch the Krita AppImage. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383792] New tool to export Nikon Image Space (https://www.nikonimagespace.com)
https://bugs.kde.org/show_bug.cgi?id=383792 --- Comment #3 from Syiad --- OK, I got a response from Nikon: "Leider sind die von Ihnen angeforderten Informationen nicht öffentlich zugänglich. Es handelt sich dabei um vertrauliche Firmeninformationen, die nicht an Personen außerhalb von Nikon weitergegeben werden dürfen. Ich bedaure, dass ich Ihnen die gewünschten Informationen nicht zur Verfügung stellen kann." I guess it's OK for you if I don't translate it. The information is confidential and they can't make it available outside Nikon. So no easy access for exporting from open-source software, which would mean reverse-engineering would be required. Seems like too much effort with possibly little demand for it. :-( -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 383853] New: IMAP flag changes should not create a new message
https://bugs.kde.org/show_bug.cgi?id=383853 Bug ID: 383853 Summary: IMAP flag changes should not create a new message Product: Akonadi Version: 5.5.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: kdeb...@equaeghe.nospammail.net CC: kdepim-b...@kde.org Target Milestone: --- In the akonadi console, one can set and remove IMAP flags. This works, but it seems that the following happens: 1. the flag changes are made 2. the message is copied 3. the message is deleted (keeping the copy) Steps 2 and 3 are, of course, superfluous. In akonadiconsole, one can see that indeed the UID (remote ID) is stepped up. (One does not see the marked-as-deleted-but-non-expunged message in akonadiconsole, which is not good, but that's another issue. Also, the remote ID field is an editable field, whereas it should not be.) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 383852] [Wayland] Suspending to RAM sometimes takes to much time
https://bugs.kde.org/show_bug.cgi?id=383852 --- Comment #1 from Alexander Mentyu --- Though, i noticed similar behavior also in X session. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383778] Search doesn't take account hidden folders
https://bugs.kde.org/show_bug.cgi?id=383778 --- Comment #5 from Alex --- About intentional feature removal: Hidden folders are present inside home folder. When I tried to find activation file for draftsight (to fix activation) I had to: - open terminal (here) - google for search command ... 5 minutes later: - type in command - look for file (nothing found) - type again - ok I got it, now let's remember where it is or copy-paste path - type in delete command ... GUI alternative: - ctrl+f, enable search inside hidden option (that's what's lacking) - type in name - wait - type in again - ok I got it, right click -> delete Problem is that you can see files inside dot folders using alt+. shortcut or via menu option. So you can go inside and search one by one and find what you want. Even more, if you go inside one of dot folders you can search within. So you are pretty able to do something bad and accidentally delete or rename files. So if you can do all this things then why you can't search especially, that when you search you more or less know what you want. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 383852] New: [Wayland] Suspending to RAM sometimes takes to much time
https://bugs.kde.org/show_bug.cgi?id=383852 Bug ID: 383852 Summary: [Wayland] Suspending to RAM sometimes takes to much time Product: Powerdevil Version: 5.10.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Usual suspending takes 1-2 seconds - but sometimes suspending takes 5-7 seconds. Looks like it happens more often when 'Lock screen on resume' option is disabled in 'Screen Locking' settings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383838] [Wayland] Incorrect cursor direction upon window change size
https://bugs.kde.org/show_bug.cgi?id=383838 David Edmundson changed: What|Removed |Added Version|master |git master Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Product|plasmashell |kwin Component|generic-wayland |general CC||k...@davidedmundson.co.uk Target Milestone|1.0 |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383838] [Wayland] Incorrect cursor direction upon window change size
https://bugs.kde.org/show_bug.cgi?id=383838 David Edmundson changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383839] [Wayland] 'Delay' and 'Rate' settings from 'Keyboard Hardware and Layout' are not applying
https://bugs.kde.org/show_bug.cgi?id=383839 David Edmundson changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 348382] Action item flag is lost in IMAP folders
https://bugs.kde.org/show_bug.cgi?id=348382 Erik Quaeghebeur changed: What|Removed |Added CC||kdebugs@equaeghe.nospammail ||.net --- Comment #2 from Erik Quaeghebeur --- (In reply to quazgar from comment #0) > If relevant: The server is an MS Exchange mail server. Exchange does not support arbitrary IMAP flags, so this does not seem surprising. Check from another IMAP client (Trojita, Thunderbird,…) whether the Action flag ($TODO) is actually propagated at all (I doubt it). It may be the case that upon every refresh the IMAP resource gets info from the server about the current flags set (none, because it's exchange) and assumes it was removed remotely and so removes it locally as well. In principle, the IMAP resource should be aware of the server's CAPABILITIES and adapt to them as needed. This may mean not offering the ability to set the $TODO flag or storing them in the Akonadi database only. However, with Exchange, the best thing is to try out the akonadi-ews resource under development: https://github.com/KrissN/akonadi-ews (it may also be in your distribution's packages). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383839] [Wayland] 'Delay' and 'Rate' settings from 'Keyboard Hardware and Layout' are not applying
https://bugs.kde.org/show_bug.cgi?id=383839 David Edmundson changed: What|Removed |Added Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Version|master |git master CC||k...@davidedmundson.co.uk Component|generic-wayland |input Target Milestone|1.0 |--- Product|plasmashell |kwin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 383778] Search doesn't take account hidden folders
https://bugs.kde.org/show_bug.cgi?id=383778 --- Comment #4 from Alex --- Unfortunately adding hidden folders option into baloo doesn't seem to work, it doesn't index more files. Besides, why should baloo index files in hidden folders (useless for everyday use) and eat memory and cpu? when I search / for .svg I will find files inside /usr and they are not indexed... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383851] New: Digikam installed from Ubuntu Software; does not start
https://bugs.kde.org/show_bug.cgi?id=383851 Bug ID: 383851 Summary: Digikam installed from Ubuntu Software; does not start Product: digikam Version: 4.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Setup-Misc Assignee: digikam-bugs-n...@kde.org Reporter: chuck_pe...@yahoo.com Target Milestone: --- Created attachment 107437 --> https://bugs.kde.org/attachment.cgi?id=107437&action=edit backtrace from crash; was said to be uninformative I installed Digikam from the Ubuntu Software Center. I am running the Ubuntu Studio version of Ubuntu 16.4 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 383831] Missing buttons for adding/removing entries in currency edit dialog
https://bugs.kde.org/show_bug.cgi?id=383831 NSLW changed: What|Removed |Added CC||lukasz.wojnilow...@gmail.co ||m --- Comment #1 from NSLW --- Please look at https://phabricator.kde.org/D5271 and determine if it's worth having this bug open for 4.8. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383832] [proposal] option for opening kicker/kickoff via mouse over
https://bugs.kde.org/show_bug.cgi?id=383832 David Edmundson changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WONTFIX --- Comment #4 from David Edmundson --- Thanks for responding. I'm not particularly convinced, we'd have to have an activation delay, because even with tooltips experience has shown people hit them too often. At which point there's no way you'd save any time with this feature. Plus there's the other suggestion Kai added. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 383850] New: Gwenview shows unreadable paths in Recent Folders
https://bugs.kde.org/show_bug.cgi?id=383850 Bug ID: 383850 Summary: Gwenview shows unreadable paths in Recent Folders Product: gwenview Version: 17.04.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: b...@londonlight.org Target Milestone: --- The paths which Gwenview shows in Recent Folders are not human-friendly. e.g.: file:///home/me/photos/bugs/ file:///tmp/icons/ It would be not only more human-friendly but also more of the path would be visible if the paths were formed as follows: /home/me/photos/bugs/ /tmp/icons/ or even: ~/photos/bugs/ /tmp/icons/ -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 383850] Gwenview shows unreadable paths in Recent Folders
https://bugs.kde.org/show_bug.cgi?id=383850 DrSlony changed: What|Removed |Added CC||b...@londonlight.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383849] New: [Wayland] System Settings crashes upon appearance of any window from options menu in Sidebar view
https://bugs.kde.org/show_bug.cgi?id=383849 Bug ID: 383849 Summary: [Wayland] System Settings crashes upon appearance of any window from options menu in Sidebar view Product: systemsettings Version: 5.10.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: notux...@gmail.com Target Milestone: --- Steps to reproduce: 1. Start System Settings (in 'Sidebar view'). 2. Select options menu (three horizontal lines in top left corner of the app). 3. Select any item from the menu. Actual result: System Settings app crashes. Contents of ~/.local/share/sddm/wayland-session.log file after 'About System Settings' menu item select: QObject::connect: invalid null parameter Using Wayland-EGL Using the 'wl-shell' shell integration WARNING: Cannot find style "org.kde.desktop" - fallback: "/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Desktop" KActivities: Database connection: "kactivities_db_resources_139808611895488_readonly" query_only: QVariant(qlonglong, 1) journal_mode:QVariant(QString, "wal") wal_autocheckpoint: QVariant(qlonglong, 100) synchronous: QVariant(qlonglong, 0) Nothing to load - the client id is empty Nothing to load - the client id is empty : QML QQuickLayoutAttached: Binding loop detected for property "minimumHeight" Creating the cache for: "applications:systemsettings.desktop" Already in database? true First update : QDateTime(2017-08-22 11:35:02.000 EEST Qt::TimeSpec(LocalTime)) Last update : QDateTime(2017-08-22 15:08:21.000 EEST Qt::TimeSpec(LocalTime)) After the adjustment Current score : 29 First update : QDateTime(2017-08-22 11:35:02.000 EEST Qt::TimeSpec(LocalTime)) Last update : QDateTime(2017-08-22 15:08:21.000 EEST Qt::TimeSpec(LocalTime)) Interval length is 0 New score : 30 ResourceScoreUpdated: "5a75bcc8-f88e-463f-8b82-c2702211560c" "org.kde.libtaskmanager" "applications:systemsettings.desktop" -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 142541] Deletion in the Synchronizer
https://bugs.kde.org/show_bug.cgi?id=142541 vollkornkartoff...@posteo.de changed: What|Removed |Added CC||vollkornkartoffeln@posteo.d ||e -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 383821] Allow applications to disconnect device via DBus
https://bugs.kde.org/show_bug.cgi?id=383821 --- Comment #1 from Albert Vaca --- Why is this needed in the first place? With the current design, devices automatically try to discover and connect to each other. This means that if we added a 'disconnect' button, after a while the devices would connect again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 383848] KSyntaxHighlighting 5.37 detects normal text files as poweshell script
https://bugs.kde.org/show_bug.cgi?id=383848 --- Comment #1 from Till Schäfer --- seems to be part of frameworks -> thus, this was introduced with the update to 5.37 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 383848] KSyntaxHighlighting 5.37 detects normal text files as poweshell script
https://bugs.kde.org/show_bug.cgi?id=383848 Till Schäfer changed: What|Removed |Added Summary|kate 17.08.0: syntax|KSyntaxHighlighting 5.37 |highlighting detects normal |detects normal text files |text files as poweshell |as poweshell script |script | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 383848] kate 17.08.0: syntax highlighting detects normal text files as poweshell script
https://bugs.kde.org/show_bug.cgi?id=383848 Till Schäfer changed: What|Removed |Added Version|unspecified |5.37.0 Component|syntax |syntax Product|kate|frameworks-syntax-highlight ||ing -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383836] [Wayland] Kate crashes upon activity in it
https://bugs.kde.org/show_bug.cgi?id=383836 --- Comment #3 from Alexander Mentyu --- Not sure - maybe this is duplikate) of it - https://bugs.kde.org/show_bug.cgi?id=383847 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383848] New: kate 17.08.0: syntax highlighting detects normal text files as poweshell script
https://bugs.kde.org/show_bug.cgi?id=383848 Bug ID: 383848 Summary: kate 17.08.0: syntax highlighting detects normal text files as poweshell script Product: kate Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Since I have upgraded to Kate 17.08.0 (from 17.04.3) all my normal text files are highlighted as powershell script by default (autodetection). The files have a ".txt" extension and not a powershell specific one. This is always reproducible. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383847] New: [Wayland] Kate sometimes crashes when clicking/dragging minimap
https://bugs.kde.org/show_bug.cgi?id=383847 Bug ID: 383847 Summary: [Wayland] Kate sometimes crashes when clicking/dragging minimap Product: kate Version: Git Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Steps to reproduce: 1. Start Kate with long file. 2. Click on various minimap regions or drag current minimap view. Reproducibility: often. Contents of ~/.local/share/sddm/wayland-session.log file: kf5idletime_kwayland: This plugin does not support polling idle time QObject::connect: invalid null parameter Using Wayland-EGL Using the 'wl-shell' shell integration Creating the cache for: "applications:org.kde.kate.desktop" Already in database? true First update : QDateTime(2017-08-22 11:51:50.000 EEST Qt::TimeSpec(LocalTime)) Last update : QDateTime(2017-08-22 15:13:17.000 EEST Qt::TimeSpec(LocalTime)) After the adjustment Current score : 25 First update : QDateTime(2017-08-22 11:51:50.000 EEST Qt::TimeSpec(LocalTime)) Last update : QDateTime(2017-08-22 15:13:17.000 EEST Qt::TimeSpec(LocalTime)) Interval length is 0 New score : 26 ResourceScoreUpdated: "5a75bcc8-f88e-463f-8b82-c2702211560c" "org.kde.libtaskmanager" "applications:org.kde.kate.desktop" KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kate path = /usr/bin pid = 1847 KCrash: Arguments: /usr/bin/kate -b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 383843] Spawning insane amounts of DBus messages while copying files
https://bugs.kde.org/show_bug.cgi?id=383843 Kevin Funk changed: What|Removed |Added CC||davidgilol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 383836] [Wayland] Kate crashes upon activity in it
https://bugs.kde.org/show_bug.cgi?id=383836 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #2 from Kåre Särs --- Hmm... that crashes deep inside Qt Wyland code. -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 383846] New: Inactive menu elements in GTK2 apps difficult to see using Breeze-Dark theme
https://bugs.kde.org/show_bug.cgi?id=383846 Bug ID: 383846 Summary: Inactive menu elements in GTK2 apps difficult to see using Breeze-Dark theme Product: kde-gtk-config Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: manutort...@chakra-project.org Reporter: b...@londonlight.org CC: aleix...@kde.org Target Milestone: --- 1. Select Breeze-Dark as your GTK2 theme. https://i.imgur.com/U5ZJCZs.png 2. Run a GTK2 app, e.g. Inkscape. 3. Open an image and right-click on it, look at the inactive items of the context menu. It takes effort to make out which items are disabled and which are not. http://i.imgur.com/aoRPOwP.png Instead of this weird hard-to-see shadow, just gray-out the item. -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 383846] Inactive menu elements in GTK2 apps difficult to see using Breeze-Dark theme
https://bugs.kde.org/show_bug.cgi?id=383846 DrSlony changed: What|Removed |Added CC||b...@londonlight.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 383843] Spawning insane amounts of DBus messages while copying files
https://bugs.kde.org/show_bug.cgi?id=383843
--- Comment #2 from Kevin Funk ---
Introduced by this commit:
commit dca3d5cfd19375f61dd7d8232586227af3f4b34b
Author: David Gil
Date: Fri Jun 7 22:06:15 2013 +0200
Port time_t to QDateTime in SlaveBase (KIO)
... with the following interesting hunks of the diff:
-void SlaveBase::processedSize( KIO::filesize_t _bytes )
+void SlaveBase::processedSize(KIO::filesize_t _bytes)
{
-bool emitSignal=false;
-struct timeval tv;
-intgettimeofday_res=gettimeofday( &tv, 0L );
+bool emitSignal = false;
+
+QDateTime now = QDateTime::currentDateTime();
-if( _bytes == d->totalSize )
+if (_bytes == d->totalSize)
emitSignal=true;
-else if ( gettimeofday_res == 0 ) {
-time_t msecdiff = 2000;
-if (d->last_tv.tv_sec) {
-// Compute difference, in ms
-msecdiff = 1000 * ( tv.tv_sec - d->last_tv.tv_sec );
-time_t usecdiff = tv.tv_usec - d->last_tv.tv_usec;
-if ( usecdiff < 0 ) {
-msecdiff--;
-msecdiff += 1000;
-}
-msecdiff += usecdiff / 1000;
-}
-emitSignal=msecdiff >= 100; // emit size 10 times a second
+else {
+if (d->lastTimeout.isValid())
+emitSignal = d->lastTimeout.msecsTo(now); // emit size 10 times a
second
+else
+emitSignal = true;
}
-if( emitSignal ) {
+if (emitSignal) {
KIO_DATA << KIO_FILESIZE_T(_bytes);
-send( INF_PROCESSED_SIZE, data );
-if ( gettimeofday_res == 0 ) {
-d->last_tv.tv_sec = tv.tv_sec;
-d->last_tv.tv_usec = tv.tv_usec;
-}
+send(INF_PROCESSED_SIZE, data);
+d->lastTimeout = now;
}
-//d->processed_size = _bytes;
+
+//d->processed_size = _bytes;
}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 383845] New: [Wayland KWin] Position of Dolphin window isn't remembered after reopening
https://bugs.kde.org/show_bug.cgi?id=383845 Bug ID: 383845 Summary: [Wayland KWin] Position of Dolphin window isn't remembered after reopening Product: kwin Version: git master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Steps for reproduce: 1. Start Dolphin and unmaximize it. 2. Remember Dolphin window position and close it. 3. Start Dolphin again. Actual result: Dolphin window started in top left corner. Expected result: Dolphin window started in previous position. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 383843] Spawning insane amounts of DBus messages while copying files
https://bugs.kde.org/show_bug.cgi?id=383843
Kevin Funk changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED |CONFIRMED
--- Comment #1 from Kevin Funk ---
This looks really bad...:
528│ void SlaveBase::processedSize(KIO::filesize_t _bytes)
529│ {
530├>bool emitSignal = false;
531│
532│ QDateTime now = QDateTime::currentDateTime();
533│
534│ if (_bytes == d->totalSize) {
535│ emitSignal = true;
536│ } else {
537│ if (d->lastTimeout.isValid()) {
538│ emitSignal = d->lastTimeout.msecsTo(now);// emit size 10
times a second
539│ } else {
540│ emitSignal = true;
541│ }
542│ }
538│ emitSignal = d->lastTimeout.msecsTo(now);// emit size 10
times a second
^ This expression is totally wrong, isn't it? It doesn't do what the comment
says. It will evaluate to true if there's just a millisecond time difference =>
signal will be emitted every ms?
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 383844] [Wayland KWin] Windows aren't remembering previous maximized state after reopening
https://bugs.kde.org/show_bug.cgi?id=383844 --- Comment #1 from Alexander Mentyu --- Not always reproducible in System Settings - behavior can be sometimes opposite - System Settings window is restarting in maximized window if previously it was unmaximized and closed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 382852] Rechtschreibprüfung funzt nicht
https://bugs.kde.org/show_bug.cgi?id=382852 --- Comment #5 from gilada --- It's probably not up to KMail, the message; "No backup for spelling" is found under "System Settings->Regional Settings->Spell Checker", although I chose German as the default language. Can I please help, urgently, thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 383844] New: [Wayland KWin] Windows aren't remembering previous maximized state after reopening
https://bugs.kde.org/show_bug.cgi?id=383844 Bug ID: 383844 Summary: [Wayland KWin] Windows aren't remembering previous maximized state after reopening Product: kwin Version: git master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Steps for reproduce: 1. Start Dolphin, maximize it, close it and open it again. 2. Start System Settings, maximize it, close it and open it again. 3. Start Discover, maximize it, close it and open it again. Actual results: All apps windows aren't remembering previous maximized state after reopening them. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 383638] Lock/Unlock Widget - suspend button broken
https://bugs.kde.org/show_bug.cgi?id=383638 Christoph Feck changed: What|Removed |Added Version|5.37.0 |unspecified Assignee|kdelibs-b...@kde.org|l.lu...@kde.org Component|general |ui Product|frameworks-kconfigwidgets |ksmserver --- Comment #2 from Christoph Feck --- Are you sure you only updated KF5 frameworks, and not other packages? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 383843] New: Spawning insane amounts of DBus messages while copying files
https://bugs.kde.org/show_bug.cgi?id=383843 Bug ID: 383843 Summary: Spawning insane amounts of DBus messages while copying files Product: frameworks-kio Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: kf...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- Observed via dbus-monitor while copying a file via the FISH kio slave: ``` ... method call time=1503401586.132715 sender=:1.3660 -> destination=:1.3659 serial=17575 path=/DataEngine/applicationjobs/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218009599 string "bytes" method call time=1503401586.133399 sender=:1.3662 -> destination=org.kde.JobViewServer serial=17658 path=/JobViewServer/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218025983 string "bytes" method call time=1503401586.133556 sender=:1.3660 -> destination=:1.3659 serial=17576 path=/DataEngine/applicationjobs/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218025983 string "bytes" method call time=1503401586.135317 sender=:1.3662 -> destination=org.kde.JobViewServer serial=17659 path=/JobViewServer/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218042367 string "bytes" method call time=1503401586.135448 sender=:1.3662 -> destination=org.kde.JobViewServer serial=17660 path=/JobViewServer/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218046462 string "bytes" method call time=1503401586.135558 sender=:1.3660 -> destination=:1.3659 serial=17577 path=/DataEngine/applicationjobs/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218042367 string "bytes" method call time=1503401586.135569 sender=:1.3660 -> destination=:1.3659 serial=17578 path=/DataEngine/applicationjobs/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218046462 string "bytes" method call time=1503401586.149265 sender=:1.3662 -> destination=org.kde.JobViewServer serial=17661 path=/JobViewServer/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218058751 string "bytes" method call time=1503401586.149698 sender=:1.3660 -> destination=:1.3659 serial=17579 path=/DataEngine/applicationjobs/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218058751 string "bytes" method call time=1503401586.150065 sender=:1.3662 -> destination=org.kde.JobViewServer serial=17662 path=/JobViewServer/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218062846 string "bytes" method call time=1503401586.150196 sender=:1.3660 -> destination=:1.3659 serial=17580 path=/DataEngine/applicationjobs/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218062846 string "bytes" method call time=1503401586.150800 sender=:1.3662 -> destination=org.kde.JobViewServer serial=17663 path=/JobViewServer/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218075131 string "bytes" method call time=1503401586.150944 sender=:1.3660 -> destination=:1.3659 serial=17581 path=/DataEngine/applicationjobs/JobView_2; interface=org.kde.JobViewV2; member=setProcessedAmount uint64 218075131 string "bytes" ... ``` The sender (:1.3660) is the kuiserver executable in this case. This is part of the reason why the Plasma Desktop tends to become *really* sluggish when copying large files (observed in a number of other bug reports, such as https://bugs.kde.org/show_bug.cgi?id=356479). When copying files via Dolphin, I usually get the following CPU usages: - plasmashell: 120% CPU - Xorg: 60% CPU - kwin_x11: 7% CPU - fish.so OR sftp.so: ~5% CPU Note: This is unrelated to the fish kio slave, it also happens with the sftp kio slave. I didn't test others. I'm not sure how/when the 'processedAmount' updates are triggered; but right now the happen *far* too often. The desktop cannot cope with this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 366299] System setting "Energy Saving" window is too large for a standard laptop screen
https://bugs.kde.org/show_bug.cgi?id=366299 Christoph Feck changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #18 from Christoph Feck --- *** Bug 360358 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 360358] KCMultiDialog should have scroll bars
https://bugs.kde.org/show_bug.cgi?id=360358 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 366299 *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 383842] New: [Wish DrKonqi] Add ability to send DrKonqi crash reports from DrKonqi itself
https://bugs.kde.org/show_bug.cgi?id=383842 Bug ID: 383842 Summary: [Wish DrKonqi] Add ability to send DrKonqi crash reports from DrKonqi itself Product: drkonqi Version: 5.10.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: notux...@gmail.com Target Milestone: --- Created attachment 107436 --> https://bugs.kde.org/attachment.cgi?id=107436&action=edit drkonqi-crash-window Currently if DrKonqi crashed - 'Report Bug' button is disabled in DrKonqi window and informative text in it says - 'You cannot report this error, because drkonqi does not provide a bug reporting address.' -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 383050] Discover make not download and installation.
https://bugs.kde.org/show_bug.cgi?id=383050 --- Comment #4 from Christoph Feck --- If you can provide the information requested in comment #3, please add it. -- You are receiving this mail because: You are watching all bug changes.
