[plasmashell] [Bug 375113] Plasmashell crashes when selecting a status widget with "Status and Notifications" open.
https://bugs.kde.org/show_bug.cgi?id=375113 Marco Martin changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- doens't seem to happen anymore -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 375230] New: Issue with upload image
https://bugs.kde.org/show_bug.cgi?id=375230 Bug ID: 375230 Summary: Issue with upload image Product: choqok Version: 1.6 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: Twitter Assignee: mehrdad.mom...@gmail.com Reporter: elavdevelo...@gmail.com CC: scarp...@kde.org Target Milestone: --- Created attachment 103475 --> https://bugs.kde.org/attachment.cgi?id=103475&action=edit Issue in Choqok When a try attach an image in Choqok: Creating the new post failed, with error: Missing or invalid url parameter. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 375176] No document preview (.odt, .doc, .docx, .ods)
https://bugs.kde.org/show_bug.cgi?id=375176 --- Comment #2 from Benjamin --- Okay, I tried to find the new version on kubuntu backport ppa, but couldn't find them so far. Is there any date, when it will be released, or any other way to install the 3.0 on kubuntu 16.04? Thanks -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 375051] New scroll bar width: cofiguration missing and inconsistent with GTK theme
https://bugs.kde.org/show_bug.cgi?id=375051 --- Comment #2 from Fuchs --- (In reply to Hugo Pereira Da Costa from comment #1) > Hi, Hi! > thanks for reporting. You're welcome. > Despite of what the commit says (sorry we did not update), and after long > discussions on phabricator (https://phabricator.kde.org/D3210), it was > decided not to make the scrollbar visible width configurable. > The rationale is that > - we avoid the added code complexity understandable. > - the default small width is good Heavily disagree, but that's a matter of personal preference, so not really discussable > - the hit area is unchanged with respect to the previous design (it is > larger than the visible width of the handle), so that no usability is lost. actually making it larger than visible is a massive usability issue. If you disabled animations and thus it is always visible, grabbing the mouse event when near but not on the scrollbar is against user expectations and thus a big UX flaw. Say I have a file view in dolphin and I want to start selecting multiple items by drawing a rectangle. If I started close to a scrollbar, it might activate the scrolling instead, even though the mouse was not over it. That would be very bad. > Now, that this makes the scrollbar inconsistent with gtk should be fixed of > course. > Reassigning to the gtk theme (of which I am not the maintainer and for which > I lack the skills to fix) I shall patch both to the old width locally, then. > Best, > > Hugo Kind regards, Christian -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375228] Meta doesn't toggle application launcher after laptop woken up from suspend.
https://bugs.kde.org/show_bug.cgi?id=375228 Nikolai changed: What|Removed |Added Summary|Meta not togles application |Meta doesn't toggle |launcher after laptop woken |application launcher after |up from suspend.|laptop woken up from ||suspend. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375229] New: Non-storage of Desktop icons across sessions
https://bugs.kde.org/show_bug.cgi?id=375229 Bug ID: 375229 Summary: Non-storage of Desktop icons across sessions Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: udip...@gmail.com Target Milestone: 1.0 [This is a Plasma 5 thing, it always worked for me on Plasma 4.] To start with: I love, and use, the Desktop Search and Launch for many icons, to start programmes, do settings, etc. I have arranged those icons in a specific manner across my screen (1920x1200). I even locked the widgets. Sometimes, I am restricted to the internal screen, 1440xsomething. Then the nicely arranged icons get pushed to the left and top; not scaled. And when I return to my larger screen, the icons are still there, squeezed to the left and top in an ugly manner. No question, the expected behaviour is for them to return to the original settings. I can't and wouldn't want to redo all these twice a week; I think this is understandable. On Plasma 4 this problem did not occur. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375228] New: Meta not togles application launcher after laptop woken up from suspend.
https://bugs.kde.org/show_bug.cgi?id=375228 Bug ID: 375228 Summary: Meta not togles application launcher after laptop woken up from suspend. Product: plasmashell Version: 5.8.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: d...@cyclinggeorgian.com CC: plasma-b...@kde.org Target Milestone: 1.0 When laptop suspended (ram) and woken up meta key not toggling application launcher any more, only Alt+F1 works. Steps: 1. Toggle application menu by pressing "meta" key (it works, nice). 2. put your laptop to sleep (suspend to ram). 3. wake it up and try to open application launcher by pressing "meta" key. It doesn't work any more...only Alt+F1 works. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375122] Painting with Krita all day today and noticed a few bugs.
https://bugs.kde.org/show_bug.cgi?id=375122 --- Comment #4 from edgar.ej.mercad...@gmail.com --- I forgot to mention that I've been on Krita 3.1.1 I tested 2.8... only got 5 min into it before I realized it isn't for me. I couldn't open any of the files I created in 3.1.1. I tried looking into the nightly build, but that seems over my head. So back to testing 3.1.1 it is. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 375045] Notification about active network appears every time I start a plasma session
https://bugs.kde.org/show_bug.cgi?id=375045 --- Comment #4 from Dr. Chapatin --- This behavior is annoying. I think the better behavior is show the notication only when the user enables the network manually. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 --- Comment #4 from Elvis Angelaccio --- Ah right, boost likes code in headers... But then again, if a cmake project is using boost, it can just remove -fno-operator-names from the CMAKE_CXX_FLAGS variable. -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195
--- Comment #3 from Kevin Funk ---
Okay, external projects (here: boost) are indeed a problem...:
/usr/include/boost/graph/transitive_reduction.hpp:108:25: error: unknown type
name 'not'
if( not edge_in_closure[i][j] ) {
^
/usr/include/boost/graph/transitive_reduction.hpp:108:29: error: variable
declaration in condition must have an initializer
if( not edge_in_closure[i][j] ) {
^
/usr/include/boost/graph/transitive_reduction.hpp:110:29: error: unknown type
name 'not'
if( not edge_in_closure[i][k] ) {
^
/usr/include/boost/graph/transitive_reduction.hpp:110:33: error: variable
declaration in condition must have an initializer
if( not edge_in_closure[i][k] ) {
^
4 errors generated.
--
You are receiving this mail because:
You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 Kevin Funk changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Kevin Funk --- Note: All issues in Digikam + libkdcraw are resolved already. I think there's a real benefit to use this flag globally (as it inhibits us writing non-cross-platform code). I'll keep this open for now, for other opinions -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375122] Painting with Krita all day today and noticed a few bugs.
https://bugs.kde.org/show_bug.cgi?id=375122 --- Comment #3 from edgar.ej.mercad...@gmail.com --- I totally forgot to list down my pc specs: sony vaio duo 11 intel i7 3rd gen 8g memory intel hd 4400 windows 10 home I didn't noticed the weird aberrations as much yesterday, but I did noticed horrible lag once I started working with bigger resolutions and Krita crashed on me once. I disabled opengl and that helped a little bit as well as playing around with the undo stack. The lag was still apparent though :(. I read somewhere that going back to an earlier version of Krita for windows would help. Should I try this approach? -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 375227] New: Dragon Player Crashes on Video
https://bugs.kde.org/show_bug.cgi?id=375227 Bug ID: 375227 Summary: Dragon Player Crashes on Video Product: dragonplayer Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: ol...@quickaudio.com CC: myr...@kde.org Target Milestone: --- Application: dragon (16.08.3) Qt Version: 5.6.2 Frameworks Version: 5.29.0 Operating System: Linux 4.8.16-200.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: I was playing back a video, after playing many short videos in a row and checking the first second or two of each one. The crash can be reproduced sometimes. -- Backtrace: Application: Dragon Player (dragon), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1ecef57940 (LWP 22211))] Thread 3 (Thread 0x7f1ebf6e4700 (LWP 22213)): #0 0x7f1edd44556d in poll () at /lib64/libc.so.6 #1 0x7f1ed98bfa06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f1ed98bfb1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f1ede24b75b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f1ede1fa81a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f1ede059353 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f1ede452559 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f1ede05d9ba in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f1edb53b5ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f1edd4510ed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f1ec5650700 (LWP 22212)): #0 0x7f1edd44556d in poll () at /lib64/libc.so.6 #1 0x7f1eda405f80 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f1eda407b79 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f1ec839bf99 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f1ede05d9ba in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f1edb53b5ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f1edd4510ed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f1ecef57940 (LWP 22211)): [KCrash Handler] #6 0x55699018b6b0 in () #7 0x55698e99abbe in Dragon::MainWindow::load(QUrl const&) () #8 0x55698e9a090b in Dragon::MainWindow::open(QUrl const&) () #9 0x55698e997d25 in Dragon::PlayerApplication::newInstance(bool, QList const&) () #10 0x55698e9984de in Dragon::PlayerApplication::slotActivateRequested(QStringList const&, QString const&) () #11 0x7f1ede2240fc in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #12 0x7f1ee05e53c7 in KDBusService::activateRequested(QStringList const&, QString const&) () at /lib64/libKF5DBusAddons.so.5 #13 0x7f1ee05dfb24 in KDBusService::CommandLine(QStringList const&, QString const&, QMap const&) () at /lib64/libKF5DBusAddons.so.5 #14 0x7f1ee05e522d in KDBusServiceExtensionsAdaptor::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.0] () at /lib64/libKF5DBusAddons.so.5 #15 0x7f1ee05e5347 in KDBusServiceExtensionsAdaptor::qt_metacall(QMetaObject::Call, int, void**) () at /lib64/libKF5DBusAddons.so.5 #16 0x7f1ede45dc78 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () at /lib64/libQt5DBus.so.5 #17 0x7f1ede462198 in QDBusConnectionPrivate::activateCall(QObject*, int, QDBusMessage const&) () at /lib64/libQt5DBus.so.5 #18 0x7f1ede462864 in QDBusConnectionPrivate::activateObject(QDBusConnectionPrivate::ObjectTreeNode&, QDBusMessage const&, int) () at /lib64/libQt5DBus.so.5 #19 0x7f1ede4650fe in QDBusActivateObjectEvent::placeMetaCall(QObject*) () at /lib64/libQt5DBus.so.5 #20 0x7f1ede224e19 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #21 0x7f1edeb13e4c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #22 0x7f1edeb1932f in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #23 0x7f1ede1fb9da in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #24 0x7f1ede1fda8f in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #25 0x7f1ede24b6c3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #26 0x7f1ed98bf6ba in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #27 0x7f1ed98bfa70 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #28 0x7f1ed98bfb1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #29
[kmail2] [Bug 297930] Kmail hangs on "Retrieving folder contents ... please wait"
https://bugs.kde.org/show_bug.cgi?id=297930 sedrubal changed: What|Removed |Added CC||k...@sedrubal.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375226] New: Disappearing pinned icons
https://bugs.kde.org/show_bug.cgi?id=375226 Bug ID: 375226 Summary: Disappearing pinned icons Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: alexander.l...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Bug 365617 fixed this issue for Chromium, but the problem persists with other applications. Applications where the pinned icons still disappear are: - keepassx - pycharm there may be others, but these are the ones i use and found. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375225] New: Discover started to crash - Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=375225 Bug ID: 375225 Summary: Discover started to crash - Segmentation fault Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kont...@soee.pl Target Milestone: --- Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f79057958c0 (LWP 9785))] Thread 43 (Thread 0x7f782bfff700 (LWP 9829)): #0 0x7f7901ab8b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f78fd0a739c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78fd0a7722 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7888555916 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f78fd0cdbc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f78fef4d6ba in start_thread (arg=0x7f782bfff700) at pthread_create.c:333 #6 0x7f7901ac482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 42 (Thread 0x7f7848dbd700 (LWP 9828)): #0 0x7f7901ab469d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f78fd0ea740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78fd0a6e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78fd0a7340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f78fd0a74ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f78fd0a74e9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f78fd0cdbc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f78fef4d6ba in start_thread (arg=0x7f7848dbd700) at pthread_create.c:333 #8 0x7f7901ac482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 41 (Thread 0x7f78497fa700 (LWP 9827)): #0 0x7f79024b8009 in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f79026eb98f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f78fd0a692d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78fd0a72cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f78fd0a74ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f79026ec23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7902696cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79024bbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f79024c0b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f78fef4d6ba in start_thread (arg=0x7f78497fa700) at pthread_create.c:333 #10 0x7f7901ac482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 40 (Thread 0x7f7849ffb700 (LWP 9826)): #0 0x7f79026eb9c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f78fd0a692d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78fd0a72cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78fd0a74ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f79026ec23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7902696cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79024bbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79024c0b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f78fef4d6ba in start_thread (arg=0x7f7849ffb700) at pthread_create.c:333 #9 0x7f7901ac482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 39 (Thread 0x7f784a7fc700 (LWP 9825)): #0 0x7f78fd0ebac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f78fd0a6ddc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78fd0a7340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78fd0a74ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f79026ec23b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7902696cea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79024bbfb4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79024c0b98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f78fef4d6ba in start_thread (arg=0x7f784a7fc700) at pthread_create.c:333 #9 0x7f7901ac482d in clone () at ../sysdeps/unix/
[plasmashell] [Bug 366578] Some tray icons have black background sometimes
https://bugs.kde.org/show_bug.cgi?id=366578 Marco Martin changed: What|Removed |Added Component|System Tray |XembedSNIProxy -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 375224] New: C# importer crashes on enums when they're used before being defined
https://bugs.kde.org/show_bug.cgi?id=375224
Bug ID: 375224
Summary: C# importer crashes on enums when they're used before
being defined
Product: umbrello
Version: unspecified
Platform: unspecified
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: umbrello-de...@kde.org
Reporter: badpoint...@gmail.com
Target Milestone: ---
There's no concept of forward declarations in C#, so it's allowed to use enum
types before they're defined but when I try to import this C# code,
umbrello crashes.
namespace TestNamespace
{
public class TestClass
{
void Dispatch(COMMAND com);
}
public enum COMMAND
{
OPTION1,
OPTION2,
OPTION3
}
}
If I rearange the code like this, it works fine
namespace TestNamespace
{
public enum COMMAND
{
OPTION1,
OPTION2,
OPTION3
}
public class TestClass
{
void Dispatch(COMMAND com);
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[umbrello] [Bug 375223] New: C# importer doesn't support properties
https://bugs.kde.org/show_bug.cgi?id=375223
Bug ID: 375223
Summary: C# importer doesn't support properties
Product: umbrello
Version: unspecified
Platform: unspecified
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: umbrello-de...@kde.org
Reporter: badpoint...@gmail.com
Target Milestone: ---
C# importer fails to parse property1 properly and doesn't import property2 and
property3 at all
public class TestClass
{
public int property1 { get; set; }
public int property2 { get; set; }
public int property3 { get; set; }
}
--
You are receiving this mail because:
You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 --- Comment #1 from Elvis Angelaccio --- Those failing builds can be fixed with the following cmake trick: https://phabricator.kde.org/D3850#78322 Boost should do something similar in their build system, I suppose... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345012] Shorcuts assigned to a plasmoid inside the systemtray don't work if plasmashell was started in a locked state
https://bugs.kde.org/show_bug.cgi?id=345012 Marco Martin changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||notm...@gmail.com --- Comment #2 from Marco Martin --- doesn't happen anymore with the new systray -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 375051] New scroll bar width: cofiguration missing and inconsistent with GTK theme
https://bugs.kde.org/show_bug.cgi?id=375051 Hugo Pereira Da Costa changed: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com Assignee|hugo.pereira.da.costa@gmail |scionicspec...@gmail.com |.com| Component|QStyle |gtk theme --- Comment #1 from Hugo Pereira Da Costa --- Hi, thanks for reporting. Despite of what the commit says (sorry we did not update), and after long discussions on phabricator (https://phabricator.kde.org/D3210), it was decided not to make the scrollbar visible width configurable. The rationale is that - we avoid the added code complexity - the default small width is good - the hit area is unchanged with respect to the previous design (it is larger than the visible width of the handle), so that no usability is lost. Now, that this makes the scrollbar inconsistent with gtk should be fixed of course. Reassigning to the gtk theme (of which I am not the maintainer and for which I lack the skills to fix) Best, Hugo -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 375045] Notification about active network appears every time I start a plasma session
https://bugs.kde.org/show_bug.cgi?id=375045 Jan Grulich changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #3 from Jan Grulich --- Closing as it seems to be correct behaviour. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 375209] Ark crash when drag&drop to expand a zip file
https://bugs.kde.org/show_bug.cgi?id=375209 Elvis Angelaccio changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |elvis.angelac...@kde.org Product|dolphin |ark Status|UNCONFIRMED |RESOLVED CC||elvis.angelac...@kde.org, ||rthoms...@gmail.com Component|general |general Resolution|--- |UNMAINTAINED --- Comment #1 from Elvis Angelaccio --- You're using a very old version of Ark. Please upgrade to a supported release. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 375115] Comic Strip 'Add Comic' Button crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=375115 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Version|unspecified |5.8.5 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 375115] Comic Strip 'Add Comic' Button crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=375115 David Edmundson changed: What|Removed |Added Version|5.8.5 |unspecified Component|general |Comic Applet Target Milestone|1.0 |--- Product|plasmashell |kdeplasma-addons Assignee|k...@davidedmundson.co.uk|notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375222] New: Add filter bar or "filter as you type" to Folder View widget
https://bugs.kde.org/show_bug.cgi?id=375222 Bug ID: 375222 Summary: Add filter bar or "filter as you type" to Folder View widget Product: plasmashell Version: 5.8.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: nortex...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 It would be nice to have a filter bar or a method of filtering-as-you-type when opening a folder view widget. Suppose I have a widget that opens folder X which contains a lot of files. It would be nice after opening/focusing the folder view widget if one could start typing to filter for the desired file. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 375221] New: Kontact crashes after deleting multiple message tags ("Nachrichten-Markierungen")
https://bugs.kde.org/show_bug.cgi?id=375221
Bug ID: 375221
Summary: Kontact crashes after deleting multiple message tags
("Nachrichten-Markierungen")
Product: kontact
Version: 5.2.3
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: michael.br...@uni-muenster.de
Target Milestone: ---
Application: kontact (5.2.3)
Qt Version: 5.6.1
Frameworks Version: 5.28.0
Operating System: Linux 4.4.0-59-generic x86_64
Distribution: Ubuntu 16.04.1 LTS
-- Information about the crash:
- What I was doing when the application crashed:
I configered Kontact - Mail - Appearance and on the last tab I deleted some
message tags (German: "Nachrichten-Markierungen").
After confirming changes, Kontact crashed.
BTW: The reason for deleting the tags was, that my original tags had doubled
and mutliplied themselves over time. This I deleted all but one of the
identical tags. maybe this behaviour contributed to the crash.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f65aaee6940 (LWP 2918))]
Thread 38 (Thread 0x7f64925f2700 (LWP 6958)):
#0 0x7f65bbd10ae4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x7f65bbccb9b0 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f65bbccc2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f65bbccc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7f65c309737b in QEventDispatcherGlib::processEvents
(this=0x7f654821a000, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5 0x7f65c303fffa in QEventLoop::exec (this=this@entry=0x7f64925f1c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6 0x7f65c2e689e4 in QThread::exec (this=) at
thread/qthread.cpp:500
#7 0x7f65c2e6d808 in QThreadPrivate::start (arg=0x4b36680) at
thread/qthread_unix.cpp:341
#8 0x7f65bc4f66ba in start_thread (arg=0x7f64925f2700) at
pthread_create.c:333
#9 0x7f65c256582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
Thread 37 (Thread 0x7f6492df3700 (LWP 6956)):
#0 0x7fff29d999a9 in ?? ()
#1 0x7fff29d99cd5 in clock_gettime ()
#2 0x7f65c2573c86 in __GI___clock_gettime (clock_id=1,
tp=tp@entry=0x7f6492df29e0) at ../sysdeps/unix/clock_gettime.c:115
#3 0x7f65c2f196c6 in qt_clock_gettime (ts=0x7f6492df29e0, clock=) at tools/qelapsedtimer_unix.cpp:105
#4 do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#5 qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#6 0x7f65c3094f09 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f6544000e00) at kernel/qtimerinfo_unix.cpp:84
#7 0x7f65c3095475 in QTimerInfoList::timerWait (this=0x7f6544000e00,
tm=...) at kernel/qtimerinfo_unix.cpp:381
#8 0x7f65c309685e in timerSourcePrepareHelper (timeout=0x7f6492df2ab4,
src=) at kernel/qeventdispatcher_glib.cpp:126
#9 timerSourcePrepare (source=, timeout=0x7f6492df2ab4) at
kernel/qeventdispatcher_glib.cpp:159
#10 0x7f65bbccb92d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f65bbccc2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7f65bbccc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7f65c309737b in QEventDispatcherGlib::processEvents
(this=0x7f65440014e0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#14 0x7f65c303fffa in QEventLoop::exec (this=this@entry=0x7f6492df2c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#15 0x7f65c2e689e4 in QThread::exec (this=) at
thread/qthread.cpp:500
#16 0x7f65c2e6d808 in QThreadPrivate::start (arg=0x6a85d90) at
thread/qthread_unix.cpp:341
#17 0x7f65bc4f66ba in start_thread (arg=0x7f6492df3700) at
pthread_create.c:333
#18 0x7f65c256582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
Thread 36 (Thread 0x7f64a0a95700 (LWP 6954)):
#0 0x7f65bbd10ac9 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x7f65bbccbddc in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f65bbccc340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f65bbccc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7f65c309737b in QEventDispatcherGlib::processEvents
(this=0x7f653c009480, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5 0x7f65c303fffa in QEventLoop::exec (this=this@entry=0x7f64a0a94c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6 0x7f65c2e689e4 in QThread::exec (this=) at
thread/qthread.cpp:500
#7 0x7f65c2e6d808 in QThreadPrivate::s
[gwenview] [Bug 364805] Gwenview fails to open images with russian letters in path - Invalid url QUrl("") or file or path does not exist
https://bugs.kde.org/show_bug.cgi?id=364805 --- Comment #2 from Alexander Danilov --- Adding to my previous report. Gwenview 16.08.3 (KDE Frameworks 5.29.0, Qt 5.6.2) is working all good as expected. Kompare-4.1.3 and filelight-1.21 are now working as well. It looks like either KDE Frameworks update 5.23.0 -> 5.29.0, or Qt update 5.6.1 -> 5.6.2 fixed the problem. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 342372] password asked for browsing files
https://bugs.kde.org/show_bug.cgi?id=342372 --- Comment #7 from Albert Vaca --- Version 0.8 is old and unsupported. Please upgrade to 1.0. I recommend you asking the Ubuntu packagers to provide a recent version, so it fixes it not only for you but for all Ubuntu users. The more people who complain the higher the chance they finally update it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375220] New: mouse wheel scrolling broken after update to 16.12
https://bugs.kde.org/show_bug.cgi?id=375220 Bug ID: 375220 Summary: mouse wheel scrolling broken after update to 16.12 Product: okular Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jirisl...@gmail.com Target Milestone: --- After recent update, perhaps to okular 16.12 (it may be 16.04 or 16.08, only I haven't noticed yet), scrolling by mouse wheel is broken. I very suspect this to be a genuine Qt5 bug. What I do: * click somewhere in the PDF document * scroll down by wheel * click somewhere in the PDF document again * scroll down by wheel again What happens is that the second scroll starts exactly where the first started. So it actually jumps to the position as if the first scroll never happened and starts scrolling from there on. I actually need not to click anywhere in the document. It is enough to switch to another window and continue scrolling in the PDF document -- it always jumps back. okular update activity: 2015-10-19 08:56:31|install|okular|15.08.1-1.1|x86_64||repo-oss|dfb3cd4078a7ee603649922dd7e1227ddb01eacd| 2015-10-28 09:38:56|install|okular|15.08.2-1.1|x86_64||repo-oss|677b4ae12073bcb1f148ff088fb3abb927f59950| 2015-11-22 17:44:31|install|okular|15.08.3-1.1|x86_64||repo-oss|841eea27c9382abdc43659103694e0d9ba325c94| 2016-01-27 10:44:25|install|okular|15.12.0-1.2|x86_64||repo-oss|2e13d9db644338fe2ad135506ae8d4b04599d927| 2016-02-11 08:57:06|install|okular|15.12.1-1.1|x86_64||repo-oss|3b3969fc66e4d06539a63991a0ba54676af57947| 2016-03-14 15:02:26|install|okular|15.12.2-1.1|x86_64||repo-oss|3ff3ef063d6f55088a99cff21f0cefb50dad71a0| 2016-04-09 16:41:59|install|okular|15.12.3-1.1|x86_64||repo-oss|1e335bb1ec55cb8c53629898ded236c27eac3663| 2016-05-11 17:49:56|install|okular|15.12.3-1.2|x86_64||repo-oss|d0d2dc86a294337b47794b7d0f71b4602e5bc8d0| 2016-06-08 07:30:59|install|okular|16.04.1-1.1|x86_64||repo-oss|d07dbfe284c2954c17902400cb278d0229fd77f0| 2016-06-27 11:35:19|install|okular|16.04.2-1.2|x86_64||repo-oss|aa7679343a8c0494adbeae8d4aadb060390a6588| 2016-07-25 15:21:05|install|okular|16.04.2-2.1|x86_64||repo-oss|954abaa8ebbf3b7f2d897511cb5e0ab0cb2f7488| 2016-07-29 10:58:37|install|okular|16.04.3-1.1|x86_64||repo-oss|ac9ab429ef5acebc044fdd97dfd2011561d5b25e| 2016-09-07 19:29:29|install|okular|16.08.0-1.2|x86_64||repo-oss|373d93459f554c170b3f8805f1764a6d92132995| 2016-10-05 14:17:36|install|okular|16.08.1-1.1|x86_64||repo-oss|df595a3fd03a27dfaaa4110b1a38f3dabd5b9e76| 2016-11-07 12:20:45|install|okular|16.08.2-1.1|x86_64||repo-oss|1e767632c1d5007ab1d1f3cb5a53818f41d45528| 2016-12-01 21:26:46|install|okular|16.08.3-1.1|x86_64||repo-oss|a5b02bbe269fc86c2c90f816ce44e7f26cdbf982| 2017-01-05 08:28:09|install|okular|16.12.0-1.1|x86_64||repo-oss|7c8083cceb312244c96320ce1f7373da698db0dd| -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375195] Pass -fno-operator-names when supported breaks build of several packages
https://bugs.kde.org/show_bug.cgi?id=375195 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org, ||kf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 375128] Newest version does not work with nvidia
https://bugs.kde.org/show_bug.cgi?id=375128 Vincent PINON changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Vincent PINON --- Hello, The commit causing this crash on NVidia has been reverted, just uploaded the new stable PPA packages. Please confirm that it fixes your problem. Thanks for the report, Vincent -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375108] AppImage has no application icon showing in Ubuntu
https://bugs.kde.org/show_bug.cgi?id=375108 --- Comment #4 from caulier.gil...@gmail.com --- Git commit c92689a20bfbcb3b77900b3c2164aa709718442e by Gilles Caulier. Committed on 18/01/2017 at 09:07. Pushed by cgilles into branch 'master'. copy desktop file and icon at right place in AppImage M +3-8project/bundles/appimage/04-build-appimage.sh https://commits.kde.org/digikam-software-compilation/c92689a20bfbcb3b77900b3c2164aa709718442e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375219] New: Gnome windows loose characters
https://bugs.kde.org/show_bug.cgi?id=375219 Bug ID: 375219 Summary: Gnome windows loose characters Product: kwin Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compatibility Assignee: kwin-bugs-n...@kde.org Reporter: bugzi...@eyra.se Target Milestone: --- Created attachment 103474 --> https://bugs.kde.org/attachment.cgi?id=103474&action=edit Showing missing letters in Gnome windows (emacs and gnome-calculator) while KDE windows (kcalc and okular) work. Kubuntu 16.04 with kwin-x11 4:5.5.5-0ubuntu1, using nouveau drivers. Some times (usually after some uptime) windows of Gnome programs will loose most of the characters, with only some visible. See attached screen shot. I don't know where to start trouble shooting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373075] Changing Resolution hides programs in task manager
https://bugs.kde.org/show_bug.cgi?id=373075 --- Comment #3 from Bastian Köcher --- Hi, I am now using the 5.9 beta and that bug should be fixed in this release? Because I still observe the bug. If I remove my second screen, the applications in the task manager are not updated nor I can click on the applications that are visible in the task manager. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363641] Replace launcher icon with Plasma logo icon
https://bugs.kde.org/show_bug.cgi?id=363641 Pascal d'Hermilly changed: What|Removed |Added CC||pas...@dhermilly.dk --- Comment #7 from Pascal d'Hermilly --- So the icon in the launcher was changed with an update in KDE Neon... How the heck am I over the phone going to explain to my daft family members which button to click? A K was super easy. Now I have to try with the "3 different sized dots and an arrow." >From a user perspective the new launcher icon is bad - first because it changed, second because its undescribable. >From a KDE fan perspective I'm sad to see the last piece of visual identity disappear. It's no longer KDE, but Plasma which is part of the kde project -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 375218] New: Delayed send of an eMail does not act
https://bugs.kde.org/show_bug.cgi?id=375218 Bug ID: 375218 Summary: Delayed send of an eMail does not act Product: kmail2 Version: 5.3.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: thopp...@web.de Target Milestone: --- I want to sent an mail via the 'Send'-Button in the mail editor. I was asked if I want to send the mail now or later. If I choose later the mail will be send immedialtely. Then I try to use the menu 'Send / Send later' (this is a retranslation) there I get the popUp to choose the send time. But after this I miss the popUp to input the passphrase of my GPG-Sig. So this time the will be send later, but without GPG-Sig. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369105] KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"
https://bugs.kde.org/show_bug.cgi?id=369105 Sven Brauch changed: What|Removed |Added Status|NEEDSINFO |ASSIGNED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #7 from Sven Brauch --- It seems like we ship libxcb-dri2.so already, so I'll include libxcb-dri3.so as well in 5.0.4 and 5.0.81 and we can test if that works better for you. Maybe that's the reason. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 363237] Breakpoints (Breakpoints View) are not updated after removing/adding couple lines of code
https://bugs.kde.org/show_bug.cgi?id=363237 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Sven Brauch --- Hmm, can't reproduce the crash but yes, the display is definitely buggy, we need to look into that. But, how did you lose data? Crash recovery should easily be able to restore all changes to the file in this case ... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 375136] Deleted mails moves to local trash
https://bugs.kde.org/show_bug.cgi?id=375136 Hufschmidt changed: What|Removed |Added CC||hufsc...@hrz.uni-marburg.de --- Comment #1 from Hufschmidt --- Had the same issue yesterday after a lot of fidling. Fixed itself after a full system restart for me (at least for now). Potential duplicate of: https://bugs.kde.org/show_bug.cgi?id=357945 Might also be related to: https://bugs.kde.org/show_bug.cgi?id=371664 -- You are receiving this mail because: You are watching all bug changes.
