[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup

[Thomas Weissel]

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

--- Comment #10 from Thomas Weissel  ---
i can confirm that in 

plasma 2.8.90
frameworks 2.28.0
Qt 5.7.0

this bug is still unresolved. it just changes a little bit...

kquitapp5 plasmashell ; /usr/bin/plasmashell --shut-up

brings back my messed up icons in the panel (different bug) but this time
screen number 2 stays black..

so it keeps the problem alive now even if i kill it !

btw. why is this bug still "unconfirmed"? 
is there no developer with a multiscreen setup experiencing the same thing?

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

[kdevelop] [Bug 372280] New: Automatically generated virtual methods always use C++11 'override' keyword

[Jakub Schmidtke]

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

Bug ID: 372280
   Summary: Automatically generated virtual methods always use
C++11 'override' keyword
   Product: kdevelop
   Version: 5.0.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: sja...@gmail.com
  Target Milestone: ---

In 5.x version, generating method declaration using ctrl+space ALWAYS adds
'override' at the end. I don't use c++11 mode, so this does not compile. In the
projects settings, in "language support" I have C++03 selected. This is NOT
C++03!

Also, when generating declarations/definitions like that, new kdevelop ALWAYS
adds full namespaces - including inside the class declaration, or in the
implementation file even when "using namespace" is used.

Both of these are incredibly annoying!

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

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

[Sven Brauch]

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

--- Comment #11 from Sven Brauch  ---
That is unrelated to the original issue and looks very much like a bug in
libclang. It should be reported (and fixed) there.

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

[plasmashell] [Bug 348680] CPU Load Monitor widget with wrong layout on vertical panel

[H Rantala]

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

--- Comment #4 from H Rantala  ---
This has been OK at least for me for long time now. State to fixed?

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

[kwin] [Bug 241557] Kwin's Zoom effect conflicts with other desktop effects like Blur

[Martin Gräßlin]

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

--- Comment #20 from Martin Gräßlin  ---
It's unconfirmed because we don't care about the state. We don't go into the
bugs and mark them as confirmed. It's as simple as that: it does not have any
meaning.

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

[plasmashell] [Bug 370975] device notifier pretends it cannot mount usb device while actually mounting it

[brancaleone]

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

brancaleone  changed:

   What|Removed |Added

 CC||cedric.devill...@gmail.com

--- Comment #4 from brancaleone  ---
I'd like to confirm the same issue on openSuse 42.1, plasma 5.8.3 and qt 5.6.2.

The bug is always reproducible. I also noticed that sometimes after a reboot it
works for a while, but not everytime (and i don't reboot the laptop often).

I've also had this issue for a while.

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

[kwin] [Bug 241557] Kwin's Zoom effect conflicts with other desktop effects like Blur

[Antonio Orefice]

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

--- Comment #19 from Antonio Orefice  ---
Yes, yes, i did not mean that.
I really mean just what i asked :)

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

[kwin] [Bug 241557] Kwin's Zoom effect conflicts with other desktop effects like Blur

[Martin Gräßlin]

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

--- Comment #18 from Martin Gräßlin  ---
(In reply to Antonio Orefice from comment #17)
> Any particular reason this bug is still marked as UNCONFIRMED (!?)

This is a common confusion among users. The state has no influence on the bug
at all. For us fixing bugs it's not a question of whether the bug is in
unconfirmed or confirmed state.

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

[kwin] [Bug 241557] Kwin's Zoom effect conflicts with other desktop effects like Blur

[Antonio Orefice]

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

--- Comment #17 from Antonio Orefice  ---
Any particular reason this bug is still marked as UNCONFIRMED (!?)

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

[Touchpad-KCM] [Bug 346210] Touchpad KCM always asks to save changes

[Antonio Rojas]

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

Antonio Rojas  changed:

   What|Removed |Added

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

--- Comment #4 from Antonio Rojas  ---
Can't reproduce this anymore in 5.8.3

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

[konqueror] [Bug 372279] New: Crash on recaptcha

[Cristian Anghel]

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

Bug ID: 372279
   Summary: Crash on recaptcha
   Product: konqueror
   Version: unspecified
  Platform: FreeBSD Ports
OS: FreeBSD
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: crist...@anghel.info
  Target Milestone: ---

Application: konqueror (4.14.10)
KDE Platform Version: 4.14.10
Qt Version: 4.8.7
Operating System: FreeBSD 11.0-RELEASE-p1 amd64
Distribution (Platform): FreeBSD Ports

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

It did not load recaptcha images when completing form for FoxyForm email. While
loading recaptha, Konqueror crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
[KCrash Handler]
#8  0x00081f0c06ab in DOM::Node::Node () from /usr/local/lib/libkhtml.so.5
#9  0x00081f0ca219 in DOM::Document::Document () from
/usr/local/lib/libkhtml.so.5
#10 0x00081ee22629 in KHTMLPart::document () from
/usr/local/lib/libkhtml.so.5
#11 0x00081f05e791 in KJS::Identifier::qstring () from
/usr/local/lib/libkhtml.so.5
#12 0x00081f05f669 in KJS::Identifier::qstring () from
/usr/local/lib/libkhtml.so.5
#13 0x0008021a0c21 in QObject::event () from
/usr/local/lib/qt4/libQtCore.so.4
#14 0x00080280ac0c in QApplicationPrivate::notify_helper () from
/usr/local/lib/qt4/libQtGui.so.4
#15 0x00080280d231 in QApplication::notify () from
/usr/local/lib/qt4/libQtGui.so.4
#16 0x000800c729b7 in KApplication::notify () from
/usr/local/lib/libkdeui.so.5
#17 0x00080218d0c6 in QCoreApplication::notifyInternal () from
/usr/local/lib/qt4/libQtCore.so.4
#18 0x0008021bc6dc in QEventDispatcherUNIXPrivate::processThreadWakeUp ()
from /usr/local/lib/qt4/libQtCore.so.4
#19 0x0008021ba681 in QEventDispatcherGlib::QEventDispatcherGlib () from
/usr/local/lib/qt4/libQtCore.so.4
#20 0x0008077f2b75 in g_main_context_dispatch () from
/usr/local/lib/libglib-2.0.so.0
#21 0x0008077f2ea4 in g_main_context_pending () from
/usr/local/lib/libglib-2.0.so.0
#22 0x0008077f2f34 in g_main_context_iteration () from
/usr/local/lib/libglib-2.0.so.0
#23 0x0008021b9dde in QEventDispatcherGlib::processEvents () from
/usr/local/lib/qt4/libQtCore.so.4
#24 0x0008028abc4d in QX11Info::isCompositingManagerRunning () from
/usr/local/lib/qt4/libQtGui.so.4
#25 0x00080218a6b2 in QEventLoop::exec () from
/usr/local/lib/qt4/libQtCore.so.4
#26 0x00080218d66d in QCoreApplication::exec () from
/usr/local/lib/qt4/libQtCore.so.4
#27 0x00081657c3d8 in kdemain () from
/usr/local/lib/libkdeinit4_konqueror.so
#28 0x0040a138 in ?? ()
#29 0x0040af03 in ?? ()
#30 0x00408540 in ?? ()
#31 0x00407561 in ?? ()
#32 0x00404d1f in ?? ()
#33 0x000800631000 in ?? ()
#34 0x in ?? ()

Reported using DrKonqi

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

[kscreenlocker] [Bug 372275] New session breaks login screen locker

[bugzilla_noreply]

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

--- Comment #3 from kde.u...@mail.ru ---
No, different user.

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

[kmail2] [Bug 372278] New: Kmail won't start

[ObsoleteMan]

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

Bug ID: 372278
   Summary: Kmail won't start
   Product: kmail2
   Version: 4.14.1
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: msovi...@gmail.com
  Target Milestone: ---

Created attachment 102154
  --> https://bugs.kde.org/attachment.cgi?id=102154=edit
Error report

Akonadi Server Self-Test Report
===

Test 1:  SUCCESS


Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server
configuration and was found on your system.

File content of '/home/michael/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-michael.22RIJb/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


Test 2:  SUCCESS


Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the
recommended setup for a secure system.

Test 3:  SUCCESS


MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server
'/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure
you have the necessary read and execution rights on the server executable. The
server executable is typically called 'mysqld'; its location varies depending
on the distribution.

Test 4:  SUCCESS


MySQL server is executable.
Details: MySQL server found: 161110  1:49:22 [Warning] Using unique option
prefix key_buffer instead of key_buffer_size is deprecated and will be removed
in a future release. Please use the full name instead.
/usr/sbin/mysqld  Ver 5.5.53-0+deb8u1 for debian-linux-gnu on x86_64 ((Debian))


Test 5:  SUCCESS


No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup. The
log can be found in '/home/michael/.local/share/akonadi/db_data/mysql.err'.

Test 6:  SUCCESS


MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is
readable at /etc/akonadi/mysql-global.conf.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp 
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#
sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of
data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for
debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM
information_schema.tables WHERE table_schema not in ("mysql",
"information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show
global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other
internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables
(default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin,
8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but
more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)

[kwin] [Bug 241557] Kwin's Zoom effect conflicts with other desktop effects like Blur

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||tho...@mitterfellner.at

--- Comment #16 from Martin Gräßlin  ---
*** Bug 372264 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 372264] Full desktop zoom shows unzoomed translucent artifacts for translucent elements

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Gräßlin  ---


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

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

[Discover] [Bug 372277] New: Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

Bug ID: 372277
   Summary: Discover crashes when used to open rpm file
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: mustafa10...@gmail.com
  Target Milestone: ---

I tried to open chrome rpm using plasma-discover and it crashed, this is the
backtrace (drkonqi couldn't report it because it says "plasma-discover doesn't
provide a bug reporting address")


Application: plasma-discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185 62: movl(%rsp), %edi
[Current thread is 1 (Thread 0x7f70fd067900 (LWP 7793))]

Thread 5 (Thread 0x7f70e0b77700 (LWP 7798)):
#0  g_mutex_unlock (mutex=0x7f70d8000990) at gthread-posix.c:1348
#1  0x7f7102299ffd in g_main_context_iterate
(context=context@entry=0x7f70d8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3877
#2  0x7f710229a26c in g_main_context_iteration (context=0x7f70d8000990,
may_block=may_block@entry=1) at gmain.c:3990
#3  0x7f7109f5fd8b in QEventDispatcherGlib::processEvents
(this=0x7f70d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f7109f110ba in QEventLoop::exec (this=this@entry=0x7f70e0b76cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7f7109d6e643 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f7109d72a1a in QThreadPrivate::start (arg=0x7f70d4003650) at
thread/qthread_unix.cpp:344
#7  0x7f71076ac6ca in start_thread (arg=0x7f70e0b77700) at
pthread_create.c:333
#8  0x7f7109165f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f70e1378700 (LWP 7797)):
#0  0x7f71022df7f9 in g_mutex_lock (mutex=mutex@entry=0x7f70d4000990) at
gthread-posix.c:1336
#1  0x7f710229a258 in g_main_context_iteration (context=0x7f70d4000990,
may_block=may_block@entry=1) at gmain.c:3989
#2  0x7f7109f5fd8b in QEventDispatcherGlib::processEvents
(this=0x7f70d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7f7109f110ba in QEventLoop::exec (this=this@entry=0x7f70e1377c50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#4  0x7f7109d6e643 in QThread::exec (this=this@entry=0x564c70825080) at
thread/qthread.cpp:507
#5  0x7f710cfd6ca6 in QQuickPixmapReader::run (this=0x564c70825080) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/quick/util/qquickpixmapcache.cpp:823
#6  0x7f7109d72a1a in QThreadPrivate::start (arg=0x564c70825080) at
thread/qthread_unix.cpp:344
#7  0x7f71076ac6ca in start_thread (arg=0x7f70e1378700) at
pthread_create.c:333
#8  0x7f7109165f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f70e3fff700 (LWP 7796)):
#0  0x7f710915a00d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f710229a156 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f70dc002e70, timeout=, context=0x7f70dc000990)
at gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7f70dc000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3924
#3  0x7f710229a26c in g_main_context_iteration (context=0x7f70dc000990,
may_block=may_block@entry=1) at gmain.c:3990
#4  0x7f7109f5fd8b in QEventDispatcherGlib::processEvents
(this=0x7f70dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f7109f110ba in QEventLoop::exec (this=this@entry=0x7f70e3ffeca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7f7109d6e643 in QThread::exec (this=this@entry=0x564c6f3b4ad0) at
thread/qthread.cpp:507
#7  0x7f710a824735 in QQmlThreadPrivate::run (this=0x564c6f3b4ad0) at
/usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/ftw/qqmlthread.cpp:147
#8  0x7f7109d72a1a in QThreadPrivate::start (arg=0x564c6f3b4ad0) at
thread/qthread_unix.cpp:344
#9  0x7f71076ac6ca in start_thread (arg=0x7f70e3fff700) at
pthread_create.c:333
#10 0x7f7109165f6f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f70e97f6700 (LWP 7795)):
[KCrash Handler]
#6  0x7f7109f3c87d in QObject::disconnect (sender=0x7f70d8003860,
signal=signal@entry=0x0, receiver=receiver@entry=0x7f70e4014a70,
method=method@entry=0x0) at kernel/qobject.cpp:2956
#7  0x7f710d877fd0 in QObject::disconnect (member=0x0,
receiver=0x7f70e4014a70, this=) at
../../src/corelib/kernel/qobject.h:359
#8  QDBusConnectionPrivate::closeConnection (this=this@entry=0x7f70e4014a70) at
qdbusintegrator.cpp:1133
#9  0x7f710d8648c2 in QDBusConnectionManager::run (this=0x7f710d8da060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at

[kwin] [Bug 366651] Kwin Compositor Stops Updating Windows

[Martin Gräßlin]

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

--- Comment #6 from Martin Gräßlin  ---
> Plugin: org.kde.kwin.aurorae

Please try to use the breeze window decoration.

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

[kwin] [Bug 366651] Kwin Compositor Stops Updating Windows

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #5 from Martin Gräßlin  ---

Version
===
KWin version: 5.5.5
Qt Version: 5.5.1
Qt compile version: 5.5.1
XCB compile version: 1.11.1

Operation Mode: X11 only

Build Options
=
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11804000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==
Plugin: org.kde.kwin.aurorae
Theme: __aurorae__svg__osx
Blur: 1
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 5
decorationButtonsRight: 3, 4
borderSize: 3
gridUnit: 10
font: Ubuntu,10,-1,5,75,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Options
===
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 4
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
unredirectFullscreen: false
glSmoothScale: 2
colorCorrected: false
xrenderSmoothScale: false
maxFpsInterval: 1666
refreshRate: 0
vBlankTime: 600
glStrictBinding: false
glStrictBindingFollowsDriver: true
glCoreProfile: false
glPreferBufferSwap: 101
glPlatformInterface: 1

Screen Edges

desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
===
Multi-Head: no
Active screen follows mouse:  no
Number of Screens: 2

Screen 0:
-
Name: DVI-0
Geometry: 1920,0,1920x1080
Refresh Rate: 60

Screen 1:
-
Name: HDMI-0
Geometry: 0,0,1920x1080
Refresh Rate: 60


Compositing
===
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD CAICOS (DRM 2.43.0, LLVM 3.8.0)
OpenGL version string: 3.0 Mesa 11.2.0
OpenGL platform interface: GLX
OpenGL shading language version string: 1.30
Driver: R600G
GPU class: NI
OpenGL version: 3.0
GLSL version: 1.30
Mesa version: 11.2
X server version: 1.18.4
Linux kernel version: 4.4
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Loaded Effects:
---
zoom
slidingpopups
kwin4_effect_login
slide
screenshot
kwin4_effect_translucency
kwin4_effect_windowaperture
minimizeanimation
desktopgrid
kwin4_effect_fade
kwin4_effect_maximize
presentwindows
kwin4_effect_dialogparent
highlightwindow
blur
contrast
logout
startupfeedback
screenedge
kscreen

Currently Active Effects:
-
blur
contrast

Effect Settings:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1

slidingpopups:
fadeInTime: 150
fadeOutTime: 250

kwin4_effect_login:

slide:

screenshot:

kwin4_effect_translucency:

kwin4_effect_windowaperture:

minimizeanimation:

desktopgrid:
zoomDuration: 300
border: 10
desktopNameAlignment: 0
layoutMode: 0
customLayoutRows: 2
usePresentWindows: true

kwin4_effect_fade:

kwin4_effect_maximize:

presentwindows:

[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget

[Sebastian Kuhne]

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

Sebastian Kuhne  changed:

   What|Removed |Added

 CC||sebastiankuhne1@googlemail.
   ||com

--- Comment #15 from Sebastian Kuhne  ---
I have a similar issue reported to openSUSE bugzilla already
(https://bugzilla.opensuse.org/show_bug.cgi?id=1008797)

I am running openSUSE tumbleweed, Plasma 5.8.3, KDE Framework 5.27.0, QT 5.7.0.

Maybe my analysis helps in the finding of the issue:
- If I enable standard calendar applet with default settings, everything is ok.
- If I enable "PIM events Plugin" only in "Settings", the applet crashes and
also plasmashell crahes.
- If I additionally enable in the settings "PIM events Plugin" a certain number
of calendars synchronized with google calendar in PIM everything is fine again.

Again, I know this is not exactly the same behaviour as described in the
original thread but maybe it helps to understand the issue.

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

[kscreenlocker] [Bug 372275] New session breaks login screen locker

[Martin Gräßlin]

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

--- Comment #2 from Martin Gräßlin  ---
Are you starting a new session with same user name?

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

[kscreenlocker] [Bug 372197] wrong XAUTHORITY setting leads to crashing kscreenlocker_greeter

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

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

--- Comment #9 from Martin Gräßlin  ---
Good investigation! But that also means it's not a bug in our software. We can
hardly protect against another process replacing the authority file ;-)

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

[kdevelop] [Bug 371645] "Program received signal SIGSEGV, Segmentation fault" while idle

[bugzilla_noreply]

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

--- Comment #10 from red...@cox.net ---
I have used the AppImage on a modern linux distro and do not have any problems.
The code base is very small for that project though so the background parse
does not run much (only a couple threads too).

Back trace for the crash when parsing the linux kernel source:

(gdb) bt
#0  0x7fffacfd9e8c in clang::analyze_format_string::ArgType::matchesType ()
   from kdevelop5/KDevelop-5.0.2-1-x86_64/usr/lib/libclang.so.3.8
#1  0x0aa977c9 in ?? ()
#2  0x0002 in ?? ()
#3  0x09d676e0 in ?? ()
#4  0x7fffac4198b8 in (anonymous
namespace)::CheckScanfHandler::HandleScanfSpecifier ()
   from kdevelop5/KDevelop-5.0.2-1-x86_64/usr/lib/libclang.so.3.8
#5  0x7fffacfe2c98 in clang::analyze_format_string::ParseScanfString ()
   from kdevelop5/KDevelop-5.0.2-1-x86_64/usr/lib/libclang.so.3.8
#6  0x71253ec8 in main_arena () from /lib64/libc.so.6
#7  0x049df6d0 in ?? ()
#8  0x7fffced4c0e0 in ?? ()
#9  0x00010050 in ?? ()
#10 0x04a3f3e0 in ?? ()
#11 0x7fffced4c170 in ?? ()
#12 0x in ?? ()

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

[digikam] [Bug 372217] The results of the Duplicates are currently sorted by the image id and sortable by name and count if similars. But it should be sortable by the similarity of the duplicates, too

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||5.4.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/04c4024d4c7d3f03d91ed89
   ||2286c2de78abeeb37
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from caulier.gil...@gmail.com ---
Git commit 04c4024d4c7d3f03d91ed892286c2de78abeeb37 by Gilles Caulier.
Committed on 10/11/2016 at 05:33.
Pushed by cgilles into branch 'master'.

Apply patches #102120 and #102121 from Mario Frank

102120: Extended the duplicates search list view. Now, the average
similarity of the found duplicates (excluding the original image) is shown as
table column. Sorting the result set by the average similarity is thus
possible. To implement this feature, the haariface had to be modified. It
returns a map of average similarities to a map of image ids to the set of
similar images instead of the map of image ids to the set of similar images.
Communicating the average similarity to the search list view was not possible
via slots and signals and this would have lead to sending a map of image ids
to average similarities and then distributing the appropriate average
similarity to the correct FindDuplicateAlbumItem. Instead, the average
similarity is communicated via the SearchXml-query as a field of the group.
This way, the correct item gets the correct similarity automatically. The
evaluation of the new field by an SQL query is surpressed by the introduction
of noEffect fields which need to have a prefix "noeffect_". So, the log is
not polluted by unnecessary debug information.

102121: The items in the FindDuplicatesAlbum were sorted by
lexicographic order which does not make sense for the average similarity
column (e.g. 100.00 is not correctly sorted). Thus, the less than operator
was adopted such that for the average similarity column, arithmetic order is
used. To make the code more stable against regressions due to reordering the
columns, an enum was introduced.
FIXED-IN: 5.4.0
CCMAIL: fr...@uni-potsdam.de

M  +60   -30   libs/database/haar/haariface.cpp
M  +5-5libs/database/haar/haariface.h
M  +1-1libs/database/item/imagelister.cpp
M  +5-1libs/database/item/imagequerybuilder.cpp
M  +3-2utilities/fuzzysearch/findduplicatesalbum.cpp
M  +27   -4utilities/fuzzysearch/findduplicatesalbumitem.cpp
M  +9-0utilities/fuzzysearch/findduplicatesalbumitem.h
M  +4-4utilities/fuzzysearch/findduplicatesview.cpp
M  +9-6utilities/fuzzysearch/fuzzysearchview.cpp

http://commits.kde.org/digikam/04c4024d4c7d3f03d91ed892286c2de78abeeb37

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

[digikam] [Bug 372217] The results of the Duplicates are currently sorted by the image id and sortable by name and count if similars. But it should be sortable by the similarity of the duplicates, too

[bugzilla_noreply]

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

--- Comment #3 from caulier.gil...@gmail.com ---
ok forget my previous comment, i forget to apply patch 1 before patch 2...

[gilles@localhost core]$ git reset --hard   
HEAD is now at a503172 update   

[gilles@localhost core]$ patch -p1 <
DIGIKAM_DuplicatesSearch_ResultSet_AverageSimilarity.patch  
patching file libs/database/haar/haariface.cpp  
patching file libs/database/haar/haariface.h
patching file libs/database/item/imagelister.cpp
patching file libs/database/item/imagequerybuilder.cpp  
patching file utilities/fuzzysearch/findduplicatesalbum.cpp 
patching file utilities/fuzzysearch/findduplicatesalbumitem.cpp 

[gilles@localhost core]$ patch -p1 <
DIGIKAM_DuplicatesSearch_ResultSet_ArithmeticOrder.patch 
patching file utilities/fuzzysearch/findduplicatesalbumitem.cpp 
patching file utilities/fuzzysearch/findduplicatesalbumitem.h   

[gilles@localhost core]$

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

[digikam] [Bug 372217] The results of the Duplicates are currently sorted by the image id and sortable by name and count if similars. But it should be sortable by the similarity of the duplicates, too

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #2 from caulier.gil...@gmail.com ---
Mario,

After to apply your patch from bug #369051, I cannot apply the file patch over
source code :

[gilles@localhost core]$ patch -p1 <
DIGIKAM_DuplicatesSearch_ResultSet_ArithmeticOrder.patch 
patching file utilities/fuzzysearch/findduplicatesalbumitem.cpp
Hunk #1 FAILED at 64.
Hunk #2 FAILED at 79.   
Hunk #3 succeeded at 102 (offset -10 lines).
Hunk #4 succeeded at 120 (offset -10 lines).
2 out of 4 hunks FAILED -- saving rejects to file
utilities/fuzzysearch/findduplicatesalbumitem.cpp.rej   
patching file utilities/fuzzysearch/findduplicatesalbumitem.h   

Gilles Caulier

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

[digikam] [Bug 369051] Too low similarity threshold in fuzzy/duplicate search bloats the results with potentially unwished high-similarity results [patch]

[bugzilla_noreply]

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

--- Comment #7 from caulier.gil...@gmail.com ---
>Next step for me is to review your new patch from bug #372217. Note that your
>next patch must close certainly bug #302923 (please confirm).

I respond myself:

your patch from bug #372217 cannot solve bug #302923, because patch is
dedicated to sort search albums from left sidebar, not the icon view on the
center.

I will appreciate a patch aver icon-view model/view to be able to sort by
similarly level. Thanks in advance

Gilles Caulier

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

[digikam] [Bug 369051] Too low similarity threshold in fuzzy/duplicate search bloats the results with potentially unwished high-similarity results [patch]

[bugzilla_noreply]

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

--- Comment #6 from caulier.gil...@gmail.com ---
Mario,

Your patch is now applied to current implementation and will be avaialble for
next 5.4.0 release.

Next step for me is to review your new patch from bug #372217. Note that your
next patch must close certainly bug #302923 (please confirm). 

In parallel, can you check what can be do to improve again duplicate searches
tool with:

- bug #261417 : the searches album counter is not updated.
- bug #353331 : typically this one can be certainly closed as we can limit
search to a specific physical or virtual album. Please just review to confirm.
- bug #207188 : as i remember, the algorithm to process fingerprints over image
take a care about colors contents (else, this will have no sense...). So i"m
not sure if this file is valid...
- bug #274360 : i cannot figure why some king of image type are ignored. All
image format supported by digiKam will be processed while fingerprints
computation and searches.

Again, thanks for your contributions. I appreciate the quality of your patches,
which a a pleasure to review.

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

[digikam] [Bug 369051] Too low similarity threshold in fuzzy/duplicate search bloats the results with potentially unwished high-similarity results [patch]

[bugzilla_noreply]

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

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

   What|Removed |Added

   Version Fixed In||5.4.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/afe577f0b297a343ab412ce
   ||95c1f75303edfb18b
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from caulier.gil...@gmail.com ---
Git commit afe577f0b297a343ab412ce95c1f75303edfb18b by Gilles Caulier.
Committed on 10/11/2016 at 04:48.
Pushed by cgilles into branch 'master'.

Apply big patch #101176 from Mario Frank

This one extended the findduplicatesview and fuzzysearchview with an
additional QSpinBox which denotes the maximum similarity. The new QSpinBox
has a minimum value that is the current value of the minimal similarity
threshold. When the minimum threshold is altered, the range of the new
QSpinBox is updated. If the minimum threshold is increased beyond the current
value of the new QSpinBox, the value of the new QSpinBox is increased
automatically. In the fuzzysearchview, altering the maximum similarity also
triggers the reuild of the similar images album. The extension can be highly
valuable if you knowingly want to ignore almost identical images but want to
find images that have a similarity of, let's say 50-60%, due to resizing,
cropping or something similar, without bloating your image pane.
FIXED-IN: 5.4.0
CCMAIL: fr...@uni-potsdam.de

M  +2-0app/utils/searchmodificationhelper.cpp
M  +1-0app/utils/searchmodificationhelper.h
M  +4-3libs/database/dbjobs/dbjob.cpp
M  +16   -5libs/database/dbjobs/dbjobinfo.cpp
M  +7-3libs/database/dbjobs/dbjobinfo.h
M  +27   -16   libs/database/haar/haariface.cpp
M  +9-8libs/database/haar/haariface.h
M  +9-2libs/database/item/imagelister.cpp
M  +53   -25   utilities/fuzzysearch/findduplicatesview.cpp
M  +1-0utilities/fuzzysearch/findduplicatesview.h
M  +58   -11   utilities/fuzzysearch/fuzzysearchview.cpp
M  +2-1utilities/fuzzysearch/fuzzysearchview.h
M  +16   -10   utilities/maintenance/duplicatesfinder.cpp
M  +2-2utilities/maintenance/duplicatesfinder.h

http://commits.kde.org/digikam/afe577f0b297a343ab412ce95c1f75303edfb18b

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

[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup

[Kyle]

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

Kyle  changed:

   What|Removed |Added

 CC||kylejv...@gmail.com

--- Comment #9 from Kyle  ---
I have a laptop and external screen, My laptop screen has my taskbar and both
desktops have the same background. When my computer wakes from sleep, sometimes
the laptop screen is black and I am not able to right click and assign a
background again. Restart fixes the issue

Plasma 5.8.2 Debian Stretch

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

[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows

[Kyle]

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

Kyle  changed:

   What|Removed |Added

 CC||kylejv...@gmail.com

--- Comment #14 from Kyle  ---
I just got this on Plasma 5.8.2 on Debian Stretch

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

[digikam] [Bug 123097] SCAN : ignore some directories in digiKam [patch]

[bugzilla_noreply]

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

--- Comment #30 from caulier.gil...@gmail.com ---
Jan,

Any progress here to be able to include your patch in next 5.4.0 release ?

Thanks in advance 

Gilles Caulier

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

[muon] [Bug 372276] New: pdates never happens after installation of kubuntu 14.01 software 32 bit version

[MUTHU]

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

Bug ID: 372276
   Summary: pdates never happens after installation of kubuntu
14.01 software 32 bit version
   Product: muon
   Version: 5.5.3
  Platform: Other
OS: OpenBSD
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: agnipe...@yahoo.co.in
CC: silh...@gmail.com
  Target Milestone: ---

Updates never happens after installation of kubuntu 14.01 software 32 bit
version

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

[kscreenlocker] [Bug 372275] New session breaks login screen locker

[bugzilla_noreply]

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

--- Comment #1 from kde.u...@mail.ru ---
Here is the link to KDE Neon forum where I posted about this problem initially:
https://forum.kde.org/viewtopic.php?f=309=137086

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

[kscreenlocker] [Bug 372275] New session breaks login screen locker

[bugzilla_noreply]

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

kde.u...@mail.ru changed:

   What|Removed |Added

 CC||kde.u...@mail.ru

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

[kscreenlocker] [Bug 372275] New: New session breaks login screen locker

[bugzilla_noreply]

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

Bug ID: 372275
   Summary: New session breaks login screen locker
   Product: kscreenlocker
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: greeter
  Assignee: plasma-b...@kde.org
  Reporter: kde.u...@mail.ru
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

I am running KDE Neon with latest updates (Plasma 5.8.3 at this moment). Every
time I start a new session, when I return to the initial one (ctrl+alt+F7) I
get black screen saying that screen locker is broken and I should go to virtual
terminal and run "loginctl unlock-sessions".

Here is my log:
lock called
Lock window Id:  25165846
CreateNotify: 25165846
UnmapNotify: 25165846
CreateNotify: 46137347
CreateNotify: 46137350
CreateNotify: 46137352
CreateNotify: 46137354
CreateNotify: 46137356
MapNotify: 46137354
MapNotify: 25165846
CreateNotify: 46137358
powerdevil: ACTIVE SESSION PATH CHANGED: "/"
powerdevil: Switched to inactive session - leaving unchanged
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kscreenlocker_greet path =
/usr/lib/x86_64-linux-gnu/libexec pid = 2092
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
--immediateLock --graceTime 5000 --ksldfd 73
UnmapNotify: 46137354
UnmapNotify: 25165835
UnmapNotify: 25165835
powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_33"
powerdevil: Current session is now inactive
CreateNotify: 46137347
CreateNotify: 46137350
CreateNotify: 46137352
CreateNotify: 46137354
CreateNotify: 46137356
MapNotify: 46137354
uhoh! duplicate!
uhoh! duplicate!
CreateNotify: 46137358
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kscreenlocker_greet path =
/usr/lib/x86_64-linux-gnu/libexec pid = 2154
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
--immediateLock --graceTime 5000 --ksldfd 64
UnmapNotify: 46137354
CreateNotify: 46137347
CreateNotify: 46137350
CreateNotify: 46137352
CreateNotify: 46137354
CreateNotify: 46137356
MapNotify: 46137354
uhoh! duplicate!
uhoh! duplicate!
CreateNotify: 46137358
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kscreenlocker_greet path =
/usr/lib/x86_64-linux-gnu/libexec pid = 2174
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
--immediateLock --graceTime 5000 --ksldfd 64
UnmapNotify: 46137354
QXcbConnection: XCB error: 3 (BadWindow), sequence: 1, resource id:
46137354, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 15556, resource id:
46137354, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 15557, resource id:
46137354, major code: 20 (GetProperty), minor code: 0
CreateNotify: 56623107
CreateNotify: 56623110
CreateNotify: 56623112
CreateNotify: 56623114
CreateNotify: 56623116
MapNotify: 56623114
CreateNotify: 56623118
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kscreenlocker_greet path =
/usr/lib/x86_64-linux-gnu/libexec pid = 2183
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet
--immediateLock --graceTime 5000 --ksldfd 64
UnmapNotify: 56623114
powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_34"
powerdevil: Current session is now inactive
powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_32"
powerdevil: Current session is now active
powerdevil: Can't contact ck
powerdevil: We are now into activity  "6bcf02db-444e-4ca6-96f8-9d206adb7798"
powerdevil: () ()
powerdevil: () ()
powerdevil: Loading profile for plugged AC
powerdevil: Activity is not forcing a profile
powerdevil:
powerdevil: Loading timeouts with  60
CreateNotify: 56623107
kdeinit5: Got SETENV 'KDE_MULTIHEAD=false' from launcher.
CreateNotify: 58720259
Initializing  "kcm_input" :  "kcminit_mouse"
kdeinit5: Got SETENV 'XCURSOR_THEME=breeze_cursors' from launcher.
CreateNotify: 56623112
QXcbConnection: XCB error: 3 (BadWindow), sequence: 16761, resource id:
56623112, major code: 18 (ChangeProperty), minor code: 0
kdeinit5: Got SETENV 'KDE_MULTIHEAD=false' from launcher.
Initializing  "kcm_input" :  "kcminit_mouse"
kdeinit5: Got SETENV 'XCURSOR_THEME=breeze_cursors' from launcher.
CreateNotify: 58720264
QXcbConnection: XCB error: 3 (BadWindow), sequence: 16950, resource id:
58720264, major code: 18 (ChangeProperty), minor code: 0
powerdevil: ACTIVE SESSION PATH CHANGED: "/"
powerdevil: Switched to inactive session - leaving unchanged
powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_35"
powerdevil: Current session is now inactive
Grab Released
powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/_32"
powerdevil: Current session is now 

[Touchpad-KCM] [Bug 346210] Touchpad KCM always asks to save changes

[Roman]

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

Roman  changed:

   What|Removed |Added

 CC||subd...@gmail.com

--- Comment #3 from Roman  ---
Still relevant?

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

[plasmashell] [Bug 372274] New: Plasmashell High CPU usage

[GLutz]

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

Bug ID: 372274
   Summary: Plasmashell High CPU usage
   Product: plasmashell
   Version: 5.8.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: gustavo.alma...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.4.30-1-MANJARO x86_64
Distribution: "Manjaro Linux"

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

Sometimes the plasmashell starts having high CPU usage between 50 - 90%, I
couldn't spot what really triggers this behavior, I noticed this downloading
torrents (using qBitTorrent) or big files (like games from steam), and today
using unetbootin. All I do is stop the service and start it again, then it runs
normaly untill restart.

The crash can be reproduced sometimes.

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

Thread 10 (Thread 0x7f50377ff700 (LWP 2557)):
#0  0x7f51115364ed in read () at /usr/lib/libc.so.6
#1  0x7f510481df81 in pa_read () at
/usr/lib/pulseaudio/libpulsecommon-9.0.so
#2  0x7f5104ead50e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0
#3  0x7f5104eadf80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7f5104eae040 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7f5104ebc069 in  () at /usr/lib/libpulse.so.0
#6  0x7f510484ced8 in  () at /usr/lib/pulseaudio/libpulsecommon-9.0.so
#7  0x7f5110d3d454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f51115437df in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f5040b01700 (LWP 2556)):
#0  0x7f510c847db9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f510c801c95 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f510c8026ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f510c80289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f5111e5c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f5111e0623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f5111c290f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f5114f8c2d5 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7f5111c2dd78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f5110d3d454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f51115437df in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f5052993700 (LWP 2550)):
#0  0x7f510c801d58 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7f510c8026ab in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f510c80289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5111e5c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f5111e0623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5111c290f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5054ebf0a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7f5111c2dd78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f5110d3d454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f51115437df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f505fc06700 (LWP 2547)):
#0  0x7f511153a48d in poll () at /usr/lib/libc.so.6
#1  0x7f510c802786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f510c80289c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f5111e5c72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f5111e0623a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5111c290f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5115b2b856 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7f5111c2dd78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f5110d3d454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f51115437df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f50f2399700 (LWP 2546)):
#0  0x7f5110d4310f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f51175bbac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f51175bbb09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f5110d3d454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f51115437df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f50f3fff700 (LWP 2545)):
#0  0x7f51115364ed in read () at /usr/lib/libc.so.6
#1  0x7f510c846a10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f510c802235 in g_main_context_check () at 

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[RN]

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

--- Comment #9 from RN  ---
Is there more information needed to mark this report as confirmed? How can I
help?
Regards.

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

[kdev-python] [Bug 372273] New: @property properties shown as functions

[Nicolás Alvarez]

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

Bug ID: 372273
   Summary: @property properties shown as functions
   Product: kdev-python
   Version: 5.0.2
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language support
  Assignee: m...@svenbrauch.de
  Reporter: nicolas.alva...@gmail.com
  Target Milestone: ---

It seems kdev-python doesn't support @property at all. If I declare a property
getter with it, the property is shown as a function. For example:

class Foo:
@property
def prop(self):
return "meow"

def f(self):
a = self.prop
# 'prop' and 'a' are shown as functions, but they should be str

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

[plasmashell] [Bug 372272] New: Plasmashell crash after upgrade to 4.4.0-47-generic 11/9/2016

[bugzilla_noreply]

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

Bug ID: 372272
   Summary: Plasmashell crash after upgrade to 4.4.0-47-generic
11/9/2016
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: riffr...@riffraffs.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
System will not come up after rebooting after patching to new kernel.  Must run
startx from CLI to get any desktop. Two more plasmashell crashes in quick
succession after this one:
Executable: plasmashell PID: 2714 Signal: Aborted (6) Time: 11/9/16 18:37:53
Executable: plasmashell PID: 2755 Signal: Aborted (6) Time: 11/9/16 18:37:54

The crash can be reproduced every time.

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

Thread 7 (Thread 0x7f331b42e700 (LWP 2699)):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7f33caf5ae92 in __GI___pthread_mutex_lock (mutex=0x7f33c7bc2a40) at
../nptl/pthread_mutex_lock.c:115
#2  0x7f33c795f9f2 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#3  0x7f33c7964290 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#4  0x7f33c79647aa in ?? () from /usr/lib/nvidia-304/libGL.so.1
#5  0x7f33c433fbf7 in ?? () from
/usr/lib/nvidia-304/tls/libnvidia-tls.so.304.132
#6  0x7f33c854e740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f33c850ae84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f33c850b340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f33c850b4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f33cc0a27eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f33cc049b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f33cbe66834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f3310c217d7 in KCupsConnection::run() () from
/usr/lib/x86_64-linux-gnu/libkcupslib.so
#14 0x7f33cbe6b7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f33c7965754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#16 0x7f33caf5870a in start_thread (arg=0x7f331b42e700) at
pthread_create.c:333
#17 0x7f33cb78182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f33a1f9c700 (LWP 2513)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f33d0ab3bd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f33d0ab3c19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f33c7965754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#4  0x7f33caf5870a in start_thread (arg=0x7f33a1f9c700) at
pthread_create.c:333
#5  0x7f33cb78182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f33a3868700 (LWP 2512)):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7f33caf5ae92 in __GI___pthread_mutex_lock (mutex=0x7f33c7bc2a40) at
../nptl/pthread_mutex_lock.c:115
#2  0x7f33c795f9f2 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#3  0x7f33c7964290 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#4  0x7f33c79647aa in ?? () from /usr/lib/nvidia-304/libGL.so.1
#5  0x7f33c433fbf7 in ?? () from
/usr/lib/nvidia-304/tls/libnvidia-tls.so.304.132
#6  0x7f33c854e740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f33c850ae84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f33c850b340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f33c850b4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f33cc0a27eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f33cc049b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f33cbe66834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f33ce70e3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7f33cbe6b7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f33c7965754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#16 0x7f33caf5870a in start_thread 

[kmymoney4] [Bug 370227] Crash on exit

[RJVB]

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

--- Comment #13 from RJVB  ---
Looking at the backtrace again I'm not sure that this is a likely result of
using delete instead of deleteLater, but you could begin by checking that
AqBanking dialog. If it's a KDE dialog it could be a prime candidate for using
deleteLater.

In fact, I suspect the bug is in gwenhywfar, possible AqBanking, not in KMM.
Though it may be possible to avoid the crash by deferring a KMM exit request
until the ongoing operation is finished or aborted properly.

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

[plasmashell] [Bug 372271] New: Black screen on dual monitor

[Federico]

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

Bug ID: 372271
   Summary: Black screen on dual monitor
   Product: plasmashell
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: federico127...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.5-2-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Boot the PC
- Unusual behavior I noticed:
Dual monitor (via VGA) crash Plasma. The second monitor (of Laptop) is black. I
have different background for these monitor.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7fb87cdbc700 (LWP 2290)):
#0  0x7fb93e0f448d in poll () at /usr/lib/libc.so.6
#1  0x7fb9393bc786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fb9393bc89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fb93ea1672b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fb93e9c023a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fb93e7e30f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fb87f2e80a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7fb93e7e7d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fb88c1ad700 (LWP 2281)):
#0  0x7fb9393bbc95 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7fb9393bc6ab in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fb9393bc89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fb93ea1672b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fb93e9c023a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fb93e7e30f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fb9426e5856 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7fb93e7e7d78 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fb916fac700 (LWP 2280)):
#0  0x7fb93d8fd10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb944175ac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fb944175b09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fb924d60700 (LWP 2279)):
#0  0x7fb93ea15e73 in  () at /usr/lib/libQt5Core.so.5
#1  0x7fb9393bbc89 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fb9393bc6ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fb9393bc89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fb93ea1672b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fb93e9c023a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fb93e7e30f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fb941b462d5 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7fb93e7e7d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fb9267c0700 (LWP 2218)):
#0  0x7fb93e7def22 in QMutex::lock() () at /usr/lib/libQt5Core.so.5
#1  0x7fb93ea16009 in  () at /usr/lib/libQt5Core.so.5
#2  0x7fb9393bc179 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fb9393bc724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fb9393bc89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fb93ea1672b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fb93e9c023a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fb93e7e30f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fb941b462d5 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7fb93e7e7d78 in  () at /usr/lib/libQt5Core.so.5
#10 0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fb927fff700 (LWP 2175)):
#0  0x7fb93e7def20 in QMutex::lock() () at /usr/lib/libQt5Core.so.5
#1  0x7fb93ea15e9f in  () at 

[kscreenlocker] [Bug 372197] wrong XAUTHORITY setting leads to crashing kscreenlocker_greeter

[Stefan Brüns]

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

--- Comment #8 from Stefan Brüns  ---
Actually, both ~/.Xauthority and /tmp/xauth-$UID-_$DISPLAY are correct
locations, see https://cgit.kde.org/kinit.git/tree/src/kdeinit/kinit.cpp#n1470
for details.

The problem is caused by sddm.

When selecting "Switch User" and then starting a new session for an already
logged in user (which I triggered inadvertently from the lock screen, which
sometimes misbehaves on a dual screen setup - different bug), sddm replaces the
contents of the ~/Xauthority file.

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

[neon] [Bug 372007] Heaptrack isn't packaged by neon

[Jonathan Riddell]

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

--- Comment #4 from Jonathan Riddell  ---
heaptrack is now in Neon developer unstable edition

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

[Spectacle] [Bug 372270] New: Display pixel-width and height of selected region before taking a screenshot

[bugzilla_noreply]

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

Bug ID: 372270
   Summary: Display pixel-width and height of selected region
before taking a screenshot
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: cher...@aip.de
  Target Milestone: ---

When using the rectangular selection to make a screenshot, the width and height
of the selected region should (optionally) be shown.  This is essential for
making a series of pixel perfect screenshot.  

The this feature was present in KSnapshot but not ported to Spectacle.

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

[Spectacle] [Bug 358641] Have Spectacle remember filename

[bugzilla_noreply]

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

cher...@aip.de changed:

   What|Removed |Added

 CC||cher...@aip.de

--- Comment #4 from cher...@aip.de ---
Yes - this is a big feature missing in spectacle compared to KSnapshot before. 
Pleas

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

[kmymoney4] [Bug 370227] Crash on exit

[Marko Käning]

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

--- Comment #12 from Marko Käning  ---
So, what are we going to do about this crash now?

Which delete()'s exactly should I replace by deleteLater()?

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

[konversation] [Bug 372269] New: requesting support for SASL external protocol

[jon]

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

Bug ID: 372269
   Summary: requesting support for SASL external protocol
   Product: konversation
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: protocol
  Assignee: konversation-de...@kde.org
  Reporter: skpl1...@gmail.com
  Target Milestone: ---

please add support for SASL external protocol so as to allow connecting to
freenode through hidden service

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

[kmymoney4] [Bug 372254] Crash when importing CSV file

[allan]

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

--- Comment #1 from allan  ---
(In reply to allan from comment #0)
> The crash of KMM seems to happen every time, at least with one particular
> account.  I get Segmentation fault (core dumped)
> but with no other detail.

The Segmentation fault (core dumped) is not related to this problem, but seems
to occur whenever KMM is closed.

The main problem here was triggered by resource file content for this account,
which I have now removed.  What actually caused the crash looks to be an out of
bounds index, but unfortunately I'm not familiar with the logic here.

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

[krita] [Bug 372268] New: Application crash on creation of document

[bugzilla_noreply]

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

Bug ID: 372268
   Summary: Application crash on creation of document
   Product: krita
   Version: 3.0.1.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: vra...@live.fr
  Target Milestone: ---

File creation scenarii:
---
1)
* Open Krita
* Do a ctrl-N
* Configure new file
* Click on Create

2)
* Open Krita
* Click on File > New
* Configure new file
* Click on Create

Expected behavior:
--
A new file is open.

Current behavior:
-
The application close itself without any warning.

*
-
*

Open file scenarii:
---
1)
* Open Krita
* Do a ctrl-O
* Select a picture file (e.G. .png)
* Click on Open

2)
* Open Krita
* Click on File > Open
* Select a picture file (e.G. .png)
* Click on Open

Expected behavior:
--
The selected file is open.

Current behavior:
-
The application close itself without any warning.

*
-
*

Information:

1) My Krita is in French, so I don't have english labels (I assumed labels like
"open" or "create" in the issue description).
2) I'm on a Manjaro Linux (ArchLinux distribution)
3) I installed Krita with pacman, the default package manager
4) I never opened Krita before
5) I did not any configuration of the application
6) If I open Krita in a terminal, after click on create or open, I got those
logs:
--
Could not load cursor from qrc, trying filesystem "tool_rectangle_cursor.png"
Could not load cursor from filesystem "tool_rectangle_cursor.png"
libpng warning: iCCP: too many profiles
krita.lib.flake: "InteractionTool" : action "object_order_lower" conflicts with
canvas action "rotate_canvas_left" shortcut: "Ctrl+["
krita.lib.flake: "InteractionTool" : action "object_order_raise" conflicts with
canvas action "rotate_canvas_right" shortcut: "Ctrl+]"
krita.lib.flake: "InteractionTool" : action "object_order_lower" conflicts with
canvas action "rotate_canvas_left" shortcut: "Ctrl+["
krita.lib.flake: "InteractionTool" : action "object_order_raise" conflicts with
canvas action "rotate_canvas_right" shortcut: "Ctrl+]"
krita.lib.flake: "KritaShape/KisToolBrush" : action "object_order_lower"
conflicts with canvas action "rotate_canvas_left" shortcut: "Ctrl+["
krita.lib.flake: "KritaShape/KisToolBrush" : action "object_order_raise"
conflicts with canvas action "rotate_canvas_right" shortcut: "Ctrl+]"
Erreur de segmentation (core dumped)
--

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

[ktorrent] [Bug 372267] New: A way to bulk edit torrent announcers

[truf]

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

Bug ID: 372267
   Summary: A way to bulk edit torrent announcers
   Product: ktorrent
   Version: 4.3.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: trufano...@gmail.com
  Target Milestone: ---

There is a way to add new torrent tracker or disable\enable existing one in
KTorrent. But this can't be made for several torrents at once.

Usecase is following.
Sometimes torrent trackers have to change their domain name. Especially if they
are forced to do this by legal problems. And then they ask users to change
announcers in torrents they seed to something new keeping passkey value. Like
"please change our announcer http://olddomain.us?annonce.php?uid=passkey; to
http://newdomain.us?annonce.php?uid=passkey in all torrents you seed or
redownload them". It's pretty annoying to make these changes manually if you
have a lot of torrents seeding.

uTorrent has GUI features that let user make such changes for all torrents per
once. You just need to add tracker column to the list of torrents, sort by this
column, multiselect right torrents and then edit tracker value.
And nothing like that in KTorrent. So user forced to pay with bash and regexps
to edit KTorrent files.

Would be great if such functionality will be added in fueature versions.

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

[kde] [Bug 372266] New: plasmashell crash (on resume from sleep)

[Dean Schaf]

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

Bug ID: 372266
   Summary: plasmashell crash (on resume from sleep)
   Product: kde
   Version: unspecified
  Platform: PCLinuxOS
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: deanyourfriendi...@yahoo.com
  Target Milestone: ---

Created attachment 102153
  --> https://bugs.kde.org/attachment.cgi?id=102153=edit
Text file with allegedly relevant info about the crash

Application: plasmashell (5.8.3)

Qt Version: 5.6.2
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-pclos1 x86_64
Distribution: "PCLinuxOS"

-- Information about the crash:


The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

BUT HERE'S WHAT WAS HAPPENING WHEN THE CRASH OCCURRED:
I had put the computer on standby (sleep).  When I came back to use it
and woke it up, I was greeted with the notification that the plasmashell
had crashed.  And, I was given the chance to report the bug.

Tragically, the bug-report creation system is an epic failure, so I
put this silly blurb together just for Esses & Gees.

Report to https://bugs.kde.org/

Application: Plasma (plasmashell), signal: Segmentation fault
[Current thread is 1 (process 3452)]

Thread 1 (process 3452):
#0  0x7fac7aa7467f in ?? ()
#1  0x in ?? ()

About The System

SOFTWARE
KDE Framworks Version: 5.27.0
Qt Version: 5.6.2
Kernel Version: 4.8.6-pclos1
OS Type: 64-bit

HARDWARE
CPU: AMD Athlon(tm) X4 860K Quad-Core Processor
RAM: 16 GBs (2 x 8 GBs)
DISKS:
* sda Seagate ST3750528S   HDD
  ⱺ sda1 . Linux Swap
  ⱺ sda2 . ext4

* sdb Seagate ST3320620AS  HDD
  ⱺ sdb1 . ext4

* sdc SanDisk SDSSDA120G   SSD
  ⱺ sdc1 . ext4   /
  ⱺ sdc2 . ext4   /home

GRAPHICAL INFORMATION
Server Information
Name of the Display::0
Vendor String:  The X.Org Foundation
Vendor Release Number:  11,804,000
Version Number: 11.0

Display Adapter: nVidia GeForce GT 610 GC LP 2GB DDR3 64BIT

Motherboard: MSI A58M-E33

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

[kst] [Bug 372265] "Change Data File" does not update file name references in text box

[bugzilla_noreply]

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

netterfi...@astro.utoronto.ca changed:

   What|Removed |Added

 CC||netterfield@astro.utoronto.
   ||ca

--- Comment #1 from netterfi...@astro.utoronto.ca ---
These automatic strings automatically created by the data source are the
problem.  This is not (under the hood) a DataScalar, so it never shows up in
the list of things to change when you change datasources.

A work around for now is to create->string and then create a data string from
the data source from field FILE.  This properly updates when you "change
datasource".
However, you have to hit reload to actually redraw it.  I was working on fixing
that on the way into work this morning.

What to do with the automatic scalars and automatic vectors is more
problematic.  
-How valuable are these automatic scalars/vectors.  Would it be better to just
create them with create->scalar and create->string so they are consistent with
everything else?  There should be create scalar and create string shortcut
icons in the label dialogs in any case.

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

[kdenlive] [Bug 372020] Ungrouped clips don't stay ungrouped.

[Edward]

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

--- Comment #4 from Edward  ---
Ok, I saw an update for Kdenlive (16.08.3) and thought I'd see if the issue was
taken care of. Sadly, it had not. However, I thought I'd try something. I
ungrouped the clips and tried shifting the audio. I could not move it. I then
tried to shift the video and I could shift it. Taking a risk I shifted it a few
seconds, saved and quit. When I re-opened the project the clips were ungrouped
and in their last saved positions. At this point I could also shift the audio
clip. But when I returned them so they aligned, saved, quit, and re-opened they
were grouped again.

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

[plasmashell] [Bug 217950] Ability to set desktop wallpaper via a dbus command

[Josep Febrer]

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

Josep Febrer  changed:

   What|Removed |Added

 CC||jfeb...@gmail.com

--- Comment #47 from Josep Febrer  ---
One thing I don't understand is why it only works when the widgets aren't
locked.
When the widgets are locked in Plasma, you are able to change the wallpaper
with the desktop settings, so I think by coherence it should be able to change
the wallpaper with dbus even if the widgets are locked.

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

[kst] [Bug 372265] New: "Change Data File" does not update file name references in text box

[Ben Lewis]

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

Bug ID: 372265
   Summary: "Change Data File" does not update file name
references in text box
   Product: kst
   Version: 2.0.8
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@kde.org
  Reporter: benlewis...@gmail.com
  Target Milestone: ---

I would like to display some header information on a plot and have that
information update as the underlying data file changes. Currently this does not
work for me.

Using a text box I can display information (string data) contained in the
header of my data file. The link to this header information requires the file
name of the data file.  When using the "Change Data File" function the file
name reference in the text box is not updated to the new data file name and the
link is broken.

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

[kdevelop] [Bug 362037] [OS X] frequent "beachballing"

[RJVB]

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

--- Comment #7 from RJVB  ---
Yes, that's exactly what it is - but you can also provoke a nice fireworks
display of context browser tooltips with it ;)

It might resemble more of a fix if it's possible to check after processing the
events if an action was taken which should abort the ongoing operation. Not
sure how you'd do that, but I'm not sure either if there's a truly better,
different solution. From what I see, the expensive operation is launched as
part of a tooltip display callback, meaning there isn't much else that callback
can do when you offload the expensive content creation operation to a
background thread. Unless you can create and show the tooltip from a background
job?


I'd be happy to test if you have something that should work.

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

[ktouch] [Bug 350336] KTouch lags and uses full (100%) CPU resources when typing fast.

[Andrzej Telszewski]

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

--- Comment #11 from Andrzej Telszewski  ---
I was hoping it'll compile on KDE4, but it won't.
See you once I move to KDE5 :-)

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

[kdevelop] [Bug 362037] [OS X] frequent "beachballing"

[Kevin Funk]

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

Kevin Funk  changed:

   What|Removed |Added

   Target Milestone|--- |5.0.3
 CC||kf...@kde.org

--- Comment #6 from Kevin Funk  ---
Agreed, we/I should look into this issue. I'm afraid your patch merely serves
as a work-around though.

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

[ktouch] [Bug 350336] KTouch lags and uses full (100%) CPU resources when typing fast.

[Sebastian Gottfried]

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

--- Comment #10 from Sebastian Gottfried  ---
No, not yet. It will be released as a part of KDE Application 16.12 on December
15. You can grab a copy of the source code from the repository. All the fixes
are in the master branch.

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

[krazy] [Bug 372256] Krazy thinks QMessageBox is a Qt4 class

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 347041] Tooltip interaction in multi-row Task Manager suffers from not being able to reach tooltip for lower rows of delegates

[René Fürst]

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

René Fürst  changed:

   What|Removed |Added

 CC||r...@fuerst.biz

--- Comment #3 from René Fürst  ---
I haven't tested it but I think the patches in bug 358930 should also fix this.

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

[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list

[René Fürst]

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

--- Comment #8 from René Fürst  ---
Created attachment 102152
  --> https://bugs.kde.org/attachment.cgi?id=102152=edit
Patch for plasma-desktop

The two patches fix the issue but I had to touch plasma-framework. If you agree
with all the changes then I'd be happy to find it merged. Otherwise you can at
least use it as base for fixing the issue.

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

[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list

[René Fürst]

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

--- Comment #7 from René Fürst  ---
Created attachment 102151
  --> https://bugs.kde.org/attachment.cgi?id=102151=edit
Patch for plasma-framework

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

[kwin] [Bug 372264] New: Full desktop zoom shows unzoomed translucent artifacts for translucent elements

[Thomas Mitterfellner]

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

Bug ID: 372264
   Summary: Full desktop zoom shows unzoomed translucent artifacts
for translucent elements
   Product: kwin
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

Created attachment 102150
  --> https://bugs.kde.org/attachment.cgi?id=102150=edit
Screenshot showing the artifact

The full desktop zoom (Zoom Factor: 2.0, Mouse Pointer: scale, Mouse Tracking:
proportional) shows semi-transparent artifacts seemingly caused by not scaling
and panning graphical the translucency part of elements like the task panel,
tool tips, or popups (non-classical windows, like the calender or the volume
info that pops up when I hit the volume keys),.
Thus, e.g. with a task panel at the bottom, upon zooming, one gets a
semi-transparent stripe spanning the bottom of the screen having the height of
the panel. The height of that translucent stripe stays the same with increasing
magnification, i.e. does not scale proportionally.
When I hover over some items in the systray, I get translucent rectangles the
size the pop-up would have been had I not zoomed. These don't move, i.e. stay
at the position of the unzoomed element even when panning.

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

[plasmashell] [Bug 372237] Superkey + L Causes Crash

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #1 from David Edmundson  ---
Thanks, should be fixed in 5.8.3

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

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

[plasmashell] [Bug 371201] plasma crashed

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 CC||xunilh...@8chan.co

--- Comment #2 from David Edmundson  ---
*** Bug 372237 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 345563] Assert in QGLXContext::init when OpenGL drivers are not installed

[David Edmundson]

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

--- Comment #102 from David Edmundson  ---
*** Bug 372229 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 372229] nvidia

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

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

--- Comment #6 from David Edmundson  ---
As Sasha correctly identified this is a driver setup problem. There's nothing
we can do about it.

I'm afraid we can't do distro specific support here. Please contact Kubuntu

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

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

[plasmashell] [Bug 372229] nvidia

[krirz79]

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

--- Comment #5 from krir...@gmail.com  ---
Nvidia-304.132 remove and reinstall nvidia 304.131 áll good. Thanks tips.

2016. nov. 9. 12:42 ezt írta ("Krisztián Veress" ):

> How tó install nvidia 304.131 package?
>
> 2016. nov. 9. 12:35 ezt írta ("Sasha Unspecified" <
> bugzilla_nore...@kde.org>):
>
>> https://bugs.kde.org/show_bug.cgi?id=372229
>>
>> --- Comment #3 from Sasha Unspecified  ---
>> I discovered that in my case the crash is caused by upgrade:
>> - from: nvidia-304 package of version 304.131-0ubuntu3
>> - to: nvidia-304 package of version 304.132-0ubuntu0.16.04.2
>> (within KUbuntu Xenial 16.04.1).
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>
>

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

[valgrind] [Bug 371916] execution tree xtree concept

[Philippe Waroquiers]

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

--- Comment #16 from Philippe Waroquiers  ---
(In reply to Josef Weidendorfer from comment #15)
> Hi Philippe, nice patch!
> 
> I think it is good to move functionalty from tools to the core, if it
> can make other tools better or easier to write. Attaching data to call
> trees built from stack traces should fit here.
> However, I did not check the large rewrite of massif.
> 
> General comments (I may be missing something here):
>  
> * is this bound to memory allocation, or is memory allocation just
>   an example use case of the API? It would be nice if tools could
>   attach arbitrary data to xtrees. Perhaps separate the memory allocation
>   stuff into different files (e.g. xtree_memalloc.h).
The API is done so that arbitrary data can be attached.
Of course, to be output as a callgrind or massif file, the data
must be translatable in (positive) integers values.

For what concerns separating the memory allocation stuff in another file:
that is a good suggestion, I will take a look at this. I think this
should be no problem.

> 
> * behavior of some functions in the XTree API depend on command line
>   options. Wouldn't it be better for a tool using this API to be in
>   full control here, ie. the tool parses command line
>   options and pass them as flags?
Basically, that is what the patch does:
command line options are parsed (specifically --xtree-memory=none|allocs|full)
and then the tool calls the memory support functions according to
the command line option (e.g. calling VG_(XTMemory_Full_alloc)).
The tool is in full control, e.g. it might implement 
   --xtree-memory=allocs
completely differently, if needed.

>  About the changes in the malloc
>   wrappers, I think it would be better if the tool can register handlers,
>   and these handlers then call e.g. VG_(XTMemory_Full_alloc).
I guess this could be done, but I think this would be less practical
than the current approach:  the malloc replacement is today
calling a tool replacement function.
So, these replacement functions are doing the job of e.g. recording
the allocated blocks in a tool specific way. In this replacement function,
the tool can (if desired) call e.g. VG_(XTMemory_Full_alloc)).
IMO, having another handler separated from the current handler function
would complexity things, as e.g. the tool would have to associate the
work/data done/prepared in the 'first handler' with the 'following' handler
calls related to xtree. So, in summary, there is now a handler that tells
the tool to e.g. execute a malloc, and this tool function can do the
needed work in one single invocation (e.g. re-using the execontext
done for tool purpose as data input for the xtree).


> 
> About the XTree API, why do you need these add/sub variants?
> Why not just have a function to get a pointer to the value to be updated?
> Any reduction operation may be useful, such as min/max.
Yes, any operation can be done in the add/sub : these functions
get a pointer to the value being updated.
It might be possible to use maybe a more generic name than add/sub
(maybe  Operate(...) ?), but then we will need more arguments for Operate
to indicate what this has to really do, and m_xtree.c itself need to do some
additions to e.g. produce some totals. So, one way or another, there is
an (somewhat flexible) notion of addition which is needed.
The current add/sub_data_fn are matching the current usage (xtree memory).
As a follow-up, I intend to work on a 'syscall xtree' which e.g. might
capture min/max (or maybe an histogram) of values. If needed, we might
revisit the interface of the *_data_fn (e.g. I suspect we might need
a destroy_data_fn if we want a more flexible/variable data set).

What I can do in any case is to add some comments
to indicate that the semantic of 'add' is quite flexible, and that e.g.
a 'max' or 'min' can be computed as part of the an 'add'.

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

[plasmashell] [Bug 371487] Plasma crashes when changing tray icon settings

[Lastique]

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

Lastique  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #6 from Lastique  ---
After a recent system update the problem has disappeared. I can no longer
reproduce the crash, at least it didn't happen in a dozen attempts while it was
happening 100% of times previously. I guess, something fixed.

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

[plasmashell] [Bug 364541] Icons in system tray popup are too small

[Thomas Mitterfellner]

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

--- Comment #6 from Thomas Mitterfellner  ---
I found here:
https://forum.kde.org/viewtopic.php?f=289=131736=c2949ae23a5898dc5b401abd4977014a=30#p365350
that this can actually be configured now (not obvious, but anyway).
In

~/.config/plasma-org.kde.plasma.desktop-appletsrc

I added a line

itenSize=2 

under the section

[Containments][19][General]

(It was not present in my case). The number in the [] might be different in
your case.

>From my point of view, this could be closed or resolved as a duplicate of
https://bugs.kde.org/show_bug.cgi?id=364431.

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

[kwin] [Bug 366651] Kwin Compositor Stops Updating Windows

[Mike C . Fletcher]

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

--- Comment #4 from Mike C. Fletcher  ---
(In reply to Martin Gräßlin from comment #3)
> waiting for debug output

https://paste.kde.org/p3jrxca0u has the output from a different machine showing
the same behaviour. When the information was captured the Eric IDE was "stuck"
such that I could edit/change/scroll etc the source window, but nothing else
would update. As noted, hitting Alt+Shift+F12 a couple times does eliminate the
condition.

Frequency seems to have dropped off significantly at this point, I see the
effect once every few weeks now, instead of many times/day. Likely that is due
to an OS update on Kubuntu.

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

[plasmashell] [Bug 345563] Assert in QGLXContext::init when OpenGL drivers are not installed

[Duun]

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

Duun  changed:

   What|Removed |Added

 CC|kde-b...@ondrejovci.de  |

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

[ktouch] [Bug 350336] KTouch lags and uses full (100%) CPU resources when typing fast.

[Andrzej Telszewski]

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

Andrzej Telszewski  changed:

   What|Removed |Added

 CC||atelszew...@gmail.com

--- Comment #9 from Andrzej Telszewski  ---
Is the source tarball of the new version available somewhere?

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

[digikam] [Bug 371543] BQM TimeAdjust tool language is wrong

[bugzilla_noreply]

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

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

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
   Version Fixed In||5.4.0

--- Comment #8 from caulier.gil...@gmail.com ---
The settings about i18n is complex in KDE. So i have no idea where to search
about this problem.

At least the problem is not located in digiKam as well...

Gilles Caulier

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

[digikam] [Bug 372159] Add option to run only the selected queue in BQM

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
  Component|BatchQueueManager   |BatchQueueManager-Workflow

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

[konsole] [Bug 369632] %u doesnt show current user anymore

[bugzilla_noreply]

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

--- Comment #2 from farmb...@googlemail.com ---
This bug can be closed. It works again.
I am using Plasma 5.8.3 and konsole 16.08.02 now.
Not sure exactly when it was fixed.

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

[krusader] [Bug 372259] The tarball is missing the manpage generation rules

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

   Assignee|m...@fork.pl  |alex.bikado...@kdemail.net
 CC||alex.bikado...@kdemail.net
 Ever confirmed|0   |1
 Status|UNCONFIRMED |ASSIGNED

--- Comment #1 from Alex Bikadorov  ---

Thanks for reporting.

create_tarballs_kf5 is preferred over releaseme/tarme, good to know that.

The patch is not needed but ill this keep it open until the next release.

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

[digikam] [Bug 307332] GROUP : problem about grouped items at copy operation

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.4.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/digi
   ||kam/8ae20d946cfd5bec8d0f419
   ||32d8d9b7858e32512
 Resolution|--- |FIXED

--- Comment #8 from Maik Qualmann  ---
Git commit 8ae20d946cfd5bec8d0f41932d8d9b7858e32512 by Maik Qualmann.
Committed on 09/11/2016 at 18:39.
Pushed by mqualmann into branch 'master'.

apply patch #101347 to remove grouping for copied or identical images
Related: bug 368762
FIXED-IN: 5.4.0

M  +3-1NEWS
M  +3-0libs/database/item/imagescanner.cpp

http://commits.kde.org/digikam/8ae20d946cfd5bec8d0f41932d8d9b7858e32512

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

[digikam] [Bug 368762] Only Jpg files are visible if importing them into a Subfolder of a Grouped folder [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.4.0
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/digi
   ||kam/8ae20d946cfd5bec8d0f419
   ||32d8d9b7858e32512

--- Comment #3 from Maik Qualmann  ---
Git commit 8ae20d946cfd5bec8d0f41932d8d9b7858e32512 by Maik Qualmann.
Committed on 09/11/2016 at 18:39.
Pushed by mqualmann into branch 'master'.

apply patch #101347 to remove grouping for copied or identical images
Related: bug 307332
FIXED-IN: 5.4.0

M  +3-1NEWS
M  +3-0libs/database/item/imagescanner.cpp

http://commits.kde.org/digikam/8ae20d946cfd5bec8d0f41932d8d9b7858e32512

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

[digikam] [Bug 368762] Only Jpg files are visible if importing them into a Subfolder of a Grouped folder [patch]

[Maik Qualmann]

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

--- Comment #2 from Maik Qualmann  ---
I see this patch at the moment as best solution. Also for the Bug 307332.

Maik

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

[plasmashell] [Bug 364541] Icons in system tray popup are too small

[Thomas Mitterfellner]

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

Thomas Mitterfellner  changed:

   What|Removed |Added

 CC||tho...@mitterfellner.at

--- Comment #5 from Thomas Mitterfellner  ---
Created attachment 102148
  --> https://bugs.kde.org/attachment.cgi?id=102148=edit
Systray screenshot

Indeed, it is very hard to identify the tiny icons for me as I am visually
impaired (in KDE 4, the readability was much better). From an accessibility
point of view, it would be highly desirable if there was an option to increase
their size, or rather decrease the whitespace, i.e. padding/margin/border size.

Is there a possibility to do this manually, i.e. by changing some configuration
file?

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Thomas Schmitt]

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

--- Comment #28 from Thomas Schmitt  ---
Hi,

afaik (hearsay from discussions about video UDF):
On Linux udftools have been superseded by UDF write support in the kernel.
Both are not suitable for DVD video because they cannot guarantee the
directory structure which is demanded.

The free DVD authoring tools seem to rely on mkisofs for the job.
On Ubuntu i see only dvdauthor and its frontends.
http://dvdauthor.sourceforge.net/ says
  "Things DVDAuthor does not do:
   Make a disc image or burn the disc: this is left to tools like mkisofs
   and dvd+rw-tools."

Have a nice day :)

Thomas

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

[konsole] [Bug 371068] yakuke / konsole with breeze color schema htop has some part unreadable

[Vasyl Demin]

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

Vasyl Demin  changed:

   What|Removed |Added

 CC||vasyl.de...@gmail.com

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

[digikam] [Bug 372230] Searches tool : "Current Searches" virtual album appears more than one

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com
Summary|Context menu not complete   |Searches tool : "Current
   |on right click on searches  |Searches" virtual album
   ||appears more than one

--- Comment #1 from caulier.gil...@gmail.com ---
The description of this file is wrong.

"Current Searches" virtual album cannot be deleted. Contextual menu is right
for this album. Others searches virtual album renamed can be deleted through
contextual menu.

But "Current Searches" appears more than one time on the list-view. This is
reproducible under non Linux system.

Gilles Caulier

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

[krazy] [Bug 372256] Krazy thinks QMessageBox is a Qt4 class

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

Summary|Krazy warns about   |Krazy thinks QMessageBox is
   |QMessageBox |a Qt4 class

--- Comment #3 from Elvis Angelaccio  ---
Title changed to better describe the report.

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

[kdeplasma-addons] [Bug 372218] Task switcher "Compact" ignores font anti-aliasing settings

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |k...@privat.broulik.de
 CC||k...@privat.broulik.de
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #5 from Kai Uwe Broulik  ---
Just looked at the source code - it is just a plain Text item, not
PlasmaComponents Label - so it doesn't use native rendering. I'll have a look.

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

[krazy] [Bug 372256] Krazy warns about QMessageBox

[Elvis Angelaccio]

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

--- Comment #2 from Elvis Angelaccio  ---
(In reply to Allen Winter from comment #1)
> is this a matter of the explanation string being wrong or that we are ok
> using QMessageBox in some cases instead of KMessageBox?
> 
> last I knew, we should be using KMessageBox over QMessageBox in KDE
> applications.

Right, this is more about the warning message (since it's not a Qt4 class).
Now that I think about it, if we still have KMessagebox there must be a reason
and we should probably use it. So it makes sense that krazy looks for this.

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

[krazy] [Bug 372256] Krazy warns about QMessageBox

[Allen Winter]

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

--- Comment #1 from Allen Winter  ---
is this a matter of the explanation string being wrong or that we are ok using
QMessageBox in some cases instead of KMessageBox?

last I knew, we should be using KMessageBox over QMessageBox in KDE
applications.

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

[krazy] [Bug 372257] Krazy should not look for spelling errors in translated json files

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

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

--- Comment #1 from Allen Winter  ---
should be fixed.
we'll need to wait a day or so for the EBN to pick and run the new code.

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

[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Dainius Masiliūnas]

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

--- Comment #27 from Dainius Masiliūnas  ---
For UDF, there's also udftools (mkudffs). It goes only up to 2.01, though.

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

[kmymoney4] [Bug 372263] New: KMyMoney crashes on opening

[Rob V]

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

Bug ID: 372263
   Summary: KMyMoney crashes on opening
   Product: kmymoney4
   Version: 4.7.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: rvalk...@gmail.com
  Target Milestone: ---

Application: kmymoney (4.7.2)
KDE Platform Version: 4.14.25
Qt Version: 4.8.7
Operating System: Linux 4.8.6-201.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

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

- What happened: The splash screen briefly appeared, followed by the crash
reporter. The main KMyMoney window never appeared.

The crash can be reproduced every time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
84  T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x000186d6 in  ()
#7  0x7f1990149688 in qt_plugin_instance() () at
/home/rob/Downloads/kmymoney-4.8.0/kmymoney/plugins/onlinetasks/national/nationalonlinetasksloader.cpp:36
#8  0x7f19aeac80df in KLibrary::factory(char const*) (lib=0x56281aff43d0)
at /usr/src/debug/kdelibs-4.14.25/kdecore/util/klibrary.cpp:149
#9  0x7f19aeac80df in KLibrary::factory(char const*) (this=0x56281aff43d0,
factoryname=0x56281a5db778 "konlinetasks_national") at
/usr/src/debug/kdelibs-4.14.25/kdecore/util/klibrary.cpp:169
#10 0x7f19aeace677 in KPluginLoader::factory()
(this=this@entry=0x7ffd54519e80) at
/usr/src/debug/kdelibs-4.14.25/kdecore/util/kpluginloader.cpp:197
#11 0x7f19b32bce5e in
KMyMoneyPlugin::PluginLoader::loadPlugin(KPluginInfo*) (error=, args=..., parent=0x56281a5ff490, parentWidget=0x0,
this=0x56281af863c0) at /usr/include/kde4/kservice.h:571
#12 0x7f19b32bce5e in
KMyMoneyPlugin::PluginLoader::loadPlugin(KPluginInfo*) (error=, args=..., parent=0x56281a5ff490, this=) at
/usr/include/kde4/kservice.h:550
#13 0x7f19b32bce5e in
KMyMoneyPlugin::PluginLoader::loadPlugin(KPluginInfo*)
(this=this@entry=0x56281af824d0, info=0x56281af83cf0) at
/usr/src/debug/kmymoney-4.7.2/kmymoney/plugins/pluginloader.cpp:98
#14 0x7f19b32bd6e8 in KMyMoneyPlugin::PluginLoader::loadPlugins()
(this=0x56281af824d0) at
/usr/src/debug/kmymoney-4.7.2/kmymoney/plugins/pluginloader.cpp:86
#15 0x562817f9e429 in KMyMoneyApp::loadPlugins()
(this=this@entry=0x56281a5ff490) at
/usr/src/debug/kmymoney-4.7.2/kmymoney/kmymoney.cpp:7111
#16 0x562817fe4b4f in KMyMoneyApp::KMyMoneyApp(QWidget*)
(this=0x56281a5ff490, parent=, __in_chrg=,
__vtt_parm=) at
/usr/src/debug/kmymoney-4.7.2/kmymoney/kmymoney.cpp:398
#17 0x562817f947d0 in main(int, char**) (argc=,
argv=) at /usr/src/debug/kmymoney-4.7.2/kmymoney/main.cpp:157

Reported using DrKonqi

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

[KScreen] [Bug 372228] libkscreen-qt5: qt_message_fatal(): kscreen_backend_launcher

[Rex Dieter]

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

--- Comment #3 from Rex Dieter  ---
#3  ... "QXcbConnection: Could not connect to display ..."

is the failure here (I think), hard to say *why* that is happening though.

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

[systemsettings] [Bug 372262] New: Have to disable main sound output to be able to use bluetooth headset

[wingear]

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

Bug ID: 372262
   Summary: Have to disable main sound output to be able to use
bluetooth headset
   Product: systemsettings
   Version: 5.8.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_phonon
  Assignee: sit...@kde.org
  Reporter: gruz...@gmail.com
  Target Milestone: ---

I'm trying to set B703/HN-B701 bluettoth headset as primary sound output device
after connect. I moved it to first position in all sound categories. But, even
after I clicked to "apply", primary soundcard was still used as audio output.
Only after pressing "left" and "right" buttons produced sound in headset. After
I disabled "Internal audio analog stereo", I can hear sound from headset. After
turn off and reconnect ganiture, there was no any devices in "Device
preference" tab. If I relaunch system-settings, headset audio source was still
in second position. And I have to again turn off "internal audio analog stereo"
to be able hear something from garniture. 

Can I send you some logs to help fix this?

Hint: after installing & configuring Blueman from GNOME, issue was fixed, so, I
think, some specific pulseaudio configuration needed

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

[KScreen] [Bug 372228] libkscreen-qt5: qt_message_fatal(): kscreen_backend_launcher

[RJ]

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

--- Comment #2 from RJ  ---
I'm using Fedora 25 to make it better. These bugs appears when I logout from
LXqt and login to KDE Plasma.

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

[kalarm] [Bug 372223] Problem in QIconPrivate::~QIconPrivate

[RJ]

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

--- Comment #2 from RJ  ---
(In reply to Christoph Feck from comment #1)
> This issue could be caused by "libqtxdg". I have no idea what component is
> responsible for loading this library, neither Qt nor KDE sources reference
> it.

libqtxdg is library from lxqt desktop.

Anyway, if you start lxqt desktop and then start Kalarmm on it then close it
from tray icon you will get crash. That it. Is this a bug in lxqt or kalarm
itself, please let me know.

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

[digikam] [Bug 372027] Adjust grouping behavior [patch]

[Maik Qualmann]

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

--- Comment #11 from Maik Qualmann  ---
(In reply to Simon from comment #10)
> There are two bug reports (that I found) which are fixed by or related to
> this patch. As I don't know how the control mechanisms of bugs.kde.org work,
> I will just list them here:
> https://bugs.kde.org/show_bug.cgi?id=294579

Thanks Simon, yes this bug we can close.

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

This bug not yet, he has another cause in addition.
https://bugs.kde.org/show_bug.cgi?id=368762

Maik

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

[digikam] [Bug 294579] GROUP : grouped pictures are not processed together except the first one (Renaming, Tags, Metadata, Labels, etc.)

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.4.0
 CC||metzping...@gmail.com
  Latest Commit||http://commits.kde.org/digi
   ||kam/5f6aa8656cf333e8949b106
   ||60407e8c8a0c0cc4f
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Maik Qualmann  ---
Git commit 5f6aa8656cf333e8949b10660407e8c8a0c0cc4f by Maik Qualmann.
Committed on 08/11/2016 at 21:11.
Pushed by mqualmann into branch 'master'.

apply patch #102005 from Simon Frei to adjust grouping behavior
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +1-1app/items/digikamimageview.cpp
M  +29   -18   app/items/imagecategorizedview.cpp
M  +6-3app/items/imagecategorizedview.h
M  +0-27   app/items/imageviewutilities.cpp
M  +12   -3app/views/digikamview.cpp
M  +96   -49   app/views/tableview/tableview.cpp
M  +10   -4app/views/tableview/tableview.h
M  +0-24   app/views/tableview/tableview_model.cpp
M  +0-2app/views/tableview/tableview_model.h
M  +13   -0libs/database/item/imageinfolist.cpp
M  +2-1libs/database/item/imageinfolist.h
M  +1-0libs/models/imagefiltermodel.h
M  +0-1libs/tags/tagslineeditoverlay.cpp

http://commits.kde.org/digikam/5f6aa8656cf333e8949b10660407e8c8a0c0cc4f

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