[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Fraser_Bell via KDE Bugzilla]

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

--- Comment #142 from Fraser_Bell  ---
>Note that 5.5 brings an activity pager, which is one step closer to solving 
>the real issue of:

... but, it is *not* the cube. ;-)

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

[telepathy] [Bug 349851] Cannot access group chat from the systray "Presence" icon

[Kenneth Perry via KDE Bugzilla]

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

Kenneth Perry  changed:

   What|Removed |Added

 CC||thothone...@gmail.com

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

[kmail2] [Bug 333611] error on decoding PGP-encoded messages

[Andrew Gaydenko via KDE Bugzilla]

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

Andrew Gaydenko  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #21 from Andrew Gaydenko  ---
The Arch Linux team has kindly applied the patch, and now I can verify the
issue is resolved. Thanks to the KDE team!

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

[kjumpingcube] [Bug 357409] New: KDEInit could not launch '/usr/bin/kjumpingcube'

[André Marcelo Alvarenga via KDE Bugzilla]

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

Bug ID: 357409
   Summary: KDEInit could not launch '/usr/bin/kjumpingcube'
   Product: kjumpingcube
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: iandw...@gmail.com
  Reporter: alvare...@kde.org
CC: kde-games-b...@kde.org

This error is displayed in a dialog when I close Kjumpingcube lauched from
Kickoff and Kicker .

Reproducible: Always




Using Manjaro Linux - KDE Applications 15.12 and Frameworks 5.17.

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

[kblocks] [Bug 357408] New: KDEInit could not launch '/usr/bin/kblocks'

[André Marcelo Alvarenga via KDE Bugzilla]

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

Bug ID: 357408
   Summary: KDEInit could not launch '/usr/bin/kblocks'
   Product: kblocks
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: squall.leonhart@gmail.com
  Reporter: alvare...@kde.org
CC: kde-games-b...@kde.org

This error is displayed in a dialog when I close Kblocks lauched from Kickoff
and Kicker .

Reproducible: Always




Using Manjaro Linux - KDE Applications 15.12 and Frameworks 5.17.

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

[plasmashell] [Bug 341951] Popup notification freeze plasmashell when in standby mode/lock screen

[Johannes Pfrang via KDE Bugzilla]

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

Johannes Pfrang  changed:

   What|Removed |Added

 CC||johannespfrang+...@gmail.co
   ||m

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

[rkward] [Bug 357402] New: Add UI for identify() and / or locator() to graphics windows

[Thomas Friedrichsmeier via KDE Bugzilla]

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

Bug ID: 357402
   Summary: Add UI for identify() and / or locator() to graphics
windows
   Product: rkward
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: rkward-de...@kde.org
  Reporter: thomas.friedrichsme...@ruhr-uni-bochum.de

Subject says all. identify() and locator() are pretty useful, but
hard-to-discover features, could gain a tool button.

In fact, for RK() device, it may also be possible to show coordinates
implicitly, while moving the mouse cursor?

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

[korganizer] [Bug 353118] KDEInit could not launch '/usr/bin/korganizer'

[André Marcelo Alvarenga via KDE Bugzilla]

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

André Marcelo Alvarenga  changed:

   What|Removed |Added

 CC||alvare...@kde.org

--- Comment #1 from André Marcelo Alvarenga  ---
Hi.

I can reproduce this bug with Korganizer released with KDE Applications 15.08,
but I can't reproduce this bug with 5.1 version (KDE Applications 15.12).

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

[muon] [Bug 357245] Don't try to fetch updates if such a privilege isn't granted

[David Edmundson via KDE Bugzilla]

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

--- Comment #11 from David Edmundson  ---
Easiest way to test is to change your   to auth_admin

As for fixing Kauth should report back whether auth is required or not in
::status()

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

[ksnapshot] [Bug 309335] KSnapshot should not bind "new screenshot" to the space key

[Vladimir Panteleev via KDE Bugzilla]

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

Vladimir Panteleev  changed:

   What|Removed |Added

 CC||thecybersha...@gmail.com

--- Comment #2 from Vladimir Panteleev  ---
Agreed. This behavior/code is actually redundant because the "Take a New
Snapshot" button is already focused by default, thus Space will continue
working as a "new snapshot" key until the user changes focus.

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

[plasmashell] [Bug 357405] Wrong icon in battery widget tooltip

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
   Assignee|k...@privat.broulik.de   |visual-des...@kde.org
  Component|Battery Monitor |Theme - Breeze

--- Comment #1 from Kai Uwe Broulik  ---
There's some icons missing in the Breeze theme there.

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

[korganizer] [Bug 353118] KDEInit could not launch '/usr/bin/korganizer'

[André Marcelo Alvarenga via KDE Bugzilla]

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

--- Comment #2 from André Marcelo Alvarenga  ---
(In reply to André Marcelo Alvarenga from comment #1)
> Hi.
> 
> I can reproduce this bug with Korganizer released with KDE Applications
> 15.08, but I can't reproduce this bug with 5.1 version (KDE Applications
> 15.12).

Using Manjaro Linux 15.12 (KDE Applications 15.12, Plasma 5.5.2 and Frameworks
5.17).

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

[krita] [Bug 356245] [Krita Animation Beta] Animation playback behaves differently when moving the brush tool on the canvas.

[Dmitry Kazakov via KDE Bugzilla]

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

Dmitry Kazakov  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/call
   |a/9fda1f749e9392a644b4b71c5 |igra/bd79d3ca3fa17c4a9e5f0a
   |6e5cf76ae4832bb |80c6265d96ca19a0a0

--- Comment #5 from Dmitry Kazakov  ---
Git commit bd79d3ca3fa17c4a9e5f0a80c6265d96ca19a0a0 by Dmitry Kazakov.
Committed on 01/01/2016 at 17:47.
Pushed by dkazakov into branch 'krita-animation-pentikainen'.

Implemented a "Drop Frames" mode for Krita and made it default option

Now you can switch on the "Drop Frames" mode in the Animation Docker
to ensure your animation is playing with the requested frame rate,
even when the GPU cannot handle this amount of data to be shown.

TODO: we still need an icon for this feature! Atm it uses "Auto Frame" icon!
CC:kimages...@kde.org

# Conflicts:
#krita/ui/canvas/kis_animation_player.cpp
#krita/ui/canvas/kis_animation_player.h
#krita/ui/kis_config_notifier.cpp

M  +57   -6krita/plugins/extensions/dockers/animation/animation_docker.cpp
M  +3-0krita/plugins/extensions/dockers/animation/animation_docker.h
M  +1-0   
krita/plugins/extensions/dockers/animation/kis_animation_utils.cpp
M  +1-0krita/plugins/extensions/dockers/animation/kis_animation_utils.h
M  +10   -0krita/plugins/extensions/dockers/animation/wdg_animation.ui
M  +122  -29   krita/ui/canvas/kis_animation_player.cpp
M  +2-2krita/ui/canvas/kis_animation_player.h
M  +16   -1krita/ui/kis_config.cc
M  +4-1krita/ui/kis_config.h
M  +15   -1krita/ui/kis_config_notifier.cpp
M  +8-1krita/ui/kis_config_notifier.h

http://commits.kde.org/calligra/bd79d3ca3fa17c4a9e5f0a80c6265d96ca19a0a0

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

[plasmashell] [Bug 357411] Double arrows in applications list if legacy Plasma svgs are in theme

[via KDE Bugzilla]

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

--- Comment #1 from obno...@gmail.com ---
Created attachment 96402
  --> https://bugs.kde.org/attachment.cgi?id=96402=edit
Example toolbar-icons/go.svg file to trigger the bug

Save it as /toolbar-icons/go.svg to see the problem in Kickoff.

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

[kdenlive] [Bug 357397] Image Sequence (with period in filename) missing upon re-opening project

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

Jean-Baptiste Mardelle  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #2 from Jean-Baptiste Mardelle  ---
Thanks for the report. Indeed, I found several major bugs in slideshows that I
just fixed in git master and 15.12 branch. Please test again and let me know...

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

[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too

[Jagadguru via KDE Bugzilla]

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

--- Comment #35 from Jagadguru  ---
DItto Comment 33.

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

[muon] [Bug 357245] Don't try to fetch updates if such a privilege isn't granted

[Aleix Pol via KDE Bugzilla]

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

Aleix Pol  changed:

   What|Removed |Added

Summary|spurious PackageKit |Don't try to fetch updates
   |authentication request for  |if such a privilege isn't
   |remote session  |granted

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

[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too

[Jagadguru via KDE Bugzilla]

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

Jagadguru  changed:

   What|Removed |Added

 CC||jguru...@gmail.com

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

[muon] [Bug 357245] Don't try to fetch updates if such a privilege isn't granted

[Aleix Pol via KDE Bugzilla]

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

--- Comment #10 from Aleix Pol  ---
I'll see what I can do. Do you know of an easy way to reproduce? That would
greatly help to provide a fix.

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

[kalarm] [Bug 356048] kalarm always crashes when changing alarms

[Kevin via KDE Bugzilla]

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

--- Comment #1 from Kevin  ---
I figured out how to reproduce this bug as a new user with a 100% default home
directory. All one needs to do is go to
System Settings -> Regional Settings -> Spell Check
and check the
"automatic spell checking enabled by default"
box. Once this is done, create an alarm in kalarm. Once the alarm is created,
try to edit it. Kalarm will crash.

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

[kalarm] [Bug 356048] kalarm always crashes when changing alarms

[Kevin via KDE Bugzilla]

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

Kevin  changed:

   What|Removed |Added

 CC||kjs...@gmail.com

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

[plasmashell] [Bug 357411] New: Double arrows in applications list if legacy Plasma svgs are in theme

[via KDE Bugzilla]

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

Bug ID: 357411
   Summary: Double arrows in applications list if legacy Plasma
svgs are in theme
   Product: plasmashell
   Version: 5.5.2
  Platform: openSUSE RPMs
   URL: http://i.imgur.com/ZmFjY9p.png
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: obno...@gmail.com
CC: plasma-b...@kde.org

See URL for screenshot.

Since 5.5.0, Kickoff shows two kind of arrows on every listitem in its
applications view. It shows left arrows from both widgets/arrows.svg and
toolbar-icons/go.svg if it exists. The issue seems to stem from
quickgit.kde.org/?p=plasma-desktop.git=blob=applets/kickoff/package/contents/ui/ApplicationsView.qml
line 218. This was not the case in 5.4.3 and earlier versions.

The issue is not visible using Breeze because it does not provide the
toolbar-icons folder.

Reproducible: Always

Steps to Reproduce:
1. Use a theme that provides toolbar-icons/go.svg [go-next]
2. Open Kickoff and switch to the Applications tab

Actual Results:  
Two kinds of arrows are used for every listitem

Expected Results:  
Only one arrow is used at most.

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

[kde] [Bug 357412] New: KDE user swap crash

[laurie jarden via KDE Bugzilla]

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

Bug ID: 357412
   Summary: KDE user swap crash
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: laur...@internode.on.net

kde crashed when trying to swap user to a user already setup in system.
only two users had been setup.
this type of crash happened on first user swap after last update with
tumbleweed.

Reproducible: Always

Steps to Reproduce:
1.start machine and login to tumbleweed (kernel 4.3.3.2-default, Plasma5)
2.start new user from application launcher menu
3.swap back to original user.

Actual Results:  
KDE user interface crash occurs.
sometimes recovers after closing bug dialog box, but mostly not which requires
a reboot.
sometimes recovers by holding keys Ctrl+Alt and pressing backspace twice.

Expected Results:  
menu strip covering middle of screen showing selection of users to swap to.

Mainboard: ASUS M5A99FX-PRO Rev 2.0 rev.1.01
CPU: AMD FX-8350 Black edition
HDD: Caviar Black, 2000 GB 7200rpm Sata II
Memory: HyperX Fury RED Kit of 2 (DDR3,  1866 Mhz, 1.5v) 16Gb
mouse: Logiteck MK120
Monitor 1: Benq 27" M2700HD
Monitor 2: Dell 22" P2210t
Videocard: Gigabyte (ATI Radeon R7 260X) GV-R726XOC-2GD Rev.3

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Fraser_Bell via KDE Bugzilla]

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

--- Comment #143 from Fraser_Bell  ---
>I totally disagree with your approach to customers' needs / requests . 
>Those who are successful know very well who their REAL customer is as well as 
>their real needs and their real options. When you nix them you nix your future 
>.

Uh, we are not "customers", we are "users".

This is not a Commercial Enterprise, it is a Community of Programmers (Devs)
who volunteer their time and efforts to create something *they* want.  If we
want to use it -- become users -- they let us.  They do not try to *sell* it to
us or push it on us.

We get what they give us, unless we want to develop our *own* desktop.

Since there seem to be so many here who want the different Wallpapers and --
especially -- the different Widgets, and since most seem to want it back in
Virtual Desktops the same way it was in KDE4, why not do the same as was done
with OpenOffice?

When they could not agree, when politics got in the way of development, they
split out into LibreOffice.

KDE4 could be forked to an alternative desktop.

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

[systemsettings] [Bug 357404] New: Setting about single/double click to open files/folders does no effect until I restart Dolphin

[Dr . Chapatin via KDE Bugzilla]

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

Bug ID: 357404
   Summary: Setting about single/double click to open
files/folders does no effect until I restart Dolphin
   Product: systemsettings
   Version: 5.5.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_mouse
  Assignee: unassigned-b...@kde.org
  Reporter: yy...@gmx.com
CC: unassigned-b...@kde.org

Setting about single/double click to open files/folders does no effect until I
restart Dolphin

Reproducible: Always

Steps to Reproduce:
1.Open dolphin
2.open kde settings panel, open mouse settings module and change the mouse
setting to open files with single or double click
3. Test the new setting in Dolphin file manager

Actual Results:  
Previous mouse setting is still doing effect. I need restart Dolphin to the new
setting works.

Expected Results:  
I think correct behavior is the new mouse setting does effect immediately
without restart Dolphin.

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

[ksmserver] [Bug 357413] New: kde crash on user swap

[laurie jarden via KDE Bugzilla]

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

Bug ID: 357413
   Summary: kde crash on user swap
   Product: ksmserver
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: laur...@internode.on.net

Application: ksmserver ()
 (Compiled from sources)
Qt Version: 5.5.1
Operating System: Linux 4.3.3-2-default x86_64
Distribution: "openSUSE Tumbleweed (20151229) (x86_64)"

-- Information about the crash:
graphic user interface crashes and replaced with black screen and crash report
assistant when attempting to swap user

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f60e1de6700 (LWP 10669)):
#0  0x7f6104fcf07f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f60e2fcdd6a in ?? () from /usr/lib64/dri/radeonsi_dri.so
#2  0x7f60e2fcd597 in ?? () from /usr/lib64/dri/radeonsi_dri.so
#3  0x7f6104fc94a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7f610f183bdd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f60ec8a9700 (LWP 10671)):
#0  0x7f61036a14d4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f610365d910 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f610365e193 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f610365e36c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f6109d4852b in QEventDispatcherGlib::processEvents
(this=0x7f60b8209ae0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f6109cf263a in QEventLoop::exec (this=this@entry=0x7f60ec8a8c70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f6109b1eb1c in QThread::exec (this=this@entry=0x12b2060) at
thread/qthread.cpp:503
#7  0x7f610d3379a5 in QQmlThreadPrivate::run (this=0x12b2060) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#8  0x7f6109b2394f in QThreadPrivate::start (arg=0x12b2060) at
thread/qthread_unix.cpp:331
#9  0x7f6104fc94a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f610f183bdd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f610f83b940 (LWP 9305)):
[KCrash Handler]
#6  ref (this=0x4) at /usr/include/qt5/QtCore/qrefcount.h:54
#7  toQString (this=) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4string_p.h:84
#8  toQString (this=) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4string_p.h:145
#9  QV4::Heap::StringObject::StringObject (this=,
engine=0x1260510, val=...) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4stringobject.cpp:91
#10 0x7f610d1fc885 in alloc (arg2=..., arg1=0x1260510, this=) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4mm_p.h:126
#11 QV4::ExecutionEngine::newStringObject (this=0x1260510, value=...) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4engine.cpp:557
#12 0x7f610d29075e in QV4::Runtime::getProperty (engine=0x1260510,
object=..., nameIndex=) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4runtime.cpp:682
#13 0x7f610ce3f0b5 in ?? ()
#14 0x012a6220 in ?? ()
#15 0x7211aa50 in ?? ()
#16 0x00040003 in ?? ()
#17 0x7f610d28f393 in call (d=, this=) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4object_p.h:305
#18 QV4::RuntimeHelpers::objectDefaultValue (object=0x7211aa50,
typeHint=) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4runtime.cpp:408
#19 0x7f610d236b7a in QV4::SimpleScriptFunction::call (that=, callData=) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4functionobject.cpp:564
#20 0x7f610d31dd2e in call (d=0x7f60d7e83008, this=) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4object_p.h:305
#21 QQmlJavaScriptExpression::evaluate (this=this@entry=0x10d4110,
context=, function=..., callData=callData@entry=0x7f60d7e83008,
isUndefined=isUndefined@entry=0x7211ac88) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/qqmljavascriptexpression.cpp:158
#22 0x7f610d31e23d in QQmlJavaScriptExpression::evaluate
(this=this@entry=0x10d4110, context=, function=...,
isUndefined=isUndefined@entry=0x7211ac88) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/qqmljavascriptexpression.cpp:116
#23 0x7f610d3246e4 in QQmlBinding::update (this=0x10d40f0, flags=...) at

[kaffeine] [Bug 151123] kaffeine showing green line

[Jaromír Cápík via KDE Bugzilla]

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

Jaromír Cápík  changed:

   What|Removed |Added

 CC||jaromir.ca...@email.cz

--- Comment #3 from Jaromír Cápík  ---
Still present in 1.2.2.

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

[kate] [Bug 356852] Kate's printing schema prints white on white when Breeze Dark color setting is selected

[via KDE Bugzilla]

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

lnx...@westlot.net changed:

   What|Removed |Added

 CC||lnx...@westlot.net

--- Comment #1 from lnx...@westlot.net ---
This happens to me as well since the upgrade Kubuntu 15.10 with Plasma 5.  This
also happens on actual printouts to paper..  The header and footer are both the
proper black print, but the body of the printout is light grey.

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

[krunner] [Bug 357406] New: CRASH when I try to run kwrite using KRunner

[Piotr Mierzwinski via KDE Bugzilla]

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

Bug ID: 357406
   Summary: CRASH when I try to run kwrite using KRunner
   Product: krunner
   Version: 5.5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: piotr.mierzwin...@gmail.com

Application: krunner (5.5.1)

Qt Version: 5.5.1
Operating System: Linux 4.3.3-2-default i686
Distribution: "openSUSE Tumbleweed (20151229) (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
Just after Plasma5 started
1. Invoke Alt+F2
2. type kwrite and ENTER
CRASH

This is not happen everytime. Application kwrite is installed.
In this start of system plasma session was restored. In previous were running:
- first desktop: firefox, konsole
- second desktop: kwrite

Application kwrite from second desktop wasn't restored only firefox and konsole
from first one.

The system (up-to-date on day 2016-01-01) is running on VirtualBox 5.0.10 with
turned off OpenGL acceleration.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb35bf7c0 (LWP 1685))]

Thread 9 (Thread 0xb1b3db40 (LWP 1686)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libxcb.so.1
#3  0x in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#4  0x in  () at /usr/lib/libQt5XcbQpa.so.5
#5  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#6  0x in start_thread () at /lib/libpthread.so.0
#7  0x in clone () at /lib/libc.so.6

Thread 8 (Thread 0xaecf9b40 (LWP 1690)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/dri/swrast_dri.so
#4  0x in  () at /usr/lib/dri/swrast_dri.so
#5  0x in start_thread () at /lib/libpthread.so.0
#6  0x in clone () at /lib/libc.so.6

Thread 7 (Thread 0xae4f8b40 (LWP 1691)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in  () at /usr/lib/dri/swrast_dri.so
#4  0x in  () at /usr/lib/dri/swrast_dri.so
#5  0x in start_thread () at /lib/libpthread.so.0
#6  0x in clone () at /lib/libc.so.6

Thread 6 (Thread 0xacaa9b40 (LWP 1700)):
#0  0x in __kernel_vsyscall ()
#1  0x in read () at /lib/libc.so.6
#2  0x in  () at /usr/lib/libglib-2.0.so.0
#3  0x in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#4  0x in  () at /usr/lib/libglib-2.0.so.0
#5  0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#6  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/sse2/libQt5Core.so.5
#7  0x in
QEventLoop::processEvents(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#8  0x in QEventLoop::exec(QFlags) () at
/usr/lib/sse2/libQt5Core.so.5
#9  0x in QThread::exec() () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in  () at /usr/lib/sse2/libQt5Qml.so.5
#11 0x in  () at /usr/lib/sse2/libQt5Core.so.5
#12 0x in start_thread () at /lib/libpthread.so.0
#13 0x in clone () at /lib/libc.so.6

Thread 5 (Thread 0xa5199b40 (LWP 1976)):
#0  0x in __kernel_vsyscall ()
#1  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0
#2  0x in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libc.so.6
#3  0x in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/sse2/libQt5Core.so.5
#4  0x in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked(ThreadWeaver::Thread*)
() at /usr/lib/libKF5ThreadWeaver.so.5
#5  0x in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x in  () at /usr/lib/libKF5ThreadWeaver.so.5
#7  0x in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*,
bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x in  () at /usr/lib/sse2/libQt5Core.so.5
#10 0x in start_thread () at /lib/libpthread.so.0
#11 0x in clone () at /lib/libc.so.6

Thread 4 (Thread 0xa4998b40 (LWP 1977)):
[KCrash Handler]
#7  0x in  () at /usr/lib/liblmdb-0.9.16.so
#8  0x in mdb_txn_begin () at /usr/lib/liblmdb-0.9.16.so
#9  0x in Baloo::Transaction::Transaction(Baloo::Database const&,
Baloo::Transaction::TransactionType) () at /usr/lib/libKF5BalooEngine.so.5
#10 0x 

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[Bernd Paysan via KDE Bugzilla]

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

--- Comment #145 from Bernd Paysan  ---
I have my free software projects myself, and I understand that you occasionally
want to rewrite something from scratch.  Usually, when the main features have
been bolted on later, and make the whole thing a maintenance nightmare.  So you
think about the feature set and how to solve that clean and lean.  In the
discussion about multiple backgrounds in KDE4, I suggested to have two
frameless unraisable windows underneath the other windows: root (for the
background) and activity on top of root.  These windows would be screen-sized,
and either you have n of them for n virtual desktops, or one, and it's attached
to all virtual desktops.  Answer was "well, it doesn't fit into the current
framework, but we can think about it next time".

Obviously, the people who did the next redesign ignored the last discussion
about multiple backgrounds for multiple windows completely.  I mean, this is
not really something cunningly new, fvwm has FvwmBacker, which also supports
per virtual-desktop backgrounds.  I don't know since when, but I'm pretty sure
it's 20 years or more.  This is not a rocket science thing.

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

[kdenlive] [Bug 350948] git master 2015-08-04 - changing project framerate does not update number of frames in source clips

[Evert Vorster via KDE Bugzilla]

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

--- Comment #10 from Evert Vorster  ---
Excellent work!

Because frames are integers, any event that happen on the same frame in the
time line, will go have the same frame number on the new time line at the new
frame rate. 

The one corner case is if one frame follows directly behind another, you have a
small chance of two frames trying to occupy the same space, or have a gap
between the two key frames, depending on whether the project's frame rate was
decreased or increased. 

One way around this would be to check for situations where key frames are
directly following each other, and then in the new time line just keep that
relationship, rather than try to convert the two key frames separately.

Unfortunately, there is not much more that can be done, as there are physically
more or less frames, and we have to aim for a logical best fit.

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

[kdenlive] [Bug 350948] git master 2015-08-04 - changing project framerate does not update number of frames in source clips

[Evert Vorster via KDE Bugzilla]

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

--- Comment #11 from Evert Vorster  ---
Just pulled from git, and there is just one small niggle. 

The displayed number of frames in the clip properties is not updated with the
change of the project's frame rate. 

The clips now play to the proper number of frames, which makes me a very happy
person. Thanks fir this fix, it's already improved the usability of kdenlive
when mixing clips of different framerates. 

I have a couple of clips that I specifically made to test this. 
I have a clip of 100 frames at 30fps. 
When I load it into a project with 25fps frame rate, it correctly displays 80
frames in length. 
The clip also plays to frame 80, (with the proper frames dropped)
If I then change the project's frame rate to 30fps, the clip now plays to frame
100, but in the clip properties it still says 80 frames. 

Like I said, it's a small niggle, but it might make troubleshooting some other
error in the future more easy if this is also corrected.

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

[kwin] [Bug 328122] off-screen kwin loops at 100% when using two users & x servers

[Fredrik Höglund via KDE Bugzilla]

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

--- Comment #20 from Fredrik Höglund  ---
(In reply to Thomas Lübking from comment #18)
> KWin has never fixed and actually cannot fix this (we'd need to track the VT
> and that requires root permissions), the behavior is completely in the
> driver (we just could at some point omit the code that sometimes reads the
> frontbuffer - iff that turns out to be the ultimate cause)

$ xprop -root | grep VT
XFree86_has_VT(INTEGER) = 1
XFree86_VT(INTEGER) = 7

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

[plasmashell] [Bug 357403] New: Plasma crashes when quickly switching desktops after a window on another desktop is focused

[Mircea Kitsune via KDE Bugzilla]

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

Bug ID: 357403
   Summary: Plasma crashes when quickly switching desktops after a
window on another desktop is focused
   Product: plasmashell
   Version: 5.5.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sonichedgehog_hyperblas...@yahoo.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Plasma crashes when a program on one desktop focuses a window on another
desktop, then the user quickly switches back to the initial desktop. You must
wait about 10 seconds in order to avoid the crash.

Reproducible: Always

Steps to Reproduce:
1. Make sure the system has at least two desktops. Put your default web browser
on one (I use Firefox) and your file manager on the other (I use Dolphin).

2. Create a shortcut file to a website or find one on your drive, then click
it. You will automatically be taken to the other desktop as the web browser is
focused.

3. Quickly use the pager to scroll back to the initial desktop, on which you
have the file manager open. Ideally click on the background or various Plasma
menus afterward.

Actual Results:  
plasmashell crashes and the KDE crash reporter pops up.


Several details which might be related to the problem: The crash occurs while I
still have the bouncing icon on the cursor, as well as the task manager entry
of the web browser showing the spinning cursor. I use the icon-only task manger
on the default panel. I use the following KWin and Plasma themes:

http://opendesktop.org/content/show.php?content=168737

http://opendesktop.org/content/show.php?content=168760

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

[plasmashell] [Bug 357403] Plasma crashes when quickly switching desktops after a window on another desktop is focused

[Mircea Kitsune via KDE Bugzilla]

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

Mircea Kitsune  changed:

   What|Removed |Added

 CC||sonichedgehog_hyperblast00@
   ||yahoo.com

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

[kmymoney4] [Bug 349938] hang freeze during QIF import

[via KDE Bugzilla]

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

t_...@tbheil.com changed:

   What|Removed |Added

 CC||t_...@tbheil.com

--- Comment #13 from t_...@tbheil.com ---
FYI: I also have this problem with some .qif files, but not others.  KMyMoney
4.7.2 (and earlier) on Windows 8.1 locks upon importing.

Locks up after the "QIF Import" dialogue, but before the Account Selection
dialogue.

The QIF file is very short, contains no sensitive financials, and is inlined
below:
--
!Type:Bank
D12/31/2015
C*
PCredit Dividend
M
T0.37
^
D12/30/2015
C*
PMYCOMPANY  - EDIPAYMENT
MACH Deposit
T369.00
^

--

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

[plasmashell] [Bug 357405] New: Wrong icon in battery widget tooltip

[via KDE Bugzilla]

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

Bug ID: 357405
   Summary: Wrong icon in battery widget tooltip
   Product: plasmashell
   Version: 5.5.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Battery Monitor
  Assignee: k...@privat.broulik.de
  Reporter: perrantre...@googlemail.com
CC: plasma-b...@kde.org

If you have oxygen-icons installed, the tooltip for the battery monitor will
use an oxygen icon even when Breeze is the chosen icon theme.

To make it use the correct Breeze icon, you must uninstall the oxygen-icon
theme, though this may be a dependency of some legacy KDE4 program you may use.

Reproducible: Always

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

[plasmashell] [Bug 357410] New: Telepathy crash

[Seth Izenzon via KDE Bugzilla]

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

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

Application: plasmashell (5.4.3)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-22-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
This has been reported several times but I can never mark as duplicate. Hoping
for a fix soon.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbd13456800 (LWP 2859))]

Thread 18 (Thread 0x7fbcf73e6700 (LWP 2989)):
#0  0x7fbd0a935884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fbd0a8f0770 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbd0a8f111b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbd0a8f12fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbd0e4c829b in QEventDispatcherGlib::processEvents
(this=0x7fbcf8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fbd0e46e75a in QEventLoop::exec (this=this@entry=0x7fbcf73e5da0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fbd0e28c3d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fbd10ae3f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fbd0e2912be in QThreadPrivate::start (arg=0x2021a30) at
thread/qthread_unix.cpp:337
#9  0x7fbd0d36e6aa in start_thread (arg=0x7fbcf73e6700) at
pthread_create.c:333
#10 0x7fbd0db9deed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7fbcec1ce700 (LWP 2998)):
#0  0x7fbd0a935869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fbd0a8f0789 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbd0a8f111b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbd0a8f12fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbd0e4c829b in QEventDispatcherGlib::processEvents
(this=0x7fbce40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fbd0e46e75a in QEventLoop::exec (this=this@entry=0x7fbcec1cdda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fbd0e28c3d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fbd10ae3f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fbd0e2912be in QThreadPrivate::start (arg=0x2398cf0) at
thread/qthread_unix.cpp:337
#9  0x7fbd0d36e6aa in start_thread (arg=0x7fbcec1ce700) at
pthread_create.c:333
#10 0x7fbd0db9deed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7fbce971e700 (LWP 3006)):
#0  __libc_disable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:98
#1  0x7fbd0db928e9 in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0x7fbd0a8f11ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbd0a8f12fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fbd0e4c829b in QEventDispatcherGlib::processEvents
(this=0x7fbce8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fbd0e46e75a in QEventLoop::exec (this=this@entry=0x7fbce971dda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fbd0e28c3d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fbd10ae3f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fbd0e2912be in QThreadPrivate::start (arg=0x22361a0) at
thread/qthread_unix.cpp:337
#9  0x7fbd0d36e6aa in start_thread (arg=0x7fbce971e700) at
pthread_create.c:333
#10 0x7fbd0db9deed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fbcdbdf6700 (LWP 3007)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbd12ead114 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fbd12ead159 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fbd0d36e6aa in start_thread (arg=0x7fbcdbdf6700) at
pthread_create.c:333
#4  0x7fbd0db9deed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7fbc58a7e700 (LWP 3013)):
#0  0x7fbd0a935884 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fbd0a8f1306 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbd0e4c829b in 

[kwin] [Bug 331841] "Prevent Screen Locking" corner action is not implemented

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

 CC||dmr@yandex.com

--- Comment #13 from Thomas Lübking  ---
*** Bug 339885 has been marked as a duplicate of this bug. ***

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

[plasma4] [Bug 339885] screen edge prevent screenlocker does not work

[Thomas Lübking via KDE Bugzilla]

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

Thomas Lübking  changed:

   What|Removed |Added

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

--- Comment #1 from Thomas Lübking  ---


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

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

[kdenlive] [Bug 357397] Image Sequence (with period in filename) missing upon re-opening project

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit bde554125a70f0587eb0d38b423b649777d7c5be by Jean-Baptiste Mardelle.
Committed on 01/01/2016 at 22:19.
Pushed by mardelle into branch 'Applications/15.12'.

Fix severe issues with slideshow clips

M  +1-0src/dialogs/clipcreationdialog.cpp
M  +2-2src/mltcontroller/clipcontroller.cpp
M  +55   -26   src/project/dialogs/slideshowclip.cpp

http://commits.kde.org/kdenlive/bde554125a70f0587eb0d38b423b649777d7c5be

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

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

[via KDE Bugzilla]

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

--- Comment #10 from scionicspec...@gmail.com ---
There are still some themes (Oxygen, Bespin, QtCurve) that appear to utilize
the functionality, so we should only 'turn it off' for Breeze, I think, if it's
possible to do so. If we get around to recreating the theme-generation script
that pre-applies the colors, I would prefer to have that checkbox activate the
script rather than whatever it's trying to do now.

Still, that's a chunk of work outside of the theme itself. That's a long ways
out, as I'm not certain I'll be able to contribute to the theme for a while.

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

[muon] [Bug 357245] Don't try to fetch updates if such a privilege isn't granted

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

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

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

[umbrello] [Bug 357372] Add support for C++11

[via KDE Bugzilla]

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

milasud...@gmail.com changed:

   What|Removed |Added

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

--- Comment #1 from milasud...@gmail.com ---


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

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

[umbrello] [Bug 338649] Extend C++ import for C++11

[via KDE Bugzilla]

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

milasud...@gmail.com changed:

   What|Removed |Added

 CC||milasud...@gmail.com

--- Comment #4 from milasud...@gmail.com ---
*** Bug 357372 has been marked as a duplicate of this bug. ***

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

[umbrello] [Bug 338649] Extend C++ import for C++11

[via KDE Bugzilla]

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

--- Comment #5 from milasud...@gmail.com ---
I thought libclang would be usable. This way, new features would already be
implemented there.

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

[dolphin] [Bug 352702] Dolphin Right Click Crashes when selecting the Activities item

[ahmadkruiz via KDE Bugzilla]

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

--- Comment #4 from ahmadkruiz  ---
(In reply to Emmanuel Pescosta from comment #2)
> Thanks! The bug has been reported already and is fixed in KF 5.14.
> 
> *** This bug has been marked as a duplicate of bug 352207 ***

Thanks for your efforts, but I still have this bug.

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

[dolphin] [Bug 352702] Dolphin Right Click Crashes when selecting the Activities item

[ahmadkruiz via KDE Bugzilla]

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

ahmadkruiz  changed:

   What|Removed |Added

 CC||ahmad19...@windowslive.com

--- Comment #3 from ahmadkruiz  ---
Thanks for your efforts, but I still have this bug.

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

[umbrello] [Bug 357373] When opening a saved file, the class diagram becomes a real mess

[via KDE Bugzilla]

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

milasud...@gmail.com changed:

   What|Removed |Added

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

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

[gwenview] [Bug 343452] Does not sort numbers naturally any longer

[via KDE Bugzilla]

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

ant.cerv...@gmail.com changed:

   What|Removed |Added

 CC||ant.cerv...@gmail.com

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

[plasmashell] [Bug 357383] New: Plasma crashed on startup

[via KDE Bugzilla]

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

Bug ID: 357383
   Summary: Plasma crashed on startup
   Product: plasmashell
   Version: 5.5.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: b.gatessu...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.0)

Qt Version: 5.5.1
Operating System: Linux 4.2.8-300.fc23.x86_64+debug x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

After entering username and password at the login screen, Plasma was loading.
The desktop showed a Konsole and the taskbar, then the crash occurred without
any user action having occurred.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3cc2069940 (LWP 2860))]

Thread 9 (Thread 0x7f3ca213e700 (LWP 2862)):
#0  0x7f3cb9a4cffd in poll () at /lib64/libc.so.6
#1  0x7f3cbff01272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f3cbff02ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f3ca40c7da9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f3cba6553ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f3cb8d9060a in start_thread () at /lib64/libpthread.so.0
#6  0x7f3cb9a58a9d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f3c9b5ef700 (LWP 2943)):
#0  0x7f3cb9a4cffd in poll () at /lib64/libc.so.6
#1  0x7f3cb4f7516c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f3cb4f7527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f3cba88cf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f3cba833f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f3cba650424 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f3cbe99ab45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f3cba6553ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f3cb8d9060a in start_thread () at /lib64/libpthread.so.0
#9  0x7f3cb9a58a9d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f3c91421700 (LWP 2944)):
#0  0x7f3cb8d95b10 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3c98e2e773 in radeon_drm_cs_emit_ioctl () at
/usr/lib64/dri/r600_dri.so
#2  0x7f3c98e2dec7 in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so
#3  0x7f3cb8d9060a in start_thread () at /lib64/libpthread.so.0
#4  0x7f3cb9a58a9d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f3c8d34a700 (LWP 2946)):
#0  0x7f3cb9a4cffd in poll () at /lib64/libc.so.6
#1  0x7f3cb4f7516c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f3cb4f7527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f3cba88cf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f3cba833f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f3cba650424 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f3cbe99ab45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f3cba6553ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f3cb8d9060a in start_thread () at /lib64/libpthread.so.0
#9  0x7f3cb9a58a9d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f3c87866700 (LWP 2962)):
#0  0x7f3cb9a4cffd in poll () at /lib64/libc.so.6
#1  0x7f3cb4f7516c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f3cb4f7527c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f3cba88cf0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f3cba833f0a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f3cba650424 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f3cbe99ab45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f3cba6553ce in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f3cb8d9060a in start_thread () at /lib64/libpthread.so.0
#9  0x7f3cb9a58a9d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f3c8601d700 (LWP 3022)):
#0  0x7f3cb8d95b10 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3cc17f2514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#2  0x7f3cc17f2559 in  () at /lib64/libQt5Script.so.5
#3  0x7f3cb8d9060a in start_thread () at /lib64/libpthread.so.0
#4  0x7f3cb9a58a9d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f3bff2e9700 (LWP 3062)):
#0  0x7f3cb9a4cffd in poll () at 

[parley] [Bug 357385] New: Cannot edit existing collection

[Dimitris Kardarakos via KDE Bugzilla]

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

Bug ID: 357385
   Summary: Cannot edit existing collection
   Product: parley
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: editor
  Assignee: parley-bugs-n...@kde.org
  Reporter: dimk...@gmail.com

When trying to update an existing collection, upon saving, the following error
popup is displayed:
"Writing file x resulted in an error:The lock file can't be created."

Reproducible: Always

Steps to Reproduce:
1. Open an existing collection
2. Edit an existing entry or add a new entry
3. Save

Actual Results:  
Error "Writing file x resulted in an error:The lock file can't be created."

Expected Results:  
File to be saved

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

[plasmashell] [Bug 357384] New: Keyboard switcher applet randomly disappearing

[Robin Green via KDE Bugzilla]

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

Bug ID: 357384
   Summary: Keyboard switcher applet randomly disappearing
   Product: plasmashell
   Version: 5.5.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: gree...@greenrd.org

The KDE keyboard switcher applet keeps randomly disappearing after I upgraded
to Fedora 23. Yesterday I fixed this problem by rebooting, I think. But now
rebooting does not help.

However, if I start a new session with a different user, and enable keyboard
"switching" for one keyboard layout in system settings, the keyboard switcher
applet appears for that user.

This is a workaround I have found to make it reappear when it disappears:

 1.  Right-click on an area of the system tray which is for some reason, empty.
(Side note: I think this is part of the problem - not all applets are
appearing, or appearing properly, in the system tray.)
 2.  Choose "System tray settings"
 3. Choose the second settings panel, called "Entries"
 4.  Set the Keyboard Layout visibility dropdown to "Hidden"
 5.  Click the Apply button
 6. Set the Keyboard Layout visibility dropdown to "Shown"
 7. Click the OK button

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

[kaddressbook] [Bug 357374] Huge Skype and Google Talk icons in Contacts panel view

[Laurent Montel via KDE Bugzilla]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #3 from Laurent Montel  ---
indeed it's a big icon !

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

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

[Dave Flogeras via KDE Bugzilla]

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

--- Comment #8 from Dave Flogeras  ---
Good point.  Screen locking works fine if I press CTRL-ALT-L.

However, I noticed something else today which I didn't notice before because my
screen usually blanks (or the machine hibernates) on this laptop before the
10minute screen locker timeout is reached.  I set the screen locking timeout to
1 minute, and disabled power management so the screen would not blank.  I
waited 2 minutes and the screen did not lock on its own.

Finally, if I manually do the following:
qdbus org.kde.screensaver /ScreenSaver Lock

The screen does lock.

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

[plasmashell] [Bug 357387] New: can't use specific homepage for browser-widget

[Justin T . Frisch via KDE Bugzilla]

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

Bug ID: 357387
   Summary: can't use specific homepage for browser-widget
   Product: plasmashell
   Version: 5.5.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Folder
  Assignee: h...@kde.org
  Reporter: just...@gmx.net
CC: plasma-b...@kde.org

the kde4 browser widget would remember the last visited website url and on the
next login, go back to that address. there was also a bookmark functionality.
the new kde5 widget always goes to www.kde.org and there is no way to change
this default address, the bookmark functions havn't been ported either.


Reproducible: Always

Steps to Reproduce:
1. add a browser widget to the desktop
2. visit any website
3. logout and log back in


Actual Results:  
the browser widget shows www.kde.org again


Expected Results:  
it should show the website you last went to


or offer a configuration option to set the default homepage url.

the grave severity is exclusive to the browser widget because it is basically
useless without being able to a specify a homepage.

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

[kdenlive] [Bug 350948] git master 2015-08-04 - changing project framerate does not update number of frames in source clips

[Evert Vorster via KDE Bugzilla]

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

Evert Vorster  changed:

   What|Removed |Added

 Resolution|--- |REMIND
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #5 from Evert Vorster  ---
Ah, here it is. 
I remember writing a report about this. 
After having run into it many times, I can describe exactly how to hit the
problem. 

When a clip is opened in the Project bin the first time, it's duration is
converted into a number of frames at the project's frame rate. When the clip
has the same frame rate as the project, this approach works beautifully. 

Where it all comes crashing down is that when the project's frame rate is
updated, the number of frames for each clip is not updated. 
This is clearly not right, and is causing all kinds of weirdness, like clips
stopping playback halfway through, or not being able to display the entire
clip, depending on whether the frame rate of the project was increased or
decreased. 

The workaround currently is to delete the clip out of the Project bin, and
loading it again, which will give it the correct number of frames for the
project's frame rate. Unfortunately, hitting the "Reload Clip" button does not
update the number of frames for the clip. Also, when a clip is deleted out of
the Project bin, it is also removed from the timeline, which is a PITA. 

So, updating the number of frames for each clip currently in the Project bin
every time is updated is a necessity. 

To carry on, every time there is a change in the frame rate, a dialog pops up,
saying that transitions and such will shift. Fixing this problem is related to
re-reading the clips... The items on the timeline are all specified in frame
numbers. This includes all transitions and effects. 
So, in order to avoid things shifting around temporally, every frame reference
on the timeline also needs to be converted to the new framerate. 

ie: if an event happens at frame 100, and the project's frame rate is changed
from 25fps to 30fps, that event has to move: frame 100 to (100/25)*30 = frame
120
Of course, frames are integers, so no fractional frames. 

So, to get rid of that horrible dialog, and make changing the framerate of a
project bulletproof, 
all the clips need to have their frame numbers re-calculated, and then every
frame reference in the timeline also needs to be converted to the new
framerate.

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

[plasmashell] [Bug 357390] New: Multi-Monitor support severly broken

[via KDE Bugzilla]

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

Bug ID: 357390
   Summary: Multi-Monitor support severly broken
   Product: plasmashell
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slartibar...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Attaching a 2nd monitor via hdmi out (using hdmi-dvi connector)
Plasma crashes so often that normal working with the system (as opposed to
running with a single screen) is nearly impossible. Examples:
- opening kicker menu, adding an entry to the favorites menu -> crash
- favorites entries keep changing depending on a single or multiple monitors
being attached (2 monitors: favorites is empty, removing it: 'default' entries
(dolphin, systemsettings etc) appear)
- setting up the 2nd monitor as main display (systemsettings - display and
monitor - primary display) : crash

All this happens after a new user is set up (useradd, then logging in into kde
for the first time). Removing the user and his directories and starting from
scratch shows same behaviours. This all happens when trying to work with the
system... in kde4 this was just working amazingly well, but now


Reproducible: Always

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

[parley] [Bug 351976] Missing Comment in desktop file

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/parl
   ||ey/73d44ec6e141eace6dea4de9
   ||be269eb7adc49c2c
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit 73d44ec6e141eace6dea4de9be269eb7adc49c2c by Andreas Cord-Landwehr.
Committed on 01/01/2016 at 14:42.
Pushed by cordlandwehr into branch 'master'.

Add Comment to desktop file.

This is the tag line from the edu-website.

M  +1-0src/org.kde.parley.desktop

http://commits.kde.org/parley/73d44ec6e141eace6dea4de9be269eb7adc49c2c

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

[parley] [Bug 357385] Cannot edit existing collection

[Andreas Cord-Landwehr via KDE Bugzilla]

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

Andreas Cord-Landwehr  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/libk
   ||eduvocdocument/1d14e946aacb
   ||395330e21c7b7696913fccaf255
   ||4
 Resolution|--- |FIXED

--- Comment #1 from Andreas Cord-Landwehr  ---
Git commit 1d14e946aacb395330e21c7b7696913fccaf2554 by Andreas Cord-Landwehr.
Committed on 01/01/2016 at 15:00.
Pushed by cordlandwehr into branch 'master'.

Make QString to QUrl conversions explicit.

This avoids silent conversions from file paths that are not provided in
url format and thus result in empty QUrl paths.

M  +3-1CMakeLists.txt
M  +4-4keduvocdocument/keduvocdocument.cpp
M  +2-2keduvocdocument/tests/converter.cpp

http://commits.kde.org/libkeduvocdocument/1d14e946aacb395330e21c7b7696913fccaf2554

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

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

[Wulf via KDE Bugzilla]

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

--- Comment #9 from Wulf  ---
I don't know anything about the technical context and what 'Apply colors to
non-Qt applications' really does.
I did not know pixmaps is part of these contexts.

If I understand it right, it's gimp/inkscape, who do not understand or ignore
the color codes set by KDE in /.config/gtkrc-2.0
yes, then disabling it by default would be a good workaround

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

[kdeplasma-addons] [Bug 357387] can't use specific homepage for browser-widget

[David Edmundson via KDE Bugzilla]

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

--- Comment #2 from David Edmundson  ---
yeah, it needs to read/write to Plasma.configuration


If you've found that, maybe it's something you'd like to look into fixing?

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

[kdeplasma-addons] [Bug 357387] can't use specific homepage for browser-widget

[Mihail Ivchenko via KDE Bugzilla]

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

--- Comment #3 from Mihail Ivchenko  ---
Hello,

I'll try to add "Default URL" option to config dialog if it's OK for everyone.
:)

Best regards,
Mikhail Ivchenko.

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

[parley] [Bug 357385] Cannot edit existing collection

[Dimitris Kardarakos via KDE Bugzilla]

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

--- Comment #3 from Dimitris Kardarakos  ---
I can now update existing collections but this prevents me from creating new
collections.

In console, I get the following:
QFile::copy: Empty or null file name

In application UI, I get the attached popup.

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

[ksmserver] [Bug 354097] Session management broken when using several virtual desktops

[via KDE Bugzilla]

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

kdebugs.anon...@yahoo.com changed:

   What|Removed |Added

 CC||kdebugs.anon...@yahoo.com

--- Comment #2 from kdebugs.anon...@yahoo.com ---
I am having also having the problem where if I use "restore last session", then
most programs aren't restored at all, only a few.

I rely heavily of the "restore last session", so this is a VERY significant
problem for me, so much that it is preventing me from permanently moving to
Plasma 5.  This is very disappointing.  :(

My System:
openSUSE Leap 42.1 for x86_64
plasma5-workspace v5.5.2-158.1
KDE Platform Version 4.14.10

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

[parley] [Bug 357385] Cannot edit existing collection

[Dimitris Kardarakos via KDE Bugzilla]

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

--- Comment #2 from Dimitris Kardarakos  ---
Created attachment 96397
  --> https://bugs.kde.org/attachment.cgi?id=96397=edit
popup error

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

[kdenlive] [Bug 357386] Git master 2016-01-01 - Saved custom filter stack has fixed keyframes

[via KDE Bugzilla]

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

wegwerf-1-...@gmx.de changed:

   What|Removed |Added

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

--- Comment #1 from wegwerf-1-...@gmx.de ---
I've noticed this before too; it also seems to happen when copying and pasting
effects within an project from one clip to another. However, sometimes the
improper keyframe translation kicks in, sometimes not. I still need to find out
exactly when this happens.

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

[via KDE Bugzilla]

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

kdebugs.anon...@yahoo.com changed:

   What|Removed |Added

 CC||kdebugs.anon...@yahoo.com

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

[ksmserver] [Bug 343518] Plasma doesn't restore everything after a reboot

[via KDE Bugzilla]

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

--- Comment #38 from kdebugs.anon...@yahoo.com ---
I am having also having the problem where if I use "restore last session", then
most programs aren't restored at all when logging back in.

I rely HEAVILY on the "restore last session" function, so this is a VERY
significant problem for me, so much that it is preventing me from permanently
moving to Plasma 5.  This is very disappointing.  :(

My System:
openSUSE Leap 42.1 for x86_64
plasma5-workspace v5.5.2-158.1
KDE Platform Version 4.14.10

Reproducible: Always

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

[parley] [Bug 357385] Cannot edit existing collection

[Dimitris Kardarakos via KDE Bugzilla]

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

--- Comment #5 from Dimitris Kardarakos  ---
Created attachment 96399
  --> https://bugs.kde.org/attachment.cgi?id=96399=edit
qurl to qstring patch

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

[parley] [Bug 357385] Cannot edit existing collection

[Andreas Cord-Landwehr via KDE Bugzilla]

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

--- Comment #6 from Andreas Cord-Landwehr  ---
Git commit 322cb7e34e3b7ca7ebf4caf4ed75b22fb51fd68d by Andreas Cord-Landwehr.
Committed on 01/01/2016 at 15:53.
Pushed by cordlandwehr into branch 'master'.

Use more robust comparison.

Solves popup error when saving new file.

M  +1-1src/parleydocument.cpp

http://commits.kde.org/parley/322cb7e34e3b7ca7ebf4caf4ed75b22fb51fd68d

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

[kdenlive] [Bug 350948] git master 2015-08-04 - changing project framerate does not update number of frames in source clips

[Jean-Baptiste Mardelle via KDE Bugzilla]

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

--- Comment #7 from Jean-Baptiste Mardelle  ---
Git commit 964b9ef8ce36e9c73bd32ed790b3e1dd59656d2c by Jean-Baptiste Mardelle.
Committed on 01/01/2016 at 15:58.
Pushed by mardelle into branch 'master'.

Reload all bin clips on project's fps  change. There is a small but in MLT
causing the displayed clip length to be wrong, but it's only a display bug

M  +15   -0src/bin/bin.cpp
M  +2-0src/bin/bin.h
M  +1-1src/bin/projectclip.cpp
M  +3-0src/doc/kdenlivedoc.cpp

http://commits.kde.org/kdenlive/964b9ef8ce36e9c73bd32ed790b3e1dd59656d2c

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

[ksmserver] [Bug 355707] Sessions saved automatically are not restored at new login

[via KDE Bugzilla]

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

kdebugs.anon...@yahoo.com changed:

   What|Removed |Added

 CC||kdebugs.anon...@yahoo.com

--- Comment #3 from kdebugs.anon...@yahoo.com ---
I am having also having the problem where if I use "restore last session", then
most programs aren't restored at all when logging back in. I rely HEAVILY on
the "restore last session" function, so this is a VERY significant problem for
me, so much that it is preventing me from permanently moving to Plasma 5. This
is very disappointing. :(

My System:
openSUSE Leap 42.1 for x86_64
plasma5-workspace v5.5.2-158.1
KDE Platform Version 4.14.10

Reproducible: Always

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

[parley] [Bug 357385] Cannot edit existing collection

[Dimitris Kardarakos via KDE Bugzilla]

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

--- Comment #4 from Dimitris Kardarakos  ---
I have managed to both create and update collections by reverting
1d14e946aacb395330e21c7b7696913fccaf2554 and following the primitive (?)
approach of the attached patch, added just in case that helps.

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

[plasmashell] [Bug 357394] vmware workstation not working

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
(vmware-modconfig:8302): Gtk-WARNING **: Unable to locate theme engine in
module_path: "adwaita",

That's  GTK's defualt theme not being installed, nothing to do with us.

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

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

[Kai Uwe Broulik via KDE Bugzilla]

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

--- Comment #9 from Kai Uwe Broulik  ---
Actually I'm not sure if the screenlocker supports Consolekit 2, PowerDevil
does but locking on suspend has been moved to the screen locker. Should be
trivial to add, however. Patches welcome :)

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

[plasma4] [Bug 310647] plasma-desktop crashes on start with basic configuration, adding systemtray wideget.

[Justin T . Frisch via KDE Bugzilla]

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

Justin T. Frisch  changed:

   What|Removed |Added

 CC||emati...@gmail.com,
   ||just...@gmx.net

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

[plasmashell] [Bug 357387] can't use specific homepage for browser-widget

[Justin T . Frisch via KDE Bugzilla]

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

Justin T. Frisch  changed:

   What|Removed |Added

 CC||emati...@gmail.com

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

[plasmashell] [Bug 357387] can't use specific homepage for browser-widget

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||k...@privat.broulik.de

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

[systemsettings] [Bug 357389] New: Some mouse buttons for gestures are not mapped correctly

[via KDE Bugzilla]

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

Bug ID: 357389
   Summary: Some mouse buttons for gestures are not mapped
correctly
   Product: systemsettings
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_khotkeys
  Assignee: k...@michael-jansen.biz
  Reporter: seym...@gmail.com

Cannot set mouse button 10 to be used for gestures.
Mouse button 9 is the forward button on the mouse, physically.
Mouse button 10 should be the thumb button, but when mouse button 10 is set for
gestures it's still using the forward button.
So both button 9 and 10 are pointing to the same physical mouse button in
gestures.

Tried to set every number in gestures, but none of them use the thumb button.

According to xev the thumb button is button 10.
xbindkeys can also use it as button 10.

Reproducible: Always




Submit Bug report - System Settings:
Version: 4.11.13
Linux (x86_64) release 3.16.0-4-amd64
Compiler: cc

KDE - Be Free!
Platform Version 4.14.2

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

[linuxfluesterer via KDE Bugzilla]

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

--- Comment #141 from linuxfluesterer  ---
(In reply to David Edmundson from comment #129)
> It's probably in your interest not to piss me off.

Plasma is nice, but useless comparing to the final KDE 4.14.11 with it's main,
outragous features. So, my question to the devs is: Why did you begin to create
a Plasma, if the intention is not to build a better environment than KDE 4 was?
I mean, if you feel pissed off by the users, who really know to value KDE 4, if
you won't intent to give them at least the same in Plasma (you might announce
in the long run).
I really, really admire your work (for KDE 4), but if in the end Plasma will
not offer the specs, which made KDE 4 outragous, then my suggestion: Stop going
on working on it. Let it be, if you will only disappoint the real users of KDE.
I feel very sad to say this, but I am honest, I am in the customers place here.
And for me, I see no reason to change from a reliable, rather good featured,
older model (KDE 4) to a still experimental and even less useful new model
(Plasma).

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

[Baloo] [Bug 357391] New: Baloo crash

[Alejandro Moreno Calvo via KDE Bugzilla]

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

Bug ID: 357391
   Summary: Baloo crash
   Product: Baloo
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: almo...@gmail.com
CC: pinak.ah...@gmail.com

Application: baloo_file (5.15.0)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-22-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
Baloo crash every day. 
I do not notice anything unusual. I do a normal desktop use and suddenly it
crashs. Sometime Krunner crashs too.

I use Kubuntu 15.10.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Bus error
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9ebfc29800 (LWP 1192))]

Thread 2 (Thread 0x7f9d74b78700 (LWP 2076)):
[KCrash Handler]
#6  __memcpy_sse2_unaligned () at
../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:116
#7  0x7f9ebe774f90 in memcpy (__len=1879109376, __src=0x7f9d74b77b90,
__dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53
#8  QByteArray::QByteArray (this=0x7f9d74b77ad0, data=0x7f9d74b77b90
"\360\206f\002", size=1879109376) at tools/qbytearray.cpp:1374
#9  0x7f9ebee1c601 in Baloo::DocumentDB::get
(this=this@entry=0x7f9d74b77b90, docId=docId@entry=90171829062207489) at
../../../src/engine/documentdb.cpp:96
#10 0x7f9ebee35e5a in Baloo::WriteTransaction::replaceDocument
(this=0x7f9d70003170, doc=..., operations=...) at
../../../src/engine/writetransaction.cpp:188
#11 0x7f9ebee2eba9 in Baloo::Transaction::replaceDocument
(this=this@entry=0x7f9d74b77c90, doc=..., operations=..., operations@entry=...)
at ../../../src/engine/transaction.cpp:263
#12 0x0041c7f3 in Baloo::XAttrIndexer::run (this=0x2720850) at
../../../src/file/xattrindexer.cpp:77
#13 0x7f9ebe76de73 in QThreadPoolThread::run (this=0x260d540) at
thread/qthreadpool.cpp:93
#14 0x7f9ebe7712be in QThreadPrivate::start (arg=0x260d540) at
thread/qthread_unix.cpp:337
#15 0x7f9ebd3e36aa in start_thread (arg=0x7f9d74b78700) at
pthread_create.c:333
#16 0x7f9ebdd81eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f9ebfc29800 (LWP 1192)):
#0  0x7f9ebdd7249d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f9ebafa74e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9ebaf63cd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9ebaf64190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9ebaf642fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f9ebe9a827f in QEventDispatcherGlib::processEvents (this=0x258c0b0,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#6  0x7f9ebe94e75a in QEventLoop::exec (this=this@entry=0x7ffcad1ec810,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x7f9ebe9562cc in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1188
#8  0x00415aec in main (argc=1, argv=) at
../../../src/file/main.cpp:88

Possible duplicates by query: bug 335214.

Reported using DrKonqi

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

[kdeplasma-addons] [Bug 357387] can't use specific homepage for browser-widget

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

   Assignee|h...@kde.org|plasma-b...@kde.org
Product|plasmashell |kdeplasma-addons
   Target Milestone|1.0 |---
  Component|Folder  |webbrowser

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

[kscreenlocker] [Bug 357368] Screen is not locked when resuming from suspend after upgrading to plasma 5.5.0

[Dave Flogeras via KDE Bugzilla]

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

--- Comment #10 from Dave Flogeras  ---
I would like to help, but would require some hand holding as I do not
understand the design of the software.  For instance, I see in the logind.cpp
there are multiple references to falling back to Consolekit if logind is not
available.  Also, in ksldapp.cpp it seems to fallback to letting Solid send a
signal if logind is not available.  Was the implementation started, but not
plumbed in?  Or is this leftover from when it was broken out into its own
package?

If someone gives me step by step instructions of what needs to be done, I can
take a crack at it.  However, if it is trivial and just a matter of hooking up
a few things it might be a waste of time explaining how to do vs just doing it.

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

[dolphin] [Bug 357395] New: Copy existing file: Dialog does not show details

[Axel Braun via KDE Bugzilla]

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

Bug ID: 357395
   Summary: Copy existing file: Dialog does not show details
   Product: dolphin
   Version: 15.08.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: axel.br...@gmx.de

Copy a file to a location, where the same file already exists: Dolphin does not
show information about source and target (but it did in earlier version -
regression error?)

Reproducible: Always

Steps to Reproduce:
1. copy file into folder, where file with same name already exists
2. no information shown
3.


Expected Results:  
last change date of source and target are displayed

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

[dolphin] [Bug 357395] Copy existing file: Dialog does not show details

[Axel Braun via KDE Bugzilla]

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

--- Comment #1 from Axel Braun  ---
Created attachment 96398
  --> https://bugs.kde.org/attachment.cgi?id=96398=edit
current dialog dislayed

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

[krunner] [Bug 346689] Unused Desktop Sessions appear when switching users

[Toby Newman via KDE Bugzilla]

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

--- Comment #3 from Toby Newman  ---
Just updated to Fedora 23 KDE spin yesterday.
I'm running kf5-plasma.x86_64 5.17.0-3.fc23.
Not caught up to 5.2/.3 yet, will report back when I do.

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

[kdenlive] [Bug 357386] New: Git master 2016-01-01 - Saved custom filter stack has fixed keyframes

[Evert Vorster via KDE Bugzilla]

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

Bug ID: 357386
   Summary: Git master 2016-01-01 - Saved custom filter stack has
fixed keyframes
   Product: kdenlive
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: evert.vors...@yandex.com

I have a pretty complicated filter stack that does not change much between
render jobs, so I saved it. 
The filter stack consists of: De-fish, Levels, White balance, Saturation,
Sharpening. 
None of these effects take key frames when first applied. However, when the
entire stack is saved and applied to another clip, they suddenly have key
frames. Worse, the key frames is for the frame numbers of the previous clip,
and if this happens to be after the last frame of the current clip, the effects
are applied at their highest negative setting. 

Reproducible: Always

Steps to Reproduce:
1. Make a filter stack a few levels deep. Save it as a custom one. 
2. Apply the filter stack to another clip, and look at the frame numbers the
effects in the stack have now suddenly gained. 
3. Add one more keyframe, and delete the original keyframe. 
4. The keyframes now disappear for the selected effect in the stack. 

Actual Results:  
Effects stack does not apply without fiddling, and looks different from the one
that was saved. 

Expected Results:  
The effect stack to be key frame agnostic, just like the one I saved. 

This is a little annoying, and I found half a workaround by making the effect
stack on the first frame of a clip, and then saving it. Then the effect stack
is applied each time, at least. However the key frames remain until I pick a
key frame in the clip, and delete the others. 

This could actually be quite a nifty feature, if it was possible to leave the
key frames add button to each effect, and then just interpolate between the key
frames if more than one key frame is added. 

However, the key frames should be adjusted to the first frame of the clip that
the effect is being applied to, as specifying a key frame that is not in the
range of the clip does not make sense. 
Also, the frame with the key frames in should also be hidden when there is only
one key frame, to save screen space. It is then assumed that the effect does
not change for the entire.
If the button for adding more key frames is left in, and expose the key frame
window when another key frame is added, it could be quite a feature at almost
no extra coding cost.

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

[plasmashell] [Bug 357387] can't use specific homepage for browser-widget

[Justin T . Frisch via KDE Bugzilla]

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

--- Comment #1 from Justin T. Frisch  ---
in /usr/share/plasma/plasmoids/org.kde.plasma.webbrowser/contents/ui/main.qml
there is 

ColumnLayout {
RowLayout{...
PlasmaExtras.ScrollArea {...
WebView {...
url: "http://kde.org;;

which can be changed to an arbitrary address. however, it's not possible to
have multiple browser widgets pointing to different home pages either, then

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

[umbrello] [Bug 357373] When opening a saved file, the class diagram becomes a real mess

[Ralf Habacker via KDE Bugzilla]

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

Ralf Habacker  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||ralf.habac...@freenet.de

--- Comment #1 from Ralf Habacker  ---
Please provide a related test xmi file.

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

[plasmashell] [Bug 357388] New: Konsole on 2nd monitor shows only empty window-frame

[via KDE Bugzilla]

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

Bug ID: 357388
   Summary: Konsole on 2nd monitor shows only empty window-frame
   Product: plasmashell
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slartibar...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Two-monitor setup (laptop and 2nd hdmi screen)
I made the 2nd monitor the default screen (systemsettings - display -
display config - primary monitor)
Right-Klicking on 1st screen and opening konsole from contextmenu opens a
konsole window with the terminal inside.
Right-klicking on 2nd screen and opening konsole from contextmenu opens a
konsole window without anything inside, just a copy of the background (which is
then movable with the window). Opening a second konsole window on 2nd monitor
is then ok and contains the terminal

Reproducible: Always

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

[kwin] [Bug 328122] off-screen kwin loops at 100% when using two users & x servers

[Robin Green via KDE Bugzilla]

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

Robin Green  changed:

   What|Removed |Added

 CC||gree...@greenrd.org

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

[plasmashell] [Bug 357392] New: Attaching of 2nd monitor not detected

[via KDE Bugzilla]

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

Bug ID: 357392
   Summary: Attaching of 2nd monitor not detected
   Product: plasmashell
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: slartibar...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Have plasma5 started and connect a 2nd monitor (vga, hdmi)
It's more than luck if the monitor is detected, sometimes it works only in the
sddm login screen, sometimes only when plasmashell is running.
The release of the 2nd monitor is also not detected.

This is not production ready as it is right now - what about those in need of a
beamer for a presentation It's worse than windows...


Reproducible: Always

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

[plasma-nm] [Bug 342074] Connection manager crashes when editing/adding openVPN connection

[via KDE Bugzilla]

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

--- Comment #3 from kdebugs.anon...@yahoo.com ---
Created attachment 96396
  --> https://bugs.kde.org/attachment.cgi?id=96396=edit
New crash information added by DrKonqi

kde-nm-connection-editor (0.9.3.5) on KDE Platform 4.14.9 using Qt 4.8.6

- What I was doing when the application crashed:
1.  Open the Network Manager Connection editor
2.  Click the button labeled "Add"
3.  Click the option labeled "openVPN" to create a new VPN connection
4.  The Network Manager Connection editor crashes immediately.

Reproducible every time.

-- Backtrace (Reduced):
#6  0x7ff3769ae3d9 in SettingWidget::SettingWidget (this=0x1edca50,
setting=..., parent=, f=...) at
/usr/src/debug/plasma-nm-0.9.3.5/libs/editor/widgets/settingwidget.cpp:25
#7  0x7ff37699247a in IPv6Widget::IPv6Widget (this=0x1edca50, setting=...,
parent=, f=...) at
/usr/src/debug/plasma-nm-0.9.3.5/libs/editor/settings/ipv6widget.cpp:66
#8  0x7ff3769b2ab9 in ConnectionDetailEditor::initTabs
(this=this@entry=0x1ae30d0) at
/usr/src/debug/plasma-nm-0.9.3.5/libs/editor/connectiondetaileditor.cpp:396
#9  0x7ff3769b4ad2 in ConnectionDetailEditor::initEditor
(this=this@entry=0x1ae30d0) at
/usr/src/debug/plasma-nm-0.9.3.5/libs/editor/connectiondetaileditor.cpp:260
#10 0x7ff3769b6914 in ConnectionDetailEditor::ConnectionDetailEditor
(this=0x1ae30d0, type=, parent=, vpnType=...,
shared=, f=...) at
/usr/src/debug/plasma-nm-0.9.3.5/libs/editor/connectiondetaileditor.cpp:117

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

[plasma-nm] [Bug 342074] Connection manager crashes when editing/adding openVPN connection

[via KDE Bugzilla]

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

kdebugs.anon...@yahoo.com changed:

   What|Removed |Added

 CC||kdebugs.anon...@yahoo.com

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

[plasmashell] [Bug 357393] Password field randomly does or doesn't have focus, when screen locks

[Dan Barrett via KDE Bugzilla]

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

--- Comment #1 from Dan Barrett  ---
I am using sddm 0.11.0-0ubuntu11, if that matters.

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

[plasmashell] [Bug 357393] Password field randomly does or doesn't have focus, when screen locks

[Dan Barrett via KDE Bugzilla]

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

Dan Barrett  changed:

   What|Removed |Added

 CC||k...@blazemonger.com

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

[plasmashell] [Bug 357393] New: Password field randomly does or doesn't have focus, when screen locks

[Dan Barrett via KDE Bugzilla]

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

Bug ID: 357393
   Summary: Password field randomly does or doesn't have focus,
when screen locks
   Product: plasmashell
   Version: 5.4.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Look & Feel package
  Assignee: plasma-b...@kde.org
  Reporter: k...@blazemonger.com
CC: plasma-b...@kde.org

When the screen locks due to inactivity, and then I press a key (like SHIFT) to
unblank the screen, the "Password" field sometimes has focus and sometimes does
not.

So sometimes, you can just type your password immediately, and other times you
have to click in the Password field first.

Reproducible: Sometimes

Steps to Reproduce:
1. Set up the screen locker to require a password.
2. Let the screen lock after inactivity.
3. Press the Shift key a few times so the screen unblanks.
4. See if the password field has focus or not. Sometimes it does, and sometimes
it doesn't.

Actual Results:  
Sometimes the password field has focus, and sometimes it doesn't.

Expected Results:  
The password field should always have focus when the screen unblanks. This was
the case in earlier versions of KDE (say, Kubuntu 14.04 LTS).

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

[plasmashell] [Bug 357387] can't use specific homepage for browser-widget

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

   Severity|grave   |minor
 CC||k...@davidedmundson.co.uk

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

[KScreen] [Bug 357392] Attaching of 2nd monitor not detected

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

Product|plasmashell |KScreen
   Assignee|k...@davidedmundson.co.uk|dvra...@kde.org
  Component|general |common

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