[korganizer] [Bug 345498] monthly To-do given incorrect start and due dates

[Karsten de Freese]

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

Karsten de Freese  changed:

   What|Removed |Added

 CC||kars...@maxi-dsl.de

--- Comment #2 from Karsten de Freese  ---
I can confirm this issue with
KOrganizer 5.3
KDE Applications 16.08.2
OpenSUSE leap 42.2

also for other frequencies of recurrence.
When setting up a non-recurring to-do, everything seems to work as expected - I
can set start dates, due dates and reminders without the different settings
influencing each other.
However if the to-do is set to recurring, response to the settings is erratic.
An example:
- I set up a to-do, starting the next day (at a specific time), and due one day
later. A reminder is set at 15min before due time.
- the to-do is shown correctly in the to-do list view, and also more detailed
via the 'show' context menu entry
- when I add a weekly recurrence, start and due dates are mysteriously moved by
two days in the to-do list view, while via the 'show' context menu only the due
date is shifted, and only by one day..
In other cases I've also seen the reminder being changed in addition,
recurrence setting being greyed out, or also an error messages when trying to
save the modified task (something like 'only allocated resources are allowed to
make changes', I can't reproduce this right now). 

The behavior does seem independent of the calendar type I select - local
personal calendar vs. CalDAV

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

[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)

[Luiz Angelo De Luca]

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

--- Comment #10 from Luiz Angelo De Luca  ---
The patch was already in use. See:
https://github.com/lede-project/source/blob/lede-17.01/package/devel/valgrind/patches/200-musl_fix.patch

I managed to compile a SVN version
https://github.com/lede-project/source/compare/lede-project:lede-17.01...luizluca:cc/valgrind-svn?expand=1

But it changed nothing. At least, it would be easier to test SVN changes in the
future.

I also compiled valgrind with debug and used gdb. Inside gdb, I still see
SIGILL (Illegal instruction), but running the program outside gdb seems to miss
it. Maybe it is catched.

Program received signal SIGILL, Illegal instruction.
0x38065bf0 in vgPlain_machine_get_hwcaps () at m_machine.c:1719
1719   have_DSPr2 = False;
(gdb) cont
Continuando.

Program received signal SIGILL, Illegal instruction.
0x38065c34 in vgPlain_machine_get_hwcaps () at m_machine.c:1730
1730  have_DSP = False;
(gdb) cont
Continuando.
warning: GDB can't find the start of the function at 0x42ae1d6c.

GDB is unable to find the start of the function at 0x42ae1d6c
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0x42ae1d6c for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.

Program received signal SIGSEGV, Segmentation fault.
0x42ae1d6c in ?? ()

Here is where I get the SIGSEGV. Maybe stack got corrupted. Is there any tips
from here?

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

[marble] [Bug 377967] marble installs file into /usr/etc/xdg/ instead of /etc/xdg/

[Fat-Zer]

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

Alexander Golubev (Fat-Zer)  changed:

   What|Removed |Added

 CC||fatz...@gmail.com

--- Comment #1 from Alexander Golubev (Fat-Zer)  ---
The problem itself is triggered because KDEInstallDirs.cmake from
extra-cmake-modules[1] sets KDE_INSTALL_SYSCONFDIR to
${CMAKE_INSTALL_SYSCONFDIR} which is set by GNUInstallDirs.cmake[2] as "etc"
and interpreted as a relative path to CMAKE_INSTALL_PREFIX.

[1]
https://github.com/KDE/extra-cmake-modules/blob/master/kde-modules/KDEInstallDirs.cmake
[2] https://github.com/KDE/marble/blob/master/CMakeLists.txt#L14

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

[kwin] [Bug 377913] Windows are not centered correctly

[Nikos Chantziaras]

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

--- Comment #4 from Nikos Chantziaras  ---
With decisions like that, no wonder KDE is still a broken mess.

I wonder why the hell I even bother reporting issues. Bugs are by design these
days.

Never again.

Have a nice life.

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

[kde] [Bug 377947] Crash on changing theme

[Unreal Name]

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

--- Comment #2 from Unreal Name <2112...@jeffcoschools.us> ---
Also this should be assigned to plasma or kcmshell5.

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

[kde] [Bug 377947] Crash on changing theme

[Unreal Name]

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

Unreal Name <2112...@jeffcoschools.us> changed:

   What|Removed |Added

 CC||2112...@jeffcoschools.us

--- Comment #1 from Unreal Name <2112...@jeffcoschools.us> ---
I also have this problem. This is only with a look-and-feel theme though. I
think this is one of those segfaults-on-heavy-load that seem to be very common
for some reason.

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

[frameworks-kiconthemes] [Bug 365363] Changing icons from System Settings is broken

[Pulfer]

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

--- Comment #22 from Pulfer  ---
(In reply to Michael Pyne from comment #21)
> As far as fixing it, that's rather far outside of what I will be able to
> accomplish unless the cause is already fully identified/diagnosed,
> especially given that it's KDE4. :(

Thanx for your help anyway :-)

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

[kwallet-pam] [Bug 376573] kwallet-pam does not work with sddm

[bugzilla_noreply]

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

--- Comment #3 from un...@physics.ubc.ca ---
Nope no ssh passwords in kwallet. 
It simply never gets the password from pam to open kwallet (password always
empty)
There is something wrong either with the timing (kwallet asking pam for the
password befor pam has the password) or with the way kwallet is asking pam for
the password. 
This is really annoying as I have to enter my password every time I open Chrome
after a reboot. As such it is also insecure, as each time one enters a password
is a chance for a shouldersurfer to snaffle the password.

Does this really work for everyone else and I am the only one who has trouble?

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

[simon] [Bug 377968] New: Simon searches all opendesktop categories for icons

[Unreal Name]

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

Bug ID: 377968
   Summary: Simon searches all opendesktop categories for icons
   Product: simon
   Version: 0.4.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: simon
  Assignee: kde...@unormal.org
  Reporter: 2112...@jeffcoschools.us
  Target Milestone: ---

During Simon setup, if I click on the "Download" button when selecting a base
model, it shows me everything from GTK themes to KDE apps.
Using Simon from git.

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

[marble] [Bug 377967] New: marble installs file into /usr/etc/xdg/ instead of /etc/xdg/

[bugzilla_noreply]

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

Bug ID: 377967
   Summary: marble installs file into /usr/etc/xdg/ instead of
/etc/xdg/
   Product: marble
   Version: 2.1 (KDE Applications 16.12)
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: andreas.sturmlech...@gmail.com
  Target Milestone: ---

>>> /usr/etc/xdg/marble.knsrc

This happens in 16.12.x as well as git master from today.

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

[plasmashell] [Bug 377958] plasma5-session not updated to 5.9.3 when all the other components were

[Nate Graham]

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

--- Comment #7 from Nate Graham  ---
Thanks Christoph! I've filed
https://bugzilla.opensuse.org/show_bug.cgi?id=1030559

And I just want to mention how impressed I've been with the responsiveness of
the KDE team on Bugzilla tickets, yourself included. It's really refreshing.
Keep up the awesome work!

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

[valgrind] [Bug 377966] disInstr(arm64): unhandled instruction 0xD50B7425 (dc zva,)

[John Reiser]

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

John Reiser  changed:

   What|Removed |Added

Summary|disInstr(arm64): unhandled  |disInstr(arm64): unhandled
   |instruction 0xD50B7425  |instruction 0xD50B7425 (dc
   ||zva,)

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

[valgrind] [Bug 377966] New: disInstr(arm64): unhandled instruction 0xD50B7425

[John Reiser]

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

Bug ID: 377966
   Summary: disInstr(arm64): unhandled instruction 0xD50B7425
   Product: valgrind
   Version: 3.12.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: jrei...@bitwagon.com
  Target Milestone: ---

On aarch64 (64-bit ARM) memcheck complains "unhandled instruction 0xD50B7425"
which is "dc zva, x5".  This is a data cache control instruction; it [allocates
and] clears the cache line whose address corresponds to the contents of
register x5.  Optimized code uses "dc zva," when it will be writing the entire
cache line.  Therefore the hardware need not read the line from memory (which
otherwise would be required upon the first write to the line), which saves
time.

Other related instructions which are used soon afterwards: "dc cvau," [Clean
data cache line by Virtual Address to point of Unification] to force the cache
line to be written to memory; and "ic ivau," [Invalidate icache line by Virtual
Address to point of Unification] to force the icache to forget the old contents
of a newly-overwritten instruction stream.

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

[krita] [Bug 377952] Assistant Tool cursor follow does not draw

[bugzilla_noreply]

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

flibbertigibbet...@gmail.com changed:

   What|Removed |Added

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

--- Comment #7 from flibbertigibbet...@gmail.com ---
Tested on Nvidia GTX 1080 computer windows 10 desktop. 

Exactly the same as all the others. Not an Intel graphics bug.

It may not be the screen or canvas refresh, rather a cursor location refresh? I
don't know the code. Just trying to give some suggestions of where to look.

Assistant tool "preview" lines that follow the cursor (like vanishing point) do
not refresh or draw when cursor outline option is "no outline". All other
cursor outline options, the assistant tool preview lines show, and follows the
cursor properly.

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

[okular] [Bug 190203] Allow to create bookmarks from the "table of contents"

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/oku
   ||lar/a2aceadc13ea4917dff2c58
   ||f470dd6eb8bc2cf53

--- Comment #3 from Albert Astals Cid  ---
Git commit a2aceadc13ea4917dff2c58f470dd6eb8bc2cf53 by Albert Astals Cid, on
behalf of Gilbert Assaf.
Committed on 23/03/2017 at 00:22.
Pushed by aacid into branch 'Applications/17.04'.

Allow to create bookmarks from the TOC
REVIEWS: 12

M  +13   -2part.cpp
M  +2-0part.h
M  +12   -0ui/toc.cpp
M  +5-0ui/toc.h

https://commits.kde.org/okular/a2aceadc13ea4917dff2c58f470dd6eb8bc2cf53

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

[krita] [Bug 377965] New: Pen pressure does not work with Artisul tablet

[Riley]

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

Bug ID: 377965
   Summary: Pen pressure does not work with Artisul tablet
   Product: krita
   Version: 3.1.2
  Platform: unspecified
OS: Windows CE
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: rabash...@hotmail.com
  Target Milestone: ---

Krita does not seen to support Artisul tablets. My pen pressure does not work
in Krita. I've tried updating my drivers, reinstalling, etc.

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

[plasmashell] [Bug 377958] plasma5-session not updated to 5.9.3 when all the other components were

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #6 from Christoph Feck  ---
plasma5-session is an openSUSE package. Please report this issue directly to
the bug tracker of your distribution.

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

[plasmashell] [Bug 377958] plasma5-session not updated to 5.9.3 when all the other components were

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|plasma5.desktop file not|plasma5-session not updated
   |updated for 5.9.3 (still|to 5.9.3 when all the other
   |says 5.9.2) |components were

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

[plasmashell] [Bug 377958] plasma5.desktop file not updated for 5.9.3 (still says 5.9.2)

[Nate Graham]

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

--- Comment #5 from Nate Graham  ---
kinfocenter5-5.9.3-1.1

However it looks like that file comes from plasma5-session, and indeed, I still
have the old version of it:

$ zypper info plasma5-session | grep Version
Version: 5.9.2-1.1

Is this a KDE issue, or a SUSE packaging issue?

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

[plasmashell] [Bug 377958] plasma5.desktop file not updated for 5.9.3 (still says 5.9.2)

[Christoph Feck]

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

--- Comment #4 from Christoph Feck  ---
Which version of kinfocenter do you have installed?

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

[plasma-nm] [Bug 352326] Plasma nm applet keeps spinning even after wifi network is connected

[kolAflash]

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

--- Comment #73 from kolAflash  ---
(In reply to Guo Yunhe (郭云鹤) from comment #70)
> [...]
> I found this problem is caused by Weather widget on openSUSE 42.1. If you
> remove Weather widget, the problem might disappear.

Same for me.

Used to have the problem in openSUSE 42.2 / KDE-Plasma 5.8.2.

After removing the weather widget from desktop, logging out an in the problem
disappeared.

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

[amarok] [Bug 375731] Amarok Crash

[Christoph Feck]

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

--- Comment #5 from Christoph Feck  ---
John, unless you install debug symbols for amarok and qt4, it does not make
sense to report more crashes.

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

[amarok] [Bug 377710] Amarok crashed while changing details of a mp3.

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
The crash is caused by memory corruption within the Amarok process. Needs a
valgrind log if this is reproducible.

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

[okular] [Bug 377688] No output to print for PDF since update to 1.0.3

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #12 from Albert Astals Cid  ---
Your bug seems very much like the bug where the broken gs interpreter breaks
everything https://bugs.kde.org/show_bug.cgi?id=371887

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

[plasma-nm] [Bug 352326] Plasma nm applet keeps spinning even after wifi network is connected

[kolAflash]

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

kolAflash  changed:

   What|Removed |Added

 CC||kolafl...@kolahilft.de

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

[kdenlive] [Bug 377957] beim verschieben eines clips stürtzt kdenlive ständig ab

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Version|16.12.3 |16.12.1
   Severity|normal  |crash

--- Comment #2 from Christoph Feck  ---
Changing version, because of bug 376925 from same reporter.

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

[konqueror] [Bug 377082] libQt5WebKit5: konqueror browser crashes while using split screen

[Kurt Seebauer]

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

Kurt Seebauer  changed:

   What|Removed |Added

Summary|konqueror browser crashes   |libQt5WebKit5: konqueror
   |while using split screen|browser crashes while using
   ||split screen

--- Comment #1 from Kurt Seebauer  ---
This time with a better backtrace. 
Reproduce the crash by opening about 5 horizontally and vertically split
windows, browser the web and see the crash:

System:
Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.3-1-default x86_64
Distribution: "openSUSE Tumbleweed"


Thread 1 (Thread 0x7f3f625da940 (LWP 11437)):
[KCrash Handler]
#6  0x7f3f2dfd0422 in WebCore::Node::hasTagName(WebCore::QualifiedName
const&) const () at dom/Element.h:804
#7  0x7f3f2dfd0422 in WebCore::isHTMLScriptElement(WebCore::Node*) () at
html/HTMLScriptElement.h:72
#8  0x7f3f2dfd0422 in WebCore::toScriptElementIfPossible(WebCore::Element*)
() at dom/ScriptElement.cpp:423
#9  0x7f3f2dff442f in
WebCore::ScriptRunner::timerFired(WebCore::Timer*) () at
dom/ScriptRunner.cpp:121
#10 0x7f3f2d2328ba in WebCore::ThreadTimers::sharedTimerFiredInternal() ()
at platform/ThreadTimers.cpp:129
#11 0x7f3f5c9a5573 in QObject::event(QEvent*) (this=0x44d5350, e=) at kernel/qobject.cpp:1285
#12 0x7f3f5daf4eac in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x44d5350, e=0x7fffd3a90150) at
kernel/qapplication.cpp:3799
#13 0x7f3f5dafc661 in QApplication::notify(QObject*, QEvent*)
(this=0x7fffd3a904e0, receiver=0x44d5350, e=0x7fffd3a90150) at
kernel/qapplication.cpp:3556
#14 0x7f3f5c978b00 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x44d5350, event=event@entry=0x7fffd3a90150) at
kernel/qcoreapplication.cpp:988
#15 0x7f3f5c9cc10e in QCoreApplication::sendEvent(QObject*, QEvent*)
(event=0x7fffd3a90150, receiver=) at
../../src/corelib/kernel/qcoreapplication.h:231
#16 0x7f3f5c9cc10e in QTimerInfoList::activateTimers() (this=0x23d95b0) at
kernel/qtimerinfo_unix.cpp:644
#17 0x7f3f5c9cc631 in timerSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at kernel/qeventdispatcher_glib.cpp:182
#18 0x7f3f557bd697 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#19 0x7f3f557bd900 in  () at /usr/lib64/libglib-2.0.so.0
#20 0x7f3f557bd9ac in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#21 0x7f3f5c9cd16f in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x2403810, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x7f3f5c976aea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fffd3a903a0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#23 0x7f3f5c97f25c in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1261
#24 0x7f3f621f79e6 in kdemain(int, char**) (argc=,
argv=) at /usr/src/debug/konqueror-16.12.3/src/konqmain.cpp:233
#25 0x7f3f61db0541 in __libc_start_main (main=0x400690 , argc=1,
argv=0x7fffd3a906a8, init=, fini=,
rtld_fini=, stack_end=0x7fffd3a90698) at ../csu/libc-start.c:295
#26 0x004006ca in _start () at ../sysdeps/x86_64/start.S:120

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

[kdenlive] [Bug 376925] wenn ich mit mit dem curser von einem clip zum nächsten springe stürzt kdenlive immer ab

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

Version|16.12.2 |16.12.1

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

[kdenlive] [Bug 376925] wenn ich mit mit dem curser von einem clip zum nächsten springe stürzt kdenlive immer ab

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

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

[kdenlive] [Bug 377957] beim verschieben eines clips stürtzt kdenlive ständig ab

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Christoph Feck  ---
Please add a valid backtrace. For more information, please see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

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

[kdevelop] [Bug 377964] Plugin "Cppcheck Support" is enabled as default despite missing cppcheck in the system

[Piotr Mierzwinski]

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 CC||piotr.mierzwin...@gmail.com

--- Comment #1 from Piotr Mierzwinski  ---
Just updating.
Also options from group: "Analyze with" are active.

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

[kdevelop] [Bug 377963] One cannot change color schema for editor

[Piotr Mierzwinski]

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

Piotr Mierzwinski  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||piotr.mierzwin...@gmail.com

--- Comment #1 from Piotr Mierzwinski  ---
Please ignore this. All is fine.

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

[kate] [Bug 377962] kate crashes after closing a file with long lines / wayland [Backtrace with debug symbols attached]

[Kurt Seebauer]

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

--- Comment #1 from Kurt Seebauer  ---
ok, forget about the long lines and even about kate. Closed dolphin and the
same thing happenes:

Thread 1 (Thread 0x7fa696b31140 (LWP 7203)):
[KCrash Handler]
#6  0x7fa680927059 in wl_map_insert_at (map=,
flags=flags@entry=0, i=, data=) at
src/wayland-util.c:249
#7  0x7fa68092322e in proxy_destroy (proxy=0x1bff7f0) at
src/wayland-client.c:411
#8  wl_proxy_destroy (proxy=0x1bff7f0) at src/wayland-client.c:442
#9  0x7fa67fc67415 in wl_registry_destroy (wl_registry=) at
/usr/include/wayland/wayland-client-protocol.h:1065
#10 KWayland::Client::WaylandPointer::release
(this=0x1e82000, this=0x1e82000) at
/usr/src/debug/kwayland-5.31.0/src/client/wayland_pointer_p.h:53
#11 KWayland::Client::Registry::release (this=this@entry=0x1e5d750) at
/usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:358
#12 0x7fa67fc6743c in KWayland::Client::Registry::~Registry
(this=0x1e5d750, __in_chrg=) at
/usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:353
#13 0x7fa67fc674d9 in KWayland::Client::Registry::~Registry
(this=0x1e5d750, __in_chrg=) at
/usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:354
#14 0x7fa690659f31 in QObjectPrivate::deleteChildren
(this=this@entry=0x230d5b0) at kernel/qobject.cpp:1970
#15 0x7fa6906632bf in QObject::~QObject (this=,
__in_chrg=) at kernel/qobject.cpp:1041
#16 0x7fa66836a7e3 in WaylandIntegration::~WaylandIntegration
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:51
#17 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:37
#18 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:43
#19 0x7fa69634cc50 in __run_exit_handlers (status=0, listp=0x7fa6966b45b8
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at exit.c:83
#20 0x7fa69634ccaa in __GI_exit (status=) at exit.c:105
#21 0x7fa696335548 in __libc_start_main (main=0x400640, argc=3,
argv=0x7ffc16540cd8, init=, fini=,
rtld_fini=, stack_end=0x7ffc16540cc8) at ../csu/libc-start.c:329
#22 0x0040067a in _start ()

something's seriously broken.

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

[kdevelop] [Bug 377964] New: Plugin "Cppcheck Support" is enabled as default despite missing cppcheck in the system

[Piotr Mierzwinski]

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

Bug ID: 377964
   Summary: Plugin "Cppcheck Support" is enabled as default
despite missing cppcheck in the system
   Product: kdevelop
   Version: 5.1.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Analyzer: Cppcheck
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
  Target Milestone: ---

As in subject.
After first start new version, so 5.1 I noticed that Plugin cppcheck is
enabled. I was a bit surprised, because I don't have installed cppcheck binary
in the system.

$ which cppcheck
which: no cppcheck in (..

Anyway. I'm not sure is this bug or intended (default) setting.

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

[kdenlive] [Bug 371353] Timeline corruption when moving more then one clip and undo afterwards

[farid]

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

--- Comment #3 from farid  ---
This timeline corruption bugs are the reason we are doing the refactoring.
After it is finished besides this problems will be gone and the great new
features will be shining. My workaround for now is to not do this things that
trigger the corruption.

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

[kdevelop] [Bug 377963] New: One cannot change color schema for editor

[Piotr Mierzwinski]

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

Bug ID: 377963
   Summary: One cannot change color schema for editor
   Product: kdevelop
   Version: 5.1.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: all editors
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: piotr.mierzwin...@gmail.com
  Target Milestone: ---

Using "Settings -> Color Theme" I changed theme to "Dark Breeze". After that I
wanted to change also color scheme for editor. Unfortunately  I wasn't able to
do it.

In "KDevelop Settings -> Editor -> Fonts and colors" I selected schema "Breeze
Dark". After that "Apply" button didn't change its activity, so still was not
active. Pressing "OK" didn't bring effect, so still is "Normal".

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

[kate] [Bug 377962] New: kate crashes after closing a file with long lines / wayland [Backtrace with debug symbols attached]

[Kurt Seebauer]

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

Bug ID: 377962
   Summary: kate crashes after closing a file with long lines /
wayland [Backtrace with debug symbols attached]
   Product: kate
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: kurt_seeba...@yahoo.de
  Target Milestone: ---

Application: kate (16.12.3)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.3-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
test driving kde wayland again, as I do once in a while. This time kate crashed
and the backtrace seems to indicate it's wayland-related. I opened a file with
long lines (22275 chars max), clicked "Temporarily raise limit and reload
file", scrolled around. 
After clicking close (x-symbol) kate crashes. 

Crash is reproducable.

Any more info I can provide?

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

Thread 7 (Thread 0x7f4d29b10700 (LWP 7366)):
#0  0x7f4d4f2429a6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x1267068) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x1267018, cond=0x1267040)
at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x1267040, mutex=0x1267018) at
pthread_cond_wait.c:655
#3  0x7f4d331a780b in ?? () from /usr/lib64/dri/radeonsi_dri.so
#4  0x7f4d331a7537 in ?? () from /usr/lib64/dri/radeonsi_dri.so
#5  0x7f4d4f23c537 in start_thread (arg=0x7f4d29b10700) at
pthread_create.c:456
#6  0x7f4d52bdc04f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 6 (Thread 0x7f4d2a311700 (LWP 7365)):
#0  0x7f4d4f2429a6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x1267068) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x1267018, cond=0x1267040)
at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x1267040, mutex=0x1267018) at
pthread_cond_wait.c:655
#3  0x7f4d331a780b in ?? () from /usr/lib64/dri/radeonsi_dri.so
#4  0x7f4d331a7537 in ?? () from /usr/lib64/dri/radeonsi_dri.so
#5  0x7f4d4f23c537 in start_thread (arg=0x7f4d2a311700) at
pthread_create.c:456
#6  0x7f4d52bdc04f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 5 (Thread 0x7f4d2ab12700 (LWP 7364)):
#0  0x7f4d4f2429a6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x1267068) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x1267018, cond=0x1267040)
at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x1267040, mutex=0x1267018) at
pthread_cond_wait.c:655
#3  0x7f4d331a780b in ?? () from /usr/lib64/dri/radeonsi_dri.so
#4  0x7f4d331a7537 in ?? () from /usr/lib64/dri/radeonsi_dri.so
#5  0x7f4d4f23c537 in start_thread (arg=0x7f4d2ab12700) at
pthread_create.c:456
#6  0x7f4d52bdc04f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 4 (Thread 0x7f4d2b313700 (LWP 7363)):
#0  0x7f4d4f2429a6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x1267068) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x1267018, cond=0x1267040)
at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x1267040, mutex=0x1267018) at
pthread_cond_wait.c:655
#3  0x7f4d331a780b in ?? () from /usr/lib64/dri/radeonsi_dri.so
#4  0x7f4d331a7537 in ?? () from /usr/lib64/dri/radeonsi_dri.so
#5  0x7f4d4f23c537 in start_thread (arg=0x7f4d2b313700) at
pthread_create.c:456
#6  0x7f4d52bdc04f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 3 (Thread 0x7f4d2bd4e700 (LWP 7362)):
#0  0x7f4d4f2429a6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x1525ac0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x1525a70, cond=0x1525a98)
at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x1525a98, mutex=0x1525a70) at
pthread_cond_wait.c:655
#3  0x7f4d331a780b in ?? () from /usr/lib64/dri/radeonsi_dri.so
#4  0x7f4d331a7537 in ?? () from /usr/lib64/dri/radeonsi_dri.so
#5  0x7f4d4f23c537 in start_thread (arg=0x7f4d2bd4e700) at
pthread_create.c:456
#6  0x7f4d52bdc04f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 2 (Thread 0x7f4d464c2700 (LWP 7361)):
#0  0x7f4d52bd27bd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f4d4d2ea896 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f4d4d2ea9ac in 

[krita] [Bug 375878] Eraser will not switch back to brush after turning Wacom pen back around

[Boudewijn Rempt]

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

--- Comment #31 from Boudewijn Rempt  ---
It's not in an official release yet. Either use an older version, or use the
latest dev build from files.kde.org/krita/3/windows/devbuilds -- if you're on
Windows. I haven't made OSX or Linux devbuilds yet.

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

[frameworks-plasma] [Bug 377961] hint-tile-center does not work in Plasma desktopthemes

[Ian Smith]

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

Ian Smith  changed:

   What|Removed |Added

 CC||iansa...@gmail.com

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

[frameworks-plasma] [Bug 377961] New: hint-tile-center does not work in Plasma desktopthemes

[Ian Smith]

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

Bug ID: 377961
   Summary: hint-tile-center does not work in Plasma desktopthemes
   Product: frameworks-plasma
   Version: 5.26.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: libplasma
  Assignee: notm...@gmail.com
  Reporter: iansa...@gmail.com
  Target Milestone: ---

The hint-tile-center option has stopped working, at least in the translucent
panel-background.svgz and the standard widget background.svgz. It may well not
work in other widget backgrounds, but these are the two I have tried.

It is worth noting that in the tutorial
https://techbase.kde.org/Development/Tutorials/Plasma5/ThemeDetails
hint-tile-center is still discussed.

Reproducible: Always

Steps to Reproduce:
1. Copy one of the standard themes to .local/share/plasma/desktoptheme/
2. Edit metadata.desktop: change the name of the theme so that it is
identifiable in System Settings.
3. Edit widgets/background.svgz:
a) locate the object with id="center"
b) use the fill and stroke tool to give the object a gradient (if "center"
is a group object, it will be necessary to make the gradient on one of the
group's members).
c) if there is not already an object called hint-tile-center, duplicate one
of the other hint objects, (e.g."hint-stretch-borders") and change the id to
hint-tile-center.
d) save the file.
4. Open System Settings>Workspace Theme>Desktop Theme
5. Select the theme that was renamed in step 2.
6. Click "Apply".

Actual Results:  
Widgets such as Folderviews, Network Monitor and Thermal Monitor will display
the background stretched across the entire widget.

Expected Results:  
The background should be tiled across the widgets.

Using a gradient is a simple example to demonstrate the bug. I have also
obtained similar results using a freehand path within the center group.

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

[plasmashell] [Bug 377958] plasma5.desktop file not updated for 5.9.3 (still says 5.9.2)

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Plasma version reported |plasma5.desktop file not
   |incorrectly |updated for 5.9.3 (still
   ||says 5.9.2)
   Target Milestone|--- |1.0
  Component|Info|general
Product|kinfocenter |plasmashell
 CC||bhus...@gmail.com,
   ||plasma-b...@kde.org

--- Comment #3 from Nate Graham  ---
Okay, so plasmaVersion() looks at /usr/share/xsessions/plasma.desktop, and sure
enough:

grep Version /usr/share/xsessions/plasma5.desktop
X-KDE-PluginInfo-Version=5.9.2

So it's not KInfocenter's fault, but rather whichever package/component is
responsible for updating the plasma5.desktop file.

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

[kdevplatform] [Bug 377960] Segfault on exit in DUChainPrivate::doMoreCleanup

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

Version|git master  |5.1.0

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

[kdevplatform] [Bug 377960] New: Segfault on exit in DUChainPrivate::doMoreCleanup

[Francis Herne]

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

Bug ID: 377960
   Summary: Segfault on exit in DUChainPrivate::doMoreCleanup
   Product: kdevplatform
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: language
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: m...@flherne.uk
  Target Milestone: ---

(there's no 5.1.0 or 5.1-git bug category)

KDevelop/platform 5.1-git, compiled with Clang, crashed on exit with the
following backtrace.

Core was generated by `kdevelop -s KDev'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fb98c02012f in KDevelop::DUChainPrivate::doMoreCleanup(int,
KDevelop::DUChainPrivate::LockFlag) () from
/usr/local/lib64/libKDevPlatformLanguage.so.10
[Current thread is 1 (Thread 0x7fb963c01700 (LWP 31875))]
(gdb) bt
#0  0x7fb98c02012f in KDevelop::DUChainPrivate::doMoreCleanup(int,
KDevelop::DUChainPrivate::LockFlag) () at
/usr/local/lib64/libKDevPlatformLanguage.so.10
#1  0x7fb98c03f4f7 in
KDevelop::DUChainPrivate::CleanupThread::~CleanupThread() () at
/usr/local/lib64/libKDevPlatformLanguage.so.10
#2  0x7fb98ebfc6d8 in  () at /usr/lib/libQt5Core.so.5
#3  0x7fb9868122e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fb98dfe554f in clone () at /usr/lib/libc.so.6


===

(gdb) thread apply all bt

Thread 18 (Thread 0x7fb972788700 (LWP 31869)):
#0  0x7fb98dfdb67d in poll () at /usr/lib/libc.so.6
#1  0x7fb9827db7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fb9827db8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fb98ee2c04f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fb98edd589a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fb98ebf7a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fb991ba2125 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7fb98ebfc6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fb9868122e7 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fb98dfe554f in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7fb995b400c0 (LWP 31867)):
#0  0x7fb989134060 in WTF::fastMalloc(unsigned long) () at
/usr/lib/libQt5WebKit.so.5
#1  0x7fb988c23b7f in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7fb988c3b335 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7fb988c62278 in  () at /usr/lib/libQt5WebKit.so.5
#4  0x7fb988c625ab in  () at /usr/lib/libQt5WebKit.so.5
#5  0x7fb988c6262b in  () at /usr/lib/libQt5WebKit.so.5
#6  0x7fb988c73deb in  () at /usr/lib/libQt5WebKit.so.5
#7  0x7fb987c92c96 in  () at /usr/lib/libQt5WebKit.so.5
#8  0x7fb987c97261 in  () at /usr/lib/libQt5WebKit.so.5
#9  0x7fb987cb9e8b in  () at /usr/lib/libQt5WebKit.so.5
#10 0x7fb987cc293b in  () at /usr/lib/libQt5WebKit.so.5
#11 0x7fb987cc474c in  () at /usr/lib/libQt5WebKit.so.5
#12 0x7fb987c99a08 in  () at /usr/lib/libQt5WebKit.so.5
#13 0x7fb987c9a379 in  () at /usr/lib/libQt5WebKit.so.5
#14 0x7fb987c9a562 in  () at /usr/lib/libQt5WebKit.so.5
#15 0x7fb987c98168 in  () at /usr/lib/libQt5WebKit.so.5
#16 0x7fb987d0c40a in  () at /usr/lib/libQt5WebKit.so.5
#17 0x7fb987d020a6 in  () at /usr/lib/libQt5WebKit.so.5
#18 0x7fb987d03302 in  () at /usr/lib/libQt5WebKit.so.5
#19 0x7fb987d0404d in  () at /usr/lib/libQt5WebKit.so.5
#20 0x7fb987d11f31 in  () at /usr/lib/libQt5WebKit.so.5
#21 0x7fb987a3aaf2 in QWebFrameAdapter::init(QWebPageAdapter*) () at
/usr/lib/libQt5WebKit.so.5
#22 0x7fb989bf0e61 in QWebFrame::QWebFrame(QWebPage*) () at
/usr/lib/libQt5WebKitWidgets.so.5
#23 0x7fb989bf4ab9 in  () at /usr/lib/libQt5WebKitWidgets.so.5
#24 0x7fb989bf5a1d in QWebPage::mainFrame() const () at
/usr/lib/libQt5WebKitWidgets.so.5
#25 0x7fb989bf5a5d in  () at /usr/lib/libQt5WebKitWidgets.so.5
#26 0x7fb989bf6400 in QWebPage::setViewportSize(QSize const&) const () at
/usr/lib/libQt5WebKitWidgets.so.5
#27 0x7fb989bf64da in QWebPage::setView(QWidget*) () at
/usr/lib/libQt5WebKitWidgets.so.5
#28 0x7fb989bf665b in QWebPage::QWebPage(QObject*) () at
/usr/lib/libQt5WebKitWidgets.so.5
#29 0x7fb989bfca01 in QWebView::page() const () at
/usr/lib/libQt5WebKitWidgets.so.5
#30 0x7fb989bfcaf9 in QWebView::settings() const () at
/usr/lib/libQt5WebKitWidgets.so.5
#31 0x7fb98bd39459 in
KDevelop::StandardDocumentationView::StandardDocumentationView(KDevelop::DocumentationFindWidget*,
QWidget*) () at /usr/local/lib64/libKDevPlatformDocumentation.so.10
#32 0x7fb960177b10 in
PhpDocumentationWidget::PhpDocumentationWidget(KDevelop::DocumentationFindWidget*,
QUrl const&, PhpDocsPlugin*, QWidget*) ()
at /usr/local/lib64/plugins/kdevplatform/27/kdevphpdocs.so
#33 0x7fb96017938a in
PhpDocumentation::documentationWidget(KDevelop::DocumentationFindWidget*,
QWidget*) 

[valgrind] [Bug 377698] Missing memory check for futex() uaddr arg for FUTEX_WAKE and FUTEX_WAKE_BITSET, check only 4 args for FUTEX_WAKE_BITSET, and 2 args for FUTEX_TRYLOCK_PI

[Julian Seward]

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

--- Comment #7 from Julian Seward  ---
(In reply to Diane M from comment #6)
> I believe the if is necessary, because it is checking whether the function
> pointer is defined, [..]

Oh, you're right.  I missed that.

r+ then; can you attach a patch that builds and tests OK agains the trunk?

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

[kinfocenter] [Bug 377958] Plasma version reported incorrectly

[Nate Graham]

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

--- Comment #2 from Nate Graham  ---
$ plasmashell --version
plasmashell 5.9.3

So that reports the correct version, too

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

[kinfocenter] [Bug 377958] Plasma version reported incorrectly

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|Plasma and framework|Plasma version reported
   |versions reported   |incorrectly
   |incorrectly |

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

[plasma-mediacenter] [Bug 377959] New: Media Controller hotkeys not working in chrome

[qwad1000]

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

Bug ID: 377959
   Summary: Media Controller hotkeys not working in chrome
   Product: plasma-mediacenter
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: MediaController
  Assignee: ksi...@gmail.com
  Reporter: qwad1...@ukr.net
  Target Milestone: ---

Play-pause/next/previous keys are not registered in chrome while they are set
as keys for MediaController.

Steps to reproduce:
0) Be sure that Media Controller hotkeys are set (Global shortcuts > Media
Controller)
1) Go to chrome://extensions
2) Scroll down and open "Keyboard shortcuts".
3) Try to set any shortcut with same (Play/Next/Previous) keys.
Actual results:
Nothing happens. Shortcut is not set. Keypresses just not appears for chrome.
Expected results:
Shortcut is set and usable.

I'm using KDE Neon User edition now (5.9.3-5.9.4 while I'm writing this).

Additional information:
1) Expected results are achievable on Kubuntu 16.04.
2) Try first set Media Controller shortcut (e.g. Play) to 'None' in Global
Shortcuts. Then the shortcut would be easily registered in chrome. Moreover -
when you set shortcut back in Global Shortcuts chrome is still able to work
with it. But after system reboot the problem renews.
3) I've used Yandex.Music chrome extension and vk.com music library with those
hotkeys (in case you need this info).

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

[kinfocenter] [Bug 377958] Plasma and framework versions reported incorrectly

[Nate Graham]

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

--- Comment #1 from Nate Graham  ---
This is affecting at least one other person as well:
https://www.reddit.com/r/openSUSE/comments/60wxef/whens_kde_plasma_593_expected_to_arrive_on/dfa26gp/

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

[kinfocenter] [Bug 377958] Plasma and framework versions reported incorrectly

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kinfocenter] [Bug 377958] New: Plasma and framework versions reported incorrectly

[Nate Graham]

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

Bug ID: 377958
   Summary: Plasma and framework versions reported incorrectly
   Product: kinfocenter
   Version: 5.9.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Info
  Assignee: hubn...@gmail.com
  Reporter: pointedst...@zoho.com
  Target Milestone: ---

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

Using openSUSE Tumbleweed with kinfocenter5-5.9.3-1.1. Here are the packages I
have installed:

$ zypper info plasma5-desktop | grep Version
Version: 5.9.3-2.1

$ zypper info plasma-framework | grep Version
Version: 5.31.0-1.1


Yet KInfocenter shows:
KDE Plasma Version: 5.9.2
KDE Frameworks Version 5.3.10

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

[kdenlive] [Bug 377957] New: beim verschieben eines clips stürtzt kdenlive ständig ab

[Rico]

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

Bug ID: 377957
   Summary: beim verschieben eines clips stürtzt kdenlive ständig
ab
   Product: kdenlive
   Version: 16.12.3
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: texasrange...@web.de
  Target Milestone: ---

GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/kdenlive...Reading symbols from
/usr/lib/debug/.build-id/d0/dd276f361be57a4384e9e405647e2b5ecbe616.debug...done.
done.
Attaching to program: /usr/bin/kdenlive, process 4276
Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Vorgang nicht zulässig.
(gdb)

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

[krita] [Bug 377781] Krita Random Crash While Idle

[Leo]

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

--- Comment #5 from Leo  ---
(In reply to Boudewijn Rempt from comment #4)
> Sure, that's fine!

Yes, I can confirm a similar crash with the most current Krita appimage.

In all instances, I have file/s open that I have been working on. I will leave
the computer for a break, perhaps an hour or more and return to find that Krita
has crashed and no longer running.

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

[frameworks-kiconthemes] [Bug 365363] Changing icons from System Settings is broken

[Michael Pyne]

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

--- Comment #21 from Michael Pyne  ---
I'd recommend instead adding the env variable to your system startup scripts
using whatever method is appropriate (/etc/local.d or something like that?). 
You don't want to manually edit the distro startkde if you can avoid it.

As far as fixing it, that's rather far outside of what I will be able to
accomplish unless the cause is already fully identified/diagnosed, especially
given that it's KDE4. :(

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

[gwenview] [Bug 364805] Gwenview fails to open images with russian letters in path - Invalid url QUrl("") or file or path does not exist

[Wadlax]

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

--- Comment #13 from Wadlax  ---
Created attachment 104692
  --> https://bugs.kde.org/attachment.cgi?id=104692=edit
compiled gwenview

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

[gwenview] [Bug 364805] Gwenview fails to open images with russian letters in path - Invalid url QUrl("") or file or path does not exist

[Wadlax]

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

--- Comment #12 from Wadlax  ---
Christoph Feck, what qt version do you have?

I have found a pattern in this error.
Gwenview can be fixed, but i think that problem may be related to qt, as in bug
https://bugs.kde.org/show_bug.cgi?id=186038

.

Pattern in source code:
Some programms , that does not understand russian letters (in my system) call
"KLocalizedString::setApplicationDomain." prior to QApplication app(argc,
argv);"

Not working - for example - Gwenview, KTorrent

.

Programms, that have "QApplication app(argc, argv);" first and
"KLocalizedString::setApplicationDomain("");" later - show russian
chars for me.

Working - example - dolphin, okular

.

So, i have installed KDevelop, downloaded Gwenview git sources.

1st compile and run - same error - russian chars do not recognized.

2nd - moved line "QApplication app(argc, argv);" before line
"KLocalizedString::setApplicationDomain("gwenview");"
and programm work good.

(I dont know C++ very well, so i cannot debug deeper - to find common place of
problem)

.

Attaching screen.
Bottom right - two compiled gwenview - showing "russian" folder and "russian"
filenames - working as desired.

.

Hope this will help to find a main bug, common to all apps.

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

[krita] [Bug 377952] Assistant Tool cursor follow does not draw

[bugzilla_noreply]

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

--- Comment #6 from flibbertigibbet...@gmail.com ---
I don't believe that Krita has ever seen or "touched" the discrete nvidia card
on the Asus machine, either in windows or in ubuntu due to the integrated
graphics and the optimus capability. 

I don't believe Nvidia card actually ever worked in ubuntu, and I didn't notice
any change when I tried to force the gpu in windows nvidia driver for krita.

So I will try on the computer with the dedicated nvidia cards to verify when I
get home. The two desktops I have at home have windows 10 natively with nvidia
gtx cards, but I can dualboot to a usb for ubuntu.

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

[plasmashell] [Bug 377956] System tray's popups get lost if minimized (via global shortcut)

[JanKusanagi]

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

--- Comment #1 from JanKusanagi  ---
Just for completeness: I just checked, and once this bug is triggered, the
Battery and Brightness icon, the KDE Connect icon, and the Clipboard icon
suffer the same fate, if they're in the systray.

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

[krita] [Bug 377952] Assistant Tool cursor follow does not draw

[bugzilla_noreply]

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

--- Comment #5 from flibbertigibbet...@gmail.com ---
Also tried the same ubuntu linux install from the asus on the macbook by dual
booting.
It may be an intel graphics issue. Since there is a commonality between all the
devices. But I did try every OS.

I have a desktop machine at home I can try that is an Nvidia GTX 1080 dedicated
card... and an Intel NUC machine that has another integrated intel graphics
card.

I could boot up my old rig that has a dedicated Nvidia GTX 570ti to test too.

But those are at home, am at work at the moment.

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

[plasmashell] [Bug 377652] Some Kicker icons should be highlighted while hovering cursor over them (like in Kickoff)

[Eike Hein]

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

--- Comment #7 from Eike Hein  ---
This needs some further work in IconItem to allow us to do applet size hints
similar to Image does - I've got a patch coming up, and one to Kicker to port
it to IconItem.

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

[plasmashell] [Bug 377956] System tray's popups get lost if minimized (via global shortcut)

[JanKusanagi]

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

JanKusanagi  changed:

   What|Removed |Added

 CC||jan-b...@gmx.co.uk

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

[plasmashell] [Bug 377956] New: System tray's popups get lost if minimized (via global shortcut)

[JanKusanagi]

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

Bug ID: 377956
   Summary: System tray's popups get lost if minimized (via global
shortcut)
   Product: plasmashell
   Version: 5.8.6
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: jan-b...@gmx.co.uk
  Target Milestone: 1.0

OK, I'm going for weird bug of the year here =)

First, some background: I have global shortcuts set for maximizing and
minimizing windows, configured in System Settings > Workspace > Shortcuts >
Global Shortcuts. I have only one screen and only one panel, at the bottom.


Today the Device Notifier popup appeared after inserting a USB drive, at the
time I went to minimize a window with my global shortcut. Apparently the Device
Notifier stole the focus, because the "minimizing" happened to the DN popup,
not to the currently active window.

Fair enough... but now, clicking on the Device Notifier, or any other, let's
say, "plasma-native" icon in the systray that would show a popup (notifications
and volume controller, in my case), no longer appear. Clicking them now shows a
slight animation like focus is traveling from that icon to a point outside of
the screen, somewhere at the far right/down corner, and no popup. Clicking the
icon again reverses that "animation" and the "little light" comes back to the
icon from that limbo-place xD

For comparison, I can trigger the same thing to the "calendar popup" that
appears when clicking the Digital Clock plasmoid in the panel, but in this
case, the calendar appears correctly after clicking the clock again, only this
time, it appears with a "restore window from minimized state" animation, which
looks weird, but it _is_ restored. It seems to be only an issue with the popups
that come from the systray.

This happened to me in Plasma 5.8.6, but I've reproduced it on the first try on
a Plasma 5.9.3 machine.

I realize this is a bug that very few people will ever trigger, but still ;)

Thanks!

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

[krita] [Bug 377952] Assistant Tool cursor follow does not draw

[bugzilla_noreply]

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

--- Comment #4 from flibbertigibbet...@gmail.com ---
On linux only used the app image build 3.1.2 from the website. 
on OSX used the packaged version from the website.
Windows used the installer from the website.

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

[krita] [Bug 377952] Assistant Tool cursor follow does not draw

[bugzilla_noreply]

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

--- Comment #3 from flibbertigibbet...@gmail.com ---
Tested on 

Asus Laptop with Nvidia GTX780m and Intel graphics (with Optimus)
Windows 10: (multiple recent driver versions)
Linux Ubuntu 16.10: Nouveau or Xorg driver (recent) 

Macbook Air mid2014 with intel graphics
OSX 10.12 : Intel (unknown driver version)

Thinkpad Laptop with Intel graphics
Linux Debian 3.16.36 : xorg driver (2:2.21.15)

All experienced the same issue.

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

[yakuake] [Bug 377955] yakuake does no longer accept input

[Achim Herwig]

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

Achim Herwig  changed:

   What|Removed |Added

   Platform|Other   |openSUSE RPMs

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

[yakuake] [Bug 377955] New: yakuake does no longer accept input

[Achim Herwig]

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

Bug ID: 377955
   Summary: yakuake does no longer accept input
   Product: yakuake
   Version: 3.0.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: achim.her...@wodca.de
  Target Milestone: ---

Sometimes yakuake stops accepting input. It does not help to open new tabs
(which is still possible) as these tabs also do not accept input any more. It
happens more often when I switch my keyboard to another computer via an USB
switch. Normal konsole windows continue to work.

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

[krita] [Bug 375878] Eraser will not switch back to brush after turning Wacom pen back around

[bugzilla_noreply]

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

1995...@gmail.com changed:

   What|Removed |Added

 CC||1995...@gmail.com

--- Comment #30 from 1995...@gmail.com ---
so, guys...um...im still having this problem and im an artist who doesnt know
much about git or code or program compilation or anything like that.

so heres a dumb-sounding question: where do i download this bug fix so i can
finally upgrade from photoshop to krita without this problem?

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

[valgrind] [Bug 377698] Missing memory check for futex() uaddr arg for FUTEX_WAKE and FUTEX_WAKE_BITSET, check only 4 args for FUTEX_WAKE_BITSET, and 2 args for FUTEX_TRYLOCK_PI

[Diane M]

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

--- Comment #6 from Diane M  ---
Julian, I encountered the problem while implementing and testing futex() for
sparc linux.

+  if (VG_(tdict).track_pre_reg_read) {
+ PRA6("futex",int,val3);
+  }

I believe the if is necessary, because it is checking whether the function
pointer is defined, whereas PRA6 eventually invokes this code which actually
calls the function pointed to.

#define PRRAn_LE(n,s,t,a)  \
   do {\
  Int here = layout->o_arg##n; \
  vg_assert(sizeof(t) <= sizeof(UWord));   \
  vg_assert(here >= 0);\
  VG_(tdict).track_pre_reg_read(   \
 Vg_CoreSysCall, tid, s"("#a")",   \
 here, sizeof(t)   \
  );   \
   } while (0)

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

[krita] [Bug 377952] Assistant Tool cursor follow does not draw

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||b...@valdyas.org

--- Comment #2 from Boudewijn Rempt  ---
I guess you did not really test this bug on a representative set of Windows,
OSX and Linux devices? So... What OS? What graphics card? What driver? If it's
Linux, appimages or distribution builds?

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

[konqueror] [Bug 377954] New: Konqueror Crash Loading ESPN page

[bugzilla_noreply]

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

Bug ID: 377954
   Summary: Konqueror Crash Loading ESPN page
   Product: konqueror
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: robert.l.k...@gmail.com
  Target Milestone: ---

Application: konqueror (4.14.16)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.8.0-42-generic x86_64
Distribution: Linux Mint 18.1 Serena

-- Information about the crash:
Konqueror crashed while loading an ESPN page with two embeded videos.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff5226fc900 (LWP 32123))]

Thread 4 (Thread 0x7ff4f4f7e700 (LWP 32215)):
#0  0x7ff51b70a709 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7ff51e9f8384 in QWaitCondition::wait(QMutex*, unsigned long)
(time=3, this=0x858b1c0) at thread/qwaitcondition_unix.cpp:84
#2  0x7ff51e9f8384 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x858a100, mutex=mutex@entry=0x732e7e8, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x7ff51e9eafe7 in QThreadPoolThread::run() (this=0x858a0f0) at
concurrent/qthreadpool.cpp:142
#4  0x7ff51e9f7e3c in QThreadPrivate::start(void*) (arg=0x858a0f0) at
thread/qthread_unix.cpp:352
#5  0x7ff51b7046ba in start_thread (arg=0x7ff4f4f7e700) at
pthread_create.c:333
#6  0x7ff52200382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7ff4f577f700 (LWP 32189)):
#0  0x7ff51b70a709 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7ff51e9f8384 in QWaitCondition::wait(QMutex*, unsigned long)
(time=3, this=0x7584120) at thread/qwaitcondition_unix.cpp:84
#2  0x7ff51e9f8384 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x732e8f0, mutex=mutex@entry=0x732e7e8, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x7ff51e9eafe7 in QThreadPoolThread::run() (this=0x732e8e0) at
concurrent/qthreadpool.cpp:142
#4  0x7ff51e9f7e3c in QThreadPrivate::start(void*) (arg=0x732e8e0) at
thread/qthread_unix.cpp:352
#5  0x7ff51b7046ba in start_thread (arg=0x7ff4f577f700) at
pthread_create.c:333
#6  0x7ff52200382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7ff4ffb24700 (LWP 32131)):
#0  0x7ff51b253a79 in g_mutex_lock (mutex=mutex@entry=0x7ff4f80009a0) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gthread-posix.c:1335
#1  0x7ff51b20e7f7 in g_main_context_prepare
(context=context@entry=0x7ff4f80009a0, priority=priority@entry=0x7ff4ffb23b50)
at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3382
#2  0x7ff51b20f2bb in g_main_context_iterate
(context=context@entry=0x7ff4f80009a0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3820
#3  0x7ff51b20f49c in g_main_context_iteration (context=0x7ff4f80009a0,
may_block=may_block@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#4  0x7ff51eb382ce in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7ff4f80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x7ff51eb0618f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7ff4ffb23c90, flags=...) at kernel/qeventloop.cpp:149
#6  0x7ff51eb064f5 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ff4ffb23c90, flags=...) at kernel/qeventloop.cpp:204
#7  0x7ff51e9f5549 in QThread::exec() (this=this@entry=0x71fcb20) at
thread/qthread.cpp:538
#8  0x7ff520ace17e in KIO::NameLookUpThread::run() (this=0x71fcb20) at
/build/kde4libs-oFCmS0/kde4libs-4.14.16/kio/kio/hostinfo.cpp:226
#9  0x7ff51e9f7e3c in QThreadPrivate::start(void*) (arg=0x71fcb20) at
thread/qthread_unix.cpp:352
#10 0x7ff51b7046ba in start_thread (arg=0x7ff4ffb24700) at
pthread_create.c:333
#11 0x7ff52200382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7ff5226fc900 (LWP 32123)):
[KCrash Handler]
#6  0x7ff5044f7e90 in
KJS::PropertyMap::getPropertyNames(KJS::PropertyNameArray&,
KJS::PropertyMap::PropertyMode) const (r=0x1) at
/build/kde4libs-oFCmS0/kde4libs-4.14.16/kjs/identifier.h:114
#7  0x7ff5044f7e90 in
KJS::PropertyMap::getPropertyNames(KJS::PropertyNameArray&,
KJS::PropertyMap::PropertyMode) const (rep=0x1, this=0x7ffd77f178f0) at
/build/kde4libs-oFCmS0/kde4libs-4.14.16/kjs/identifier.h:50
#8  0x7ff5044f7e90 in
KJS::PropertyMap::getPropertyNames(KJS::PropertyNameArray&,
KJS::PropertyMap::PropertyMode) const (this=this@entry=0x7ff501910008,

[krita] [Bug 326441] Brush parameters mixes up when switch between Stylus and Eraser.

[bugzilla_noreply]

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

1995...@gmail.com changed:

   What|Removed |Added

 CC|1995...@gmail.com   |

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

[krita] [Bug 326441] Brush parameters mixes up when switch between Stylus and Eraser.

[bugzilla_noreply]

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

1995...@gmail.com changed:

   What|Removed |Added

 CC||1995...@gmail.com

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

[kdepimlibs] [Bug 377946] Findings from a code review

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 CC||mon...@kde.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #1 from Laurent Montel  ---
4.4.10 code is closed.
Last version is 5.4.3
Regards

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

[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.

[Petros]

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

--- Comment #5 from Petros  ---
I am talkiing about something like this: 
http://lh5.ggpht.com/_feJtUp7IGuI/ShVuDHT__oI/AIw/jxd0y4dCYFA/image_thumb[1].png?imgmax=800

Ok, you get the point. While the code and some various toolviews are docked, a
special toolview -eg Documentation, or something else you want to view with
ease and at once, without scrolling and resizing- will be a second kdevelop
window.

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

[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.

[Petros]

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

--- Comment #4 from Petros  ---
(In reply to Kevin Funk from comment #3)
> @Petros: Which tool view? Maybe we should rather re-layout this particular
> tool view so it fits to contents?

Well it's not just one... I am thiniking of Valgrind outputs,
Disassembly/Registers and of course Documentation.

It would be nice if they could act as seperate windows if one wishes so.

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

[krita] [Bug 377952] Assistant Tool cursor follow does not draw

[bugzilla_noreply]

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

--- Comment #1 from flibbertigibbet...@gmail.com ---
Turning off OpenGL makes it worse. Only portions of the lines are drawn on
screen, and causes artifacts to remain on screen.

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

[kdev-python] [Bug 377720] Variable names in comments are highlighted

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

   Version Fixed In||5.1.0

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

[plasmashell] [Bug 377951] Crash desktop, black, after changes in clock config

[Antonin Roussel]

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

--- Comment #1 from Antonin Roussel  ---
Looks close to Bug 377936, but backtraces beginings are different (I don't know
what makes backtraces similar enough)

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

[plasmashell] [Bug 377953] New: plasmashell uses full cpu core: "Track file transfers and other jobs"

[Pascal d'Hermilly]

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

Bug ID: 377953
   Summary: plasmashell uses full cpu core: "Track file transfers
and other jobs"
   Product: plasmashell
   Version: 5.9.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: pas...@dhermilly.dk
CC: mklape...@kde.org
  Target Milestone: 1.0

When transferring a bunch of files plasmashell uses a full cpu core and Xorg
also uses a fair share. I'm suspecting the tiny animation - unchecking "Track
file transfers and other jobs" in notification settings instantly removes the
load.
Disabling desktop effects makes no difference.

Running KDE Neon 5.9.3 (QT 5.7.1)
Intel graphics.
kinfocenter says renderer is Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)

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

[digikam] [Bug 377587] The --database-directory argument should also be the location of the digikamrc file when used

[Glenn Washburn]

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

--- Comment #5 from Glenn Washburn  ---
In my example I was making use of the checkbox config option labeled "Write to
sidecar files" in the Metadata pane of the configuration dialog.  Once
selected, a select box become enabled, where one of the options is labeled
"Write to image and to XMP Sidecar".  This option will modify the data of image
files.  So my constructed scenario was over two disjoint image sets, one where
you want the image data modified and one where you didn't.  I was attempting to
show how using a shared config you could get into a situation where you end up
modifying the image data in the image set that you did not want to modify
because you had changed the setting in DK while using the other dataset.  If
you are unaware that that config is stored in the shared config file, as
opposed to the database, you might not realize that it had been changed for the
other image set that shared that config file.  Basically it would appear as
though someone had changed that setting without your knowledge and you might
not discover this until DK had started to write to your images.  And if that's
your only set of image (bad practice, but I doubt that uncommon), then you've
just irreversibly modified your originals.  I hope that makes it a little more
clear.

I take your point about the non-obviousness of my suggestion, and I agree that
generally options should not modify other options.  It can be confusing.  I
think to help alleviate that a short sentence in the --database-directory help
text could say something like "This option changes the default config to be in
the given directory."

I think what makes this issue critical is that DK can modify your data without
you realizing it because of a non-obvious sequence of events.  I'm concerned
with anything that might modify the database or image files in a way that the
user was not-expecting and which can not easily be reversed.  My example was a
case where the images were modified, but I believe there's a case for modifying
the database when using the Maintenance tool and syncing the image metadata to
the database.  It could be overwriting data you didn't intend if you're not
checking the Metadata settings every time (because say you don't think you need
to because you didn't change it in this instance).

After looking at the config options a little more, I don't think there's a lot
of areas where this problem exists.  Its mostly related to the the Metadata
pane.  For most of the settings, its not so consequential if the value changes
without the users knowledge.

I think my suggestion is the most conservative one to take.  If the user gets
annoyed that they have to change the same config option for each DK database
instance, they'll look into using a shared config.  Its annoying and extra time
spent, but I think that's better than potential data loss.

As to your example, I think its a very valid use case.  I just don't think it
should be the default.

Also, considering that users of the --database-directory option will have been
using the user global config file.  It might make sense to copy that file (if
it exists) to the --database-directory, and then use it.  This will effectively
break the shared config behavior that currently exists, but will minimize the
impact by keeping the expected the config values.

Since, we've had the shared config be the behavior when using
--database-directory since its implementation (I presume), I wonder if anyone
has been hit by this?  But we likely would not even know this was the issue
because the user might just think this is DK corrupting things.

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

[dolphin] [Bug 374063] file creation date

[Graham Perrin]

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

--- Comment #2 from Graham Perrin  ---
If it helps: 

https://api.kde.org/frameworks/kio/html/classKFileItem.html

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

[krita] [Bug 377952] New: Assistant Tool cursor follow does not draw

[bugzilla_noreply]

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

Bug ID: 377952
   Summary: Assistant Tool cursor follow does not draw
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: flibbertigibbet...@gmail.com
  Target Milestone: ---

Assistant tool that follows the cursor does not draw elements.

It appears that the assistant tool lines are tied to a screen or canvas
refresh. The refresh can be forced by changing focus of a layer, or by using
the "brush preview" option on the cursor.

Using the "brush preview" option makes the assistant tool lines draw as the
cursor moves.

With brush preview off, this problem can be seen by setting up a vanishing
point assistant, going to the freehand brush tool and moving the cursor:

1) Set up a vanishing point assistant.
- click Assistant tool in toolbox docker
- choose Vanishing point in the drop down in tool options docker
- click two spots on or near the canvas
2) Use a freehand brush.
- click the Freehand Brush tool in the toolbox docker
3) move the cursor on the canvas
- notice lines are not following the cursor

With "Preview shape" selected in Settings > Configure Krita > General > Cursor
Tab > Outline Shape, you will see the assistant lines following the cursor in
step three above.

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

[plasmashell] [Bug 377951] New: Crash desktop, black, after changes in clock config

[Antonin Roussel]

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

Bug ID: 377951
   Summary: Crash desktop, black, after changes in clock config
   Product: plasmashell
   Version: 5.8.6
  Platform: Mageia RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: antonin.rous...@laposte.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.6)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.9.16-desktop-2.mga6 x86_64
Distribution: "Mageia 6"

-- Information about the crash:
- What I was doing when the application crashed:
 from default :
- I added week numbers, 
- make some try to display date and seconds, apply then revert,
- added fr-fr holidays, applied, browse de calendar, but no holidays appear.
Leave the config, ask to save changes, ok. Crash.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7fdca52e7700 (LWP 685)):
#0  0x7fdd7730b000 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#1  0x7fdd7730b983 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fdd7730bb5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fdd7acad95b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fdd7ac58f9a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fdd7aa923bc in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fdd7aa96ff9 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#8  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7fdcacd3a700 (LWP 592)):
#0  0x7fdd7a3a4f9d in poll () from /lib64/libc.so.6
#1  0x7fdd7730ba54 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fdd7730bb5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fdd7acad95b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fdd7ac58f9a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fdd7aa923bc in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fdd7d324915 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7fdd7aa96ff9 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#9  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7fdccd810700 (LWP 32638)):
#0  0x7fdd7730b3ee in g_main_context_check () from /lib64/libglib-2.0.so.0
#1  0x7fdd7730b9f8 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fdd7730bb5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fdd7acad95b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fdd7ac58f9a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fdd7aa923bc in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fdd7dcaa8e2 in QQuickPixmapReader::run() () from
/lib64/libQt5Quick.so.5
#7  0x7fdd7aa96ff9 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#9  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fdd57bdf700 (LWP 32621)):
#0  0x7fdd79ba6c4f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fdd7f712234 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7fdd7f712279 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#4  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fdd61da1700 (LWP 32598)):
#0  0x7fdd77350604 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7fdd7730bb66 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#2  0x7fdd7acad95b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7fdd7ac58f9a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7fdd7aa923bc in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7fdd7d324915 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#6  0x7fdd7aa96ff9 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fdd79ba166d in start_thread () from /lib64/libpthread.so.0
#8  0x7fdd7a3b0ded in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fdd633ea700 (LWP 32595)):
#0  

[kdev-python] [Bug 377720] Variable names in comments are highlighted

[Francis Herne]

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

Francis Herne  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
 CC||m...@flherne.uk

--- Comment #2 from Francis Herne  ---
This is fixed in 5.1

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

[konsole] [Bug 377950] New: Top line of Klipper window is blank

[Jeff Seltzer]

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

Bug ID: 377950
   Summary: Top line of Klipper window is blank
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: copy-paste
  Assignee: konsole-de...@kde.org
  Reporter: je...@xilinx.com
  Target Milestone: ---

Konsole v2.3.3 in KDE 4.3.4 on RHEL 6.5 64-bit.
After Copy, top line of Klipper window, which is supposed to show the most
recently copied contents, is often blank. Performing a paste does paste the
expected contents.

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

[konsole] [Bug 377949] New: Console display only scrolls some random portion of screen

[Jeff Seltzer]

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

Bug ID: 377949
   Summary: Console display only scrolls some random portion of
screen
   Product: konsole
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: je...@xilinx.com
  Target Milestone: ---

Konsole v2.3.3 in KDE 4.3.4 on RHEL 6.5 64-bit.
During command execution (under csh), stdout only prints and scrolls in some
small portion of the lower screen instead of whole screen, resulting in
corrupted display upon command completion. Moving elevator bar up a page, then
pressing Enter or ^c results in correct display of last full screen. Using
mouse scroll wheel also causes similar screen corruption. Appears to be
intermittent. Prior versions of KDE worked ok. I found no settings to remedy.

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

[kmail2] [Bug 369011] Message view breaks after clicking on a link in an email.

[Petr Kopecký]

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

Petr Kopecký  changed:

   What|Removed |Added

 CC||ke...@centrum.cz

--- Comment #8 from Petr Kopecký  ---
I can confirm this bug on my system - Arch Linux, KMail 5.4.3, display scaling
== 2. It was not present without scaling.

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

[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.

[Kevin Funk]

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

--- Comment #3 from Kevin Funk  ---
@Petros: Which tool view? Maybe we should rather re-layout this particular tool
view so it fits to contents?

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

[kwin] [Bug 377913] Windows are not centered correctly

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Martin Gräßlin  ---
I'm sorry that center behaves differently to how you expect it. But it's the
way it is and that's by design. The feature work exactly as it's supposed to
work. I'm sorry, this won't be changed.

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

[kmail2] [Bug 376156] Deleting messages in IMAP account with server side folders enabled isn't possible

[Andrej M .]

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

Andrej M.  changed:

   What|Removed |Added

 CC||andr...@ubuntu.si

--- Comment #3 from Andrej M.  ---
Reposting my comment in this bug ...

I wasn't affected by this bug in previous KMail versions (applications 4.14.1
and lower) but now in 16.04.3 (Kontact 5.2.3) it's here and it's extremely
annoying.

- only one account out of three is problematic
- mail in Inbox cannot be moved or trashed, but copy works
- mail in other folders behaves normally, everything works
- restarting akonadi doesn't help
- restarting KMail doesn't help
- creating the account from scratch helps for a while, but then it stops
working again

In summary, KMail2 is unusable for that account no matter what I do, the same
account worked great in applications 4.14.1 and lower.

Best Regards,
Andrej

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

[Skanlite] [Bug 377929] wrong dialog at first image save

[Kåre Särs]

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

Kåre Särs  changed:

   What|Removed |Added

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

--- Comment #1 from Kåre Särs  ---
Thanks for the report!

Fixed already :)

Git commit e9eaf4c80ef0f90f53ee7aa284e56e808dcbe6c4 by Alexander Trufanov.
Committed on 09/03/2017 at 14:59.
Pushed by trufanov into branch 'master'.

Bugfix: wrong folder selection dialog behavior

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

[valgrind] [Bug 377698] Missing memory check for futex() uaddr arg for FUTEX_WAKE and FUTEX_WAKE_BITSET, check only 4 args for FUTEX_WAKE_BITSET, and 2 args for FUTEX_TRYLOCK_PI

[Julian Seward]

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

Julian Seward  changed:

   What|Removed |Added

 CC||jsew...@acm.org

--- Comment #5 from Julian Seward  ---
As background, how did you come across this problem?  Did you see some
false errors in some test cases, or something like that?

Looks ok to me, except

+  if (VG_(tdict).track_pre_reg_read) {
+ PRA6("futex",int,val3);
+  }

I think the PRA6 call shouldn't be guarded by VG_(tdict).track_pre_reg_read,
since -- as far as I can see -- PRA6 tests that anyway.  I see that that's a
pre-existing problem in this syswrap-linux.c, and IMO all of the explicit
checks of VG_(tdict).track_pre_reg_read in this file are redundant.

Please attach patches in files (the "paste text as attachment" option is
convenient, sometimes).  This avoids corruption problems.  Also, scraping
patches off the web page when it comes time to land them is difficult and
error-prone.

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

[kdeconnect] [Bug 337685] SFTP: Filesystem expose doesn't work

[bugzilla_noreply]

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

reme...@go2usa.info changed:

   What|Removed |Added

 CC||reme...@go2usa.info

--- Comment #18 from reme...@go2usa.info ---
The same problem, kdeconnect 1.0.1, Android 6.0

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

[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.

[Petros]

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

--- Comment #2 from Petros  ---
(In reply to Ian Haber from comment #1)
> I'm assuming they are qdockwidgets. as far as i know, qdockwidgets cant be
> turned into qmainwindows.

Can I do something for it?

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

[plasmashell] [Bug 377948] New: Reordering items in kmenuedit is broken

[Vladyslav Tronko]

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

Bug ID: 377948
   Summary: Reordering items in kmenuedit is broken
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: innerm...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

1. Reordering top-level nodes doesn't work. It might be not intended, but why
then drop-indicators are displayed? Definitily bug.
2. Open some node, say, Office.
You have ["A", "B", "C", "D" ... "Y", "Z"] set of items. 
2.1 Consider moving "A" item between "B" and "C". "A" is after "C" now.
Moreover, items preceding to "A" are not movable anymore, list is corrupted.
Bug.
2.2. Consider moving something "X" to position before the very first item "A".
It's now placed after "A", becoming ["A", "X", "C"]. Bug aswell, I see no sane
reason for doing that. Definitely bug.

For ones who is not sure, just backseat and try to reorder items in your way.
Occassionally you will notice that something works wrong.

If this issue gets confirmed status, I would be pleased to be assigned.

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

[frameworks-plasma] [Bug 377944] [PATCH] Mixed up color variable and wrong indexing in apply-stylesheet.sh

[Andreas]

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

Andreas  changed:

   What|Removed |Added

Product|plasmashell |frameworks-plasma
Version|master  |unspecified
   Target Milestone|1.0 |---
  Component|general |libplasma

--- Comment #1 from Andreas  ---
sorry, i put this in the wrong section

i'm not sure where to put this exactly, i'm fairly certain it belongs somewhere
under frameworks-plasma, but not sure which subsection. also, i'm not sure
which version i have to pick here, it's from the git master.

sorry again, i am new to this, if i made an error please reassign it again

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

[kde] [Bug 377947] New: Crash on changing theme

[Andrew Rembrandt]

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

Bug ID: 377947
   Summary: Crash on changing theme
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: and...@rembrandt.me.uk
  Target Milestone: ---

Application: kcmshell5 (5.9.3)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.9.16-48-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed: Downloaded several themes,
changed them (via apply) between 5-15 times and closed the window (crash on
close)

-- Backtrace:
Application: System Settings Module (kcmshell5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb887d6b180 (LWP 12256))]

Thread 6 (Thread 0x7fb8472c9700 (LWP 12263)):
#0  0x7fb8876c67bd in poll () from /lib64/libc.so.6
#1  0x7fb87f92a896 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fb87f92a9ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fb884dd718b in QEventDispatcherGlib::processEvents
(this=0x7fb848c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb884d80aea in QEventLoop::exec (this=this@entry=0x7fb8472c8cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fb884bae813 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fb884bb34c8 in QThreadPrivate::start (arg=0x6028ce0) at
thread/qthread_unix.cpp:368
#7  0x7fb881b90537 in start_thread () from /lib64/libpthread.so.0
#8  0x7fb8876d004f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fb856213700 (LWP 12260)):
#0  0x7fb8876c67bd in poll () from /lib64/libc.so.6
#1  0x7fb87f92a896 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fb87f92a9ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fb884dd718b in QEventDispatcherGlib::processEvents
(this=0x7fb858c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb884d80aea in QEventLoop::exec (this=this@entry=0x7fb856212cf0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fb884bae813 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fb884bb34c8 in QThreadPrivate::start (arg=0x6092a60) at
thread/qthread_unix.cpp:368
#7  0x7fb881b90537 in start_thread () from /lib64/libpthread.so.0
#8  0x7fb8876d004f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fb8690de700 (LWP 12259)):
#0  0x7fb8876c67bd in poll () from /lib64/libc.so.6
#1  0x7fb87f92a896 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fb87f92a9ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fb884dd718b in QEventDispatcherGlib::processEvents
(this=0x7fb85c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb884d80aea in QEventLoop::exec (this=this@entry=0x7fb8690ddcd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fb884bae813 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7fb883728305 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x7fb884bb34c8 in QThreadPrivate::start (arg=0x2615ba0) at
thread/qthread_unix.cpp:368
#8  0x7fb881b90537 in start_thread () from /lib64/libpthread.so.0
#9  0x7fb8876d004f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fb86b94e700 (LWP 12258)):
#0  0x7fb8876c67bd in poll () from /lib64/libc.so.6
#1  0x7fb87f92a896 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fb87f92a9ac in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fb884dd718b in QEventDispatcherGlib::processEvents
(this=0x7fb8640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fb884d80aea in QEventLoop::exec (this=this@entry=0x7fb86b94dcc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fb884bae813 in QThread::exec (this=this@entry=0x7fb8869ecd20
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#6  0x7fb88677b385 in QDBusConnectionManager::run (this=0x7fb8869ecd20
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#7  0x7fb884bb34c8 in QThreadPrivate::start (arg=0x7fb8869ecd20 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#8  0x7fb881b90537 in start_thread () from /lib64/libpthread.so.0
#9  0x7fb8876d004f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fb873cfe700 (LWP 12257)):
#0  0x7fb8876c67bd in poll () from /lib64/libc.so.6
#1  0x7fb881fb73e0 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fb881fb9179 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fb876269889 in 

[kdepimlibs] [Bug 377946] New: Findings from a code review

[Steve]

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

Bug ID: 377946
   Summary: Findings from a code review
   Product: kdepimlibs
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: sgr...@redhat.com
  Target Milestone: ---

Missing break/return:
kdepimlibs-4.14.10/akonadi/calendar/calendarmodel.cpp:115: unterminated_case:
The case for value "Qt::DisplayRole" is not terminated by a 'break' statement.
kdepimlibs-4.14.10/akonadi/calendar/calendarmodel.cpp:153: fallthrough: The
above case falls through to this one.

Confused code:
kdepimlibs-4.14.10/akonadi/entitylistview.cpp:193: cond_const: Condition
"menuCanceled", taking false branch. Now the value of "menuCanceled" is equal
to 0.
kdepimlibs-4.14.10/akonadi/entitylistview.cpp:195: const: At condition
"menuCanceled", the value of "menuCanceled" must be equal to 0.
kdepimlibs-4.14.10/akonadi/entitylistview.cpp:195: dead_error_condition: The
condition "menuCanceled" cannot be true.
kdepimlibs-4.14.10/akonadi/entitylistview.cpp:196: dead_error_line: Execution
cannot reach this statement: "return;".

Object Passed by Value instead of Reference:
kdepimlibs-4.14.10/kcal/icalformat_p.cpp:2548: pass_by_value: Passing parameter
r of type "icalrecurrencetype" (size 2904 bytes) by value.

Unterminated string possible:
kdepimlibs-4.14.10/kcalcore/versit/vobject.c:1238: buffer_size_warning: strncpy
does not terminate strings if they are equal to or larger than the size passed,
To be safe it needs to be manually terminated: buf1[255] = 0;

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

[digikam] [Bug 371648] not able to use in digikam cifs share with the same name under linux and windows

[bugzilla_noreply]

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

ed...@zimmermann.nl changed:

   What|Removed |Added

 CC||ed...@zimmermann.nl

--- Comment #3 from ed...@zimmermann.nl ---
Same issue here. Windows and OSX. Photos stored on a NAS. Database also.
Sharing this database from both OS would be fantastic and give Digikam a hell
of an USP!!!

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

[frameworks-plasma] [Bug 377945] New: When copying file in dolphin two notifications are shown upon completion.

[bugzilla_noreply]

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

Bug ID: 377945
   Summary: When copying file in dolphin two notifications are
shown upon completion.
   Product: frameworks-plasma
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tooltips
  Assignee: notm...@gmail.com
  Reporter: axels...@protonmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: ---

Created attachment 104691
  --> https://bugs.kde.org/attachment.cgi?id=104691=edit
Picture of the phenomenon.

Hello,

First bug report be gentle, running openSUSE Tumbleweed with KDE. When i copy
files between partitions it reports finished twice when it completes.

In my case it happens all the time, i don't know what else to include but i'm
happy to provide more info if requested.

Thanks to the KDE team for a polished user experience.

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

[valgrind] [Bug 340777] Illegal instruction on mips (ar71xx)

[Petar Jovanovic]

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

--- Comment #9 from Petar Jovanovic  ---
I believe the new (non-mips16) issues are not MIPS-related, but rather
MUSL-related.

Can you try to apply the patch in the second comment Bug 359202 and see if it
sorts out your issues with binaries that do not have or use mips16 code?

https://bugs.kde.org/show_bug.cgi?id=359202#c2

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