[kdenlive] [Bug 356407] "View" menu can't show/hide tabs
https://bugs.kde.org/show_bug.cgi?id=356407 --- Comment #2 from Jean-Baptiste Mardelle --- Did you install Kdenlive or are you running it from a custom folder without installing ? I see that you also have missing icons (the "kdenlive" icon on video tracks should be a checkerboard icon). In KDE apps, the menus are defined from an xml file called kdenliveui.rc that file must be installed in a location that can be found at runtime, and I guess it does not find it correctly. Did you compile by yourself ? -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 356320] Kopete history logs import not work.
https://bugs.kde.org/show_bug.cgi?id=356320 Honza Tvrznik changed: What|Removed |Added CC||flate...@atlas.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356411] New: Plasma crashed on startup
https://bugs.kde.org/show_bug.cgi?id=356411 Bug ID: 356411 Summary: Plasma crashed on startup Product: plasmashell Version: 5.4.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: gabrimo...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.2) Qt Version: 5.4.2 Operating System: Linux 4.2.0-19-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: The system was starting up. I've entered login and password, and the desktop was finishing loading. Main panel was adjusting, icon in the systray finished loading some second before. I'm on a dual monitor setup -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd0e4a5e800 (LWP 2588))] Thread 10 (Thread 0x7fd0ce5b6700 (LWP 2591)): #0 0x7fd0df21a8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fd0e3261bd2 in poll (__timeout=-1, __nfds=1, __fds=0x7fd0ce5b5cc0) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x1e313d0, cond=cond@entry=0x1e31410, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x7fd0e326374f in xcb_wait_for_event (c=0x1e313d0) at ../../src/xcb_in.c:623 #4 0x7fd0d1184a39 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #5 0x7fd0df90d2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd0de9fc6aa in start_thread (arg=0x7fd0ce5b6700) at pthread_create.c:333 #7 0x7fd0df225eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7fd0c7be2700 (LWP 2819)): #0 0x7fd0df21c743 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fd0dfb3f90f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd0dfb4140e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd0dfb4193e in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd0dfaea75a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd0df9083d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd0e2130f85 in QQmlThreadPrivate::run (this=0x1f62ff0) at qml/ftw/qqmlthread.cpp:141 #7 0x7fd0df90d2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd0de9fc6aa in start_thread (arg=0x7fd0c7be2700) at pthread_create.c:333 #9 0x7fd0df225eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fd0bd14d700 (LWP 2822)): #0 0x7fd0df21c743 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fd0dfb3f90f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd0dfb4140e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd0dfb4193e in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd0dfaea75a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd0df9083d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd0e2130f85 in QQmlThreadPrivate::run (this=0x232fc00) at qml/ftw/qqmlthread.cpp:141 #7 0x7fd0df90d2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd0de9fc6aa in start_thread (arg=0x7fd0bd14d700) at pthread_create.c:333 #9 0x7fd0df225eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fd0b6832700 (LWP 2831)): #0 0x7fd0df21c743 in select () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fd0dfb3f90f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd0dfb4140e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd0dfb4193e in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd0dfaea75a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd0df9083d4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd0e2130f85 in QQmlThreadPrivate::run (this=0x24ce5a0) at qml/ftw/qqmlthread.cpp:141 #7 0x7fd0df90d2be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd0de9fc6aa in start_thread
[kmail2] [Bug 356406] Add roles to folders (like junk, ...) / use special folders of account
https://bugs.kde.org/show_bug.cgi?id=356406 Laurent Montel changed: What|Removed |Added Resolution|--- |INVALID CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Laurent Montel --- see kmail->configure->identity -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356404] Link identity and SMTP Server
https://bugs.kde.org/show_bug.cgi?id=356404 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- See kmail->configure->identity -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356390] kmail version 4.14.08.2-0ubuntu1 crashes when I press on new message
https://bugs.kde.org/show_bug.cgi?id=356390 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Laurent Montel --- It's a known bug Fixed in 5.0.3 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 356403] The height of the Contact's menu bar is bigger than that of the rest of the Kontact suite.
https://bugs.kde.org/show_bug.cgi?id=356403 Laurent Montel changed: What|Removed |Added Resolution|--- |INVALID CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Laurent Montel --- it's normal there is combobox in toolbar => it increases size -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356412] New: Windows are maximized under panel
https://bugs.kde.org/show_bug.cgi?id=356412 Bug ID: 356412 Summary: Windows are maximized under panel Product: kwin Version: 5.4.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: v...@pelcak.org When I maximize window, it is behind the panel. I have set panel to be always on top and never hide. Yet, maximized windows are behind it. It is rather annoying as I have to resize windows manually to fit or have part of the window hidden. See screenshot in attachment. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356412] Windows are maximized under panel
https://bugs.kde.org/show_bug.cgi?id=356412 --- Comment #1 from Vit Pelcak --- Created attachment 95944 --> https://bugs.kde.org/attachment.cgi?id=95944&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 341930] Session management in porting preproc branch
https://bugs.kde.org/show_bug.cgi?id=341930 --- Comment #76 from Thomas Lübking --- As pointed out in comment #74 this is a completely unrelated issue. Session management in Qt5 was and is broken and won't (read: "can't") be fixed by kwin for sure, there're considerations to work around *parts* of that in ksmserver, but neither that discussion belongs into this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356412] Windows are maximized under panel
https://bugs.kde.org/show_bug.cgi?id=356412 --- Comment #2 from Thomas Lübking --- please post the output of "xrandr -q" and "xprop" (for the latter click the panel after the cursor turned into a '+') -- You are receiving this mail because: You are watching all bug changes.
[kdemultimedia] [Bug 356348] HEVC Videos Not Showing in Preview Mode
https://bugs.kde.org/show_bug.cgi?id=356348 --- Comment #6 from Rog131 --- (In reply to phillip9001 from comment #5) > I take it that KDE 4.14.2 doesn't have the necessary libraries to preview > HEVC in dolphin? > Does that mean I should update my libraries or try updating KDE Plasma 4 to > Plasma 5? > Does this problem occur in KDE Plasma 5? It is not the KDE libraries - It is the libav/ffmpeg libraries. Short : The Debian & Ubuntu decided to use the ffmpeg fork libav /1/. The Ubuntu 14.04 is using libav 9.18 /2/. Ubuntu has a stable release policy /3/ to not update old packages. There will be bug fixes for the serious bugs. When I was using the Ubuntu 14.04 I added the HEVC support to the KDE thumbnailer by: - compiling an own local version of the current ffmpeg - rebuilding the ffmpegthumbs so it is using the local ffmpeg not the distro libav. By my knowledge the Mint /4/ is using the Ubuntu packages but I don't know witch version is using the newest released version. With the Ubuntu KF5 thumbnailer there is the bug: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1505014 1. https://www.kubuntuforums.net/showthread.php?62882-Avconv-Winff-ffmpeg 2. http://packages.ubuntu.com/source/trusty-updates/libav 3. https://wiki.ubuntu.com/StableReleaseUpdates 4. https://en.wikipedia.org/wiki/Linux_Mint -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 356413] New: The CSV and ODS export scripts are not finding the Sheets
https://bugs.kde.org/show_bug.cgi?id=356413
Bug ID: 356413
Summary: The CSV and ODS export scripts are not finding the
Sheets
Product: calligraplan
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kosse...@kde.org
Reporter: cs...@bxabi.com
Version 2.9.9
Using KDE Development Platform 4.14.14
When I go to scripts, export, CSV or ODS export, I get an error message "Failed
to start Sheets. Is Sheets installed?"
Sheets is installed, but I assume the script is using and old naming or
something when it is looking for it.
The CSV export works if I disable the following check in the script (I assume
it doesn's actually need the Sheets).
if Sheets is None:
raise Exception, T.i18n("Failed to start Sheets. Is Sheets installed?")
Reproducible: Always
Steps to Reproduce:
1. Menu: Tools
2. Scripts
3. Export to ods
Actual Results:
error message: Failed to start Sheets. Is Sheets installed?
Expected Results:
export to file.
--
You are receiving this mail because:
You are watching all bug changes.
[calligraplan] [Bug 356414] New: Plan is not installable on Windows
https://bugs.kde.org/show_bug.cgi?id=356414 Bug ID: 356414 Summary: Plan is not installable on Windows Product: calligraplan Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: usability Assignee: kosse...@kde.org Reporter: cs...@bxabi.com I made a thorough search of the project planners, and I found that Calligra Plan does exactly what I need, and also, that it is the only one which is open source and contain Resource Leveling (and has a gui, because the latest TaskJuggler doesn't). So this is nice, but when I sent over my plan to Windows users, they were not able to open it. The Calligra-Gemini suite does not contain it. Reproducible: Always Steps to Reproduce: 1. Install Calligra-Gemini on Windows 2. Search for the Plan application 3. It is not included Actual Results: no Plan on windows Expected Results: Plan should have a windows installer I love Plan, but there are still many people on windows, so if I want to share the plan, I need a cross-platform tool. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 Laurent Bonnaud changed: What|Removed |Added CC||l.bonn...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 295438] Keyboard layout switcher stops working
https://bugs.kde.org/show_bug.cgi?id=295438 --- Comment #53 from Valdas --- I use workaround: right click on layout indicator -> settings -> change something simple -> undo change -> apply. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356055] login error
https://bugs.kde.org/show_bug.cgi?id=356055 venember changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED --- Comment #8 from venember --- What do not you understand? 1. KDE is your desktop manager system. 2. It is a report about the remote crash (accross vnc) on YOUR crash report screen (i copied this onto my machine). 3. Plus I investigated the relevant records from the system logging: after crash I logged in via ssh. 4. The error persists. 5. I have deleted the KDE because I need a working desktop. The complete result: BEFORE opensuse 13.2 to Tumbleweed upgrade my KDE graphical environment worked. AFTER upgrade I can choose between a full upgrade WITHOUT desktop (crash) OR a half-wiped system (polkit with other stuff, I do not know what causes the error) with IceWM desktop. I sent the problem onto the opensuse TUMBLEWEED forum, there is no answer. I can not decide that is is either your problem or the opensuse distribution. It seems to be none of you, only mine... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356200] Composite Transition will use first-selected wipe file even if "none" or different image selected
https://bugs.kde.org/show_bug.cgi?id=356200 --- Comment #1 from Jean-Baptiste Mardelle --- That was an MLT issue, I justed posted a patch proposal. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355750] When setting up panels in Plasma, plasma shell crashes
https://bugs.kde.org/show_bug.cgi?id=355750 --- Comment #6 from Martin Kyral --- Duplicate of: https://bugs.kde.org/show_bug.cgi?id=354660 After upgrade to plasma 5.5 it seems the crashes are a history. Please, close this bug as duplicate. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356359] Can't open documents with non-ascii filenames
https://bugs.kde.org/show_bug.cgi?id=356359 --- Comment #6 from Kiril Vladimiroff --- Dolphin: 15.08.3 KDE Frameworks: 5.16 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356415] New: Multiple clicks are necessary in order to activate panel elements
https://bugs.kde.org/show_bug.cgi?id=356415 Bug ID: 356415 Summary: Multiple clicks are necessary in order to activate panel elements Product: plasmashell Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: robby.engelm...@igfs-ev.de Sometimes multiple clicks are necessary in order to activate panel elements and tray icons. Reproducible: Sometimes Steps to Reproduce: 1. start 3-4 applications and having some application shown in panel also when not started 2. work with these application and switch between them multiple times 3. try to click on some tray icons Actual Results: sometimes the applications get not activated or hidden. Sometimes applications get not launched. Sometimes tray icons get not activated by only one click. With the tray I am not absolutely sure. But working 5 minutes switching between different applications will for sure trigger the bug (at least for me) Expected Results: one click is enough using plasma 5.5, Frameworks 5.16 and Qt 5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[krecipes] [Bug 356416] New: Krecipes crashed on import of recipes from Meal Master Cookbook
https://bugs.kde.org/show_bug.cgi?id=356416 Bug ID: 356416 Summary: Krecipes crashed on import of recipes from Meal Master Cookbook Product: krecipes Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krecipes-de...@kde.org Reporter: v...@pelcak.org Application: krecipes (2.0.0) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20151201) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I just tried to import text database of recipes from Meal Master. -- Backtrace: Application: Krecipes (krecipes), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd7ebc86900 (LWP 10544))] Thread 2 (Thread 0x7fd7cee24700 (LWP 17842)): #0 0x7fd7e436120d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd7e0b5a264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7fd7c8003410, timeout=, context=0x7fd7c80009a0) at gmain.c:4135 #2 0x7fd7e0b5a264 in g_main_context_iterate (context=context@entry=0x7fd7c80009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7fd7e0b5a36c in g_main_context_iteration (context=0x7fd7c80009a0, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7fd7e5b2726e in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fd7c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x7fd7e5af73e1 in QEventLoop::processEvents(QFlags) (this=this@entry=0x7fd7cee23ca0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7fd7e5af76f5 in QEventLoop::exec(QFlags) (this=this@entry=0x7fd7cee23ca0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7fd7e59f0a59 in QThread::exec() (this=this@entry=0xe11510) at thread/qthread.cpp:538 #8 0x7fd7e5ad84c3 in QInotifyFileSystemWatcherEngine::run() (this=0xe11510) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x7fd7e59f323c in QThreadPrivate::start(void*) (arg=0xe11510) at thread/qthread_unix.cpp:352 #10 0x7fd7e25754a4 in start_thread (arg=0x7fd7cee24700) at pthread_create.c:334 #11 0x7fd7e4369b9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fd7ebc86900 (LWP 10544)): [KCrash Handler] #6 0x7fd7e42b4d38 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x7fd7e42b618a in __GI_abort () at abort.c:78 #8 0x7fd7e49b9b3d in __gnu_cxx::__verbose_terminate_handler() () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x7fd7e49b7ba6 in __cxxabiv1::__terminate(void (*)()) (handler=) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:47 #10 0x7fd7e49b7bf1 in std::terminate() () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:57 #11 0x7fd7e49b7e56 in __cxxabiv1::__cxa_rethrow() () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:125 #12 0x7fd7e5af7914 in QEventLoop::exec(QFlags) (this=this@entry=0x7ffde7dbc9b0, flags=...) at kernel/qeventloop.cpp:218 #13 0x7fd7e5afcef9 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1227 #14 0x00437f97 in main () Possible duplicates by query: bug 353304, bug 352495, bug 352280, bug 351097, bug 350831. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356303] Overlay blend mode appears incorrect in a 16 bit image
https://bugs.kde.org/show_bug.cgi?id=356303 --- Comment #16 from Boudewijn Rempt --- > In my particular case that's unavoidable, as clients often require > multilayered > PSD files, and 16 bit files are too large to transfer easily. I'd work > directly in 8 bit except the airbrush is not smooth and there's more brush > lag, > but those are reports for another day. ;) Hm, in that case, I'd say, use a gamma corrected profile even in 16 bits/channel rgb, that way you won't get surprises when converting down to 8 bits/channel. -- You are receiving this mail because: You are watching all bug changes.
[krecipes] [Bug 356416] Krecipes crashed on import of recipes from Meal Master Cookbook
https://bugs.kde.org/show_bug.cgi?id=356416 --- Comment #1 from Vit Pelcak --- Created attachment 95945 --> https://bugs.kde.org/attachment.cgi?id=95945&action=edit recipes database -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] New: Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 Bug ID: 356417 Summary: Notes widget broke since upgrade to plasma 5.5 Product: plasmashell Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: robby.engelm...@igfs-ev.de CC: bhus...@gmail.com, plasma-b...@kde.org Notes widget only shows transparent style even if other style was selected prior to the upgrade from 5.4. Settings dialogue looks strange too. All sticky note styles are transparent. Reproducible: Always using plasma 5.5.0, Frameworks 5.16 and Qt 5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356418] New: usability of vectorial shapes
https://bugs.kde.org/show_bug.cgi?id=356418 Bug ID: 356418 Summary: usability of vectorial shapes Product: krita Version: 2.9.9 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Vector Objects and Tools Assignee: krita-bugs-n...@kde.org Reporter: avelinodesabb...@alice.it Good day to all. I'm trying to use the "Bezier Curve Tool" on a shiny background and I find some settings: How do I say that a curve should be open or closed? change the color, the thickness of the curve as the quality of ... The document speaks of the "Stroke and Fill dock". I use Krita testing 2.9.9 Doker but this does not exist. Where do I find the settings "Stroke and Fill"? Even with the selected shape (Path Editig tool "on or off), Ill dock" Shape Properties "it is empty. Thank Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356419] New: Custom notification location is not remembered after restart
https://bugs.kde.org/show_bug.cgi?id=356419 Bug ID: 356419 Summary: Custom notification location is not remembered after restart Product: plasmashell Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: mklape...@kde.org Reporter: robby.engelm...@igfs-ev.de CC: plasma-b...@kde.org I activated the custom location and set it to the upper right corner after I saw notifications coming up randomly at the lower left or lower right corner after I upgraded from 5.4. After each restart I have to set this again. Reproducible: Always Using plasma 5.5.0, Frameworks 5.16 and Qt5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356418] usability of vectorial shapes
https://bugs.kde.org/show_bug.cgi?id=356418 --- Comment #1 from Avelino De Sabbata --- I use Krita-testing2.9.9! -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 356420] New: Kopete crashed when closing conversation window
https://bugs.kde.org/show_bug.cgi?id=356420 Bug ID: 356420 Summary: Kopete crashed when closing conversation window Product: kopete Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: v...@pelcak.org Application: kopete (1.7.3) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20151201) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I closed conversation and then Kopete crashed. Looks like duplicate of already reported bug, therefore I set it as possible duplicate. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6dac532900 (LWP 24802))] Thread 3 (Thread 0x7f6d93469700 (LWP 24804)): #0 0x7f6da87ec20d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6da3302264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f6d8c003600, timeout=, context=0x7f6d8c0009a0) at gmain.c:4135 #2 0x7f6da3302264 in g_main_context_iterate (context=context@entry=0x7f6d8c0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f6da330236c in g_main_context_iteration (context=0x7f6d8c0009a0, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f6da9f3726e in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f6d8c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x7f6da9f073e1 in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f6d8c0013b0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f6da9f076f5 in QEventLoop::exec(QFlags) (this=0x7f6d8c0013b0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f6d94301a0f in QCA::SyncThread::run() (this=0x55f3d8ba46b0) at support/syncthread.cpp:195 #8 0x7f6da9e0323c in QThreadPrivate::start(void*) (arg=0x55f3d8ba46b0) at thread/qthread_unix.cpp:352 #9 0x7f6da548d4a4 in start_thread (arg=0x7f6d93469700) at pthread_create.c:334 #10 0x7f6da87f4b9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f6d92c68700 (LWP 24805)): #0 0x7f6da87ec20d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f6da3302264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f6d840013e0, timeout=, context=0x7f6d840009a0) at gmain.c:4135 #2 0x7f6da3302264 in g_main_context_iterate (context=context@entry=0x7f6d840009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f6da330236c in g_main_context_iteration (context=0x7f6d840009a0, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f6da9f3726e in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f6d840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x7f6da9f073e1 in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f6d92c67c40, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f6da9f076f5 in QEventLoop::exec(QFlags) (this=this@entry=0x7f6d92c67c40, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f6da9e00a59 in QThread::exec() (this=this@entry=0x55f3d8c978a0) at thread/qthread.cpp:538 #8 0x7f6d9477f0ca in XMPP::NetTrackerThread::run() (this=0x55f3d8c978a0) at /usr/src/debug/kopete-15.08.3/protocols/jabber/libiris/src/irisnet/corelib/netinterface.cpp:168 #9 0x7f6da9e0323c in QThreadPrivate::start(void*) (arg=0x55f3d8c978a0) at thread/qthread_unix.cpp:352 #10 0x7f6da548d4a4 in start_thread (arg=0x7f6d92c68700) at pthread_create.c:334 #11 0x7f6da87f4b9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f6dac532900 (LWP 24802)): [KCrash Handler] #6 0x7f6da9f1d34e in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) (sender=0x55f3d8e46cc0, signal=0x55f3d93e46c9 "destroyed()", signal@entry=0x7f6da1abba13 "2destroyed()", receiver=receiver@entry=0x55f3d86d7c00, method=0x55f3d92fa9f9 "slotManagedTopLevelWidgetDestroyed()", method@entry=0x7f6da1abc698 "1slotManagedTopLevelWidgetDestroyed()") at kernel/qobject.cpp:2920 #7 0x7f6da1aa2d79 in KParts::PartManager::~PartManager() (this=0x55f3d86d7c00, __in_chrg=) at /usr/src/debug/kdelibs-4.14.14/kparts/partmanager.cpp:132 #8 0x7f6da1aa2f29 in KParts::PartManager::~PartManager() (this=0x55f3d86d7c00, __in_chrg=) at /usr/src/debug/kdelibs-4.14.14/kparts/partmanager.cpp:143 #9 0x7f6da9f200b1 in QObjectPrivate::deleteChildren() (this=this@entry=0x55f3d8ca6f20) at kernel/qobject.cpp:1944 #10 0x7f6da9f22624 in QObject::~QObject() (this=0x55f3d8ff2a40, __in_chrg=) at kernel/qobject.cpp:954 #11 0x7f6da1a9ccf5 in KParts::Part::~Part() (this=0x55f3d8ff2a40, __vtt_parm=0x7f6d9620d628 , __i
[klipper] [Bug 356421] New: can't search/filter right away in klipper menu
https://bugs.kde.org/show_bug.cgi?id=356421 Bug ID: 356421 Summary: can't search/filter right away in klipper menu Product: klipper Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasma-widget Assignee: mgraess...@kde.org Reporter: ric...@nakts.net this might be kde frameworks 5.16, but i have to admit that the separate frameworks/plasma/whatnot versions still confuse me a lot :) in previous versions, opening the klipper menu and starting to type filtered/searched the entries right away. now it requires clicking in the "search" field, which is mighty inconvenient. would be great to return to the old behaviour either by focusing the "search" field or just capturing all input when the menu is open Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356331] KDE Power Management System init failed!
https://bugs.kde.org/show_bug.cgi?id=356331 --- Comment #2 from Matthias Apitz --- I have had it today again and the situation re/ hald is like this in the moment of 'startx': 885 - Ds 0:00,01 /usr/local/sbin/hald 890 - I0:00,03 hald-runner 764 v0- I0:00,01 /usr/local/sbin/hald 988 v0 R0:00,00 fgrep hal 06:42:19: startkde: Starting up... 06:42:20: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) 06:42:20: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. ... The proc 885 can not be killed, not even with -9; only a re-boot solves the situation; I instructed the start of hald with debug logging and it says on boot: $ fgrep hal /var/log/messages Dec 9 08:28:58 c720-r285885-amd64 hald[965]: 08:28:58.772 [E] hald_runner.c:676: Error running 'hald-addon-input': org.freedesktop.HalRunner.Failed: Start request failed Dec 9 08:28:58 c720-r285885-amd64 hald[965]: 08:28:58.772 [E] hald_dbus.c:3579: Cannot start singleton addon hald-addon-input for udi /org/freedesktop/Hal/devices/atkbd_0 Dec 9 08:28:58 c720-r285885-amd64 hald[965]: 08:28:58.772 [E] hald.c:137: Couldn't add device to singleton Don't know if the above messages are related to the problem. Right now the battery is shown fine and the hald situation is: $ ps ax | fgrep hal 965 - Ss 0:03,16 /usr/local/sbin/hald --verbose=yes --use-syslog 970 - I 0:00,04 hald-runner 1724 - S 0:00,41 /usr/local/libexec/gvfs-hal-volume-monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355122] Plasma crashed when searching application in menu
https://bugs.kde.org/show_bug.cgi?id=355122 Zsombor changed: What|Removed |Added CC||zo...@mailbox.hu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355122] Plasma crashed when searching application in menu
https://bugs.kde.org/show_bug.cgi?id=355122 --- Comment #4 from Zsombor --- Application: plasmashell (5.2.2) Qt Version: 5.4.1 Operating System: Linux 3.19.0-37-generic x86_64 Distribution: Ubuntu 15.04 -- Information about the crash: - What I was doing when the application crashed: Tried to find some application in the start menu, and after it crashed, and it restarted -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fe37c2507c0 (LWP 1960))] Thread 36 (Thread 0x7fe297fff700 (LWP 2038)): #0 0x7fe37375d789 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe3737182d7 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe373718de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe373718fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe377924c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe3778c93e2 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe377688b44 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe379416f65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fe37768db0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fe3768936aa in start_thread (arg=0x7fe297fff700) at pthread_create.c:333 #10 0x7fe377017eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 34 (Thread 0x7fe28fdf9700 (LWP 2061)): #0 0x7fe37700849d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fe37375c2f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe37371896c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe373718e60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe373718fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe377924c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe3778c93e2 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe377688b44 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe37bf00b56 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fe37768db0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fe3768936aa in start_thread (arg=0x7fe28fdf9700) at pthread_create.c:333 #11 0x7fe377017eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 33 (Thread 0x7fe28f5f8700 (LWP 2063)): #0 0x7fe37700c8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fe373718ebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe373718fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe377924c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe3778c93e2 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe377688b44 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe379416f65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fe37768db0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe3768936aa in start_thread (arg=0x7fe28f5f8700) at pthread_create.c:333 #9 0x7fe377017eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 32 (Thread 0x7fe28e3c3700 (LWP 2069)): #0 0x7fe373718362 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe373718de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe373718fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe377924c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe3778c93e2 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe377688b44 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe379416f65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fe37768db0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe3768936aa in start_thread (arg=0x7fe28e3c3700) at pthread_create.c:333 #9 0x7fe377017eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 31 (Thread 0x7fe28d2ba700 (LWP 2070)): #0 0x7fe37375d7a4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe373718ddb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe373718fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/
[klipper] [Bug 343519] Klipper systray widget is not closed automatically once a user has selected an item
https://bugs.kde.org/show_bug.cgi?id=343519 ric...@nakts.net changed: What|Removed |Added CC||ric...@nakts.net --- Comment #3 from ric...@nakts.net --- since starting to use kde5. this has been one of a few things that i would call "annoying usability regressions" :) all systray widgets do not serve the same purpose, as sudhir noted - the workflows around them are different. when a user selects a clipboard entry, most likely they would like to resume whatever they were doing before, and the old behaviour of closing the klipper menu worked very well for that. note that the new behaviour is also causing another issue - if you click the topmost entry, nothing happens. in the old klipper there was an indicator to show which entry is in the clipboard - now one can not be that sure. at first, i clicked the topmost entry a lot and wondered why nothing works :) i would also like to use this opportunity and say a huge thank you to klipper developers. despite my beef with this change, it is one awesome application that i use daily and if a klipper dev ends up in riga, latvia, poke me - i'd love to buy you a beer :) i even know a person who uses a different desktop environment, but still uses klipper in it. (sorry about the offtopic part, felt a strong need to express gratitude publicly) -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 93649] Separate configuration from history in Klipper's popup menu
https://bugs.kde.org/show_bug.cgi?id=93649 ric...@nakts.net changed: What|Removed |Added CC||ric...@nakts.net --- Comment #19 from ric...@nakts.net --- this seems to be finally solved in kde5 - unlikely to be worked on by anybody in kde4, thus i'd suggest closing this report -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 356421] can't search/filter right away in klipper menu
https://bugs.kde.org/show_bug.cgi?id=356421 Martin Gräßlin changed: What|Removed |Added CC||k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356419] Custom notification location is not remembered after restart
https://bugs.kde.org/show_bug.cgi?id=356419 Txutxifel changed: What|Removed |Added CC||jesa...@gmail.com --- Comment #1 from Txutxifel --- Same here, Opensuse 42.1, plasma 5.5.0, Frameworks 5.16 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 353325] Can't connect to jabber server which require forward secrecy
https://bugs.kde.org/show_bug.cgi?id=353325 --- Comment #3 from Andreas Schneider --- jabber.ccc.de works just fine with Pidgin but not with KTP, please try yourself ... -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 353325] Can't connect to jabber servers which require forward secrecy
https://bugs.kde.org/show_bug.cgi?id=353325 Andreas Schneider changed: What|Removed |Added Summary|Can't connect to jabber |Can't connect to jabber |server which require|servers which require |forward secrecy |forward secrecy -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 356422] New: Can not add a new element
https://bugs.kde.org/show_bug.cgi?id=356422 Bug ID: 356422 Summary: Can not add a new element Product: kmenuedit Version: 5.4.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: hans.ullr...@loop.de Dear maintainers, since KDE5 I am amissing the menu "hamradio" in kmenu. It would be not that problem, but I also can not a new element on top, only below the already existing elements. It would be nice, if you could add this feature. I believe, the configuration file for kmenu might also be able to be edited directly and I might try this, if you can point me to the required one. Also please add the menu "hamradio" again im kmenu, if possible. In LXDE it is still existent, but no more in KDE5 (aka plasma). Thank you for your efforts. Best regards Hans Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356423] New: Regression: Oxygen icon theme use Breeze icons for some programs
https://bugs.kde.org/show_bug.cgi?id=356423 Bug ID: 356423 Summary: Regression: Oxygen icon theme use Breeze icons for some programs Product: Oxygen Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: icons Assignee: n...@oxygen-icons.org Reporter: opensuse.lietuviu.ka...@gmail.com I much prefer Oxygen icons. Swithed to Oxygen theme in KDE Plasma 5.5.0. In desktop, some programs do not use default icons (like /\ for VLC ), but use Breeze icons. Reproducible: Always Steps to Reproduce: 1. Install fresh KDE Plasma 5.5.0. 2. Select Oxygen icons as default Actual Results: Desktop, programs menu show some Breeze theme icons. E.g. some rectangle (|>|) for VLC, instead of /\. I searched for icons and found, that used icons only exist in /usr/share/icons/breeze/apps/ Expected Results: KDE use default icons, like from /usr/share/pixmaps or /usr/share/icons/hicolor/ KDE Plasma 5.4 showed icons more correctly, so consider this as regression. Nothing help, nor deleting ~/.cache content, nor /tmp/*, nor /var/tmp/* . Seems like Breeze icons is somehow hardcoded. But for Oxygen, I suggest to use hicolor theme as premier fallback theme, not Breeze. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356423] Regression: Oxygen icon theme use Breeze icons for some programs
https://bugs.kde.org/show_bug.cgi?id=356423 --- Comment #1 from opensuse.lietuviu.ka...@gmail.com --- Created attachment 95946 --> https://bugs.kde.org/attachment.cgi?id=95946&action=edit Desktop with Oxygen icons + some Breeze -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356423] Regression: Oxygen icon theme use Breeze icons for some programs
https://bugs.kde.org/show_bug.cgi?id=356423 --- Comment #2 from opensuse.lietuviu.ka...@gmail.com --- Created attachment 95947 --> https://bugs.kde.org/attachment.cgi?id=95947&action=edit A bit better situation was in KDE Plasma 5.4 (less Breeze icons) -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356423] Regression: Oxygen icon theme use Breeze icons for some programs
https://bugs.kde.org/show_bug.cgi?id=356423 Paul changed: What|Removed |Added CC||pip@gmx.com --- Comment #3 from Paul --- It's not only Oxygen, it seems that _any_ non breeze icon theme now has part breeze icons shown. I reported the bug here: https://bugs.kde.org/show_bug.cgi?id=356064 a few days ago. A quick and dirty bodge that I've employed is to delete _all_ of the icons from the breeze icon set ( /usr/share/icons/breeze ) thus forcing any attempt to use them to revert to the fallback "inherits=" set in the (breeze) "index.theme"... ;) -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356423] Regression: Oxygen icon theme use Breeze icons for some programs
https://bugs.kde.org/show_bug.cgi?id=356423 opensuse.lietuviu.ka...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from opensuse.lietuviu.ka...@gmail.com --- @Paul Yes, I see *** This bug has been marked as a duplicate of bug 356064 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356064] Non Breeze themes now display some Breeze icons.
https://bugs.kde.org/show_bug.cgi?id=356064 opensuse.lietuviu.ka...@gmail.com changed: What|Removed |Added CC||opensuse.lietuviu.kalba@gma ||il.com --- Comment #2 from opensuse.lietuviu.ka...@gmail.com --- *** Bug 356423 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- screenshot? does wiping ~/.cache/plasma* fix it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356410] Crash during night when idle
https://bugs.kde.org/show_bug.cgi?id=356410 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 346517 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 346517] Plasmashell crashed after starting gparted
https://bugs.kde.org/show_bug.cgi?id=346517 David Edmundson changed: What|Removed |Added CC||hlov...@gmail.com --- Comment #29 from David Edmundson --- *** Bug 356410 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356408] Crash right after logging in
https://bugs.kde.org/show_bug.cgi?id=356408 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 355582 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355582] plasma crashes after disabling Laptop's screen
https://bugs.kde.org/show_bug.cgi?id=355582 David Edmundson changed: What|Removed |Added CC||san...@mathys.io --- Comment #4 from David Edmundson --- *** Bug 356408 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356402] Plasma restarted after unselecting several items to display in systemtray
https://bugs.kde.org/show_bug.cgi?id=356402 David Edmundson changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|mklape...@kde.org Component|general |Notifications -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355582] plasma crashes after disabling Laptop's screen
https://bugs.kde.org/show_bug.cgi?id=355582 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356394] Crash at some point while monitor power cycled
https://bugs.kde.org/show_bug.cgi?id=356394 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342763] Window List plasmoid crashes desktop shell
https://bugs.kde.org/show_bug.cgi?id=342763 David Edmundson changed: What|Removed |Added CC||estel...@elstel.org --- Comment #122 from David Edmundson --- *** Bug 356376 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349519] plasmashell occasionally crashes
https://bugs.kde.org/show_bug.cgi?id=349519 --- Comment #103 from David Edmundson --- *** Bug 356378 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356376] unstable plasmashell
https://bugs.kde.org/show_bug.cgi?id=356376 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 342763 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351507] Plasma crashed after enabling external monitors
https://bugs.kde.org/show_bug.cgi?id=351507 David Edmundson changed: What|Removed |Added CC||vychodil.hy...@gmail.com --- Comment #5 from David Edmundson --- *** Bug 356363 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356363] Plasma panels do not apears at primary output and then crash
https://bugs.kde.org/show_bug.cgi?id=356363 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 351507 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356378] Plasma crashed when starting music playing in Amarok from the system tray
https://bugs.kde.org/show_bug.cgi?id=356378 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- #7 0x7fd0888c4dcc in brw_clear (ctx=0x18652e8, mask=34) at ../../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:247 This is crashing in your graphic driver which we can't do much about. Please upgrade/downgrade your version of mesa. See information (including a workaround) in the linked report. *** This bug has been marked as a duplicate of bug 349519 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343283] Wrong cursor drawing with positive line spacing
https://bugs.kde.org/show_bug.cgi?id=343283 David Rosca changed: What|Removed |Added CC||now...@gmail.com --- Comment #8 from David Rosca --- Why is the cursor height shifted by one pixel? That way, if you have selected text right before the cursor, you will be able to distinguish the highlighted text and the cursor (it won't look as one highlighted line). This can be seen eg. in status line in less. I guess this is intended exactly for that reason, but I've checked xterm and gnome-terminal and both have the cursor height same as line height. Also I myself think it looks better if the cursor height is the same as line height. -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 350304] doesnt use next device when usb audio device unplugged
https://bugs.kde.org/show_bug.cgi?id=350304 Alejandro Villar changed: What|Removed |Added CC||alx5...@alx5000.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 --- Comment #3 from Robby Engelmann --- wiping .cache completely and creating a new user does not solve the issue -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 Robby Engelmann changed: What|Removed |Added CC||robby.engelm...@igfs-ev.de --- Comment #2 from Robby Engelmann --- Created attachment 95948 --> https://bugs.kde.org/attachment.cgi?id=95948&action=edit Notes Setting windows and lower right the transparent notes widget that should not be transparent -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 David Edmundson changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #4 from David Edmundson --- thanks -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 356420] Kopete crashed when closing conversation window
https://bugs.kde.org/show_bug.cgi?id=356420 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 355275 *** -- 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 Christoph Feck changed: What|Removed |Added CC||v...@pelcak.org --- Comment #30 from Christoph Feck --- *** Bug 356420 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 356396] Kopete crashed when chat window closed
https://bugs.kde.org/show_bug.cgi?id=356396 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 355275 *** -- 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 Christoph Feck changed: What|Removed |Added CC||semenukha+kdeb...@gmail.com --- Comment #31 from Christoph Feck --- *** Bug 356396 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 --- Comment #5 from David Edmundson --- it's working here, so I'm afraid I need to barrage you with questions Can I see your: ~/.config/plasmarc Do you have a file /usr/share/plasma/desktoptheme/default/notes.svgz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 --- Comment #6 from Robby Engelmann --- Created attachment 95949 --> https://bugs.kde.org/attachment.cgi?id=95949&action=edit plasmarc_robby -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356328] Moving the cursor and moving windows leaves drawing artefacts in with the Framebuffer backend
https://bugs.kde.org/show_bug.cgi?id=356328 --- Comment #10 from bluescreen_aven...@verizon.net --- Argh... Now I'm realizing it affects the qpainter backend, not just on the Framebuffer, but on the Wayland and X11 backends too -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 --- Comment #7 from Robby Engelmann --- robby5@nohostname:/usr/share/plasma/desktoptheme/default> ls -a . .. colors dialogs icons metadata.desktop opaque translucent widgets robby5@nohostname:/usr/share/plasma/desktoptheme/default> cd widgets/ robby5@nohostname:/usr/share/plasma/desktoptheme/default/widgets> ls actionbutton.svgz configuration-icons.svgz plot-background.svgz action-overlays.svgz containment-controls.svgz scrollbar.svgz analog_meter.svgz dragger.svgz scrollwidget.svgz arrows.svgzframe.svgz slider.svgz background.svgzglowbar.svgz tabbar.svgz bar_meter_horizontal.svgz lineedit.svgz tasks.svgz bar_meter_vertical.svgzline.svgz timer.svgz branding.svgz listitem.svgz toolbar.svgz busywidget.svgzmedia-delegate.svgztooltip.svgz button.svgzmonitor.svgz translucentbackground.svgz calendar.svgz pager.svgz viewitem.svgz checkmarks.svgzpanel-background.svgz clock.svgz picker.svgz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356409] Plasma fails to start when using old video driver
https://bugs.kde.org/show_bug.cgi?id=356409 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from David Edmundson --- Well, that window isn't using openGL, plasma does. You can try running with QT_XCB_FORCE_SOFTWARE_OPENGL set. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 --- Comment #8 from Robby Engelmann --- I could not see a notes.svgz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 --- Comment #9 from David Edmundson --- OK, well there's our problem :) It should be in plasma-framework. can you try reinstalling it? Also I'll poke some openSuSE people. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356328] Moving the cursor and moving windows leaves drawing artefacts in with the Framebuffer backend
https://bugs.kde.org/show_bug.cgi?id=356328 --- Comment #11 from bluescreen_aven...@verizon.net --- Created attachment 95950 --> https://bugs.kde.org/attachment.cgi?id=95950&action=edit the drawing glitches affecting qpainter in the wayland backend This only effects when the qpainter render is being used, for the wayland (and x11 backend) It seems qpainter also has a weird transparency issue in the xterm text going through the nested window... It does not affect the opengl backend -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355889] Active focus hardly visible
https://bugs.kde.org/show_bug.cgi?id=355889 --- Comment #3 from Kai Uwe Broulik --- The Plasma theme. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from David Edmundson --- Update. We fucked up. [13:20] d_ed: well it is problem on our (plasma) end, file from kdeplasma-addons was moved to plasma-framework [13:20] and plasma-framework didn't get relase [13:20] d_ed: frameworks 5.17 will fix it™ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356417] Notes widget broke since upgrade to plasma 5.5
https://bugs.kde.org/show_bug.cgi?id=356417 --- Comment #11 from Robby Engelmann --- thanks, actually was my first thought :-). Thanks for finding out. I filed two other bugs against plasma today, perhaps they may also be resolved after 5.17 release. I often have to click multiple times in order to get panel items activated and the custom notification location is not remembered after reboot. hmmm. I will see when somebody will have a look into these bugs... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 346768] After login only one tab is present, when several tabs where opened before logout.
https://bugs.kde.org/show_bug.cgi?id=346768 Daniel Scharrer changed: What|Removed |Added CC||dan...@constexpr.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 337155] Please allow user to sort connections in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=337155 carmelo.ianne...@gmail.com changed: What|Removed |Added CC||carmelo.ianne...@gmail.com --- Comment #3 from carmelo.ianne...@gmail.com --- Hi, could you give any hint on a workaround and/or which source files to look at if someone wanted to try patch it on his own? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356064] Non Breeze themes now display some Breeze icons.
https://bugs.kde.org/show_bug.cgi?id=356064 --- Comment #3 from opensuse.lietuviu.ka...@gmail.com --- Please for non-Breeze themes respect specifications: according http://standards.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html , the default fallback icon theme must be "hicolor". I.e. as fallback, please use /usr/share/icons/hicolor/ and /usr/share/pixmaps -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356064] Non Breeze themes now display some Breeze icons.
https://bugs.kde.org/show_bug.cgi?id=356064 --- Comment #4 from opensuse.lietuviu.ka...@gmail.com --- Created attachment 95951 --> https://bugs.kde.org/attachment.cgi?id=95951&action=edit mixed icons -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 345403] "Terminal Size" setting in profile ignored
https://bugs.kde.org/show_bug.cgi?id=345403 --- Comment #17 from Daniel Scharrer --- Created attachment 95952 --> https://bugs.kde.org/attachment.cgi?id=95952&action=edit Workaround to force the terminal size from the profile I'm not familiar enough with the code to provide a proper fix, but at least this patch makes konsole usable again for me. It breaks the "Use current window size on next startup" option though. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 337155] Please allow user to sort connections in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=337155 --- Comment #4 from Jan Grulich --- You can change this in libs/models/appletproxymodel.cpp. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356064] Non Breeze themes now display some Breeze icons.
https://bugs.kde.org/show_bug.cgi?id=356064 opensuse.lietuviu.ka...@gmail.com changed: What|Removed |Added Attachment #95951|mixed icons |mixed icons in KDE Plasma description||5.4 Attachment #95951|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356424] New: mtp URI missing forward slash ( / )
https://bugs.kde.org/show_bug.cgi?id=356424 Bug ID: 356424 Summary: mtp URI missing forward slash ( / ) Product: dolphin Version: 15.08.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: damonly...@gmail.com The URI for mtp devices is invalid. For example, Dolphin displays this: mtp:/Nexus 4/Internal storage/ The correct value is in this case mtp://Nexus 4/Internal storage/ Reproducible: Always Steps to Reproduce: 1. Open an MTP device, e.g. cellphone 2. Browse the device contents 3. Ctrl-l to to go the location bar -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot
https://bugs.kde.org/show_bug.cgi?id=343518 Daniel Scharrer changed: What|Removed |Added CC||dan...@constexpr.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349481] konsole session sometimes is not saved into ~/.config/ksmserverrc on logout
https://bugs.kde.org/show_bug.cgi?id=349481 Daniel Scharrer changed: What|Removed |Added CC||dan...@constexpr.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356064] Non Breeze themes now display some Breeze icons.
https://bugs.kde.org/show_bug.cgi?id=356064 --- Comment #5 from opensuse.lietuviu.ka...@gmail.com --- Created attachment 95953 --> https://bugs.kde.org/attachment.cgi?id=95953&action=edit Mixed icons in KDE Plasma 5.5.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356425] New: Dolphin browsing an MTP device precludes libgphoto2's access to it until dolphin is closed
https://bugs.kde.org/show_bug.cgi?id=356425 Bug ID: 356425 Summary: Dolphin browsing an MTP device precludes libgphoto2's access to it until dolphin is closed Product: dolphin Version: 15.08.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: damonly...@gmail.com When Dolphin has accessed the contents of an MTP device, libgphoto2 is unable to access the device, even if Dolphin browsing another location e.g. the user's home directory. The device becomes free only when Dolphin is closed. Additionally, there is no way for the user to do the equivalent of a virtual "unmount" to ask Dolphin/Kdeinit5 via the GUI to relinquish exclusive control of the device. There also appears to be no way using the command line either. I tried solid-hardware unmount udi (supplying the correct UDI), but solid-hardware reported the MTP device 'does not have the interface StorageAccess". Reproducible: Always Steps to Reproduce: 1. To confirm the MTP device is accessible by libgphoto2, plug in an unlocked android 4.0 + phone (for example), and from a terminal execute gphoto2 --list-folders That should work. 2. Open Dolphin and browse some folders on the phone. 3. Repeat step 1 while Dolphin is open. It fails. It makes no difference if the device is browsed in a different Dolphin tab. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356398] migrated kickofff favorites include only last item
https://bugs.kde.org/show_bug.cgi?id=356398 --- Comment #2 from Rex Dieter --- Would it make sense also to rename obsolete_kickoffrc.js to force it to run again for folks who used the prior buggy one? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 323337] Kdevelop crashes on reformat wrong preprocessor macro
https://bugs.kde.org/show_bug.cgi?id=323337 amanku changed: What|Removed |Added CC||kumarama...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 356426] New: krunner crashed when system under heavy load
https://bugs.kde.org/show_bug.cgi?id=356426 Bug ID: 356426 Summary: krunner crashed when system under heavy load Product: krunner Version: 5.4.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: alexey@gmail.com Qt Version: 5.5.1 Operating System: Linux 4.0.5-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: opened krunner using a keyboard shortcut, typed in "smplayer" (usually this always works fine) then the crash happened - Unusual behavior I noticed: My system was heavily loaded. Disk was very busy copying lots of files (using dolphin) and VirtualBox was running, compiling updates for virtual Gentoo. CPU was busy up to 98% sometimes Reproducible: Sometimes -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f4a03f8c800 (LWP 635))] Thread 16 (Thread 0x7f4a01c0e700 (LWP 641)): #0 0x7f4a1272027d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f4a11baa360 in _xcb_conn_wait (c=0x1a64b80, cond=0x1a64bc0, vector=0x0, count=0x0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459 #2 0x7f4a11bac837 in xcb_wait_for_event (c=0x1a64b80) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693 #3 0x7f4a03b85100 in QXcbEventReader::run (this=0x1a72ce0) at qxcbconnection.cpp:1229 #4 0x7f4a12e12006 in QThreadPrivate::start (arg=0x1a72ce0) at thread/qthread_unix.cpp:331 #5 0x7f4a1082e326 in start_thread (arg=0x7f4a01c0e700) at pthread_create.c:333 #6 0x7f4a1272914d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f49f8c61700 (LWP 680)): #0 g_source_iter_clear (iter=0x7f49f4000990) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:938 #1 0x7f4a0e864d6c in g_main_context_check (context=0x7f49f4000990, max_priority=2147483647, fds=0x7f49f4003070, n_fds=1) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3714 #2 0x7f4a0e864faa in g_main_context_iterate (context=0x7f49f4000990, block=1, dispatch=1, self=0x1ab5100) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3805 #3 0x7f4a0e865097 in g_main_context_iteration (context=0x7f49f4000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3869 #4 0x7f4a130b8006 in QEventDispatcherGlib::processEvents (this=0x7f49f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7f4a1303c558 in QEventLoop::processEvents (this=0x7f49f8c60d70, flags=...) at kernel/qeventloop.cpp:128 #6 0x7f4a1303c82c in QEventLoop::exec (this=0x7f49f8c60d70, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f4a12e0ac83 in QThread::exec (this=0x1c67890) at thread/qthread.cpp:503 #8 0x7f4a150c9b2b in QQmlThreadPrivate::run (this=0x1c67890) at qml/ftw/qqmlthread.cpp:141 #9 0x7f4a12e12006 in QThreadPrivate::start (arg=0x1c67890) at thread/qthread_unix.cpp:331 #10 0x7f4a1082e326 in start_thread (arg=0x7f49f8c61700) at pthread_create.c:333 #11 0x7f4a1272914d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f49f02db700 (LWP 20226)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f4a11baa2d0 in _xcb_conn_wait (c=0x1a64b80, cond=0x7f49f02d7fd0, vector=0x0, count=0x0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:427 #2 0x7f4a11bac235 in wait_for_reply (c=0x1a64b80, request=4385, e=0x7f49f02d8090) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:516 #3 0x7f4a11bac365 in xcb_wait_for_reply (c=0x1a64b80, request=4385, e=0x7f49f02d8090) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:546 #4 0x7f4a11e1919a in _XReply (dpy=0x1a637c0, rep=0x7f49f02d80f0, extra=0, discard=0) at /var/tmp/portage/x11-libs/libX11-1.6.3/work/libX11-1.6.3/src/xcb_io.c:602 #5 0x7f4a0f890f0d in ?? () from /usr/lib64/opengl/nvidia/lib/libGL.so.1 #6 0x7f4a0f860abe in ?? () from /usr/lib64/opengl/nvidia/lib/libGL.so.1 #7 0x7f4a0a762379 in ?? () from /usr/lib64/libnvidia-glcore.so.355.11 #8 0x7f4a0a7b9d74 in ?? () from /usr/lib64/libnvidia-glcore.so.355.11 #9 0x7f4a0a7c4e45 in ?? () from /usr/lib64/libnvidia-glcore.so.355.11 #10 0x7f4a0a71f735 in ?? () from /usr/lib64/libnvidia-glcore.so.355.11 #11 0x7f4a0a3a57e0 in ?? () from /usr/lib64/libnvidia-glcore.so.355.11 #12 0x7f4a0a41c986 in ?? () from /usr/lib64/libnvidia-glcore.so
[plasmashell] [Bug 356398] migrated kickofff favorites include only last item
https://bugs.kde.org/show_bug.cgi?id=356398 --- Comment #3 from Eike Hein --- I considered that, but it would undo any manual fixups, too. Not sure. We might have caught it early enough? I also mailed the distro/packager list about it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356398] migrated kickofff favorites include only last item
https://bugs.kde.org/show_bug.cgi?id=356398 --- Comment #4 from Rex Dieter --- OK, I was just implementing that in our (fedora) packaging to avoid having to tell all testers of workarounds, thought it may make sense upstream too. But, I can see doing it upstream may make less sense (since many 5.5.0 users won't see it until 5.5.1 lands) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356328] Moving the cursor and moving windows leaves drawing artefacts in with the Framebuffer backend
https://bugs.kde.org/show_bug.cgi?id=356328 --- Comment #12 from Martin Gräßlin --- beautiful :-) But actually I'm glad that it's a generic issue and not just on DRM -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 356427] New: Amarok will not start
https://bugs.kde.org/show_bug.cgi?id=356427 Bug ID: 356427 Summary: Amarok will not start Product: amarok Version: 2.8.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: chippypr...@gmail.com Application: amarok (2.8.0) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.6-2-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Trying to open a file from an external drive Previously to this crash Amarok would find files but not play them - Custom settings of the application: Clean install of Opensuse with additional repositries for packman, google-chrome-stable, steam http://software.opensuse.org/ymp/openSUSE:Leap:42.1:NonFree/standard/steam.ymp?base=openSUSE%3ALeap%3A42.1&query=steam, and multimedia codecs found here http://opensuse-community.org/codecs-kde.ymp The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Bus error Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1f59f48800 (LWP 18058))] Thread 17 (Thread 0x7f1f37c68700 (LWP 18061)): #0 0x7f1f56ca6789 in syscall () from /lib64/libc.so.6 #1 0x7f1f5113ca1c in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f31fbfacd in ?? () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so #3 0x7f1f47f96279 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #4 0x7f1f5112050c in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1f5111fb85 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #7 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f1f361e7700 (LWP 18062)): #0 0x7f1f56ca6789 in syscall () from /lib64/libc.so.6 #1 0x7f1f5113ca1c in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f31fbfacd in ?? () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so #3 0x7f1f47f96279 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #4 0x7f1f5112050c in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1f5111fb85 in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #7 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f1f2bfff700 (LWP 18063)): #0 0x7f1f54ded408 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1f33b54e2a in ?? () from /usr/lib64/libmysqld.so.18 #2 0x7f1f33b4d236 in ?? () from /usr/lib64/libmysqld.so.18 #3 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f1f2b7fe700 (LWP 18064)): #0 0x7f1f54ded408 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1f572f6c64 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x7f1f58fb817e in AbstractDirectoryWatcher::run() () from /usr/lib64/libamaroklib.so.1 #3 0x7f1f53ee9542 in ?? () from /usr/lib64/libthreadweaver.so.4 #4 0x7f1f53ee96fe in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) () from /usr/lib64/libthreadweaver.so.4 #5 0x7f1f53ee8f4b in ThreadWeaver::Thread::run() () from /usr/lib64/libthreadweaver.so.4 #6 0x7f1f572f679f in ?? () from /usr/lib64/libQtCore.so.4 #7 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f1f2affd700 (LWP 18065)): #0 0x7f1f56ca23cd in poll () from /lib64/libc.so.6 #1 0x7f1f510fabe4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1f510facec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1f574250de in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #4 0x7f1f573f6e6f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #5 0x7f1f573f7165 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #6 0x7f1f572f40bf in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x7f1f573d8783 in ?? () from /usr/lib64/libQtCore.so.4 #8 0x7f1f572f679f in ?? () from /usr/lib64/libQtCore.so.4 #9 0x7f1f54de90a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7f1f56caa7fd in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f1f298a6700 (LWP 18066)): #0 0x7f1f54ded05f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1f572f6c86 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x7f1f53ee76fc in ?? () from /usr/lib64/libthreadweaver.so.4 #3 0x7f1f53eea193 in ?? () from /usr/lib64/libthread
[plasmashell] [Bug 356428] New: Plasmashell crash when minimizing app and then hovering mouse over taskmanager
https://bugs.kde.org/show_bug.cgi?id=356428 Bug ID: 356428 Summary: Plasmashell crash when minimizing app and then hovering mouse over taskmanager Product: plasmashell Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: noeero...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.0) Qt Version: 5.5.1 Operating System: Linux 4.3.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20151124) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I minimized and app, then hovered the mouse over a launcher on the task manager. Only seems to happen "randomly" and it doesn't seem to matter what app gets minimized. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f56651ea8c0 (LWP 13402))] Thread 7 (Thread 0x7f564e753700 (LWP 13405)): #0 0x7f565e78d20d in poll () at /lib64/libc.so.6 #1 0x7f566364a432 in () at /usr/lib64/libxcb.so.1 #2 0x7f566364c007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f56508a6e29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f565ee7e94f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f565df944a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f565e795b9d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f564b8b7700 (LWP 13417)): #0 0x7f565e78d20d in poll () at /lib64/libc.so.6 #1 0x7f565ae84264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f565ae8436c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f565f0a352b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f565f04d63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f565ee79b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f56621259a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f565ee7e94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f565df944a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f565e795b9d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f5641dcb700 (LWP 13419)): #0 0x7f565df9a07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5648852d5a in () at /usr/lib64/dri/r600_dri.so #2 0x7f5648852587 in () at /usr/lib64/dri/r600_dri.so #3 0x7f565df944a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f565e795b9d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f563be62700 (LWP 13420)): #0 0x7f565e78d20d in poll () at /lib64/libc.so.6 #1 0x7f565ae84264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f565ae8436c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f565f0a352b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f565f04d63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f565ee79b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f56621259a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f565ee7e94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f565df944a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f565e795b9d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f563a60a700 (LWP 13421)): #0 0x7f565e78d20d in poll () at /lib64/libc.so.6 #1 0x7f565ae84264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f565ae8436c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f565f0a352b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f565f04d63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f565ee79b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f56621259a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f565ee7e94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f565df944a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f565e795b9d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f5638c8a700 (LWP 13424)): #0 0x7f565df9a07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f56648d6a84 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f56648d6ac9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f565df944a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f565e795b9d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f56651ea8c0 (LWP 13402)): [KCrash Handler] #6 0x7f56633c4791 in Plasma::Applet::pluginInfo() const () at /usr/lib64/libKF5Plasma.so.5 #7 0x0045c9ed in ShellCorona::executeSetupPlasmoidScript(Plasma::Containment*, Plasma::Applet*) () #8 0x7
