[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 Arthur c changed: What|Removed |Added CC||clement.art...@gmail.com --- Comment #1 from Arthur c --- I have exactly the same problem since yesterday on two PCs with the last KDE update (Fedora 23), but I have 5.5.0 packages : plasma-desktop-5.5.0-4.fc23.x86_64 kdeplasma-addons-5.5.0-2.fc23.x86_64 plasma-workspace-geolocation-5.5.0-2.fc23.x86_64 plasma-workspace-drkonqi-5.5.0-2.fc23.x86_64 plasma-pa-5.5.0-1.fc23.x86_64 plasma-systemsettings-5.5.0-1.fc23.x86_64 plasma-nm-openconnect-5.5.0-1.fc23.x86_64 plasma-nm-5.5.0-1.fc23.x86_64 plasma-milou-5.5.0-1.fc23.x86_64 plasma-workspace-libs-5.5.0-2.fc23.x86_64 plasma-desktop-doc-5.5.0-4.fc23.noarch plasma-nm-pptp-5.5.0-1.fc23.x86_64 kf5-plasma-5.16.0-4.fc23.x86_64 plasma-breeze-5.5.0-1.fc23.x86_64 plasma-nm-openvpn-5.5.0-1.fc23.x86_64 plasma-pk-updates-0.2-5.fc23.x86_64 plasma-workspace-common-5.5.0-2.fc23.x86_64 plasma-nm-l2tp-5.5.0-1.fc23.x86_64 kde-settings-plasma-23-8.fc23.noarch plasma-nm-vpnc-5.5.0-1.fc23.x86_64 plasma-breeze-common-5.5.0-1.fc23.noarch plasma-nm-openswan-5.5.0-1.fc23.x86_64 plasma-workspace-geolocation-libs-5.5.0-2.fc23.x86_64 plasma-workspace-5.5.0-2.fc23.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356428] Plasmashell crash when minimizing app and then hovering mouse over taskmanager
https://bugs.kde.org/show_bug.cgi?id=356428 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Resolution|BACKTRACE |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #6 from Kai Uwe Broulik --- Thanks. For some reason it's trying to create an applet whose Plugin info is invalid. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 354585] IPv6 connections to https://dot.kde.org fail
https://bugs.kde.org/show_bug.cgi?id=354585 --- Comment #8 from Ben Cooksley --- You could try artifically restraining your MTU, we're working with the provider on a fix though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 353428] KWin freezes until drkonqi is closed from a terminal
https://bugs.kde.org/show_bug.cgi?id=353428 --- Comment #28 from Thomas Lübking --- The inability to switch to another VT means a problem in the kernel (at least framebuffer control) Nobody said this is fixed and I assume you hit this on "your" account because of some config there crashes kwin itfp (auorae decoration?, there're plenty of bug reports on the QML V4 engine) See comment #14 - unfortunately releasing the WM selection w/o calling into the xcb connection is a bit "tricky" ;-) (comment #15) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 344567] Cannot create a new session
https://bugs.kde.org/show_bug.cgi?id=344567 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #5 from Kai Uwe Broulik --- The output doesn't show anything unusual. Does it work when you start a new session from kickoff or the new user switcher plasmoid? However, they all use KDisplayManager which is pretty old, so most likely something in your setup that breaks it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 --- Comment #2 from Arthur c --- the bug seems to never happen on the active window, we can minimize/maximize from the taskbar without problem. It's a problem when we change the focus : Scenario : Application 1 active : taskbar highlighted Cursor on the taskbar of the minimized application 2 : light highlight Click on the taskbar of the minimized application 2 : the light highlight/focus disappear. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 Christian Degenkolb changed: What|Removed |Added CC||degenk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356649] use-after-free crash on closing ark on previewing an archive
https://bugs.kde.org/show_bug.cgi?id=356649 --- Comment #4 from Santhiar --- I have posted the backtrace again. Please also refer to the backtrace provided by AddressSanitizer that I have posted at the bottom of the original report - AddressSanitizer reports the first problematic memory access, along with stacks the allocation and free sites of that memory. Application: Ark (ark), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7faf45e3f780 (LWP 24731))] Thread 2 (Thread 0x7faf303ad700 (LWP 24734)): #0 0x7faf3ec6a4ac in send () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7faf3ec65020 in __vsyslog_chk () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7faf3ec653af in syslog () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x7faf3f7e5c93 in QMutex::lock (this=0xe88670) at thread/qmutex.cpp:180 #4 0x7faf3f7c4645 in QMutex::lockInline (this=0xe88670) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:201 #5 0x7faf3f7c16c0 in QMutexLocker::QMutexLocker (this=0x7faf303aca20, m=0xe88670) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:109 #6 0x7faf3f9c6e54 in QThreadData::canWaitLocked (this=0xe88620) at ../../include/QtCore/private/../../../src/corelib/thread/qthread_p.h:236 #7 0x7faf3f9ca30b in QEventDispatcherUNIX::processEvents (this=0x7faf280008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:911 #8 0x7faf3f972f6c in QEventLoop::processEvents (this=0x7faf303acc78, flags=...) at kernel/qeventloop.cpp:149 #9 0x7faf3f973332 in QEventLoop::exec (this=0x7faf303acc78, flags=...) at kernel/qeventloop.cpp:225 #10 0x7faf3f7eb0a0 in QThread::exec (this=0xd938b0) at thread/qthread.cpp:659 #11 0x7faf3f942994 in QInotifyFileSystemWatcherEngine::run (this=0xd938b0) at io/qfilesystemwatcher_inotify.cpp:265 #12 0x7faf3f7efb2a in QThreadPrivate::start (arg=0xd938b0) at thread/qthread_unix.cpp:361 #13 0x7faf45640e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #14 0x7faf3ec6938d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #15 0x in ?? () Thread 1 (Thread 0x7faf45e3f780 (LWP 24731)): [KCrash Handler] #6 QWidget::windowType (this=0x41) at qt/src/gui/../../include/QtGui/../../src/gui/kernel/qwidget.h:938 #7 0x7faf413d46e5 in QWidget::isWindow (this=0x41) at qt/src/gui/../../include/QtGui/../../src/gui/kernel/qwidget.h:946 #8 0x7faf414441eb in QWidgetPrivate::setEnabled_helper (this=0xce9cb0, enable=true) at kernel/qwidget.cpp:3386 #9 0x7faf4144419d in QWidget::setEnabled (this=0xc6bda0, enable=true) at kernel/qwidget.cpp:3379 #10 0x7faf352b79ef in Ark::Part::setReadyGui (this=0xb6a690) at KDE/kde/kdeutils/ark/part/part.cpp:530 #11 0x7faf352b86fc in Ark::Part::slotPreviewExtracted (this=0xb6a690, job=) at KDE/kde/kdeutils/ark/part/part.cpp:620 #12 0x7faf352ad9c0 in Ark::Part::qt_static_metacall (_o=0xb6a690, _c=, _id=, _a=0x7faf20001930) at KDE/build/kde/kdeutils/ark/part/moc_part.cpp:106 #13 0x7faf3f99669d in QMetaCallEvent::placeMetaCall (this=0x7faf20001970, object=0xb6a690) at kernel/qobject.cpp:524 #14 0x7faf3f998a10 in QObject::event (this=0xb6a690, e=0x7faf20001970) at kernel/qobject.cpp:1222 #15 0x7faf413ca48f in QApplicationPrivate::notify_helper (this=0xa440f0, receiver=0xb6a690, e=0x7faf20001970) at kernel/qapplication.cpp:4565 #16 0x7faf413cca8e in QApplication::notify (this=0x7321ce68, receiver=0xb6a690, e=0x7faf20001970) at kernel/qapplication.cpp:3947 #17 0x7faf4276df7b in KApplication::notify (this=0x7321ce68, receiver=0xb6a690, event=0x7faf20001970) at KDE/kde/kdelibs/kdeui/kernel/kapplication.cpp:311 #18 0x7faf3f977dc6 in QCoreApplication::notifyInternal (this=0x7321ce68, receiver=0xb6a690, event=0x7faf20001970) at kernel/qcoreapplication.cpp:955 #19 0x7faf3f97c54a in QCoreApplication::sendEvent (receiver=0xb6a690, event=0x7faf20001970) at qt/src/corelib/../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #20 0x7faf3f9793f4 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xa154e0) at kernel/qcoreapplication.cpp:1609 #21 0x7faf3f978338 in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1477 #22 0x7faf414d1b48 in QCoreApplication::sendPostedEvents () at qt/src/gui/../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #23 0x7faf414e2082 in QEventDispatcherX11::processEvents (this=0xa1cbc0, flags=...) at kernel/qeventdispatcher_x11.cpp:82 #24 0x7faf3f972f6c in QEventLoop::processEvents (this=0x7321cc30, flags=...) at kernel/qeventloop.cpp:149 #25 0x7faf3f973332 in QEventLoop::exec (this=0x7321cc30, flags=...) at kernel/qeventloop.cpp:225 #26 0x7faf3f9785ee in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #27 0x7faf413cc526 in QApplication::exec () at kernel/qapplication.cpp:3823 #28 0x00
[kscreenlocker] [Bug 356757] hang if "New Session" is choosen
https://bugs.kde.org/show_bug.cgi?id=356757 --- Comment #2 from bifr...@hotmail.it --- Where should I report the bug? Main kernel development, xorg, or there is something for radeon driver(I can't find anything). On 16 December 2015 08:20:28 CET, "Martin Gräßlin via KDE Bugzilla " wrote: >https://bugs.kde.org/show_bug.cgi?id=356757 > >Martin Gräßlin changed: > > What|Removed |Added > > CC||k...@privat.broulik.de > >--- Comment #1 from Martin Gräßlin --- >Sorry, I fear there is not much we can do about it. The actual crash is >in the >kernel driver and needs to be fixed there. We cannot (and should not) >workaround such problems in the user facing code. > >-- >You are receiving this mail because: >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356768] New: Separators are hardly visible and creates not so nice UI
https://bugs.kde.org/show_bug.cgi?id=356768 Bug ID: 356768 Summary: Separators are hardly visible and creates not so nice UI Product: Breeze Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: QStyle Assignee: hugo.pere...@free.fr Reporter: aman...@kde.org The horizontal separator in KMail is not visible, so it is hard to grab and it does not act as a divider between message list and message content, see the attached image. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356768] Separators are hardly visible and creates not so nice UI
https://bugs.kde.org/show_bug.cgi?id=356768 --- Comment #1 from András Manţia --- Created attachment 96119 --> https://bugs.kde.org/attachment.cgi?id=96119&action=edit Screenshot with the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 353428] KWin freezes until drkonqi is closed from a terminal
https://bugs.kde.org/show_bug.cgi?id=353428 Bert Zimpel changed: What|Removed |Added CC||b...@grupo-samadhi.net --- Comment #29 from Bert Zimpel --- Hallo Robin, thank you for your comment! > I usually use F5 out of years of habit. I hope your comment is a typo. (In > reply to Robin Laing from comment #27) Fx represents F1 to F6, the available terminal screens at my system. Hopes that helps to clarify the "typo". Bert -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356769] New: Baloo crashes when database locks are held
https://bugs.kde.org/show_bug.cgi?id=356769 Bug ID: 356769 Summary: Baloo crashes when database locks are held Product: Baloo Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: olaf.the.lost.vik...@gmail.com CC: pinak.ah...@gmail.com [This report applies to ballo 5.17.0 which isn't selectable in the Version drop down above.] After my obligatory "akonadictl restart" after suspend, starting the baloo_indexer lead to crashes since the baloo-database for emails was still locked. The culprit as a baloo indexer process from yesterday that wasn't stopped by akonadictl (another bug?). After killing that process manually the new could start. A dialog telling the user why it has problems starting seems more graceful than just crashing ;-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355935] Font kerning is incorrect
https://bugs.kde.org/show_bug.cgi?id=355935 beojan changed: What|Removed |Added Version|5.4.3 |5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355935] Font kerning is incorrect
https://bugs.kde.org/show_bug.cgi?id=355935 --- Comment #4 from beojan --- Changing the font in system settings appears to fix this until Plasma is restarted. Note: By this I mean changing the font to a different font, then back to the original, so the bug is not in the font. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351425] Make the "windows" in taskbar smaller
https://bugs.kde.org/show_bug.cgi?id=351425 jeremy9...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #25 from jeremy9...@gmail.com --- With Plasma 5.5.1 and KF 5.17 the size of the window is about 250px on Manjaro and I think it's a good compromise. Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 356757] hang if "New Session" is choosen
https://bugs.kde.org/show_bug.cgi?id=356757 --- Comment #3 from Martin Gräßlin --- That's a good question and I don't really know the answer to it. Given the stack trace I'd say radeon_drm. IIRC thats on bugs.freedesktop.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 355198] Feature: Navigation through Mails using Arrow Keys
https://bugs.kde.org/show_bug.cgi?id=355198 --- Comment #3 from OlafLostViking --- In my case: The Archlinux package version is 15.08.3-2 (amd64). The About dialog says 5.0.3, using frameworks 5.17.0 and Qt 5.5.1. -- 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 tos...@tosick.net changed: What|Removed |Added CC|tos...@tosick.net | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 353428] KWin freezes until drkonqi is closed from a terminal
https://bugs.kde.org/show_bug.cgi?id=353428 --- Comment #30 from Bert Zimpel --- (In reply to Thomas Lübking from comment #28) > The inability to switch to another VT means a problem in the kernel (at > least framebuffer control) Hallo Thjomas, partially right, however the freeze and subsequently the inability to change to a terminal window does +not+ occur in Xfce (alternative Windows Manager). I had to change to Xfce as the KDE system tends to freeze always at the worst point (when files are "open") in a productive process. Bert -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 m...@honovere.de changed: What|Removed |Added CC||m...@honovere.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356740] Kwin crash if I set brightness while in kodi
https://bugs.kde.org/show_bug.cgi?id=356740 --- Comment #5 from Côme Chilliet --- There is a qt5/plasma update available, I’ll give more information after the update is done and I try again. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 352619] update fails: An error occured while applying changes
https://bugs.kde.org/show_bug.cgi?id=352619 Seppo changed: What|Removed |Added CC||seppo0...@gmail.com --- Comment #3 from Seppo --- Created attachment 96120 --> https://bugs.kde.org/attachment.cgi?id=96120&action=edit Picture of error message window -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 352619] update fails: An error occured while applying changes
https://bugs.kde.org/show_bug.cgi?id=352619 --- Comment #4 from Seppo --- Created attachment 96121 --> https://bugs.kde.org/attachment.cgi?id=96121&action=edit Terminal printout of upgrade -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window
https://bugs.kde.org/show_bug.cgi?id=355275 Dmitry changed: What|Removed |Added CC||ivad...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 352619] update fails: An error occured while applying changes
https://bugs.kde.org/show_bug.cgi?id=352619 --- Comment #5 from Seppo --- I have 2 Kubuntu machines, up to date version 15.10. Both has same error (see attached picture) every time they are updated with Muon, or if I try to install or remove packages with Muon Discover. The error message is always the same. Muon ver: 5.4.2 I run upgrade also from treminal. Listing of the terminal printout is attached. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 352097] Dolphin Version 15.08.0 trash strange behavior after deleting files.
https://bugs.kde.org/show_bug.cgi?id=352097 Zoran Dimovski changed: What|Removed |Added CC||zoki.dimov...@gmail.com --- Comment #9 from Zoran Dimovski --- I confirm this bug on multiple machines with different versions of the Plasma desktop. Every time I invoke "Empty trash" either from Dolphin or from the trash widget on the panel, the files trash.so and file.so are still opened (and their number is growing if you use "empty trash" more often). Sometimes, even Dolphin is not closing properly (you can see the Dolphin process but Dolphin is not running in your desktop). The only use case that this is not happening if you just don't use "empty trash" but delete the files from trash with regular delete function. After deleting the files manually, Dolphin _always_ exits properly and there are no more trash.so and file.so. Also, the icon stays red until you open Dolphin again. I've been testing this on plasma 5.4 till 5.5.1 KDE Plasma Version: 5.5.1 KDE Frameworks: 5.17 KDE Applications: 15.08.3 QT Version: 5.5.1 Best regards. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3
https://bugs.kde.org/show_bug.cgi?id=353203 --- Comment #43 from Mister Ypsilon --- After upgrading Frameworks to version 5.17, the problem went away for me. Login is super fast now, like 3-5 seconds. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window
https://bugs.kde.org/show_bug.cgi?id=355275 --- Comment #40 from Dmitry --- Created attachment 96122 --> https://bugs.kde.org/attachment.cgi?id=96122&action=edit New crash information added by DrKonqi kopete (1.7.3) on KDE Platform 4.14.14 using Qt 4.8.7 - What I was doing when the application crashed: I've been closing a chat window. It seems that app crashes after closing any window. -- Backtrace (Reduced): #7 0x7f8802e46a75 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQtCore.so.4 #8 0x7f87fb5eb4a9 in KParts::PartManager::~PartManager() () from /usr/lib/libkparts.so.4 #9 0x7f87fb5eb679 in KParts::PartManager::~PartManager() () from /usr/lib/libkparts.so.4 #10 0x7f8802e498b1 in QObjectPrivate::deleteChildren() () from /usr/lib/libQtCore.so.4 #11 0x7f8802e4bf54 in QObject::~QObject() () from /usr/lib/libQtCore.so.4 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356242] Aplication Launcher causes Plasma Shell to crash when searching or viewing history tab [QSQLiteDriver::QSQLiteDriver | QSQLiteDriverPlugin::create | QSqlDatabaseP
https://bugs.kde.org/show_bug.cgi?id=356242 PLX changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from PLX --- Thanks. it seems then to be a distro specific issue. I've created a bug report in Mageia's bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 --- Comment #35 from m...@honovere.de --- This bug is not fixed for me: Debian GNU/Linux 8.2 (jessie, stable), kontact 4.14.1, davfs2 1.5.2. Calender is hosted on a Synology DS215+ and works great with thunderbird and davdroid 0.9.1.2. Events created with Kontact were named like "1456278525.R86.ics" (each event one *.ics file) and are visible and synced with thunderbird and davdroid. If I delete the *.ics files on the webdav and sync again, the events are no longer visible with davdroid and thunderbird (like expected) but Kontact keeps these events for ever! Changes made via davdroid/thunderbird are not visible in Kontact. Please fix it! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356770] New: Confirmation if filename is changed to begin with a dot (= hidden file)
https://bugs.kde.org/show_bug.cgi?id=356770 Bug ID: 356770 Summary: Confirmation if filename is changed to begin with a dot (= hidden file) Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: matti.kettu...@gmail.com If user is not familiar with hidden files he/she can accidentially hide a file by changing the filename. Reproducible: Always Steps to Reproduce: 1. Activate file and press F2 to rename it 2. Press delete or backspace 3. Press enter Actual Results: File will be renamed with it's extension only. For example file.pdf -> .pdf Because new filename begins with a dot it will be hidden. Expected Results: Dolphin should ask for confirmation if user is changing filename so that the file will be hidden. Confirmation should be asked because most of the "normal" computer users are not familiar with hidden files and they might think that the file was accidentally deleted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 Eduard Valiauka changed: What|Removed |Added CC||nsbm.abb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 355616] Generated python code does not have attributes or a constructor
https://bugs.kde.org/show_bug.cgi?id=355616 Felix Zesch changed: What|Removed |Added CC||xelzife...@web.de --- Comment #1 from Felix Zesch --- I can confirm this behaviour. The software is not usable for Python developers right now, unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355592] Thumbnail icons in folder view layout desktop have wrong fixed 1:1 aspect ratio
https://bugs.kde.org/show_bug.cgi?id=355592 --- Comment #3 from garwol --- Created attachment 96123 --> https://bugs.kde.org/attachment.cgi?id=96123&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355592] Thumbnail icons in folder view layout desktop have wrong fixed 1:1 aspect ratio
https://bugs.kde.org/show_bug.cgi?id=355592 --- Comment #4 from garwol --- plasma 5.5.1 - icons still stretched -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356589] Can not trash files or folders from trash widget / delete key
https://bugs.kde.org/show_bug.cgi?id=356589 William Termini changed: What|Removed |Added Summary|Can not delete files or |Can not trash files or |folders from trash widget / |folders from trash widget / |delete key |delete key -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356082] Icon for save session is missing
https://bugs.kde.org/show_bug.cgi?id=356082 Ömer changed: What|Removed |Added Version|5.4.95 |5.5.1 --- Comment #6 from Ömer --- seems like it is missing with oxygen to http://imgur.com/e4f3s92. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356768] Separators are hardly visible and creates not so nice UI
https://bugs.kde.org/show_bug.cgi?id=356768 Hugo Pereira Da Costa changed: What|Removed |Added CC||hugo.pere...@free.fr --- Comment #2 from Hugo Pereira Da Costa --- Hi Thanks for reporting ! In general splitter have been rendered as "invisible" in breeze to unclutter the UI. The existence of the splitter being hinted only by the change of cursor when you mouse over it. Now I do agree that it looks somewhat awkward in the screenshot. Before I look for a solution, could you post screenshots on how it look with other styles ? (e.g. oxygen, fusion -if it is Qt5, or plastique -if it is Qt4) ? thanks in advance, Hugo -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355711] System Settings crashed during exit processing.
https://bugs.kde.org/show_bug.cgi?id=355711 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356589] Can not trash files or folders from trash widget / delete key
https://bugs.kde.org/show_bug.cgi?id=356589 --- Comment #3 from William Termini --- Just a follow up, after a day of sitting at my computer. I went back to deleting files on my desktop as part of a clean up. After deleting a dozen icons or so (my desktop folders a mess). Suddenly I was unable to move items to the trash with the delete key has had been just a few minutes before hand. I checked my .xsession-errors this time. Every time I press delete or drag a file to the trash widget (although I discovered if you have confirmations on this will cause plasma to segfault) I get what you see bellow. file:///usr/share/plasma/plasmoids/org.kde.ktp-contactlist/contents/ui/main.qml: QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling. file:///usr/share/plasma/plasmoids/org.kde.ktp-contactlist/contents/ui/main.qml: QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling. file:///usr/share/plasma/plasmoids/org.kde.ktp-contactlist/contents/ui/main.qml: QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling. file:///usr/share/plasma/plasmoids/org.kde.ktp-contactlist/contents/ui/main.qml: QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling. This happens when I stop the notification that never goes away Trying to perform the action "stop" qml: totalCountChanged 0 file:///usr/share/plasma/plasmoids/org.kde.ktp-contactlist/contents/ui/main.qml: QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling. file:///usr/share/plasma/plasmoids/org.kde.ktp-contactlist/contents/ui/main.qml: QML Plasmoid: Cannot anchor to an item that isn't a parent or sibling. I checked .xsession-errors on a system that did not start doing this yet, and the only output is this when I try to move a file to the trash finalDestUrl= "trash:/0-New Folder (1)" Restarting Plasma Causes the issue to go away. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 354201] Wireless icon when not connected to any wireless network is same as when connectected to one
https://bugs.kde.org/show_bug.cgi?id=354201 Jan Grulich changed: What|Removed |Added Resolution|FIXED |WONTFIX Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 356755] detaching-member: don't warn when begin()/end() used in qSort
https://bugs.kde.org/show_bug.cgi?id=356755 Sergio Martins changed: What|Removed |Added Ever confirmed|0 |1 Assignee|unassigned-b...@kde.org |smart...@kde.org Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 353783] baloo crash in mdb_dbi_open
https://bugs.kde.org/show_bug.cgi?id=353783 --- Comment #10 from Loïc Yhuel --- Even if the crashes seems to have stopped in 5.17, I think parts of my patch still applies : - Database::open isn't threadsafe - if mdb_env_open fails, m_env is leaked (see mdb_env_open documentation) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356771] New: System settings always crashes on closing
https://bugs.kde.org/show_bug.cgi?id=356771 Bug ID: 356771 Summary: System settings always crashes on closing Product: systemsettings Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andy.gura...@gmail.com Application: systemsettings5 (5.5.1) Qt Version: 5.5.1 Operating System: Linux 4.2.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Every time I change any option in system settings, click "apply" and then close the window, I see the new window with crash report The crash can be reproduced every time. -- Backtrace: Application: Системні параметри (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f97c3f5c800 (LWP 10815))] Thread 4 (Thread 0x7f97b20d1700 (LWP 10816)): #0 0x7f97c05ed18d in poll () from /usr/lib/libc.so.6 #1 0x7f97be2aeae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f97be2b0757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f97b39fc379 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f97c0cd8b8e in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f97bda2d4a4 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f97c05f613d in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f97a179c700 (LWP 10818)): #0 0x7f97bda33ec3 in pthread_getspecific () from /usr/lib/libpthread.so.0 #1 0x7f97bd536bc0 in g_thread_self () from /usr/lib/libglib-2.0.so.0 #2 0x7f97bd50ef3c in g_main_context_acquire () from /usr/lib/libglib-2.0.so.0 #3 0x7f97bd50fe75 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f97bd5100cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f97c0f1056b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f97c0eb757a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f97c0cd3be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f97bf64b055 in ?? () from /usr/lib/libQt5Qml.so.5 #9 0x7f97c0cd8b8e in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f97bda2d4a4 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f97c05f613d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f979a490700 (LWP 10820)): #0 0x7f97c05ed18d in poll () from /usr/lib/libc.so.6 #1 0x7f97bd50ffbc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f97bd5100cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f97c0f1056b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f97c0eb757a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f97c0cd3be4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f97bf64b055 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7f97c0cd8b8e in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f97bda2d4a4 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f97c05f613d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f97c3f5c800 (LWP 10815)): [KCrash Handler] #5 0x7f97c0eec8e7 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5 #6 0x7f97a4109989 in KParts::PartManager::~PartManager() () from /usr/lib/libKF5Parts.so.5 #7 0x7f97a4109c49 in KParts::PartManager::~PartManager() () from /usr/lib/libKF5Parts.so.5 #8 0x7f97c0ee684b in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #9 0x7f97c0ef05d0 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #10 0x7f97a485f55b in KHTMLPart::~KHTMLPart() () from /usr/lib/libKF5KHtml.so.5 #11 0x7f97a485f679 in KHTMLPart::~KHTMLPart() () from /usr/lib/libKF5KHtml.so.5 #12 0x7f97c0ee9200 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #13 0x7f97c23c09ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f97c23c5e86 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f97c0eb9bab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #16 0x7f97c0ebbfa6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #17 0x7f97c0f10143 in ?? () from /usr/lib/libQt5Core.so.5 #18 0x7f97bd50fdc7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x7f97bd510020 in ?? () from /usr/lib/libglib-2.0.so.0 #20 0x7f97bd5100cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x7f97c0f1054f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #22 0x7f97c0eb757a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5
[plasma-nm] [Bug 356772] New: "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 Bug ID: 356772 Summary: "connect" does not work for mobile broadband connection Product: plasma-nm Version: 5.5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: st.va...@web.de CC: lu...@kde.org I have a HUAWEI mobile broadband USB surf stick. When plugged in, it shows correctly up in th nm-applet, but hitting the "connect" buttom, nothing happens. However, I can connect using the command line with nmcli -p con up "connection name", and then disconnect using the applet. Reproducible: Always Steps to Reproduce: 1. Plugin surf stick and wait until it is recognized 2. Hit "connect" button in applet Actual Results: No connection is established. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356768] Separators are hardly visible and creates not so nice UI
https://bugs.kde.org/show_bug.cgi?id=356768 Paul changed: What|Removed |Added CC||pip@gmx.com --- Comment #3 from Paul --- (In reply to Hugo Pereira Da Costa from comment #2) > ... The existence of the splitter being hinted only by the change of > cursor when you mouse over it. Which, of course, presupposes one _knows_ the splitter is there. ;) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356768] Separators are hardly visible and creates not so nice UI
https://bugs.kde.org/show_bug.cgi?id=356768 --- Comment #4 from Hugo Pereira Da Costa --- (In reply to Paul from comment #3) > (In reply to Hugo Pereira Da Costa from comment #2) > > ... The existence of the splitter being hinted only by the change of > > cursor when you mouse over it. > > Which, of course, presupposes one _knows_ the splitter is there. ;) Sure. No objection against that :) But again, the idea behind is that: in general, you should not need the splitter: this should be the responsibility of the app to make sure that things are properly displayed and don't need resize. In the (hopefully rare) cases that interaction with the splitter is needed, then you would think that it is easy enough to figure that there is one here (if only because part of the content is chopped). Best example that comes to my mind is dolphin's side panel. Anyway: I am not saying that the situation is ideal, and cannot be improved, nor that you are wrong, I am just trying to motivate the decisions that were made so far ... -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356649] use-after-free crash on closing ark on previewing an archive
https://bugs.kde.org/show_bug.cgi?id=356649 --- Comment #5 from Elvis Angelaccio --- Yeah, your backtrace is different than mine. How exactly have you compiled Ark? From git or from a source tarball? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355711] System Settings crashed during exit processing.
https://bugs.kde.org/show_bug.cgi?id=355711 Jonathan Marten changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #7 from Jonathan Marten --- Note that the crash only happens in "Classic Tree View" mode. What seems to be happening is this: ClassicMode::initEvent() creates d->classicWidget, a QSplitter with no parent. KParts::PartManager::PartManager() is called for that splitter, which calls addManagedTopLevelWidget() for it. At this stage isTopLevel() for the splitter is true and so it is added to the d->m_managedTopLevelWidgets list. SettingsBase::changePlugin() adds the splitter to the stackedWidget, which takes ownership of the splitter. When systemsettings5 is closed, KParts::PartManager::removeManagedTopLevelWidget() is called by the destroyed() signal of the splitter. However, by this point isTopLevel() for the splitter is false (because it has been reparented above) and so it is not removed from d->m_managedTopLevelWidgets. KParts::PartManager::~PartManager() accesses the splitter, which has already been destroyed but still remains in d->m_managedTopLevelWidgets => crash. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #1 from Jan Grulich --- Weird, it works for me. Did it work before the update? Is there any attempt to activate the connection in NetworkManager log? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356768] Separators are hardly visible and creates not so nice UI
https://bugs.kde.org/show_bug.cgi?id=356768 --- Comment #5 from András Manţia --- For some reason I can't switch my KMail to Fusion or Oxygen style, and can't debug it right now. In general Oxygen in KDE4 was also bad with splitters in some apps they were really hard to grab. I'll come back later with screenshots. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356773] New: Keyboard: Modifier keys does not work with Space (AltGr, Shift and Shift + AltGr)
https://bugs.kde.org/show_bug.cgi?id=356773
Bug ID: 356773
Summary: Keyboard: Modifier keys does not work with Space
(AltGr, Shift and Shift + AltGr)
Product: plasmashell
Version: master
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: martin.lud...@outlook.com
CC: bhus...@gmail.com, plasma-b...@kde.org
I use a keyboard layout (bépo, an ergonomic layout adapted to French) that uses
modifier keys on Space key: AltGr + Space to type an underscore (Shift and
Shift + AltGr are also used for special spaces).
But since my update to Plasma5, it does not work anymore: regardless the
modifier keys, when I press the space bar, I always have a standard space.
Reproducible: Always
Steps to Reproduce:
1. Switch to a keyboard layout that uses modifier keys on Space key (like bépo)
2. Try to type an underscore (AltGr + Space)
Actual Results:
The typed character is a standard space.
Expected Results:
The typed character should be an underscore.
After searching a bit, I think this problem is that plasma manages the space
bar differently. Anyway, I checked the configuration of the keyboard layout and
it should work.
/usr/share/X11/xkb/symbols/fr:
[…]
xkb_symbols "bepo" {
[…]
key { [space, nobreakspace, underscore, U202F ] }; //normal,
Shift, AltGr, Shit + AlgGr
[…]
};
[…]
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 356773] Keyboard: Modifier keys does not work with Space (AltGr, Shift and Shift + AltGr)
https://bugs.kde.org/show_bug.cgi?id=356773 Martin Ludwag changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup
https://bugs.kde.org/show_bug.cgi?id=323230 Peter Hoeg changed: What|Removed |Added CC||peterh...@gmail.com --- Comment #35 from Peter Hoeg --- For me, this bug only triggers when the panel is placed between the monitors. If I move it from the right side of the left screen to the left side of left screen everything is OK. Same thing applies to the right monitor in the inverse. This is supposedly a limitation in X that requires panels to be flush against an absolute edge. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356774] New: unwanted dots on strokes (possibly just with stabilizer)
https://bugs.kde.org/show_bug.cgi?id=356774 Bug ID: 356774 Summary: unwanted dots on strokes (possibly just with stabilizer) Product: krita Version: 2.9.10 Platform: Windows CE URL: http://i.minus.com/izgbK8cCIJyF8.jpeg OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: kasiazl...@gmail.com It seems to be happening mainly with psd. There are times where i can't make a single stroke without getting a dot somewhere throughout making one. IT seemed to have gone away 2 updates ago but now it's back again. Reproducible: Always Steps to Reproduce: 1.open a psd file 2.select brush and stabilizer 3.draw away and wait for dots Actual Results: Dots appear on my strokes Expected Results: Just normal strokes without dots or any other glitches. -- 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 Pavel Nedrigailov changed: What|Removed |Added CC||pavel.n...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355396] dual monitor become single after reboot
https://bugs.kde.org/show_bug.cgi?id=355396 Tim changed: What|Removed |Added CC||noe@gmail.com --- Comment #1 from Tim --- Exactly the same problem. With 2 screens, at start, the configuration reseted switching from "extended" mode to "monitors show the same thing" mode. Not happen each time, but often. When I switch back in kscreen from "monitors show the same thing" to "extended mode" the configuration of the second screen is reestablished (panel, plasmoids...). Using Plasma 5.5 on openSUSE Leap 42.1. Best regards -- 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 #1 from Pavel Nedrigailov --- Created attachment 96124 --> https://bugs.kde.org/attachment.cgi?id=96124&action=edit New crash information added by DrKonqi krunner (0.1) using Qt 5.5.1 Same issue here. Baloo is turned off too (it isn't works as expected) -- Backtrace (Reduced): #5 0x7f64372cedc8 in mdb_txn_renew0 () at /lib64/liblmdb.so.0.0.0 #6 0x7f64372d0224 in mdb_txn_begin () at /lib64/liblmdb.so.0.0.0 #7 0x7f643795997e in Baloo::SearchStore::exec(Baloo::Term const&, unsigned int, int, bool) () at /lib64/libKF5Baloo.so.5 #8 0x7f6437942a02 in Baloo::Query::exec() () at /lib64/libKF5Baloo.so.5 #9 0x7f6437b6a210 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.
[krita] [Bug 356774] unwanted dots on strokes (possibly just with stabilizer)
https://bugs.kde.org/show_bug.cgi?id=356774 --- Comment #1 from Boudewijn Rempt --- Hi, Thanks for your report. I'm pretty sure it hasn't got anything to do with the format of the file, but it could be related to the stabilizer. However, the link to the image you added times out; could you add the image as an attachment to the bug? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356774] unwanted dots on strokes (possibly just with stabilizer)
https://bugs.kde.org/show_bug.cgi?id=356774 kasiazl...@gmail.com changed: What|Removed |Added URL|http://i.minus.com/izgbK8cC |http://minus.com/i/zgbK8cCI |IJyF8.jpeg |JyF8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356774] unwanted dots on strokes (possibly just with stabilizer)
https://bugs.kde.org/show_bug.cgi?id=356774 --- Comment #2 from kasiazl...@gmail.com --- I added image link instead of direct, maybe this will work Thanks On 16/12/2015 12:02, Boudewijn Rempt via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=356774 > > --- Comment #1 from Boudewijn Rempt --- > Hi, > > Thanks for your report. I'm pretty sure it hasn't got anything to do with the > format of the file, but it could be related to the stabilizer. However, the > link to the image you added times out; could you add the image as an > attachment > to the bug? Thanks! > -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 351393] support Ctrl+W in password field
https://bugs.kde.org/show_bug.cgi?id=351393 Martin Gräßlin changed: What|Removed |Added CC||ohy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 338828] plasma5/screenlocker/Items hidden due to scrolling not obvious
https://bugs.kde.org/show_bug.cgi?id=338828 Martin Gräßlin changed: What|Removed |Added CC||ohy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 336369] Lock screen: suspend option is missing
https://bugs.kde.org/show_bug.cgi?id=336369 Martin Gräßlin changed: What|Removed |Added CC||ohy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 294778] unlock screen should show system name
https://bugs.kde.org/show_bug.cgi?id=294778 Martin Gräßlin changed: What|Removed |Added CC||ohy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 353855] Media controls should be shown on lock screen.
https://bugs.kde.org/show_bug.cgi?id=353855 Martin Gräßlin changed: What|Removed |Added CC||ohy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353966] Notifications cover panel if secondary display is taller than main
https://bugs.kde.org/show_bug.cgi?id=353966 William Termini changed: What|Removed |Added Version|5.4.2 |5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 356750] Muon/updater lists the update twice. Why?
https://bugs.kde.org/show_bug.cgi?id=356750 --- Comment #3 from Aleix Pol --- Can you show what kind of answer does apt-get dist-upgrade offer? It looks like an error in the repository set up. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 355980] showfotosetup link errors - undefined reference to `Digikam::Setup*
https://bugs.kde.org/show_bug.cgi?id=355980 --- Comment #8 from Treeve Jelbert --- builds ok using make at commit f65cf709b1c26263a5000eb1a70506908065f092 I have not retested using ninja yet. digikam is the only project which fails for me using ninja -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 --- Comment #3 from Potomac --- on archlinux this bug seems solved with plasma-workspace 5.5.1-4 package : https://bugs.archlinux.org/task/47399 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 --- Comment #4 from Potomac --- a patch has been released in order to fix this bug : https://quickgit.kde.org/?p=plasma-workspace.git&a=commitdiff&h=1390b4&o=plain linux distros should apply this patch quickly, for archlinux it's already done with plasma-workspace 5.5.1-4 package version -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 294778] unlock screen should show system name
https://bugs.kde.org/show_bug.cgi?id=294778 --- Comment #1 from Jens Reuterberg --- My suggestion would be to switch wallpapers in the lockscreen - on the one hand there are ways to include a name from a design perspective without any issue to the Breeze theme but at the same time the same thing can be acquired by the user changing wallpapers on one of his/her identical laptops. (You can even add your computer Name to the lockscreen wallpaper in gimp and use that?) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 353428] KWin freezes until drkonqi is closed from a terminal
https://bugs.kde.org/show_bug.cgi?id=353428 --- Comment #31 from Thomas Lübking --- I do not question that the KWin GL context "somehow™" triggers this condition - but it really sounds like a kernel bug (and is hard to debug for this) You could simply avoid the ugly conditions by eg. switching to the XRender compositing backend (afair, xfce uses xrender exclusively for compositing) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 353428] KWin freezes until drkonqi is closed from a terminal
https://bugs.kde.org/show_bug.cgi?id=353428 --- Comment #32 from Thomas Lübking --- PS, dev note: we could investigate in "stealing" the WM selection from the restarted instance if there's a crashcounter flag in the args. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 355980] showfotosetup link errors - undefined reference to `Digikam::Setup*
https://bugs.kde.org/show_bug.cgi?id=355980 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Portability Version Fixed In||5.0.0 Latest Commit||http://commits.kde.org/digi ||kam/540bcfac14991e91d83f7c0 ||bcc3ef964e2717093 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 356775] New: Kile causes Dolphin to freeze
https://bugs.kde.org/show_bug.cgi?id=356775 Bug ID: 356775 Summary: Kile causes Dolphin to freeze Product: kile Version: 2.1.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: a.skemb...@gmail.com Whenever Kile is open, Dolphin will freeze, especially when I try to access the home directory - sometimes Dolphin may continue working, sometimes not, but even if it does continue, accessing "Home" will cause it to freeze. Once Kile is closed, dolphin will continue working normally. Dolphin windows opened after Kile causes the freeze will exhibit the same behaviour - frozen until Kile is closed. Reproducible: Always Steps to Reproduce: 1. Open Kile and a Tex document 2. Open dolphin (if not already open), go to "home" 3. Try to do anything in dolphin Actual Results: Dolphin is frozen Expected Results: Dolphin should continue working normally I am on OpenSUSE Tumbleweed rpms, Dolphin version 15.08.3, KDE Frameworks 5.17.0, Qt 5.5.1 and using a dual monitor setup with Intel graphics. Any other information is at your disposal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected
https://bugs.kde.org/show_bug.cgi?id=356764 --- Comment #5 from Arthur c --- Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356350] 2.9.9 Animation Beta - Duplicating animated layers only creates new static layer
https://bugs.kde.org/show_bug.cgi?id=356350 Dmitry Kazakov changed: What|Removed |Added Latest Commit||http://commits.kde.org/krit ||a/34b7eff796385a5caf0dbfd80 ||045235f511d5162 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Dmitry Kazakov --- Git commit 34b7eff796385a5caf0dbfd80045235f511d5162 by Dmitry Kazakov. Committed on 16/12/2015 at 13:11. Pushed by dkazakov into branch 'master'. Fix Duplicate Layer feature for animated layers Ref T1141 M +13 -0krita/image/kis_keyframe_channel.cpp M +1-0krita/image/kis_keyframe_channel.h M +8-1krita/image/kis_paint_device.cc M +1-1krita/image/kis_paint_device.h M +14 -1krita/image/kis_paint_layer.cc M +10 -0krita/image/kis_raster_keyframe_channel.cpp M +1-0krita/image/kis_raster_keyframe_channel.h M +48 -0krita/image/tests/kis_paint_device_test.cpp M +1-0krita/image/tests/kis_paint_device_test.h M +8-5krita/image/tests/kis_paint_layer_test.cpp http://commits.kde.org/krita/34b7eff796385a5caf0dbfd80045235f511d5162 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356776] New: Spell checking languages not shown
https://bugs.kde.org/show_bug.cgi?id=356776 Bug ID: 356776 Summary: Spell checking languages not shown Product: systemsettings Version: 5.5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_language Assignee: jl...@kde.org Reporter: a.skemb...@gmail.com This module does not seem to detect the installed spell checking languages. Specifically, I have installed both aspell-el and ispell-greek, but the only available language for spell checking is the system language (american english). Not even British or Canadian english are available. I believe this is causing KMail 5.0.3 to not display the available spell checking languages properly. KMail2 and Kile detect the available languages correctly (greek, american english, british english etc are available for spellchecking). Am I missing a specific package? Reproducible: Always Steps to Reproduce: 1. Install aspell-el or aspell-en 2. Open Systemsettings -> Regional Setting -> Spell check 3. Try to change default language Actual Results: Only one language is display (American English, United States) Expected Results: Other languages, such as Greek, should be available. Using version 5.5.1, KDE Frameworks 5.17.0, Qt 5.5.1, on OpenSUSE Tumbleweed RPMs. Additional information at your disposal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356777] New: PlasmaShell crash after trying to download a new Wallpaper
https://bugs.kde.org/show_bug.cgi?id=356777 Bug ID: 356777 Summary: PlasmaShell crash after trying to download a new Wallpaper 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: paulo.fidalgo...@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.7-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: I was trying to dowload a new wallpaper, through the desktop settings. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcbe3cfa940 (LWP 3041))] Thread 12 (Thread 0x7fcbc39f3700 (LWP 3044)): #0 0x7fcbdb6fcffd in poll () at /lib64/libc.so.6 #1 0x7fcbe1b97272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7fcbe1b98ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fcbc5977da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7fcbdc3053ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fcbda3a460a in start_thread () at /lib64/libpthread.so.0 #6 0x7fcbdb708a9d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fcbc0fa8700 (LWP 3063)): #0 0x7fcbd6821ce4 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #1 0x7fcbd68221d0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fcbd682227c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fcbdc53cf0b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fcbdc4e3f0a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fcbdc300424 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fcbe0623b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fcbdc3053ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fcbda3a460a in start_thread () at /lib64/libpthread.so.0 #9 0x7fcbdb708a9d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fcbb3fff700 (LWP 3064)): #0 0x7fcbdb6f8bdd in read () at /lib64/libc.so.6 #1 0x7fcbd6865390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7fcbd6821c64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fcbd6822110 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fcbd682227c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fcbdc53cf0b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fcbdc4e3f0a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fcbdc300424 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fcbe0623b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7fcbdc3053ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7fcbda3a460a in start_thread () at /lib64/libpthread.so.0 #11 0x7fcbdb708a9d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fcbb298a700 (LWP 3065)): #0 0x7fcbd6866719 in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7fcbd6821719 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7fcbd682209b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7fcbd682227c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7fcbdc53cf0b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fcbdc4e3f0a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fcbdc300424 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7fcbe0623b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7fcbdc3053ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fcbda3a460a in start_thread () at /lib64/libpthread.so.0 #10 0x7fcbdb708a9d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fcbb1011700 (LWP 3066)): #0 0x7fcbda3a9b10 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcbe3487514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fcbe3487559 in () at /lib64/libQt5Script.so.5 #3 0x7fcbda3a460a in start_thread () at /lib64/libpthread.so.0 #4 0x7fcbdb708a9d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fcbaa3a4700 (LWP 3067)): #0 0x7fcbd6866734 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7fcbd6821700 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7fcbd682209b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7fcbd682227c
[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 --- Comment #2 from Stefan Vater --- Well, this is already since some time. Unfortunately I cannot really remember since when, maybe since my switch to plasma 5. Here is what journalctl -u NetworkManager gives me when plugging the stick: Dez 16 14:00:13 mylinux.org NetworkManager[960]: (cdc-wdm0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36] Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference) Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): new Broadband device (carrier: UNKNOWN, driver: 'qmi_wwan, option1', ifindex: 0) Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): modem state 'enabling' Dez 16 14:00:49 mylinux.org NetworkManager[960]: (cdc-wdm0): device state change: unavailable -> disconnected (reason 'none') [20 30 0] Dez 16 14:00:50 mylinux.org NetworkManager[960]: (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested) The only log I could find when hitting the "connect" button was in .xsession-errors: unlocking "/org/freedesktop/ModemManager1/Modem/3" plasma-nm: unlockRequired == 3 Does that help? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356778] New: Some keys do not work
https://bugs.kde.org/show_bug.cgi?id=356778 Bug ID: 356778 Summary: Some keys do not work Product: plasmashell Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: yanjin...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org The keys "Down arrow" and "End" do not work when I'm using Plasma, but they do work when I'm using the text mode. I checked this with two different keyboards and the problem appears for both of them. Moreover, I also encountered this problem when the OS on my computer was openSUSE Leap 42.1. I use the keyboard with polish layout selected. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 356779] New: Akonadi crash at power on
https://bugs.kde.org/show_bug.cgi?id=356779 Bug ID: 356779 Summary: Akonadi crash at power on Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: crgla...@gmail.com CC: kdepim-b...@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.89.0) Qt Version: 5.5.0 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: This has happened twice this morning. The first crash locked up the keyboard and didn't allow me to finish this input. ctrl, alt, backspace to logout and log back in lead back tothis crash. I have also seen Mysql errors that say someting to the efect that Mysql cannot be reached. Will try to add that log to this report. May not be related except that the log hasn't changed since the last update. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f622c9be840 (LWP 3575))] Thread 4 (Thread 0x7f6213c2e700 (LWP 3599)): #0 0x7f6226adbc1d in poll () at /lib64/libc.so.6 #1 0x7f6221a45422 in () at /usr/lib64/libxcb.so.1 #2 0x7f6221a4700f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f6215f8ac29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f62273e955f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f6221c620a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f6226ae404d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f6211305700 (LWP 3881)): #0 0x7f6226adbc1d in poll () at /lib64/libc.so.6 #1 0x7f6220ab1e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f6220ab1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f622761aa5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f62275c1a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f62273e484a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f62273e955f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f6221c620a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f6226ae404d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f6210b04700 (LWP 3882)): #0 0x7f6221c66408 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f62273ea4c8 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f62273e6716 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f62273e955f in () at /usr/lib64/libQt5Core.so.5 #4 0x7f6221c620a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f6226ae404d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f622c9be840 (LWP 3575)): [KCrash Handler] #6 0x7f6226a34187 in raise () at /lib64/libc.so.6 #7 0x7f6226a35538 in abort () at /lib64/libc.so.6 #8 0x7f6227053b8d in __gnu_cxx::__verbose_terminate_handler() () at /usr/lib64/libstdc++.so.6 #9 0x7f6227051bf6 in () at /usr/lib64/libstdc++.so.6 #10 0x7f6227051c41 in () at /usr/lib64/libstdc++.so.6 #11 0x7f6227051ea6 in __cxa_rethrow () at /usr/lib64/libstdc++.so.6 #12 0x00466a86 in QList::append(long long const&) (this=this@entry=0x7ffdccaf4290, t=@0x7ffdccaf41f0: 134217470) at /usr/include/qt5/QtCore/qlist.h:574 #13 0x0046333b in MoveItemsTask::imapSetToList(KIMAP::ImapSet const&) (t=@0x7ffdccaf41f0: 134217470, this=0x7ffdccaf4290) at /usr/include/qt5/QtCore/qlist.h:355 #14 0x0046333b in MoveItemsTask::imapSetToList(KIMAP::ImapSet const&) (this=this@entry=0x21b9b90, set=...) at /usr/src/debug/kdepim-runtime-15.08.3/resources/imap/moveitemstask.cpp:313 #15 0x004637bd in MoveItemsTask::recordNewUid() (this=this@entry=0x21b9b90) at /usr/src/debug/kdepim-runtime-15.08.3/resources/imap/moveitemstask.cpp:255 #16 0x00464902 in MoveItemsTask::onSearchDone(KJob*) (this=0x21b9b90, job=0x19fef50) at /usr/src/debug/kdepim-runtime-15.08.3/resources/imap/moveitemstask.cpp:248 #17 0x7f62275f340f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #18 0x7f6229477d32 in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5 #19 0x7f622947859f in KJob::finishJob(bool) () at /usr/lib64/libKF5CoreAddons.so.5 #20 0x7f622b5cbb98 in KIMAP::Job::handleErrorReplies(KIMAP::Message const&) () at /usr/lib64/libKF5IMAP.so.5 #21 0x7f622b5dd638 in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () at /usr/lib64/libKF5IMAP.so.5 #22 0x7f622b5e9eba in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () at /usr/lib64/libKF5IMAP.so.5 #23 0x7f62275f4796
[systemsettings] [Bug 355711] System Settings crashed during exit processing.
https://bugs.kde.org/show_bug.cgi?id=355711 --- Comment #8 from Jonathan Marten --- https://git.reviewboard.kde.org/r/126385/ -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 --- Comment #3 from Jan Grulich --- Yes, that helps, According to the log your SIM card is protected by PIN2, is that true? We handle just PIN and PUK and not PIN2 or PUK2 or any other type. We disabled this because there were some issues due to this but it looks there are now new issues due to not handling those types. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 356779] Akonadi crash at power on
https://bugs.kde.org/show_bug.cgi?id=356779
--- Comment #1 from Chris ---
Mysql server log
2015-12-16 07:32:21 7f2e10859740 InnoDB: Warning: Using
innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in
future releases, together with the option innodb_use_sys_malloc and with the
InnoDB's internal memory allocator.
151216 7:32:21 [Note] InnoDB: Using mutexes to ref count buffer pool pages
151216 7:32:21 [Note] InnoDB: The InnoDB memory heap is disabled
151216 7:32:21 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
151216 7:32:21 [Note] InnoDB: Memory barrier is not used
151216 7:32:21 [Note] InnoDB: Compressed tables use zlib 1.2.8
151216 7:32:21 [Note] InnoDB: Using Linux native AIO
151216 7:32:21 [Note] InnoDB: Using CPU crc32 instructions
151216 7:32:21 [Note] InnoDB: Initializing buffer pool, size = 80.0M
151216 7:32:21 [Note] InnoDB: Completed initialization of buffer pool
151216 7:32:21 [Note] InnoDB: Highest supported file format is Barracuda.
151216 7:32:21 [Note] InnoDB: 128 rollback segment(s) are active.
151216 7:32:21 [Note] InnoDB: Waiting for purge to start
151216 7:32:21 [Note] InnoDB: Percona XtraDB (http://www.percona.com)
5.6.25-73.1 started; log sequence number 217698344
151216 7:32:21 [Note] Reading of all Master_info entries succeded
151216 7:32:21 [Note] Added new Master_info '' to hash table
151216 7:32:21 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.21-MariaDB' socket: '/tmp/akonadi-chrisg.48NRsQ/mysql.socket'
port: 0 openSUSE package
Additionally when I enter "akonadictl start" command the following is displayed
akonadictl start
Starting Akonadi Server...
done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Rex:~ # QCommandLineParser: option not defined: "start-without-control"
search paths: ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin",
"/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/games",
"/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec",
"/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db: "/usr/bin/mysql_install_db"
Found mysqlcheck: "/usr/bin/mysqlcheck"
/usr/bin/mysqlcheck: Got error: 2002: Can't connect to local MySQL server
through socket '/tmp/akonadi-root.qW81wQ/mysql.socket' (2 "No such file or
directory") when trying to connect
Failed to verify database server version
Query error: "MySQL server has gone away QMYSQL: Unable to execute query"
Database error: " "
"[\n0: akonadiserver(_Z11akBacktracev+0x33) [0x5dbaa3]\n1: akonadiserver()
[0x5dbd99]\n2: /lib64/libc.so.6(+0x35200) [0x7f6a94314200]\n3:
/lib64/libc.so.6(gsignal+0x37) [0x7f6a94314187]\n4:
/lib64/libc.so.6(abort+0x118) [0x7f6a94315538]\n5:
/usr/lib64/libQt5Core.so.5(_Z17qt_message_output9QtMsgTypeRK18QMessageLogContextRK7QString+0x165)
[0x7f6a94cb8e45]\n6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xeb)
[0x5de28b]\n7: /usr/lib64/libQt5Core.so.5(_ZN9QIODevice5writeEPKcx+0xe8)
[0x7f6a94dd3468]\n8: /usr/lib64/libQt5Core.so.5(_ZN11QTextStreamD2Ev+0x11c)
[0x7f6a94de409c]\n9: /usr/lib64/libQt5Core.so.5(_ZN6QDebugD2Ev+0x3f)
[0x7f6a94db428f]\n10:
akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x2ede)
[0x4f80ae]\n11:
akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xf1)
[0x482c51]\n12: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0x74)
[0x484184]\n13: akonadiserver() [0x565176]\n14:
/usr/lib64/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0x276)
[0x7f6a94ed4796]\n15:
/usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication6notifyEP7QObjectP6QEvent+0x3d)
[0x7f6a94ea3e9d]\n16:
/usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x65)
[0x7f6a94ea3ba5]\n17:
/usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1e7)
[0x7f6a94ea5d67]\n18: /usr/lib64/libQt5Core.so.5(+0x2dc5c3)
[0x7f6a94efb5c3]\n19:
/usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x254)
[0x7f6a92752c84]\n20: /usr/lib64/libglib-2.0.so.0(+0x4bed8)
[0x7f6a92752ed8]\n21:
/usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c)
[0x7f6a92752f7c]\n22:
/usr/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5c)
[0x7f6a94efaa3c]\n23:
/usr/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x123)
[0x7f6a94ea1a63]\n24:
/usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x86)
[0x7f6a94ea95d6]\n25: akonadiserver(main+0x127) [0x481dc7]\n26:
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7f6a94300b05]\n27: akonadiserver()
[0x482707]\n]\n"
ProcessControl: Application 'akonadiserver' returned with exit code 255
(Unknown error)
QCommandLineParser: option not defined: "start-without-control"
search paths: ("/sbin", "/usr/sbin", "/usr/local/sbin", "/root/bin",
"/usr/local/bin", "/usr/bin", "/bin", "/usr/bin/X11", "/usr/games",
"/usr/sbin", "/usr/
[krita] [Bug 356774] unwanted dots on strokes (possibly just with stabilizer)
https://bugs.kde.org/show_bug.cgi?id=356774 --- Comment #3 from kasiazl...@gmail.com --- Created attachment 96125 --> https://bugs.kde.org/attachment.cgi?id=96125&action=edit sample image -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 338506] image wallpapers are blurry in scaled and scaled and cropped mode
https://bugs.kde.org/show_bug.cgi?id=338506 Alex changed: What|Removed |Added CC||bugs@chezmandre.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356321] OpenSuse 42.1 plasma desktop crash
https://bugs.kde.org/show_bug.cgi?id=356321 iaiv...@126.com changed: What|Removed |Added CC||iaiv...@126.com --- Comment #6 from iaiv...@126.com --- Same problem. KIO Version: 5.16.0-3.2 / x86_64 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 279614] The Dolphin shell panel (opend by F4) does not source .bashrc
https://bugs.kde.org/show_bug.cgi?id=279614 Kevin Shepherd changed: What|Removed |Added CC||k...@scarletline.com --- Comment #26 from Kevin Shepherd --- Still happening in Dolphin v15.08.2 KDE v5.15.0 Olivier's workaround works ( Thanks Olivier ) - CTRL-D F4 I am happy to provide any logs that might help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356321] OpenSuse 42.1 plasma desktop crash
https://bugs.kde.org/show_bug.cgi?id=356321 --- Comment #7 from RichT --- Created attachment 96126 --> https://bugs.kde.org/attachment.cgi?id=96126&action=edit KIO versions hopefully this is what you were asking for -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup
https://bugs.kde.org/show_bug.cgi?id=323230 --- Comment #36 from yulaow --- I think panels are having a lot of problems with absolute/relative edges with external monitors Look what happens when I click on the menu widget (this is my external monitor)... the menu should pop up right above the panel as usual (and this correctly happens when I just use the main screen of my laptop) but, instead, it pops a lot higher than expected without reasons before click http://imgur.com/1x5a18l after click http://imgur.com/bdk4CaE -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.
https://bugs.kde.org/show_bug.cgi?id=303877 Роман Донченко changed: What|Removed |Added CC||d...@corrigendum.ru --- Comment #9 from Роман Донченко --- > Do we need to move this forward? Is .zdebug gaining mainstream acceptance? Yes and yes. Debian now defaults to compressing their debugging symbols (this change was made in debhelper v9, if anyone's curious). On x86_64 you can at least get call stacks, since .eh_frame is mandatory, but on, say, ARM or ARM64 it's not. So the call stacks stop at the first C-only library. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356649] use-after-free crash on closing ark on previewing an archive
https://bugs.kde.org/show_bug.cgi?id=356649 --- Comment #7 from Santhiar --- I have encountered a bug with a similar repro but different crash stacks. Basically opening a damaged archive and closing ark while the error window is open crashes ark. Shall I paste the details here, or open a separate bug? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356649] use-after-free crash on closing ark on previewing an archive
https://bugs.kde.org/show_bug.cgi?id=356649 --- Comment #6 from Santhiar --- I have compiled ark from git. The commit at head is 9c23ca12ad5884ddd271ea46e6b4bef3b68ed3e1 I'm on the Applications/15.04 branch (that was checkout out by kdesrc-build) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 351991] breeze skin
https://bugs.kde.org/show_bug.cgi?id=351991 Olivier Churlaud changed: What|Removed |Added CC||oliv...@churlaud.com --- Comment #3 from Olivier Churlaud --- andreas: I'm going to do this. Which one should I take? Thin? Default? And what about the dark theme? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 318322] kickoff shadow remains
https://bugs.kde.org/show_bug.cgi?id=318322 --- Comment #29 from Piotr Kloc --- Phew, my arm will be fine, for now. Thanks, ghost shadow is gone. Tested with 5.5.1 as it went to stable today. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 351121] Dolphin cannot write to Lumia (windows 8.1) phone. Nautilus has no problems
https://bugs.kde.org/show_bug.cgi?id=351121 Piotr Kloc changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #5 from Piotr Kloc --- (In reply to zx_master from comment #4) > Hello. I'm confirm that this bug still exist. > I'm not able to open Nokia 1020 from Dolphin and never was able. > > Kubuntu 15.10, Dolphin 15.08.2, KDE Frameworks 5.15.0 > > P.S. Looks like there is possible a libmtp or kio-mtp related bug. But you > should consider, that Nautilus does not have this issue. The fact is that > Nautilus works with Windows Phones, Dolphin does not. Nautilus, Nemo and some more use gvfs-mtp. Dolphin uses KDE specific libs. -- You are receiving this mail because: You are watching all bug changes.
