[plasmashell] [Bug 360333] New system tray: icons do not scale with panel height, stay very small
https://bugs.kde.org/show_bug.cgi?id=360333 Max changed: What|Removed |Added CC||haz...@gmail.com --- Comment #26 from Max --- I have a ratio of 1.3 on my machine, and the icons don't scale at all in 5.8.0. Used to scale properly in 5.7.last. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368680] Parts of the UI that may confuse new users
https://bugs.kde.org/show_bug.cgi?id=368680 --- Comment #2 from Max --- Thanks for the info, I've started a topic on the forum: https://forum.kde.org/viewtopic.php?f=137&t=135985 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368680] New: Parts of the UI that may confuse new users
https://bugs.kde.org/show_bug.cgi?id=368680 Bug ID: 368680 Summary: Parts of the UI that may confuse new users Product: krita Version: 3.0.1 Platform: Other OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: maxim.proda...@imperiaonline.org - When making a new custom brush tip, "Use color as mask" should be on by default. New users can get confused why their custom brush only paints black. - "Create brush tip from image" is kind of hidden. You may want to add it in the Edit menu (similar to Photoshop's Edit>Define Brush Preset). - Smudge brush is more often used than color smudge. "Color rate" can be 0% by default. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368679] New: Several frequently used commands are missing custom shortcuts
https://bugs.kde.org/show_bug.cgi?id=368679 Bug ID: 368679 Summary: Several frequently used commands are missing custom shortcuts Product: krita Version: 3.0.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: shortcuts Assignee: krita-bugs-n...@kde.org Reporter: maxim.proda...@imperiaonline.org - Zoom and pan tool cannot have custom shortcuts (when using tablet, it's hard to use the standard shortcuts like Ctrl+MMB) - Shortcut to increase/decrease brush angle, flatness, etc. - Shortcut to run a specific macro. - The current Ctrl+MMB shortcut to zoom in/out ought to be the default behavior when dragging with the zoom tool. It's much more useful than the curent zoom tool drag behavior. - Shortcut to toggle brush editor only turns it on, not off. It is also named "brush editor", and not "edit brush settings", which is confusing when searching for it. Names like "Show color docker; show layers docker" would be easier to find. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #133 from Max --- Perhaps it's not that you can't send multiple dataChanged signals without returning to event loop, but dataChanged is not correct signal here. dataChanged must be sent if only data of items is changed, but since order of the items in the list is also changing, beginResetModel-endResetModel pair or layoutAboutToBeChanged-layoutChanged are both correct solutions here. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 356301] Blank screen on boot but able to open apps with alt-space search
https://bugs.kde.org/show_bug.cgi?id=356301 Max changed: What|Removed |Added CC||thesource...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 356301] Blank screen on boot but able to open apps with alt-space search
https://bugs.kde.org/show_bug.cgi?id=356301 --- Comment #2 from Max --- Created attachment 98968 --> https://bugs.kde.org/attachment.cgi?id=98968&action=edit New crash information added by DrKonqi krunner (5.6.3) using Qt 5.6.0 - What I was doing when the application crashed: It seems that crash happens when I type fast in krunner search field. If I type slowly, works fine. -- Backtrace (Reduced): #5 0x7f4d137a6f3a in mdb_txn_renew0 () at /lib64/liblmdb.so.0.0.0 #6 0x7f4d137a8344 in mdb_txn_begin () at /lib64/liblmdb.so.0.0.0 #7 0x7f4d13e3695e in Baloo::SearchStore::exec(Baloo::Term const&, unsigned int, int, bool) () at /lib64/libKF5Baloo.so.5 #8 0x7f4d13e1f9b2 in Baloo::Query::exec() () at /lib64/libKF5Baloo.so.5 #9 0x7f4d14047b31 in SearchRunner::match(Plasma::RunnerContext&, QString const&, QString const&) () at /usr/lib64/qt5/plugins/krunner_baloosearchrunner.so -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 349075] [crash] When entering fullscreen mode
https://bugs.kde.org/show_bug.cgi?id=349075 --- Comment #1 from Max --- Created attachment 98499 --> https://bugs.kde.org/attachment.cgi?id=98499&action=edit New crash information added by DrKonqi gwenview (4.14.0 pre) on KDE Platform 4.14.17 using Qt 4.8.7 - What I was doing when the application crashed: I was entering fullscreen mode. - Unusual behavior I noticed: The screen became unresponsive temporarily, and it looked like it was only partially fullscreen (the image wasn't scaled to fill the screen, but the title bar and taskbar had disappeared.) -- Backtrace (Reduced): #6 0x003b007bdd4d in KIO::UDSEntry::numberValue(unsigned int, long long) const () at /lib64/libkio.so.5 #7 0x003afaeda48f in Gwenview::ThumbnailProvider::slotResult(KJob*) () at /lib64/libgwenviewlib.so.4 [...] #9 0x003afd73f6f2 in KJob::result(KJob*) () at /lib64/libkdecore.so.5 #10 0x003afd73f740 in KJob::emitResult() () at /lib64/libkdecore.so.5 #11 0x003b0078d308 in KIO::PreviewJobPrivate::determineNextFile() () at /lib64/libkio.so.5 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 349075] [crash] When entering fullscreen mode
https://bugs.kde.org/show_bug.cgi?id=349075 Max changed: What|Removed |Added CC||maxy_da...@lycos.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360192] Pidgin (gtk2) tray icon is tiny, ksensors (kde3) tray icon is misplaced
https://bugs.kde.org/show_bug.cgi?id=360192 --- Comment #7 from Max --- Tested in 5.6.2, seems fine, both icons are displayed correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 342105] [HUION] Cannot right click with the Pen of Huion H610 Pro
https://bugs.kde.org/show_bug.cgi?id=342105 --- Comment #28 from Max --- Update to my post, sorry guys but previous trick didn't actually working for thoose who still got not working Right click: remap with AutoHotKey any non conflict key on keyboard to right click - i.e. NumpadMult::Rbutton or, in case if you have tablet with keybuttons: set any keybutton on your graphic tablet to NumpadMult (any key you prefer) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 342105] [HUION] Cannot right click with the Pen of Huion H610 Pro
https://bugs.kde.org/show_bug.cgi?id=342105
Max changed:
What|Removed |Added
CC||ge...@yandex.ru
--- Comment #27 from Max ---
Hi,
i solve that issue with my Huion H58L,
it's a bit tricky but worth it
so follow this steps:
1. download AutoHotkey utility from autohotkey.com (remap key utility for
windows)
2. install to your PC
3. open AutoHotkey .ahk which is in the Documents dir by default.
4. at the end of the file in the new line paste this: Shift &
NumpadMult::send,{Rbutton}
*tip: you can replace shift and numpadMult to any keys that wont conflict to
krita shortcut
5. open huion tablet driver configuration (in the tray),
click to configure Right click button (which is right click by default) to a
shortcut key
then set that shortcut to Numpad* and Shift (or keys your choosen).
6. reload autohotkey script, by right click at the tray icon and click reload
script.
7. .. now you can use right click button on your stylus!
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 360343] New: KRunner crashed when trying to use it for a calculation
https://bugs.kde.org/show_bug.cgi?id=360343 Bug ID: 360343 Summary: KRunner crashed when trying to use it for a calculation Product: krunner Version: 5.5.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: maxy_da...@lycos.com Application: krunner (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.4.3-201.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: - What I was doing when the application crashed: After not having used it for a while, I pressed the keystroke to open KRunner, and then began typing numbers to calculate something. It froze and then crashed completely. The crash can be reproduced sometimes. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f323b466900 (LWP 3106))] Thread 11 (Thread 0x7f3233e4d700 (LWP 3108)): #0 0x003498ef757d in poll () at /lib64/libc.so.6 #1 0x00349ca0a182 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x00349ca0bc77 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f32348f8da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x0034a96a33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x003499607555 in start_thread () at /lib64/libpthread.so.0 #6 0x003498f02ded in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f322bdf4700 (LWP 3122)): #0 0x003498ef757d in poll () at /lib64/libc.so.6 #1 0x00349ae49dbc in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x00349ae49ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x0034a98daecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x0034a9881eca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x0034a969e434 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x0034c3ad99b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x0034a96a33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x003499607555 in start_thread () at /lib64/libpthread.so.0 #9 0x003498f02ded in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f321dace700 (LWP 24052)): #0 0x00349960c540 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x0034a96a466b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f32295cebdf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f32295d3388 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f32295cdc93 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f32295d0c23 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #6 0x0034a96a33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x003499607555 in start_thread () at /lib64/libpthread.so.0 #8 0x003498f02ded in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f321d2cd700 (LWP 24053)): #0 0x00349960c540 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x0034a96a466b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f32295cebdf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #3 0x7f32295d3388 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #4 0x7f32295cdc93 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #5 0x7f32295d33e2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f32295cdc93 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7f32295d0c23 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #8 0x0034a96a33de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x003499607555 in start_thread () at /lib64/libpthread.so.0 #10 0x003498f02ded in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f321cacc700 (LWP 24054)): #0 0x00349960c540 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x0034a96a466b in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f32295cebdf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at
[plasmashell] [Bug 360192] New: Pidgin (gtk2) tray icon is tiny, ksensors (kde3) tray icon is misplaced
https://bugs.kde.org/show_bug.cgi?id=360192 Bug ID: 360192 Summary: Pidgin (gtk2) tray icon is tiny, ksensors (kde3) tray icon is misplaced Product: plasmashell Version: 5.5.5 Platform: Other URL: http://i75.fastpic.ru/big/2016/0307/9f/e7a949ee5a7650d 3ef31e235ba42159f.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: thesource...@gmail.com This problem appeared in 5.5.5, in 5.5.4 those icons were fine, see screenshot: in upper right corner is very very small pidgin icon, in lower left - ksensors icon misplaced (or stretched?) beyond right border of it's area. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359776] plasmashell has started crashing after latest dnf update on Fedora 23
https://bugs.kde.org/show_bug.cgi?id=359776 Max changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #2 from Max --- I don't understand how this can be a duplicate of a bug that was opened in 2015-01-12 when my issue just started happening in the last week. So this bug is with the current version 5.5.4 and not 5.1.95. If you plan on duplicating this again with bug 342763 then how can we get 342763 assigned to someone who has the time to fix the current issues. --- Comment #3 from Max --- I don't understand how this can be a duplicate of a bug that was opened in 2015-01-12 when my issue just started happening in the last week. So this bug is with the current version 5.5.4 and not 5.1.95. If you plan on duplicating this again with bug 342763 then how can we get 342763 assigned to someone who has the time to fix the current issues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359776] plasmashell has started crashing after latest dnf update on Fedora 23
https://bugs.kde.org/show_bug.cgi?id=359776 Max changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #2 from Max --- I don't understand how this can be a duplicate of a bug that was opened in 2015-01-12 when my issue just started happening in the last week. So this bug is with the current version 5.5.4 and not 5.1.95. If you plan on duplicating this again with bug 342763 then how can we get 342763 assigned to someone who has the time to fix the current issues. --- Comment #3 from Max --- I don't understand how this can be a duplicate of a bug that was opened in 2015-01-12 when my issue just started happening in the last week. So this bug is with the current version 5.5.4 and not 5.1.95. If you plan on duplicating this again with bug 342763 then how can we get 342763 assigned to someone who has the time to fix the current issues. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359776] New: plasmashell has started crashing after latest dnf update on Fedora 23
https://bugs.kde.org/show_bug.cgi?id=359776 Bug ID: 359776 Summary: plasmashell has started crashing after latest dnf update on Fedora 23 Product: plasmashell Version: 5.5.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mvohl...@us.ibm.com CC: bhus...@gmail.com, plasma-b...@kde.org plasmashell has started crashing after latest dnf update on Fedora 23. I'm using the focus follows mouse focus policy. The crashes seem to happen when the focus is moved between windows due to movement of the mouse. The crashes don't happen all of the time though. Reproducible: Sometimes Steps to Reproduce: The crashes happen randomly but seem to be related to the focus moving between windows. Here is the stack trace from running coredumpctl gdb #0 0x7f1974907a98 in __GI_raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7f197ccdcedc in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash-5.19.0/src/kcrash.cpp:431 #2 0x7f1974907b20 in () at /lib64/libc.so.6 #3 0x00a0 in () #4 0x7f19757e2ab7 in QMetaObject::activate(QObject*, int, void**) (sender=sender@entry=0x5620ff099290, signal_index=6, argv=argv@entry=0x0) at kernel/qobject.cpp:3759 #5 0x7f19796e60e2 in VDMModelDelegateDataType::notify(QQmlAdaptorModel const&, QList const&, int, int, QVector const&) const (this=, items=..., index=0, count=1, roles=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/util/qqmladaptormodel.cpp:171 #6 0x7f197995c1ea in QQmlDelegateModel::_q_itemsChanged(int, int, QVector const&) (roles=..., count=1, index=, items=..., this=0x5620fe3edb48) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/util/qqmladaptormodel_p.h:118 #7 0x7f197995c1ea in QQmlDelegateModel::_q_itemsChanged(int, int, QVector const&) (this=, index=0, count=1, roles=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/types/qqmldelegatemodel.cpp:1144 #8 0x7f197995c34a in QQmlDelegateModel::_q_dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=, begin=..., end=..., roles=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/types/qqmldelegatemodel.cpp:1546 #9 0x7f197998386c in QQmlDelegateModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x5620fe240c40, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=12, _a=_a@entry=0x7fff34894d40) at .moc/moc_qqmldelegatemodel_p.cpp:203 #10 0x7f1979984058 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x5620fe240c40, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7fff34894d40) at .moc/moc_qqmldelegatemodel_p.cpp:344 #11 0x7f19757e2450 in QMetaObject::activate(QObject*, int, int, void**) (sender=0x5620fe3d7e90, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff34894d40) at kernel/qobject.cpp:3728 #12 0x7f19757e2a97 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f1975bf9600 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff34894d40) at kernel/qobject.cpp:3578 #13 0x7f197585eaac in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:548 #14 0x7f18b2b8928f in TaskManager::TasksModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (changes=..., this=0x5620fe3e63d0) at /usr/src/debug/plasma-workspace-5.5.4/libtaskmanager/tasksmodel.cpp:521 #15 0x7f18b2b8928f in TaskManager::TasksModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x5620fe3d7e90, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=9, _a=_a@entry=0x7fff34894ef0) at /usr/src/debug/plasma-workspace-5.5.4/x86_64-redhat-linux-gnu/libtaskmanager/moc_tasksmodel.cpp:214 #16 0x7f19757e229a in QMetaObject::activate(QObject*, int, int, void**) (sender=0x5620fecd7900, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff34894ef0) at kernel/qobject.cpp:3713 #17 0x7f19757e2a97 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f18b2daff60 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff34894ef0) at kernel/qobject.cpp:3578 #18 0x7f18b2b928e8 in TaskManager::AbstractGroupableItem::changed(QFlags) (this=, _t1=...) at /usr/src/debug/plasma-workspace-5.5.4/x86_64-redhat-linux-gnu/libtaskmanager/moc_abstractgroupableitem.cpp:223 #19 0x7f18b2b7b5b8 in TaskManager::TaskItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (change=..., this=) at /usr/src/debug/plasma-workspace-5.5.4/libtaskma
[skrooge] [Bug 358195] broken dependencies after KDE update
https://bugs.kde.org/show_bug.cgi?id=358195 --- Comment #7 from Max --- Thanks. It works now. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 358195] broken dependencies after KDE update
https://bugs.kde.org/show_bug.cgi?id=358195 --- Comment #4 from Max --- Yes, they updated Plasma and Applications yesterday and that's reprodusable once you you update from the repo... -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 358195] broken dependencies after KDE update
https://bugs.kde.org/show_bug.cgi?id=358195 --- Comment #1 from Max --- apt-cache search qtbase-abi gives me : libqt5core5a - Qt 5 core module -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 358195] New: broken dependencies after KDE update
https://bugs.kde.org/show_bug.cgi?id=358195 Bug ID: 358195 Summary: broken dependencies after KDE update Product: skrooge Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: max...@gmail.com CC: steph...@mankowski.fr After latest KDE update on Kubuntu I cant instal skrooge anymore (also skrooge was deinstalled during upgrade process). apt-get install skrooge-kf5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: skrooge-kf5 : Depends: qtbase-abi-5-4-2 Recommends: weboob but it is not going to be installed E: Unable to correct problems, you have held broken packages. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 357448] Amarok crashes when searching for tags on MusicBrainz
https://bugs.kde.org/show_bug.cgi?id=357448 --- Comment #1 from Max --- Created attachment 96430 --> https://bugs.kde.org/attachment.cgi?id=96430&action=edit New crash information added by DrKonqi amarok (2.8.0) on KDE Platform 4.14.9 using Qt 4.8.6 - What I was doing when the application crashed: Search tags wim Music Brantz 1st - normal 2 trying - crash -- Backtrace (Reduced): #5 0x7f73d498f611 in QReadWriteLock::lockForRead() () from /usr/lib64/libQtCore.so.4 [...] #8 0x7f73d554a5fb in QSortFilterProxyModel::flags(QModelIndex const&) const () from /usr/lib64/libQtGui.so.4 #9 0x7f73d550a471 in QTreeView::drawRow(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /usr/lib64/libQtGui.so.4 #10 0x7f73d550d562 in QTreeView::drawTree(QPainter*, QRegion const&) const () from /usr/lib64/libQtGui.so.4 #11 0x7f73d5510d0c in QTreeView::paintEvent(QPaintEvent*) () from /usr/lib64/libQtGui.so.4 --- Comment #2 from Max --- Created attachment 96432 --> https://bugs.kde.org/attachment.cgi?id=96432&action=edit New crash information added by DrKonqi amarok (2.8.0) on KDE Platform 4.14.9 using Qt 4.8.6 - What I was doing when the application crashed: Search tags wim Music Brantz 1st - normal 2 trying - crash -- Backtrace (Reduced): #5 0x7f73d498f611 in QReadWriteLock::lockForRead() () from /usr/lib64/libQtCore.so.4 [...] #8 0x7f73d554a5fb in QSortFilterProxyModel::flags(QModelIndex const&) const () from /usr/lib64/libQtGui.so.4 #9 0x7f73d550a471 in QTreeView::drawRow(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /usr/lib64/libQtGui.so.4 #10 0x7f73d550d562 in QTreeView::drawTree(QPainter*, QRegion const&) const () from /usr/lib64/libQtGui.so.4 #11 0x7f73d5510d0c in QTreeView::paintEvent(QPaintEvent*) () from /usr/lib64/libQtGui.so.4 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 357448] Amarok crashes when searching for tags on MusicBrainz
https://bugs.kde.org/show_bug.cgi?id=357448 Max changed: What|Removed |Added CC||dog.mi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 357448] Amarok crashes when searching for tags on MusicBrainz
https://bugs.kde.org/show_bug.cgi?id=357448 --- Comment #1 from Max --- Created attachment 96430 --> https://bugs.kde.org/attachment.cgi?id=96430&action=edit New crash information added by DrKonqi amarok (2.8.0) on KDE Platform 4.14.9 using Qt 4.8.6 - What I was doing when the application crashed: Search tags wim Music Brantz 1st - normal 2 trying - crash -- Backtrace (Reduced): #5 0x7f73d498f611 in QReadWriteLock::lockForRead() () from /usr/lib64/libQtCore.so.4 [...] #8 0x7f73d554a5fb in QSortFilterProxyModel::flags(QModelIndex const&) const () from /usr/lib64/libQtGui.so.4 #9 0x7f73d550a471 in QTreeView::drawRow(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /usr/lib64/libQtGui.so.4 #10 0x7f73d550d562 in QTreeView::drawTree(QPainter*, QRegion const&) const () from /usr/lib64/libQtGui.so.4 #11 0x7f73d5510d0c in QTreeView::paintEvent(QPaintEvent*) () from /usr/lib64/libQtGui.so.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356983] New: Audio and removable device applets in system tray disappear after plasma restart
https://bugs.kde.org/show_bug.cgi?id=356983 Bug ID: 356983 Summary: Audio and removable device applets in system tray disappear after plasma restart Product: plasmashell Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: thesource...@gmail.com When plasma is restarted (either by logout or if it crashed for some reason) audio and removable device applets in system tray start to behave strangely: removable device icon (assuming at least one removable device is attached when plasma is restarted so icon is active before restart) disappears right after restart, audio control icon sometimes disappear immediately too, sometimes it stays for several minutes and then vanish. It's not just icon image disappear because clicking on the place where it was does nothing. I can restore those icons by disabling them and then enabling again in tray settings. I noticed that before audio icon vanish tray arranges icons improperly: rows in tray are not even (upper row 2 icons larger than lower one). Reproducible: Always Steps to Reproduce: 1.Enable audio and removable device applets in system tray settings 2.Logout and log back in or kill plasmashell 3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356982] New: Plasma crash when connectiog to mobile broadband
https://bugs.kde.org/show_bug.cgi?id=356982 Bug ID: 356982 Summary: Plasma crash when connectiog to mobile broadband Product: plasmashell Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: thesource...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.0) Qt Version: 5.5.1 Operating System: Linux 4.2.8-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: Plasma often crashes when I press connect button in plasma network applet on mobile broadband connection (the connection itself gets established though). Crash also happens when activating mobile connection in connection editor (again, often but not always). Crash seem to only affect mobile connections, never happens on wired ones. I read about similar bug here and the bug was in Qt before 5.4.2, but I have Qt 5.5.1 installed and crash still happens, so I guess it might be different bug. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f3f3de51940 (LWP 5822))] Thread 8 (Thread 0x7f3f171cd700 (LWP 5844)): #0 0x7f3f3584fffd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3f30d7816c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f3f30d7827c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f3f3668ff0b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f3f18c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f3f36636f0a in QEventLoop::exec(QFlags) (this=this@entry=0x7f3f171ccc60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f3f36453424 in QThread::exec() (this=this@entry=0x558bc04bcae0) at thread/qthread.cpp:503 #6 0x7f3f3a79db45 in QQmlThreadPrivate::run() (this=0x558bc04bcae0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7f3f364583ce in QThreadPrivate::start(void*) (arg=0x558bc04bcae0) at thread/qthread_unix.cpp:331 #8 0x7f3f34b9360a in start_thread (arg=0x7f3f171cd700) at pthread_create.c:334 #9 0x7f3f3585ba9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f3f0a305700 (LWP 5861)): #0 0x7f3f30dbc734 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f3f30d77700 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f3f30d7809b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f3f30d7827c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f3f3668ff0b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f3f040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f3f36636f0a in QEventLoop::exec(QFlags) (this=this@entry=0x7f3f0a304c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f3f36453424 in QThread::exec() (this=this@entry=0x558bc08b1bc0) at thread/qthread.cpp:503 #7 0x7f3f3a79db45 in QQmlThreadPrivate::run() (this=0x558bc08b1bc0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x7f3f364583ce in QThreadPrivate::start(void*) (arg=0x558bc08b1bc0) at thread/qthread_unix.cpp:331 #9 0x7f3f34b9360a in start_thread (arg=0x7f3f0a305700) at pthread_create.c:334 #10 0x7f3f3585ba9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f3f03fff700 (LWP 5870)): #0 0x7f3f3584bbdd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3f30dbb390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f3f30d77c64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f3f30d78110 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f3f30d7827c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f3f3668ff0b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f3efc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f3f36636f0a in QEventLoop::exec(QFlags) (this=this@entry=0x7f3f03ffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f3f36453424 in QThread::exec() (this=this@entry=0x558bc07f66c0) at thread/qthread.cpp:503 #8 0x7f3f3a79db45 in QQmlThreadPrivate::run() (this=0x558bc07f66c0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #9 0x7f3f364583ce in QThreadPrivate::start(void*) (arg=0x558bc07f66c0) at thread/qthread_unix.cpp:331 #10 0x7f3f34b9360a in start_thread (arg=0x7f3f03fff700) at pthread_create.c:334 #11 0x7f3f
[dolphin] [Bug 356163] Dolphin crashes when right-clicking a file
https://bugs.kde.org/show_bug.cgi?id=356163 Max changed: What|Removed |Added CC||m...@winsoft.hu --- Comment #3 from Max --- I get this a lot also, with Kubuntu 15.10 Seems to always happen with right-clicking on a .png file saved in the Home directory, and trying "Open With..." (I have Pinta installed, and like to open with Pinta for editing) If I move the png file to the Home/Pictures folder, then the same issue no longer occurs. So- could be a settings issue around file types (to do with auto-preview perhaps) in certain folders? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356830] New: Invalid location in location bar (button mode) when browsing FTP
https://bugs.kde.org/show_bug.cgi?id=356830 Bug ID: 356830 Summary: Invalid location in location bar (button mode) when browsing FTP Product: dolphin Version: 15.08.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: thesource...@gmail.com When I descend into directory tree of FTP server, all entries in location bar after server name become the same and display the name of current folder, so if I'm in myproject/images, location bar displays images / images. Pressing any of those entries does nothing. This only happens in "button" mode of the bar. If I click aside of location buttons to switch to string mode, than the location is displayed properly. Reproducible: Always Steps to Reproduce: 1. Logon to any FTP server 2. Descend at least 2 directories down the tree 3. Actual Results: All buttons on location bar display same names, clicking on them does nothing. Expected Results: Buttons should properly display names of all folders in current tree branch, clicking on the button should change directory. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 343665] Standard shortcuts for applications with same assignment on standard and alternative give error message being ambiguous in applications (e.g. Kate)
https://bugs.kde.org/show_bug.cgi?id=343665 --- Comment #54 from Max --- I also am still having a problem for last 10 months. Have tried all of the proposed patches here, and only that really solves the problem for me is (ugly) one i made and explained in Comment 5. Does anyone knows what is actually appending those default shortcuts to the list? -- You are receiving this mail because: You are watching all bug changes.
