[digikam] [Bug 366777] New: No preview for Time Adjust tool
https://bugs.kde.org/show_bug.cgi?id=366777 Bug ID: 366777 Summary: No preview for Time Adjust tool Product: digikam Version: 5.1.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: BatchQueueManager-Tool-TimeAdjust Assignee: digikam-de...@kde.org Reporter: m.krasilni...@yandex.ru After moving Time Adjust to BQM there is no more preview of a new time. Just old and new file names, which are useless. This makes the use of this tool is just awful. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366767] UNABLE TO CONTACT TIME SERVER every time I try to set the right time
https://bugs.kde.org/show_bug.cgi?id=366767 Burkhard Lueck changed: What|Removed |Added CC||lu...@hube-lueck.de Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Burkhard Lueck --- no usefull info about the bug, no version etc, just rant -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 97420] [usability] optionally show only characters available in selected font, sorted by group
https://bugs.kde.org/show_bug.cgi?id=97420 --- Comment #10 from Ian --- Hi I took a look at your proposal, thanks. I then realised what part of the problem is ... there are two different Use Cases for KCharSelect: 1. probably the original one, which probably dates all the way back to the similar program on Windows 3.1 ... you're typing something, need a ß character, and don't know the alt-/whatever code for it, so you fire up a Character Select program to find it, copy and paste. This use case predates Unicode. 2. Other use, (eg me) is to see which glyphs are in a font, and what they look like. This is to help in deciding which font to use for a particular job. In use case 1, you may be happy with QT/system substituting a glyph from a different font. In use case 2, you need to know exactly what's what. Use case 2 is actually "Font Browser" rather than Character Select, but the existing font browser on KDE is way underpowered for proper investigation of a font. (I guess it's also very old and possibly pre-unicode, where there were only a handful of glyphs in a font). So yes, your proposals will work for me, and are a definite improvement. My only issue is what is the default view, and that I suppose depends on whether you are targeting Use Case 1 or Use Case 2 I would prefer the greyed out as default, but I accept that those in Use Case 1 would prefer the other view. Thanks, Ian -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366776] Both body and list are empty
https://bugs.kde.org/show_bug.cgi?id=366776 --- Comment #1 from jarlgjess...@gmail.com --- Created attachment 100601 --> https://bugs.kde.org/attachment.cgi?id=100601&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366776] New: Both body and list are empty
https://bugs.kde.org/show_bug.cgi?id=366776 Bug ID: 366776 Summary: Both body and list are empty Product: kmail2 Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jarlgjess...@gmail.com There are no text in the subjscts in the list, though you can see the list it self. The body contains no content Reproducible: Always Steps to Reproduce: 1.Start Kmail 2. 3. Actual Results: As described Expected Results: The mail program should be functioning normally -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 351381] Video preview of clips with transitions in project monitor area is extremely slow
https://bugs.kde.org/show_bug.cgi?id=351381 --- Comment #12 from h.k.gh...@gmail.com --- (In reply to Wegwerf from comment #5) > Hkghost, can you please give the new beta 16.07.90 a test drive? It got > timeline preview rendering where you can prerender regions of your timeline. > See here: > https://thediveo-e.blogspot.de/2016/05/kdenlive-preview-rendering-odds-and- > ends.html So I added the kdenlive-master PPA and installed Kdenlive, which got me beta version 16.11.70. The time-line controls did absolutely nothing for me. Clicking the time-line options to "add preview zone" seemed to have no behavior bound to them and/or no visible feedback that it actually did anything. I couldn't define a preview zone while trying to mark areas in the time-line or anything. The steps in the page weren't that involved, so it looks like kdenlive has other problems. Also, when trying to find the time-line preview profiles under Settings >> Configure kdenlive, I found the preview profiles option is not even available/visible in the GUI for me. In the demo video, the user simply clicks on "add preview zone" and it looks like it was already there, although it does not show how to actually create the preview zone. The page made it look really straightforward and simple, so it doesn't look like I misunderstood. If you think I did, please clarify and provide a more up-to-date reference, since the GUI in the demo video and my version are not identical. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366775] New: System Settings crashes when closing out of Online Accounts
https://bugs.kde.org/show_bug.cgi?id=366775 Bug ID: 366775 Summary: System Settings crashes when closing out of Online Accounts Product: systemsettings Version: 5.7.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: a...@haxalot.com Application: systemsettings5 (5.7.3) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.6.0-sabayon x86_64 Distribution: "Sabayon Linux amd64 16.09" -- Information about the crash: - What I was doing when the application crashed: Browsing through several tabs in the control panel, visited every section under 'Application Style', then every section under 'Workspace Theme', finally going into 'Online Accounts' and viewing the settings of my Office365/Lync over libpurple account. System Settings crashes when attempting to close it from that screen. I've also been able to replicate it by opening other options sections first, though it doesn't seem to crash if I go directly to the 'Online Accounts' settings. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #6 0x7f3677b5acd5 in QHash, Tp::Connection::Private::HandleContext*>::findNode(QPair const&, unsigned int*) const () from /usr/lib64/libtelepathy-qt5.so.0 #7 0x7f3677b5c214 in QHash, Tp::Connection::Private::HandleContext*>::remove(QPair const&) () from /usr/lib64/libtelepathy-qt5.so.0 #8 0x7f3677b3687f in Tp::Connection::Private::~Private() () from /usr/lib64/libtelepathy-qt5.so.0 #9 0x7f3677b36d2d in Tp::Connection::~Connection() () from /usr/lib64/libtelepathy-qt5.so.0 #10 0x7f3677b36db9 in Tp::Connection::~Connection() () from /usr/lib64/libtelepathy-qt5.so.0 #11 0x7f3677a46f81 in Tp::Account::Private::~Private() () from /usr/lib64/libtelepathy-qt5.so.0 #12 0x7f3677a4719d in Tp::Account::~Account() () from /usr/lib64/libtelepathy-qt5.so.0 #13 0x7f3677a47229 in Tp::Account::~Account() () from /usr/lib64/libtelepathy-qt5.so.0 #14 0x7f3677a6bdc9 in QHash >::deleteNode2(QHashData::Node*) () from /usr/lib64/libtelepathy-qt5.so.0 #15 0x7f36bf3041d9 in QHashData::free_helper(void (*)(QHashData::Node*)) () from /usr/lib64/libQt5Core.so.5 #16 0x7f3677a6495c in Tp::AccountManager::Private::~Private() () from /usr/lib64/libtelepathy-qt5.so.0 #17 0x7f3677a64b3d in Tp::AccountManager::~AccountManager() () from /usr/lib64/libtelepathy-qt5.so.0 #18 0x7f3677a64bc9 in Tp::AccountManager::~AccountManager() () from /usr/lib64/libtelepathy-qt5.so.0 #19 0x7f36844a2acc in KAccountsUiProvider::~KAccountsUiProvider() () from /usr/lib64/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so #20 0x7f36844a2ba9 in KAccountsUiProvider::~KAccountsUiProvider() () from /usr/lib64/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so #21 0x7f3686d87c4e in UiPluginsManagerPrivate::~UiPluginsManagerPrivate() () from /usr/lib64/qt5/plugins/kcm_kaccounts.so #22 0x7f3686d87cd9 in (anonymous namespace)::Q_QGS_s_instance::innerFunction()::Holder::~Holder() () from /usr/lib64/qt5/plugins/kcm_kaccounts.so #23 0x7f36beb64452 in ?? () from /lib64/libc.so.6 #24 0x7f36beb644b8 in exit () from /lib64/libc.so.6 #25 0x7f36beb4da9b in __libc_start_main () from /lib64/libc.so.6 #26 0x0040c0b9 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 366774] New: Configuring external display not possible
https://bugs.kde.org/show_bug.cgi?id=366774 Bug ID: 366774 Summary: Configuring external display not possible Product: frameworks-plasma Version: 5.24.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: jarlgjess...@gmail.com Running on neos-5.7.3 I'm not able to rightclick on the desktop of my external display in order to configure it. Reproducible: Always Steps to Reproduce: 1.Connect external display 2.Rightclick to get the desktop menu appear Actual Results: No menu appears. And I'm stuck with a black screen Expected Results: The menu should have been displayed -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 366326] OFX direct download fails when OFX UID is expected by bank
https://bugs.kde.org/show_bug.cgi?id=366326 --- Comment #10 from Thomas Baumgart --- Just got a note from our friends over at LibOFX that 0.9.11 has been released (https://sourceforge.net/projects/libofx/) with the patch included (personal contacts rock). So let's wait and see once that makes it into downstream. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366761] Crash when selecting the Plastik window decoration
https://bugs.kde.org/show_bug.cgi?id=366761 Martin Gräßlin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- Sorry Qt is broken, best use Breeze *** This bug has been marked as a duplicate of bug 361236 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 Martin Gräßlin changed: What|Removed |Added CC||spalmr...@gmail.com --- Comment #30 from Martin Gräßlin --- *** Bug 366761 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366764] Unsupported Full Screen Mode (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366764 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Martin Gräßlin --- I doubt it's a KWin bug - KWin actually handles fullscreen correctly. The failure at least is consistent, I was able to reproduce with both Gwenview and KDevelop. Given https://bugreports.qt.io/browse/QTBUG-54883 I'm tempted to blame Qt, but I'll investigate more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.
https://bugs.kde.org/show_bug.cgi?id=366742 --- Comment #1 from Martin Gräßlin --- could you please install debug symbols for KWin and gdb into the kwin process with the high cpu usage and then provide us a backtrace of it? That should be something like: 1. ps -AF | grep kwin_x11 2. gdb --pid= 3. t a a bt -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366689] kwin_wayland segfault ... error 4 in libQt5Qml.so.5.7.0
https://bugs.kde.org/show_bug.cgi?id=366689 --- Comment #7 from Martin Gräßlin --- > I won't go into the particulars unless you think it will be useful. Yes please do. I need to know the conditions which don't work. Fixing those is mostly trivial, I just need to know what doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366769] Rename aborts after first rename of many
https://bugs.kde.org/show_bug.cgi?id=366769 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- What do you use as rename scheme to complete the operation ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366773] New: plasmashell crashes every time I try to unlock widgets
https://bugs.kde.org/show_bug.cgi?id=366773 Bug ID: 366773 Summary: plasmashell crashes every time I try to unlock widgets Product: plasmashell Version: 5.7.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: m...@th0th.me CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.7.3) Qt Version: 5.7.0 Frameworks Version: 5.25.0 Operating System: Linux 4.7.0-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Every time I try to unlock widgets (by right clicking the panel, using the menu icon at the top left, or right clicking desktop) plasmashell crashes. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f915dc777c0 (LWP 30698))] Thread 11 (Thread 0x7f907e880700 (LWP 30848)): #0 0x7f9156b7710f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9157a62c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f915b9cc435 in ?? () from /usr/lib/libQt5Quick.so.5 #3 0x7f915b9ccd2a in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7f9157a61d78 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f9156b71454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f91573777df in clone () from /usr/lib/libc.so.6 Thread 10 (Thread 0x7f9089713700 (LWP 30833)): #0 0x7f9156b7710f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9157a62c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f915b9cc435 in ?? () from /usr/lib/libQt5Quick.so.5 #3 0x7f915b9ccd2a in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7f9157a61d78 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f9156b71454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f91573777df in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f90a0b3c700 (LWP 30790)): #0 0x7f9156b7710f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9157a62c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f915b9cc435 in ?? () from /usr/lib/libQt5Quick.so.5 #3 0x7f915b9ccd2a in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7f9157a61d78 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f9156b71454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f91573777df in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f90a3eef700 (LWP 30775)): #0 0x7f9156b7710f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f9157a62c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f915b9cc435 in ?? () from /usr/lib/libQt5Quick.so.5 #3 0x7f915b9ccd2a in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7f9157a61d78 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f9156b71454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f91573777df in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f90a46f0700 (LWP 30757)): #0 0x7f915736e48d in poll () from /usr/lib/libc.so.6 #1 0x7f915261afd6 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f915261b0ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f9157c9059b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f9157c3a0da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f9157a5d0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f915b95d8a6 in ?? () from /usr/lib/libQt5Quick.so.5 #7 0x7f9157a61d78 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f9156b71454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f91573777df in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f913ccea700 (LWP 30736)): #0 0x7f9156b7710f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f915d3edac4 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f915d3edb09 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f9156b71454 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f91573777df in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f913e9ac700 (LWP 30711)): #0 0x7f915265f044 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f915261ab6a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #2 0x7f915261b040 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f915261b0ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f9157c9059b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f9157c3a0da in
[kmail2] [Bug 363531] TLS negotiation was unsuccessful
https://bugs.kde.org/show_bug.cgi?id=363531 --- Comment #5 from kdebugs.anon...@yahoo.com --- I also forgot to add that after closing the first 2 dialog boxes, a new dialog box appears titled "Connection Failed - Mail Dispatcher Agent" containing the following message: "Your SMTP server claims to support TLS, but negotiation was unsuccessful. You can disable TLS in the SMTP account settings dialog" -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 361846] Akregator Crashes When Adding a New Feed
https://bugs.kde.org/show_bug.cgi?id=361846 kdebugs.anon...@yahoo.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED CC||kdebugs.anon...@yahoo.com --- Comment #2 from kdebugs.anon...@yahoo.com --- (In reply to Laurent Montel from comment #1) > I can't reproduce it in last version. > could you verify with kdepim 5.1 or 5.2 ? > thanks As of Akregator Version 4.14.10, I can no longer reproduce this problem. It seems to work correctly now. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363531] TLS negotiation was unsuccessful
https://bugs.kde.org/show_bug.cgi?id=363531 --- Comment #4 from kdebugs.anon...@yahoo.com --- I forgot to add that my system is using openSUSE Leap 42.1 for x86_64. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363531] TLS negotiation was unsuccessful
https://bugs.kde.org/show_bug.cgi?id=363531 kdebugs.anon...@yahoo.com changed: What|Removed |Added CC||kdebugs.anon...@yahoo.com --- Comment #3 from kdebugs.anon...@yahoo.com --- I am having the same problem described above. This problem is repeatable 100% of the time. I can not send emails via SMTP using TLS over port 587 in KMail Version 4.14.10. :( :( Everything worked correctly in KMail yesterday, and now with no configuration changes, this problem appeared. Sending emails *without* transport encryption over port 587 works correctly. Here are the error details: 1) A dialog box pops up titled "Server Authentication - Mail Dispatcher Agent", containing the following message: "The server failed the authenticity check (smtp.q.com). The certificate authority's certificate is invalid The root certificate authority's certificate is not trusted for this purpose The certificate cannot be verified for internal reasons" 2) I click on the button labeled "Details". A new Dialog box pops up labeled "KDE SSL Information - Mail Dispatcher Agent" containing the following message: "Current connection is secured with SSL. Address: smtp.q.com IP address: 205.169.121.111 Encrypttion: AES, using 256 bits of a 256 bit key Details: Auth = RSA, Kx = RSA, MAC = SHA-1 SSL Version: SSLv3 Certificate chain: [greyed out drop-down menu]mail.q.com Start Tabs = [Tab: Subject] Common name: mail.q.com Organization: CenturyLink Organizational unit: Interactive Services Group Country: US State: Louisiana City: Monroe [Tab:Issuer] Common name: Symantec Class 3 Secure Server SHA256 SSL CA Organization: Symantec Corporation Organizational unit: Symantec Trust Network Country: US State: [blank] City: [blank] End Tabs = Trusted: NO, there were errors: The certificate authority's certificate is invalid The root certificate authority's certificate is not trusted for this purpose The certificate cannot be verified for internal reasons Validity period: 08/04/16 12:00 AM to 08/16/17 11:59 PM Serial number: 41:5b:6d:03:67:ea:aa:ba:df:f7:a5:68:66:9e:f0:60 MD5 digest: acc7ed0f204b8991296cb80aa368e88a SHA1 digest: b60c6182356616ee3dfb36d1df7f4c081cd5d7d7" 3) Then I click the dialog button labeled "Close". I am very puzzled by this, in part because KMail is configured to use TLS, yet the certificate information displayed is for SSL. I am further puzzled that the SMTP server is configured as "smtp.q.com", and NOT "mail.q.com" as suggested by the SSL certificate information in the second dialog box. Like sedrubal stated above, I too can send emails via SMTP using TLS using port 587 in Firebird version 45.2. If it would help, I can temporarily donate an email address with CenturyLink; yet, I can not guarantee it will work outside the USA. I was on the phone with my clown of an ISP (CenturyLink) for 4 hours, and they were not able to resolve the problem - which leaves me quite screwed. Please, please help! :( I really like KMail and REALLY do not want to switch to Thunderbird or anything else. -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 97420] [usability] optionally show only characters available in selected font, sorted by group
https://bugs.kde.org/show_bug.cgi?id=97420 --- Comment #9 from Christoph Feck --- https://git.reviewboard.kde.org/r/128680/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366772] Bad actualization to kubuntu 16.04
https://bugs.kde.org/show_bug.cgi?id=366772 Johnnyred2016 changed: What|Removed |Added Platform|Other |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366772] New: Bad actualization to kubuntu 16.04
https://bugs.kde.org/show_bug.cgi?id=366772 Bug ID: 366772 Summary: Bad actualization to kubuntu 16.04 Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: jre...@hotmail.com CC: plasma-b...@kde.org In the actualization, the desktop is in black & white, no image, plasma close requently. this is the report: Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-34-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb0759c38c0 (LWP 2941))] Thread 8 (Thread 0x7fafb1c00700 (LWP 3125)): #0 0x7fb06ceb3ac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb06ce6ef26 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb06ce6f400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb06ce6f4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb070a06a9b in QEventDispatcherGlib::processEvents (this=0x7fafac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fb0709addea in QEventLoop::exec (this=this@entry=0x7fafb1bffcc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fb0707ca8a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fafb40df7d7 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #8 0x7fb0707cf84e in QThreadPrivate::start (arg=0x2797ab0) at thread/qthread_unix.cpp:331 #9 0x7fb06f8bc6fa in start_thread (arg=0x7fafb1c00700) at pthread_create.c:333 #10 0x7fb0700e5b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fb040aa3700 (LWP 3001)): #0 0x7fb06ce6c3e7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb06ce6e8cb in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb06ce6f2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb06ce6f4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb070a06a9b in QEventDispatcherGlib::processEvents (this=0x7fafb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fb0709addea in QEventLoop::exec (this=this@entry=0x7fb040aa2c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fb0707ca8a4 in QThread::exec (this=this@entry=0x24efb80) at thread/qthread.cpp:503 #7 0x7fb0739f8ed6 in QQuickPixmapReader::run (this=0x24efb80) at util/qquickpixmapcache.cpp:817 #8 0x7fb0707cf84e in QThreadPrivate::start (arg=0x24efb80) at thread/qthread_unix.cpp:331 #9 0x7fb06f8bc6fa in start_thread (arg=0x7fb040aa3700) at pthread_create.c:333 #10 0x7fb0700e5b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fb0433ef700 (LWP 2993)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb075417bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fb075417c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fb06f8bc6fa in start_thread (arg=0x7fb0433ef700) at pthread_create.c:333 #4 0x7fb0700e5b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fb048e1b700 (LWP 2975)): #0 0x7fb06ceb3ae4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb06ce6edc9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb06ce6f340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb06ce6f4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb070a06a9b in QEventDispatcherGlib::processEvents (this=0x7fb03c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fb0709addea in QEventLoop::exec (this=this@entry=0x7fb048e1ace0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fb0707ca8a4 in QThread::exec (this=this@entry=0x23fa1a0) at thread/qthread.cpp:503 #7 0x7fb0730723c5 in QQmlThreadPrivate::run (this=0x23fa1a0) at qml/ftw/qqmlthread.cpp:141 #8 0x7fb0707cf84e in QThreadPrivate::start (arg=0x23fa1a0) at thread/qthread_unix.cpp:331 #9 0x7fb06f8bc6fa in start_thread (arg=0x7fb048e1b700) at pthread_create.c:333 #10 0x7fb0700e5b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fb04acf9700 (LWP 2969)): #0 0x7fb0707c79aa in QBasicAtomicOps<8>::testAndSetRelaxed (currentValue=, newValue=0x1, expectedValue=0x0, _q_value=@0x23260a8: 0x1) at ../../include/QtCore/../../src/corelib/ar
[dolphin] [Bug 366771] New: Dolphin crashes when intenting to assign Tags
https://bugs.kde.org/show_bug.cgi?id=366771 Bug ID: 366771 Summary: Dolphin crashes when intenting to assign Tags Product: dolphin Version: 15.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: benjamin.bu...@gmail.com Application: dolphin (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Whenever I try to assign Tags to a Directory or File, Dolphin crashes. I am on openSUSE Leap 42.1. I have attempted to duplicate the bug and it does happen every time I try to tag something from within Dolphin. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0e606717c0 (LWP 2026))] Thread 4 (Thread 0x7f0e4963b700 (LWP 2028)): #0 0x7f0e5ff1fbfd in poll () at /lib64/libc.so.6 #1 0x7f0e52f2b422 in () at /usr/lib64/libxcb.so.1 #2 0x7f0e52f2d00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f0e4b9903c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f0e5a02f32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f0e55add0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f0e5ff2802d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f0e3c182700 (LWP 2029)): #0 0x7f0e55ae103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0e42bd8aa3 in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f0e42bd8227 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f0e55add0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f0e5ff2802d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f0e36d5f700 (LWP 2030)): #0 0x7f0e5ff1bccd in read () at /lib64/libc.so.6 #1 0x7f0e54f98b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0e54f57999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f0e54f57df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f0e54f57f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f0e5a261d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f0e5a208d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f0e5a02a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f0e5a02f32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f0e55add0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f0e5ff2802d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f0e606717c0 (LWP 2026)): [KCrash Handler] #6 0x7f0e51c40388 in () at /usr/lib64/liblmdb-0.9.14.so #7 0x7f0e51c43fc3 in () at /usr/lib64/liblmdb-0.9.14.so #8 0x7f0e51c4269a in mdb_cursor_get () at /usr/lib64/liblmdb-0.9.14.so #9 0x7f0e5681d941 in Baloo::PostingDB::fetchTermsStartingWith(QByteArray const&) () at /usr/lib64/libKF5BalooEngine.so.5 #10 0x7f0e5682608d in Baloo::Transaction::fetchTermsStartingWith(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #11 0x7f0e5dd71d37 in Baloo::TagListJob::start() () at /usr/lib64/libKF5Baloo.so.5 #12 0x7f0e5e2fa587 in () at /usr/lib64/libKF5BalooWidgets.so.5 #13 0x7f0e5e2fb008 in () at /usr/lib64/libKF5BalooWidgets.so.5 #14 0x7f0e5e2f9ea1 in Baloo::TagWidget::slotShowAll() () at /usr/lib64/libKF5BalooWidgets.so.5 #15 0x7f0e5a23acc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x7f0e5b4bedd2 in QLabel::linkActivated(QString const&) () at /usr/lib64/libQt5Widgets.so.5 #17 0x7f0e5b4c1a21 in () at /usr/lib64/libQt5Widgets.so.5 #18 0x7f0e5a23acc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #19 0x7f0e5b542a25 in QWidgetTextControl::linkActivated(QString const&) () at /usr/lib64/libQt5Widgets.so.5 #20 0x7f0e5b547e2c in () at /usr/lib64/libQt5Widgets.so.5 #21 0x7f0e5b548d81 in () at /usr/lib64/libQt5Widgets.so.5 #22 0x7f0e5b54d9bf in QWidgetTextControl::processEvent(QEvent*, QMatrix const&, QWidget*) () at /usr/lib64/libQt5Widgets.so.5 #23 0x7f0e5b544b5b in QWidgetTextControl::processEvent(QEvent*, QPointF const&, QWidget*) () at /usr/lib64/libQt5Widgets.so.5 #24 0x7f0e5b4c09f8 in () at /usr/lib64/libQt5Widgets.so.5 #25 0x7f0e5b3c23a1 in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #26 0x7f0e5b4bc43e in QFrame::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #27 0x7f0e5b381e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #28 0x7f0e5b3872cb in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #29 0x7f0e5a20ae95 in QCo
[krita] [Bug 366770] New: Can't see my marks on the canvas until I click outside of the canvas.
https://bugs.kde.org/show_bug.cgi?id=366770 Bug ID: 366770 Summary: Can't see my marks on the canvas until I click outside of the canvas. Product: krita Version: 3.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: aeare...@gmail.com I'll make a mark on the canvas with my tablet or my mouse and I can't see it. The canvas is still blank. However, if I click somewhere outside of the canvas, my mark appears on the screen. I want to be able to see my marks as I make them. Reproducible: Always Steps to Reproduce: 1. Open a new canvas. 2. Make a mark. 3. Click somewhere outside of the canvas to see the mark that I made. Expected Results: I should be able to see what I'm drawing as I'm drawing it. I shouldn't have to click elsewhere after every mark that I make. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 364381] sftp/kio_sftp.cpp:1249]: (style) Suspicious condition
https://bugs.kde.org/show_bug.cgi?id=364381 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Christoph Feck --- Already reported as bug 366763. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 366763] kio-extras-16.07.80/sftp/kio_sftp.cpp:1249]: (style) Suspicious condition
https://bugs.kde.org/show_bug.cgi?id=366763 Christoph Feck changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kio- ||extras/c7049eb74086986d7b59 ||dedefc7036ce9cc7440b Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Git commit c7049eb74086986d7b59dedefc7036ce9cc7440b by Christoph Feck, on behalf of David Binderman. Committed on 15/08/2016 at 01:50. Pushed by cfeck into branch 'master'. Fix suspicious condition (assignment + comparison) Reviewed by Christoph Feck M +1-1sftp/kio_sftp.cpp http://commits.kde.org/kio-extras/c7049eb74086986d7b59dedefc7036ce9cc7440b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 345245] Digikam hangs on startup
https://bugs.kde.org/show_bug.cgi?id=345245 --- Comment #16 from Ingo Dettmar --- I don't think this is very similar: in my case the application just hangs, it does not crash or produce any error messages. Also the debug log doesn't show any errors. I have googled and came up empty-handed, really. That's why I chose to reply to this post. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346519] System Settings Crashed
https://bugs.kde.org/show_bug.cgi?id=346519 Christoph Feck changed: What|Removed |Added CC|b...@belpolaris.com | -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 365083] sundtek - missing initialization for dvb device + patch
https://bugs.kde.org/show_bug.cgi?id=365083 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 361189] log-viewer triggers dialog "KDEInit could not launch '/usr/bin/ktp-log-viewer'" after closing
https://bugs.kde.org/show_bug.cgi?id=361189 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 355540] Tooltips color wrong in gtk applications
https://bugs.kde.org/show_bug.cgi?id=355540 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366769] Rename aborts after first rename of many
https://bugs.kde.org/show_bug.cgi?id=366769 --- Comment #1 from Geoff King --- I just tried it with some MOV files and some of those changed the name two at a time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop
https://bugs.kde.org/show_bug.cgi?id=350826 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366769] New: Rename aborts after first rename of many
https://bugs.kde.org/show_bug.cgi?id=366769 Bug ID: 366769 Summary: Rename aborts after first rename of many Product: digikam Version: 5.1.0 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: AdvancedRename Assignee: digikam-de...@kde.org Reporter: gski...@gmail.com Renaming video files fails after the first of many files to be renamed. This affects my MP4 video files. It does not affect jpg files. This appears similar to bug 357617 Reproducible: Always Steps to Reproduce: 1. Select several video files (in my case MP4 from GoPro) 2. F2 to start rename dialog. 3. Change the name and start the rename. Actual Results: The first file is renamed, but the others are not. a Renaming Images dialog box comes up and says Please wait... Processing. The only option is to Abort. Expected Results: All the files would be renamed. Instead 1 of 10 files were renamed. This appears similar to bug 357617 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366768] Reply quote header uses UTC timestamp instead of local time zone
https://bugs.kde.org/show_bug.cgi?id=366768 --- Comment #1 from Nick --- This is on Ubuntu 16.04 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time
https://bugs.kde.org/show_bug.cgi?id=361764 Alan Liddell changed: What|Removed |Added CC||alan.c.lidd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366768] New: Reply quote header uses UTC timestamp instead of local time zone
https://bugs.kde.org/show_bug.cgi?id=366768 Bug ID: 366768 Summary: Reply quote header uses UTC timestamp instead of local time zone Product: kmail2 Version: 5.1.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: futurepi...@gmx.us When I reply to an email with a quote the header of the quote uses a UTC timestamp instead of the local time zone. In addition even though the quote timestamp says it's the local time zone it is clearly incorrect. For example, I received an email that was sent at 8:39 AM EDT (-0400). If I reply with a quote the message says "On Sunday, August 14, 2016 12:39:05 PM EDT Foo wrote:" This would be the time in UTC even though it says EDT. It is +4 hours ahead of Eastern Time. Reproducible: Always Steps to Reproduce: 1. Open an email 2. Reply with quote 3. Compare timestamps on the actual email to the timestamp used in the quote Actual Results: Timestamp in quote is actually in UTC despite saying the local time zone (EDT in my case) Expected Results: Timestamp used in quote should actually be the local time zone time. > timedatectl Local time: Sun 2016-08-14 18:06:51 EDT Universal time: Sun 2016-08-14 22:06:51 UTC RTC time: Sun 2016-08-14 22:06:52 Time zone: America/New_York (EDT, -0400) Network time on: yes NTP synchronized: yes RTC in local TZ: no -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 225747] kopete does not encode utf xml properly when sending to jabber (xmpp) server
https://bugs.kde.org/show_bug.cgi?id=225747 --- Comment #7 from Pali Rohár --- This is bug in QtXml... My workaround for libiris: https://github.com/psi-im/iris/pull/44 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 225747] kopete does not encode utf xml properly when sending to jabber (xmpp) server
https://bugs.kde.org/show_bug.cgi?id=225747 Pali Rohár changed: What|Removed |Added CC||char...@kde.org --- Comment #6 from Pali Rohár --- *** Bug 314272 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 314272] Kopete disconnects from Jabber when sending text outside of BOM
https://bugs.kde.org/show_bug.cgi?id=314272 Pali Rohár changed: What|Removed |Added Resolution|UPSTREAM|DUPLICATE --- Comment #10 from Pali Rohár --- For sure this is same bug as #225747... I can reproduce it. *** This bug has been marked as a duplicate of bug 225747 *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 279269] Kopete history plugin escapes quote and ampersand characters
https://bugs.kde.org/show_bug.cgi?id=279269 Pali Rohár changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||pali.ro...@gmail.com --- Comment #4 from Pali Rohár --- *** This bug has been marked as a duplicate of bug 269097 *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 269097] [PATCH] Some html entities are not correctly displayed in history
https://bugs.kde.org/show_bug.cgi?id=269097 Pali Rohár changed: What|Removed |Added CC||m...@sevik.ru --- Comment #4 from Pali Rohár --- *** Bug 279269 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366767] UNABLE TO CONTACT TIME SERVER every time I try to set the right time
https://bugs.kde.org/show_bug.cgi?id=366767 --- Comment #1 from k.w.sch...@dunelm.org.uk --- fuck off page, leave me alone now! just close the report and fuck off!! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366767] New: UNABLE TO CONTACT TIME SERVER every time I try to set the right time
https://bugs.kde.org/show_bug.cgi?id=366767 Bug ID: 366767 Summary: UNABLE TO CONTACT TIME SERVER every time I try to set the right time Product: systemsettings Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_clock Assignee: p...@taniwha.com Reporter: k.w.sch...@dunelm.org.uk CC: plasma-b...@kde.org I really can't explain much, I'm not expert with computers. All I can describe is the caption that I receive saying: UNABLE TO CONTACT TIME SERVER every time I try to set the right time Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 359536] systemsettings crashes when trying to set automatic date/time change
https://bugs.kde.org/show_bug.cgi?id=359536 --- Comment #2 from k.w.sch...@dunelm.org.uk --- I really can't explain much, I'm not expert with computers. All I can describe is the caption that I receive saying: UNABLE TO CONTACT TIME SERVER every time I try to set the right time -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 359536] systemsettings crashes when trying to set automatic date/time change
https://bugs.kde.org/show_bug.cgi?id=359536 k.w.sch...@dunelm.org.uk changed: What|Removed |Added CC||k.w.sch...@dunelm.org.uk -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366568] when dragging & dropping folders, contained files are opened as blank / new.
https://bugs.kde.org/show_bug.cgi?id=366568 xaxa...@gmail.com changed: What|Removed |Added Keywords||regression, reproducible, ||usability -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366766] Dragging and dropping the same file multiple times creates duplicate entries.
https://bugs.kde.org/show_bug.cgi?id=366766 xaxa...@gmail.com changed: What|Removed |Added Keywords||reproducible, usability -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366766] Dragging and dropping the same file multiple times creates duplicate entries.
https://bugs.kde.org/show_bug.cgi?id=366766 xaxa...@gmail.com changed: What|Removed |Added CC||xaxa...@gmail.com Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366766] New: Dragging and dropping the same file multiple times creates duplicate entries.
https://bugs.kde.org/show_bug.cgi?id=366766 Bug ID: 366766 Summary: Dragging and dropping the same file multiple times creates duplicate entries. Product: kate Version: 16.04 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: xaxa...@gmail.com Every time I drag and drop a file it creates a new entry, even if it already exists. I'm using tree-view. When one entry is edited, the others are considered dirty and need reloading. This could potentially cause data loss as if you don't notice you've opened the same file twice then go to save everything you could lose all your updates if the unmodified version is saved last. Reproducible: Always Steps to Reproduce: 1. Select any text file in a file browser (I used dolphin). 2. Open Kate (I have documents panel set to tree-view, not sure if it matters). 3. Drag text file onto Kate multiple times. Actual Results: Multiple independently-editable entries shown in documents panel. Expected Results: Dropping an already open file into Kate should be ignored. System: Linux Mint XFCE 18 KDE apps installed from default Ubuntu 16.04 repository. NOTE: This is a regression from a previous Kate version (Ubuntu 14.04's version worked). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366765] New: Exporting a PSD file onto a network drive causes application hang
https://bugs.kde.org/show_bug.cgi?id=366765 Bug ID: 366765 Summary: Exporting a PSD file onto a network drive causes application hang Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: wontoon...@gmail.com When you export an *.PSD file to a drive on a network, Krita will hang. Reproducible: Always Steps to Reproduce: 1. Create image. Any image. Paint, draw, whatever. 2. Export the PSD file via "Export..." 3. Recoil in horror as Krita no longer responds, giving you the infinite circle of doom. Actual Results: Krita becomes unresponsive, have to terminate the program. PSD file is nor exported, and creates a corrupted PSD file. This also can be reproduced in 2.9. Expected Results: An exported PSD file, ready to go. This is done on a Windows 10 machine (surface 4 pro) with a mapped network folder. A workaround is to export the PSD file onto a local drive and copy that file to the network drive; the PSD export works completely fine when exporting to the local drive. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 366594] can't use ignore-modules in option stanza from config file
https://bugs.kde.org/show_bug.cgi?id=366594 --- Comment #1 from Michael Pyne --- Created attachment 100600 --> https://bugs.kde.org/attachment.cgi?id=100600&action=edit Allows 'options' blocks to apply to named module-sets Please try this patch and see if it works for you. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 359995] Wish to add a command option
https://bugs.kde.org/show_bug.cgi?id=359995 Damian Kaczmarek changed: What|Removed |Added CC||rus...@gmail.com --- Comment #3 from Damian Kaczmarek --- @Boudhayan Gupta so have you had a deluge of bugreports saying that this option does not work from GUI? If so then the number of people using it from command line is gonna be certainly lower. If not, then what makes you think as you stated? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 359995] Wish to add a command option
https://bugs.kde.org/show_bug.cgi?id=359995 Damian Nowak changed: What|Removed |Added CC||nowa...@geozone.pl --- Comment #2 from Damian Nowak --- Workaround: xclip -sel clipboard -i -t image/png < image.png @Boudhayan, here's what you can do to avoid a deluge of bug reports while still keeping the feature: 1. Copy image to clipboard. 2. Immediately after that's done check the contents of the clipboard to validate it's been copied. 3. If not, exit with non-zero status, and print a message "Could not send image to clipboard. This feature doesn't reliably work and there's no way to ensure it. Please do not raise any bug reports. Screenshot was saved to /path/image.png instead." -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366764] New: Unsupported Full Screen Mode (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=366764 Bug ID: 366764 Summary: Unsupported Full Screen Mode (on Wayland) Product: kwin Version: git master Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthias.fauconn...@gmail.com Full screen mode (e.g. in Gwenview) does not work. I am not sure whether Gwenview fails to request, or KWin fails to reconfigure. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 366763] New: kio-extras-16.07.80/sftp/kio_sftp.cpp:1249]: (style) Suspicious condition
https://bugs.kde.org/show_bug.cgi?id=366763
Bug ID: 366763
Summary: kio-extras-16.07.80/sftp/kio_sftp.cpp:1249]: (style)
Suspicious condition
Product: kio-extras
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: default
Assignee: plasma-de...@kde.org
Reporter: dcb...@hotmail.com
kio-extras-16.07.80/sftp/kio_sftp.cpp:1249]: (style) Suspicious condition
(assignment + comparison); Clarify expression with parentheses.
Source code is
} else if ((errorCode = writeToFile(fd, filedata.constData(),
filedata.size()) != 0)) {
Suggest new code
} else if ((errorCode = writeToFile(fd, filedata.constData(),
filedata.size())) != 0) {
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint
https://bugs.kde.org/show_bug.cgi?id=353960 justin gardiner changed: What|Removed |Added CC||justin.m.gardi...@gmail.com --- Comment #11 from justin gardiner --- I just hit this issue after trying linux again after a few years away. It is not good that after my first boot I was asked to enter my wifi password and then was presented with this. As I am a developer I knew what the message meant but most people wouldn't. This needs to be improved. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 366762] New: Konqueror kf5 master sidebar is empty
https://bugs.kde.org/show_bug.cgi?id=366762
Bug ID: 366762
Summary: Konqueror kf5 master sidebar is empty
Product: konqueror
Version: Git
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: sidebar
Assignee: fa...@kde.org
Reporter: lu...@hube-lueck.de
in konsole I see:
konqueror(21841)/konqueror ModuleManager::modules: No global directory found
for apps/konqsidebartng/entries. Installation problem!
konqueror/sidebar/CMakeLists.txt has:
# TODO: rewrite to KDirModel
if (${QT_QT3SUPPORT_FOUND})
add_subdirectory( trees )
endif()
No QT_QT3SUPPORT in kf5 -> subdirectory is not build
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 366755] Crash when opening activity
https://bugs.kde.org/show_bug.cgi?id=366755 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com Component|General |Engine Version|unspecified |5.21.0 Product|Baloo |frameworks-baloo -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364035] GPS correlation fails to save coordinates back to files
https://bugs.kde.org/show_bug.cgi?id=364035 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 366750] Frameworks 5.25.0 is displayed as 5.25.0.0 -> link not found
https://bugs.kde.org/show_bug.cgi?id=366750 Burkhard Lueck changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Burkhard Lueck --- SVN commit 1467064 by lueck: fix wrong link to Frameworks 5,25.0 M +1 -1 index.php WebSVN link: http://websvn.kde.org/?view=rev&revision=1467064 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366761] New: Crash when selecting the Plastik window decoration
https://bugs.kde.org/show_bug.cgi?id=366761 Bug ID: 366761 Summary: Crash when selecting the Plastik window decoration Product: kwin Version: 5.6.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: spalmr...@gmail.com Application: kwin_x11 (5.6.5) (Compiled from sources) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.4.6-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: In system settings -> Window Decorations, I switched to the Plastik window theme and clicked "Apply". KWin crashed but then started up again with the Plastik theme. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f74b26c1800 (LWP 10696))] Thread 6 (Thread 0x7f749e002700 (LWP 10699)): #0 0x7f74b1f855fd in poll () from /lib64/libc.so.6 #1 0x7f74b036ab12 in poll (__timeout=-1, __nfds=1, __fds=0x7f749e001cc0) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x1702d30, cond=cond@entry=0x1702d70, vector=vector@entry=0x0, count=count@entry=0x0) at /usr/src/debug/x11-libs/libxcb-1.11.1/libxcb-1.11.1/src/xcb_conn.c:459 #3 0x7f74b036c8ef in xcb_wait_for_event (c=0x1702d30) at /usr/src/debug/x11-libs/libxcb-1.11.1/libxcb-1.11.1/src/xcb_in.c:693 #4 0x7f749eaaf029 in QXcbEventReader::run() () from /usr/lib64/libQt5XcbQpa.so.5 #5 0x7f74b062b95c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #6 0x7f74b2249494 in start_thread () from /lib64/libpthread.so.0 #7 0x7f74b1f8e5dd in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f74973eb700 (LWP 10701)): #0 0x7f74b1f872f3 in select () from /lib64/libc.so.6 #1 0x7f74b08163b1 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib64/libQt5Core.so.5 #2 0x7f74b0817a9e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib64/libQt5Core.so.5 #3 0x7f74b0817fdd in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f74b07cc5ba in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f74b0627204 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f74b27d3235 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #7 0x7f74b062b95c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7f74b2249494 in start_thread () from /lib64/libpthread.so.0 #9 0x7f74b1f8e5dd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f748710f700 (LWP 10705)): #0 0x7f74b0817be6 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib64/libQt5Core.so.5 #1 0x7f74b0817fdd in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #2 0x7f74b07cc5ba in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #3 0x7f74b0627204 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #4 0x7f74aac8fa25 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #5 0x7f74b062b95c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #6 0x7f74b2249494 in start_thread () from /lib64/libpthread.so.0 #7 0x7f74b1f8e5dd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f7486086700 (LWP 10706)): #0 0x7f74b224f0bf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f74af7c0264 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQt5Script.so.5 #2 0x7f74af7c02a9 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQt5Script.so.5 #3 0x7f74b2249494 in start_thread () from /lib64/libpthread.so.0 #4 0x7f74b1f8e5dd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f7494ca1700 (LWP 10736)): #0 0x7f74b1f872f3 in select () from /lib64/libc.so.6 #1 0x7f74b08163b1 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib64/libQt5Core.so.5 #2 0x7f74b0817a9e in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib64/libQt5Core.so.5 #3 0x7f74b0817fdd in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f74b07cc5ba in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f74b0627204 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f74aac8fa25 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #7 0x7f74b062b95c in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #8 0x7f74b2249494 in start_thread () from /lib64/libpthread.so.0 #9 0x7f74b
[gwenview] [Bug 366760] New: Gwenview crashes when trying to save jpg image after rotating.
https://bugs.kde.org/show_bug.cgi?id=366760 Bug ID: 366760 Summary: Gwenview crashes when trying to save jpg image after rotating. Product: gwenview Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: cleit...@sfu.ca CC: myr...@kde.org Application: gwenview (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-34-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Saving a jpg image after rotating. Happens every time with the same image. Just open it, rotate it, click save in the drop-down bar, then crashes. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f82407789c0 (LWP 14290))] Thread 3 (Thread 0x7f8234058700 (LWP 14292)): [KCrash Handler] #6 0x7f824f002418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f824f00401a in __GI_abort () at abort.c:89 #8 0x7f824f42584d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f824f4236b6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f824f423701 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f824f423969 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7f824f7ba5c6 in QThreadPoolThread::run (this=0x1e5b840) at thread/qthreadpool.cpp:100 #13 0x7f824f7bd84e in QThreadPrivate::start (arg=0x1e5b840) at thread/qthread_unix.cpp:331 #14 0x7f824a5cf6fa in start_thread (arg=0x7f8234058700) at pthread_create.c:333 #15 0x7f824f0d3b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f823e6a0700 (LWP 14291)): #0 0x7f824f0c7e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8247fbcc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f8247fbe8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f82403cb629 in QXcbEventReader::run (this=0x18c5aa0) at qxcbconnection.cpp:1253 #4 0x7f824f7bd84e in QThreadPrivate::start (arg=0x18c5aa0) at thread/qthread_unix.cpp:331 #5 0x7f824a5cf6fa in start_thread (arg=0x7f823e6a0700) at pthread_create.c:333 #6 0x7f824f0d3b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f82407789c0 (LWP 14290)): #0 0x7f824f0c3a2d in write () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f824a0f17e2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f824a0aa870 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f824a0ae1e0 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f824a0ae400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f824a0ae4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f824f9f4a7f in QEventDispatcherGlib::processEvents (this=0x18a3850, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #7 0x7f824f99bdea in QEventLoop::exec (this=this@entry=0x7ffef32eb140, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7f824f9a3e8c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #9 0x0044ba70 in main () Possible duplicates by query: bug 365143, bug 354273, bug 352280. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356893] Crash when creating file from context menu
https://bugs.kde.org/show_bug.cgi?id=356893 DimitrieStr changed: What|Removed |Added CC||stratiladimitrie@rocketmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356893] Crash when creating file from context menu
https://bugs.kde.org/show_bug.cgi?id=356893 --- Comment #5 from DimitrieStr --- Created attachment 100599 --> https://bugs.kde.org/attachment.cgi?id=100599&action=edit New crash information added by DrKonqi dolphin (15.12.3) using Qt 5.5.1 - What I was doing when the application crashed: Opened the containing folder of a .deb package from Firefox 48.0 download list button -- Backtrace (Reduced): #6 QVector::isEmpty (this=) at ../../include/QtCore/../../src/corelib/tools/qvector.h:84 #7 QThreadStorageData::finish (p=p@entry=0xf8) at thread/qthreadstorage.cpp:169 #8 0x7fe446b689f5 in QThreadPrivate::finish (arg=arg@entry=0x160c210) at thread/qthread_unix.cpp:351 #9 0x7fe446b6986f in __pthread_cleanup_class::~__pthread_cleanup_class (this=, __in_chrg=) at /usr/include/pthread.h:561 #10 QThreadPrivate::start (arg=0x160c210) at thread/qthread_unix.cpp:290 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 eemantsal changed: What|Removed |Added Platform|Other |Gentoo Packages --- Comment #14 from eemantsal --- I only have dhclient installed for DHCP. Aren't NM and iwconfig using it equally? What you asked: $ ping -c 1 Juan-PC PING Juan-PC (127.0.0.1) 56(84) bytes of data. 64 bytes from Juan-PC (127.0.0.1): icmp_seq=1 ttl=64 time=0.053 ms --- Juan-PC ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.053/0.053/0.053/0.000 ms I'm on Gentoo. It doesn't use Systemd by default, but OpenRC. To see system logs I have Metalog, that I'm aware of, don't know if I could have anyone else installed as dependency of something. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 364141] Kmix crashes when trying to change the volume for individual streams with scrollwheel from systray
https://bugs.kde.org/show_bug.cgi?id=364141 whatifgodwasoneo...@hotmail.com changed: What|Removed |Added CC||whatifgodwasoneofus@hotmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 366759] New: Knotify crash
https://bugs.kde.org/show_bug.cgi?id=366759 Bug ID: 366759 Summary: Knotify crash Product: kdelibs Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: knotify Assignee: ogoff...@kde.org Reporter: j.stien...@gmail.com Application: knotify4 (4.14.21) KDE Platform Version: 4.14.22 Qt Version: 4.8.7 Operating System: Linux 4.6.5-300.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: with every kde application: each time a notification should appear, knotify segfaults. Totally reproductible, does it every time. Running Fedora 24. The crash can be reproduced every time. -- Backtrace: Application: KNotify (knotify4), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdf3a748940 (LWP 3170))] Thread 2 (Thread 0x7fdf17333700 (LWP 3171)): #0 0x7fdf37918afd in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7fdf37912a76 in pthread_mutex_lock () at /lib64/libpthread.so.0 #2 0x7fdf3a6406fa in tls_get_addr_tail () at /lib64/ld-linux-x86-64.so.2 #3 0x7fdf37610380 in __cxa_get_globals () at /lib64/libstdc++.so.6 #4 0x7fdf37610249 in std::uncaught_exception() () at /lib64/libstdc++.so.6 #5 0x7fdf37ba2929 in qt_message(QtMsgType, char const*, __va_list_tag*) () at /lib64/libQtCore.so.4 #6 0x7fdf37ba2c21 in qWarning(char const*, ...) () at /lib64/libQtCore.so.4 #7 0x7fdf37cecc94 in socketNotifierSourceCheck(_GSource*) () at /lib64/libQtCore.so.4 #8 0x7fdf33b08471 in g_main_context_check () at /lib64/libglib-2.0.so.0 #9 0x7fdf33b089e4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #10 0x7fdf33b08b5c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #11 0x7fdf37ced47e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #12 0x7fdf37cbb7bf in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #13 0x7fdf37cbbb25 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #14 0x7fdf37baaaf9 in QThread::exec() () at /lib64/libQtCore.so.4 #15 0x7fdf37c9b613 in QInotifyFileSystemWatcherEngine::run() () at /lib64/libQtCore.so.4 #16 0x7fdf37bad3ca in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4 #17 0x7fdf379105ca in start_thread () at /lib64/libpthread.so.0 #18 0x7fdf36da1ead in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fdf3a748940 (LWP 3170)): [KCrash Handler] #6 0x7fdf0ab92377 in QMetaObject::className() const () at /lib64/libQt5Core.so.5 #7 0x7fdf0b47a9df in QMetaTypeIdQObject::qt_metatype_id() () at /lib64/libQt5Widgets.so.5 #8 0x7fdf0b413167 in _GLOBAL__sub_I_qwidgetsvariant.cpp () at /lib64/libQt5Widgets.so.5 #9 0x7fdf3a63ddaa in call_init.part () at /lib64/ld-linux-x86-64.so.2 #10 0x7fdf3a63debb in _dl_init () at /lib64/ld-linux-x86-64.so.2 #11 0x7fdf3a642ab1 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #12 0x7fdf3a63dc54 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #13 0x7fdf3a642009 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #14 0x7fdf31c68f09 in dlopen_doit () at /lib64/libdl.so.2 #15 0x7fdf3a63dc54 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #16 0x7fdf31c69591 in _dlerror_run () at /lib64/libdl.so.2 #17 0x7fdf31c68fa2 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2 #18 0x7fdf155aae00 in module_Load () at /lib64/libvlccore.so.8 #19 0x7fdf1559636b in module_InitDynamic () at /lib64/libvlccore.so.8 #20 0x7fdf155966ca in AllocatePluginDir () at /lib64/libvlccore.so.8 #21 0x7fdf15596629 in AllocatePluginDir () at /lib64/libvlccore.so.8 #22 0x7fdf15596a3a in AllocatePluginPath () at /lib64/libvlccore.so.8 #23 0x7fdf15596f4a in module_LoadPlugins () at /lib64/libvlccore.so.8 #24 0x7fdf15535ca2 in libvlc_InternalInit () at /lib64/libvlccore.so.8 #25 0x7fdf153081da in libvlc_new () at /lib64/libvlc.so.5 #26 0x7fdf1584130d in LibVLC::init() () at /usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so #27 0x7fdf15823b56 in Phonon::VLC::Backend::Backend(QObject*, QList const&) () at /usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so #28 0x7fdf158247d3 in qt_plugin_instance () at /usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so #29 0x7fdf37c9fc93 in QPluginLoader::instance() () at /lib64/libQtCore.so.4 #30 0x7fdf16928011 in Phonon::KdePlatformPlugin::createBackend(KSharedPtr) () at /usr/lib64/kde4/plugins/phonon_platform/kde.so #31 0x7fdf169287ab in Phonon::KdePlatformPlugin::createBackend() () at /usr/lib64/kde4/plugins/phonon_platform/kde.so #32 0x7fdf3a3e9a6c in Phonon::FactoryPrivate::createBackend() () at /lib64/libphonon.so.4 #33 0x7fdf3a3ea218 i
[krita] [Bug 366758] New: Krita flips the image horizontally when opening a file if the mirror mode is active
https://bugs.kde.org/show_bug.cgi?id=366758 Bug ID: 366758 Summary: Krita flips the image horizontally when opening a file if the mirror mode is active Product: krita Version: 3.0 Platform: MS Windows URL: https://drive.google.com/file/d/0B5OSF4ESCy5gUEY4bW94U mhETDg/view?usp=sharing OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: comm@gmail.com When opening a file, if the mirror mode is active, the image shows flipped horizontally. In the URL of this issue I've put a link to a zip file containing images of the problem. The workaround is to deactivate the mirror mode and then opening the file. Reproducible: Always Steps to Reproduce: 1. Open a file (file 1.png of the zip file) 2. Activate the horizontal mirror mode (file 2.png of the zip file) 3. Close the image (file 3.png of the zip file) 4. Open the file again (file 4.png of the zip file) Actual Results: The image is flipped horizontally Expected Results: The image shouldn't be flipped The workaround is to deactivate the mirror mode before closing the image. Another minor bug is that although the horizontal mirror line is shown, the icon isn't active. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #13 from Lamarque V. Souza --- Since you do not have the host command installed, the output of the second command is useless. Can you ping your hostname? Like this: $ ping -c 1 Juan-PC NetworkManager does not directly change computer's hostname. The dhcp client does. Let's first try to understand what is causing your problem before messing with xauth and DISPLAY. What is you Linux distribution? I need you to send me NetworkManager's log and the way to retrieve it depends on which distribution you use. If you use one that uses journald you can retrieve it running the following command as root: journalctl -u NetworkManager.service -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 353463] RFE: Make use of iio-sensor-proxy
https://bugs.kde.org/show_bug.cgi?id=353463 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346519] System Settings Crashed
https://bugs.kde.org/show_bug.cgi?id=346519 --- Comment #61 from Bel Lord-Williams --- unsubscribe On Sun, Aug 14, 2016 at 5:13 AM Christoph Feck via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346519 > > Christoph Feck changed: > >What|Removed |Added > > > CC||dajo...@gmail.com > > --- Comment #60 from Christoph Feck --- > *** Bug 366613 has been marked as a duplicate of this bug. *** > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #12 from eemantsal --- I set the machine's name when I installed the OS, and, to be sincere, I had no idea at all one could nor should use localhost -you mean «localhost» as the computer's name, right?- in xauth's cookies and DISPLAY, amont other things because I have no clue about how to set the name in xauth's cookies, nor in DISPLAY. :/ Here is what you asked: $ hostname -f Juan-PC $ host $(hostname -f) bash: host: no se encontró la orden (command not found) $ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1 link/sit 0.0.0.0 brd 0.0.0.0 3: wlp12s0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 0e:9b:57:62:68:cc brd ff:ff:ff:ff:ff:ff inet 192.168.1.37/24 brd 192.168.1.255 scope global dynamic wlp12s0 valid_lft 259197sec preferred_lft 259197sec inet6 fe80::c9b:57ff:fe62:68cc/64 scope link valid_lft forever preferred_lft forever 4: eth0: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 00:1c:23:ae:83:50 brd ff:ff:ff:ff:ff:ff $ ip route default via 192.168.1.1 dev wlp12s0 proto static metric 600 127.0.0.0/8 dev lo scope host 192.168.1.0/24 dev wlp12s0 proto kernel scope link src 192.168.1.37 metric 600 Recreating the connection does behave the same, yes. I have stopped Networkmanager and connected with iwconfig from Konsole, and I have seen the name doesn't change (I think I had never paid attention to this detail). Seems that is NM the one that changes the PC name. Why iwconfig doesn't need to change it but NM does. Do you think there's a justified motive for it or is it a bug? Anyway you still advice me to set my PC name as «localhost» in xauth's cookies and DISPLAY? If yes, would you be so kind to tell me how or pointing me to some page where it's explained? Many thanks for your time, Larmarque. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366757] New: hey... Default builtin FX brushes dont show up in the app...
https://bugs.kde.org/show_bug.cgi?id=366757 Bug ID: 366757 Summary: hey... Default builtin FX brushes dont show up in the app... Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: wiebe...@gmail.com The brushes on the right click menu disappeared in 3.0 Reproducible: Always Steps to Reproduce: 1.boot app 2.open or create image 3.right-click. No fx or other extra brushes show up Showed all kinds of extra brush sets -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364171] One of the best brushsets for Krita is broken again (in final version of Krita v3.0)
https://bugs.kde.org/show_bug.cgi?id=364171 north w changed: What|Removed |Added CC||wiebe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 Lamarque V. Souza changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #11 from Lamarque V. Souza --- By what I can see in the logs, somehow the WEP connection is changing your computer's hostname and that is probably breaking Xorg. Your computer should be named Juan-PC (name used in xauth's cookie) but strace shows it is dhcppc4 for the WEP connection. One should always use localhost in xauth's cookies and DISPLAY to prevent that (and for performance reasons too) unless you really need Xorg's network transparency feature. What is the output of the commands below in both working and non-working setup: $ hostname -f $ host $(hostname -f) $ ip addr $ ip route If you create a new connection to the same WEP access point does the problem still happen? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #10 from eemantsal --- Created attachment 100597 --> https://bugs.kde.org/attachment.cgi?id=100597&action=edit log.txt (WPA network) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #9 from eemantsal --- Ok. «xauth list» returns: PC_name/unix:0 MIT-MAGIC-COOKIE-1 a2a8264bf3e364f4894097ee0cdc9a17 $ strace -f -o log.txt kate says: QObject::connect: invalid null parameter QObject::connect: invalid null parameter QObject::connect: Cannot connect (null)::returnPressed() to KUrlRequester::returnPressed() QObject::connect: Cannot connect (null)::returnPressed(QString) to KUrlRequester::returnPressed(QString) XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 XmbTextListToTextProperty result code -2 and Kate opens itself correctly. The log is attached below -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 312828] simple locker should allow for custom background
https://bugs.kde.org/show_bug.cgi?id=312828 Jonah changed: What|Removed |Added CC||jonah.bellem...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #8 from Lamarque V. Souza --- Please repeat the the command when no problem happen (when using wpa for instance): $ xauth list $ strace -f -o log.txt kate -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #7 from eemantsal --- Created attachment 100596 --> https://bugs.kde.org/attachment.cgi?id=100596&action=edit log.txt -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #6 from eemantsal --- Ignorant me... Despite the abortion of the action there's a log.txt file, yes. Here I attach it -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366756] Saving new projects do not default to extension *.kra but to *.exr
https://bugs.kde.org/show_bug.cgi?id=366756 Sven Langkamp changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||sven.langk...@gmail.com --- Comment #1 from Sven Langkamp --- *** This bug has been marked as a duplicate of bug 366102 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366102] Krita default file format now not .kra but openEXR format?
https://bugs.kde.org/show_bug.cgi?id=366102 Sven Langkamp changed: What|Removed |Added CC||ktr44...@zasod.com --- Comment #2 from Sven Langkamp --- *** Bug 366756 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #5 from eemantsal --- That I supposed. Well, the problem is that inmediately anter executing $ strace -f -o log.txt whatever I always get: No protocol specified QXcbConnection: Could not connect to display :0 Abortado Seems that no action is peforrmed, only that error message. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 366751] cannot click any items other than file/view and torrent/plugins rows after few hours
https://bugs.kde.org/show_bug.cgi?id=366751 --- Comment #2 from arun --- I submitted the report only once but I don't know how it got submitted twice -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 366598] Make Spectacle able to take screencasts
https://bugs.kde.org/show_bug.cgi?id=366598 Alex Oleshkevich changed: What|Removed |Added CC||alex.oleshkev...@gmail.com --- Comment #1 from Alex Oleshkevich --- +1 -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 366749] GTK+ applications complain about missing size field in oxygen
https://bugs.kde.org/show_bug.cgi?id=366749 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu --- Comment #1 from Rex Dieter --- Perhaps, but it's odd that the directory *name* here is apparently blank. ... **: Theme directory * * of theme oxygen ... -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #4 from Lamarque V. Souza --- kcalc was just example. I need the log.txt file that strace command created. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 365981] NM Connection Editor crashes on OpenVPN connection creation or modification
https://bugs.kde.org/show_bug.cgi?id=365981 --- Comment #2 from Gerard Dirkse --- Backtrace for creating a new profiles looks like this: Application: Connection editor (kde-nm-connection-editor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7fc855cf43d9 in SettingWidget::SettingWidget(QSharedPointer const&, QWidget*, QFlags) () at /usr/lib64/libplasmanetworkmanagement-editor.so #6 0x7fc855cd847a in IPv6Widget::IPv6Widget(QSharedPointer const&, QWidget*, QFlags) () at /usr/lib64/libplasmanetworkmanagement-editor.so #7 0x7fc855cf8ab9 in ConnectionDetailEditor::initTabs() () at /usr/lib64/libplasmanetworkmanagement-editor.so #8 0x7fc855cfaad2 in ConnectionDetailEditor::initEditor() () at /usr/lib64/libplasmanetworkmanagement-editor.so #9 0x7fc855cfc914 in ConnectionDetailEditor::ConnectionDetailEditor(NetworkManager::ConnectionSettings::ConnectionType, QWidget*, QString const&, bool, QFlags) () at /usr/lib64/libplasmanetworkmanagement-editor.so #10 0x0040e716 in _start () Looks like it is ipv6 related ? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 365981] NM Connection Editor crashes on OpenVPN connection creation or modification
https://bugs.kde.org/show_bug.cgi?id=365981 Gerard Dirkse changed: What|Removed |Added CC||gerard.dir...@kpnmail.nl -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 366756] New: Saving new projects do not default to extension *.kra but to *.exr
https://bugs.kde.org/show_bug.cgi?id=366756 Bug ID: 366756 Summary: Saving new projects do not default to extension *.kra but to *.exr Product: krita Version: 3.0.1 Alpha Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ktr44...@zasod.com Every time a new project is created and is saved as a new file, the file name does not default to have an extension of *kra. Rather, it defaults to *.exr so whenever Enter is pressed after typing a filename, the project isn't being saved as *.kra but rather as *.exr and the user is prompted to flatten the image. Reproducible: Always Steps to Reproduce: 1. Make a new project. 2. Save it with any filename of choosing without extension (e.g. "asdf") at any valid location of choosing Actual Results: Project is being saved as *.exr Expected Results: Project should be saved as *.kra by default -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #3 from eemantsal --- In case Kcalc were just an example and any other app would serve the same, I've installed Strace and tried: $ strace -f -o log.txt kate With the same results: No protocol specified QXcbConnection: Could not connect to display :0 Abortado «$ xauth list» returned: PC_name/unix:0 MIT-MAGIC-COOKIE-1 a2a8264bf3e364f4894097ee0cdc9a17 -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 366755] New: Crash when opening activity
https://bugs.kde.org/show_bug.cgi?id=366755 Bug ID: 366755 Summary: Crash when opening activity Product: Baloo Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: pinak.ah...@gmail.com Reporter: cirda...@hotmail.com Application: baloo_file (5.21.0) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Just switched to another activity window when it segfaulted -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff969a9a780 (LWP 2593))] Thread 2 (Thread 0x7ff81e54d700 (LWP 2612)): #0 0x7ff96403fd08 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7ff963ffcee0 in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #2 0x7ff963ffdd25 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7ff963ffdf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7ff9681ead8b in QEventDispatcherGlib::processEvents (this=0x7ff8180008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7ff968191d53 in QEventLoop::exec (this=this@entry=0x7ff81e54cd20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x0041531b in Baloo::FileContentIndexer::run (this=0x17621a0) at /usr/src/debug/baloo-5.21.0/src/file/filecontentindexer.cpp:73 #7 0x7ff967fb5382 in QThreadPoolThread::run (this=0x17daf00) at thread/qthreadpool.cpp:93 #8 0x7ff967fb832f in QThreadPrivate::start (arg=0x17daf00) at thread/qthread_unix.cpp:331 #9 0x7ff9665f90a4 in start_thread () from /lib64/libpthread.so.0 #10 0x7ff9675c502d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff969a9a780 (LWP 2593)): [KCrash Handler] #6 0x7ff967570100 in __memcpy_sse2_unaligned () from /lib64/libc.so.6 #7 0x7ff968886535 in memcpy (__len=140725123571072, __src=0xe67fbb55c, __dest=) at /usr/include/bits/string3.h:51 #8 Baloo::IdTreeDB::get (this=this@entry=0x7ffd1f005d80, docId=docId@entry=0) at /usr/src/debug/baloo-5.21.0/src/engine/idtreedb.cpp:90 #9 0x7ff968883dc0 in Baloo::DocumentUrlDB::getId (this=this@entry=0x7ffd1f005df0, docId=0, fileName=...) at /usr/src/debug/baloo-5.21.0/src/engine/documenturldb.cpp:186 #10 0x7ff968895949 in Baloo::Transaction::documentId (this=this@entry=0x7ffd1f005e70, path=...) at /usr/src/debug/baloo-5.21.0/src/engine/transaction.cpp:121 #11 0x0041d453 in Baloo::MetadataMover::removeMetadata (this=this@entry=0x1768490, tr=tr@entry=0x7ffd1f005e70, url=...) at /usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:74 #12 0x0041de02 in Baloo::MetadataMover::moveFileMetadata (this=0x1768490, from=..., to=...) at /usr/src/debug/baloo-5.21.0/src/file/metadatamover.cpp:53 #13 0x7ff9681c373f in call (a=0x7ffd1f005fe0, r=0x7ffd1f006740, this=0x1784640) at ../../src/corelib/kernel/qobject_impl.h:124 #14 QMetaObject::activate (sender=sender@entry=0x177e8d0, signalOffset=, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffd1f005fe0) at kernel/qobject.cpp:3698 #15 0x7ff9681c42e7 in QMetaObject::activate (sender=sender@entry=0x177e8d0, m=m@entry=0x638bc0 , local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffd1f005fe0) at kernel/qobject.cpp:3578 #16 0x0041e75a in KInotify::moved (this=this@entry=0x177e8d0, _t1=..., _t2=...) at /usr/src/debug/baloo-5.21.0/build/src/file/moc_kinotify.cpp:330 #17 0x004228f9 in KInotify::slotEvent (this=, socket=) at /usr/src/debug/baloo-5.21.0/src/file/kinotify.cpp:421 #18 0x7ff9681c373f in call (a=0x7ffd1f0062a0, r=0x177e8d0, this=0x1723940) at ../../src/corelib/kernel/qobject_impl.h:124 #19 QMetaObject::activate (sender=sender@entry=0x17567b0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd1f0062a0) at kernel/qobject.cpp:3698 #20 0x7ff9681c42e7 in QMetaObject::activate (sender=sender@entry=0x17567b0, m=m@entry=0x7ff9685e2780 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd1f0062a0) at kernel/qobject.cpp:3578 #21 0x7ff9682458ee in QSocketNotifier::activated (this=this@entry=0x17567b0, _t1=13) at .moc/moc_qsocketnotifier.cpp:134 #22 0x7ff9681d0a89 in QSocketNotifier::event (this=0x17567b0, e=0x7ffd1f006410) at kernel/qsocketnotifier.cpp:260 #23 0x7ff96819418d in QCoreApplication::notify (this=, receiver=, event=) at kernel/qcoreapplication.cpp:1038 #24 0x7ff968193e95 in QCoreApplication::notifyInternal (this=0x7ffd1f0066b0, receiver=0x17567b0, event=event@entry=0x7ffd1f006410) at kernel/qcoreapplication.cpp:965 #25 0x7ff9681ebca5 in sendEvent (event=0x7ffd1f006410, receiver=) at ../../src/corel
[krita] [Bug 364183] Stabilizer's Finish line option is down
https://bugs.kde.org/show_bug.cgi?id=364183 --- Comment #5 from eliotJ --- Thank you so much, Dmitry :). I will wait for new win dev build. Then I will test fixed Finish line feature. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 366754] New: When trying to create an audio alert for a reminder the file selector isn't seeing .ogg files.
https://bugs.kde.org/show_bug.cgi?id=366754 Bug ID: 366754 Summary: When trying to create an audio alert for a reminder the file selector isn't seeing .ogg files. Product: korganizer Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: korganizer-de...@kde.org Reporter: ninawilson2...@yahoo.co.uk A weekly reminder I had set-up before upgrading from Ubuntu 14 to 16.04 was failing to play the audio file. This was one of the standard alerts from usr/share/sounds which I had copied to another directory. When I tried to re-create the alert the file selector wouldn't see the file. However, I now notice that the file selector can now go to the "Computer" folder rather than being stuck in my home folder. So I went to usr/share/sounds and it doesn't see any of the .ogg files. Reproducible: Always Steps to Reproduce: 1. set up an event 2. Select the reminder tab 3. Select the New option to add a reminder action 4. Select "Play sound file" 5. Go to any folder with .ogg files such as usr/share/sounds Actual Results: It sees folders in the directory but not any .ogg files Expected Results: It should see the list of files and allow them to be selected -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 366668] Plasma network manager "hijacks" the launch of apps when connected to a WEP wifi
https://bugs.kde.org/show_bug.cgi?id=38 --- Comment #2 from eemantsal --- I don't have strace nor kcalc. I understand the purpose of Strace and if necessary I'll install it, but are you sure I need a calculator program I have never used? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365909] OGG format seems to be missing from the render menu
https://bugs.kde.org/show_bug.cgi?id=365909 --- Comment #4 from Aaron Honeycutt --- Yea different product, did not mean to sound rude if I did, just woke up to this comment. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 365909] OGG format seems to be missing from the render menu
https://bugs.kde.org/show_bug.cgi?id=365909 --- Comment #3 from Nina --- Sorry Aaron, it was the only ogg related bug that showed up when I clicked on the bug report list from KOrganiser, I hadn't noticed that it was a different product. I'm sure the two different KDE products having problems with ogg files have no connection whatsoever. I'll make a different report elsewhere for my fault. -- You are receiving this mail because: You are watching all bug changes.
