[kdenlive] [Bug 366516] git master 2016-08-08: Speed effect artificial limit.

[Evert Vorster via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366516

--- Comment #6 from Evert Vorster  ---
If the speed effect had audio support, one should be able to apply it to an
audio clip. 

On my setup audio is automatically split out, and does not resize with the
video when the speed is adjusted. 
Ah, I see it does speed up the audio, but only if it is not split out. I guess
I will have to file a bug on this one

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[Aaron Honeycutt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355540

Aaron Honeycutt  changed:

   What|Removed |Added

 CC||aaronhoneyc...@kubuntu.org

--- Comment #22 from Aaron Honeycutt  ---
I can confirm removing:
~/.config/gtkrc
~/.config/gtkrc-2.0

Fixes it in Kubuntu Yakkety Yak with:
Plasma 5.7.2
Frameworks 5.24.0
Qt 5.6.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 355540] Tooltips color wrong in gtk applications

[Aaron Honeycutt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355540

Aaron Honeycutt  changed:

   What|Removed |Added

  Flags||Usability-

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 366570] New: Kdenlive git master: crash on invoking render widget with MLT 6.3.0(git master)

[lukefromdc via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366570

Bug ID: 366570
   Summary: Kdenlive git master: crash on invoking render widget
with MLT 6.3.0(git master)
   Product: kdenlive
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: directact...@hushmail.com

Immediate crash and segfault on Kdenlive master with MLT master whenever the
render widget is invoked.

Since commit
http://quickgit.kde.org/?p=kdenlive.git=commit=9a9346e21eed58d6d58ee9e10ecb3e88f0c39bc3
(Fix crashes when using MLT 6.2.0) and the later 8a4ebe4 requires to build it,
clicking the "render" button on the toolbar or selecting "render" from the menu
instantly crashes kdenlive with a segfault.  This is with Movit enabled and
using MLT 6.3.0 from git master, MLT builds from  July 5 2016 and August 8 2016
pulls exact same behavior. QT and KF5 are what is in Debian Unstable as of
August 10 2016 and same with what was in Debian Unstable in late July.

I was able to trace the exact offending line in commit 9a9346e to the line
below in mainwindow.cpp :

m_renderWidget->errorMessage(m_compositeAction->currentAction()->data().toInt()
== 1 ? i18n("Rendering using low quality track compositing") : QString());

Reverting that line to the previous

 m_renderWidget->errorMessage(m_compositeAction->currentItem() == 1 ?
i18n("Rendering using low quality track compositing") : QString());

will permit kdenlive to build and run without crashing when the renderwidget is
invoked as of today. Last commit was
http://quickgit.kde.org/?p=kdenlive.git=commit=f8580603474e1765289d29d00e17ca1b3289f215
 


Reproducible: Always

Steps to Reproduce:
1. Build MLT from git master, build kdenlive from git master and install on
Debian Unstable
2. Start kdenlive
3. click the "render" button in the toolbar or invoke "render" from the project
menu

Actual Results:  
Immediate crash and segfault

Expected Results:  
Render widget appearing, displaying the options for rendering out the finished
video.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 281802] KCheckpass doesn't work correctly with samba accounts

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=281802

--- Comment #4 from Martin Gräßlin  ---
> /etc/pam.d/kcheckpass just includes system-auth for all 4 sections. 

This file is not provided by us. Seems mageia adds it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 365083] sundtek - missing initialization for dvb device + patch

[Mauro Carvalho Chehab via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365083

--- Comment #11 from Mauro Carvalho Chehab  ---
The point is that the DVB support on version 2.x is partially done via
libdvbv5. The new version of the library detects itself the DVB devices (and
will allow to not only use local devices, but also remote ones).
The Kaffeine 2.0.1 implementation to support the closed-source userspace driver
is a hack: as it seeks for userspace-created fake nodes under /dev/dvb and
expects that the library would work fine with that. This won't be true anymore
with newer versions of the library, as the library needs to do different things
if the device is local or remote. So, it relies on udev for local devices
In other words, it doesn't use the device's path (/dev/dvb/..), but, instead,
the name announced by the driver via sysfs.
It would still be possible to add support to the userspace driver, if someone
with the hardware has interest on writing such code, but the approach will be
different.
Anyway, my plan is to add support for the new version of the library in a
couple of weeks. So, IMHO, it doesn't make sense to apply a patch that we know
it will be broken real soon now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[k3b] [Bug 366569] New: K3b doesn't allow using network files

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366569

Bug ID: 366569
   Summary: K3b doesn't allow using network files
   Product: k3b
   Version: 2.0.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: enkouy...@gmail.com
CC: mich...@jabster.pl, tr...@kde.org

If one tries to add files to any K3b project, there will be a warning message
stating that "You can only select local files."

Reproducible: Always

Steps to Reproduce:
1. Open K3b
2. Navigate to Project > Add files
3. Select a network folder smb://Network_Driver/Folderx/Fodlerx-a
4. Click Open

Actual Results:  
A warning message states "You can only select local files."

Expected Results:  
K3b proceeds to add the selected file/folder.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-ki18n] [Bug 353880] KActionMenu(const QIcon , const QString , QObject *parent) failed to i18nc

[Leslie Zhai via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353880

Leslie Zhai  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Leslie Zhai  ---
kf5.24.0 fixed

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366067] Impartial kscreen config for setup leads to partially configured desktop on hitting 'Apply'

[Sebastian Kügler via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366067

Sebastian Kügler  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.8.0
 Resolution|--- |FIXED

--- Comment #12 from Sebastian Kügler  ---
Alright. It seems to all boil down to not being able to enable the display.

I've fixed two bugs in kscreen, which lead to this behavior. These should fix
the root cause for your problem. These fixes will be released with Plasma 5.8.

Thanks a lot for the useful bug-report and quick follow-ups!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 361672] Plasma Ignores the KWin Setting of Disabling "Desktop navigation wraps around"

[Michael Butash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361672

Michael Butash  changed:

   What|Removed |Added

 CC||mich...@butash.net

--- Comment #1 from Michael Butash  ---
I am having this same problem, further more I noticed as of 5.7 upgrade to
neon, it causes a kwin crash as well to break compositing.  If I untick
"Desktop navigation wraps around", and cause an infinite loop of the desktops,
kwin does not crash.

Same as above to reproduce, but Mouse scroll causes kwin to crash as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366362] [kcm] initial position of newly connected known output is wrong

[Sebastian Kügler via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366362

Sebastian Kügler  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/kscr
   ||een/e4a5acc65d40f9dc5b9c2ab
   ||eacfadf602b2da19a
 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #1 from Sebastian Kügler  ---
Git commit e4a5acc65d40f9dc5b9c2abeacfadf602b2da19a by Sebastian Kügler.
Committed on 10/08/2016 at 00:50.
Pushed by sebas into branch 'master'.

[kcm] correctly position newly connected outputs

Outputs appearing at runtime weren't correctly positioned, since they
initially may be disabled, and are then enabled by the kded module
loading a known config. Disabled outputs don't have a position, and we
weren't updating it when enabling the output.

We can't simply listen to the output's posChanged signal since this
leads to complex round-trip loops with async calls.

M  +4-3kcm/src/declarative/qmlscreen.cpp

http://commits.kde.org/kscreen/e4a5acc65d40f9dc5b9c2abeacfadf602b2da19a

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 366536] Updater says packages available - discover reports up to date

[Aleix Pol via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366536

Aleix Pol  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from Aleix Pol  ---
No, no no. No problem with mixing packagekit and apt-get, other than the
problem described here. I'll see what I can do.

You might be wondering, in Kubuntu we use QApt which talks directly to apt, so
this problem doesn't happen.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 362096] Can't find apps I want to install using the "search" field

[Tony via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362096

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #8 from Tony  ---
Possible duplicate/related to this one:
https://bugs.kde.org/show_bug.cgi?id=362585

-- 
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.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366568

xaxa...@gmail.com changed:

   What|Removed |Added

 CC||xaxa...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kate] [Bug 366568] New: when dragging & dropping folders, contained files are opened as blank / new.

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366568

Bug ID: 366568
   Summary: when dragging & dropping folders, contained files are
opened as blank / new.
   Product: kate
   Version: 16.04
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: xaxa...@gmail.com

Dragging and dropping a folder that contains text files doesn't read the
content of the text files, but instead creates new blank documents for them and
colors them grey in the tree view.

Attempting to save these files would likely cause loss of data.

Perhaps this might be related to https://bugs.kde.org/show_bug.cgi?id=366260.

Reproducible: Always

Steps to Reproduce:
1. Open Kate with Tree View shown.
2. In dolphin (or another file browser) find a folder containing text files.
3. Drag & Drop this folder into Kate.

Actual Results:  
Kate creates entries for the created text files, but they are colored grey and
have no content when selected.

Expected Results:  
The created text file entries would contain the text their file contains.

System: Linux Mint XFCE 18
KDE apps installed from default Ubuntu 16.04 repository.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366567] Allow choosing several duplicate results

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366567

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Summary|Allow choosing several  |Allow choosing several
   |duplicates  |duplicate results

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 365083] sundtek - missing initialization for dvb device + patch

[Nicolás Alvarez via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365083

Nicolás Alvarez  changed:

   What|Removed |Added

 CC||nicolas.alva...@gmail.com
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|WONTFIX |---

--- Comment #10 from Nicolás Alvarez  ---
I don't even care what weird proprietary hardware would be fixed by this: the
existing code looks buggy and the patch seems to fix it.

DvbLinuxDeviceManager::componentAdded(QString node, int adapter, int index) is
creating a DvbLinuxDevice with heap garbage in the 'adapter', 'index', and
'dvbv5_parms' members. Unless I'm missing something, they are not initialized
anywhere, not even in the constructor. How is that not a bug, and why not merge
the patch?

If different future changes break support for this hardware again because the
driver is doing things fundamentally wrong, we'll discuss it then, but it's
orthogonal.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366567] New: Allow choosing several duplicates

[Simon via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366567

Bug ID: 366567
   Summary: Allow choosing several duplicates
   Product: digikam
   Version: 5.1.0
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Searches-Fuzzy
  Assignee: digikam-de...@kde.org
  Reporter: freisi...@gmail.com

Currently in the duplicate part of fuzzy search I can only select one group of
duplicates at a time. This is ok if you have just a few duplicates. However I
have lots of duplicates and want to sort/remove them. For this case the current
state is useless, I would have to go through hundreds of duplicates one by one.
If I could choose all/several of them I could then apply tags and use filters
on all of the duplicates. Thus I could choose a subset of all picture that have
a duplicate and remove them.

Reproducible: Always

Steps to Reproduce:
1. Search for duplicates
2. Try to select multiple items

Actual Results:  
Only one selection possible.

Expected Results:  
Select as many duplicate groups as you want.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366528] Rating=4 automatically added to XMP sidecar when saving metadata

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366528

--- Comment #2 from elfie.gros...@gmail.com ---
OK, I did some more testing. The problem seems to appear only when the
'IPTC:By-line' tag is set in the image metadata (I set this tag using Exiftool
in my workflow before loading the image into DigiKam).
I also tested with a couple other tags from the IPTC ApplicationRecord group
with the same results (IPTC:Source for instance).

You'll find a test NEF image with the By-line tag set to 'Test' here:
https://www.dropbox.com/sh/3iven4s0jamu5m5/AAC_6Of-XkPQu4krf2FpLSSNa?dl=0

DigiKam displays a rating of 4 for this image as soon as I drop it into one of
my albums. So the bug does not seem to be strictly related to XMP sidecars as I
first thought, even though for some images (but not all) the behavior only
appears after I have saved the metadata to a XMP sidecar first and then reread
it into DigiKam.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 365083] sundtek - missing initialization for dvb device + patch

[Luigi Toscano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365083

--- Comment #9 from Luigi Toscano  ---
(In reply to Markus Rechberger from comment #8)
> That's right and that is why the drivers are in userspace and not in
> kernelspace.
> 
> And that being said most customers prefer the binary form anyway because
> they just use our script to deploy the drivers on ARM, PPC, SH4, MIPS, X86
> (independent of the kernel version)
> The package is compatible with all linux versions down to 2.6.16

Apart from the issue of supporting the non-standard driver, as reported many
times, a Solid backend would do the trick instead of relying on the
application.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kaffeine] [Bug 365083] sundtek - missing initialization for dvb device + patch

[Markus Rechberger via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365083

--- Comment #8 from Markus Rechberger  ---
That's right and that is why the drivers are in userspace and not in
kernelspace.

And that being said most customers prefer the binary form anyway because they
just use our script to deploy the drivers on ARM, PPC, SH4, MIPS, X86
(independent of the kernel version)
The package is compatible with all linux versions down to 2.6.16

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 366498] InvalidResponseCode

[Paul D Mallett via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366498

--- Comment #5 from Paul D Mallett  ---
Guess what, if I scroll back we get a lot more. Sorry about that.
20:49:25.673 Imap::Mailbox::OpenConnectionTask OpenConnectionTask:  Activated
20:49:25.723 *** Looking up imap.postoffice.net...
20:49:25.723 conn Resolving hostname...
20:49:26.082 *** Connecting to imap.postoffice.net:143...
20:49:26.082 conn Connecting to the IMAP server...
20:49:26.225 *** Connection established
20:49:26.225 *** Connected
20:49:26.225 conn Checking capabilities...
20:49:26.365 <<< * OK IMAP4rev1 ca22 7134 1bdeuYz031 server ready␍␊
20:49:26.365 conn Waiting for encryption...
20:49:26.366 >>> y0 CAPABILITY␍␊
20:49:26.512 <<< * CAPABILITY IMAP4REV1 STARTTLS NAMESPACE CHILDREN UIDPLUS
IDLE␍␊
20:49:26.512 <<< y0 OK CAPABILITY completed␍␊
20:49:26.512 conn Asking for encryption...
20:49:26.513 >>> y1 STARTTLS␍␊
20:49:26.655 *** STARTTLS
20:49:26.656 <<< y1 OK Begin TLS negotiation now␍␊
20:49:26.656 conn Starting encryption (STARTTLS)...
20:49:27.144 *** [Socket is encrypted now; 1 errors: The root certificate of
the certificate chain is self-signed, and untrusted (CN: Entrust Root
Certification Authority) ]
20:49:27.144 conn Checking certificates (STARTTLS)...
20:49:27.148 conn Checking capabilities (after STARTTLS)...
20:49:27.148 >>> y2 CAPABILITY␍␊
20:49:27.293 <<< * OK IMAP4rev1 ca22 7134 1bdeuYz031 server ready␍␊
20:49:27.472 <<< * CAPABILITY IMAP4REV1 NAMESPACE CHILDREN UIDPLUS IDLE␍␊
20:49:27.473 <<< y2 OK CAPABILITY completed␍␊
20:49:27.473 conn Logging in...
20:49:39.432 >>> [LOGIN command goes here]
20:49:39.590 <<< y3 OK LOGIN completed␍␊
20:49:39.590 conn Checking capabilities (after login)...
20:49:39.591 >>> y4 CAPABILITY␍␊
20:49:39.738 <<< * CAPABILITY IMAP4REV1 NAMESPACE CHILDREN UIDPLUS IDLE␍␊
20:49:39.738 <<< y4 OK CAPABILITY completed␍␊
20:49:39.738 conn Logged in.
20:49:39.739 Imap::Mailbox::OpenConnectionTask OpenConnectionTask: Logged in.
Completed
20:49:39.739 Imap::Mailbox::GetAnyConnectionTask Activated
20:49:39.740 Imap::Mailbox::GetAnyConnectionTask Completed
20:49:39.740 Imap::Mailbox::ListChildMailboxesTask Listing stuff below mailbox 
Activated
20:49:39.741 Imap::Mailbox::GetAnyConnectionTask Completed
20:49:39.741 Imap::Mailbox::NumberOfMessagesTask attached to INBOX Activated
20:49:39.742 Imap::Mailbox::GetAnyConnectionTask Completed
20:49:39.742 Imap::Mailbox::NumberOfMessagesTask attached to Draft Activated
20:49:39.742 Imap::Mailbox::GetAnyConnectionTask Completed
20:49:39.743 Imap::Mailbox::NumberOfMessagesTask attached to Junk Mail
Activated
20:49:39.743 Imap::Mailbox::GetAnyConnectionTask Completed
20:49:39.744 Imap::Mailbox::NumberOfMessagesTask attached to Sent Activated
20:49:39.744 Imap::Mailbox::GetAnyConnectionTask Completed
20:49:39.744 Imap::Mailbox::NumberOfMessagesTask attached to Trash Activated
20:49:39.745 Imap::Mailbox::GetAnyConnectionTask Completed
20:49:39.745 Imap::Mailbox::ListChildMailboxesTask Listing stuff below mailbox 
Activated
20:49:39.746 >>> y5 LIST "" "%"␍␊
20:49:39.746 >>> y6 STATUS INBOX (MESSAGES UNSEEN RECENT)␍␊
20:49:39.746 >>> y7 STATUS Draft (MESSAGES UNSEEN RECENT)␍␊
20:49:39.746 >>> y8 STATUS "Junk Mail" (MESSAGES UNSEEN RECENT)␍␊
20:49:39.746 >>> y9 STATUS Sent (MESSAGES UNSEEN RECENT)␍␊
20:49:39.746 >>> y10 STATUS Trash (MESSAGES UNSEEN RECENT)␍␊
20:49:39.746 >>> y11 LIST "" "%"␍␊
20:49:39.894 <<< * LIST (\HasNoChildren) "/" "Draft"␍␊
20:49:39.895 <<< * LIST (\HasNoChildren) "/" "Inbox"␍␊
20:49:39.895 <<< * LIST (\HasNoChildren) "/" "Junk Mail"␍␊
20:49:39.895 <<< * LIST (\HasNoChildren) "/" "Sent"␍␊
20:49:39.895 <<< * LIST (\HasNoChildren) "/" "Trash"␍␊
20:49:40.025 <<< y5 OK LIST completed␍␊
20:49:40.025 <<< * STATUS "Inbox" (MESSAGES 140 RECENT 11 UNSEEN 138)␍␊
20:49:40.025 <<< y6 OK STATUS completed␍␊
20:49:40.025 <<< * STATUS "Draft" (MESSAGES 0 RECENT 0 UNSEEN 0)␍␊
20:49:40.025 <<< y7 OK STATUS completed␍␊
20:49:40.026 <<< * STATUS "Junk Mail" (MESSAGES 2 RECENT 2 UNSEEN 2)␍␊
20:49:40.026 <<< y8 OK STATUS completed␍␊
20:49:40.026 <<< * STATUS "Sent" (MESSAGES 0 RECENT 0 UNSEEN 0)␍␊
20:49:40.026 <<< y9 OK STATUS completed␍␊
20:49:40.027 Imap::Mailbox::ListChildMailboxesTask Listing stuff below mailbox 
Completed
20:49:40.027 Imap::Mailbox::NumberOfMessagesTask [invalid mailboxIndex]
Completed
20:49:40.028 Imap::Mailbox::NumberOfMessagesTask [invalid mailboxIndex]
Completed
20:49:40.028 Imap::Mailbox::NumberOfMessagesTask [invalid mailboxIndex]
Completed
20:49:40.028 Imap::Mailbox::NumberOfMessagesTask [invalid mailboxIndex]
Completed
20:49:40.032 Imap::Mailbox::GetAnyConnectionTask Activated
20:49:40.033 Imap::Mailbox::GetAnyConnectionTask Completed
20:49:40.033 Imap::Mailbox::NumberOfMessagesTask attached to INBOX Activated
20:49:40.035 Imap::Mailbox::GetAnyConnectionTask Activated
20:49:40.036 Imap::Mailbox::GetAnyConnectionTask Activated
20:49:40.037 Imap::Mailbox::GetAnyConnectionTask Activated
20:49:40.038 

[kaffeine] [Bug 365083] sundtek - missing initialization for dvb device + patch

[Luigi Toscano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365083

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it

--- Comment #7 from Luigi Toscano  ---
A pri(In reply to Markus Rechberger from comment #6)
> This behaviour is absolutely rubbish, right now there's a bug and a 3 lines
> patch available.
> 
> Whatever Mauro touches is a disaster in terms of maintainance. The truth is
> he has nothing to say when it comes to our drivers because we implemented
> the entire linux TV stack from scratch in userspace and it's out of his
> control. It's his competition and he's afraid of that.
> The compatibility is much higher of that the latest stack works until 2.6.16
> while the project he's in charge of needs heavy workarounds and removes
> several drivers to achieve some kind of backward compatibility.

A proprietary closed userspace driver, for people who don't know.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[David H . Gutteridge via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

David H. Gutteridge  changed:

   What|Removed |Added

 CC||dhgutteri...@hotmail.com

--- Comment #2 from David H. Gutteridge  ---
Under Gnome 3.20, KAlarm is starting for me when I've explicitly disabled
start-at-login for it via the UI's settings panel. This is with KAlarm
2.11.7-5ak (KDE Applications 16.04.3) on Fedora 24. The final entry in
/etc/xdg/autostart/kalarm.autostart.desktop is
"X-KDE-autostart-condition=kalarmrc:General:AutoStart:false" but that has no
effect (which is presumably because it's a KDE-specific directive). My
.config/kalarmrc also contains "NoAutoStart=true".

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356994] Task manager shows windows from wrong screen or not at all in dual monitor setup

[marco via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356994

--- Comment #13 from marco  ---
having that too with 4 monitors.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 356994] Task manager shows windows from wrong screen or not at all in dual monitor setup

[marco via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356994

marco  changed:

   What|Removed |Added

 CC||e-an...@gmx.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kajongg] [Bug 366566] kajongg can't start due to an "AttributeError: 'Tileset'"

[David Geiger via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366566

David Geiger  changed:

   What|Removed |Added

 Resolution|DOWNSTREAM  |FIXED

--- Comment #4 from David Geiger  ---
Ok found! as it is still an kde4 apps we need to install libkmahjongg from kde4
and not the one from kf5.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366549] plasmashell stops updating panel after suspend/resume or locked screen

[Thilo-Alexander Ginkel via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366549

--- Comment #1 from Thilo-Alexander Ginkel  ---
Brief update: I have been able to capture a plasmashell backtrace after the
freeze happened:

Thread 8 (Thread 0x7f499c8e1700 (LWP 4136)):
#0  0x7f4a5e26d48d in poll () from /usr/lib/libc.so.6
#1  0x7f4a59523fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f4a595240ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f4a5eb8f57f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f4a5eb390da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f4a5e95c0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f499ee050d7 in KCupsConnection::run() () from
/usr/lib/libkcupslib.so
#7  0x7f4a5e960d78 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f4a5da70454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f4a5e2767df in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f49afc14700 (LWP 4135)):
#0  0x7f4a5e26d48d in poll () from /usr/lib/libc.so.6
#1  0x7f4a59523fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f4a595240ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f4a5eb8f59b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f4a5eb390da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f4a5e95c0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f4a6285c8a6 in ?? () from /usr/lib/libQt5Quick.so.5
#7  0x7f4a5e960d78 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f4a5da70454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f4a5e2767df in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f4a36da2700 (LWP 4134)):
#0  0x7f4a5da7610f in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f4a642ecac4 in ?? () from /usr/lib/libQt5Script.so.5
#2  0x7f4a642ecb09 in ?? () from /usr/lib/libQt5Script.so.5
#3  0x7f4a5da70454 in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f4a5e2767df in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f4a44b56700 (LWP 4133)):
#0  0x7f4a5e26d48d in poll () from /usr/lib/libc.so.6
#1  0x7f4a59523fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f4a595240ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f4a5eb8f57f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f4a5eb390da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f4a5e95c0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f4a61cbd445 in ?? () from /usr/lib/libQt5Qml.so.5
---Type  to continue, or q  to quit---
#7  0x7f4a5e960d78 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f4a5da70454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f4a5e2767df in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f4a467bf700 (LWP 4132)):
#0  0x7f4a5e26d48d in poll () from /usr/lib/libc.so.6
#1  0x7f4a59523fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f4a595240ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f4a5eb8f57f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f4a5eb390da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f4a5e95c0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f4a61cbd445 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7f4a5e960d78 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f4a5da70454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f4a5e2767df in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f4a47fff700 (LWP 4130)):
#0  0x7f4a5e26d48d in poll () from /usr/lib/libc.so.6
#1  0x7f4a59523fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f4a595240ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f4a5eb8f59b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f4a5eb390da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f4a5e95c0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f4a5f6dce75 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f4a5e960d78 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f4a5da70454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f4a5e2767df in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f4a4de05700 (LWP 4129)):
#0  0x7f4a5e26d48d in poll () from /usr/lib/libc.so.6
#1  0x7f4a632368e0 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f4a63238679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f4a4fb42469 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f4a5e960d78 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f4a5da70454 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f4a5e2767df in clone () from /usr/lib/libc.so.6

[kio] [Bug 320775] KDE Help Center is unable to display writing_scrollkeeper_omf_files.xml

[Burkhard Lueck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=320775

Burkhard Lueck  changed:

   What|Removed |Added

 CC||lu...@hube-lueck.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 366503] Broken canvas

[wolthera via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366503

wolthera  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from wolthera  ---
Then please update to Krita 3.0, there's a ton of bugfixes between 3.0 and 2.9.
We will not fix bugs in 2.9 anymore.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kajongg] [Bug 366566] kajongg can't start due to an "AttributeError: 'Tileset'"

[Wolfgang Rohdewald via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366566

Wolfgang Rohdewald  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|UNCONFIRMED |RESOLVED
 CC||wolfg...@rohdewald.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kajongg] [Bug 366566] kajongg can't start due to an "AttributeError: 'Tileset'"

[Wolfgang Rohdewald via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366566

--- Comment #3 from Wolfgang Rohdewald  ---
You could edit /usr/share/apps/kajongg/tileset.py and replace __noTilesetsFound
with __noTilesetFound.

An upcoming version of kajongg will have that typo fixed.

If you fix that, you will get another error message telling you that kajongg
was not able to find any tilesets, asking you whether libkmahjongg is
installed.

So the real question is - do you have libkmahjongg installed? If not, why? Did
you only use the official Mageia package installer? If yes, please ask Mageia
to doublecheck kajongg package dependencies

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 357653] kalarm.autostart.desktop missing OnlyShowIn=KDE

[Rex Dieter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357653

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[Rex Dieter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

-- 
You are receiving this mail because:
You are watching all bug changes.

[kajongg] [Bug 366566] kajongg can't start due to an "AttributeError: 'Tileset'"

[Rex Dieter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366566

--- Comment #2 from Rex Dieter  ---
In particular, kde4-based libkmahjongg-14.12.3 (or newer libkmahjongg-16.04.x
if care is taken that it installs tilesets to the same place kmajongg expects)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kajongg] [Bug 366566] kajongg can't start due to an "AttributeError: 'Tileset'"

[Rex Dieter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366566

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

--- Comment #1 from Rex Dieter  ---
is libkmahjongg installed ?

(had similar problem in fedora until I added the necessary dependency)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 365991] Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection."

[Pip via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365991

--- Comment #7 from Pip  ---
Quite a lot of things. Kontact starts, go to settings, add a Local agent, add a
KMail mail folder, delete the Maildir agent. You should get your old mail and
accounts back. But the new mail doesn't seem to be displayed and I can't send
anything.
Progress of a sort.

-- 
You are receiving this mail because:
You are watching all bug changes.

[marble] [Bug 358094] Regression; Scroll-zoom with touchpads broken in Marble v15.12

[Andrej Dundovic via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358094

Andrej Dundovic  changed:

   What|Removed |Added

 CC||adund...@gmail.com

--- Comment #8 from Andrej Dundovic  ---
Also confirm.
- Marble ver. 1.14.1
- KDE Frameworks 5.24.0
- Qt 5.6.1 (built against 5.6.1)
- The xcb windowing system

-- 
You are receiving this mail because:
You are watching all bug changes.

[kajongg] [Bug 366566] New: kajongg can't start due to an "AttributeError: 'Tileset'"

[David Geiger via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366566

Bug ID: 366566
   Summary: kajongg can't start due to an "AttributeError:
'Tileset'"
   Product: kajongg
   Version: 4.13.0
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: wolfg...@rohdewald.de
  Reporter: geiger.david68...@gmail.com
CC: kde-games-b...@kde.org

Hi,

On Mageia 6 we can't use kajongg anymore due to an AttributeError: 'Tileset':

$ kajongg
Traceback (most recent call last):
  File "/bin/kajongg", line 188, in 
MainWindow()
  File "/usr/share/apps/kajongg/mainwindow.py", line 144, in __init__
self.setupUi()
  File "/usr/share/apps/kajongg/mainwindow.py", line 254, in setupUi
self.windTileset = Tileset(Internal.Preferences.windTilesetName)
  File "/usr/share/apps/kajongg/tileset.py", line 108, in __init__
self.__noTilesetsFound()
AttributeError: 'Tileset' object has no attribute '_Tileset__noTilesetsFound'
$

$ kajongg --version
Qt : 4.8.7
Plate-forme de développement de KDE : 4.14.22
Ka-jongg : 4.13.0
$

This is with the latest kajongg release: kajongg-16.04.3

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[marble] [Bug 358094] Regression; Scroll-zoom with touchpads broken in Marble v15.12

[Dennis Nienhüser via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358094

--- Comment #9 from Dennis Nienhüser  ---
Should be fixed with KDE Applications 16.08 (Marble 2.0). See
https://phabricator.kde.org/D1585

-- 
You are receiving this mail because:
You are watching all bug changes.

[k3b] [Bug 366565] New: k3b freezes desktop while burning disk

[court via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366565

Bug ID: 366565
   Summary: k3b freezes desktop while burning disk
   Product: k3b
   Version: 2.0.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Data Project
  Assignee: k...@kde.org
  Reporter: courthic...@gmail.com
CC: mich...@jabster.pl, tr...@kde.org

I will do a data project burn, and while the burn is in progress the desktop
will freeze if I try to use a hot corner. Once the project is done, the desktop
unfreezes and I can resume my work.

Reproducible: Always

Steps to Reproduce:
1. Start data project
2. Begin burning the disk
3. Do a hot corner (my testing has been with desktop grid)
4. Wait for burn to finish so desktop unfreezes

Actual Results:  
Desktop freezes and renders desktop unusable, however I can still change TTYs.
Unfreezes when the disk burn is complete

Expected Results:  
Desktop doesn't freeze and I can multitask while the burn is in progress

This is KDE Neon 5.7.3 and I am using OpenGL 3.1 for rendering

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 362668] Dolphin crash because Home/.config/katerc NOT writeable

[Mike C . Fletcher via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362668

--- Comment #3 from Mike C. Fletcher  ---
Created attachment 100519
  --> https://bugs.kde.org/attachment.cgi?id=100519=edit
New crash information added by DrKonqi

dolphin (15.12.3) using Qt 5.5.1

- What I was doing when the application crashed:

Just saw this happen when browsing to a (remote, slow) smb server. Clicked the
address bar, typed in the *wrong-cased* next segment of the URL I wanted to
visit. When replicating there was a dialog displayed saying that the
wrong-cased version of the path didn't exist before Dolphin crashed. That is,
it may not just be permissions causing the issue, it may be simply "missing"
directories.

-- Backtrace (Reduced):
#8  0x7f3200968b99 in KDialogJobUiDelegate::Private::next() () from
/usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#9  0x7f31fd145ea1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f31fdc1905c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7f31fdc1e516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f31fd11662b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 362668] Dolphin crash because Home/.config/katerc NOT writeable

[Mike C . Fletcher via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362668

Mike C. Fletcher  changed:

   What|Removed |Added

 CC||mcfle...@vrplumber.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366333] Plasma-5 crash using sddm as login manager using "users switch".

[Sandro via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366333

Sandro  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #11 from Sandro  ---
Ok  now i've made some experiment:

I tried with "Funtoo Stable" with xorg-server-1.17.4 and "nouveau" drivers.
The users exchange now takes place on a regular basis. Then the problem is
probably due to the release of xorg-server and / or proprietary nvidia-drivers.

Sorry for this bug report; Now the "users-switch" seems to work properly.

I tried it with "Funtoo Stable" with xorg-server-1.17.4 and "nouveau" drivers.
The users exchange now takes place on a regular basis. Then the problem is
probably due to the release of xorg-server and / or proprietary nvidia-drivers.

But I also tried other distributions as Manjaro and devuan; with them there
were problems with nouveau.

I hope this feedback can be considered "positive" :)
I will write in "nvidia.com" that there are troubles with graphics proprietary
drivers _'_
Thanks for All _'_

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366559] Wrong item counting in face detection view

[Stefano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366559

--- Comment #2 from Stefano  ---
Ok, but the first is a number related to a single album, in a multi-album
view... not very meaningful.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 281802] KCheckpass doesn't work correctly with samba accounts

[David Walser via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=281802

David Walser  changed:

   What|Removed |Added

 CC||luigiwal...@yahoo.com

--- Comment #3 from David Walser  ---
This appears to be a problem with using non-local users in general.  However,
KDE4 (Mageia 5) worked fine.  It's not until Plasma 5 (5.7.2 being the first
version I tested) where the issue shows up (Mageia Cauldron).

I confirmed that running kcheckpass in the Konsole also gives Authentication
failure when entering the correct password.  For a local user, it works just
fine.  I have reported this also here:
https://bugs.mageia.org/show_bug.cgi?id=19103

/etc/pam.d/kcheckpass just includes system-auth for all 4 sections.  My
non-local users are using sssd (the accounts are in Active Directory).

/etc/pam.d/system-auth has this:
authrequired  pam_env.so
authrequired  pam_mount.so
authsufficientpam_tcb.so shadow nullok prefix=$2a$ count=8
use_first_pass
authsufficientpam_sss.so use_first_pass
authrequired  pam_deny.so

account sufficientpam_tcb.so shadow
account [default=bad success=ok user_unknown=ignore] pam_sss.so
account required  pam_permit.so

passwordrequired  pam_cracklib.so try_first_pass retry=3 minlen=4 
dcredit=0  ucredit=0
passwordsufficientpam_tcb.so use_authtok shadow write_to=shadow nullok
prefix=$2a$ count=8
passwordsufficientpam_sss.so use_authtok
passwordrequired  pam_deny.so

session required  pam_mkhomedir.so umask=0026 skel=/etc/skel/ silent
session optional  pam_keyinit.so revoke
session required  pam_limits.so
session [success=1 default=ignore] pam_succeed_if.so service in crond quiet
use_uid
-sessionoptional  pam_systemd.so
session required  pam_tcb.so
session optional  pam_sss.so
session optional  pam_mount.so disable_interactive

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366559] Wrong item counting in face detection view

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366559

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
The counter differs, when more than one face is detected per image. I do not
really see it as a problem.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366558] Face detection does not honour album selection in options

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366558

--- Comment #6 from Maik Qualmann  ---
Oh, wrong thread of Comments 5...

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 357315] Resume from Standby (Suspend to RAM) results in black screen (but with themed cursor)

[Simone Gaiarin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357315

--- Comment #2 from Simone Gaiarin  ---
I forget to say, that a workaround is to restart plasma.

-- 
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

[Andrés Becerra Sandoval via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361189

--- Comment #1 from Andrés Becerra Sandoval  ---
Still present with version 16.04.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366558] Face detection does not honour album selection in options

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366558

--- Comment #5 from Maik Qualmann  ---
The counter differs, when more than one face is detected per image. I do not
really see it as a problem.

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 366502] title editor can't edit older version saved titles *.kdenlivetitle

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366502

--- Comment #9 from Wegwerf  ---
You'll need to install some KF5 Plasma and frameworks packges; as I'm using
Kubuntu I unfortunately don't remember which packages need to be installed so
that the file dialogs work correctly; this is somehow related to media types.
Please search the Kdenlive forum for help, there are several threads about
installing Kdenlive on Ubuntu.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 357315] Resume from Standby (Suspend to RAM) results in black screen (but with themed cursor)

[Simone Gaiarin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=357315

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

--- Comment #1 from Simone Gaiarin  ---
Same problem here. To me it happens on a single screen (the laptop screen) when
using a multimonitor configuration.

The panel is on the external monitor, which is set as primary.

Resuming from sleep causes the laptop screen to be black, and impossible to
interact with. The screen is on, and I can see the mouse cursor. The external
monitor works just fine.

How can I provide more debugging information?

Running plasma 5.7.3

Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
   Display Server: X.Org 1.17.4 driver: intel Resolution:
1920x1080@60.02hz, 1920x1080@60.00hz
   GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa
12.0.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 366502] title editor can't edit older version saved titles *.kdenlivetitle

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366502

--- Comment #8 from dimitrisbolar...@gmail.com ---
No i use GNOME

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 366502] title editor can't edit older version saved titles *.kdenlivetitle

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366502

--- Comment #7 from dimitrisbolar...@gmail.com ---
I'm in Ubuntu 16.06 after upgrading from 14.04

The saving steps:
I make the title, press the upper left button "Save As", on window choose
folder, i give title name (always as .kdenlivetitle) and then "save" as i use
to do on previous edition of kdenlive (9.0)

When trying  to reopen the title nothing appears in selected folder

I will search about KF5 plasma

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 365991] Starting Kontact/Kmail causes crash. Command line shows - akonadicore_log: Failed SpecialCollectionsRequestJob::slotResult "Failed to fetch the resource collection."

[Pip via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365991

--- Comment #6 from Pip  ---
A way around: I took out the KMail Mail Folder agent and put in a Maildir agent
pointing to the same place. At first glance, that seems to get around the
problem, though there are still things to tidy up.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 364721] KMail Crash every time I press "Enter" for completing a mail recipient.

[Daniel Vrátil via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364721

Daniel Vrátil  changed:

   What|Removed |Added

   Version Fixed In||16.08.0
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/akon
   ||adi/3d9ebd56a6f6ca20c8ff7ac
   ||19bc5abbf819db182

--- Comment #5 from Daniel Vrátil  ---
Git commit 3d9ebd56a6f6ca20c8ff7ac19bc5abbf819db182 by Daniel Vrátil.
Committed on 09/08/2016 at 19:07.
Pushed by dvratil into branch 'Applications/16.08'.

Ignore any response that arrives after job has finished
FIXED-IN: 16.08.0

M  +16   -7src/core/jobs/job.cpp

http://commits.kde.org/akonadi/3d9ebd56a6f6ca20c8ff7ac19bc5abbf819db182

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[David Jarvie via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

David Jarvie  changed:

   What|Removed |Added

  Component|kalarmd |general

--- Comment #1 from David Jarvie  ---
KAlarm is designed to autostart at login once it has been run, to ensure that
alarms are not missed. But it shouldn't start if it has never been used, or if
the user has explicitly disabled start-at-login for it.

What version of KAlarm are you using? What you report may well have been fixed
in version 2.11.6 (KDE Applications 16.04.1). The fix prevents KAlarm
autostarting in non-KDE desktops if KAlarm's start-at-login is disabled. See
https://forum.kde.org/viewtopic.php?f=229=131410.

Please see further explanation of autostart in non-KDE desktops at
https://bugs.kde.org/show_bug.cgi?id=357653.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 366516] git master 2016-08-08: Speed effect artificial limit.

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366516

--- Comment #5 from Wegwerf  ---
Evert, you don't *see* audio support? It should be audible, any joking aside.
But I'm not sure within which speed range, so it may be limited to a certain
speed range only.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366542] Build failure on i686

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366542

caulier.gil...@gmail.com changed:

   What|Removed |Added

   Version Fixed In||5.2.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/067a88d8c84a5149469961d
   ||54b1d5c93df6a3167
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from caulier.gil...@gmail.com ---
Git commit 067a88d8c84a5149469961d54b1d5c93df6a3167 by Gilles Caulier.
Committed on 09/08/2016 at 18:41.
Pushed by cgilles into branch 'master'.

apply patch #100514 to fix broken compilation under 32 bits platform with GCC
6.1
FIXED-IN: 5.2.0

M  +2-1NEWS
M  +9-2libs/rawengine/libraw/libraw/libraw_types.h

http://commits.kde.org/digikam/067a88d8c84a5149469961d54b1d5c93df6a3167

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366473] Please package Kirigami

[Jonathan Riddell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366473

Jonathan Riddell  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Jonathan Riddell  ---
venga 
http://build.neon.kde.org/job/xenial_unstable_kde-extras_kirigami/

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 366516] git master 2016-08-08: Speed effect artificial limit.

[Evert Vorster via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366516

--- Comment #4 from Evert Vorster  ---
I don't see any audio support on the new speed effect, is that still to be
implemented?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366558] Face detection does not honour album selection in options

[Stefano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366558

--- Comment #4 from Stefano  ---
No, I'm not using that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366558] Face detection does not honour album selection in options

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366558

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #3 from caulier.gil...@gmail.com ---
And do you use Group photos feature ? Its know that count of items is wrong
when items are grouped...

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 366564] New: Please change autostart defaults to not interfere with non-KDE desktops

[piedro via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366564

Bug ID: 366564
   Summary: Please change autostart defaults to not interfere with
non-KDE desktops
   Product: kdeconnect
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: piedro.kul...@googlemail.com

The kdeconnectd.desktop entries in /etc/xdg/autostart indicate that kdeconnectd
is started with every desktop environment. Imo this is very intrusive, a user
who installs a secondary DE should not beforced to run KDE daemons in the
background. The use of kdeconnectd should be optional and not enabled by
default.  

Please change the entry in kdeconnectd.desktop from  

> X-GNOME-Autostart-enabled=true
> OnlyShowIn=KDE;GNOME;Unity;XFCE;

to 

> X-GNOME-Autostart-enabled=false
> OnlyShowIn=KDE;

thx, p.


Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366563] New: Idle computer crash

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366563

Bug ID: 366563
   Summary: Idle computer crash
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rudder2junkm...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-31-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
When the computer is idle it crashes alot.  All it is doing is turning off the
monitor...I don't have it go in to a power save state.

The crash can be reproduced sometimes.

-- Backtrace:
A useful backtrace could not be generated

Possible duplicates by query: bug 366485, bug 366465, bug 366460, bug 366439,
bug 366428.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366247] Digikam writes metadata to some files only not every one

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366247

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #7 from Maik Qualmann  ---
Here not to reproduce with a Windows VM and a real Windows machine. If you are
using an antivirus program, you can disable it for testing?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] New: Kalarm starts in non-KDE desktop environments...

[piedro via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

Bug ID: 366562
   Summary: Kalarm starts in non-KDE desktop environments...
   Product: kalarm
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kalarmd
  Assignee: djar...@kde.org
  Reporter: piedro.kul...@googlemail.com

Kalarm is by default set to start with every desktop environment. 

Please add 

X-GNOME-Autostart-enabled=false
OnlyShowIn=KDE

or something along these lines to the default autostart configuration file in
/etc/xdg/autostart/. 

A KDE application should not be autostarted within other DEs unless explicitly
asked for. 

It's just a little change to the default configuration and leads to less people
wondering how to disable kalarm when starting Gnome which  has it's own
calendar and reminder service. 

thx a lot, piedro 

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366558] Face detection does not honour album selection in options

[Stefano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366558

--- Comment #2 from Stefano  ---
I have the "all tags" ticked.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366558] Face detection does not honour album selection in options

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366558

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
The problem is not to reproduce. Do you have the inclusion of keywords
disabled?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 366561] New: Baloo file daemon starts with non-KDE Desktop environments

[piedro via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366561

Bug ID: 366561
   Summary: Baloo file daemon starts with non-KDE Desktop
environments
   Product: frameworks-baloo
   Version: 5.24.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: pinak.ah...@gmail.com
  Reporter: piedro.kul...@googlemail.com

As I found out after looking into the /ec/xdg/autostart folder - the following
settings are used to start the baloo file daemon in the background no matter
what DE is used. 

> X-GNOME-Autostart-enabled=true
> OnlyShowIn=KDE;GNOME;Unity;XFCE 

This is unnecessarily intrusive behaviour. Users installing another desktop
environment alongside KDE will have a distorted experience (like performance
issues - Gnome for example has it's own background service for indexing!). 

Since there are now additional background processes running which have no
function within their DE. 

Please change the configuration defaults to something like:  

> X-GNOME-Autostart-enabled=false
> OnlyShowIn=KDE

thx, piedro

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366528] Rating=4 automatically added to XMP sidecar when saving metadata

[Maik Qualmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366528

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
This problem is not to reproduce with my NEF files here under Linux and
Windows. Can you provide a test image?

Maik

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 366555] The limit of sensitivity levels tablet Huion h610

[dude via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366555

--- Comment #2 from dude  ---
Created attachment 100515
  --> https://bugs.kde.org/attachment.cgi?id=100515=edit
log

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 366560] New: When i try to create the document Krita was crash.

[George via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366560

Bug ID: 366560
   Summary: When i try to create the document Krita was crash.
   Product: krita
   Version: 3.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: george.shada...@gmail.com

Application: krita (3.0)

Qt Version: 5.7.0
Frameworks Version: 5.24.0
Operating System: Linux 4.4.16-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed: I click file>make
file>templates>A4 and Krita was crush.
OS Manjaro 16.06.1 Daniella KDE, Kenel x86_64 Linux 4.4.16-1-MANJARO, WM KWin,
CPU AMD A4-1200 APU with Radeon HD Graphics @ 1GHz,  GPU AMD Radeon HD 8180.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f68fd8ec7c0 (LWP 2936))]

Thread 8 (Thread 0x7f68a0ffc700 (LWP 3964)):
#0  0x7f68f4a58458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f68fb054b66 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f68fb050274 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f68fb053d78 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f68f4a52484 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f68fa7506dd in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f68bd5fb700 (LWP 3963)):
#0  0x7f68f4a58458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f68fb054b66 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f68fb050274 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f68fb053d78 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f68f4a52484 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f68fa7506dd in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f68bddfc700 (LWP 3015)):
#0  0x7f68f4a580af in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f68fb054c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f68fc131851 in ?? () from /usr/lib/libQt5Widgets.so.5
#3  0x7f68fb053d78 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f68f4a52484 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f68fa7506dd in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f68be9fe700 (LWP 3014)):
#0  0x7f68f4a580af in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f68fb054c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f68fb04de26 in QSemaphore::tryAcquire(int, int) () from
/usr/lib/libQt5Core.so.5
#3  0x7f68f8b0439a in KisTileDataSwapper::run() () from
/usr/lib/libkritaimage.so.15
#4  0x7f68fb053d78 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f68f4a52484 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f68fa7506dd in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f68bf1ff700 (LWP 3013)):
#0  0x7f68f4a580af in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f68fb054c2b in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f68fb04db33 in QSemaphore::acquire(int) () from
/usr/lib/libQt5Core.so.5
#3  0x7f68f8ae80dd in ?? () from /usr/lib/libkritaimage.so.15
#4  0x7f68fb053d78 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f68f4a52484 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f68fa7506dd in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f68db75f700 (LWP 2940)):
#0  0x7f68fa7476cd in poll () from /usr/lib/libc.so.6
#1  0x7f68f3467fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f68f34680ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f68fb28259b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f68fb22c0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f68fb04f0f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f68f4c7de75 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f68fb053d78 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f68f4a52484 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f68fa7506dd in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f68dc505700 (LWP 2939)):
#0  0x7f68fa7204fd in nanosleep () from /usr/lib/libc.so.6
#1  0x7f68fa749b54 in usleep () from /usr/lib/libc.so.6
#2  0x7f68df181d00 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#3  0x7f68de882332 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#4  0x7f68de882385 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#5  

[kmymoney4] [Bug 366326] OFX direct download fails when OFX UID is expected by bank

[Swj via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366326

--- Comment #6 from Swj  ---
Is there a not too difficult way I could get a windows binary with these
patches in it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366559] New: Wrong item counting in face detection view

[Stefano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366559

Bug ID: 366559
   Summary: Wrong item counting in face detection view
   Product: digikam
   Version: 5.0.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Faces-Management
  Assignee: digikam-de...@kde.org
  Reporter: rs4...@gmail.com

When viewing the faces to detect, if you select only on item you'll get in
lower-left corner a counting of the current album items over the detected
faces, which is not useful and misleading: for example, "DSC03254.JPG (1684 of
2017)" where 1684 is the number of images in the album and 2034 is the total
number of faces to detect among the collection.

If you select two images, it correctly gives "2/2017 items selected".

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366558] New: Face detection does not honour album selection in options

[Stefano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366558

Bug ID: 366558
   Summary: Face detection does not honour album selection in
options
   Product: digikam
   Version: 5.0.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Faces-Management
  Assignee: digikam-de...@kde.org
  Reporter: rs4...@gmail.com

Even if you choose the albums on which face detection should be done, it always
works on the entire collection.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366557] New: Face detection/recognition options are not persistent

[Stefano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366557

Bug ID: 366557
   Summary: Face detection/recognition options are not persistent
   Product: digikam
   Version: 5.0.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Faces-Management
  Assignee: digikam-de...@kde.org
  Reporter: rs4...@gmail.com

Face detection/recognition options are not persistent, you need to adjust
accuracy level and options like "Work on all cores" every time you launch it.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366556] New: Add possibility to exclude an album (and possibily its children) from face detection

[Stefano via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366556

Bug ID: 366556
   Summary: Add possibility to exclude an album (and possibily its
children) from face detection
   Product: digikam
   Version: 5.0.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Faces-Management
  Assignee: digikam-de...@kde.org
  Reporter: rs4...@gmail.com

It would be desirable to avoid face-detection on album trees and subtrees where
you don't care about face tagging: for example if you routinely shoot crowded
public events you'd likely avoid to have those albums scanned for faces, having
thousands of data to manually discard.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366428] Plasma crash on login with two monitors - No wallpaper on second screen, panels missing

[Emmanuel Dieul via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366428

--- Comment #2 from Emmanuel Dieul  ---
Concerning the second screen (the black one with no background wallpaper),
precisely, the mouse can be shown on the whole screen.
Windows too but they must not be fully on the second screen (there must be at
least one part of the window on the screen with the background wallpaper).
Otherwise, they disappear.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 366555] The limit of sensitivity levels tablet Huion h610

[wolthera via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366555

wolthera  changed:

   What|Removed |Added

   Platform|Other   |MS Windows
 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||griffinval...@gmail.com

--- Comment #1 from wolthera  ---
Could you make us a tablet log as well? https://docs.krita.org/KritaFAQ#Windows

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 366548] monitor configuration disappears when logging out

[Sebastian Kügler via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366548

Sebastian Kügler  changed:

   What|Removed |Added

 Resolution|--- |UNMAINTAINED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Sebastian Kügler  ---
Thanks, Thomas, for the bug report!

We're not maintaining Plasma 4 anymore upstream, so this bug is unlikely to get
attention in Plasma 4. I'm pretty confident that this is fixed in Plasma 5,
however, so once you decide to upgrade, it should work just fine. If it doesn't
(especially with 5.8, where we fixed a lot of multi screen problems), please
file a separate bug report.

Sorry to not be more useful for your immediate situation, though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366542] Build failure on i686

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366542

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||l...@lexa.ru

--- Comment #9 from caulier.gil...@gmail.com ---
Yes the fix sound like correct for me and simple.

In fact, this code come from Libraw. I CC Libraw team as feedback. The right
fix will appear in offcial Libraw 0.18.0 that i will backport.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 366555] New: The limit of sensitivity levels tablet Huion h610

[dude via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366555

Bug ID: 366555
   Summary: The limit of sensitivity levels tablet Huion h610
   Product: krita
   Version: unspecified
  Platform: Other
   URL: https://drive.google.com/file/d/0Byw-S-mAgmDOajU2S3JpU
Tl1aEE/view?usp=sharing
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: ur10...@gmail.com

Operating sitstema windows7 \ XP sp3. The video shows that the sensitivity of
the pressing step, and is limited to ~256 levels of 2048. This occurs on all
versions as far as I remember, from the last known 2.9.11, 3.0 for sure. Driver
for graphics tablet tested are different, and the effect of this everywhere.
Tested version 8.01 , 11.0.7 , 12.2.16, and others. As the work and even
checked on another machine with windows XP and other programs work correctly
(except for version driver 12 and further, worst response), I exclude the
possibility of incorrect installation of drivers and software. In case, if it
is indeed a defect and not my hands curves, I hope for a speedy solution to the
problem in new versions of the software\drivers.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

[Anton Kirilov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360571

--- Comment #6 from Anton Kirilov  ---
Just a theoretical question.

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366375] libkf5dgantt2-5 can't be upgraded kde neon user edition

[Jonathan Riddell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366375

Jonathan Riddell  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Jonathan Riddell  ---
closing as fixed in user edition

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

[Julian Seward via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360571

--- Comment #5 from Julian Seward  ---
(In reply to Anton Kirilov from comment #4)
> Just a quick idea - do you think it is worth it supporting more than one
> range (e.g. for running code generated by a compiler that misbehaves in the
> same way as GCC 2.96 in an environment similar to Android)?

Well, not really.  The gcc-2.96 style read/write below SP errors are real bugs
and I'd prefer to make it hard to hide those :-).  In the worst case you could
simply use
  --ignore-accesses-below-sp-range=0,8191

and then they would all disappear.

Do you have an actual use case like this?  Or is it more of a theoretical
question?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366542] Build failure on i686

[Rex Dieter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366542

--- Comment #8 from Rex Dieter  ---
Created attachment 100514
  --> https://bugs.kde.org/attachment.cgi?id=100514=edit
quick-n-dirty fix

here's a quick-n-dirty patch I used that fixes it for me

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366375] libkf5dgantt2-5 can't be upgraded kde neon user edition

[Bernhard Scheirle via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366375

Bernhard Scheirle  changed:

   What|Removed |Added

 CC||bernhard+...@scheirle.de

--- Comment #3 from Bernhard Scheirle  ---
I also had this issue with the old(=ubuntu) PIM packages.

> does this work now in user edition?
Since neon provides the PIM packages the issue is gone.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 364583] Composition effect: Using the zoom produces black outlines

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364583

--- Comment #4 from Wegwerf  ---
Sounds like the issue I also saw in one of my projects. 

Re: affine ... it is computationally more intensive; new "Composite and
transform" may give better rendering performance,  but then, we have now
timeline preview rendering in the current beta.

Re: compose ... downside is luma bleed, which is a constant headache; upside is
wipe support, which I still lack for the new C+T transition.

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366542] Build failure on i686

[David Geiger via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366542

David Geiger  changed:

   What|Removed |Added

 CC||geiger.david68...@gmail.com

--- Comment #7 from David Geiger  ---
Confirmed also here on Mageia6 (Cauldron):

http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20160809103222.ennael.duvel.26316/log/digikam-5.1.0-1.mga6/build.0.20160809103357.log

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 364583] Composition effect: Using the zoom produces black outlines

[Stefan Naumann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364583

--- Comment #3 from Stefan Naumann  ---
There are rather thin black lines around the edges of the virtual text-layer
which is shrinking in size. These black lines appear not directly at the text,
but the edge of the layer.

Affine is (or at least was in older versions) way heavier on cpu-power and
therefore rendering-time, than composite.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 366531] git master: Transform (qtblend) effect doesn't allow for CCW rotation; rotation origin is top-left instead of center

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366531

--- Comment #1 from Wegwerf  ---
3. Can the alpha operation parameter be used at all for a filter/effect?

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 366551] Unclear dialog when associating people to faces

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366551

caulier.gil...@gmail.com changed:

   What|Removed |Added

Version|unspecified |5.0.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366554] Funny overlapping lock screens on overlapping monitors

[Josef Kufner via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366554

--- Comment #1 from Josef Kufner  ---
Created attachment 100513
  --> https://bugs.kde.org/attachment.cgi?id=100513=edit
The screenshot

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 366554] New: Funny overlapping lock screens on overlapping monitors

[Josef Kufner via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366554

Bug ID: 366554
   Summary: Funny overlapping lock screens on overlapping monitors
   Product: plasmashell
   Version: 5.6.5
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: j...@frozen-doe.net
CC: plasma-b...@kde.org

See the attached screenshot. The lock screen is shown twice when two displays
are overlapping (partial clone). The screenshots shows the screen layout, where
the large screen (matching the dimensions of the screenshot) is the primary
screen. And small portion in top left corner is what is visible on the second
screen. And there is the second prompt for password, overlapping the first one.

Reproducible: Always

Steps to Reproduce:
1. Set the second screen to show portion of the primary screen.
2. Lock the desktop.

Actual Results:  
See the screenshot.

Expected Results:  
A single lock screen as if the second screen is disabled.

$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
280mm x 160mm
   1920x1080 60.04*+  59.93
   1680x1050 59.9559.88
   1600x1024 60.17
   ...
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x
0mm
   1920x1080i60.00 +  50.0059.94
   1920x1080 60.0050.0059.94
   1280x720  60.0050.0059.94
   800x600   72.19*
   720x576   50.00
   720x576i  50.00
   720x480   60.0059.94
   720x480i  60.0059.94
   1360x768_59.80  59.80
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated
Graphics (rev 09)

$ uname -a
Linux 4.5.0-2-amd64 #1 SMP Debian 4.5.5-1 (2016-05-29) x86_64 GNU/Linux

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 366553] New: Dolphin shows Trash: files origin path wrong if same name file was moved to trash twice

[Morgan Leijström via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366553

Bug ID: 366553
   Summary: Dolphin shows Trash: files origin path wrong if same
name file was moved to trash twice
   Product: dolphin
   Version: unspecified
  Platform: Mageia RPMs
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: t...@tribun.eu

Cloned from https://bugs.mageia.org/show_bug.cgi?id=18608
Dolphin 16.04.3 ,  KDE 5.24.0 , Qt 5.6.1 on Mageia 6 (Cauldron)
While using KDE & Dolphin:

1. create file "text" in your home, then "delete" it to trash
 then again:
2. create file "text" in your home, then "delete" it to trash
3. Open trash and see the files listed as:

_File__Folder___
text /home/user
text(1)  /home/user/text


That "/home/user/text" is plain wrong; the file was not deleted from am folder
named text!
(trash folders are listed without trailing dash "/" )

It works correctly; i can restore that text(1) and it ends up as "text" in
/home/user/


Quick test using thunar to delete files to trash:
The files in trash is shown by the original name in trash using thunar
  unfortunately it seem thunar can not show source (original file location)
Looking at those files in trash using dolphin they are named like *.2 instead
of *(1) (that is irrelevant) but also for them dolphin show wrong path


BTW it is even more confusing if user happen to delete a file named "something
(1)" twice, dolphin then list a never existed filename "something (2)" in
trash, and say it was deleted from folder "whatever/something (1)"

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 360571] Error about the Android Runtime reading below the stack pointer on ARM

[Anton Kirilov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360571

--- Comment #4 from Anton Kirilov  ---
(In reply to Julian Seward from comment #3)
> An alternative is to introduce a new flag, something like this (eg)
> 
>   --ignore-accesses-below-sp-range=-
> 
> so that just the specified range is ignored.
Yes, that will work as well.

Just a quick idea - do you think it is worth it supporting more than one range
(e.g. for running code generated by a compiler that misbehaves in the same way
as GCC 2.96 in an environment similar to Android)?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 364583] Composition effect: Using the zoom produces black outlines

[Wegwerf via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=364583

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #2 from Wegwerf  ---
I can't see it either, at least not on my tablet. Are these rather thin black
lines, as opposed to thicker borders? I noticed them when using then Affine
transition in some border cases; Vincent, wasn't there some Affine fix in MLT
or something in frei0r related to that some time ago?

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 366375] libkf5dgantt2-5 can't be upgraded kde neon user edition

[Jonathan Riddell via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366375

--- Comment #2 from Jonathan Riddell  ---
does this work now in user edition?  All of KDE PIM should be updated now

-- 
You are receiving this mail because:
You are watching all bug changes.