[LabPlot2] [Bug 379104] creating a plot or a fit must be improved
https://bugs.kde.org/show_bug.cgi?id=379104 --- Comment #1 from Alexander Semke --- Hi Uwe, thanks for your feedback! The steps 2, 3 and 4 in LabPlot are only required if you want to plot the original data, too. In case you only want to create a fit, you select/create a plot, add a fit-curve and specify the data for it. But I agree with you in general. We need to improve the usability here. One idea is to add all those analysis functions to the context menu of the xy-curve. For the use-cases where you have the data already plotted in the plot, you simply right-click on the curve in the plot and select "Fit" - with this a new fit-curve will be created and the data for the fit will be already selected. This would improve the worksheet-centric workflows. For spreadsheet-centric workflows like in your example with MagicPlot we'll also add similar functionality to the context menu in the spreadsheet. This is all very easy to implement and is just a matter of time. Besides of this, we'll add some more generic wizards where the user will be guided through such an analysis process like fitting and where worksheets+plots+curves will be created automatically at the end. This is currently work in progress and we'll release this for 2.5. As to the comparison with MagicPlot: I had a brief look now at this program. I see some modal dialogs for editing the properties which overlapp the underlying objects, obsolete scroll bars, etc. This program looks similarly overloaded as Origin. LabPlot is not perfect (yet), but I think it's not unfair to say here that there many things that are solved better in LabPlot. Regards, Alexander -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379108] New: Checking metadata display for targets in assignments
https://bugs.kde.org/show_bug.cgi?id=379108
Bug ID: 379108
Summary: Checking metadata display for targets in assignments
Product: kdevelop
Version: 5.1.0
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: markus.elfr...@web.de
Target Milestone: ---
I am wondering about the next detail during my use of the source code editor in
the application “KDevelop 5.1.0-26.1”. I can get additional information
displayed in a corresponding window after the mouse pointer is positioned over
an identifier in an expression for a conditional statement. It seems that I do
not get such a metadata display if I would like to inspect the same identifier
when it is used within the target of assignments.
Example:
{
struct my_info* ref;
…
ref = do_something(my_work);
if (!ref)
return -ENOMEM;
…
}
Does different syntax colouring indicate also any further software development
challenges there?
--
You are receiving this mail because:
You are watching all bug changes.
[ksshaskpass] [Bug 343562] Cannot remove a wrong user/password after it was stored
https://bugs.kde.org/show_bug.cgi?id=343562 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #5 from Karl Ove Hufthammer --- I just got bitten by the same problem, using ksshaskpass 5.9.4 and all the latest libraries. Marking bug as ‘Confirmed’. -- You are receiving this mail because: You are watching all bug changes.
[docs] [Bug 379109] New: Update plasma doc to include new feature "Simplified Global Shortcuts" (ModifierOnlyShortcuts) - meta key only
https://bugs.kde.org/show_bug.cgi?id=379109 Bug ID: 379109 Summary: Update plasma doc to include new feature "Simplified Global Shortcuts" (ModifierOnlyShortcuts) - meta key only Product: docs Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Missing Content Assignee: kde-doc-engl...@kde.org Reporter: prusselltechgr...@gmail.com Target Milestone: --- This is a >= 5.8 Plasma documentation only request to reflect a new feature. Link [1] below is the plasma documentation titled, "KDE Fundamentals" - "Common Keyboard Shortcuts". I picked this page because it contains a special block pertaining to the Meta key. It was also the page that came up when I did the original search. In Plasma 5.8, the Meta (super/win) key will trigger the menu/launcher. Could the documentation be updated to: 1. Reflect plasma's new usage of the Meta key 2. How to configure/disable the feature Link [2] talks about the issue. Link [3] talks about the new implementation in plasma. Link [4] official announcement (Simplified Global Shortcuts) Link [5] talks about how to disable IE Configure: ~/.config/kwinrc [ModifierOnlyShortcuts] Meta= Links: [1] https://docs.kde.org/trunk5/en/applications/fundamentals/kbd.html [2] https://blog.hanschen.org/2012/10/17/open-application-launcher-with-super-key/ [3] https://blog.martin-graesslin.com/blog/2016/08/modifier-only-shortcuts-available-in-plasma-5-8/ [4] https://www.kde.org/announcements/plasma-5.8.0.php [5] https://www.reddit.com/r/kde/comments/55udc1/how_do_i_stop_the_meta_key_from_opening_the/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370143] Desktop Settings doesn't save changes after logout
https://bugs.kde.org/show_bug.cgi?id=370143 Marcos Paulino Roriz Junior changed: What|Removed |Added CC||marcosroriz...@gmail.com --- Comment #12 from Marcos Paulino Roriz Junior --- I'm still having this issue on KDE 5.8.5 in Kubuntu 16.04. Any idea on how to fix it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379110] New: Plasma is not saving desktop setting (folder view) after logout
https://bugs.kde.org/show_bug.cgi?id=379110 Bug ID: 379110 Summary: Plasma is not saving desktop setting (folder view) after logout Product: plasmashell Version: 5.8.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: marcosroriz...@gmail.com Target Milestone: 1.0 Created attachment 105155 --> https://bugs.kde.org/attachment.cgi?id=105155&action=edit plasma config Hello everyone, I'm having a major issue when trying to change my plasma shell view to folder view (showing desktop). Precisely, when I reboot or logout it restores the plasma view to its default view. I'm running KDE 5.8.5 on Kubuntu 16.04. This bug seems to be a follow up of https://bugs.kde.org/show_bug.cgi?id=370143, which tried to fix this issue in 5.8.4. However, it still appears in KDE 5.8.5 on Kubuntu 16.04. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 379103] missing icon for LabPlot in the Windows start menu
https://bugs.kde.org/show_bug.cgi?id=379103 Stefan Gerlach changed: What|Removed |Added Severity|normal |minor Assignee|alexander.se...@web.de |stefan.gerlach@uni-konstanz ||.de Status|UNCONFIRMED |CONFIRMED Version|unspecified |Frameworks CC||stefan.gerlach@uni-konstanz ||.de Ever confirmed|0 |1 --- Comment #1 from Stefan Gerlach --- the smallest size icon is missing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379111] New: Vertical sync causes flickering on screen capturing
https://bugs.kde.org/show_bug.cgi?id=379111 Bug ID: 379111 Summary: Vertical sync causes flickering on screen capturing Product: kwin Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: michal.dybc...@gmail.com Target Milestone: --- Vertical synchronization causes screen capturing to flicker. I discovered it during tests with OBS and simplescreenrecorder. Disabling vertical sync stops flickering completely but introduces small, sporadical screen tearing when moving windows so it's desirable to have this option on, however, it conflicts with screen capturing programs. I already informed OBS developer about it to see if he can do something about it on his end, but the fact that this bug happens in more capturing programs shows a basic problem on kwin end. I made a video showing how disabling and enabling vertical sync influences the flickering: https://www.youtube.com/watch?v=XutOV1wffMQ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379111] Vertical sync causes flickering on screen capturing
https://bugs.kde.org/show_bug.cgi?id=379111 Michał Dybczak changed: What|Removed |Added CC||michal.dybc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 379055] Icon of USB headset device is wrong
https://bugs.kde.org/show_bug.cgi?id=379055 David Rosca changed: What|Removed |Added CC||myr...@kde.org Version|5.9.4 |unspecified Component|kcm |settings Product|plasma-pa |Phonon Assignee|now...@gmail.com|sit...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 375354] Add the option to open the multimedia KCM in context menu
https://bugs.kde.org/show_bug.cgi?id=375354 David Rosca changed: What|Removed |Added Version Fixed In||5.10.0 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378986] KMail 5.4.3: Attachments with non-ASCII characters get strange name
https://bugs.kde.org/show_bug.cgi?id=378986 --- Comment #2 from Axel Braun --- Actually I cant reproduce it at the moment - but there was an update to some libQT and libKF5 libraries installed yesterday. I will send an update once I can reproduce. Thanks Axel -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 378491] Volume feedback checkbox not working
https://bugs.kde.org/show_bug.cgi?id=378491 --- Comment #1 from David Rosca --- Do you have multiple instances of Volume applet? This option applies only to the instance from which you opened the settings. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 378755] Notifications sound does not work
https://bugs.kde.org/show_bug.cgi?id=378755 David Rosca changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #5 from David Rosca --- *** This bug has been marked as a duplicate of bug 378031 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 378031] Notifications volume not changing from 0
https://bugs.kde.org/show_bug.cgi?id=378031 David Rosca changed: What|Removed |Added CC||jamesru...@outlook.com --- Comment #7 from David Rosca --- *** Bug 378755 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 379097] Cannot specify correct LabPlot version in bugtracker
https://bugs.kde.org/show_bug.cgi?id=379097 Stefan Gerlach changed: What|Removed |Added Severity|normal |minor Assignee|alexander.se...@web.de |stefan.gerlach@uni-konstanz ||.de Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||stefan.gerlach@uni-konstanz ||.de --- Comment #1 from Stefan Gerlach --- A ticket to add all versions is opened (T5929) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372284] digikam disables application style support by default
https://bugs.kde.org/show_bug.cgi?id=372284 --- Comment #3 from caulier.gil...@gmail.com --- Because we need to homogeneous everywhere : Linux but also Windows, and MacOS. Under Windows and MAcOS, Fusion style is the only one which give good result. All others one are horrible and introduce dysfunction. So if Linux packagers want to use more style, they can, through the compilation option. But that all. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376065] auto-hide panel flickers
https://bugs.kde.org/show_bug.cgi?id=376065 --- Comment #3 from achat1...@free.fr --- An update on this. I update my Neon to hwe stack 16.04 (linux kernel 4.8 + xserver) and problem seem gone on the Skylake config and greatly improve on the Ivy Bridge (can still see a little flickering on the edge on panel when closed but the whole panel stopped flickering) (packages I installed are: linux-generic-hwe-16.04 and xserver-xorg-hwe-16.04) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373741] Drawing while switching between layers with PgUp/PgDown results in a layer acting like it's in a locked group
https://bugs.kde.org/show_bug.cgi?id=373741 Nicholas LaPointe changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Nicholas LaPointe --- Resolved with the fixing of bug 376214 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone
https://bugs.kde.org/show_bug.cgi?id=368438 --- Comment #16 from Theresa --- @Albert/Matt: any idea what's causing my connection drops?! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 378858] Crash trying to start akonadi after failed mysql connect
https://bugs.kde.org/show_bug.cgi?id=378858 Daniel Vrátil changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Daniel Vrátil --- Sorry, KDEPIM 4 is not supported anymore. The message (akonadi_baloo_indexer(6706)/libakonadi: Unable to register service \"org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer\" at dbus) indicates that there's a problem with your DBus session, or that there's already another (stuck?) instance of akonadi_baloo_indexer running that holds the service. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 378858] Crash trying to start akonadi after failed mysql connect
https://bugs.kde.org/show_bug.cgi?id=378858 --- Comment #2 from Con Kolivas --- Eh that's most unusual, I'm not running kde4. I guess some kde4 packages are still around in kubuntu 16.10 and somehow this came up. I'm actually on kde frameworks 5.26 and qt 5.6.1 so I guess whatever crashed in the failing imap session on kmail 5.2.3 somehow triggered an... interaction with kde4 or something??? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364984] group not editable at new window view.
https://bugs.kde.org/show_bug.cgi?id=364984 --- Comment #8 from Nicholas LaPointe --- The "hang" set of steps I gave in bug 374496 (more or less the same as Jörn PM's steps in comment 7) still manages to reproduce this bug as of the current Git master. This time around, the "Group not editable" message doesn't show up, but drawing becomes impossible. Also, at step 4 of my instructions, Krita now shows "Waiting for image operation to complete..." -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379112] New: App "Discover" crashes regularly
https://bugs.kde.org/show_bug.cgi?id=379112 Bug ID: 379112 Summary: App "Discover" crashes regularly Product: Discover Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: themoole...@gmail.com Target Milestone: --- Application: plasma-discover (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-19-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: This app crashed when installing an application from the store. This is a common occurence. It also often crashes when uninstalling applications. Another issue I have is that the cursor will freeze such that it is in text-selection mode and I am unable to click on anything within the discover application. I experience crashes with the discover app very regularly. -- Backtrace: 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 0x7f9afcb328c0 (LWP 3197))] Thread 13 (Thread 0x7f9ac0a3d700 (LWP 4954)): #0 0x7f9af8cfc3a5 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f9af2d81a6d in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9af2d8249b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9af2d8268c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9af8cfcf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9af8ca688a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9af8ad3fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9af8ad8c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9af4eb36da in start_thread (arg=0x7f9ac0a3d700) at pthread_create.c:456 #9 0x7f9af80dc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 12 (Thread 0x7f9a857fa700 (LWP 4951)): #0 0x7f9af4eb98b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f9af8ad9a86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9af8ad52b2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f9af8ad8c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9af4eb36da in start_thread (arg=0x7f9a857fa700) at pthread_create.c:456 #5 0x7f9af80dc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 11 (Thread 0x7f9ac1e9a700 (LWP 4950)): #0 0x7f9af4eb98b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f9af8ad9a86 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9af8ad52b2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f9af8ad8c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9af4eb36da in start_thread (arg=0x7f9ac1e9a700) at pthread_create.c:456 #5 0x7f9af80dc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 10 (Thread 0x7f9a66ffd700 (LWP 4949)): #0 0x7f9af8cfb0ee in QTimerInfoList::repairTimersIfNeeded() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f9af8cfb163 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f9af8cfc4fe in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f9af2d81a6d in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9af2d8249b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9af2d8268c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f9af8cfcf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9af8ca688a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9af8ad3fe3 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f9af8ad8c98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9af4eb36da in start_thread (arg=0x7f9a66ffd700) at pthread_create.c:456 #11 0x7f9af80dc17f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 9 (Thread 0x7f9aa7fff700 (LWP 3212)): #0 0x7f9af80d018d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9af2d82576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9af2d8268c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9af8cfcf2b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f
[krita] [Bug 379113] New: Segfault with "Flatten layer" when layer contains local selection
https://bugs.kde.org/show_bug.cgi?id=379113 Bug ID: 379113 Summary: Segfault with "Flatten layer" when layer contains local selection Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: nicholaslapoin...@gmail.com Target Milestone: --- Reproducible: Always Krita receives a segfault when trying to flatten a layer which contains a local selection. Steps to Reproduce: 1. Create a new document 2. Add a local selection to a layer 3. Flatten layer GDB Ouput: Thread 22 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffacdd0700 (LWP 944)] KisNode::lastChild (this=0x0) at src/krita/libs/image/kis_node.cpp:347 347 QReadLocker l(&m_d->nodeSubgraphLock); (gdb) bt #0 KisNode::lastChild (this=0x0) at src/krita/libs/image/kis_node.cpp:347 #1 0x73896c21 in KisLayerUtils::CleanUpNodes::reparentSelectionMasks (this=this@entry=0xcf83f00, image=..., newLayer=..., selectionMasks=...) at src/krita/libs/image/kis_layer_utils.cpp:697 #2 0x73899c21 in KisLayerUtils::CleanUpNodes::populateChildCommands (this=0xcf83f00) at src/krita/libs/image/kis_layer_utils.cpp:679 #3 0x724cfed7 in KisCommandUtils::AggregateCommand::redo (this=0xcf83f08) at src/krita/libs/command/kis_command_utils.cpp:36 #4 0x7384f93a in KisStrokeStrategyUndoCommandBased::doStrokeCallback (this=0x7f34310, data=) at src/krita/libs/image/kis_stroke_strategy_undo_command_based.cpp:118 #5 0x739a7421 in KisStrokeJob::run (this=) at builds/krita_standard/libs/image/../../../../src/krita/libs/image/kis_stroke_job.h:44 #6 KisUpdateJobItem::run (this=0x7feab30) at builds/krita_standard/libs/image/../../../../src/krita/libs/image/kis_update_job_item.h:66 #7 0x75d61be3 in ?? () from /opt/Qt-5.6/lib/libQt5Core.so.5 #8 0x75d657e8 in ?? () from /opt/Qt-5.6/lib/libQt5Core.so.5 #9 0x7fffeffb06ba in start_thread (arg=0x7fffacdd0700) at pthread_create.c:333 #10 0x7545d82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379058] Brush presets docker does not let go of scroll wheel
https://bugs.kde.org/show_bug.cgi?id=379058 Nicholas LaPointe changed: What|Removed |Added Resolution|--- |FIXED CC||nicholaslapoin...@gmail.com Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Nicholas LaPointe --- Thanks for your report! Do you know which version of Qt is installed on your computer? If you are using Qt 5.7 (or presumably newer), then you are probably experiencing bug 364850. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379058] Brush presets docker does not let go of scroll wheel
https://bugs.kde.org/show_bug.cgi?id=379058 Nicholas LaPointe changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 377405] Bluetooth disabled after resume from sleep or hibernate, or startup
https://bugs.kde.org/show_bug.cgi?id=377405 David Rosca changed: What|Removed |Added CC||b...@mrvanes.com --- Comment #4 from David Rosca --- *** Bug 379107 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 379107] Bluetooth control deactivated until plasma restart
https://bugs.kde.org/show_bug.cgi?id=379107 David Rosca changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Rosca --- *** This bug has been marked as a duplicate of bug 377405 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 377405] Bluetooth disabled after resume from sleep or hibernate, or startup
https://bugs.kde.org/show_bug.cgi?id=377405 David Rosca changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 377405] Bluetooth disabled after resume from sleep or hibernate, or startup
https://bugs.kde.org/show_bug.cgi?id=377405 David Rosca changed: What|Removed |Added Product|Bluedevil |frameworks-bluez-qt Component|general |general Version|5.7.5 |5.33.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379114] New: (Git master only) Segfault when opening a document containing a file layer
https://bugs.kde.org/show_bug.cgi?id=379114 Bug ID: 379114 Summary: (Git master only) Segfault when opening a document containing a file layer Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: nicholaslapoin...@gmail.com Target Milestone: --- Reproducible: Always Krita receives a segfault when opening a document which has a file layer. This doesn't happen in the 3.1 branch. Steps to Reproduce: 1. Create a new document 2. Add a file layer 3. Save and close document 4. Open document Output, including backtrace: QObject: Cannot create children for a parent that is in a different thread. (Parent is QStatusBar(0x69ca070), parent's thread is QThread(0xa888f0), current thread is QThread(0x2542c30) QCoreApplication::postEvent: Unexpected null receiver QObject::killTimer: Timers cannot be stopped from another thread QObject::startTimer: Timers cannot be started from another thread QObject: Cannot create children for a parent that is in a different thread. (Parent is QStatusBar(0x69ca070), parent's thread is QThread(0xa888f0), current thread is QThread(0x2542c30) QLayout: Attempting to add QLayout "" to QStatusBar "", which already has a layout QObject::killTimer: Timers cannot be stopped from another thread QObject::startTimer: Timers cannot be started from another thread Thread 1 "krita" received signal SIGSEGV, Segmentation fault. 0x768d9bfc in QLayout::widgetEvent(QEvent*) () from /opt/Qt-5.6/lib/libQt5Widgets.so.5 (gdb) bt #0 0x768d9bfc in QLayout::widgetEvent(QEvent*) () from /opt/Qt-5.6/lib/libQt5Widgets.so.5 #1 0x768b7d9a in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /opt/Qt-5.6/lib/libQt5Widgets.so.5 #2 0x768bd306 in QApplication::notify(QObject*, QEvent*) () from /opt/Qt-5.6/lib/libQt5Widgets.so.5 #3 0x778ae0c7 in KisApplication::notify (this=, receiver=0x69ca070, event=0x7fffc4082310) at src/krita/libs/ui/KisApplication.cpp:550 #4 0x75f3a298 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /opt/Qt-5.6/lib/libQt5Core.so.5 #5 0x75f3c15a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /opt/Qt-5.6/lib/libQt5Core.so.5 #6 0x75f8f173 in ?? () from /opt/Qt-5.6/lib/libQt5Core.so.5 #7 0x7fffefa8f197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fffefa8f3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fffefa8f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x75f8f57f in QEventDispatcherGlib::processEvents(QFlags) () from /opt/Qt-5.6/lib/libQt5Core.so.5 #11 0x778dd1ff in runActionImpl(std::function) (func=...) at src/krita/libs/ui/kis_async_action_feedback.cpp:52 #12 0x778dba99 in KisAsyncActionFeedback::runAction(std::function) (this=this@entry=0x7fffc7e0, func=...) at src/krita/libs/ui/kis_async_action_feedback.cpp:61 #13 0x778d79ed in KisImportExportManager::convert (this=0x7d74750, direction=direction@entry=KisImportExportManager::Import, location=..., realLocation=..., mimeType=..., showWarnings=showWarnings@entry=false, exportConfiguration=...) at src/krita/libs/ui/KisImportExportManager.cpp:264 #14 0x778d7c9b in KisImportExportManager::importDocument (this=, location=..., mimeType=...) at src/krita/libs/ui/KisImportExportManager.cpp:88 #15 0x778bd890 in KisDocument::openFile (this=this@entry=0x7cc5c80) at src/krita/libs/ui/KisDocument.cpp:1088 #16 0x778be3a2 in KisDocument::openUrlInternal (this=this@entry=0x7cc5c80, url=...) at src/krita/libs/ui/KisDocument.cpp:1489 #17 0x778be7a0 in KisDocument::openUrl (this=this@entry=0x7cc5c80, _url=..., flags=flags@entry=KisDocument::OPEN_URL_FLAG_NONE) at src/krita/libs/ui/KisDocument.cpp:994 #18 0x778dfcf0 in KisMainWindow::openDocumentInternal (this=this@entry=0x69f49c0, url=..., newdoc=0x7cc5c80, newdoc@entry=0x0) at src/krita/libs/ui/KisMainWindow.cpp:772 #19 0x778e7115 in KisMainWindow::openDocument (this=this@entry=0x69f49c0, url=...) at src/krita/libs/ui/KisMainWindow.cpp:754 #20 0x778e7638 in KisMainWindow::slotFileOpen (this=0x69f49c0) at src/krita/libs/ui/KisMainWindow.cpp:1348 #21 0x778ef214 in KisMainWindow::qt_static_metacall (_o=0x69f49c0, _c=, _id=, _a=0x7fffd0c0) at builds/krita_standard/libs/ui/moc_KisMainWindow.cpp:310 #22 0x75f66b61 in QMetaObject::activate(QObject*, int, int, void**) () from /opt/Qt-5.6/lib/libQt5Core.so.5 #23 0x768ae8c2 in QAction::triggered(bool) () from /opt/Qt-5.6/lib/libQt5Widgets.so.5 #24 0x768b13e0 in QAction::activate(QAction::ActionEvent) () from /opt/Qt-5.6/lib/libQt5Widge
[plasma-pa] [Bug 378491] Volume feedback checkbox not working
https://bugs.kde.org/show_bug.cgi?id=378491 --- Comment #2 from Ural --- I had two. When I removed one, it seems worked. So if I want to disable volume feedback, I need to uncheck checkbox for both? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 378755] Notifications sound does not work
https://bugs.kde.org/show_bug.cgi?id=378755 Ural changed: What|Removed |Added CC||uralz...@autistici.org --- Comment #6 from Ural --- You can unmute it and move slider in 'pavucontrol' instead of 'audiovolume settings', while this bug will be fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 378491] Volume feedback checkbox not working
https://bugs.kde.org/show_bug.cgi?id=378491 David Rosca changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from David Rosca --- Yes, you need to disable it in all volume applet instances, otherwise you will get feedback from each applet instance. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 378755] Notifications sound does not work
https://bugs.kde.org/show_bug.cgi?id=378755 --- Comment #7 from David Rosca --- Unmuting the Notification Sounds stream with Mute button (in top right corner) doesn't work too? Or the issue is only when moving the slider from 0? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379111] Vertical sync causes flickering on screen capturing
https://bugs.kde.org/show_bug.cgi?id=379111 --- Comment #1 from Martin Gräßlin --- Please provide output of qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 378755] Notifications sound does not work
https://bugs.kde.org/show_bug.cgi?id=378755 --- Comment #8 from Ural --- For me, unmuting didn't worked. I tried to unmute and move slider, it was always returned back. Only pavucontrol helped. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 378858] Crash trying to start akonadi after failed mysql connect
https://bugs.kde.org/show_bug.cgi?id=378858 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel --- Uninstall all kde4 apps from your distro. See "Application: akonadi_baloo_indexer (4.14) KDE Platform Version: 4.14.22" so indeed it's kde4 here. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379105] Neon Packaging issue with KDE Apps 17.04
https://bugs.kde.org/show_bug.cgi?id=379105 --- Comment #1 from Jonathan Riddell --- Seems similar to https://bugs.kde.org/show_bug.cgi?id=379091 what happens if you ask it to install libastro1? sudo apt update sudo apt install libastro1 -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 374224] KFileDialog Options drop-down menu grabs keyboard and mouse with QtCurve style
https://bugs.kde.org/show_bug.cgi?id=374224 Valeriy Malov changed: What|Removed |Added CC||jazzv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379115] New: dolphin-dbg not in the repository
https://bugs.kde.org/show_bug.cgi?id=379115 Bug ID: 379115 Summary: dolphin-dbg not in the repository Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: sefa6...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Because dolphin-dbg is not in the package repository (User Edition not LTS), I could not install dolphin-dbg because it depends on the ubuntu compiled version (4:15.12.3-0ubuntu1) and not on neon's compiled version (4:17.04.0-0neon+16.04+build23). TL;DR Add dolphin-dbg to package repository -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379115] dolphin-dbg not in the repository
https://bugs.kde.org/show_bug.cgi?id=379115 Sefa Eyeoglu changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379061] when i try to draw sonething the cursor won't show up and it takes a long time to load the line
https://bugs.kde.org/show_bug.cgi?id=379061 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||b...@valdyas.org Component|Vector Objects and Tools|OpenGL Canvas Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- Does the problem go away if you disable opengl? If so, your display driver is buggy and probably outdated. See https://docs.krita.org/KritaFAQ#Krita_starts_with_a_black_or_blank_canvas_and_nothing_changes_when_you_try_to_draw.2Fshows_a_black_or_blank_screen_on_my_Windows_system_with_an_Intel_GPU Please report the exact version of your display driver and the type of your intel graphics adapter. -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 379063] build of win32libs/icu fails when invoking awk in build of kdevelop: error while loading shared libraries: msys-readline7.dll
https://bugs.kde.org/show_bug.cgi?id=379063 Hannah von Reth changed: What|Removed |Added Version Fixed In||57899bbe52cf77f17303b7477df ||f7c039075f2c0 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Hannah von Reth --- I fixed msys. Please remove the msys dir and reinstall it using "craft -i msys" -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379091] wrong libastro1 package to be installed borks update
https://bugs.kde.org/show_bug.cgi?id=379091 --- Comment #2 from m...@etruscott.co.uk --- I get this: Starting pkgProblemResolver with broken count: 3 Starting 2 pkgProblemResolver with broken count: 3 Investigating (0) marble-plugins [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( misc ) Broken marble-plugins:amd64 Depends on libmarblewidget-qt5-27 [ amd64 ] < none -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:17.04.0-0neon+16.04+build31) Considering libmarblewidget-qt5-27:amd64 0 as a solution to marble-plugins:amd64 3 Re-Instated libmarblewidget-qt5-27:amd64 Re-Instated marble-plugins:amd64 Investigating (0) libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) Broken libmarblewidget-qt5-26:amd64 Depends on libastro1 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:16.12.3-0neon+16.04+build28) Considering libastro1:amd64 10004 as a solution to libmarblewidget-qt5-26:amd64 2 Removing libmarblewidget-qt5-26:amd64 rather than change libastro1:amd64 Investigating (0) marble-qt [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( misc ) Broken marble-qt:amd64 Depends on libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) (= 4:16.12.3-0neon+16.04+build28) Considering libmarblewidget-qt5-26:amd64 2 as a solution to marble-qt:amd64 0 Re-Instated marble-qt:amd64 Investigating (0) digikam [ amd64 ] < 4:5.4.0-0neon+16.04+build14 -> 4:5.5.0-0neon+16.04+build18 > ( graphics ) Broken digikam:amd64 Depends on libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) Considering libmarblewidget-qt5-26:amd64 2 as a solution to digikam:amd64 0 Re-Instated digikam-data:amd64 Re-Instated digikam:amd64 Done The following package was automatically installed and is no longer required: kde-l10n-engb Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: digikam digikam-data kde-l10n-engb libmarblewidget-qt5-27 marble marble-data marble-plugins marble-qt Suggested packages: digikam-doc gosmore monav-routing-daemon routino The following packages will be REMOVED libmarblewidget-qt5-26 The following NEW packages will be installed libmarblewidget-qt5-27 The following packages will be upgraded: digikam digikam-data kde-l10n-engb libastro1 marble marble-data marble-plugins marble-qt When I ran this, the system upgraded without issue. Thanks for the suggestion. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379091] wrong libastro1 package to be installed borks update
https://bugs.kde.org/show_bug.cgi?id=379091 --- Comment #3 from m...@etruscott.co.uk --- I get this: Starting pkgProblemResolver with broken count: 3 Starting 2 pkgProblemResolver with broken count: 3 Investigating (0) marble-plugins [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( misc ) Broken marble-plugins:amd64 Depends on libmarblewidget-qt5-27 [ amd64 ] < none -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:17.04.0-0neon+16.04+build31) Considering libmarblewidget-qt5-27:amd64 0 as a solution to marble-plugins:amd64 3 Re-Instated libmarblewidget-qt5-27:amd64 Re-Instated marble-plugins:amd64 Investigating (0) libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) Broken libmarblewidget-qt5-26:amd64 Depends on libastro1 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:16.12.3-0neon+16.04+build28) Considering libastro1:amd64 10004 as a solution to libmarblewidget-qt5-26:amd64 2 Removing libmarblewidget-qt5-26:amd64 rather than change libastro1:amd64 Investigating (0) marble-qt [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( misc ) Broken marble-qt:amd64 Depends on libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) (= 4:16.12.3-0neon+16.04+build28) Considering libmarblewidget-qt5-26:amd64 2 as a solution to marble-qt:amd64 0 Re-Instated marble-qt:amd64 Investigating (0) digikam [ amd64 ] < 4:5.4.0-0neon+16.04+build14 -> 4:5.5.0-0neon+16.04+build18 > ( graphics ) Broken digikam:amd64 Depends on libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) Considering libmarblewidget-qt5-26:amd64 2 as a solution to digikam:amd64 0 Re-Instated digikam-data:amd64 Re-Instated digikam:amd64 Done The following package was automatically installed and is no longer required: kde-l10n-engb Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: digikam digikam-data kde-l10n-engb libmarblewidget-qt5-27 marble marble-data marble-plugins marble-qt Suggested packages: digikam-doc gosmore monav-routing-daemon routino The following packages will be REMOVED libmarblewidget-qt5-26 The following NEW packages will be installed libmarblewidget-qt5-27 The following packages will be upgraded: digikam digikam-data kde-l10n-engb libastro1 marble marble-data marble-plugins marble-qt When I ran this, the system upgraded without issue. Thanks for the suggestion. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379105] Neon Packaging issue with KDE Apps 17.04
https://bugs.kde.org/show_bug.cgi?id=379105 --- Comment #2 from Vangelis --- $ sudo apt-get install libastro1 Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 3 Starting 2 pkgProblemResolver with broken count: 3 Investigating (0) libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) Broken libmarblewidget-qt5-26:amd64 Depends on libastro1 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:16.12.3-0neon+16.04+build28) Considering libastro1:amd64 10003 as a solution to libmarblewidget-qt5-26:amd64 2 Removing libmarblewidget-qt5-26:amd64 rather than change libastro1:amd64 Investigating (0) marble-plugins [ amd64 ] < 4:16.12.3-0neon+16.04+build28 -> 4:17.04.0-0neon+16.04+build31 > ( misc ) Broken marble-plugins:amd64 Depends on libmarblewidget-qt5-27 [ amd64 ] < none -> 4:17.04.0-0neon+16.04+build31 > ( libs ) (= 4:17.04.0-0neon+16.04+build31) Considering libmarblewidget-qt5-27:amd64 0 as a solution to marble-plugins:amd64 2 Re-Instated libmarblewidget-qt5-27:amd64 Re-Instated marble-plugins:amd64 Investigating (0) digikam [ amd64 ] < 4:5.4.0-0neon+16.04+build14 -> 4:5.5.0-0neon+16.04+build18 > ( graphics ) Broken digikam:amd64 Depends on libmarblewidget-qt5-26 [ amd64 ] < 4:16.12.3-0neon+16.04+build28 > ( libs ) Considering libmarblewidget-qt5-26:amd64 2 as a solution to digikam:amd64 1 Re-Instated digikam-data:amd64 Re-Instated digikam:amd64 Investigating (0) showfoto [ amd64 ] < 4:5.4.0-0neon+16.04+build14 -> 4:5.5.0-0neon+16.04+build18 > ( graphics ) Broken showfoto:amd64 Depends on digikam [ amd64 ] < 4:5.4.0-0neon+16.04+build14 -> 4:5.5.0-0neon+16.04+build18 > ( graphics ) (= 4:5.4.0-0neon+16.04+build14) Considering digikam:amd64 1 as a solution to showfoto:amd64 0 Re-Instated showfoto:amd64 Done The following additional packages will be installed: digikam digikam-data libmarblewidget-qt5-27 marble marble-data marble-plugins showfoto Suggested packages: digikam-doc gosmore monav-routing-daemon routino The following packages will be REMOVED: libmarblewidget-qt5-26 The following NEW packages will be installed: libmarblewidget-qt5-27 The following packages will be upgraded: digikam digikam-data libastro1 marble marble-data marble-plugins showfoto 7 upgraded, 1 newly installed, 1 to remove and 70 not upgraded. Need to get 126 MB of archives. After this operation, 35.9 MB of additional disk space will be used. Do you want to continue? [Y/n] -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379116] New: Failure when updating kate
https://bugs.kde.org/show_bug.cgi?id=379116 Bug ID: 379116 Summary: Failure when updating kate Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages Dev Edition [unstable] Assignee: neon-b...@kde.org Reporter: mgraess...@kde.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: kate : Depends: kate5-data (>= 4:17.04.0+p16.04+git20170423.0131-0) but 4:17.04.0+p16.04+git20170421.0347-0 is installed E: Unmet dependencies. Try using -f. sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies...Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following additional packages will be installed: kate5-data The following packages will be upgraded: kate5-data 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 43 not fully installed or removed. Need to get 0 B/1.210 kB of archives. After this operation, 12,3 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 323185 files and directories currently installed.) Preparing to unpack .../kate5-data_4%3a17.04.0+p16.04+git20170423.0131-0_all.deb ... Unpacking kate5-data (4:17.04.0+p16.04+git20170423.0131-0) over (4:17.04.0+p16.04+git20170421.0347-0) ... dpkg: error processing archive /var/cache/apt/archives/kate5-data_4%3a17.04.0+p16.04+git20170423.0131-0_all.deb (--unpack): trying to overwrite '/usr/share/locale/nb/LC_MESSAGES/plasma_applet_org.mo', which is also in package kdeplasma-addons-data 4:5.9.4+p16.04+git20170422.0314-0 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/kate5-data_4%3a17.04.0+p16.04+git20170423.0131-0_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379091] wrong libastro1 package to be installed borks update
https://bugs.kde.org/show_bug.cgi?id=379091 Jonathan Riddell changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from Jonathan Riddell --- so looks all good -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 379105] Neon Packaging issue with KDE Apps 17.04
https://bugs.kde.org/show_bug.cgi?id=379105 --- Comment #3 from Vangelis --- In the previous comment I just posted what happens if I ask to install libastro1. I haven't installed it yet! Let me know if you need me do any more testing in order to get the problem resolved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379117] New: META key to invoke menu stop working after changing shortcuts in Custom Shortcuts settings
https://bugs.kde.org/show_bug.cgi?id=379117 Bug ID: 379117 Summary: META key to invoke menu stop working after changing shortcuts in Custom Shortcuts settings Product: plasmashell Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: davidi...@seznam.cz CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 When I try to change the settings of my shortcuts: http://imgur.com/a/MqunL The Meta key stops working when pressed alone. So, I can't just press the meta key for getting the menu to show, but I need to use alt + f2 or click on the Plasma menu icon. Another interesting thing is that I have tried to set meta + j for activate task manager entry 1, meta + k for task man. entry 2, meta + l for 3 and meta + ; for task man. entry 4 and all except meta + k worked. Then I restarted the system and everything suddenly started to work again - including meta + k. Maybe the custom shortcuts part of plasma mess some things up or general settings when clicked on apply? Could somebody look at this bug? Thanks. Here are links where I talk about these issues: https://www.reddit.com/r/kde/comments/671mh0/i_find_out_when_the_meta_key_for_invoking_the/ https://www.reddit.com/r/kde/comments/671ksa/unable_to_set_meta_k_as_a_custom_shortcut/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379117] META key to invoke menu stop working after changing shortcuts in Custom Shortcuts settings
https://bugs.kde.org/show_bug.cgi?id=379117 --- Comment #1 from davidka --- How do I edit the bug description? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 379116] Failure when updating kate
https://bugs.kde.org/show_bug.cgi?id=379116 Harald Sitter changed: What|Removed |Added Assignee|neon-b...@kde.org |caslav.i...@gmx.net Severity|normal |major Component|Packages Dev Edition|general |[unstable] | CC||aleix...@kde.org, ||kdelibs-b...@kde.org Product|neon|frameworks-ki18n --- Comment #1 from Harald Sitter --- I think something broke in ki18n there. CCing Aleix as he's done some changes in the area. Note that both packages install `/usr/share/locale/nb/LC_MESSAGES/plasma_applet_org.mo`. The original po in kate's case was named `plasma_applet_org.kde.plasma.katesessions.po`, so it appears a regex is doing a poor job of handling points in the file name, losing everything after the first which naturally leads to file clashes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 379116] Failure when updating kate
https://bugs.kde.org/show_bug.cgi?id=379116 --- Comment #2 from Jonathan Riddell --- I'm confused what this has to do with ki18n, surely if the neon dev packages are including the wrong .po file that's a problem made by neon's scripts for working out what .po files to include? The released Kate includes the correct one. (To workaround this run sudo dpkg --install --force-overwrite /var/cache/apt/archives/kate5-data_4%3a17.04.0+p16.04+git20170423.0131-0_all.deb ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370583] In a dual monitor setup, if a Plasma panel is in between the monitors, windows will sometimes be moved to the bottom of the screen during cursor movement.
https://bugs.kde.org/show_bug.cgi?id=370583 Vassiliy changed: What|Removed |Added CC||taranov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370583] In a dual monitor setup, if a Plasma panel is in between the monitors, windows will sometimes be moved to the bottom of the screen during cursor movement.
https://bugs.kde.org/show_bug.cgi?id=370583 --- Comment #3 from Vassiliy --- I can reproduce this bug any time with the configuration. ➜ ~ lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description:Linux Mint 18.1 Serena Release:18.1 Codename: serena ➜ ~ konsole --version Qt: 5.6.1 KDE Frameworks: 5.28.0 Konsole: 16.04.3 ➜ ~ dolphin --version dolphin 16.04.3 I have a laptop(1920x1080) and monitor(2560x1080) https://www.dropbox.com/s/1cw09hncn11kp8l/screen.mkv?dl=0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379118] New: Discover became useless with bug. (He doesn't show programs, only fonts and vidgets)
https://bugs.kde.org/show_bug.cgi?id=379118 Bug ID: 379118 Summary: Discover became useless with bug. (He doesn't show programs, only fonts and vidgets) Product: Discover Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kirillov2...@gmail.com Target Milestone: --- Created attachment 105156 --> https://bugs.kde.org/attachment.cgi?id=105156&action=edit Discover doesn't show programs, only plasma vidgets and fonts. Discover hasn't been working since updating system kubuntu 14.04 into 16.04. Yes, it updates all packages and programs, but I have konsole and apt (or apt-get, or aptitude)for this. I need to download programs more comfortable than in konsole, but Discover just can't show me them. (Working sections are only vidgets and fonts) Please, help me. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379118] Discover became useless with bug. (He doesn't show programs, only fonts and vidgets)
https://bugs.kde.org/show_bug.cgi?id=379118 Alex changed: What|Removed |Added Keywords||Brainstorm, usability -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379118] Discover became useless with bug. (He doesn't show programs, only fonts and widgets)
https://bugs.kde.org/show_bug.cgi?id=379118 Alex changed: What|Removed |Added Summary|Discover became useless |Discover became useless |with bug. (He doesn't show |with bug. (He doesn't show |programs, only fonts and|programs, only fonts and |vidgets)|widgets) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 379118] Discover became useless with bug. (He doesn't show programs, only fonts and widgets)
https://bugs.kde.org/show_bug.cgi?id=379118 Alex changed: What|Removed |Added Attachment #105156|Discover doesn't show |Discover doesn't show description|programs, only plasma |programs, only plasma |vidgets and fonts. |widgets and fonts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379117] META key to invoke menu stop working after changing shortcuts in Custom Shortcuts settings
https://bugs.kde.org/show_bug.cgi?id=379117 --- Comment #2 from Christoph Feck --- Just add a comment with your findings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373514] kwin_wayland crashes after Alt+Tab
https://bugs.kde.org/show_bug.cgi?id=373514 Martin Gräßlin changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #5 from Martin Gräßlin --- Waiting for response for further investigation. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 379119] New: Amarok crashes while attempting to "Get Tags from MusicBrainz"
https://bugs.kde.org/show_bug.cgi?id=379119 Bug ID: 379119 Summary: Amarok crashes while attempting to "Get Tags from MusicBrainz" Product: amarok Version: 2.8.0 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: kri...@kristawhipple.com Target Milestone: 2.9 Application: amarok (2.8.0) KDE Platform Version: 4.14.21 Qt Version: 4.8.7 Operating System: Linux 4.4.38 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: Application: Amarok OS: Slackware 14.2 x64 (4.4.38) WM: Xfce 4.12 Steps to reproduce: Right click on an artist or album - click "Edit Track Details" Click "Get Tags from MusicBrainz" Tracks populate in the "MusicBrainz Tagger" window. When the progress bar reads 100%, Amarok crashes. The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fabe422f7c0 (LWP 12621))] Thread 17 (Thread 0x7fab13fff700 (LWP 12641)): #0 0x7fabdf9c036f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabdffa85aa in () at /usr/lib64/qt/lib/libQtScript.so.4 #2 0x7fabdffa85d9 in () at /usr/lib64/qt/lib/libQtScript.so.4 #3 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #4 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fab2914b700 (LWP 12640)): #0 0x7fabda8c7849 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fabda884191 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7fabda8848df in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fabda884a6c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fabe16400ce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #5 0x7fabe16105d1 in QEventLoop::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #6 0x7fabe16108e5 in QEventLoop::exec(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #7 0x7fabe1509c39 in QThread::exec() () at /usr/lib64/qt/lib/libQtCore.so.4 #8 0x7fabe150c3bc in () at /usr/lib64/qt/lib/libQtCore.so.4 #9 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #10 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fab2a14d700 (LWP 12637)): #0 0x7fabdf9c036f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe150c8d4 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/qt/lib/libQtCore.so.4 #2 0x7fabdea1866c in () at /usr/lib64/libthreadweaver.so.4 #3 0x7fabdea1b0a3 in () at /usr/lib64/libthreadweaver.so.4 #4 0x7fabdea19d7f in ThreadWeaver::Thread::run() () at /usr/lib64/libthreadweaver.so.4 #5 0x7fabe150c3bc in () at /usr/lib64/qt/lib/libQtCore.so.4 #6 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #7 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fab2b18b700 (LWP 12636)): #0 0x7fabe0e34e3d in read () at /lib64/libc.so.6 #1 0x7fabda8c6630 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fabda884494 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fabda884908 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fabda884ce2 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #5 0x7fabd0749986 in () at /usr/lib64/libgio-2.0.so.0 #6 0x7fabda8aa275 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #8 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fab2b98c700 (LWP 12635)): #0 0x7fabe0e3930d in poll () at /lib64/libc.so.6 #1 0x7fabda884964 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fabda884a6c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fabda884aa9 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fabda8aa275 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #6 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fab788ae700 (LWP 12634)): #0 0x7fabdf9c036f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabd8326d9d in () at /usr/lib64/qt/lib/libQtWebKit.so.4 #2 0x7fabd8326df9 in () at /usr/lib64/qt/lib/libQtWebKit.so.4 #3 0x7fabdf9ba684 in start_thread () at /lib64/libpthread.so.0 #4 0x7fabe0e44efd in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fab89bf2700 (LWP 12633)): #0 0x7fabdf9c036f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fabe150c8d4 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/qt/lib/libQtCore.so.4 #2 0x7fabdea1866c i
[Discover] [Bug 379120] New: Discover Applications would crash when clicking back button
https://bugs.kde.org/show_bug.cgi?id=379120 Bug ID: 379120 Summary: Discover Applications would crash when clicking back button Product: Discover Version: 5.9.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: cruzh...@att.net Target Milestone: --- Application: plasma-discover (5.9.4) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-19-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: When I would view an application then click the back button, the application would crash. I could restart the program and repeat several times in a row. The crash can be reproduced every time. -- Backtrace: 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 0x7fc8342e1440 (LWP 3887))] Thread 10 (Thread 0x7fc790ff9700 (LWP 3927)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc830284b4b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc8336ca495 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7fc8336cad8a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fc830283c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc82c65e6da in start_thread (arg=0x7fc790ff9700) at pthread_create.c:456 #6 0x7fc82f88717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 9 (Thread 0x7fc7ed2fb700 (LWP 3902)): #0 0x7fc82f876cad in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc82a553b30 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc82a50f042 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc82a50f514 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc82a50f68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc8304a7f2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc83045188a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc83027efe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc830283c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc82c65e6da in start_thread (arg=0x7fc7ed2fb700) at pthread_create.c:456 #10 0x7fc82f88717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 8 (Thread 0x7fc7fccd3700 (LWP 3897)): #0 0x7fc82f87b18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc82a50f576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc82a50f68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc8304a7f2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc83045188a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc83027efe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc830283c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc82c65e6da in start_thread (arg=0x7fc7fccd3700) at pthread_create.c:456 #8 0x7fc82f88717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 7 (Thread 0x7fc7fe9a3700 (LWP 3895)): #0 0x7fc82a50c55f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc82a50ea0b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc82a50f49b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc82a50f902 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc800793476 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7fc82a536f65 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc82c65e6da in start_thread (arg=0x7fc7fe9a3700) at pthread_create.c:456 #7 0x7fc82f88717f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7fc7ff1a4700 (LWP 3894)): #0 0x7fc82f87b18d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc82a50f576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc82a50f68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc82a50f6d1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc82a536f65 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc82c65e6da in start_thread (arg=0x7fc7ff1a4700) at pthread_create.c:456 #6 0x7fc82f88717f in clon
[kwin] [Bug 361598] Alt+Tab does not always work when pressing it quickly
https://bugs.kde.org/show_bug.cgi?id=361598
Daniel Lichtenberger changed:
What|Removed |Added
CC||daniel.lichtenber...@gmx.ne
||t
--- Comment #4 from Daniel Lichtenberger ---
I also experience this problem with Plasma 5.9.4. I tried disabling/modifying
various desktop effects, reducing or increasing animation speed, as well as
using the compact application switcher.
When the application switcher fails, the Alt+Tab command seems to be
registered. The current window briefly loses focus, but it is re-focused after
a short delay instead of switching to the previous window.
I can kind of reliably reproduce the issue using xdotool, to rule out keyboard
or keypress timing issues:
for i in {1..10}; do echo 'Switching...'; xdotool key 'alt+Tab'; sleep 1; done
Usually this works as expected, toggling between the konsole window and the
previously selected window, but sometimes the same window gets focused multiple
times. I used several applications as the previous window (Dolphin, Firefox, VS
Code, ...), but couldn't notice a pattern. Is there any debug output that could
help diagnose the problem?
--
You are receiving this mail because:
You are watching all bug changes.
[calligraplan] [Bug 359537] Calligra Plan Crash every time when try to start a templet
https://bugs.kde.org/show_bug.cgi?id=359537 --- Comment #8 from Dag Andersen --- This is a different issue. The symbol indicates it's a crash in KGantt. KGantt has been moved out of calligra and is a separate package now. Could you report it there? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 379100] generate data from function does nothing
https://bugs.kde.org/show_bug.cgi?id=379100 Stefan Gerlach changed: What|Removed |Added Component|frontend|general Ever confirmed|0 |1 CC||stefan.gerlach@uni-konstanz ||.de Status|UNCONFIRMED |CONFIRMED Assignee|alexander.se...@web.de |stefan.gerlach@uni-konstanz ||.de Severity|normal |major --- Comment #1 from Stefan Gerlach --- * works on Linux * "x" works, "2*x" and "exp(x)" does not -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379121] New: "Output destination" uses wrong dialog on GNOME, making choosing destination impossible
https://bugs.kde.org/show_bug.cgi?id=379121 Bug ID: 379121 Summary: "Output destination" uses wrong dialog on GNOME, making choosing destination impossible Product: kdenlive Version: 16.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: mikekla...@gmail.com Target Milestone: --- Created attachment 105157 --> https://bugs.kde.org/attachment.cgi?id=105157&action=edit Image showing the wrong dialog. This is a simple bug that comes from running Kdenlive on GNOME and not on Plasma. Steps to reproduce the bug: 1. On a GNOME Shell session, click the "render" button or go to "Project - Render" in the menu bar. The render options dialog opens. 2. Click the folder button next to "output destination" to attempt to change the output destination. Expected Result: A "save file" dialog should appear. Actual result: An "open file" dialog appears and picking a file destination is not possible. Is Kdenlive using Zenity for the GNOME file dialogs? If so we could fix this just by adding '--save' as a parameter for the window opened by the "Output Destination" button. If not, I do not expect it should be too hard to fix, since it's only some sort of shell/front-end/toolkit calling the wrong dialog for GNOME. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379121] "Output destination" uses wrong dialog on GNOME, making choosing destination impossible
https://bugs.kde.org/show_bug.cgi?id=379121 Mike Ironfist changed: What|Removed |Added Severity|minor |normal -- You are receiving this mail because: You are watching all bug changes.
[calligraplan] [Bug 359537] Calligra Plan Crash every time when try to start a templet
https://bugs.kde.org/show_bug.cgi?id=359537 --- Comment #9 from Andreas Plank --- Thanks for your tip with KGantt2. I feel somewhat ashamed for having reported it here because it turned out I was lax in setting repository priorities, hence the system did install libKGantt2 (5.0.0git-13.1) from another repository but I actually needed version 2.6.0-14.1 of http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.2/ of the same repo from which I obtained calligraplan. In my case this solved the issue: zypper install --oldpackage --details libKGantt2=2.6.0-14.1 libKChart2=2.6.0-14.1 -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 379122] New: KTouch Empty page on startup
https://bugs.kde.org/show_bug.cgi?id=379122 Bug ID: 379122 Summary: KTouch Empty page on startup Product: ktouch Version: 16.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: philippe.ques...@gmail.com Target Milestone: --- On Xubuntu 17.04, KTouch opens with an empty page. I can see the following message if I start it from a console: file:///usr/share/ktouch/qml/main.qml:19:1: module "QtQuick" is not installed import QtQuick 2.4 ^ >From what I can see, QtQuick 5.7.1 is installed. I can also see dependencies in the package for libqt5quick5 (>=5.6.1) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379123] New: digikam crashes after update to kde 17.04.0 and setting a link /lib/libmarblewidget-qt5.so.26 -> libmarblewidget-qt5.so.0.27.0
https://bugs.kde.org/show_bug.cgi?id=379123 Bug ID: 379123 Summary: digikam crashes after update to kde 17.04.0 and setting a link /lib/libmarblewidget-qt5.so.26 -> libmarblewidget-qt5.so.0.27.0 Product: digikam Version: 5.6.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: blumensch...@dokom.net Target Milestone: --- Application: digikam (5.6.0) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.11-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: crashes on startup: digikam.geoiface: QFSFileEngine::open: No file name specified digikam.geoiface: "setting backend marble" digikam.geoiface: "ROADMAP" digikam.facesengine: Face database ready for use digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer digikam.facesengine: Face database ready for use digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer QFSFileEngine::open: No file name specified digikam.geoiface: "setting backend marble" digikam.geoiface: "ROADMAP" digikam.geoiface: "setting backend marble" digikam.geoiface: "ROADMAP" digikam.geoiface: KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f43cfc7a640 (LWP 7117))] Thread 42 (Thread 0x7f42753dc700 (LWP 7228)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 41 (Thread 0x7f4275bdd700 (LWP 7227)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 40 (Thread 0x7f42763de700 (LWP 7226)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 39 (Thread 0x7f4276bdf700 (LWP 7225)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 38 (Thread 0x7f42773e0700 (LWP 7224)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f43c6d4bb7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f43c6db55b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f43cbc1a6d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f43ca8062e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f43caf1554f in clone () at /usr/lib/libc.so.6 Thread 37 (Thread 0x7f4277be1700 (LWP 7223)): #0 0x7f43ca80c756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f43cbc1b7cb in QWaitCondition::wa
[marble] [Bug 379123] digikam crashes after update to kde 17.04.0 and setting a link /lib/libmarblewidget-qt5.so.26 -> libmarblewidget-qt5.so.0.27.0
https://bugs.kde.org/show_bug.cgi?id=379123 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |general CC||caulier.gil...@gmail.com Version|5.6.0 |unspecified Product|digikam |marble Target Milestone|--- |some future version Assignee|digikam-de...@kde.org |marble-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379117] META key to invoke menu stop working after changing shortcuts in Custom Shortcuts settings
https://bugs.kde.org/show_bug.cgi?id=379117 --- Comment #3 from davidka --- ok -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 379124] New: Financial Year issue
https://bugs.kde.org/show_bug.cgi?id=379124 Bug ID: 379124 Summary: Financial Year issue Product: kmymoney4 Version: 4.8.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: nicolas.puir...@gmail.com Target Milestone: --- Hello Before explanation, sorry for my english, I am french (and my KMyMoney is in french mode). In the KMyMoney configuration, in General page, I set the begin of the fiscal year to the 1st July. When I list the operations, I see the "This year" in yellow, but the begin is the 1st January (and not the 1st July as set in configuration). => not critic When I want to set a budget, the fiscal year beginning is not taking into account. Indeed, the 12 months are listed in order (January to December) and not to July to June. The budget seems to use a civil year and not the fiscal year. => critic Perhaps I am the bug :). Thank you a lot for your response Regards Nicolas -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379125] New: Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 Bug ID: 379125 Summary: Opening with... in file manager results in for every image digiKam instance spawns Product: digikam Version: 5.5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Workflow Assignee: digikam-de...@kde.org Reporter: piroxil...@gmail.com Target Milestone: --- Thank you, digiKam guys. Steps to reproduce: 1. Use any file manager. (I use Dolphin) 2. In file manager open a folder with number of images. 3. Select a number of images. 4. Open Right click menu -> Open with... and open them with digiKam. 5. digiKam is going to load a new instance for every image. (I had 100 images selected, and my desktop machine gone to almost unresponsive state. So I needed to somehow execute `killall digiKam`) Additional information: digikam (5.5.0) Kwin_wayland (kwin 5.9.4) Plasma Desktop (5.9.4) Arch Linux (Linux Archer 4.10.10-1-ARCH #1 SMP PREEMPT Wed Apr 12 18:50:28 CEST 2017 x86_64 GNU/Linux) P.S. 1. Severity Effect of bug can be equal to "Crash" severity, because it hangs all system almost completely. I waited for 20 minutes for desktop to sort-out situation. But in the end I needed take another 5 minutes to login to Linux console and kill all digiKam instances. 2. What I wanted to do Basically I was figuring-out how to import images to my album structure. And tried this variant. As a user I expected: Select one image - open import dialog for that image. Or ask me for action. Select bunch of images - open import dialog for that images. Or ask me for action. If images are in albums already - select them there. Or ask me for a custom action. Asking what I want to do. If some images already present - have option to ignore already imported images, report how much of them ignored, how much left to import and view of them (with a button to view what images was ignored, and where they are already in digiKam). Thank you, I appreciate digiKam. Regards, Anton Latukha. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379125] Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |DOWNSTREAM CC||caulier.gil...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- Who setup to open image with digiKam. This is not the right way to configure the desktop. The application to use is Showfoto, not digiKam. Showfoto is the digiKam stand alone version of image editor. digiKam is a photo management program which need to setup collection to be used. It do not use image as well in CLI. So report this problem to ArchLinux team. The package is not configured properly. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] New: digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 Bug ID: 379126 Summary: digiKam on Wayland Plasma crashes at start Product: digikam Version: 5.5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: piroxil...@gmail.com Target Milestone: --- Application: digikam (5.5.0) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.10-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Starting digiKam application. (From Application Launcher.) - Custom settings of the application: Plasma on Wayland - Additional information: digikam (5.5.0) Kwin_wayland (kwin 5.9.4) Plasma Desktop (5.9.4) Arch Linux (Linux Archer 4.10.10-1-ARCH #1 SMP PREEMPT Wed Apr 12 18:50:28 CEST 2017 x86_64 GNU/Linux) The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f034bcc8680 (LWP 23631))] Thread 84 (Thread 0x7f02171d6700 (LWP 23768)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 83 (Thread 0x7f02179d7700 (LWP 23767)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 82 (Thread 0x7f02181d8700 (LWP 23766)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 81 (Thread 0x7f02189d9700 (LWP 23765)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 80 (Thread 0x7f02191da700 (LWP 23764)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 79 (Thread 0x7f02199db700 (LWP 23763)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 78 (Thread 0x7f021a1dc700 (LWP 23762)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1
[digikam] [Bug 379126] digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 --- Comment #1 from Anton Latuha --- Created attachment 105158 --> https://bugs.kde.org/attachment.cgi?id=105158&action=edit system log from start of application to finish System log during digiKam start and crash. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 --- Comment #3 from Dr. Chapatin --- Created attachment 105159 --> https://bugs.kde.org/attachment.cgi?id=105159&action=edit k3b 2.0.3 and k3b 17.04 This bug is not fixed on k3b 17.04 running on Arch. Compare these two screenshots: K3b 2.0.3 screenshot shows correct disc space/time bar. K3b 17.04 screenshot shows thin disc space/time bar, I cant read used/available disc space/time. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 374563] Device is not accessible when in sleep mode
https://bugs.kde.org/show_bug.cgi?id=374563 pmarget...@gmail.com changed: What|Removed |Added CC||pmarget...@gmail.com --- Comment #1 from pmarget...@gmail.com --- Environment: Phone model: Xiaomi Redmi note 3 pro (MIUI 8.2 global ROM) KDE Connect 1.6 on phone, 1.0.3-1 PC Phone and PC have been paired. Steps to reproduce: -let phone enter standby -reboot PC Result: "No paired devices available" until phone is first activated from standby. As soon as the screen goes on, everything KDE connect related starts working, I don't even need to unlock it. Reproducible: always. Notes: KDE Connect on phone granted every priviledge (auto-start, read SMS, allow notifications on lock screen etc) I'm hereby confirming the bug. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 379093] Spectacle logs user out of the system when user clicks Export image > Share > Save as
https://bugs.kde.org/show_bug.cgi?id=379093 ruudolfs.strazd...@gmail.com changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from ruudolfs.strazd...@gmail.com --- And it gets even more bizarre because sometimes the SDDM screen is windowed with the system title bar visible. I could resize the window, move it around, etc. And there's a notification in the system tray widget that reads Copying data:[,,,]. Here's the image that I tried to screenshot: http://i.imgur.com/Wv7RqyU.png?1 And here's the very long error window: http://i.imgur.com/GifQhpw.jpg And here's the error itself: http://i.imgur.com/Mw0lEoC.gifv Maybe the option to save the image from Export > Share > Save as should be removed since the image can already be saved. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- digiKam 5.6.0 pre version do not crash under Wayland using Linux Mageia 6 Cauldron, with Plasma 5 desktop. The backtrace do not show a specific code in digiKam which crash the application. It decent in-deep in Qt5 and the system libraries. Also, if you can install debug symbols this can help to investigate. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 Dr. Chapatin changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space/time bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 Dr. Chapatin changed: What|Removed |Added Summary|Disc space bar is broken|Disc space/time bar is ||broken -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 Dr. Chapatin changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 379123] digikam crashes after update to kde 17.04.0 and setting a link /lib/libmarblewidget-qt5.so.26 -> libmarblewidget-qt5.so.0.27.0
https://bugs.kde.org/show_bug.cgi?id=379123 Dennis Nienhüser changed: What|Removed |Added CC||nienhue...@kde.org --- Comment #1 from Dennis Nienhüser --- I just installed latest digikam on arch, which consists of marble-common-17.04.0-1 marble-data-17.04.0-1 digikam-5.5.0-2. This works fine here. Does the crash occur every time you start digikam? The symlink mentioned in the title is not needed anymore after https://mail.kde.org/pipermail/release-team/2017-April/010244.html. It could be a problem even, can you remove it and try with the latest arch packages to see if that makes a difference? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space/time bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 --- Comment #4 from Dr. Chapatin --- Created attachment 105160 --> https://bugs.kde.org/attachment.cgi?id=105160&action=edit k3b 2.0.3 screenshot -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377105] Disc space/time bar is broken
https://bugs.kde.org/show_bug.cgi?id=377105 Dr. Chapatin changed: What|Removed |Added Attachment #105159|k3b 2.0.3 and k3b 17.04 |k3b 17.04 screenshot description|| -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 379127] New: K3B does not show the splashscreen correctly
https://bugs.kde.org/show_bug.cgi?id=379127 Bug ID: 379127 Summary: K3B does not show the splashscreen correctly Product: k3b Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: GUI/Usability Assignee: k...@kde.org Reporter: yy...@gmx.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 105161 --> https://bugs.kde.org/attachment.cgi?id=105161&action=edit screencast I'm running K3B 17.04 on Arch. The splashscreen appears quickly, disappears and reappears with some transparency. Watch the screencast please. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 328928] Add text word wrap for all tooltips
https://bugs.kde.org/show_bug.cgi?id=328928 Alex Bikadorov changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kru ||sader/0e661e9fd290fc22f27e4 ||a844e26a4cc0ffd7e1b --- Comment #1 from Alex Bikadorov --- Git commit 0e661e9fd290fc22f27e4a844e26a4cc0ffd7e1b by Alexander Bikadorov. Committed on 18/04/2017 at 14:01. Pushed by abikadorov into branch 'master'. Panel: Added detailed tooltip for filename column in panel; Uses tooltip delay setting. + Merged duplicate code in KrSort and KrVfsModel FIXED: [ 328928 ] Add text word wrap for all tooltips M +21 -0krusader/GUI/krstyleproxy.cpp M +5-0krusader/GUI/krstyleproxy.h M +1-19 krusader/Panel/krinterbriefview.cpp M +0-1krusader/Panel/krinterbriefview.h M +15 -7krusader/Panel/krinterdetailedview.cpp M +3-15 krusader/Panel/krsort.cpp M +0-2krusader/Panel/krsort.h M +43 -25 krusader/Panel/krvfsmodel.cpp M +2-0krusader/Panel/krvfsmodel.h M +18 -2krusader/Panel/krview.cpp M +6-2krusader/Panel/krview.h M +1-1krusader/Panel/krviewitem.cpp https://commits.kde.org/krusader/0e661e9fd290fc22f27e4a844e26a4cc0ffd7e1b -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 tempel.jul...@gmail.com changed: What|Removed |Added CC||tempel.jul...@gmail.com --- Comment #14 from tempel.jul...@gmail.com --- I have found a workaround: When you login with "*" for both user and password for a share which doesn't require a password, add another "*" to the adress. Example: You have opened a share and the adress looks like this: smb://*@pcname/sharename/ Change it to smb://*:*@pcname/sharename/ and press enter. Voila, you should have write access. Can this please get fixed? It should be so easy and it's really annoying... -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 379128] New: Allow remote command: lock, halt, reboot KDE session
https://bugs.kde.org/show_bug.cgi?id=379128 Bug ID: 379128 Summary: Allow remote command: lock, halt, reboot KDE session Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: piotr.budny+bugs...@gmail.com Target Milestone: --- Android app could allow one-click session lock, halt or reboot, or, execute custom commands. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379129] New: Duplicate recent document opened
https://bugs.kde.org/show_bug.cgi?id=379129 Bug ID: 379129 Summary: Duplicate recent document opened Product: plasmashell Version: 5.9.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: danjar...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 105162 --> https://bugs.kde.org/attachment.cgi?id=105162&action=edit application launcher with recent documents duplicated the recent documents opened appear duplicates To reproduce: Open a file many times, and this files appear duplicate many times in krunner and laucher menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379129] Duplicate recent document opened
https://bugs.kde.org/show_bug.cgi?id=379129 --- Comment #1 from danjar...@gmail.com --- Created attachment 105163 --> https://bugs.kde.org/attachment.cgi?id=105163&action=edit krunner with recent documents duplicated -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 --- Comment #15 from mathoj...@gmail.com --- Thank you, I use a workaround too : I use ftps ;) But using a workaround is not a deal. And I really think that a network protocols should have a high priority in a DE. More and more NAS, multimedia servers ... are making use of : - SMB (bad implementation on KDE) - NFS (not implemented in KDE... incredible, but true) - DLNA/uPnP : there was a kio package for that, but I never successed to use it It's really not serious for a DE. I don't know how all of this is working on Gnome (never tried, because I'm an early fan of KDE, and plasma), but network protocols are a just weak and poor on KDE, and it's a big anomaly. I still hope a developper will fix it (and if he could work on NFS, and DLNA/uPnP would be great) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379130] New: KDE taskbar randomly crashing when clicking above any application icon.
https://bugs.kde.org/show_bug.cgi?id=379130 Bug ID: 379130 Summary: KDE taskbar randomly crashing when clicking above any application icon. Product: plasmashell Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ch.mercesmore...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.11.0-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Tried to open some application by its icon located on the KDE taskbar (botton left). Here is one image pointing out where is the location I'm talking about: http://imgur.com/uPAeBsE - Unusual behavior I noticed: The system freezes and the taskbar dissapears. After about 5 seconds the bar reappeares and the system goes back to normal state. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7ea45f6800 (LWP 908))] Thread 18 (Thread 0x7f3d7f70b700 (LWP 13723)): #0 0x7f7e9d260b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7e9e3a64c6 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7e9e3a1bc4 in () at /usr/lib/libQt5Core.so.5 #3 0x7f7e9e3a56d8 in () at /usr/lib/libQt5Core.so.5 #4 0x7f7e9d25a2e7 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f7e9dcb854f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f7d9cff9700 (LWP 2201)): #0 0x7f7e9d260756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7e9e3a658b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7de89981d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7de899c9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7de899ca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7de899a249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7e9e3a56d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f7e9d25a2e7 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f7e9dcb854f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f7d9d7fa700 (LWP 2200)): #0 0x7f7e9d260756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7e9e3a658b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7de89981d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7de899c9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f7de899ca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f7de899ca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f7de899ca32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f7de899a249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f7e9e3a56d8 in () at /usr/lib/libQt5Core.so.5 #13 0x7f7e9d25a2e7 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f7e9dcb854f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f7d9dffb700 (LWP 2199)): #0 0x7f7e9d260756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f7e9e3a658b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f7de89981d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f7de899c9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f7de8997263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Th
[Akonadi] [Bug 379131] New: Gmail authentication expires after some time
https://bugs.kde.org/show_bug.cgi?id=379131
Bug ID: 379131
Summary: Gmail authentication expires after some time
Product: Akonadi
Version: GIT (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: IMAP resource
Assignee: chrig...@fastmail.fm
Reporter: aro...@archlinux.org
CC: kdepim-b...@kde.org, vkra...@kde.org
Target Milestone: ---
This is with kmail/akonadi 5.5 (17.04). After running kmail for a few hours,
the Gmail account stops working. Folders are not synced anymore and messages
are not displayed.
I'm using two different Gmail accounts, in case it makes any difference.
Akonadi terminal output:
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.kimap: sasl_client_step failed with: -1 "SASL(0): successful
result: "
user=*user*(redacted)auth=Bearer*hash*(redacted)Pass a valid window to
KWallet::Wallet::openWallet().
qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on
non-plain connection
org.kde.pim.kimap: Connection to server lost 0
org.kde.pim.imapresource: Session login cancelled
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.kimap: sasl_client_step failed with: -1 "SASL(0): successful
result: "
user=**user2**(redacted)auth=Bearer**hash**(redacted)Pass a valid window to
KWallet::Wallet::openWallet().
qt.network.ssl: QSslSocket::startClientEncryption: cannot start handshake on
non-plain connection
org.kde.pim.kimap: Connection to server lost 0
org.kde.pim.imapresource: Session login cancelled
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
KGAPI2::EventFetchJob(0x10898a0) "Autenticación no válida."
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
KGAPI2::ContactsGroupFetchJob(0x24d1940) "Autenticación no válida."
org.kde.pim.akonadicore: Deleting items from the akonadi database failed: "No
items found"
org.kde.pim.akonadicore: Error during ItemSync: "Failed to parse stream"
CalendarFetchJob::url()
QUrl("https://www.googleapis.com/calendar/v3/users/me/calendarList";)
org.kde.pim.akonadicore: Received response with a different tag!
QIODevice::write (KTcpSocket): device not open
Pass a valid window to KWallet::Wallet::openWallet().
[SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
![SASL-XOAUTH2] - filling prompts
![SASL-XOAUTH2] - Requesting authID![SASL-XOAUTH2] - Requesting token
!org.kde.pim.akonadicore: Got a stale 'changed' notification for an item which
was already removed. 2137 ""
org.kde.pim.akonadicore: Got a stale 'changed' notification for an item which
was already removed. 2137 ""
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 376320] Task switcher themes not working under wayland
https://bugs.kde.org/show_bug.cgi?id=376320 Martin Vysny changed: What|Removed |Added CC||vy...@baka.sk -- You are receiving this mail because: You are watching all bug changes.
