[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

[Sebastian Kuhne]

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

Sebastian Kuhne  changed:

   What|Removed |Added

 CC||sebastiankuhne1@googlemail.
   ||com

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

[neon] [Bug 410779] Slow or unreliable downloads of KDE Neon release images and lack of adoption of Metalink

[Kristopher Ives]

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

--- Comment #3 from Kristopher Ives  ---
Thanks for reminding me. I have released it under the MIT license. Please let
me know if there is anything else I can do to help.

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

[dolphin] [Bug 410836] New: Trying to copy from zip to SFTP disconnects the SFTP

[bugzilla_noreply]

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

Bug ID: 410836
   Summary: Trying to copy from zip to SFTP disconnects the SFTP
   Product: dolphin
   Version: 19.04.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: darrenwstu...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

SUMMARY

If you try to copy from a zip window to a SFTP window, it doesn't only not
copy, but kills the SFTP session

STEPS TO REPRODUCE
1. Open zip in Dolphin instance
2. Open SFTP instance in another Dolphin instance
3. Drag and drop from zip to SFTP
4. Popup saying can't write to directory

OBSERVED RESULT

Can't write to directory popup

EXPECTED RESULT

Copied files

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon User Edition 5.16 x86_64
(available in About System)
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version: 5.12.3

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

[kwin] [Bug 410827] Neither KWinscript nor wmctrl show all the windows on Wayland

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |LATER
 Status|REPORTED|RESOLVED

--- Comment #1 from Martin Flöser  ---
Wmctrl is an X11 tool. Obviously it cannot show Wayland windows.

Wayland windows are currently excluded from scripting due to security
constraints. This will eventually be changed in future. As this is currently
intended I'm setting to resolved later.

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

[gwenview] [Bug 277996] Make it possible to adjust JPEG quality/compression settings when saving

[Nate Graham]

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

--- Comment #9 from Nate Graham  ---
I've submitted a patch to implement this feature:
https://phabricator.kde.org/D23106.

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

[kmail2] [Bug 341909] Reply and Print time is in UTC, not in locale

[Bug Janitor Service]

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

--- Comment #20 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[blinken] [Bug 410270] sound problems

[Bug Janitor Service]

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

--- Comment #6 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[krusader] [Bug 346011] (BUG) Using F3/F4 in search results overwrites clipboard (when searching with "Containing text") with the text you searched for

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[plasmashell] [Bug 410179] Plasma shell killed by OOM killer after few seconds of running

[Bug Janitor Service]

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

--- Comment #6 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[frameworks-kio] [Bug 410263] Dolphin just crashed out of the blue

[Bug Janitor Service]

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

--- Comment #6 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[krusader] [Bug 314390] Krusader crashed while synchronizing two folders.

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #3 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[frameworks-ktexteditor] [Bug 363013] Automatic brackets does not add a closing }

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

[Michael A Borders]

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

Michael A Borders  changed:

   What|Removed |Added

 CC||michael.a.bord...@gmail.com

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

[kalarm] [Bug 410834] Excessive Akonadi CPU and storage use

[BryanFRitt]

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

--- Comment #1 from BryanFRitt  ---
Ops... I meant /usr/bin/akonadi_control was the one using CPU... 'End Process'
this, and no more of those files will be created.

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

[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app

[Yaohan Chen]

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

Yaohan Chen  changed:

   What|Removed |Added

 CC||yaohan.c...@gmail.com

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

[Falkon] [Bug 410835] New: FALKON_PLUGIN_PATH is not actually treated as a search path

[Alexei Robyn]

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

Bug ID: 410835
   Summary: FALKON_PLUGIN_PATH is not actually treated as a search
path
   Product: Falkon
   Version: 3.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: bugs@shados.net
  Target Milestone: ---

Contrary to its description in CMakeLists.txt, FALKON_PLUGIN_PATH is not
actually treated as a search path of directories to load plugins from, but
instead as the single directory to load plugins from (if it is set).

>From a brief look through the code, it appears that it is written to account
for multiple plugin directories, but that src/lib/app/datapaths.cpp assumes
that the environment variable contains a single directory path when reading it,
rather than assuming it contains a delimiter-separated list of directory paths.

I would suggest changing it to parse FALKON_PLUGIN_PATH as a list of
directories, separated by ':' characters (which would be in line with $PATH, as
well as $MOZ_PLUGIN_PATH in Firefox).

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

[kalarm] [Bug 410834] New: Excessive Akonadi CPU and storage use

[BryanFRitt]

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

Bug ID: 410834
   Summary: Excessive Akonadi CPU and storage use
   Product: kalarm
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Akonadi
  Assignee: djar...@kde.org
  Reporter: bryanfr...@hotmail.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE ?
0. Upgrade Debian from Stretch(9) to Buster(10)
1. Start KAlarm
2. Let /usr/bin/akonadi_ical_resource run without killing it

OBSERVED RESULT
~/.local/share/akonadi_ical_resource_3/ will get filled up with bunches of
calendar.ics- wasting storage space (identical size..., different ...)
while /usr/bin/akonadi_ical_resource consumes lots of CPU 

EXPECTED RESULT
not lots of CPU used, not lots of files made

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
A semi work around seams to be: 
end process akonadi/Kalarm
delete the files
set the directory to read only
restart KAlarm ...
CONS related to workaround? editing creates new alarm instead of editing

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

[bugs.kde.org] [Bug 410284] Terminology used on bugs.kde.org repeatedly refers to "bugs" in the context of non-bugs (e.g. feature requests, wishlist items, proposed improvements)

[Filipus Klutiero]

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

--- Comment #6 from Filipus Klutiero  ---
(In reply to Nate Graham from comment #4)
> There's a certain amount of this that's not really resolvable, and people
> will just need to interpret things accordingly.


Can you clarify which amount or which part is not really resolvable?

> [...]

Could you explain your latest changes to this ticket? Do you want the part
about community.kde.org to be tracked in a different ticket?

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

[bugs.kde.org] [Bug 410284] Terminology used on bugs.kde.org repeatedly refers to "bugs" in the context of non-bugs (e.g. feature requests, wishlist items, proposed improvements)

[Filipus Klutiero]

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

--- Comment #5 from Filipus Klutiero  ---
This also needs changing the Importance field's name from current "Severity" to
"Importance", when filing a ticket.

Also, this may exceed this ticket's scope, but either the default value for
Severity should be undetermined, or there should be none.

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

[frameworks-plasma] [Bug 376658] Customized tabbox does not work and makes kwin stuck and slow

[Xu Zhao]

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

Xu Zhao  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #2 from Xu Zhao  ---
Fixed on Plasma 5.16.4

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

[Powerdevil] [Bug 410799] Screen poweroff does not poweroff external monitors, only laptop display

[Tim Richardson]

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

--- Comment #5 from Tim Richardson  ---
(continued: because the only backlight that my computer can control is the
laptop's own backlight, not the backlights of the two external monitors, hence
'dim' only takes effect on the laptop panel. Dim should problem do something
more macos-like, and dim backlight to a non-zero setting.)

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

[bugs.kde.org] [Bug 410831] Please automatically link on a ticket mention in the form "ticket #123456"

[Filipus Klutiero]

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

Filipus Klutiero  changed:

   What|Removed |Added

  Component|general |general
Product|kde |bugs.kde.org
 CC||she...@kde.org
   Assignee|unassigned-b...@kde.org |sysad...@kde.org

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

[bugs.kde.org] [Bug 410832] Please automatically link on a ticket mention in the form "issue [report] [#]123456"

[Filipus Klutiero]

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

Filipus Klutiero  changed:

   What|Removed |Added

  Component|general |general
   Assignee|unassigned-b...@kde.org |sysad...@kde.org
 CC||she...@kde.org
Product|kde |bugs.kde.org

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

[Powerdevil] [Bug 410799] Screen poweroff does not poweroff external monitors, only laptop display

[Tim Richardson]

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

--- Comment #4 from Tim Richardson  ---
I think  I may have confused myself about something.The automatic dim option
actually fades the display backlight to completely off. This may give the
illusion that only one display is being powered off.

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

[bugs.kde.org] [Bug 409930] Please automatically link to clear mentions of a given ticket ("ticket #12345")

[Filipus Klutiero]

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

--- Comment #9 from Filipus Klutiero  ---
This ticket's status should be set to CLOSED MOVED, but as reported in ticket
#410833, I cannot change it at this time.

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

[bugs.kde.org] [Bug 410833] New: Changing ticket resolution from "RESOLVED NOT A BUG" to MOVED fails

[Filipus Klutiero]

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

Bug ID: 410833
   Summary: Changing ticket resolution from "RESOLVED NOT A BUG"
to MOVED fails
   Product: bugs.kde.org
   Version: unspecified
  Platform: Other
   URL: https://bugs.kde.org/show_bug.cgi?id=409930
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sysad...@kde.org
  Reporter: chea...@gmail.com
CC: she...@kde.org
  Target Milestone: ---

If I try fixing ticket #409930's status, by setting the Status fields to CLOSED
MOVED, the attempt fails with the following error message when I use "Save
Changes":
You tried to change the Resolution field from INVALID to MOVED, but only the
assignee or reporter of the bug, or a user with the required permissions may
change that field.

I suppose "Resolution" refers to the status, "INVALID" comes from the "NOT A
BUG" value, and "the bug" refers to the issue. However, I am the issue's
reporter.

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

[bugs.kde.org] [Bug 328622] 'RESOLVED UPSTREAM' ticket status undocumented

[Filipus Klutiero]

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

Filipus Klutiero  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||chea...@gmail.com
Summary|No documentation for|'RESOLVED UPSTREAM' ticket
   |'RESOLVED UPSTREAM' bug |status undocumented
   |status  |

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

[neon] [Bug 410779] Slow or unreliable downloads of KDE Neon release images and lack of adoption of Metalink

[Harald Sitter]

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

--- Comment #2 from Harald Sitter  ---
Stellar work! This looks like a really smart solution.

Before we can do anything you'll need to make your code free software though.
We have a wiki page going into great detail on the matter [1], what you want to
do is a pick a license an stick a license header into your source file.

https://community.kde.org/Policies/Licensing_Policy

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

[bugs.kde.org] [Bug 409930] Please automatically link to clear mentions of a given ticket ("ticket #12345")

[Filipus Klutiero]

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

--- Comment #8 from Filipus Klutiero  ---
Per comment #7, following ticket #410284's comment #1, I filed 2 separate
tickets to replace this one:
Please automatically link on a ticket mention in the form "ticket #123456":
https://bugs.kde.org/show_bug.cgi?id=410831
Please automatically link on a ticket mention in the form "issue [report]
[#]123456": https://bugs.kde.org/show_bug.cgi?id=410832

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

[kwin] [Bug 342582] Intel hd 4600 + OpenGL + kwin = can't load

[Roman Gilg]

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

Roman Gilg  changed:

   What|Removed |Added

 CC||subd...@gmail.com

--- Comment #33 from Roman Gilg  ---
As a heads-up I maybe will enabling it again by default. On two systems I have,
AMD and Intel, the extension is present and KWin works with the env var set
fine.

>From how I understand it we lose quite a lot of robustness by not syncing with
the X present complete notify on vblank through this extension.

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

[kde] [Bug 410831] Please automatically link on a ticket mention in the form "ticket #123456"

[Filipus Klutiero]

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

Filipus Klutiero  changed:

   What|Removed |Added

Summary|Please automatically link   |Please automatically link
   |to mentions of a given  |on a ticket mention in the
   |ticket in the form "ticket  |form "ticket #123456"
   |#123456"|

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

[kde] [Bug 410832] Please automatically link on a ticket mention in the form "issue [report] [#]123456"

[Filipus Klutiero]

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

Filipus Klutiero  changed:

   What|Removed |Added

Summary|Please automatically link   |Please automatically link
   |to mentions of a given  |on a ticket mention in the
   |ticket in the form "issue   |form "issue [report]
   |[report] [#]123456" |[#]123456"

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

[bugs.kde.org] [Bug 409930] Please automatically link to clear mentions of a given ticket ("ticket #12345")

[Filipus Klutiero]

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

Filipus Klutiero  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=410832

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

[kde] [Bug 410831] Please automatically link to mentions of a given ticket in the form "ticket #123456"

[Filipus Klutiero]

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

Filipus Klutiero  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=410832

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

[kde] [Bug 410832] New: Please automatically link to mentions of a given ticket in the form "issue [report] [#]123456"

[Filipus Klutiero]

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

Bug ID: 410832
   Summary: Please automatically link to mentions of a given
ticket in the form "issue [report] [#]123456"
   Product: kde
   Version: unspecified
  Platform: Other
   URL: https://bugs.kde.org/show_bug.cgi?id=409912
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: chea...@gmail.com
  Target Milestone: ---

I am filing this ticket despite https://bugs.kde.org/show_bug.cgi?id=410284
with the assumption that its comment #1 is correct.

I put this ticket in the "general" component, but I suppose nothing prevents
addressing this with a code customization... please feel free to change the
component as you wish.

As discussed in https://bugs.kde.org/show_bug.cgi?id=409930 it would be very
handy if, when a description or comment referred to a ticket using phrasing
with low ambiguity like "issue #123456" or "issue report 123456", that this
text be automatically made a link to the ticket mentioned
(https://bugs.kde.org/show_bug.cgi?id=123456).

This already works for bugs, as can be seen in ticket #409930 comment #2, but
only when using the misleading form "bug #123456", and not for other issues or
when using general terminology, as ticket #409912's Description and comment #1
show.

Sometimes, a ticket may report several issues, or sub-issues. A description may
therefore list a number of issues, as in the following:
1. "Issue #123456" is not supported.
2. "Issue report #123456" is not supported.

Such a ticket may later refer to these "sub-issues" as "issue #1" (or "issue
#2"), which does not designate https://bugs.kde.org/show_bug.cgi?id=1, but
rather the first "sub-issue" reported in the current ticket.

To prevent generation of bogus links in such cases, it would be best to:
A. require at least 2 digits in the ticket number
B. or/and provide a syntax to disable automatic linking, such as
"~no-parse~issue #1~/no-parse~".

A KDE ticket may also refer to an issue in non-KDE software, for example the
X.org issue which has ticket number 12345. To prevent a sentence which contains
something like "this is blocked by X.org issue #12345" from generating a bogus
link to KDE's ticket #12345, a syntax to disable automatic linking like the one
just discussed (in point B) could be provided.

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

[i18n] [Bug 410826] Traducción de dos cadenas de texto en Krusader

[bugzilla_noreply]

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

--- Comment #2 from 20l8kxxl8...@opayq.com ---
Hint: Since this is a bug regarding the translated strings, if you do not get a
reply after a while, you may want to send an email to the last translator of
Krusader (you can find more information in [1]).

[1]
https://websvn.kde.org/trunk/l10n-kf5/es/messages/extragear-utils/krusader.po?view=markup

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

[Powerdevil] [Bug 410799] Screen poweroff does not poweroff external monitors, only laptop display

[Tim Richardson]

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

--- Comment #3 from Tim Richardson  ---
While I definitely observed the behaviour in my comment (only one screen
powerered off), I tested it again today, first then "Even when external monitor
is connected" checked. As expected, all monitors turned off. I think cleared
the button, and repeated (I definitely Applied the setting change) but all
monitors again turned off.

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

[bugs.kde.org] [Bug 409930] Please automatically link to clear mentions of a given ticket ("ticket #12345")

[Filipus Klutiero]

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

Filipus Klutiero  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=410831

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

[kde] [Bug 410831] New: Please automatically link to mentions of a given ticket in the form "ticket #123456"

[Filipus Klutiero]

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

Bug ID: 410831
   Summary: Please automatically link to mentions of a given
ticket in the form "ticket #123456"
   Product: kde
   Version: unspecified
  Platform: Other
OS: All
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: chea...@gmail.com
  Target Milestone: ---

I am filing this ticket despite https://bugs.kde.org/show_bug.cgi?id=410284
with the assumption that its comment #1 is correct.

I put this ticket in the "general" component, but I suppose nothing prevents
addressing this with a code customization... please feel free to change the
component as you wish.

As discussed in https://bugs.kde.org/show_bug.cgi?id=409930 it would be very
handy if, when a description or comment referred to a ticket using phrasing
like "ticket #123456", that this text be automatically made a link to the
ticket mentioned (https://bugs.kde.org/show_bug.cgi?id=123456).

This already works for bugs, as can be seen in ticket #409930 comment #2, but
only when using the misleading form "bug #123456", and not for tickets, as
ticket #409913's comment #1 shows.

As ticket #409930 comment #1 implies, KDE has 2 ticketing systems, bugs.kde.org
and https://phabricator.kde.org/maniphest/
The latter has for some time used the term "ticket" to refer to any of its
entries, as can be seen on https://community.kde.org/Sysadmin
Therefore, referring to a KDE ticket by its number could be ambiguous.

Thankfully, that system now refers to its entries as "tasks", with identifiers
of the form "Td+" (for example, "T341"). I therefore recommend that references
like "ticket 123456" are not automatically linked, only those with a hash,
distinguishing between "ticket #123456" and "ticket T123456".

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

[dolphin] [Bug 407979] Keyboard input focus lost after closing terminal panel

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

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

[plasma-pa] [Bug 404387] Allow to set a maximum volume less than 100%

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
   Version Fixed In||5.17.0
  Latest Commit||https://commits.kde.org/pla
   ||sma-pa/faef1e8f152e4ad3fcb0
   ||3b1ff92c350dda0904fc
 Resolution|--- |FIXED

--- Comment #2 from Nate Graham  ---
Git commit faef1e8f152e4ad3fcb03b1ff92c350dda0904fc by Nate Graham, on behalf
of Kishore Gopalakrishnan.
Committed on 11/08/2019 at 22:33.
Pushed by ngraham into branch 'master'.

Allow to set maximum volume < 100%

Summary:
Currently one cannot set the maximum volume < 100%. This feature is required
because some earphones / speakers are more sensitive than others and may get
damaged at high volumes. In particular, one easily ends up overshooting safe
volume levels when using the mouse scroll wheel to change the volume. After
this change, one can safely use the mouse wheel to change volume.
FIXED-IN: 5.17.0

Test Plan:
1. Right-click on applet > 'Configure audio volume'.
2. Try to set maximum volume < 100% and click 'OK'.
3. Scroill on the systray icon to change maximum volume. Check if it is limited
to the configured maximum.

Reviewers: #plasma, drosca, ngraham, romangg

Reviewed By: #plasma, ngraham, romangg

Subscribers: romangg, ngraham, plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D23082

M  +1-1applet/contents/ui/ConfigGeneral.qml

https://commits.kde.org/plasma-pa/faef1e8f152e4ad3fcb03b1ff92c350dda0904fc

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

[amarok] [Bug 140676] Command line option --pause incorrectly acts just like --play-pause

[Nicole]

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

Nicole  changed:

   What|Removed |Added

 CC||nicole.sim...@gmail.com

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

[krita] [Bug 410830] New: play/pause button behaves like a play/stop button

[Nicole]

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

Bug ID: 410830
   Summary: play/pause button behaves like a play/stop button
   Product: krita
   Version: 4.2.5
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: nicole.sim...@gmail.com
  Target Milestone: ---

SUMMARY
the timing header starts from the beginning of the timeline when hitting
play/pause. when pausing an animation by clicking on the play/stop button, it
starts at the beginning instead of pausing on the currnt frame.

EXPECTED RESULT
when clicking the play/stop button, the timing header should stop on the currnt
frame.

please fix this. it's been reported back in 2017-02-24 11:25:54 UTC and hasn't
been fixed and updated since.

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

[krita] [Bug 410797] Krita will occasionally stop receiving input events.

[wolthera]

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

--- Comment #2 from wolthera  ---
Created attachment 122073
  --> https://bugs.kde.org/attachment.cgi?id=122073=edit
The diff of the debug that dmitry added to my build.

Adding the diff of the debug that dmitry added to my build.

It's bizarre that only one of the functions seems to be put out?

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

[krita] [Bug 410797] Krita will occasionally stop receiving input events.

[wolthera]

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

--- Comment #1 from wolthera  ---
Another one:

wolthera@Euthenia:~/krita/build$ gdb krita
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from krita...done.
(gdb) run
Starting program: /home/wolthera/krita/inst/bin/krita 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd3c6a700 (LWP 31202)]
[New Thread 0x7fffcf789700 (LWP 31203)]
[Thread 0x7fffd3c6a700 (LWP 31202) exited]
[Thread 0x7fffcf789700 (LWP 31203) exited]
[New Thread 0x7fffcf789700 (LWP 31206)]
[New Thread 0x7fffd3c6a700 (LWP 31210)]
[Thread 0x7fffcf789700 (LWP 31206) exited]
[Thread 0x7fffd3c6a700 (LWP 31210) exited]
[New Thread 0x7fffd3c6a700 (LWP 31211)]
[New Thread 0x7fffcf789700 (LWP 31212)]
[Thread 0x7fffd3c6a700 (LWP 31211) exited]
[Thread 0x7fffcf789700 (LWP 31212) exited]
[New Thread 0x7fffcf789700 (LWP 31213)]
[New Thread 0x7fffd3c6a700 (LWP 31218)]
[New Thread 0x7fffc4ebc700 (LWP 31219)]
Set style "fusion"
KoColor debug runtime checks are active.
krita.lib.pigment: Illegal XML palette:
"/home/wolthera/.local/share/krita/palettes/colorset.xml"
krita.lib.pigment: Error (line 1 , column 159 ): "Unknown XML palette format.
Expected SCRIBUSCOLORS, found Colorset"
krita.lib.widgets: Loading resource 
"/home/wolthera/.local/share/krita/palettes/colorset.xml" failed. "ko_palettes"
krita.lib.pigment: Illegal XML palette:
"/home/wolthera/.local/share/krita/palettes/profiles.xml"
krita.lib.pigment: Error (line 1 , column 10 ): "Unknown XML palette format.
Expected SCRIBUSCOLORS, found Profiles"
krita.lib.widgets: Loading resource 
"/home/wolthera/.local/share/krita/palettes/profiles.xml" failed. "ko_palettes"
[New Thread 0x7fff94e02700 (LWP 31504)]
QObject::startTimer: Timers cannot have negative intervals
[New Thread 0x7fff92bff700 (LWP 31510)]
[New Thread 0x7fff923fe700 (LWP 31511)]
[Thread 0x7fff92bff700 (LWP 31510) exited]
Comparators already registered for type KoSvgText::AutoValue
Debug stream operator already registered for type KoSvgText::AutoValue
Comparators already registered for type KoSvgText::BackgroundProperty
Debug stream operator already registered for type KoSvgText::BackgroundProperty
Comparators already registered for type KoSvgText::StrokeProperty
Debug stream operator already registered for type KoSvgText::StrokeProperty
/home/wolthera/krita/inst/lib/x86_64-linux-gnu/krita-python-libs/krita added to
PYTHONPATH
krita.scripting: "Traceback (most recent call last):"
krita.scripting: "  File
\"/home/wolthera/krita/inst/share/krita/pykrita/palette_docker/__init__.py\",
line 2, in "
krita.scripting: "from .palette_docker import *"
krita.scripting: "  File
\"/home/wolthera/krita/inst/share/krita/pykrita/palette_docker/palette_docker.py\",
line 31, in "
krita.scripting: "class Palette_Docker(DockWidget):"
krita.scripting: "  File
\"/home/wolthera/krita/inst/share/krita/pykrita/palette_docker/palette_docker.py\",
line 126, in Palette_Docker"
krita.scripting: "@pyqtSlot('KisSwatch')"
krita.scripting: "TypeError: C++ type 'KisSwatch' is not supported as a
pyqtSlot type argument type"
krita.scripting: "Could not import palette_docker"
krita.scripting: Error loading plugin "palette_docker"
[New Thread 0x7fff92bff700 (LWP 31680)]
[New Thread 0x7fff7d536700 (LWP 31689)]
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
Could not set current file 0 "Thumbnails/thumbnail.png"
[New Thread 0x7fffa82a8700 (LWP 31706)]
[New Thread 0x7fffa6fe7700 (LWP 31707)]
krita.core: Add node  KisPaintLayer(0x607000134e20, name = "Layer 1")  to 
KisGroupLayer(0x606001efe720, name = "root")
[New Thread 0x7fff7c532700 (LWP 31787)]
[New Thread 0x7fff7bd31700 (LWP 31788)]
[New Thread 0x7fff7b530700 (LWP 31789)]
[New Thread 0x7fff7ad2f700 (LWP 31790)]
[New Thread 0x7fff7a52e700 (LWP 31791)]
[New Thread 0x7fff79d2d700 (LWP 31792)]
[New Thread 0x7fff7952c700 (LWP 31793)]
[New Thread 0x7fff78d2b700 (LWP 31794)]
[Thread 0x7fff7a52e700 (LWP 31791) exited]
[Thread 0x7fff7bd31700 (LWP 31788) exited]
[Thread 0x7fff7952c700 (LWP 31793) exited]
[Thread 0x7fff7ad2f700 (LWP 31790) exited]
[Thread 0x7fff78d2b700 (LWP 31794) exited]
[Thread 0x7fff79d2d700 (LWP 

[systemsettings] [Bug 410506] "Run in Terminal" and "Terminal=true" ignored for default email client

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |major
   Keywords||usability
 Status|REPORTED|CONFIRMED
Summary|Setting Email Client to |"Run in Terminal" and
   |mutt doesn't run mutt in a  |"Terminal=true" ignored for
   |terminal|default email client
 Ever confirmed|0   |1

--- Comment #3 from Nate Graham  ---
Darn. Confirmed.

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

[systemsettings] [Bug 410506] Setting Email Client to mutt doesn't run mutt in a terminal

[Matti Klock]

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

--- Comment #2 from Matti Klock  ---
Yes.

It's also ignoring "Terminal=true" in the .desktop file.  Setting a shortcut in
"Global Shortcuts" for mutt.desktop didn't work either until I edited it as
above.

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

[digikam] [Bug 399923] Segmentation fault during face detection

[bugzilla_noreply]

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

--- Comment #169 from timo...@zoho.com ---
> Which Linux version do you use exactly? I could not determine it in the 
> thread.

It's in the first post: NixOS. Or do you mean the actual linux kernel version?
That would be 4.19.65.

> For me, it looks like the loading task is being killed from "outside"...

How could that happen? Its a segfault after all, not a reaction to a SIGKILL or
something. Also remember that the same issue occurs with the snap, which
probably rules out some external factors. Though I agree that a
hardware-related failure doesn't seem much more likely. We do have some people
in the CC list, not sure if they're seeing the same error.

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

[krita] [Bug 410829] [krita-sprint-2019 bug/discussions] Annoying autosave on-canvas notifications while in canvas-only mode

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||b...@valdyas.org
 Ever confirmed|0   |1

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

[krita] [Bug 410829] New: [krita-sprint-2019 bug/discussions] Annoying autosave on-canvas notifications while in canvas-only mode

[David REVOY]

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

Bug ID: 410829
   Summary: [krita-sprint-2019 bug/discussions] Annoying autosave
on-canvas notifications while in canvas-only mode
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: i...@davidrevoy.com
  Target Milestone: ---

Hi,

When switching the autosave to a short period of time (eg. 2min) and using the
"canvas-only mode" with , the on-canvas notification starts to be annoying
(because long, blinking and repetitive). It is indeed two notifications: one
telling that the autosaving is in progress and a second one immediately after
reporting everything was saved and display the filename. (and sometime one
telling autosave is post-poned while painting)

While I understand this informations might be useful (I learned during the
meeting they come from a request) the notifications could be a bit more little,
compact and short; maybe smaller and less text or icons?

I'm open to any proposal to enhance this in the future to enjoy more painting
in canvas-only mode while keeping security of frequent autosaves (especially
for beta-testers). Thank you!

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

[plasmashell] [Bug 410828] New: [plasmashell][kdeinit5] Sometimes a KDE component prevents the system from going to sleep

[bugzilla_noreply]

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

Bug ID: 410828
   Summary: [plasmashell][kdeinit5] Sometimes a KDE component
prevents the system from going to sleep
   Product: plasmashell
   Version: 5.16.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: temptem...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

It so happens that sometimes, mainly when resuming firstly from a sleep
session, the computer will refuse to go into sleep when a suspend operation is
issued anew.

The computer freezes for a moment, then gives back control.


STEPS TO REPRODUCE (This doesn't happen consistently)
1. Put the computer in sleep mode
2. Wake the computer up
3. Ask immediately or after 1-2 minutes the system to sleep again
4. Witness the phenomenon



OBSERVED RESULT
The computer freezes for a moment, then gives back control, having failed
entering sleep mode

EXPECTED RESULT
The computer should be able to go back to sleep immediately. This works
flawlessly on Windows on the same machine.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.2.5-zen1-1-zen #1 ZEN SMP PREEMPT

KDE Plasma Version: 5.16.4-1
KDE Frameworks Version: 5.60
Qt Version: 5.13.0

ADDITIONAL INFORMATION


[lun. août  5 17:46:17 2019] PM: suspend entry (deep)
[lun. août  5 17:46:17 2019] Filesystems sync: 0.180 seconds
[lun. août  5 17:46:17 2019] Freezing user space processes ... 
[lun. août  5 17:46:37 2019] Freezing of tasks failed after 20.003 seconds (1
tasks refusing to freeze, wq_busy=0):
[lun. août  5 17:46:37 2019] file.so D0  >7838   1333
0x4084
[lun. août  5 17:46:37 2019] Call Trace:
[lun. août  5 17:46:37 2019]  ? __schedule+0x27f/0x710
[lun. août  5 17:46:37 2019]  ? request_wait_answer+0x12a/0x270 [fuse]
[lun. août  5 17:46:37 2019]  schedule+0x8c/0x220
[lun. août  5 17:46:37 2019]  request_wait_answer+0x12a/0x270 [fuse]
[lun. août  5 17:46:37 2019]  ? wait_woken+0x70/0x70
[lun. août  5 17:46:37 2019]  ? wait_woken+0x70/0x70
[lun. août  5 17:46:37 2019]  fuse_simple_request+0x228/0x290 [fuse]
[lun. août  5 17:46:37 2019]  fuse_dentry_revalidate+0x1b5/0x390 [fuse]
[lun. août  5 17:46:37 2019]  ? __switch_to_asm+0x34/0x70
[lun. août  5 17:46:37 2019]  ? __switch_to_asm+0x40/0x70
[lun. août  5 17:46:37 2019]  ? __switch_to_asm+0x34/0x70
[lun. août  5 17:46:37 2019]  ? __switch_to_asm+0x40/0x70
[lun. août  5 17:46:37 2019]  lookup_fast+0x280/0x320
[lun. août  5 17:46:37 2019]  path_lookupat.isra.0+0x159/0x610
[lun. août  5 17:46:37 2019]  filename_lookup+0xc2/0x1d0
[lun. août  5 17:46:37 2019]  vfs_statx+0xad/0x130
[lun. août  5 17:46:37 2019]  __se_sys_statx+0x5a/0xa0
[lun. août  5 17:46:37 2019]  do_syscall_64+0x5f/0x1d0
[lun. août  5 17:46:37 2019]  ? page_fault+0x8/0x30
[lun. août  5 17:46:37 2019]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[lun. août  5 17:46:37 2019] RIP: 0033:0x7f54701c6894
[lun. août  5 17:46:37 2019] Code: Bad RIP value.
[lun. août  5 17:46:37 2019] RSP: 002b:7fffe08ec2d0 EFLAGS: 0246
ORIG_RAX: 014c
[lun. août  5 17:46:37 2019] RAX: ffda RBX: 558b958548b0 RCX:
7f54701c6894
[lun. août  5 17:46:37 2019] RDX:  RSI: 558b9585a4d8 RDI:
ff9c
[lun. août  5 17:46:37 2019] RBP: 7fffe08ec3c0 R08: 7fffe08ec3c0 R09:
ff9c
[lun. août  5 17:46:37 2019] R10: 0fff R11: 0246 R12:
558b9585a4d8
[lun. août  5 17:46:37 2019] R13: 72a67077 R14: 7fffe08ec3b0 R15:
558b95854898
[lun. août  5 17:46:37 2019] OOM killer enabled.
[lun. août  5 17:46:37 2019] Restarting tasks ... done.
[lun. août  5 17:46:37 2019] PM: suspend exit

Upon investigating kernel's OoM reported culprit PID:

$ps aux | grep -i 7838
7838  0.0  0.0 109760 17016 ?Daoût09   0:00 file.so 
[kdeinit5] file local:/run/user/1000/klauncherquTPQa.1.slave-socket 
local:/run/user/1000/kded5zUkbGw.41.slave-socket

With regards,
Thanks for your work.

Darkeox099

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

[kwin] [Bug 410827] New: Neither KWinscript nor wmctrl show all the windows on Wayland

[Xu Zhao]

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

Bug ID: 410827
   Summary: Neither KWinscript nor wmctrl show all the windows on
Wayland
   Product: kwin
   Version: 5.16.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: platform-wayland
  Assignee: kwin-bugs-n...@kde.org
  Reporter: i...@xuzhao.net
  Target Milestone: ---

Created attachment 122072
  --> https://bugs.kde.org/attachment.cgi?id=122072=edit
Only one window being recognized by the kwinscript

SUMMARY

Neither KWinscript nor wmctrl correctly show all the open windows on KWin
Wayland.

STEPS TO REPRODUCE
1. Open a few applications in KWin 5.16.4: Firefox, Emacs, Alacritty, Okular
2. Run "wmctrl -l" or the following KWinscript:
var clist = workspace.clientList();
print(clist.length);
for(var i = 0; i < clist.length; i ++) {
print(clist[i]);
}
3. Should print all the windows, but only one of them got printed. See
screenshot: https://ibb.co/YpFF7xG

OBSERVED RESULT

Only one window got printed

EXPECTED RESULT

All the windows are printed with their names.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux 5.2.0 , openSUSE Tumbleweed latest
(available in About System)
KDE Plasma Version: Plasma 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version:  5.13.0

ADDITIONAL INFORMATION
See the attachment

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

[i18n] [Bug 410826] Traducción de dos cadenas de texto en Krusader

[Toni Asensi Esteve]

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

--- Comment #1 from Toni Asensi Esteve  ---
P.D. Como en el menú de Krusader ya existe «Herramientas > Gestor de
montaje...» ¿tal vez sea mejor usar siempre "Gestionar acciones de usuario" en
vez de usar a veces esa palabra y a veces "Administrar acciones de usuario"?

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

[i18n] [Bug 410826] New: Traducción de dos cadenas de texto en Krusader

[Toni Asensi Esteve]

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

Bug ID: 410826
   Summary: Traducción de dos cadenas de texto en Krusader
   Product: i18n
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: es
  Assignee: kde-l10n...@kde.org
  Reporter: toni.ase...@kdemail.net
  Target Milestone: ---

Hola, soy Toni Asensi Esteve, uno de los desarrolladores de Krusader.

Parece que haya algún problema con dos cadenas de texto en Krusader y es mejor
verlo ahora (como dijeron en kde-i18n-...@kde.org: "Krusader stable branch is
now in the string and doc freeze mode. We plan to release v2.7.2 on
2019-08-25.").

La traducción del texto de la casilla "Query to clipboard" (que se puede ver en
el diálogo de búsqueda, tras pulsar en Ctrl+S) no sería "Consultar el
portapapeles" (ya que no se saca información del portapapeles sino que, por el
contrario, se añade información al portapapeles) sino ¿un texto como "Criterio
al portapapeles"?

Nota: Se puede consultar la «ayuda» de dicha casilla, que dice «Situar el texto
a buscar en el portapapeles cuando se abre un archivo encontrado».

En el menú "Acciones de usuario" de Krusader aparece un submenú "Gestionar
acciones de usuario..." parece que haya de ser ¿"Administrar acciones de
usuario", que es el título que aparece en la ventana que lanza dicho submenú?
(intentaríamos evitar el que los usuarios nuevos se liaran).

¡Y gracias por la traducción tan buena!

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

[krita] [Bug 410825] Safe ASSERT after doing a selection in the global selection mask and save

[vanyossi]

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

--- Comment #1 from vanyossi  ---
Popup message text

Krita has encountered an internal error:

SAFE ASSERT (krita): "clonedDocument->image()->isIdle()" in file
/Users/boud/dev/ivanbuild/krita-4.2.5/libs/ui/KisDocument.cpp, line 842

Please report a bug to developers!

Press Ignore to try to continue.
Press Abort to see developers information (all unsaved data will be lost)

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

[krita] [Bug 410825] New: Safe ASSERT after doing a selection in the global selection mask and save

[vanyossi]

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

Bug ID: 410825
   Summary: Safe ASSERT after doing a selection in the global
selection mask and save
   Product: krita
   Version: 4.2.5
  Platform: Other
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools/Selection
  Assignee: krita-bugs-n...@kde.org
  Reporter: ghe...@gmail.com
  Target Milestone: ---

Created attachment 122071
  --> https://bugs.kde.org/attachment.cgi?id=122071=edit
backtrace

If trying to save after making a selection with a global selection active and
the global selection layer as selected, a safe assert is thrown. on 4.2.5 there
is a crash after the safe assert popup


STEPS TO REPRODUCE
1. Set global selection ON
2. Make selection
3. Select global selection layer
4. Make selection again
5. Save

It may be needed to repeat 4 and 5 while the global selection layer is selected
for it to trigger. (HIDEN_SAFE_ASSERT must be off to be seen). On macos it will
eventually crash apparently.


SOFTWARE/OS VERSIONS
macOS: 10.14.6

ADDITIONAL INFORMATION

SESSION: 11 Aug 2019 17:59:05 +0200. Executing
/Volumes/Osiris/programs/krita-master/i/bin/krita.app/Contents/MacOS/krita

WARNING: This file contains information about your system and the
images you have been working with.

If you have problems with Krita, the Krita developers might ask
you to share this file with them. The information in this file is
not shared automatically with the Krita developers in any way. You
can disable logging to this file in Krita's Configure Krita Dialog.

Please review the contents of this file before sharing this file with
anyone.

Krita

 Version: 4.3.0-prealpha (git 31b1f9f)
 Languages: es
 Hidpi: true

Qt

  Version (compiled): 5.12.3
  Version (loaded): 5.12.3

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: darwin
  Kernel Version: 18.7.0
  Pretty Productname: macOS Mojave (10.14)
  Product Type: osx
  Product Version: 10.14


Hardware Information

  GPU Acceleration: desktop
  Memory: 8192 Mb
  Number of Cores: 4
  Swap Location: /Users/daedalus

11 Aug 2019 18:00:17 +0200: Importing application/x-krita to
application/x-krita. Location:
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra. Real location:
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra. Batchmode: 0
11 Aug 2019 18:00:18 +0200: Instant Preview Setting: 0
11 Aug 2019 18:00:18 +0200: Enabled simple smoothing.
11 Aug 2019 18:00:18 +0200: Enabled simple smoothing.
11 Aug 2019 18:00:18 +0200: Enabled simple smoothing.
11 Aug 2019 18:00:18 +0200: Enabled simple smoothing.
11 Aug 2019 18:00:18 +0200: Enabled simple smoothing.
11 Aug 2019 18:00:18 +0200: Enabled simple smoothing.
11 Aug 2019 18:00:18 +0200: Instant Preview Setting: 0
11 Aug 2019 18:00:19 +0200: Instant Preview Setting: 0
11 Aug 2019 18:00:37 +0200: Saving Document
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra as
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra (mime:
application/x-krita). 2048 * 2048 pixels, 4 layers.  101 frames, 24 framerate.
Export configuration: No configuration
11 Aug 2019 18:00:37 +0200: Converting from application/x-krita to
application/x-krita. Location:
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra. Real location:
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra. Batchmode: 0.
Configuration: none
11 Aug 2019 18:00:38 +0200: Completed saving
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra (mime:
application/x-krita). Result: OK
11 Aug 2019 18:03:32 +0200: Saving Document
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra as
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra (mime:
application/x-krita). 2048 * 2048 pixels, 4 layers.  101 frames, 24 framerate.
Export configuration: No configuration
11 Aug 2019 18:03:33 +0200: SAFE ASSERT (krita):
"clonedDocument->image()->isIdle()" in file
/Volumes/Osiris/programs/krita-master/krita/libs/ui/KisDocument.cpp, line 952
11 Aug 2019 18:09:47 +0200: SAFE ASSERT (krita): "QThread::currentThread() ==
(static_cast(QCoreApplication::instance()))->thread()" in file
/Volumes/Osiris/programs/krita-master/krita/libs/ui/flake/kis_shape_selection.cpp,
line 118
11 Aug 2019 18:09:57 +0200: SAFE ASSERT (krita): "QThread::currentThread() ==
(static_cast(QCoreApplication::instance()))->thread()" in file
/Volumes/Osiris/programs/krita-master/krita/libs/ui/flake/kis_shape_selection.cpp,
line 118
11 Aug 2019 18:09:59 +0200: Converting from application/x-krita to
application/x-krita. Location:
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra. Real location:
/Volumes/Osiris/devs/bugreports/noUpdate_invertSel.kra. Batchmode: 0.
Configuration: none
11 Aug 2019 18:10:00 +0200: Completed saving

[krita] [Bug 410824] Pen barrel button + drag reverts back to selected tool with XP-Pen Artist 15.6

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 CC||b...@valdyas.org
 Status|REPORTED|RESOLVED

--- Comment #1 from Boudewijn Rempt  ---
Don't do that; set your pen button to middle click, and will pan automatically.
We cannot get xp-pen tablets to send usable events if it's set to space.

Note that we really do not recommend xp-pen; their drivers keep breaking and
they don't, apparently, test their hardware with Krita.

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

[Breeze] [Bug 392269] Audacity device toolbar squashed vertically with breeze

[petrk]

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

petrk  changed:

   What|Removed |Added

 Attachment #111596|0   |1
is obsolete||

--- Comment #6 from petrk  ---
Created attachment 122070
  --> https://bugs.kde.org/attachment.cgi?id=122070=edit
Current state, better but not perfect.

I'm not sure if 100% fixed, but it's much better now. I can finally revert to
distro provided package. Text is not being alligned to the left, which is more
logical.

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

[krita] [Bug 410824] New: Pen barrel button + drag reverts back to selected tool with XP-Pen Artist 15.6

[Cameron]

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

Bug ID: 410824
   Summary: Pen barrel button + drag reverts back to selected tool
with XP-Pen Artist 15.6
   Product: krita
   Version: 4.2.5
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: theban...@gmail.com
  Target Milestone: ---

SUMMARY
In previous drawing programs, I map the space bar to a button on the pen
barrel, so that holding the button activates the move tool and I can then
scroll by dragging on the screen, but I am having trouble making this work in
Krita.

STEPS TO REPRODUCE
1. Windows 10/Krita 4.2.5/XP-Pen Artist 15.6
2. Set either button on pen barrel to "space"
3. With any tool selected (most obvious with the brush tool), hold the pen
barrel button down
4. Attempt to scroll by dragging pen across screen

OBSERVED RESULT
While holding the pen barrel button, the cursor turns into the move tool icon,
as expected. However, upon dragging, the brush tool is activated again and it
just draws on the screen.

EXPECTED RESULT
The canvas should scroll, as if the space bar was held down. 

SOFTWARE/OS VERSIONS
Windows: Windows 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[BalooWidgets] [Bug 410823] New: baloo stopped working at start up

[Eion MacDonald]

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

Bug ID: 410823
   Summary: baloo stopped working at start up
   Product: BalooWidgets
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: stefan.bru...@rwth-aachen.de
  Reporter: eion...@btinternet.com
  Target Milestone: ---

Created attachment 122069
  --> https://bugs.kde.org/attachment.cgi?id=122069=edit
copy of error file

SUMMARY Baloo stopped working start up and an error  notification appeared


STEPS TO REPRODUCE
1. Unknown.
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  No openSUSE using XFCE DE
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Both XFCE (main DE) and KDE installed . XFCE used. Leap 15.1

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

[kmymoney] [Bug 410812] Raise minimum required version of AqBanking

[Thomas Baumgart]

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

Thomas Baumgart  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #1 from Thomas Baumgart  ---
The current 5.7.8 will still work until sometime in September as has been
reported by various users (also to GnuCash and other applications). To be on
the safe side we make sure to send the necessary information. The logic is only
provided by AqBanking >= 5.8.0, hence the update.

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

[kwin] [Bug 410822] New: Blur effect appears to blur slightly outside window borders

[bugzilla_noreply]

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

Bug ID: 410822
   Summary: Blur effect appears to blur slightly outside window
borders
   Product: kwin
   Version: 5.16.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-window-management
  Assignee: kwin-bugs-n...@kde.org
  Reporter: heroofg...@gmail.com
  Target Milestone: ---

Created attachment 122068
  --> https://bugs.kde.org/attachment.cgi?id=122068=edit
screenshot

SUMMARY
When the blur effect is enabled, it blurs the background along the edge of
windows. It's especially noticeable when using curved window decorations

STEPS TO REPRODUCE
Enable blur effect in Settings/Desktop Behavior/Desktop Effects

OBSERVED RESULT
Blurring appears slightly appears slightly outside the borders of windows. (It
seems slightly more visible on the left side.)

EXPECTED RESULT
Blurring should only appear inside the window

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.1.16-arch1-1-ARCH
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.59.0
Qt Version: 5.13.0

ADDITIONAL INFORMATION

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

[Breeze] [Bug 410821] Need crossed out plasma icon

[Kai Uwe Broulik]

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

--- Comment #2 from Kai Uwe Broulik  ---
16, instead of 12, obviously :/
16, 32, 48, 128.

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

[Breeze] [Bug 410821] Need crossed out plasma icon

[Kai Uwe Broulik]

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

--- Comment #1 from Kai Uwe Broulik  ---
I need it in sizes 12, 32, 48, 128 px, like
https://cgit.kde.org/plasma-browser-integration.git/plain/extension/icons/plasma-128.png
It doesn't have to be in upstream Breeze icons, just four PNGs for p-b-i should
be sufficient

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

[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards

[Andre Kovacs]

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

--- Comment #164 from Andre Kovacs  ---
Hi Rob,

The beauty of the scripting approach is that there's no need to change anything
in Ekos.
Just providing the script into the Contents directory of the app, and a
documentation of the configuration process, is sufficient.

Thanks,
Andre

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

[Breeze] [Bug 410821] New: Need crossed out plasma icon

[Kai Uwe Broulik]

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

Bug ID: 410821
   Summary: Need crossed out plasma icon
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: k...@privat.broulik.de
CC: kain...@gmail.com
  Target Milestone: ---

SUMMARY
For Plasma Browser Integration I need a crossed out Plasma icon, or one with a
diagonal bar, to denote that the extension isn't supported/enabled.

Basically those four Plasma icons [1] with a diagonal line through them.

[1] https://cgit.kde.org/plasma-browser-integration.git/tree/extension/icons

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

[digikam] [Bug 399923] Segmentation fault during face detection

[Maik Qualmann]

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

--- Comment #168 from Maik Qualmann  ---
Which Linux version do you use exactly? I could not determine it in the thread.
Since even Gilles with his Intel machine can not reproduce the problem and we
should have a lot more feedback on a problem in digiKam, I think the problem is
somewhere else. For me, it looks like the loading task is being killed from
"outside"...

Maik

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

[kdevelop] [Bug 410820] Crash when closing a document opened with Okteta plugin

[Friedrich W. H. Kossebau]

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

Friedrich W. H. Kossebau  changed:

   What|Removed |Added

  Latest Commit||https://invent.kde.org/kde/
   ||kdevelop/commit/4e0b20cd8b3
   ||6814527331a3e62513377304dd0
   ||5e
 Status|REPORTED|RESOLVED
   Version Fixed In||5.4.1
 Resolution|--- |FIXED

--- Comment #1 from Friedrich W. H. Kossebau  ---
Git commit 4e0b20cd8b36814527331a3e62513377304dd05e by Friedrich W. H.
Kossebau.
Committed on 11/08/2019 at 17:38.
Pushed by kossebau into branch '5.4'.

Fix crash: add missing Q_INTERFACES to OktetaDocument for IDocument

Some places rely on this being properly set due to using qobject_cast
for quick cross-casting.
FIXED-IN: 5.4.1

M  +1-0plugins/okteta/oktetadocument.h

https://invent.kde.org/kde/kdevelop/commit/4e0b20cd8b36814527331a3e62513377304dd05e

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

[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session

[Daniel]

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

Daniel  changed:

   What|Removed |Added

 CC||lui...@gmail.com

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

[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session

[Daniel]

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

--- Comment #21 from Daniel  ---
Created attachment 122067
  --> https://bugs.kde.org/attachment.cgi?id=122067=edit
New crash information added by DrKonqi

kate (18.08.0) using Qt 5.11.3

- What I was doing when the application crashed:
Passed mouse over scroll bar when activated the option "show text preview on
scroll bar" under Wayland 

- Custom settings of the application:
When is checked the option "show text preview on scroll bar"

-- Backtrace (Reduced):
#8  0x7fdd61c9db79 in
QApplicationPrivate::notifyActiveWindowChange(QWindow*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x7fdd616c5ce5 in
QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x7fdd616c5f1d in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x7fdd616a006b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
[...]
#13 0x7fdd6119a27b in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

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

[konqueror] [Bug 410811] !"The Requested Operation Could Not Be Completed - Undocumented Error" Unk error code 1327958384

[bugzilla_noreply]

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

--- Comment #1 from kde.0...@gishpuppy.com ---
After removing the web browser from favorites, which is where I initially
edited the name, I unlocked my desktop screen and re-opened it. It opened to
the Konqueror website, whereas before it used to open to the KDE.org homepage.
This time it did not display any error messages. After I renamed it back to
Konqueror initially, I opened it twice right after and I got the second error
message both times. It looks like the errors have stopped, but hopefully not to
many people want to change names on the start menu and other places like
myself.  At least I did not have to remove and reinstall Konqueror to fix those
errors.

As a side note, it would be nice to have an easy option to add a preferred name
to your icons. Windows and Mac OS both used shortcuts for a number of things,
including their menus. I may look into it to see if a similar option is being
used for the start menu in Q4OS and other Linux desktops. So far, I'm not sure
if I missed any option to do this without getting to technical, but it's only
my second day using this OS.

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

[digikam] [Bug 399923] Segmentation fault during face detection

[bugzilla_noreply]

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

--- Comment #167 from timo...@zoho.com ---
Unfortunately no luck with either approach :/

With b436cb9c0b04da9efff0bda66cf10b71271a1857:

> digikam.facesengine: Verifying face QRect(552,144 49x49) using cascade 8
> digikam.facesengine: feature QRectF(0.1,0.4 0.8x0.6) QRect(552,144 49x49) 
> QRect(557,164 39x29)
> digikam.facesengine: detectMultiScale: image size ( 39 , 29 ) searchIncrement 
> 1.1 grouping 2 flags 0 min size ( 5 , 5 )
> digikam.facesengine: detectMultiScale gave ()
> digikam.general: Found 0 faces in "IMG-20171231-WA0001.jpg" QSize(1280, 1105) 
> QSize(1280, 1105)
> digikam.facesengine: detectMultiScale: image size ( 800 , 599 ) 
> searchIncrement 1.1 grouping 3 flags 1 min size ( 26 , 26 )
> 
> Thread 30 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fff377fe700 (LWP 25666)]
> 0x76e8536b in std::__atomic_base::load 
> (__m=std::memory_order_relaxed, this=)
> at 
> /nix/store/wr5dlcw1asw8dwgm4bwjmga8f52m5lfx-gcc-7.4.0/include/c++/7.4.0/bits/atomic_base.h:396
> 396 return __atomic_load_n(&_M_i, __m);
> (gdb) bt
> #0  0x76e8536b in std::__atomic_base::load 
> (__m=std::memory_order_relaxed, this=) at 
> /nix/store/wr5dlcw1asw8dwgm4bwjmga8f52m5lfx-gcc-7.4.0/include/c++/7.4.0/bits/atomic_base.h:396
> #1  QAtomicOps::load (_q_value=...) at 
> /nix/store/hy0z060pmjwrdrbb0qrii7hnwif8cz1y-qtbase-5.12.0-dev/include/QtCore/qatomic_cxx11.h:227
> #2  QBasicAtomicInteger::load (this=) at 
> /nix/store/hy0z060pmjwrdrbb0qrii7hnwif8cz1y-qtbase-5.12.0-dev/include/QtCore/qbasicatomic.h:103
> #3  QtPrivate::RefCount::isShared (this=) at 
> /nix/store/hy0z060pmjwrdrbb0qrii7hnwif8cz1y-qtbase-5.12.0-dev/include/QtCore/qrefcount.h:101
> #4  QMap::detach (this=) at 
> /nix/store/hy0z060pmjwrdrbb0qrii7hnwif8cz1y-qtbase-5.12.0-dev/include/QtCore/qmap.h:364
> #5  QMap::insert (avalue=..., akey=..., this= out>) at 
> /nix/store/hy0z060pmjwrdrbb0qrii7hnwif8cz1y-qtbase-5.12.0-dev/include/QtCore/qmap.h:706
> #6  Digikam::DImg::setAttribute (this=0x2b41058, key=..., value=...) at 
> /home/timo/tmp/source/core/libs/dimg/dimg_props.cpp:207
> #7  0x76f592d2 in Digikam::LoadSaveThread::exifRotate (image=..., 
> filePath=...) at 
> /home/timo/tmp/source/core/libs/threadimageio/fileio/loadsavethread.cpp:336
> #8  0x76f41a61 in Digikam::PreviewLoadingTask::execute 
> (this=0x2b40e60) at 
> /home/timo/tmp/source/core/libs/threadimageio/preview/previewtask.cpp:298
> #9  0x76f5901e in Digikam::LoadSaveThread::run (this=0x2abfc40) at 
> /home/timo/tmp/source/core/libs/threadimageio/fileio/loadsavethread.cpp:133
> #10 0x76f7a28e in Digikam::DynamicThread::Private::run 
> (this=0x2ceb1d0) at 
> /home/timo/tmp/source/core/libs/threads/dynamicthread.cpp:183
> #11 0x7fffef3127d2 in ?? () from 
> /nix/store/683732s7dq6bxrl267lcadl5lvn6i4nh-qtbase-5.12.0/lib/libQt5Core.so.5
> #12 0x7fffef30e062 in ?? () from 
> /nix/store/683732s7dq6bxrl267lcadl5lvn6i4nh-qtbase-5.12.0/lib/libQt5Core.so.5
> #13 0x764e1ef7 in start_thread () from 
> /nix/store/iykxb0bmfjmi7s53kfg6pjbfpd8jmza6-glibc-2.27/lib/libpthread.so.0
> #14 0x7fffed6eb22f in clone () from 
> /nix/store/iykxb0bmfjmi7s53kfg6pjbfpd8jmza6-glibc-2.27/lib/libc.so.6

And with the new detection/recognition code (at
0b749b2623ee3b0b9561bf9a47178e8fbdbe8c55):

> String, "autodetectedFace"), QVariant(int, 281), QVariant(int, 281), 
> QVariant(QString, "tagRegion"))
> digikam.facedb: nnmodel:  "" , nndata  ""
> digikam.facesengine: cv::Exception: OpenCV(3.4.7) 
> /build/source/modules/dnn/src/caffe/caffe_io.cpp:1121: error: (-2:Unspecified 
> error
> ) FAILED: fs.is_open(). Can't open "" in function 'ReadProtoFromTextFile'
> 
> digikam.general: Found 0 faces in "IMG-20170907-WA0003.jpg" QSize(1280, 720) 
> QSize(1280, 720)
> digikam.facedb: nnmodel:  "" , nndata  ""
> digikam.facesengine: cv::Exception: OpenCV(3.4.7) 
> /build/source/modules/dnn/src/caffe/caffe_io.cpp:1121: error: (-2:Unspecified 
> error
> ) FAILED: fs.is_open(). Can't open "" in function 'ReadProtoFromTextFile'
> 
> digikam.general: Found 0 faces in "IMG-20170907-WA0004.jpg" QSize(1032, 581) 
> QSize(1032, 581)
> digikam.dimg: "/home/timo/tmp/deletable-pics/Syncthing-3TB/Oneplus 
> One/Whatsapp/Media/WhatsApp Images/IMG-20170907-WA0006.jpg"  : JPE
> G file identified
> digikam.general: Check for finish:  51 packages, 0 infos to filter, 
> hasFinished() false
> digikam.database: Search result: 36
> digikam.general: Removing old entries ()
> digikam.general: Cancel Main Thread
> [Thread 0x7fff37fff700 (LWP 17296) exited]
> digikam.general: One job is done
> digikam.general: Cancel Main Thread
> digikam.general: Cannot extract preview for 
> "/home/timo/tmp/deletable-pics/Syncthing-3TB/Oneplus 
> One/Whatsapp/Media/WhatsApp Images/I
> MG-20171021-WA.jpeg"
> digikam.dimg: "/home/timo/tmp/deletable-pics/Syncthing-3TB/Oneplus 
> One/Whatsapp/Media/WhatsApp 

[kdevelop] [Bug 410820] New: Crash when closing a document opened with Okteta plugin

[bugzilla_noreply]

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

Bug ID: 410820
   Summary: Crash when closing a document opened with Okteta
plugin
   Product: kdevelop
   Version: 5.4.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: krzysio.ku...@wp.pl
  Target Milestone: ---

Application: kdevelop (5.4.0)

Qt Version: 5.13.0
Frameworks Version: 5.60.0
Operating System: Linux 5.2.5-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

Closing a tab that has an okteta view open (e.g. with a SPIR-V shader).

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f08b4fe20c0 (LWP 9569))]

Thread 15 (Thread 0x7f0872ffd700 (LWP 9782)):
#0  0x7f08c36e8e05 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f08c61e1fef in QWaitConditionPrivate::wait (deadline=...,
this=0x559887f2a610) at thread/qwaitcondition_unix.cpp:146
#2  QWaitCondition::wait (this=, mutex=0x559887f2a6f0,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#3  0x7f08c61e20d9 in QWaitCondition::wait (this=0x559887f08998,
mutex=0x559887f2a6f0, time=) at
../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68
#4  0x7f08c2d306c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f08c2d2ccfa in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f08c2d2d0ae in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f08c2d2cd51 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f08c2d2d0ae in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f08c2d2cd51 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f08c2d2d0ae in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f08c2d2cd51 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f08c2d2d0ae in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f08c2d2cd51 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f08c2d2d0ae in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#15 0x7f08c2d2cd51 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#16 0x7f08c2d2d0ae in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#17 0x7f08c2d2cebb in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#18 0x7f08c61dc112 in QThreadPrivate::start (arg=0x7f08640038e0) at
thread/qthread_unix.cpp:360
#19 0x7f08c36e2faa in start_thread () from /lib64/libpthread.so.0
#20 0x7f08c7cc673f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7f08737fe700 (LWP 9781)):
#0  0x7f08c36e8e05 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f08c61e1fef in QWaitConditionPrivate::wait (deadline=...,
this=0x559887f2a610) at thread/qwaitcondition_unix.cpp:146
#2  QWaitCondition::wait (this=, mutex=0x559887f2a6f0,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#3  0x7f08c61e20d9 in QWaitCondition::wait (this=0x559887f08998,
mutex=0x559887f2a6f0, time=) at
../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68
#4  0x7f08c2d306c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f08c2d2ccfa in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#6  0x7f08c2d2d0ae in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#7  0x7f08c2d2cd51 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#8  0x7f08c2d2d0ae in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#9  0x7f08c2d2cd51 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#10 0x7f08c2d2d0ae in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib64/libKF5ThreadWeaver.so.5
#11 0x7f08c2d2cebb in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f08c61dc112 in QThreadPrivate::start (arg=0x7f086c0034e0) at
thread/qthread_unix.cpp:360
#13 0x7f08c36e2faa in start_thread () from /lib64/libpthread.so.0
#14 0x7f08c7cc673f in clone () from /lib64/libc.so.6

Thread 13 

[Breeze] [Bug 407639] With the default Breeze theme, labels on tabs in Firefox are hard to read when using CSDs

[Nate Graham]

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

--- Comment #11 from Nate Graham  ---
I did, sorry about that.

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

[bugs.kde.org] [Bug 410284] Terminology used on bugs.kde.org repeatedly refers to "bugs" in the context of non-bugs (e.g. feature requests, wishlist items, proposed improvements)

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|bugs.kde.org and|Terminology used on
   |community.kde.org   |bugs.kde.org repeatedly
   |inconsistent about  |refers to "bugs" in the
   |reporting KDE issues other  |context of non-bugs (e.g.
   |than defects on |feature requests, wishlist
   |bugs.kde.org|items, proposed
   ||improvements)
   Assignee|unassigned-b...@kde.org |sysad...@kde.org
 CC||she...@kde.org
Product|kde |bugs.kde.org
  Component|general |general
   Severity|grave   |normal

--- Comment #4 from Nate Graham  ---
There's a certain amount of this that's not really resolvable, and people will
just need to interpret things accordingly. That said I do think the proposed
changes to bugs.kde.org are reasonable.

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

[kde] [Bug 410284] bugs.kde.org and community.kde.org inconsistent about reporting KDE issues other than defects on bugs.kde.org

[Filipus Klutiero]

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

--- Comment #3 from Filipus Klutiero  ---
Looking at https://bugs.kde.org/show_bug.cgi?id=409930 I am afraid that
statuses need fixing too. It is currently possible for tickets with importance
"wishlist" to be set to status RESOLVED NOT A BUG. This status should probably
become INVALID.

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

[konsole] [Bug 410819] The konsole shortcuts would not sync to the terminal panels in dolphin

[bugzilla_noreply]

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

--- Comment #1 from tcanabr...@kde.org ---
That’s not a bug, ctrl c sends the kill signal in terminal apps.


Em dom, 11 de ago de 2019 às 18:05, jason 
escreveu:

> https://bugs.kde.org/show_bug.cgi?id=410819
>
> Bug ID: 410819
>Summary: The konsole shortcuts would not sync to the terminal
> panels in dolphin
>Product: konsole
>Version: 18.04.0
>   Platform: Other
> OS: Linux
> Status: REPORTED
>   Severity: normal
>   Priority: NOR
>  Component: keyboard
>   Assignee: konsole-de...@kde.org
>   Reporter: f...@outlook.com
>   Target Milestone: ---
>
> I have set shortcuts in konsole: Copy is "Ctrl+c" and Paste is "Ctrl+v";
> but in the terminal panels in dolphin, the shortcuts: Copy is
> "Ctrl+Shift+c"
> and Paste is "Ctrl+Shift+v"
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

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

[kde] [Bug 410284] bugs.kde.org and community.kde.org inconsistent about reporting KDE issues other than defects on bugs.kde.org

[Filipus Klutiero]

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

Filipus Klutiero  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---
 Ever confirmed|0   |1
Summary|community.kde.org (and  |bugs.kde.org and
   |bugs.kde.org) inconsistent  |community.kde.org
   |about reporting KDE issues  |inconsistent about
   |other than defects on   |reporting KDE issues other
   |bugs.kde.org|than defects on
   ||bugs.kde.org

--- Comment #2 from Filipus Klutiero  ---
Thank you very much Nate.

I am re-titling to clarify that, assuming that comment 1 is correct,
bugs.kde.org needs fixing. I am afraid there may be lots of place which need to
be switched to proper terms. Without pretending to be exhaustive, all of the
following places are currently incoherent:
# Site title "KDE Bugtracking System", which could read "KDE Issue Tracking
System", or - more succinctly - "KDE Issue Tracker".
# The homepage only offers to "File a Bug", and doing that brings to an "Enter
Bug" page.
# The ticket visualization/edition controller presents all issues as "bugs",
even those with importance "wishlist" (see
https://bugs.kde.org/show_bug.cgi?id=9055 for example)
# To my knowledge, the site only has subdomain "bugs.kde.org", which - while
not necessarily a bug, is at least misleading. It would be much clearer to at
least support access through a representative subdomain, such as
"issues.kde.org".

There is still some work needed on community.kde.org, at least on
https://community.kde.org/Get_Involved/Issue_Reporting. For example, the name
of step #1 ("Step 1: Make sure it's a valid bug or feature request") currently
doesn't allow requests for improvements other than feature additions and
bug-fixes.

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

[digikam] [Bug 410787] can't export to Google photo

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #14 from caulier.gil...@gmail.com ---
Maik, 

Perhaps a tip somewhere in plugin settings widget can help users to prevent
future problems about Google download limitations.

Gilles

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

[konsole] [Bug 410819] New: The konsole shortcuts would not sync to the terminal panels in dolphin

[jason]

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

Bug ID: 410819
   Summary: The konsole shortcuts would not sync to the terminal
panels in dolphin
   Product: konsole
   Version: 18.04.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: keyboard
  Assignee: konsole-de...@kde.org
  Reporter: f...@outlook.com
  Target Milestone: ---

I have set shortcuts in konsole: Copy is "Ctrl+c" and Paste is "Ctrl+v";
but in the terminal panels in dolphin, the shortcuts: Copy is "Ctrl+Shift+c"
and Paste is "Ctrl+Shift+v"

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

[kdeplasma-addons] [Bug 366342] System Load Viewer Plasmoid shows only used memory including cache

[Garry Williams]

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

--- Comment #8 from Garry Williams  ---
Created attachment 122065
  --> https://bugs.kde.org/attachment.cgi?id=122065=edit
Patch To Restore Cache Display and Allow Hover

I also submitted a patch to allow hovering on the load viewer so that
it wouldn't disappear until moving the mouse off of it.  That was
rejected on some consistency grounds -- not on its merit.

I, too didn't like the change here.  But it seems that no one agrees.
That being the case, I have been carrying my own patches to restore
the cache display and to allow hover to prevent the display from
closing.

Here are my patches, if you are interested.  I apply them (after
updates regress them) with the following commands (Fedora):

sudo patch
/usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml
ui/SystemLoadViewer.qml.patch
sudo patch
/usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/ColorSettings.qml
ui/ColorSettings.qml.patch
sudo patch
/usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/config/main.xml
config/main.xml.patch

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

[kdevplatform] [Bug 67994] configure shortcuts is not consistent, kdevelop shortcuts are application-wide and editor shortcuts are per file...

[jason]

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

jason  changed:

   What|Removed |Added

 CC||f...@outlook.com

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

[frameworks-kio] [Bug 410818] New: Generic icon displayed when typing the name of a file instead of using the list in KFileDialog

[Raphaël Jakse]

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

Bug ID: 410818
   Summary: Generic icon displayed when typing the name of a file
instead of using the list in KFileDialog
   Product: frameworks-kio
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Open/save dialogs
  Assignee: fa...@kde.org
  Reporter: raphael@jakse.fr
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 122064
  --> https://bugs.kde.org/attachment.cgi?id=122064=edit
A video of the bug

SUMMARY

When typing the name of a file in the Name field, the file is selected.
However, the icon in the Name Field is generic. When selecting a file using the
list, the icon is the actual icon of the file.

STEPS TO REPRODUCE
1. In Kate, File > Open
2. Type the name of an existing file that should not have a generic file name

OBSERVED RESULT

A generic icon is displayed. If the name of a folder is typed, the icon of a
generic file is displayed.

EXPECTED RESULT

A specific icon should be displayed. If the name of a folder is typed, the icon
of a folder should be displayed.

SOFTWARE/OS VERSIONS: Current Neon Docker

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

[digikam] [Bug 410787] can't export to Google photo

[Maik Qualmann]

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

--- Comment #13 from Maik Qualmann  ---
(In reply to Philippe ROUBACH from comment #12)
> i tried to transfer by batch of 48.
> 
> at the fifth batch at the moment i get 48/48 i get an error message :
> 
> Error transferring
> https://photoslibrary.googleapis.com/v1/mediaItems:batchCreate - server
> replied: Bad Request
> 
> progress indicator on thumbnails stays spinning.
> 
> at google photo then photos was not added.

This looks like the bug in digiKam-6.2.0. We wait until you have tested
pre-release 6.3.0.

Maik

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

[frameworks-kio] [Bug 410817] New: Select files from the address (folder) bar in KFileDialog

[Raphaël Jakse]

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

Bug ID: 410817
   Summary: Select files from the address (folder) bar in
KFileDialog
   Product: frameworks-kio
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Open/save dialogs
  Assignee: fa...@kde.org
  Reporter: raphael@jakse.fr
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Hello,

I find myself often trying to start typing a file name in the address bar of
the open / save dialog.

When doing this, nothing happens, and if the file name is completely typed and
then the enter key is pressed, the dialog tries to open the file as a folder,
and this obviously fails.

Conversely, typing an address / a folder name in the "Name" field of the dialog
works (which, by the way, has by far the best behavior I could notice across
the different file dialogs I was (un)lucky to come across).

I think the current behavior of trying to open a file entered in the address
bar as a folder and fail is not intuitive.

I have two (contradictory) suggestions:

1) Either make the address bar act like the name field, with the optional
difference that folders should be selected / suggested before files.
2) Or keep the current behavior of suggesting folders as they are typed, and
then files. When enter is pressed:
2.1) Either open the selected file
2.2) Or show a dialog telling the user that this is a file (and not a
folder). "Would you like to open this file (or) replace the existing file?".

In both cases, if (the prefix of) a file is entered / selected in the address
bar, the file's icon should be shown instead of the folder icon in the address
bar.

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

[okular] [Bug 410041] I can not click in a reference if I highlight a text

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #8 from Albert Astals Cid  ---
I got mistaken, we're not doing what I said we do.

We need to merge  the handling of rightclick in mousePressEvent and
mouseReleaseEvent.

I have the feeling there's some code around that was trynig to do that?

Anyone remembers?

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

[calligraplan] [Bug 410816] New: Export options

[bugzilla_noreply]

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

Bug ID: 410816
   Summary: Export options
   Product: calligraplan
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: usability
  Assignee: dand...@get2net.dk
  Reporter: isaacson31...@gmail.com
  Target Milestone: ---

We need to be able to export plans to other standard formats (xml, csv)
otherwise were committed to working on one application which may or may not
continue to be updated.

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

[digikam] [Bug 410787] can't export to Google photo

[Philippe ROUBACH]

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

--- Comment #12 from Philippe ROUBACH  ---
i tried to transfer by batch of 48.

at the fifth batch at the moment i get 48/48 i get an error message :

Error transferring
https://photoslibrary.googleapis.com/v1/mediaItems:batchCreate - server
replied: Bad Request

progress indicator on thumbnails stays spinning.

at google photo then photos was not added.

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

[digikam] [Bug 267742] Digikam crashes during startup

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||6.3.0

--- Comment #3 from caulier.gil...@gmail.com ---
Fixed with bug #260864

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

[digikam] [Bug 256391] Aplication crashes on startup

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||6.3.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Fixed with bug #243107

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

[digikam] [Bug 260864] Digikam fails to start

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||6.3.0
 Resolution|DUPLICATE   |FIXED

--- Comment #7 from caulier.gil...@gmail.com ---
Fixed with bug #243107

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

[digikam] [Bug 253200] Digikam Crashes As Soon As I Hit the Icon to Load

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||6.3.0

--- Comment #2 from caulier.gil...@gmail.com ---
Fixed with bug #243107

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

[digikam] [Bug 251403] Crash after trying to check the setup

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||6.3.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Fixed with bug 24

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

[digikam] [Bug 245920] digikam crash when open in suse 11.3

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||6.3.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Fixed with bug #245472

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

[digikam] [Bug 246666] Digikam crashes at launch

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||6.3.0

--- Comment #8 from caulier.gil...@gmail.com ---
Fixed with bug #243107

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

[digikam] [Bug 245472] digiKam crashed after clicking on the "Configure digiKam" option in the Settings menu

[bugzilla_noreply]

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

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

   What|Removed |Added

 Resolution|DUPLICATE   |FIXED
   Version Fixed In||6.3.0

--- Comment #3 from caulier.gil...@gmail.com ---
Fixed with bug #243107

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

[digikam] [Bug 298717] Unreadable Tooltips - dark grey on black

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||6.3.0
 Resolution|DUPLICATE   |FIXED

--- Comment #3 from caulier.gil...@gmail.com ---
Fixed with bug #283572

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

[cantor] [Bug 410802] Cantor uses a bundled, patched discount copy and fails to build if LANG is not poperly set

[Nikita Sirgienko]

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

--- Comment #4 from Nikita Sirgienko  ---
(In reply to Luca Beltrame from comment #2)
> (In reply to Nikita Sirgienko from comment #1)
> > "discount-2.2.6-patched.tar" placed in cantor/thirdparty directory. It is
> 
> It looks like it fails if LANG isn't properly set. If setting LANG to
> "en_US.UTF-8" prior to building, it builds. I've edited the title to reflect
> this.
> 
> That said, it is not acceptable for distros to have bundled third party deps
> (unless you can disable the bundled copy and use the system one), nor that
> the feature summary doesn't tell you that it's going to use a bundled
> library.
> 
> The README should also mention this.

So you suggest to add information in README, that Cantor uses bundled third
party library, right?
Could you also give an example, how information like that is mentioned in KDE
programs?

> That won't fly with distributions for a lot of good reasons: what if the
> bundled library does not build anymore for newer compilers? What if there is
> a security vulnerability in the bundled library that is not patched? What if
> there are bugs in the bundled library that are fixed in newer versions?

Of course, current situation with Discount always planned as temporary
solution.

> As this change is in master only, there is enough time for 19.12 to:
> 
> a. Submit discount changes upstream
> b. Allow the build system to *not* use the bundled discount fork (because
> that's what it is)
> c. Write at the end of the cmake call whether a bundled library is being
> used or not.

Not sure about 19.12, I mean, I will send pull request in few days, but I don't
know, how fast upstream will respond and which Discount version will available
for 19.12
But, just in case, for variant, when needed changes won't be available in
system library version, that you could recommend?

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

[digikam] [Bug 333792] Crash when renaming category

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||6.3.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Fixed with bug #329697

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

[digikam] [Bug 320436] Update mime data settings to remove mpo extension

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||6.3.0
 Resolution|DUPLICATE   |FIXED

--- Comment #2 from caulier.gil...@gmail.com ---
Fixed with bug #276592

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