[digikam] [Bug 222550] Digikam crashes when looking at pictures
https://bugs.kde.org/show_bug.cgi?id=222550 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 272586] crash when playing with databasebackend
https://bugs.kde.org/show_bug.cgi?id=272586 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Albums -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 181545] Digikam crashes unexpectledly while working
https://bugs.kde.org/show_bug.cgi?id=181545 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Mysql -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 267190] digiKam crashes when other applications rename files it is loading.
https://bugs.kde.org/show_bug.cgi?id=267190 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Albums -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 249985] digiKam crashed while downloading images from camera
https://bugs.kde.org/show_bug.cgi?id=249985 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Import -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 300795] Crashed when adding name on 50 photos
https://bugs.kde.org/show_bug.cgi?id=300795 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 290650] DigiKam crashes while trying to display directory of photos
https://bugs.kde.org/show_bug.cgi?id=290650 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Sqlite -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 253283] digikam crashes when renaming files/directory
https://bugs.kde.org/show_bug.cgi?id=253283 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Albums -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 274863] Digikam crashes on close of application
https://bugs.kde.org/show_bug.cgi?id=274863 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Portability -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 302178] digiKam crashed while adding collection
https://bugs.kde.org/show_bug.cgi?id=302178 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database-Media |Portability -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 302178] digiKam crashed while adding collection
https://bugs.kde.org/show_bug.cgi?id=302178 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Media -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 273765] replacing pgf files with an open digikam lead to reproducible crash
https://bugs.kde.org/show_bug.cgi?id=273765 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Portability -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 273399] Crash on exit
https://bugs.kde.org/show_bug.cgi?id=273399 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 223617] digikam crash when changing the name of a pict
https://bugs.kde.org/show_bug.cgi?id=223617 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 230531] digikam crashed while moving pictures from one folder to another
https://bugs.kde.org/show_bug.cgi?id=230531 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 231866] Crash when assigning score
https://bugs.kde.org/show_bug.cgi?id=231866 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 226888] digikam crashs after edit a few images
https://bugs.kde.org/show_bug.cgi?id=226888 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 230799] crash while editing picture
https://bugs.kde.org/show_bug.cgi?id=230799 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 259005] digikam crashed after external disk was turned off
https://bugs.kde.org/show_bug.cgi?id=259005 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 269925] Crash on library creation from usb drive
https://bugs.kde.org/show_bug.cgi?id=269925 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 225263] digikam crashed while applying black and white effect
https://bugs.kde.org/show_bug.cgi?id=225263 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 267359] Crash after unmount hdd drive during process running.
https://bugs.kde.org/show_bug.cgi?id=267359 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 229857] crash while browsing pictures
https://bugs.kde.org/show_bug.cgi?id=229857 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 226663] digikam crashed after applying captions change.
https://bugs.kde.org/show_bug.cgi?id=226663 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 274957] Crash on copy multiple files
https://bugs.kde.org/show_bug.cgi?id=274957 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Thumbs -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 382207] Explanation about how to use the screen reader
https://bugs.kde.org/show_bug.cgi?id=382207 Burkhard Lueck changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/577a208b03e884f ||dec348d0fcf284a8e22c06302 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Burkhard Lueck --- Git commit 577a208b03e884fdec348d0fcf284a8e22c06302 by Burkhard Lück. Committed on 26/07/2017 at 16:27. Pushed by lueck into branch 'master'. Add section about screen reader to kcmaccess kcm docbook add info from http://blogs.fsfe.org/gladhorn/2015/08/09/testing-plasma-next-with-orca-screen-reader/ Differential Revision: https://phabricator.kde.org/D6886 M +29 -2doc/kcontrol/kcmaccess/index.docbook https://commits.kde.org/plasma-desktop/577a208b03e884fdec348d0fcf284a8e22c06302 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382759] New: Can't keep pager positioned in lower right corner of desktop
https://bugs.kde.org/show_bug.cgi?id=382759 Bug ID: 382759 Summary: Can't keep pager positioned in lower right corner of desktop Product: plasmashell Version: 5.10.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: avru...@math.umass.edu CC: plasma-b...@kde.org Target Milestone: 1.0 I have four fully-updated Fedora 26 machines running plasmashell 5.10.1 and on each I use 12 desktops in 4 rows of 3, with the pager sitting just above the (bottom) panel in the lower right corner of the screen. This arrangement has worked in KDE for a long time (and I've had a pager in the lower right corner since I was using fvwm a long time ago, so I want to keep it here). But since I upgraded to Fedora 26 (using "dnf system-upgrade"), I've had trouble keeping the pager in that location. It seems to want to be in the lower left. Initially, I couldn't even move it more than about 7/8 to the right along the panel; if I went farther than that, the pager would just snap back to the lower left corner. And though I could move it to the right edge if I kept it far enough above the panel, when I started to move it down, it would shrink to a minuscule size. After killing off the instance of the pager that was running, I've been able to get a new instance to move most of the way into the lower right corner and stay there until I log out. But whenever I log back in, the pager has moved to the lower left corner (even if I lock widgets before logging off). Saving the session doesn't seem to have any effect, either. I've created a new user on two different machines and seen the same behavior. A web search didn't turn up any indication of changes in the pager that would affect its location or any other reports of this sort of problem. I have asked about this on the Fedora KDE list and haven't received any response, so I assume nobody else is seeing this problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373284] digikam crashed with SIGSEGV in QSortFilterProxyModel::parent()
https://bugs.kde.org/show_bug.cgi?id=373284 Ritesh Raj Sarraf changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #13 from Ritesh Raj Sarraf --- (In reply to caulier.gilles from comment #12) > This problem still reproducible with last 5.6.0 ? No. I haven't seen this crash for the past couple of months. Hence closing. -- You are receiving this mail because: You are watching all bug changes.
[libqapt] [Bug 382693] Muon crashes during package install/remove(in QApt::Backend::package(QLatin1String) const ())(encoding?)
https://bugs.kde.org/show_bug.cgi?id=382693
--- Comment #1 from Ｖ字龍(Vdragon) ---
I rebuilt libqapt and muon with -g -O0, here's the stack trace:
```
Thread 1 "muon" received signal SIGSEGV, Segmentation fault.
0x77648bed in pkgDepCache::FindPkg (this=0x0, Name="dgit") at
/usr/include/apt-pkg/depcache.h:358
358inline PkgIterator FindPkg(std::string const &Name) {return
Cache->FindPkg(Name);};
```
```
#0 0x77648bed in pkgDepCache::FindPkg (this=0x0, Name="dgit") at
/usr/include/apt-pkg/depcache.h:358
#1 0x7763fe28 in QApt::Backend::package (this=0xa35d80, name=...)
at libqapt-3.0.3+p16.04+git20170630.2221/src/backend.cpp:346
#2 0x77640e1d in QApt::Backend::search (this=0xa35d80,
searchString=...)
at libqapt-3.0.3+p16.04+git20170630.2221/src/backend.cpp:585
#3 0x0043acfa in PackageProxyModel::search (this=0x735980,
searchText=...)
at
muon-5.7.0-0+16.04+xenial+build4/src/PackageModel/PackageProxyModel.cpp:71
#4 0x004432b2 in PackageWidget::startSearch (this=0x736030)
at muon-5.7.0-0+16.04+xenial+build4/src/PackageModel/PackageWidget.cpp:410
#5 0x0042a1fa in ManagerWidget::reload (this=0x736030)
at muon-5.7.0-0+16.04+xenial+build4/src/ManagerWidget.cpp:63
#6 0x004289da in MainWindow::reload (this=0x745000)
at muon-5.7.0-0+16.04+xenial+build4/src/MainWindow.cpp:370
#7 0x004284ae in MainWindow::transactionStatusChanged (this=0x745000,
status=QApt::FinishedStatus)
at muon-5.7.0-0+16.04+xenial+build4/src/MainWindow.cpp:304
#8 0x0045dfac in MainWindow::qt_static_metacall (_o=0x745000,
_c=QMetaObject::InvokeMetaMethod,
_id=12, _a=0x7fffd040)
at
muon-5.7.0-0+16.04+xenial+build4/obj-x86_64-linux-gnu/src/moc_MainWindow.cpp:179
#9 0x74edbc19 in QMetaObject::activate (sender=0x1d55a00,
signalOffset=,
local_signal_index=, argv=) at
kernel/qobject.cpp:3766
#10 0x77682b9f in QApt::Transaction::statusChanged (this=0x1d55a00,
_t1=QApt::FinishedStatus)
at
libqapt-3.0.3+p16.04+git20170630.2221/obj-x86_64-linux-gnu/src/moc_transaction.cpp:539
#11 0x77671964 in QApt::Transaction::updateProperty (this=0x1d55a00,
type=3, variant=...)
at libqapt-3.0.3+p16.04+git20170630.2221/src/transaction.cpp:632
#12 0x77681d37 in QApt::Transaction::qt_static_metacall (_o=0x1d55a00,
_c=QMetaObject::InvokeMetaMethod, _id=24, _a=0x7fffd2e0)
at
libqapt-3.0.3+p16.04+git20170630.2221/obj-x86_64-linux-gnu/src/moc_transaction.cpp:286
#13 0x74edbc19 in QMetaObject::activate (sender=0x1d72f50,
signalOffset=,
local_signal_index=, argv=) at
kernel/qobject.cpp:3766
#14 0x7767ee8b in
OrgKubuntuQaptworker3TransactionInterface::propertyChanged (this=0x1d72f50,
_t1=3,
_t2=...)
at
libqapt-3.0.3+p16.04+git20170630.2221/obj-x86_64-linux-gnu/src/transactioninterface_p.moc:372
#15 0x7767e203 in
OrgKubuntuQaptworker3TransactionInterface::qt_static_metacall (_o=0x1d72f50,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fffd4b0)
at
libqapt-3.0.3+p16.04+git20170630.2221/obj-x86_64-linux-gnu/src/transactioninterface_p.moc:188
#16 0x7767eba9 in
OrgKubuntuQaptworker3TransactionInterface::qt_metacall (this=0x1d72f50,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fffd4b0)
at
libqapt-3.0.3+p16.04+git20170630.2221/obj-x86_64-linux-gnu/src/transactioninterface_p.moc:313
#17 0x7383aee3 in QDBusConnectionPrivate::deliverCall (this=, object=,
msg=..., metaTypes=..., slotIdx=) at qdbusintegrator.cpp:998
#18 0x74edcc59 in QObject::event (this=0x1d72f50, e=) at
kernel/qobject.cpp:1246
#19 0x758173fc in QApplicationPrivate::notify_helper (this=, receiver=0x1d72f50,
e=0x7fffd8029aa0) at kernel/qapplication.cpp:3717
#20 0x7581ee07 in QApplication::notify (this=0x7fffdb70,
receiver=0x1d72f50, e=0x7fffd8029aa0)
at kernel/qapplication.cpp:3476
#21 0x74eaf798 in QCoreApplication::notifyInternal2
(receiver=0x1d72f50,
event=event@entry=0x7fffd8029aa0) at kernel/qcoreapplication.cpp:1018
#22 0x74eb1f7b in QCoreApplication::sendEvent (event=0x7fffd8029aa0,
receiver=)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233
#23 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0,
data=0x69fd60) at kernel/qcoreapplication.cpp:1678
#24 0x74eb23e8 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0,
event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1532
#25 0x74f05323 in postEventSourceDispatch (s=0x6e9ce0) at
kernel/qeventdispatcher_glib.cpp:276
#26 0x7fffeff8f197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7fffeff8f3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7fffeff8f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x74f0492f in QEvent
[krita] [Bug 382690] Bezier Curve Selection Tool doesn't work after making the first selection
https://bugs.kde.org/show_bug.cgi?id=382690 Raghavendra kamath changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||raghavendr.ra...@gmail.com --- Comment #3 from Raghavendra kamath --- Same I can reproduce the same issue on master. Also don't know if this is related to this the freehand path tool doesn't work afterwords. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382758] New: Freeze effect doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=382758 Bug ID: 382758 Summary: Freeze effect doesn't work at all Product: kdenlive Version: 16.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: nicolas.guilm...@free.fr Target Milestone: --- Hi, Freeze effect doesn't work whatever I choose Freeze Before or Freeze After or don't check any box. Very strange (Speed effect works fine). I use Kdenlive in French (the Freeze effect is known as "Geler"). Thanks. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 380879] [Qt 5.9] Konsole tabbar does not have empty space at the right side anymore
https://bugs.kde.org/show_bug.cgi?id=380879 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com --- Comment #12 from Roman Gilg --- Ok with this (no fixed length, but not expanding anymore)? https://phabricator.kde.org/D6935 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382748] XWayland rendering artifacts with KWIN_COMPOSE=Q
https://bugs.kde.org/show_bug.cgi?id=382748 --- Comment #5 from Martin Flöser --- Problematic code: const QRect target = QRect(toplevel->clientPos(), toplevel->clientSize()); const QRect src = QRect(toplevel->clientPos() + toplevel->clientContentPos(), pixmap->image().size()); the image size does not match clientSize in the X11 case. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382757] New: Won't launch "Undefined Symbol: qt_hash_seed"
https://bugs.kde.org/show_bug.cgi?id=382757 Bug ID: 382757 Summary: Won't launch "Undefined Symbol: qt_hash_seed" Product: kdenlive Version: 16.04.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: ghon...@gmail.com Target Milestone: --- After the latest update, kdenlive will no longer launch. Installed the KDE Neon/Ubuntu version. Then uninstalled and tried via adding the kdenlive-stable ppa to install from there. Both versions do nothing when clicking the icon. And when attempting to launch via cli return the error: kdenlive: symbol lookup error: kdenlive: undefined symbol: qt_qhash_seed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382748] XWayland rendering artifacts with KWIN_COMPOSE=Q
https://bugs.kde.org/show_bug.cgi?id=382748 Martin Flöser changed: What|Removed |Added Component|wayland-generic |scene-qpainter -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382748] XWayland rendering artifacts with KWIN_COMPOSE=Q
https://bugs.kde.org/show_bug.cgi?id=382748 Martin Flöser changed: What|Removed |Added Keywords||reproducible --- Comment #4 from Martin Flöser --- Just tried myself and yes only drawing is wrong. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382748] XWayland rendering artifacts with KWIN_COMPOSE=Q
https://bugs.kde.org/show_bug.cgi?id=382748 --- Comment #3 from Fabian Vogt --- (In reply to Martin Flöser from comment #2) > is it also scaled down? I mean if you move the mouse over the menu does it > highlight at the correct positions? It's only the drawing that's wrong, if I try xeyes, the offset between cursor and eye increases the further away the cursor is from (0/0), the top left. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 355298] Outlook 2013 hangs after Kleopatra 2.2.0 asks for passphrase when performing signing, encryption, verification, etc.
https://bugs.kde.org/show_bug.cgi?id=355298 --- Comment #6 from Daniel --- I'm not entirely sure how my company is pushing the policy that is setting the permissions but to see the offending settings it is: 1) Component Services 2) Double-click Computers 3) Double-click My Computer 4) Double-click DCOM Config 5) Right-click on ShellWindows and select Properties 6) Click on the Security Tab There you will see the various permission states that are possible. For me it's all grayed out. Apparently this can be normal and there are ways to fix that but the settings just keep getting pushed down on me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382748] XWayland rendering artifacts with KWIN_COMPOSE=Q
https://bugs.kde.org/show_bug.cgi?id=382748 Martin Flöser changed: What|Removed |Added Flags||Wayland+, X11- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382748] XWayland rendering artifacts with KWIN_COMPOSE=Q
https://bugs.kde.org/show_bug.cgi?id=382748 --- Comment #2 from Martin Flöser --- is it also scaled down? I mean if you move the mouse over the menu does it highlight at the correct positions? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382756] New: Plasma crashed, while loading firefox, darkening display but doesn't affecting anything else
https://bugs.kde.org/show_bug.cgi?id=382756 Bug ID: 382756 Summary: Plasma crashed, while loading firefox, darkening display but doesn't affecting anything else Product: plasmashell Version: 5.10.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: pirminbraun16+bugs.kde@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.4) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.13.0-rc2-mainline x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: loading firefox with many tabs - Unusual behavior I noticed: display background brightness getting lowered after or while crash crash icon was in systray/dock, otherwise I didn't notice it was a crash -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f19d1ff9d80 (LWP 919))] Thread 20 (Thread 0x7f1846bd3700 (LWP 2591)): #0 0x7f19c63fbae3 in () at /usr/lib/libglib-2.0.so.0 #1 0x7f19c63fe07b in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f19c63feb3b in () at /usr/lib/libglib-2.0.so.0 #3 0x7f19c63fed1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f19cbf77084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f19cbf1affb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f19cbd3440e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f19ceebd1d5 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f19cbd3915b in () at /usr/lib/libQt5Core.so.5 #9 0x7f19caf00049 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f19cb64cf0f in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f186f0ea700 (LWP 2584)): #0 0x7f19bf97244d in pa_pstream_unref () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #1 0x7f19bf9729a3 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7f19bf97320a in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #3 0x7f19bffe499c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0 #4 0x7f19bffe4d9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #5 0x7f19bffe4e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #6 0x7f19bfff2e29 in () at /usr/lib/libpulse.so.0 #7 0x7f19bf982fe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #8 0x7f19caf00049 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f19cb64cf0f in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f186ded9700 (LWP 1544)): #0 0x7ffe787fead4 in clock_gettime () #1 0x7f19cb65a546 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f19cbf76972 in () at /usr/lib/libQt5Core.so.5 #3 0x7f19cbf7510a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f19cbf756e6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f19cbf76dcf in () at /usr/lib/libQt5Core.so.5 #6 0x7f19c63fe148 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #7 0x7f19c63feb3b in () at /usr/lib/libglib-2.0.so.0 #8 0x7f19c63fed1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #9 0x7f19cbf77084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7f19cbf1affb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7f19cbd3440e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #12 0x7f19ceebd1d5 in () at /usr/lib/libQt5Qml.so.5 #13 0x7f19cbd3915b in () at /usr/lib/libQt5Core.so.5 #14 0x7f19caf00049 in start_thread () at /usr/lib/libpthread.so.0 #15 0x7f19cb64cf0f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f1875766700 (LWP 1484)): #0 0x7f19cb642e9d in poll () at /usr/lib/libc.so.6 #1 0x7f19c63fec09 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f19c63fed1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f19cbf77084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f19cbf1affb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f19cbd3440e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1876bb218a in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f19cbd3915b in () at /usr/lib/libQt5Core.so.5 #8 0x7f19caf00049 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f19cb64cf0f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f1891e50700 (LWP 1476)): #0 0x7f19cbd30a4f in QMutex::unlock() () at /usr/lib/libQt5Core.so.5 #1 0x7f19cbf76fa2 in () at /usr/lib/libQt
[krita] [Bug 382690] Bezier Curve Selection Tool doesn't work after making the first selection
https://bugs.kde.org/show_bug.cgi?id=382690 Quiralta changed: What|Removed |Added CC||rjquira...@gmail.com --- Comment #2 from Quiralta --- I can reproduce this behavior exactly the same on the master branch, not only the Bezier curve selection but also the Bezier Curve tool, they both had the same effect, mentioned here, Git-build on Linux. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 381828] quick channel zapping eventually stops tv playback
https://bugs.kde.org/show_bug.cgi?id=381828 --- Comment #3 from Mauro Carvalho Chehab --- (In reply to Tuxo from comment #2) > Hello, sorry for the delay - I did not get a notification mail for your > request, hope I fixed this now in my email preferences ... > > I just build 2.0.12 from git and I'm afraid it still happens. Try switching > with the previous/next buttons ... it will work for a wille then actually > stop the playback. It's a clean stop with not errors: I just noticed even > the play button changes from "play" to "stop" icon, but I'm not asking it to > do so! Hmm.. perhaps for some reason the channel it tried to play was not detected. If this is the case, if you enable DVB debug, you'll be able to see the messages reporting it from: qCDebug(logDvb, "tuning failed on %.2f MHz", backend->getFrqMHz()); If that's the case, there's not much we can do at Kaffeine, as this is the expected behavior: if a channel can't be played, it should be placed into STOP mode. Yet, in such case, why the tuning is failing? It could be either due to: 1) The hardware takes a long time to tune, and Kaffeine gives up too early; 2) signal is too weak for some channels; 3) some Kernel driver or hardware issue. For (1), there's a setting at the TV config screen that allows you to adjust the maximum amount of time, in ms, that Kaffeine will wait for the driver to lock into a channel. Kaffeine's default is 1500 ms. Such timeout depends on the hardware. Changing it to a higher value should solve it. For (2), you may need a better antenna. At 2.0.12, you can enable dvb debug by calling Kaffeine with: QT_LOGGING_RULES=kaffeine.dvb.debug=true kaffeine > Hitting "play" again will resume playback without an error. Weird > stuff, could it be vdpau related? Can you tell me how to use the xvideo > output instead of vdpau display output? Take a look at README.md. It contains some instructions about how to adjust the video output driver at libVLC. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 381827] DCMAKE_BUILD_TYPE=Release creates debug version
https://bugs.kde.org/show_bug.cgi?id=381827 --- Comment #5 from Mauro Carvalho Chehab --- (In reply to Tuxo from comment #3) > Any plans on adding a debian build structure to your git three? I actually use Fedora here on my main machines ;) My test machine is using Ubuntu, currently, but I don't generate .deb packages there. I don't have any plans to add .deb or .rpm build infra there, but if you send patches for it, I may consider applying, as this could be useful for the others. (In reply to Tuxo from comment #4) > Confirmed, this works nicely in v2.0.12 with the Release build type: there > is no debug without debug option specified, plus debug category filtering > works fine (tested with QT_LOGGING_RULES=kaffeine.dvb.debug=true), thank you! Anytime! > How do I add these environment options into a kaffeine.desktop file? Not sure what you want to do. I mean, by default, debug should be disabled, as this is useful only if someone wants to report a bug. Kaffeine has already a "--debug" option that enables everything, even if built as Release. The main difference is that building Kaffeine in debug node will keep Kaffeine's symbols at its exec file, so debug messages can show the line of the code where each mention was produced, with helps on more critical errors. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 381827] DCMAKE_BUILD_TYPE=Release creates debug version
https://bugs.kde.org/show_bug.cgi?id=381827 --- Comment #4 from Tuxo --- Confirmed, this works nicely in v2.0.12 with the Release build type: there is no debug without debug option specified, plus debug category filtering works fine (tested with QT_LOGGING_RULES=kaffeine.dvb.debug=true), thank you! How do I add these environment options into a kaffeine.desktop file? -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 382755] New: Preparing a translation session
https://bugs.kde.org/show_bug.cgi?id=382755 Bug ID: 382755 Summary: Preparing a translation session Product: lokalize Version: 2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: sha...@ukr.net Reporter: micet2004-li...@yahoo.de Target Milestone: --- I translate sometimes wordpress plugins. I do not need a Project file. IMHO open a POT file should force an autocratically check for language files in the same directory and list them in the overview (instant project). If possible I would like to set-up a second save directory for .mo files. I used pedit earlier and was until now not able to create .mo files here in lokalize. I would like to vote for a solution. where project settings like other directory’s where saved in the comment section inside the .pot file. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 382754] New: K3b complains about missing cdrskin at start up
https://bugs.kde.org/show_bug.cgi?id=382754 Bug ID: 382754 Summary: K3b complains about missing cdrskin at start up Product: k3b Version: 17.04.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: GUI/Usability Assignee: k...@kde.org Reporter: pla...@opensuse.org CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- See Bug 137436 On start up k3b gives this message: Unable to find cdrskin executable K3b uses cdrskin in place of cdrecord. Solution: Install the libburn package which contains cdrskin Forcing unsuspecting users to use a development alternative to cdrecord which works fine for years. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 382747] Kmymoney frameworks branch crashes on start
https://bugs.kde.org/show_bug.cgi?id=382747 Robby Engelmann changed: What|Removed |Added CC||robby.engelm...@igfs-ev.de --- Comment #2 from Robby Engelmann --- I choose option 3) :-) can live with it for a while and want to further test/use the master branch to give feedback. Thanks a lot for KMM and for keeping it alive also under KF5! -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 381828] quick channel zapping eventually stops tv playback
https://bugs.kde.org/show_bug.cgi?id=381828 --- Comment #2 from Tuxo --- Hello, sorry for the delay - I did not get a notification mail for your request, hope I fixed this now in my email preferences ... I just build 2.0.12 from git and I'm afraid it still happens. Try switching with the previous/next buttons ... it will work for a wille then actually stop the playback. It's a clean stop with not errors: I just noticed even the play button changes from "play" to "stop" icon, but I'm not asking it to do so! Hitting "play" again will resume playback without an error. Weird stuff, could it be vdpau related? Can you tell me how to use the xvideo output instead of vdpau display output? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382753] New: Plasma crashed while querying the string in the application menu
https://bugs.kde.org/show_bug.cgi?id=382753 Bug ID: 382753 Summary: Plasma crashed while querying the string in the application menu Product: plasmashell Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: wrightand...@yahoo.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.3) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.2-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Opened up the global application menu, then tried to query the string (in my case I wrote 'qt'). The query results (files and apps) appeared for a fraction of a second, then Plasma crashed. Probably the cause is quite different as the situation can't be reproduced, plus for some reason pulseaudio is mentioned in the stack trace. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe1cf2f3d80 (LWP 7969))] Thread 26 (Thread 0x7fe0ace15700 (LWP 4610)): #0 0x7fe1bcc6798c in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #1 0x7fe1bcc6820a in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7fe1bd2d999c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0 #3 0x7fe1bd2d9d9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fe1bd2d9e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fe1bd2e7e29 in () at /usr/lib/libpulse.so.0 #6 0x7fe1bcc77fe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x7fe1c81f0049 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe1c893cf0f in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fe0afa63700 (LWP 4609)): #0 0x7fe1c8932e9b in poll () at /usr/lib/libc.so.6 #1 0x7fe1c36f3c09 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe1c36f3d1c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fe1c9267084 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe1c920affb in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe1c902440e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fe1cc1ad1d5 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fe1c902915b in () at /usr/lib/libQt5Core.so.5 #8 0x7fe1c81f0049 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fe1c893cf0f in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7fe0c0ff9700 (LWP 11950)): #0 0x7fe1c81f61ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe1c902a5ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe10dd323cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fe10dd372b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fe10dd31913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fe10dd34b6b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fe1c902915b in () at /usr/lib/libQt5Core.so.5 #7 0x7fe1c81f0049 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe1c893cf0f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fe0c17fa700 (LWP 11949)): #0 0x7fe1c81f61ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe1c902a5ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe10dd323cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fe10dd372b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fe10dd31913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fe10dd34b6b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fe1c902915b in () at /usr/lib/libQt5Core.so.5 #7 0x7fe1c81f0049 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe1c893cf0f in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fe0c1ffb700 (LWP 11948)): #0 0x7fe1c81f61ad in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe1c902a5ec in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fe10dd323cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fe10dd372b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0
[plasmashell] [Bug 382728] Icons are pixelated in SystemTray
https://bugs.kde.org/show_bug.cgi?id=382728 --- Comment #2 from Aleksey Kontsevich --- In recent QuiteRss version 0.18.6 they've fixed the icon, only problem with Skype one remains (not critical however). Another bug found with icons in sys tray: QuiteRss draws unread news number on the icon and when icon back to normal (all news was read) it disappears so need to restart application to see the icon again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 382752] New: non-copyable text in notifications
https://bugs.kde.org/show_bug.cgi?id=382752 Bug ID: 382752 Summary: non-copyable text in notifications Product: frameworks-knotifications Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: mklape...@kde.org Reporter: jure.s...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- It would be helpful if we're able to copy text from notifications as sometimes errors and warning show up there and if copying is allowed, we can easily paste it to bug reports or other places where necessary. Example: issuing a notification using eg. `notify-send "title" "body of text I wish to copy"` pops up a notification, but I cannot select nor copy the text displayed. This seems to have been resolved in plasma 4 as per bug 217606, however it seems to be an issue again. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382632] Regression, Harald Sitter is missing a bowtie
https://bugs.kde.org/show_bug.cgi?id=382632 Alex Fiestas changed: What|Removed |Added Priority|NOR |HI --- Comment #6 from Alex Fiestas --- (In reply to Kai Uwe Broulik from comment #5) > I've also seen reports of ENOSUSPENDERS I have observed the same problem. This together with the bowtie situation requires an increase in the importance. Setting it to High. -- You are receiving this mail because: You are watching all bug changes.
[blogilo] [Bug 382751] New: Crash on trying to download blog entries from blogger/blogspot
https://bugs.kde.org/show_bug.cgi?id=382751 Bug ID: 382751 Summary: Crash on trying to download blog entries from blogger/blogspot Product: blogilo Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mehrdad.mom...@gmail.com Reporter: martin.tlus...@gmail.com Target Milestone: --- Application: blogilo (5.5.3) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.4.0-87-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: I had configured blogilo with the blogspot api (blogger wouldn't work), and tried to download the latest blog entries. The crash can be reproduced every time. -- Backtrace: Application: Blogilo (blogilo), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff70d4d6980 (LWP 21530))] Thread 18 (Thread 0x7ff6a31eb700 (LWP 21561)): #0 0x7ff72da756be in timerSourcePrepareHelper (timeout=0x7ff6a31eaa74, src=) at kernel/qeventdispatcher_glib.cpp:132 #1 timerSourcePrepare (source=, timeout=0x7ff6a31eaa74) at kernel/qeventdispatcher_glib.cpp:165 #2 0x7ff71f07791d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff71f0782bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff71f07849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff72da7594b in QEventDispatcherGlib::processEvents (this=0x7ff698c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff72da1e7ca in QEventLoop::exec (this=this@entry=0x7ff6a31eac40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7ff72d847cd4 in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7ff72d84c989 in QThreadPrivate::start (arg=0x2cc9140) at thread/qthread_unix.cpp:368 #9 0x7ff7208976ba in start_thread (arg=0x7ff6a31eb700) at pthread_create.c:333 #10 0x7ff72cf433dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7ff6a3ffe700 (LWP 21556)): #0 0x7ff72cf332ad in write () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ff72ceb4bff in _IO_new_file_write (f=0x7ff72d201540 <_IO_2_1_stderr_>, data=0x7ff6a3ffacb0, n=47) at fileops.c:1263 #2 0x7ff72ceb538a in new_do_write (to_do=47, data=0x7ff6a3ffacb0 "[warn] epoll_wait: Ung\303\274ltiger Dateideskriptor\n", fp=0x7ff72d201540 <_IO_2_1_stderr_>) at fileops.c:518 #3 _IO_new_file_xsputn (f=0x7ff72d201540 <_IO_2_1_stderr_>, data=, n=47) at fileops.c:1342 #4 0x7ff72ce8bf94 in buffered_vfprintf (s=0x7ff72d201540 <_IO_2_1_stderr_>, format=, args=) at vfprintf.c:2341 #5 0x7ff72ce8932d in _IO_vfprintf_internal (s=s@entry=0x7ff72d201540 <_IO_2_1_stderr_>, format=0x7ff71c204734 "[%s] %s\n", ap=ap@entry=0x7ff6a3ffd268) at vfprintf.c:1293 #6 0x7ff72cf52b89 in ___fprintf_chk (fp=0x7ff72d201540 <_IO_2_1_stderr_>, flag=1, format=) at fprintf_chk.c:35 #7 0x7ff71c1ec45e in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #8 0x7ff71c1ec654 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #9 0x7ff71c1f0c38 in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #10 0x7ff71c1dae2d in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 #11 0x7ff7240c292e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7ff7240be3e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7ff7240db0ba in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7ff7240f2f56 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #15 0x7ff7240ef0fd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #16 0x7ff7208976ba in start_thread (arg=0x7ff6a3ffe700) at pthread_create.c:333 #17 0x7ff72cf433dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7ff6c8ff9700 (LWP 21555)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ff7240e73b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7ff7240e7464 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7ff7240c239d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7ff7240be3e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7ff7240db0ba in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7ff7240f2f56 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7ff7240ef0fd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7ff7208976ba in start_thread (arg=0x7f
[kmymoney] [Bug 382747] Kmymoney frameworks branch crashes on start
https://bugs.kde.org/show_bug.cgi?id=382747 NSLW changed: What|Removed |Added CC||lukasz.wojnilow...@gmail.co ||m Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from NSLW --- The problem is know and I think the cause is QWebEngine 5.9. You can: 1) try revert 5c886160ce22f6a0ef17cfd996473f284473fa74 (it doesn't crash after that) 2) downgrade somehow to QWebEngine 5.8 3) wait for an fix in KMM -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369014] Krita freezes/locks up when saving to jpeg or png files (esp when overwrite existing)
https://bugs.kde.org/show_bug.cgi?id=369014 --- Comment #30 from Boudewijn Rempt --- We've been discussing this on irc for the past two days. Today I created a new Sierra installation on a fresh hard disk, downloaded Krita, created a png screenshot, loaded that into krita, saved as another png file and no freeze happened :-( -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377857] Ideas to improve usability of metadata sidebar
https://bugs.kde.org/show_bug.cgi?id=377857 --- Comment #5 from Andrius --- Wanted to paste a couple of screenshots of another pieces of software for your reference. WLPG: https://www.techsupportalert.com/files/photo-gallery.jpg https://ceeesquared.files.wordpress.com/2011/02/tag.jpg I have used WLPG for few years. Its interface is one of the fastest for basic tagging tasks. Zoner: http://images.wondershare.com/images/multimedia/video-editor/zoner-photo-studio-free.jpg I have used it too but did not get attached to it. Many people will really like the right panel. My opinion - keywords (tags) are missing I am not asking anyone to copy anything. Just wanted to paste it here for reference only. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 381827] DCMAKE_BUILD_TYPE=Release creates debug version
https://bugs.kde.org/show_bug.cgi?id=381827 --- Comment #3 from Tuxo --- Ahh, thanks Mauro, will test this ASAP - the last couple of weeks I added QT_LOGGING_RULES="*.debug=false" to my /etc/environment, but it was still weirding me out, how the debian/stable sources I built using the same method were not affected. If I build their source "the debian way" I end up with a deb package and an additional package with the debug symbols. Any plans on adding a debian build structure to your git three? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 382749] New: corona->importLayout() new strange behavior, subject of broken configurations
https://bugs.kde.org/show_bug.cgi?id=382749 Bug ID: 382749 Summary: corona->importLayout() new strange behavior, subject of broken configurations Product: frameworks-plasma Version: 5.36.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: mvourla...@gmail.com Target Milestone: --- Hello, I have two issues with corona->importLayout() which I think I didnt have in the past. we use this function in the upcoming Latte in order to copy a dock. (a dock is a containment containing applets). We copy the dock configuration we want in a new file and from that new file we use the importLayout in order to load the copied dock. 1. In the past the importLayout function was updating also the applet ids when it was used. Now even though it updates the containment id, the applet ids remain the same. That creates a crash of course when removing the copied dock. We workaround this by changing the ids by ourselves and providing unique ids for containments and applets that arent used yet. This of course includes also the settings updating and the systray case 2. Even though the above (1) doesnt create crashes anymore, we observed a very strange behavior that may be irrelevant of (1). the importLayout creates double references to applets. For example if a containment contains two applets with ids(40, 45). The importLayout returns a contaiment that contains 4 applets with ids (40, 40, 45, 45). It is like it double loads the applets -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382750] New: Right click desktop, configure desktop opens ten windows
https://bugs.kde.org/show_bug.cgi?id=382750 Bug ID: 382750 Summary: Right click desktop, configure desktop opens ten windows Product: plasmashell Version: 5.9.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: oliver.urs.l...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 On Kubuntu 17.04, right clicking on the desktop and selecting configure desktop opens 10 (!) windows. I am using two monitors. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows
https://bugs.kde.org/show_bug.cgi?id=368891 oulenz changed: What|Removed |Added CC||oliver.urs.l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382249] bug
https://bugs.kde.org/show_bug.cgi?id=382249 --- Comment #8 from prenol --- Comment on attachment 106869 --> https://bugs.kde.org/attachment.cgi?id=106869 attachment-9665-0.html > > > > > > data-placeholder="Traduction" id="tw-target-text" style="text-align: left; > height: 48px;" data-fulltext="" dir="ltr">Hello > >I send you a video youtube in exmple to see the bug in direct live > > > > > > href="https://youtu.be/oPEs6w5QmJA";>https://youtu.be/oPEs6w5QmJA > > data-placeholder="Traduction" id="tw-target-text" style="text-align: left; > height: 36px;" data-fulltext="" dir="ltr">cordially Prenol > SYLVAIN > > > >-- > >src="https://lh3.googleusercontent.com/-d0MHXSFFwK0/V13YDeC1UzE/eiI/YWuLoRmWWWwxLQXw6nUXV9fzrTMgKIQIgCCo/s144-c/6295425408249975601"; > alt="Prenol SYLVAIN" title="Prenol SYLVAIN" style="float: > left; padding: 0 10px 0 0;" height="92" width="92"> >Prenol SYLVAIN | > > >Tel. +33628594465 > >mailto:prenol.sylv...@gmail.com"; style="color: #403120; > text-decoration: none; border-bottom: 1px #33 > dotted;">prenol.sylv...@gmail.com >http://www.facebook.com/blackjocker973"; style="color: > #0095a2; text-decoration: none; border-bottom: 1px #33 > dotted;">Facebook | >http://fr.linkedin.com/in/prenolsylvain"; style="color: > #0095a2; text-decoration: none; border-bottom: 1px #33 > dotted; target=" _blank"="">linkedin.com | > > > > -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382249] bug
https://bugs.kde.org/show_bug.cgi?id=382249 --- Comment #7 from prenol --- Bonjour As can be seen on the video I sent once I drag the clips into my project and ben the editing is complement deformed -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 381433] Kate crashes when opening
https://bugs.kde.org/show_bug.cgi?id=381433 --- Comment #5 from Jim --- UPDATE (Ignore a lot of the preceding comment) Some of the preceding tests were inadvertently run against the packaged binary (16.12.3) NOT against the fresh locally-built version (17.11.70). All tests are working against the locally-built binary (and opening/saving a session renders that session open-able in the packaged binary). Thank you again! -- You are receiving this mail because: You are watching all bug changes.
[calligracommon] [Bug 323143] Backspace behaves unintuitively in Tamil keyboard layout
https://bugs.kde.org/show_bug.cgi?id=323143 --- Comment #11 from beojan --- In fact, there's an easy way for anyone to reproduce this without knowing Tamil. The bug is in how Unicode combining characters are handled. Here is a Unicode combining acute accent: ́ Here is an 'e' followed by the above character: é Type an e in your chosen application, then copy and paste the acute accent from above. If you then press backspace, only the accent should be deleted. If the bug is present, the e will also be deleted. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371489] Breeze style elements are looking too big
https://bugs.kde.org/show_bug.cgi?id=371489 --- Comment #7 from Aleksey Kontsevich --- When it will be fixed? Need to switch to other style for now? -- You are receiving this mail because: You are watching all bug changes.
[calligracommon] [Bug 323143] Backspace behaves unintuitively in Tamil keyboard layout
https://bugs.kde.org/show_bug.cgi?id=323143 --- Comment #10 from beojan --- QtCreator doesn't exhibit this bug, neither does VLC. KWrite (17.04) does. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 363269] Crash when projects contains *.txt file that is actually a binary file [cmListFileLexerSetToken, CMakeListsParser::readCMakeFile]
https://bugs.kde.org/show_bug.cgi?id=363269 --- Comment #32 from Axel Kellermann --- (In reply to Sven Brauch from comment #31) > Ah yes, if you trick the mimetype detection, you will still crash. You are > also right about strncpy. > > phabricator should be simple enough to use, just log in (with > identity.kde.org), click differential, then click new diff and paste your > diff. OK, I added the diff to phabricator: https://phabricator.kde.org/D6924 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382748] XWayland rendering artifacts with KWIN_COMPOSE=Q
https://bugs.kde.org/show_bug.cgi?id=382748 --- Comment #1 from Fabian Vogt --- Created attachment 106873 --> https://bugs.kde.org/attachment.cgi?id=106873&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382748] New: XWayland rendering artifacts with KWIN_COMPOSE=Q
https://bugs.kde.org/show_bug.cgi?id=382748 Bug ID: 382748 Summary: XWayland rendering artifacts with KWIN_COMPOSE=Q Product: kwin Version: git master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de Target Milestone: --- With KWIN_COMPOSE=Q, Xwayland windows seem to be drawn at a size different from the native pixmap. They appear squashed and do not fill the window borders. Screenshot attached, the konsole on the top is an X window, the konsole in the background a native wayland client. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 381433] Kate crashes when opening
https://bugs.kde.org/show_bug.cgi?id=381433 --- Comment #4 from Jim --- Just confirming that commit 34e61eda173a3e2db5b8d4f0ba86c3b2eb05f5df by Christoph Cullmann largely resolved the reported issue, with a few caveats detailed below. Thank you Christoph, and sorry for the lack of response earlier. Let me know if you'd still like a sample session config. (Built from master branch at commit c7d3c9bbc77aff60223603c3acfb087226081627) - Starting Kate and selecting "New Session" from the initial Session chooser correctly creates a new, fully-functional session. - Saving a new session and reloading it works as expected However: - Trying to load an older session from the initial Session chooser dialog (before Kate is loaded) causes a crash similar to the initial bug report - Creating a new session and then attempting to switch to an older session similarly crashed (via both session dialogue and quick-open menu) I'm happy enough to just delete my old/pre-existing sessions, but will refrain from doing so for now in case there's useful info in them. Let me know if I can supply configs/backtraces/other info, otherwise I'm happy for this to remain as RESOLVED FIXED. -- You are receiving this mail because: You are watching all bug changes.
[calligracommon] [Bug 323143] Backspace behaves unintuitively in Tamil keyboard layout
https://bugs.kde.org/show_bug.cgi?id=323143 --- Comment #9 from Camilla Boemann --- The hint about clementine is relevant as it is probably then a problem in both Kate and Calligra. Not the same directly but we seem to both have made a similar mistake The next thing is finding a tamill speaking developer and have them get in contact with us. Without a tamill keyboard and knowledge etc it's rather hard for us to know if we are doing the right thing - let alone that we don't have time to work on it -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 202370] closing tab sets focus to search instead of content
https://bugs.kde.org/show_bug.cgi?id=202370 Volkmar Wörner changed: What|Removed |Added CC|volkmar.woerner+KDE@mailbox | |.org| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376048] Filter "Levels" wrong histogram
https://bugs.kde.org/show_bug.cgi?id=376048 Raghavendra kamath changed: What|Removed |Added CC||raghavendr.ra...@gmail.com --- Comment #2 from Raghavendra kamath --- I saw a weird behaviour regarding this. If you switch to logarithmic and switch back to normal again it shows the correct one. Also i noticed that histogram (wrong one) is a bit pixelated, could it be that it is stretched horizontally beyond the graph? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 382485] OpenGL 2 compositing setup failed
https://bugs.kde.org/show_bug.cgi?id=382485 --- Comment #6 from Yannick --- Ok, forget what I said in my previous comment... I just had the same issue with the OpenGL 3.1 backend (starting Steam will disable kwin compositing, and it won't enable it again). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 382747] New: Kmymoney frameworks branch crashes on start
https://bugs.kde.org/show_bug.cgi?id=382747 Bug ID: 382747 Summary: Kmymoney frameworks branch crashes on start Product: kmymoney Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: General Assignee: kmymoney-de...@kde.org Reporter: robby.engelm...@igfs-ev.de Target Milestone: --- Kmymoney latest master is crashing several times when trying to start it. After some tries it finally will start. Here is what I get in the terminal: :~> kmymoney KMyMoney csvexport plugin loaded KMyMoney csvimport plugin loaded KMyMoney iCalendar plugin loaded KMyMoney kbanking plugin loaded KMyMoney ofximport plugin loaded KMyMoney printcheck plugin loaded Connect was done KMyMoneyPlugin::KMMViewInterface(0x5578a2dd0530) [1:1:0100/00.293958:ERROR:broker_posix.cc(41)] Invalid node channel message Segmentation fault (core dumped) Kmymoney should be at latest git from here: http://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/Unstable:/Extra/openSUSE_Tumbleweed/): KDE Frameworks 5.36.0 Qt 5.9.1 (built against 5.9.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382638] Task manager keeps an empty list open when a group is undone
https://bugs.kde.org/show_bug.cgi?id=382638 --- Comment #3 from Christoph Feck --- When closing a single entry from a group menu, the group menu also used to resize. Now it keeps a blank entry. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382663] Usability
https://bugs.kde.org/show_bug.cgi?id=382663 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Christoph Feck --- Please report issues in separate tickets. They need to be assigned to different developers and are to be resolved independently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382746] New: Plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=382746 Bug ID: 382746 Summary: Plasmashell crash Product: plasmashell Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: erz96...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.3) Qt Version: 5.9.1 Frameworks Version: 5.36.0 Operating System: Linux 4.11.8-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Plasmashell already ran at 48% for a while. When I closed an Okular window, it crashed and restarted. I have observed this behaviour before, typically when closing more than one Okular window in quick succession. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f11c65fa8c0 (LWP 3204))] Thread 10 (Thread 0x7f10e29f6700 (LWP 9521)): #0 0x7f11bfc1e18d in poll () at /lib64/libc.so.6 #1 0x7f11b6a30881 in () at /usr/lib64/libpulse.so.0 #2 0x7f11b6a22240 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f11b6a228d0 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f11b6a22960 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f11b6a307c9 in () at /usr/lib64/libpulse.so.0 #6 0x7f11b5a810b8 in () at /usr/lib64/pulseaudio/libpulsecommon-10.0.so #7 0x7f11bf4e14d7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f11bfc27b2f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f10e3fff700 (LWP 9520)): #0 0x7ffd1353da8c in clock_gettime () #1 0x7f11bfc35076 in clock_gettime () at /lib64/libc.so.6 #2 0x7f11c053c0c1 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f11c053a999 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f11c053af15 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f11c053c45e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f11bac53258 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f11bac53c4b in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f11bac53e2c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f11c053c6ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f11c04e535a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f11c031531a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f11c3460635 in () at /usr/lib64/libQt5Qml.so.5 #13 0x7f11c0319d2e in () at /usr/lib64/libQt5Core.so.5 #14 0x7f11bf4e14d7 in start_thread () at /lib64/libpthread.so.0 #15 0x7f11bfc27b2f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f10f6afb700 (LWP 3859)): #0 0x7f11bfc1e18d in poll () at /lib64/libc.so.6 #1 0x7f11bac53d19 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f11bac53e2c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f11c053c6ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f11c04e535a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f11c031531a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f10f939cf37 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7f11c0319d2e in () at /usr/lib64/libQt5Core.so.5 #8 0x7f11bf4e14d7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f11bfc27b2f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f110cbac700 (LWP 3732)): #0 0x7ffd1353db10 in clock_gettime () #1 0x7f11bfc35076 in clock_gettime () at /lib64/libc.so.6 #2 0x7f11c053c0c1 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f11c053a999 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f11c053af15 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f11c053c45e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f11bac53258 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f11bac53c4b in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f11bac53e2c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f11c053c6ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f11c04e535a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f11c031531a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f11c4007342 in () at /usr/lib64/libQt5Quick.so.5 #13 0x7f11c0319d2e in () at /usr/lib64/libQt5Core.so.5 #14 0x7f11bf4e14d7 in start_thread () at /lib64/libpthread.so.0 #15 0x7f11bfc27b2f in clone () a
[kate] [Bug 382720] crash after change sessions
https://bugs.kde.org/show_bug.cgi?id=382720 Christoph Feck changed: What|Removed |Added Severity|critical|crash Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Christoph Feck --- If this happes again, add the backtrace of the crash. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 382719] Close program when ctrl+w
https://bugs.kde.org/show_bug.cgi?id=382719 Christoph Feck changed: What|Removed |Added Severity|critical|crash Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Christoph Feck --- If this happes again, add the backtrace of the crash. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 382739] Report
https://bugs.kde.org/show_bug.cgi?id=382739 Christoph Feck changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Use the Plasma 5 version (kcmshell5 clock). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 380972] Overlapping labels on front page
https://bugs.kde.org/show_bug.cgi?id=380972 Fabian Vogt changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Fabian Vogt --- Still happens if the words are fairly long. There just needs to me more space between the icons, like in the icon view. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371489] Breeze style elements are looking too big
https://bugs.kde.org/show_bug.cgi?id=371489 Christoph Feck changed: What|Removed |Added CC||akontsev...@gmail.com --- Comment #6 from Christoph Feck --- *** Bug 382740 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382740] QTreeVeiw line spacing in KDE and Qt applications
https://bugs.kde.org/show_bug.cgi?id=382740 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 371489 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382745] New: Crash when switching desktops while KDE is currently switching me to another one I don't want to go to yet
https://bugs.kde.org/show_bug.cgi?id=382745 Bug ID: 382745 Summary: Crash when switching desktops while KDE is currently switching me to another one I don't want to go to yet Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jose...@main.nc.us CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-87-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: When I click on a URL in an application (usually Thunderbird or PassKeeperX), it immediately activates my browser window on another desktop. I want the URL to open, but not activate the browser window - I want to stay in the current window/desktop until I am ready to switch. I don't know of a way to get this desired behavior. Because of this, I often press the keyboard shortcut to take me back to the desktop where I was - very quickly - before the desktop is finished switching. I think this is what has caused me multiple crashes like this. If I am more patient and let it settle first, it does not crash. I tried to mark this as a possible duplicate of 342763, but didn't see how to do that because it was a nested bug report and seemed to ignore my selection. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f64066bf8c0 (LWP 16066))] Thread 8 (Thread 0x7f633e499700 (LWP 16328)): #0 0x7f6400dd270d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f63fdb6738c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f63fdb6749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f64016ff7eb in QEventDispatcherGlib::processEvents (this=0x7f63380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f64016a6b4a in QEventLoop::exec (this=this@entry=0x7f633e498cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f64014c3834 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f63409777d7 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f64014c87be in QThreadPrivate::start (arg=0x386f8f0) at thread/qthread_unix.cpp:331 #8 0x7f64005b46ba in start_thread (arg=0x7f633e499700) at pthread_create.c:333 #9 0x7f6400dde3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f63d53ab700 (LWP 16084)): #0 0x7f6400dd270d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f63fdb6738c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f63fdb6749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f64016ff7eb in QEventDispatcherGlib::processEvents (this=0x7f634c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f64016a6b4a in QEventLoop::exec (this=this@entry=0x7f63d53aac90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f64014c3834 in QThread::exec (this=this@entry=0x139d180) at thread/qthread.cpp:503 #6 0x7f64046f1ed6 in QQuickPixmapReader::run (this=0x139d180) at util/qquickpixmapcache.cpp:817 #7 0x7f64014c87be in QThreadPrivate::start (arg=0x139d180) at thread/qthread_unix.cpp:331 #8 0x7f64005b46ba in start_thread (arg=0x7f63d53ab700) at pthread_create.c:333 #9 0x7f6400dde3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f63d7fff700 (LWP 16074)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6406110bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f6406110c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f64005b46ba in start_thread (arg=0x7f63d7fff700) at pthread_create.c:333 #4 0x7f6400dde3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f63ddd18700 (LWP 16073)): #0 0x7f63fdbaba94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f63fdb67381 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f63fdb6749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f64016ff7eb in QEventDispatcherGlib::processEvents (this=0x7f63d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f64016a6b4a in QEventLoop::exec (this=this@entry=0x7f63ddd17ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f64014c3834 in QThread::exec (this=this@entry=0xf45b40) at thre
[plasmashell] [Bug 379994] KDE freeze for 2-3 Minutes due to network disconnect while cifs mount
https://bugs.kde.org/show_bug.cgi?id=379994 --- Comment #4 from David Edmundson --- #2 0x7f7ec7f37884 in QFileInfo::isDir() const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f7ec227f452 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #4 0x7f7ec2283bd6 in KFileItem::mimeComment() const () from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #5 0x7f7ec601fc29 in KDirModel::data(QModelIndex const&, int) const () from /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #6 0x7f7e14bbbfd5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/private/desktopcontainment/folder/libfolderplugin.so ... sendHoverEvent backtrace of plasma freeze -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382632] Regression, Harald Sitter is missing a bowtie
https://bugs.kde.org/show_bug.cgi?id=382632 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #5 from Kai Uwe Broulik --- I've also seen reports of ENOSUSPENDERS -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379994] KDE freeze for 2-3 Minutes due to network disconnect while cifs mount
https://bugs.kde.org/show_bug.cgi?id=379994 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WONTFIX |--- -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 382632] Regression, Harald Sitter is missing a bowtie
https://bugs.kde.org/show_bug.cgi?id=382632 Harald Sitter changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Harald Sitter --- Mh. I see what you mean, UX regressed rather severely there. The good news is: I think I know what the problem is. Working on a fix now. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 163044] KDE 4 performs very badly on Freenx remote connections.
https://bugs.kde.org/show_bug.cgi?id=163044 --- Comment #5 from Frédéric COIFFIER --- Setting in my .bashrc : export QT_GRAPHICSSYSTEM=native solved this problem during several years. (Unfortunately, it no longer works with Qt5 and FreeNX is unusable with Qt5/KDE5/Plasma) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 382744] New: Akonadi DAV resource crashes on start
https://bugs.kde.org/show_bug.cgi?id=382744 Bug ID: 382744 Summary: Akonadi DAV resource crashes on start Product: Akonadi Version: 4.13 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: m.w...@web.de Target Milestone: --- Created attachment 106872 --> https://bugs.kde.org/attachment.cgi?id=106872&action=edit crash report Since an update about one two weeks ago the akonadi dav resource always crashes on start. I can not tell the version number, but the crashes happens with the latest packages in KDE Neon (user, not dev version). -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 202032] Some widgets are not refreshed during scrolling
https://bugs.kde.org/show_bug.cgi?id=202032 Frédéric COIFFIER changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||frederic.coiff...@free.fr Resolution|--- |FIXED --- Comment #3 from Frédéric COIFFIER --- This problem has disappeared with Qt5. -- You are receiving this mail because: You are watching all bug changes.
[calligracommon] [Bug 323143] Backspace behaves unintuitively in Tamil keyboard layout
https://bugs.kde.org/show_bug.cgi?id=323143 --- Comment #8 from jagannatha...@gmail.com --- I am using the Tamil layout from ibus/ibus-m17n and set it at boot time to switch between US and IN(TAM) using CAPS. I wanted to set it up globally to make sure it works in other WMs as well and it works inside plasma as well. For example the intended behaviour described in the first comment works in Firefox and for a pure Qt example, clementine search has this behaviour. I am testing clementine's Qt5 experimental branch. Please do suggest any other test I could perform to narrow it down. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 150121] Build Failed Generating index.cache.bz2
https://bugs.kde.org/show_bug.cgi?id=150121 Frédéric COIFFIER changed: What|Removed |Added CC||frederic.coiff...@free.fr --- Comment #22 from Frédéric COIFFIER --- I think KDE4 is no longer maintained and I have never seen this problem in recent KDE5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382581] Add window search in places which list open windows
https://bugs.kde.org/show_bug.cgi?id=382581 --- Comment #2 from Eugene --- > Btw you can also start typing in Present Windows to filter. Wow, thank you very much, this wasn't evident to me, at all. Consider adding a search bar maybe? > Can you explain this in more detail, please? What does "active sources" mean? Active sources = currently enabled search plugins. It was possible before to assign a shortcut to a plugin-scoped search, like this: https://i.stack.imgur.com/0eleR.png, was very convenient. -- You are receiving this mail because: You are watching all bug changes.
[kcalcore] [Bug 382712] Wrong timezone in SOGo
https://bugs.kde.org/show_bug.cgi?id=382712 Oleg Solovyov changed: What|Removed |Added CC||mcpa...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382743] Text is not updating properly
https://bugs.kde.org/show_bug.cgi?id=382743 Oleg Solovyov changed: What|Removed |Added CC||mcpa...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382743] New: Text is not updating properly
https://bugs.kde.org/show_bug.cgi?id=382743 Bug ID: 382743 Summary: Text is not updating properly Product: plasmashell Version: 5.10.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: mcpa...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 106871 --> https://bugs.kde.org/attachment.cgi?id=106871&action=edit Update subtext on changing window titles Text containing window titles is not updating properly. It happens ONLY when minimizing or restoring any window, not when title is actually updated. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 382046] [mtp] Cannot paste from clipboard to empty folders
https://bugs.kde.org/show_bug.cgi?id=382046 Albert Vaca changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kio ||/0ac78aa3fba42dbd72f656c200 ||e0748223c41397 --- Comment #5 from Albert Vaca --- Git commit 0ac78aa3fba42dbd72f656c200e0748223c41397 by Albert Vaca. Committed on 26/07/2017 at 08:34. Pushed by albertvaka into branch 'master'. Emit a "." UDSEntry when not present, even on empty directories. Differential Revision: https://phabricator.kde.org/D6906 M +10 -10 src/core/slavebase.cpp https://commits.kde.org/kio/0ac78aa3fba42dbd72f656c200e0748223c41397 -- You are receiving this mail because: You are watching all bug changes.
