[konversation] [Bug 310544] Per-network proxy settings

[Luke-Jr via KDE Bugzilla]

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

Luke-Jr  changed:

   What|Removed |Added

 CC||luke-jr+kdeb...@utopios.org

--- Comment #4 from Luke-Jr  ---
How about when a proxy is *only* needed for a specific server? Eg, use Tor only
for .onion servers...

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

[plasmashell] [Bug 361211] Missing Letters

[PGillespie via KDE Bugzilla]

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

--- Comment #4 from PGillespie  ---
Created attachment 98210
  --> https://bugs.kde.org/attachment.cgi?id=98210=edit
Completely gone...

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

[ksnapshot] [Bug 361323] ksnapshot "Send To..." button crash

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[digikam] [Bug 361316] kipi-plugins fails to build with flex-2.6.0

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[kdelibs] [Bug 347917] knotify crash on openSUSE because of mismatch in vlc version

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||b...@blws.org

--- Comment #91 from Christoph Feck  ---
*** Bug 361298 has been marked as a duplicate of this bug. ***

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

[phonon-backend-vlc] [Bug 361298] digikam crashes on start

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Christoph Feck  ---


*** This bug has been marked as a duplicate of bug 347917 ***

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

[neon] [Bug 361276] "Error loading QML" messages instead of launcher and task manager after recent update.

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Christoph Feck  ---
Already reported as bug 361277.

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

[Akonadi] [Bug 361322] Crash during cold boot

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|unassigned-b...@kde.org |kdepim-b...@kde.org
Product|kde |Akonadi
  Component|general |general

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

[kmix] [Bug 361320] Sound Sliders appear on wrong screen when taskbar icon is clicked

[Christoph Feck via KDE Bugzilla]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |UNMAINTAINED
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Christoph Feck  ---
Linux Mint 17.3 uses packages from Ubuntu 14.04 repositories, which does not
have the KMix version with the fix. Either use a more recent distribution, or
ask in a distribution-specific forum how to add backport repositories with more
recent KDE software versions.

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

[kmail2] [Bug 345992] Keyboard shortcut assigned to "archive mail" works once, unconfigures itself

[Rewarp via KDE Bugzilla]

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

Rewarp  changed:

   What|Removed |Added

 CC||rew...@thestrayworld.com

--- Comment #4 from Rewarp  ---
Since this is a keyboard shortcut issue, I am adding my own custom shortcut
problem here as well.
 I have assigned the "Right" and "Left" key to Next and Previous message
respectively.

For some odd reason, The shortcut for "Focus on Next Message" is not the
default Alt+Right, but is Right. This conflicts with my custom key for "Next
Message".

After changing "Focus on Next Message" to the default Alt+Right, the Right key
works once to move to the next message, but on the second tap is suddenly
reassigned to "Focus on Next Message again"

Steps to reproduce:

1. Reassign shortcut for "Focus on Next Message" to default Alt+Right
2. Assign shortcut for "Next Message" to Right.
3. Press Right.

Expected:

The next email message should be selected.

Instead:

1. The next message is selected.
2. The custom shortcut fails and is reassigned to "Focus on Next Message".

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

[korganizer] [Bug 361332] New: Upgrade from 4.14.2 to 15.12.3 breaks syncing with original ICS calendar file

[tleedavidson via KDE Bugzilla]

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

Bug ID: 361332
   Summary: Upgrade from 4.14.2 to 15.12.3 breaks syncing with
original ICS calendar file
   Product: korganizer
   Version: 15.12.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: bugz.ou...@recursor.net

After the upgrade, I noticed that the calendar file,
"~/.kde4/share/apps/korganizer/std.ics", wasn't being updated after making
changes to my ToDo list even though the changes persisted in KOrganizer between
launches. They were obviously cached by Akonadi.

So, I stopped Akonadi, removed "~./local/share/akonadi", and restarted Akonadi
to try forcing a re-sync. Akonadi failed to reload the calendar file
complaining with:
Invalid URL: QUrl("/home/user/.kde4/share/apps/korganizer/std.ics")
"Could not load file '/home/user/.kde4/share/apps/korganizer/std.ics'."

The file is there, has not been modified, and was working fine with KOrganizer
v4.14. But, it does not get loaded by KOrganizer5 causing no calendars
available even though the Personal calendar is shown in Settings and has the
correct location.

Reproducible: Always

Steps to Reproduce:
1. Upgrade from KOrganizer 4 to KOrganizer 5 (15)
2. Stop the Akonadi server, remove the Akonadi database, and restart the server
3. Launch KOrganizer; your calendar is unavailable.

Actual Results:  
ToDo list is gone. Calendar is unavailable.

Expected Results:  
Pre-upgrade personal data migrated and syncing preserved.

KDE Plasma Version: 5.5.5
Qt Version: 5.5.1
Kernel Version: 4.1.15
OS Type: 64-bit

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

[kwin] [Bug 360878] ::allowClientActivation should unconditionally return false for unreasonable focus policies

[via KDE Bugzilla]

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

--- Comment #15 from r...@alum.mit.edu ---
I see.

The comment "raising is split from activation, we are more generous on former,
so that the user does not easily miss windows that are denied activation" (from
reviewboard 124130) describes what I have in mind.  I want new top level
windows (as opposed to things like dialogs, menus, and such) to not get focus
unless I explicitly activate them by moving the mouse into them, but I do want
them to be visible.  But I don't think I want the timestamps to come into play.
 Even if I haven't typed into the current window in an hour, I don't want a
window that newly pops up to get focus.

There's the other problem of focus going to windows on a different virtual
desktop.  It's hard for me to see how that makes sense with any focus policy.

I can well believe there are a lot of corner cases here.

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

[cantor] [Bug 296615] R’s help.start() does not produce any content

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |r-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 296814] file.show does not do anything in cantor/R

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |r-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 229845] Cantor crashed after Maxima backend crash

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |maxima-backend

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

[cantor] [Bug 299385] Cantor stops responding when R returns a matrix 50̣×50

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |r-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 330478] Issue with LaTeX output for maxima backend

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |maxima-backend

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

[cantor] [Bug 312738] Should import Sage LaTeX macros

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |sage-backend

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

[cantor] [Bug 328185] cantor crash

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |sage-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 336024] Cantor crashes when rendering equations

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |maxima-backend

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

[cantor] [Bug 283216] Evaluation crash

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |sage-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 246943] R backend: when compiling, R should be run with --no-init-file

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |r-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 296546] cantor_rserver fails to start

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |r-backend

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

[cantor] [Bug 316186] cantor fails testoctave

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |octave-backend

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

[cantor] [Bug 299403] R images have a white vertical line to the right

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |r-backend

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

[cantor] [Bug 266040] Cantor crashed when computing Eigenvalues using Sage

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |sage-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 262899] Cantor crash with sage backend

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |sage-backend

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

[cantor] [Bug 292611] cantor is crashing with scilab backend enable

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |scilab-backend
 CC||alexanderrie...@gmail.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

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

[cantor] [Bug 321285] Cantor (with maxima backend) crashed after asking for a graph

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |maxima-backend

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

[Akonadi] [Bug 351628] Akonadi DAV Resource does not sync all calendars on ownCloud any more

[somnium via KDE Bugzilla]

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

--- Comment #20 from somnium  ---
It seems that the problem has something to do with the new owncloud version
9.0.

The urls changed from: https://ADDRESS/remote.php/caldav/ and
https://ADDRESS/remote.php/carddav/ to https://ADDRESS/remote.php/dav/ (caldav
and carddav). I changed this manually in akonadiconsole and the calendars and
contacts appeared again.

I think, this is an easy fix in kontact/kdepim.

Cheers.

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

[cantor] [Bug 236571] Cantor doesn't enable Maxima backend on Vista

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |maxima-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 323261] Cantor with octave: plots in functions are not shown

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |octave-backend

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

[cantor] [Bug 334669] Crash configuring cantor python2 backend

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |python2-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 345610] Cantor crashed when using python pylab

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org
  Component|general |python2-backend

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

[cantor] [Bug 356103] Python 3 backend is not functional

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |python3-backend

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

[cantor] [Bug 348180] rcallbacks.cpp:48:23: error: 'onReadConsole' was not declared in this scope

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

  Component|general |r-backend
 CC||alexanderrie...@gmail.com,
   ||fil...@kde.org

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

[cantor] [Bug 354772] Cantor: hardcoded include of luajit-2.0/lua.hpp

[Filipe Saraiva via KDE Bugzilla]

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

Filipe Saraiva  changed:

   What|Removed |Added

 CC||fil...@kde.org
  Component|general |lua-backend

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

[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor

[PhillB via KDE Bugzilla]

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

--- Comment #42 from PhillB  ---
Just a quick note: I noticed a couple of weeks ago (and meant to add it here)
that when the screenlocker becomes unresponsive to KB/Mouse the shift key still
works. That is to say the bold notice, indicating the shift key is active,
appears when you press the shift key and goes away when you release it.

However, that probably doesn't help I suspect.

P

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

[kdenlive] [Bug 361090] Audio thumbnail incorrect

[via KDE Bugzilla]

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

--- Comment #7 from qubo...@gmail.com ---
Regarding the above two comments, I think there might be an issue with
pre-existing thumbnails when a video file is used in a new project (possibly
with another fps). I deleted all thumbnails to create a clean slate - that
seemed to have helped - but haven't thoroughly tested how to trigger the bug
yet.

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

[krita] [Bug 361331] New: Reference image docker causes a crash on browsing directories with pictures

[via KDE Bugzilla]

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

Bug ID: 361331
   Summary: Reference image docker causes a crash on browsing
directories with pictures
   Product: krita
   Version: 2.9.7
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: scaylathe...@gmail.com

Reference image docker crashes Krita when opening a directory with pictures
inside. It doesn't happen on every directory or even same one, but when I try
changing directories with pictures inside them it always seems to crash within
3 to 10 directories.
Pressing "back" button might be required too, not sure on this one.
Directories with images inside seem to load longer, crash seems to happen
during/after loading.
Image preview window can be shown or hidden, happens both ways.

Reproducible: Always

Steps to Reproduce:
1. Open Krita and reference image docker
2. In the docker navigate to directories that have some images stored inside
them
3. Move forward and backwards between them and a crash should occur

Actual Results:  
Krita closes with a crash. A crash reporting dialog comes up, but can't seem to
gather anything beyond "aborted" even with debugging symbols installed.

Expected Results:  
The selected folder should open and images inside it should load in the preview
window below.

Running Krita 2.9.7 on Ubuntu 15.10, kernel 4.2.0-34-generic.
When running Krita from terminal the following is produced on crash:

(krita:16013): GLib-GIO-ERROR **: inotify read(): Bad file descriptor
Trace/breakpoint trap (core dumped)

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

[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

[Frederik Schwarzer via KDE Bugzilla]

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

Frederik Schwarzer  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #9 from Frederik Schwarzer  ---
Ah, thanks. Now I can reproduce.

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

[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

[Antonio Rojas via KDE Bugzilla]

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

--- Comment #8 from Antonio Rojas  ---
Simpler steps to reproduce: open ~/.config/kmahjonggrc, and point Layout_file
to a non-existant path. The KDE4 settings migration is just the trigger here.

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

[kwin] [Bug 360878] ::allowClientActivation should unconditionally return false for unreasonable focus policies

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #14 from Thomas Lübking  ---
(In reply to rlk from comment #13)
> When I type "konsole", the *new* konsole window that pops up gets the focus 
> away from
> the existing one.

Yes, this is determined by the focus stealing prevention (as you figured)

> After 5 seconds, when the konsole popped up, the focus was
> switched to it despite medium focus stealing prevention.
Yes, because the medium FSP won't deny it under this circumstances (high will
if uncertain about the start time)
The new windows "start time" is newer than the last focus assignment or
"interaction" (usertime stamp)

The extreme FSP will keep the focus where it is, the high one if uncertain
about one of the timestamps and actuallly™ two konsole windows might end up in
the same group (depends on some attributes, didn't actually check) what might
allow them to distribute the focus "among" each other as it pleases them (but I
don't think so, there should be a correct PID split atm)

FSP isn't trivially doing "the right thing" and there's bug #110543 and
ultimately https://git.reviewboard.kde.org/r/124130/ (which would preserve the
focus on the if you're still typing in konsole at a reasonable speed)

FFM unlike FUM/FSUM *is* subject to focus distribution (that's the major
differentce between the first and second two policies); if you want to keep the
focus where it is, you'll have to pick extreme FSP.

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

[digikam] [Bug 354364] Crash of DNG converter

[Maik Qualmann via KDE Bugzilla]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||wscheffn...@gmail.com

--- Comment #34 from Maik Qualmann  ---
*** Bug 361312 has been marked as a duplicate of this bug. ***

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

[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

[naughtypine]

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

naughtyp...@openmailbox.org  changed:

   What|Removed |Added

 CC||naughtyp...@openmailbox.org

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

[kmail2] [Bug 316153] can't move or delete messages in imap inbox

[Richard via KDE Bugzilla]

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

Richard  changed:

   What|Removed |Added

 CC|richard.taub...@gmx.de  |

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

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Maik Qualmann via KDE Bugzilla]

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

--- Comment #6 from Maik Qualmann  ---
With your CMakeLists patch crashes now the renamecustomizertest at end. Compile
or linking problems do not exist here.

Maik

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

[kmenuedit] [Bug 361330] New: In KDE Menu Editor, cannot save the shortcut key for any application.

[Yiming Yang via KDE Bugzilla]

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

Bug ID: 361330
   Summary: In KDE Menu Editor, cannot save the shortcut key for
any application.
   Product: kmenuedit
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: yang.yihm...@gmail.com

Every time I set a shortcut key for an application (e.g. Konsole) in the
"advanced" label, and saved it. After exiting, I started the KDE Menu Editor
again, and found the shortcut key for that application is reset to "None".
Thus, my customized shortcut key never worked.

Reproducible: Always

Steps to Reproduce:
1. Open KDE Menu Editor by right clicking at the "start-menu" icon;
2. Choose any application, then choose "advanced" label;
3. Set the shortcut key for that application;
4. Save it;
5. Exit KDE Menu Editor;
6. Open KDE Menu Editor again.

Actual Results:  
You will see that the shortcut key you just set has been changed back to
"None", and that shortcut key never worked.

Expected Results:  
It should have been saved as the shortcut key you just set, instead of being
"None". And the key should have worked.

This happens in OpenSuSE Leap distribution.

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

[kipiplugins] [Bug 361329] New: Flickr uploader does not clean /tmp after upload

[Terje Runde via KDE Bugzilla]

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

Bug ID: 361329
   Summary: Flickr uploader does not clean /tmp after upload
   Product: kipiplugins
   Version: 4.14.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Flickr
  Assignee: kde-imag...@kde.org
  Reporter: terje.ru...@gmail.com

The Flickr uploader stores all images it uploads on tmpfs (/tmp), but it does
not remove them after upload. After 700+ image uploads, my tmpfs got full and I
got a generic error message in the uploader GUI.

I believe the image.save(path, "JPEG", imageQuality) in flickrtalker.cpp should
have a corresponding delete when the file is no longer read.

Reproducible: Always

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

[kio] [Bug 76380] Moving to trash shouldn't move across partitions

[francisco_t via KDE Bugzilla]

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

francisco_t  changed:

   What|Removed |Added

 CC||leviat...@gmx.com

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

[kscreenlocker] [Bug 361328] Kscreenlock locks screen instantly and ignores 'require password after' timeout

[via KDE Bugzilla]

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

--- Comment #2 from nothank...@mailinator.com ---
Yes appears to be a duplicate. You've got another bug then because when I
submitted the bug (I've just checked again) it's showing the top 100
kscreenlocker bugs are 'no bugs were found'.

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

lp.allar...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

lp.allar...@gmail.com changed:

   What|Removed |Added

Version|unspecified |4.7.2
   Severity|critical|crash
  Component|general |database

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

[kdenlive] [Bug 361090] Audio thumbnail incorrect

[Chris Gebhardt via KDE Bugzilla]

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

Chris Gebhardt  changed:

   What|Removed |Added

 CC||d...@openserve.org

--- Comment #5 from Chris Gebhardt  ---
Assuming recent (29/03/2016) prior commits are actually included in the
kdenlive-master PPA build listed below, I'm still seeing no audio thumbnails in
my existing projects or in a fresh project with a single clip. Switching
profiles initiates recreation of thumbnails, but then they don't actually
appear in the timeline.

kdenlive - 4:16.07.70+git201603301437~ubuntu15.10.1

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

--- Comment #16 from lp.allar...@gmail.com ---
OK I managed to fix most of the errors CC threw at me.  There are still some
errors (6) which is much better than 120...

Another thing, theres a "Equity" account with a sub-account named "Opening
balances".  This was not there with KMM 4.6.2.. What is this account?  Some
(4/6) of the errors left are related to this account...  Knowing what it does
and its purpose will help me fix the remaining errors.

For now, I can save the DB to a file (.kmy) and perform CC as I want, without
crashes!!!

Next time I see a seg fault I will try to setup the debugger...

Thanks!!

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

[plasmashell] [Bug 361200] Plasmashell Signal: Illegal Instruction - On KUBUNTU 16.04 Beta2 - During Install - Under Hyper-V

[Harrison via KDE Bugzilla]

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

--- Comment #5 from Harrison  ---
Good news, the problem ONLY occurs under Hyper-V!  I created an Install DVD and
it boots just fine.  So, the problem must be related to something in the
release of Plasmashell that is shipped with Kubuntu 16.04 [famous last words]. 
Is there any possibility of having someone else with a different environment
try this under Hyper-V to eliminate the possibility that it is unique to my
environment: Intel XEON E3-1275-v5 running on a ASRockRack C236M systemboard
with the Intel C236 chipset using the onboard processor graphics support?

If the "backtrace" would be of additional value, I will see whether there is
some way of creating a file that I can send to you.  The problem is, as I
previously said, this problem occurs so early in the Install process, there
isn't even any formatted disks upon which to put the backtrace file when the
crash occurs.  And, Hyper-V imposes limitations/restrictions on the test
environment [by design].

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

[kalarm] [Bug 361115] daylight savings time is handled incorrectly

[Graeme Hewson via KDE Bugzilla]

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

Graeme Hewson  changed:

   What|Removed |Added

 CC||b...@wormhole.me.uk

--- Comment #3 from Graeme Hewson  ---
See also bug 360674

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

[kalarm] [Bug 360674] Post-daylight savings time, kalarm records alarms 1 hour later than it should

[Graeme Hewson via KDE Bugzilla]

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

Graeme Hewson  changed:

   What|Removed |Added

 CC||b...@wormhole.me.uk

--- Comment #4 from Graeme Hewson  ---
I confirm this. I created an alarm several years ago to pop up at a certain
time on Saturday afternoon, and it's been fine until today. Six days after the
UK changed from GMT to BST (GMT+1), the alarm popped up an hour later than it
should have.

The machine hasn't been rebooted since Sunday. Using Kubuntu 15.10.
"kalarm --version" reports:

QCoreApplication::arguments: Please instantiate the QApplication object first
Qt: 5.4.2
KDE Frameworks: 5.15.0
KAlarm: 2.11.3-5ak

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

[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

[Bernd Steinhauser via KDE Bugzilla]

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

Bernd Steinhauser  changed:

   What|Removed |Added

 CC||li...@bernd-steinhauser.de

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

[kwin] [Bug 360878] ::allowClientActivation should unconditionally return false for unreasonable focus policies

[via KDE Bugzilla]

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

--- Comment #13 from r...@alum.mit.edu ---
No, because I haven't closed the first konsole window.  When I type "konsole",
the *new* konsole window that pops up gets the focus away from the existing
one.

The same thing happens with xterm or gnome-terminal: when I create a new
window, it gets the focus.

I tried another experiment: in an xterm, I ran

% sleep 5; konsole

and moved the mouse (and focus) to another window (tried with both firefox and
pidgin).  After 5 seconds, when the konsole popped up, the focus was switched
to it despite medium focus stealing prevention.

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

[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

[Frederik Schwarzer via KDE Bugzilla]

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

--- Comment #7 from Frederik Schwarzer  ---
Now I removed the whole install dir and the build dirs of libkdegames,
libkmahjongg and kmahjongg, rebuilt everything and still the same. Here it
starts fine.

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

[kscreenlocker] [Bug 361328] Kscreenlock locks screen instantly and ignores 'require password after' timeout

[Rog131 via KDE Bugzilla]

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

Rog131  changed:

   What|Removed |Added

 CC||samrog...@hotmail.com

--- Comment #1 from Rog131  ---
Duplicate of the https://bugs.kde.org/show_bug.cgi?id=361008 ?

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

[kwin] [Bug 360878] ::allowClientActivation should unconditionally return false for unreasonable focus policies

[Thomas Lübking via KDE Bugzilla]

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

--- Comment #12 from Thomas Lübking  ---
ffm is like Ctf, mInus the need to click. the focus is not bound to the mouse
position, but the fsp policy. the precedence is relevant to the focus decision
when a window is closed and the wm needs to select then next one.
this is *not* a bug.

the plasma popup situation is ridiculous, but unrelated. the popup is simply
buggy (due to caveats of qml)

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

[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

[Frederik Schwarzer via KDE Bugzilla]

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

--- Comment #6 from Frederik Schwarzer  ---
What am I doing wrong?

I do:
- copy the file attached earlier to ~.kde/share/config/kmahjonggrc,
- change the path inside the file to the location of the desktop file on my
system (resides under $HOME),
- remove .config/kmahjonggrc and then
- start KMahjongg.

KMahjongg starts fine and the new kmahjonggrc file is created in .config/ with
the correct layout.

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[Jack via KDE Bugzilla]

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

--- Comment #15 from Jack  ---
On 4/2/2016 1:14 PM, via KDE Bugzilla wrote:
> Then I did another CC on the DB and this time it reported identical output but
> at the bottom:
>
> Finished: 0 problems corrected. 111 problems still present.
That is not really as bad as it looks.  All those errors about account 
opening dates are from recent changes to the program, so you would not 
have seen them previously.  However, I don't think any of these errors 
should cause a crash.  The first step is to recover your data and let 
you keep working.  After that, if saved a copy of the bad database, then 
at a lower priority, it might be possible to find the source of the crash.

The issue is that an account should not have any transaction with a date 
earlier than the opening date of the account.  In KMM, payees and 
categories are internally treated as accounts, and when they are 
created, their opening date is the date they were created, not the date 
of the first transaction.  This is where most of these issues come from.

As you saw, KMM was able to fix most of those errors by altering the 
opening date of the account.  For the others, you can try to manually 
edit the account and change the opening day to be early enough.  In 
general, the best way I have found to do this is to open the ledger for 
the target account, then click the edit account icon (if you have it 
displayed) or else select the Account/Edit menu.  It seems the "Opening 
Balances" account is a bit difficult to find - but the first transaction 
in the ledger for most other accounts is the initial transfer of the 
opening balance for that account, so you can right click on the 
transaction, and there should be a choice "Go to 'Opening Balances"'.

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

[kwin] [Bug 360878] ::allowClientActivation should unconditionally return false for unreasonable focus policies

[via KDE Bugzilla]

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

--- Comment #11 from r...@alum.mit.edu ---
Another, simple case:

0) Focus follows mouse, mouse precedence, focus stealing prevention medium,
both autoraise and click to raise turned off.

1) Start konsole, put it on the right hand side of the screen, leave mouse over
the konsole window.

2) In the konsole, run

konsole

Result: second konsole window gets focus.

Expected result: focus stays with the original konsole window

With focus stealing prevention high this doesn't happen, but then it's very
difficult to use the KDE menu from the panel (I have to explicitly defocus the
mouse by clicking over the root window in order to be able to use it).

So this would appear not to be related to focus under mouse.

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

[konsole] [Bug 360360] Paste-special from Konsole in LibreOffice vaporizes Desktop Session

[Martin van Es via KDE Bugzilla]

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

--- Comment #1 from Martin van Es  ---
This is what happens in the kernel.log when the crash happens:

Apr  2 19:27:23 minivanes kernel: [  602.673721] kactivitymanage[1636]:
segfault at 7fe548cfacd0 ip 7fe5300a3291 sp 7ffedd08d398 error 4 in
libQt5Sql.so.5.5.1[7fe53008f000+3f000]
Apr  2 19:27:24 minivanes sddm-helper[1415]: [PAM] Ended.
Apr  2 19:27:24 minivanes sddm[1122]: Auth: sddm-helper exited successfully
Apr  2 19:27:24 minivanes sddm[1122]: Socket server stopping...
Apr  2 19:27:24 minivanes sddm[1122]: Socket server stopped.
Apr  2 19:27:24 minivanes sddm[1122]: Display server stopping...
Apr  2 19:27:24 minivanes sddm[1122]: Display server stopped.
Apr  2 19:27:24 minivanes sddm[1122]: Running display stop script 
"/usr/share/sddm/scripts/Xstop"
Apr  2 19:27:24 minivanes sddm[1122]: Removing display ":0" ...
Apr  2 19:27:24 minivanes sddm[1122]: Adding new display on vt 7 ...
Apr  2 19:27:24 minivanes sddm[1122]: Display server starting...
Apr  2 19:27:24 minivanes sddm[1122]: Running: /usr/bin/X -nolisten tcp -auth
/var/run/sddm/{0df7c23d-c88b-4aa9-9c79-130bdf4a6ae1} -background none -noreset
-displayfd 18 vt7
Apr  2 19:27:24 minivanes sddm[1122]: Running display setup script 
"/usr/share/sddm/scripts/Xsetup"
Apr  2 19:27:24 minivanes sddm[1122]: Display server started.
Apr  2 19:27:24 minivanes sddm[1122]: Socket server starting...
Apr  2 19:27:24 minivanes sddm[1122]: Socket server started.
Apr  2 19:27:24 minivanes sddm[1122]: Greeter starting...

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

[marble] [Bug 346333] "Wait duration:" portion is not enabled/editable when trying to edit a FlyTo item in a Tour when it is the first item in the Tour playlist

[Sanjiban Bairagya via KDE Bugzilla]

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

--- Comment #2 from Sanjiban Bairagya  ---
I'm pretty sure that function has been changed by now after I had written it,
so I'm not very confident about the intention of that code either. However, I
had a discussion about this with Torsten long back, and he mentioned that this
bug report is not actually a bug, but a feature itself, and that, setting the
wait duration for the first flyto item should be intentionally disabled, so
that it seems like the tour is starting from the first element itself, without
any wait there, so I think this bug report can be closed if necessary :)

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

--- Comment #14 from lp.allar...@gmail.com ---
Then I did another CC on the DB and this time it reported identical output but
at the bottom:

Finished: 0 problems corrected. 111 problems still present.

Im not sure how to proceed from there... Why so much errors about account
creation dates and such?  Previously I never had errors like that, but I must
be honest, last month I did a lot of cleanup in the database (renamed accounts,
changed transactions categories, created and deleted categories and reassigned
transactins to the categories, etc)

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

[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.

[dns2utf8 via KDE Bugzilla]

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

--- Comment #19 from dns2utf8  ---
Yes, all 3 are 64-bit.

The desktop uses an E3-1245 v3, the old laptop is an t400.
The new laptop with the problems is a t460s.

I noticed something odd:
1. open yakuake
2. split the terminal
3. open another tab
4. close and open yakuake
5. close the terminal
6. now you are on the second tab in the second split
7a. close and open yakuake
8a. you are still in the second split
7b. type something, should end up in the second split
8b. close and open and you are in the fist split

So depending upon if you type something after closing a tab, it works on my
t460s for one cycle.

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

[kmymoney4] [Bug 360938] Scheduled transactions entered in credit card (liability) have random descriptions populated

[via KDE Bugzilla]

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

--- Comment #13 from lp.allar...@gmail.com ---
Jack,  I managed to copy my "production" DB to a "testing" copy and performed a
check for consistency.  For whatever reason, it worked, and the output is
rather scary:

  * Opening date of Account 'Opening Balances' cannot be changed to support
transaction 'T13' post date.
  * Transaction 'T13' has a post date '01/01/09' before one of
the referenced account's opening date.
Referenced accounts: Opening Balances
The post date was not updated to '15/02/09'.
  * Transaction 'T001390' has a post date '01/01/09' before one of
the referenced account's opening date.
Referenced accounts: Opening Balances
The post date was not updated to '15/02/09'.
  * Transaction 'T10' post date '2009-02-15' is older than
opening date '2015-01-25' of account 'X'.
Account opening date updated.
  * Transaction 'T16' post date '2009-02-17' is older than
opening date '2009-02-18' of account 'X'.
Account opening date updated.
  * Transaction 'T19' post date '2009-02-21' is older than
opening date '2009-02-22' of account 'X'.
Account opening date updated.
  * Transaction 'T19' post date '2009-02-21' is older than
opening date '2009-02-22' of account 'X'.
Account opening date updated.
  * Transaction 'T40' post date '2009-02-26' is older than
opening date '2016-02-27' of account 'X'.
Account opening date updated.

 [cropped about 40 similar messages to the aboves]

Account opening date updated.
  * Transaction 'T000210' post date '2009-05-17' is older than
opening date '2010-03-05' of account 'X'.
Account opening date updated.
  * Transaction 'T000232' post date '2009-05-23' is older than
opening date '2014-05-11' of account 'X'.
Account opening date updated.
  * Transaction 'T000245' post date '2009-05-30' is older than
opening date '2009-05-31' of account 'X'.
Account opening date updated.
  * Transaction 'T000281' post date '2009-06-09' is older than
opening date '2009-06-10' of account 'X'.
Account opening date updated.
  * Transaction 'T000291' post date '2009-06-14' is older than
opening date '2015-01-25' of account 'X'.
Account opening date updated.
  * Transaction 'T000401' post date '2009-07-23' is older than
opening date '2015-02-01' of account 'X'.
Account opening date updated.
  * Transaction 'T000422' post date '2009-07-28' is older than
opening date '2015-01-18' of account 'X'.
Account opening date updated.
  * Transaction 'T000424' post date '2009-07-29' is older than
opening date '2015-01-25' of account 'X'.
Account opening date updated.
  * Transaction 'T000449' post date '2009-08-02' is older than
opening date '2015-01-25' of account 'X'.
Account opening date updated.
  * Transaction 'T000481' has a post date '13/08/09' before one of
the referenced account's opening date.
Referenced accounts: XXX
The post date was not updated to '23/10/09'.
  * Transaction 'T000482' post date '2009-08-15' is older than
opening date '2015-01-31' of account 'X'.
Account opening date updated.
  * Transaction 'T000492' post date '2009-08-22' is older than
opening date '2011-05-01' of account 'X'.
Account opening date updated.
  * Transaction 'T000496' post date '2009-08-24' is older than
opening date '2016-02-27' of account 'X'.
Account opening date updated.
  * Transaction 'T000497' post date '2009-08-24' is older than
opening date '2015-01-25' of account 'X'.
Account opening date updated.
  * Transaction 'T000497' post date '2009-08-24' is older than
opening date '2015-01-31' of account 'X'.
Account opening date updated.
  * Transaction 'T000577' post date '2009-09-18' is older than
opening date '2015-01-25' of account 'X'.
Account opening date updated.
  * Opening date of Account 'XX' cannot be changed to support transaction
'T000622' post date.
  * Transaction 'T000622' has a post date '10/10/09' before one of
the referenced account's opening date.
Referenced accounts: Xx
The post date was not updated to '23/10/09'.
  * Transaction 'T000630' post date '2009-10-13' is older than
opening date '2015-01-25' of account 'X'.
Account opening date updated.
  * Transaction 'T000630' post date 

[trojita] [Bug 361308] "apt-get update" warning "W: http://download.opensuse.org/repositories/home:/jkt-gentoo:/trojita/Debian_8.0/Release.gpg: Signature by key 62797E5BC0F3A65DCFB2F94D121EE1B7A6A3666

[Jan Kundrát via KDE Bugzilla]

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

Jan Kundrát  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #1 from Jan Kundrát  ---
Yeah, we are aware of this. Unfortunately, this is not about a key strength or
a key algorithm (we've already regenerated the key). It's about a hard-coded
constant in the OpenSuSE's Open Build Service's signing component which
specifies that the package signatures should use SHA1 as the hashing algorithm.

I've opened a bugreport at https://github.com/openSUSE/obs-sign/issues/5 .
Please note that the OBS is a hosted service and we cannot do anything to
change it.

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

[kmix] [Bug 361320] Sound Sliders appear on wrong screen when taskbar icon is clicked

[John Michalak via KDE Bugzilla]

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

--- Comment #3 from John Michalak  ---
(In reply to John Michalak from comment #2)
> (In reply to Christoph Feck from comment #1)
> > Which version of kmix are you using? It should be fixed since version 14.12.
> 
> john@john-IC780M-A2:~/the_odin_project/google-homepage > kmix -version
> Qt: 4.8.6
> KDE Development Platform: 4.14.2
> KMix: 4.5

``` uname -a
Linux john-IC780M-A2 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22
09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
```
Its the version included with a fully updated Linux Mint 17.3 installation...

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

[kmix] [Bug 361320] Sound Sliders appear on wrong screen when taskbar icon is clicked

[John Michalak via KDE Bugzilla]

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

--- Comment #2 from John Michalak  ---
(In reply to Christoph Feck from comment #1)
> Which version of kmix are you using? It should be fixed since version 14.12.

john@john-IC780M-A2:~/the_odin_project/google-homepage > kmix -version
Qt: 4.8.6
KDE Development Platform: 4.14.2
KMix: 4.5

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

[kscreenlocker] [Bug 361328] New: Kscreenlock locks screen instantly and ignores 'require password after' timeout

[via KDE Bugzilla]

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

Bug ID: 361328
   Summary: Kscreenlock locks screen instantly and ignores
'require password after' timeout
   Product: kscreenlocker
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: nothank...@mailinator.com
CC: bhus...@gmail.com, mgraess...@kde.org

Settings: [YES] Lock screen automatically after 5 minutes
Require password after locking: 5 sec
Lock screen on resume [YES]

Previously in Kscreenlock 5.5, the locked screen banner would appear and if you
moved your mouse within 5 second, it would close and return you to your desktop
without needing your password (expected behavior)

Now in Kscreenlock 5.6, settings have not changed but as soon as the screen
lock banner appears, the PC is locked, the 5 second timeout selected is
entirely ignored and you need a password to unlock it all the time now (this is
wrong behavior)

Reproducible: Always

Steps to Reproduce:
1. Follow setup in details
2. Leave screen for 5 minues
3. Move mouse when banner appears

Actual Results:  
Password is required for unlocking

Expected Results:  
Login request window should close automatically without password

Using Arch linux (not testing branches)

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

[frameworks-solid] [Bug 270808] KDE should spin-down external hard disks when 'safely removed'

[Soukyuu via KDE Bugzilla]

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

--- Comment #33 from Soukyuu  ---
Oh and all "udisksctl power-off /dev/sdx" does in my case is spin the HDD
down then up again.
OT: why can't I seem to find the vote link for this bug?

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

[frameworks-solid] [Bug 270808] KDE should spin-down external hard disks when 'safely removed'

[Soukyuu via KDE Bugzilla]

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

Soukyuu  changed:

   What|Removed |Added

 CC||chrno-sphe...@hotmail.com

--- Comment #32 from Soukyuu  ---
I do hope this will get fixed eventually, my external HDD makes unhealthy
screeching noises when I unplug it without letting it spin down. I can't
imagine it being healthy in the long run - especially since it seems to trigger
the "unexpected power loss" counter on S.M.A.R.T. statistics. 

The same HDD gracefully (and silently) spins down in windows.

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

[plasmashell] [Bug 361327] New: crash while trying to change output sound source

[RJ via KDE Bugzilla]

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

Bug ID: 361327
   Summary: crash while trying to change output sound source
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: ogldel...@mail.ru

Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb31a7800 (LWP 1594))]

Thread 9 (Thread 0xb160eb40 (LWP 1597)):
#0  0xb77b2f3d in __kernel_vsyscall ()
#1  0xb4e2817b in poll () from /lib/libc.so.6
#2  0xb714399d in poll (__timeout=-1, __nfds=1, __fds=0xb160e11c) at
/usr/include/bits/poll2.h:46
#3  _xcb_conn_wait (c=0x86c2b80, cond=0x86c2ba4, vector=0x0, count=0x0) at
xcb_conn.c:459
#4  0xb7145a9b in xcb_wait_for_event (c=0x86c2b80) at xcb_in.c:693
#5  0xb175a483 in QXcbEventReader::run (this=0x86d2c00) at
qxcbconnection.cpp:1229
#6  0xb510ac00 in QThreadPrivate::start (arg=0x86d2c00) at
thread/qthread_unix.cpp:331
#7  0xb4cdd2f5 in start_thread () from /lib/libpthread.so.0
#8  0xb4e3255e in clone () from /lib/libc.so.6

Thread 8 (Thread 0xb0098b40 (LWP 1605)):
#0  0xb77b2f3d in __kernel_vsyscall ()
#1  0xb4e2251b in read () from /lib/libc.so.6
#2  0xb4540005 in read (__nbytes=16, __buf=0xb0097fec, __fd=) at
/usr/include/bits/unistd.h:44
#3  g_wakeup_acknowledge (wakeup=0xb0c00ed8) at gwakeup.c:210
#4  0xb44fbbc6 in g_main_context_check (context=0xaf7004d8,
max_priority=2147483647, fds=0xaf702738, n_fds=1) at gmain.c:3632
#5  0xb44fc081 in g_main_context_iterate (context=context@entry=0xaf7004d8,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3837
#6  0xb44fc224 in g_main_context_iteration (context=0xaf7004d8, may_block=1) at
gmain.c:3901
#7  0xb5329a84 in QEventDispatcherGlib::processEvents (this=0xaf700468,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#8  0xb52d14c3 in QEventLoop::processEvents (this=0xb00981d8, flags=...) at
kernel/qeventloop.cpp:128
#9  0xb52d18fa in QEventLoop::exec (this=0xb00981d8, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb5105855 in QThread::exec (this=0x8768de8) at thread/qthread.cpp:503
#11 0xb692248f in QQmlThreadPrivate::run (this=0x8768de8) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#12 0xb510ac00 in QThreadPrivate::start (arg=0x8768de8) at
thread/qthread_unix.cpp:331
#13 0xb4cdd2f5 in start_thread () from /lib/libpthread.so.0
#14 0xb4e3255e in clone () from /lib/libc.so.6

Thread 7 (Thread 0xac7edb40 (LWP 1612)):
#0  0xb77b2f3d in __kernel_vsyscall ()
#1  0xb4ce2a2b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb4e3f4dd in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xae67e75a in cnd_wait (mtx=0x88b634c, cond=0x88b6364) at
../../../../../include/c11/threads_posix.h:159
#4  pipe_semaphore_wait (sema=0x88b634c) at
../../../../../src/gallium/auxiliary/os/os_thread.h:259
#5  radeon_drm_cs_emit_ioctl (param=0x88b60e8) at radeon_drm_winsys.c:653
#6  0xae67de55 in impl_thrd_routine (p=0x87d1148) at
../../../../../include/c11/threads_posix.h:87
#7  0xb4cdd2f5 in start_thread () from /lib/libpthread.so.0
#8  0xb4e3255e in clone () from /lib/libc.so.6

Thread 6 (Thread 0xaa844b40 (LWP 1613)):
#0  0xb77b2c76 in __vdso_clock_gettime ()
#1  0xb4e40002 in clock_gettime () from /lib/libc.so.6
#2  0xb51a478c in qt_clock_gettime (ts=0xaa843f48, clock=) at
tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#5  0xb5327501 in QTimerInfoList::updateCurrentTime (this=0xa9f0289c) at
kernel/qtimerinfo_unix.cpp:84
#6  0xb53279b4 in QTimerInfoList::timerWait (this=0xa9f0289c, tm=...) at
kernel/qtimerinfo_unix.cpp:381
#7  0xb5328ed1 in timerSourcePrepareHelper (timeout=0xaa84403c, src=0xa9f02868)
at kernel/qeventdispatcher_glib.cpp:127
#8  timerSourcePrepare (source=0xa9f02868, timeout=0xaa84403c) at
kernel/qeventdispatcher_glib.cpp:160
#9  0xb44fb65b in g_main_context_prepare (context=0xa9f004d8,
priority=0xaa844098) at gmain.c:3442
#10 0xb44fbffc in g_main_context_iterate (context=context@entry=0xa9f004d8,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3820
#11 0xb44fc224 in g_main_context_iteration (context=0xa9f004d8, may_block=1) at
gmain.c:3901
#12 0xb5329a84 in QEventDispatcherGlib::processEvents (this=0xa9f00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#13 0xb52d14c3 in QEventLoop::processEvents (this=0xaa8441d8, flags=...) at
kernel/qeventloop.cpp:128
#14 0xb52d18fa in QEventLoop::exec (this=0xaa8441d8, flags=...) at
kernel/qeventloop.cpp:204
#15 0xb5105855 in QThread::exec (this=0x8948a68) at thread/qthread.cpp:503
#16 0xb692248f in QQmlThreadPrivate::run (this=0x8948a68) at

[digikam] [Bug 361275] Compile time error: undefined reference while linking renamecustomizertest

[Lukáš Karas via KDE Bugzilla]

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

--- Comment #5 from Lukáš Karas  ---
No. When I compile it by these instructions, it fails too. On linking
renamecustomizertest...

Are you able to reproduce? I can try to prepare Docker image if you will have
problems to reproduce this bug...

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

[kdialog] [Bug 323650] KDialog incredibly slow to respond

[via KDE Bugzilla]

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

--- Comment #22 from tomi.uran...@gmail.com ---
I news on this? Makes it impossible to attach any files when the app itself is
using KDIALOG

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

[LabPlot2] [Bug 361326] New: Unable to select curves by clicking on it.

[Anu via KDE Bugzilla]

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

Bug ID: 361326
   Summary: Unable to select curves by clicking on it.
   Product: LabPlot2
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: frontend
  Assignee: alexander.se...@web.de
  Reporter: anu22mit...@gmail.com

When I create a new worksheet > new x-y plot  followed by adding:
--> two x-y curves from a mathematical equation: I am only able to select the
second curve by directly clicking on it, clicking on the first curve doesn't
highlight it.
--> three x-y curves from mathematical equation: I am able to select only the
third curve by directly clicking on it, clicking on the other two curve doesn't
highlight them.
--> similar is the same with four curves, only the last curve can be selected
by clicking on it.
Is it suppose to be in this manner?

Reproducible: Always

Steps to Reproduce:
1.Create new worksheet
2.Add new > x-y plot
3.Under xy plot add new> x-y curves from mathematical equation more than one.

Actual Results:  
Unable to select the curve by clicking on it.

Expected Results:  
Whichever curve has been selected by clicking on it must get highlighted.

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

[krita] [Bug 361325] New: Immense problems and inconsistencies in shortcut dialog, changes in shortcuts are not saved too

[Raghavendra kamath via KDE Bugzilla]

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

Bug ID: 361325
   Summary: Immense problems and inconsistencies in shortcut
dialog, changes in shortcuts are not saved too
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: raghavendr.ra...@gmail.com

There are some problems and inconsistencies in the shortcut dialog box of krita
3.0 git master
the problems are as follows:

1) The shortcuts which are changed don't get saved or implemented.
2) To work around this I tried to save the changed scheme by pressing save/load
button The browse file dialog shows home folder, ( this is not in the resources
folder so I doubt it s supposed to get loaded next time I start krita) I
browsed to resource folder and saved it .
3) As expected the shortcut scheme I saved didn't get loaded so I pressed load
shortcut and then browsed to the place where I saved it , but to my dismay the
file dialog doesn't show it , the file type filter is "Shortcuts" and the file
that is saved doesn't have any extension.
4) Now in a bid to save my changes I tried by pressing the "new" button in the
shortcut dialog it gave me a popup window to input the name for this scheme, I
added a name and saved it , the changes were applied. but
5) next time i load krita this new shortcut scheme is not loaded so my changes
are again lost

To add to this there is also a crash when we cancel the save and load dialog, I
have reported 
that in other bug report here -> https://bugs.kde.org/show_bug.cgi?id=360595

I really wish this bug gets solved and there is some clarity in handling
keyboard shortcuts. The concept of custom shortcut scheme is really nice and
good , but these bugs hamper the newly implemented system.

Let me know if you need any more details.

P.S. I am marking this major as shortcuts are integral part and right now
changing them or doing anything is kind of confusing and buggy, if you guys
feel it to be classified as normal you may do so 

thank you



Reproducible: Always

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

[plasmashell] [Bug 360219] Right Click opens files

[Eike Hein via KDE Bugzilla]

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

--- Comment #5 from Eike Hein  ---
Against the "Folder" component of product "plasmashell".

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

[plasmashell] [Bug 360219] Right Click opens files

[Florian Röhrer via KDE Bugzilla]

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

--- Comment #4 from Florian Röhrer  ---
I use single click. For the future...where should i have reported this bug?

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

[plasma-pa] [Bug 361324] New: Update kradio4 --> kradio5 and integrate with plasma5

[PGillespie via KDE Bugzilla]

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

Bug ID: 361324
   Summary: Update kradio4  --> kradio5 and integrate with plasma5
   Product: plasma-pa
   Version: 5.5.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: vtp...@myfairpoint.net

Since radiotray stopped working on kubuntu 16.04 I've been using kradio4.

It doesn't appear to be an official component of plasma5 but I'd like to see it
added. It's a great piece of software.

Lastly, the tray icon for kradio4 is ***ghastly*** -- sort of a "Walking Dead"
Van Gogh ear (after it was cut off). Who wants to see somebody's disembodied
ear on their desktop?

I replaced all the icons (laboriously) so that it played well with Breeze.

Would also like to see it more tightly integrated with the plasma-pa widget (on
top of everything else you're doing).

Reproducible: Always




Kernel: 4.4.0-16-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.4
   Distro: Ubuntu 16.04 xenial

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

[plasmashell] [Bug 361202] Taskbar unusable after placing a widget into it

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Eike Hein  ---
Can you provide a screenshot of what you mean by widget and what you mean by
the last item that is brought up?

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

[ksnapshot] [Bug 361323] New: ksnapshot "Send To..." button crash

[Chris Kelling via KDE Bugzilla]

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

Bug ID: 361323
   Summary: ksnapshot "Send To..." button crash
   Product: ksnapshot
   Version: 0.8.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ase...@kde.org
  Reporter: kelli...@gmail.com

Application: ksnapshot (0.8.2)
KDE Platform Version: 4.14.18
Qt Version: 4.8.7
Operating System: Linux 4.4.5-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
I was trying to send the capture to the printer.  I click on Send To... and the
application crashes - What I was doing when the application crashed:

The crash can be reproduced every time.

-- Backtrace:
Application: KSnapshot (ksnapshot), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f33df121900 (LWP 2316))]

Thread 3 (Thread 0x7f33be9cd700 (LWP 2317)):
#0  0x7f33d5dffbbc in g_main_context_check () at /lib64/libglib-2.0.so.0
#1  0x7f33d5e00110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f33d5e0027c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f33db0b4e7e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQtCore.so.4
#4  0x7f33db083131 in
QEventLoop::processEvents(QFlags) () at
/lib64/libQtCore.so.4
#5  0x7f33db0834a5 in
QEventLoop::exec(QFlags) () at
/lib64/libQtCore.so.4
#6  0x7f33daf72a99 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x7f33db063203 in QInotifyFileSystemWatcherEngine::run() () at
/lib64/libQtCore.so.4
#8  0x7f33daf7538c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#9  0x7f33dacd360a in start_thread () at /lib64/libpthread.so.0
#10 0x7f33da172a4d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f33a21f6700 (LWP 2321)):
#0  0x7f33dacd8b10 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f33daf758f6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQtCore.so.4
#2  0x7f33c1e9e888 in KIPIPlugins::KPRawThumbThread::run() () at
/lib64/libkipiplugins.so.4.14.0
#3  0x7f33daf7538c in QThreadPrivate::start(void*) () at
/lib64/libQtCore.so.4
#4  0x7f33dacd360a in start_thread () at /lib64/libpthread.so.0
#5  0x7f33da172a4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f33df121900 (LWP 2316)):
[KCrash Handler]
#6  0x7f33d6cd0431 in QCA::MessageAuthenticationCode::clear() () at
/lib64/libqca.so.2
#7  0x7f33d6cd1f05 in
QCA::MessageAuthenticationCode::MessageAuthenticationCode(QString const&,
QCA::SymmetricKey const&, QString const&) () at /lib64/libqca.so.2
#8  0x7f33a30dfa9f in
KIPIShwupPlugin::SwConnector::setupRequest(KIO::TransferJob*, QString const&,
QString const&, QString const&, QString const&, QString const&, bool) () at
/usr/lib64/kde4/kipiplugin_shwup.so
#9  0x7f33a30e09a0 in KIPIShwupPlugin::SwConnector::getRestServiceURL() ()
at /usr/lib64/kde4/kipiplugin_shwup.so
#10 0x7f33a30db5d1 in KIPIShwupPlugin::SwWindow::SwWindow(QString const&,
QWidget*) () at /usr/lib64/kde4/kipiplugin_shwup.so
#11 0x7f33a30d8ebf in KIPIShwupPlugin::Plugin_Shwup::slotExport() () at
/usr/lib64/kde4/kipiplugin_shwup.so
#12 0x7f33db098a50 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /lib64/libQtCore.so.4
#13 0x7f33dbfc69d2 in QAction::triggered(bool) () at /lib64/libQtGui.so.4
#14 0x7f33dbfc7d33 in QAction::activate(QAction::ActionEvent) () at
/lib64/libQtGui.so.4
#15 0x7f33dc424f7d in
QMenuPrivate::activateCausedStack(QList const&, QAction*,
QAction::ActionEvent, bool) () at /lib64/libQtGui.so.4
#16 0x7f33dc429369 in QMenuPrivate::activateAction(QAction*,
QAction::ActionEvent, bool) () at /lib64/libQtGui.so.4
#17 0x7f33dc023130 in QWidget::event(QEvent*) () at /lib64/libQtGui.so.4
#18 0x7f33dc42d5eb in QMenu::event(QEvent*) () at /lib64/libQtGui.so.4
#19 0x7f33dbfcc93c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQtGui.so.4
#20 0x7f33dbfd3956 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQtGui.so.4
#21 0x7f33dcd5860a in KApplication::notify(QObject*, QEvent*) () at
/lib64/libkdeui.so.5
#22 0x7f33db0848bd in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /lib64/libQtCore.so.4
#23 0x7f33dbfd2f5d in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at
/lib64/libQtGui.so.4
#24 0x7f33dc04e1ec in QETWidget::translateMouseEvent(_XEvent const*) () at
/lib64/libQtGui.so.4
#25 0x7f33dc04c21d in QApplication::x11ProcessEvent(_XEvent*) () at
/lib64/libQtGui.so.4
#26 0x7f33dc075299 in x11EventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQtGui.so.4
#27 

[plasmashell] [Bug 360219] Right Click opens files

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #3 from Eike Hein  ---
Do you use single click or double click?

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

[plasmashell] [Bug 360219] Right Click opens files

[Eike Hein via KDE Bugzilla]

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

--- Comment #2 from Eike Hein  ---
Folder bugs can't be fixed if they're reported against the wrong component and
the reports aren't seen.

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

[plasmashell] [Bug 360578] Desktop folder view icons not movable if widgets are locked

[Eike Hein via KDE Bugzilla]

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

Eike Hein  changed:

   What|Removed |Added

   Assignee|se...@kde.org   |h...@kde.org
 CC||h...@kde.org,
   ||plasma-b...@kde.org
  Component|Desktop Containment |Folder

--- Comment #2 from Eike Hein  ---
Sorry, I missed this since it was reported against the wrong component.

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

[plasmashell] [Bug 360578] Desktop folder view icons not movable if widgets are locked

[Eike Hein via KDE Bugzilla]

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

--- Comment #3 from Eike Hein  ---
I can't reproduce it though -- moving icons works fine with widgets locked for
me.

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

[plasmashell] [Bug 360226] Desktop icons in Folder View sometimes doesnt snap to the dragged destination

[Eike Hein via KDE Bugzilla]

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

--- Comment #4 from Eike Hein  ---
Indeed, I don't understand your report - with widgets locked, icons can still
be selected (including rubberband) and moved. That's normal.

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

[kalarm] [Bug 361115] daylight savings time is handled incorrectly

[Hauke Laging via KDE Bugzilla]

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

--- Comment #2 from Hauke Laging  ---
(In reply to David Jarvie from comment #1)
> Which version of KDE and KAlarm are you using?

Version 2.11.4-5ak (I could not select that one in the bug report form).

KDE Frameworks 5.20.0
Qt 5.5.1 (kompiliert gegen 5.5.1)
Das xcb Fenstersystem

> Which time zone is configured as the default for KAlarm?

Europe/Berlin

> Do you use KAlarm's default time zone for your alarms? To verify this, open
> an alarm and if you're using the default, no time zone will be listed beside
> the Time Zone button.

Nothing is listed there for both existing and new alarms. I have to click on
"more options" (in German) in order to see the time zone setting at all. And I
don't think I ever clicked that before.

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

[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.

[silentz0r via KDE Bugzilla]

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

--- Comment #18 from silentz0r  ---
(In reply to dns2utf8 from comment #17)
> (In reply to dns2utf8 from comment #16)
> > This bug appeared on my laptop again.
> > 
> > It works on the desktop.
> > 
> > Both have the latest Arch Linux with yakuake 3.0.2
> 
> I think it is a race condition, because I noticed it works on all my slow
> computers but not on the new ones.

Are they both 64-bit? Do they both use the same packages?

I've had this issue on my 2009 and 2015 laptops, as well as an Arch VM with KDE
installed. It's never gone away.

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

[plasmashell] [Bug 359764] Panel doesn't allow resizing

[via KDE Bugzilla]

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

bzugme...@gmail.com changed:

   What|Removed |Added

 CC||bzugme...@gmail.com

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

[yakuake] [Bug 356853] Wrong split is focused when showing/hiding the terminal.

[dns2utf8 via KDE Bugzilla]

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

--- Comment #17 from dns2utf8  ---
(In reply to dns2utf8 from comment #16)
> This bug appeared on my laptop again.
> 
> It works on the desktop.
> 
> Both have the latest Arch Linux with yakuake 3.0.2

I think it is a race condition, because I noticed it works on all my slow
computers but not on the new ones.

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

[kwin] [Bug 361274] Special Application/Window Settings Inconsistent

[PGillespie via KDE Bugzilla]

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

--- Comment #4 from PGillespie  ---
Hi Thomas, in reference to gthumb, both activities are correctly listed under
altf3.

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

[kwin] [Bug 361154] Running native OpenGL games - with compositing enabled - breaks X11 Plasma 5.6.0 Window Decorations

[Bob Wya via KDE Bugzilla]

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

--- Comment #13 from Bob Wya  ---
(In reply to Thomas Lübking from comment #11)
> (In reply to Bob Wya from comment #9)
> 
> > glxgears -fullscreen
> > doesn't actually run fullscreen
> 
> you can "kstart5 --fullscreen glxgears"

Yes it's fullscreen now. No compositing issues (during or post).

> And depending on your findings (and since you're on gentoo ;-):
> https://github.com/luebking/starfield
> 
> Sorry for advertising, but "starfield fullscreen" (run from the build dir
> since it looks for the star textures in . only)
> a) should work (fullscreenwise) and
> b) it's a pretty dumb implementation on the fixed function pipeline, yet in
> comparism to glxgears uses textures (in case that should be relevant)

Damn spam again :-) I like it so much - I've packaged it up for my Layman
Overlay. Seriously looks quite cool across my dual-monitor setup :-)

Sadly (or not sadly) there are still no compositing issues (during or post).

> > I can disable compositing for say the Steam client (in a kwin rule) and
> > launching a Steam game - does not cause the compositing issues. Is that what
> > you're asking?
> 
> Yes, because it means it's not related to 361091, ie.
> _NET_WM_BYPASS_COMPOSITOR and whatever rphl encounters in this case.

Sure. Seems to be a separate issue. May not even be a "thing" if Steffen
doesn't having matching symptoms.

Every second Nvidia driver appears to have some annoying bug in it - that
breaks something for me (like suspend-resume). Just now I've even got access to
TTY consoles (finally) - damn UEFI!! So I'm reluctant to change versions... 8-)

Thanks

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

[kwin] [Bug 361274] Special Application/Window Settings Inconsistent

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

  Component|general |activities

--- Comment #3 from Thomas Lübking  ---
Since only one system is affected, I sense troubles reg. the activity manager -
how many activities are listed in the alt+f3 menu ("set on activity ...")

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

[plasma-pa] [Bug 353232] Audio Volume system settings regression from Kmix: Moving audio to a different output device.

[via KDE Bugzilla]

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

quentin.de...@gmail.com changed:

   What|Removed |Added

 CC||quentin.de...@gmail.com

--- Comment #5 from quentin.de...@gmail.com ---
Great!!! Thanks!

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