[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around

[Michail Vourlakos]

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

--- Comment #17 from Michail Vourlakos  ---
(In reply to Kai Uwe Broulik from comment #15)
> 
> Anyway, from what I can tell is that the startup task matches to
> /usr/share/applications/org.kde.dolphin.desktop whereas the running
> application ends up being mapped to applications:org.kde.dolphin.desktop
> 

how about the launcherPosition and launcherActivities functions from TasksModel
shouldnt these functions also understand the new urls e.g.
applications:systemsettings.desktop

in order to not return -1 and null when the new style is used?

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

[digikam] [Bug 329391] digiKam creates 'Document Name' metadata with unreadable characters (encoding problem of accents)

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #7 from Maik Qualmann  ---
I see it like Wolfgang. When the image is rotated, the DocumentName should not
be updated. I will remove this code.

Maik

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

[kmymoney4] [Bug 385402] No way to change the date format

[Thomas Baumgart]

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

--- Comment #7 from Thomas Baumgart  ---
I still believe that this is caused by running KMyMoney 4.8 on a KF5 based
environment without the KDE4 tools installed.

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

[systemsettings] [Bug 383379] Modernize Input Devices section to work with Libinput

[Nate Graham]

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

--- Comment #13 from Nate Graham  ---
Slimbook team, any progress on turning your app into a KCM visible in System
Settings?

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

[konsole] [Bug 385620] app crashed after i put in a command

[Nate Graham]

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

--- Comment #4 from Nate Graham  ---
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.

[plasma-pa] [Bug 385602] Add option to show volume level in OSD

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |wishlist
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

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

[konsole] [Bug 385620] app crashed after i put in a command

[bugzilla_noreply]

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

--- Comment #3 from animerocks...@gmail.com ---
How do I attach backtrace

On Oct 11, 2017 9:30 PM, "Nate Graham"  wrote:

> https://bugs.kde.org/show_bug.cgi?id=385620
>
> Nate Graham  changed:
>
>What|Removed |Added
> 
> 
>  Resolution|WAITINGFORINFO  |BACKTRACE
>
> --- Comment #2 from Nate Graham  ---
> Also, please attach a backtrace. This isn't actionable without one.
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[plasma-pa] [Bug 385602] Add option to show volume level in OSD

[Petr Nehez]

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

Petr Nehez  changed:

   What|Removed |Added

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

--- Comment #2 from Petr Nehez  ---
Yes, the textual form would be really appreciated.

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

[digikam] [Bug 385592] digikam segfaults occasionally, when renaming/moving multiple images

[Maik Qualmann]

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

--- Comment #7 from Maik Qualmann  ---
Created attachment 108290
  --> https://bugs.kde.org/attachment.cgi?id=108290=edit
ImageInfo.patch

Johannes,

can you apply this patch and test it? This crash I have never seen or
reproduced here.

Maik

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

[okular] [Bug 385384] Some PNG files produced by acdsee can't be displayed

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Nate Graham  ---
Thanks for the bug and the investigation. Please feel free to submit a patch on
http://phabricator.kde.org/!

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

[systemsettings] [Bug 383379] Modernize Input Devices section to work with Libinput

[Arthur Țițeică]

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

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@cloud.titeica.ro

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

[digikam] [Bug 385592] digikam segfaults occasionally, when renaming/moving multiple images [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

Summary|digikam segfaults   |digikam segfaults
   |occasionally, when  |occasionally, when
   |renaming/moving multiple|renaming/moving multiple
   |images  |images [patch]

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

[Spectacle] [Bug 385559] "Copy to Clibboard" CLI option for spectacle

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

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

--- Comment #1 from Nate Graham  ---


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

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

[Spectacle] [Bug 384830] add option "copy to clipboard automatically"

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||kirill.bogdane...@gmail.com

--- Comment #2 from Nate Graham  ---
*** Bug 385559 has been marked as a duplicate of this bug. ***

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

[konsole] [Bug 385620] app crashed after i put in a command

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |BACKTRACE

--- Comment #2 from Nate Graham  ---
Also, please attach a backtrace. This isn't actionable without one.

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

[konsole] [Bug 385620] app crashed after i put in a command

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
Is this in Ubuntu 16.04?

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

[plasmashell] [Bug 385631] Launch feedback on icon-only taskbar moves launcher icon

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Nate Graham  ---


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

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|launchInPlace is broken |launchInPlace is broken
   |from libtaskmanager |from libtaskmanager; causes
   ||Icons-Only Task manager
   ||icons to jump around

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||chris.vansteenlandt@gmail.c
   ||om

--- Comment #16 from Nate Graham  ---
*** Bug 385631 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 385626] KWin crashed when Alt+Tab-ing through open windows

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

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

--- Comment #1 from Martin Flöser  ---
Crash in Mesa. Please report there. The quality of the backtrace is really
good, so please report it.

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

[kwin] [Bug 385623] Clicking on left screen edge ignored

[Martin Flöser]

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

--- Comment #3 from Martin Flöser  ---
Please xprop the left edge.

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

[kwin] [Bug 385573] desktop-cubes do not start automatically

[Martin Flöser]

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

--- Comment #3 from Martin Flöser  ---
Alt+shift+f12 is the shortcut to activate compositing. Not the desktop cube.

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

[frameworks-knotifications] [Bug 383709] Systray icons under Gnome only expose XEmbed, not KSNI

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[frameworks-kparts] [Bug 385639] New: Adapting the preview to available space (i.e. current width and height of preview tool view)

[avlas]

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

Bug ID: 385639
   Summary: Adapting the preview to available space (i.e. current
width and height of preview tool view)
   Product: frameworks-kparts
   Version: 5.38.0
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: jsar...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Right now the KTextEditorPreviewPlugin allows to preview different sort of text
files (for example SVG and dot files). However, there is the limitation that
the size of the preview is fixed. Ideally, this size would be adapted to
available space.

Discussion of this feature request appeared first here:
https://frinring.wordpress.com/2017/10/09/ktexteditorpreviewplugin-0-2-0/#comment-5652

The developer of KTextEditorPreviewPlugin mentioned that this feature could
also be interesting for other KParts plugins, like the Ark preview.

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

[kgraphviewer] [Bug 385638] New: Black color is used when background color is set to none in dot file

[avlas]

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

Bug ID: 385638
   Summary: Black color is used when background color is set to
none in dot file
   Product: kgraphviewer
   Version: 2.4.2
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kl...@free.fr
  Reporter: jsar...@gmail.com
  Target Milestone: ---

I have problems visualizing dot files with transparent background color: the
background appears in black (background color actually set to none), which
hides most of its content.

I wonder if it would be possible for transparent backgrounds to do like
Gwenview, where the user can choose between 1) setting a chess board background
(default), or 2) selecting a specific background color.

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

[systemsettings] [Bug 385608] Main list jumps when scrolling (mostly down)

[Michael D]

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

Michael D  changed:

   What|Removed |Added

 CC||nortex...@gmail.com

--- Comment #1 from Michael D  ---
Same issue here when scrolling with Elan touchpad, making it nearly impossible
to normally scroll the system settings categories in the left pane.

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

[krita] [Bug 385568] The brush stroke wont appear on the canvas until i click the layer it is on.

[bugzilla_noreply]

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

--- Comment #2 from rainbowgiraff...@gmail.com ---
I did that and it didn't change anything... I'm not sure what to do.

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

[Discover] [Bug 385637] New: Crash on startup

[Szczepan Hołyszewski]

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

Bug ID: 385637
   Summary: Crash on startup
   Product: Discover
   Version: 5.11.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: rula...@wp.pl
  Target Milestone: ---

Application: plasma-discover (5.11.0)

Qt Version: 5.9.2
Frameworks Version: 5.38.0
Operating System: Linux 4.13.5-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

Tried to launch the Discover using its icon on the icon taskbar.

The crash can be reproduced every time.

-- Backtrace:
Application: Odkrywca (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f81d17d0480 (LWP 11059))]

Thread 13 (Thread 0x7f818cc52700 (LWP 11075)):
#0  0x7f81ccf06d4b in poll () at /usr/lib/libc.so.6
#1  0x7f81c74dfed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f81c74dffae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f81cd845cf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f81cd7e948b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f81cd60227e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f81cd606fcb in  () at /usr/lib/libQt5Core.so.5
#7  0x7f81c96c208a in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f81ccf1124f in clone () at /usr/lib/libc.so.6

Thread 12 (Thread 0x7f818da89700 (LWP 11071)):
#0  0x7f81c75075f9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f81c74dfeb8 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f81c74e0f42 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3  0x7f818f155e28 in  () at /usr/lib/libgio-2.0.so.0
#4  0x7f81c74d41eb in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f81c96c208a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f81ccf1124f in clone () at /usr/lib/libc.so.6

Thread 11 (Thread 0x7f818e28a700 (LWP 11070)):
#0  0x7f81ccf02868 in read () at /usr/lib/libc.so.6
#1  0x7f81c7507521 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f81c74de90b in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f81c74dfe76 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f81c74dffae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f81c74e0002 in  () at /usr/lib/libglib-2.0.so.0
#6  0x7f81c74d41eb in  () at /usr/lib/libglib-2.0.so.0
#7  0x7f81c96c208a in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f81ccf1124f in clone () at /usr/lib/libc.so.6

Thread 10 (Thread 0x7f81a48b1700 (LWP 11069)):
#0  0x7f81c96c86cd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f81cd608311 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f81cd6033f6 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f81cd606fcb in  () at /usr/lib/libQt5Core.so.5
#4  0x7f81c96c208a in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f81ccf1124f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7f81a50b2700 (LWP 11068)):
#0  0x7f81c96c86cd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f81cd608311 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f81cd6033f6 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f81cd606fcb in  () at /usr/lib/libQt5Core.so.5
#4  0x7f81c96c208a in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f81ccf1124f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7f81a5aba700 (LWP 11067)):
#0  0x7f81c96c86cd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f81cd608311 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f81cd6033f6 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f81cd606fcb in  () at /usr/lib/libQt5Core.so.5
#4  0x7f81c96c208a in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f81ccf1124f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f81a6951700 (LWP 11066)):
#0  0x7f81c96c86cd in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f81cd608311 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f81cd6033f6 in  () at /usr/lib/libQt5Core.so.5
#3  0x7f81cd606fcb in  () at /usr/lib/libQt5Core.so.5
#4  0x7f81c96c208a in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f81ccf1124f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f81a7152700 (LWP 11065)):
#0  0x7f81ccf06d4b in poll () at /usr/lib/libc.so.6
#1  0x7f81c74dfed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f81c74dffae in g_main_context_iteration () 

[Discover] [Bug 385636] New: Discover Crash

[Jeremy Stevenson]

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

Bug ID: 385636
   Summary: Discover Crash
   Product: Discover
   Version: 5.9.5
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: jeremy.m.steven...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.9.5)
 (Compiled from sources)
Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-37-generic x86_64
Distribution: Ubuntu 17.04

-- Information about the crash:
- What I was doing when the application crashed:
Initial application update after "upgrading" from Kubuntu from Ubuntu 17.04 via
bash

The crash can be reproduced sometimes.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f207b828440 (LWP 5979))]

Thread 10 (Thread 0x7f1fc654a700 (LWP 6024)):
#0  0x7f2073b28510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f2077798b4b in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

Thread 9 (Thread 0x7f1fc73a1700 (LWP 6018)):
#0  0x7f20719caef4 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f207198510a in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f20719855e0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2071985902 in g_main_loop_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f20142d5476 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7f20719acf65 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f2073b226da in start_thread (arg=0x7f1fc73a1700) at
pthread_create.c:456
#7  0x7f2076d93d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7f1fc7ba2700 (LWP 6017)):
#0  0x7f2076d838ad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f20719c9b30 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2071985042 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2071985514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f207198568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f20719856d1 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f20719acf65 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f2073b226da in start_thread (arg=0x7f1fc7ba2700) at
pthread_create.c:456
#8  0x7f2076d93d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7f2036ffd700 (LWP 5991)):
#0  0x7f2076d838ad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f20719c9b30 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2071985042 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2071985514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f207198568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f20779bbf2b in QEventDispatcherGlib::~QEventDispatcherGlib() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f2036ffcc90 in  ()
#7  0x5625ee53d8e0 in  ()
#8  0xf1649513d6b52800 in  ()
#9  0x7f2036ffcd00 in  ()
#10 0x7f2036ffcd00 in  ()
#11 0x in  ()

Thread 6 (Thread 0x7f2046cd2700 (LWP 5986)):
#0  0x7f2076d838ad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f20719c9b30 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2071985042 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2071985514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f207198568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f20779bbf2b in QEventDispatcherGlib::~QEventDispatcherGlib() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f2046cd1c90 in  ()
#7  0x5625ee4f1d90 in  ()
#8  0xf1649513d6b52800 in  ()
#9  0x7f2046cd1d00 in  ()
#10 0x7f2046cd1d00 in  ()
#11 0x in  ()

Thread 5 (Thread 0x7f2057fff700 (LWP 5985)):
#0  0x7f207198549b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f207198568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f20779bbf2b in QEventDispatcherGlib::~QEventDispatcherGlib() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f2057ffec20 in  ()
#4  0x5625ee396cb0 in  ()
#5  0xf1649513d6b52800 in  ()
#6  0x7f2057ffec90 in  ()
#7  0x7f2057ffec90 in  ()
#8  0x in  ()

Thread 4 (Thread 0x7f205edca700 (LWP 5982)):
#0  0x7f2076da1d8f in __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67
#1  0x7f2076d87d82 in poll () 

[Oxygen] [Bug 384864] Oxygen cursors have some reversed symlinks

[Jack]

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

--- Comment #2 from Jack  ---
I have prepared a patch for Phabricator - who do I list as reviewer?  (It
doesn't accept #oxygen.)

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

[k3b] [Bug 385635] New: verification appears to be via checksum comparison rather than actual data comparison

[bugzilla_noreply]

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

Bug ID: 385635
   Summary: verification appears to be via checksum comparison
rather than actual data comparison
   Product: k3b
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Verfication
  Assignee: k...@kde.org
  Reporter: zcw...@aserty.com
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

version is 2.0.2 (I am in the process of burning the latest Debian DVDs for an
upgrade)

Checksum comparison seems a rather dubious way of verifying a burn and gains
you nothing in performance:

chrisw@acer-Aspire-5610:~$ time cat /dev/sr0 >/dev/null

real8m51.207s
user0m0.128s
sys 0m10.596s
chrisw@acer-Aspire-5610:~$ time md5sum /dev/sr0
9c8951b69992c0a14821da030f27198d  /dev/sr0

real8m49.449s
user0m29.040s
sys 0m9.092s
chrisw@acer-Aspire-5610:~$ time cmp /dev/sr0 '/work/Debian
9.1.0/firmware-9.1.0-i386-DVD-1.iso' 

real8m49.058s
user0m32.916s
sys 0m20.336s
chrisw@acer-Aspire-5610:~$

Checksum(s) can still be calculated, but, I think it's important to do a proper
read back check.

A graph of the read speed would also be helpful in showing if the burned disc
has any bad spots.

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

[plasmashell] [Bug 357367] Desktop Settings -> Mouse Actions -> Vertical Scroll set to Application Launcher does not work

[Wulf]

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

Wulf  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #8 from Wulf  ---
Hello,

I can see the changes in
/usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderView.qml

But unfortunately the bug isn't resolved with Plasma 5.11

Desktop Settings -> Mouse Actions -> Vertical Scroll set to Application
Launcher still does not work

thx

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

[krita] [Bug 384544] No GMIC plugin for Linux

[Rafael]

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

--- Comment #10 from Rafael  ---
I'm using now appimage, expecting some long ago bugs have been solved, but only
the GMIC issue is solved at this point. Text tools issues continues and in the
appimage resizing brush tool (AltGR + ]) doesn't work  :(

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

[krita] [Bug 378572] Text does not display properly when being edited

[Rafael]

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

Rafael  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #2 from Rafael  ---
Still not solved in appimage  :(

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

[krita] [Bug 383411] Life broking Text Tools problems

[Rafael]

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

Rafael  changed:

   What|Removed |Added

 CC||rafael.linux.u...@gmail.com

--- Comment #2 from Rafael  ---
This appear as resolved, however, I'm using latest appimage version and the bug
continues appearing.

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

[plasmashell] [Bug 385634] New: Yakuake starts off screen

[bugzilla_noreply]

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

Bug ID: 385634
   Summary: Yakuake starts off screen
   Product: plasmashell
   Version: 5.11.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: generic-wayland
  Assignee: plasma-b...@kde.org
  Reporter: syz...@elitemail.org
  Target Milestone: 1.0

This is only happens when I log into the wayland session. When I open up
yakuake and start typing, I can't see what I'm typing since it's off the
screen. I can finally see what I'm typing once I've typed several lines.

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

[konsole] [Bug 385633] New: [Wayland] konsole crash on close.

[Tony]

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

Bug ID: 385633
   Summary: [Wayland] konsole crash on close.
   Product: konsole
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: jodr...@live.com
  Target Milestone: ---

Application: konsole (17.11.70)

Qt Version: 5.9.2
Frameworks Version: 5.39.0
Operating System: Linux 4.13.5-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
I had 3 tabs open when i close the konsole window, then i closed the window the
crash pop right after.

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f520bbd2700 (LWP 10640)):
#0  0x7f5220750cab in poll () from /lib64/libc.so.6
#1  0x7f52169a9149 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f52169a925c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f521cca025b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f521cc4873a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f521ca781fa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f521ade2a45 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7f521ca7cc0e in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f5218492558 in start_thread () from /lib64/libpthread.so.0
#9  0x7f522075b45f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f5220e48040 (LWP 10639)):
[KCrash Handler]
#6  0x7f520f325099 in wl_map_insert_at (map=,
flags=flags@entry=0, i=, data=) at
src/wayland-util.c:249
#7  0x7f520f3211ae in proxy_destroy (proxy=0x55b1080a6d30) at
src/wayland-client.c:411
#8  wl_proxy_destroy (proxy=0x55b1080a6d30) at src/wayland-client.c:442
#9  0x7f520db3f6a7 in org_kde_plasma_window_destroy
(org_kde_plasma_window=0x55b1080a6d30) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/build/src/client/wayland-plasma-window-management-client-protocol.h:634
#10 KWayland::Client::WaylandPointer::release (this=0x55b107fdf5b0,
this=0x55b107fdf5b0) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/wayland_pointer_p.h:53
#11 KWayland::Client::PlasmaWindow::release (this=this@entry=0x55b107e1a780) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/plasmawindowmanagement.cpp:745
#12 0x7f520db3f6ca in KWayland::Client::PlasmaWindow::~PlasmaWindow
(this=0x55b107e1a780, __in_chrg=) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/plasmawindowmanagement.cpp:735
#13 0x7f520db3f7c9 in KWayland::Client::PlasmaWindow::~PlasmaWindow
(this=0x55b107e1a780, __in_chrg=) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/plasmawindowmanagement.cpp:736
#14 0x7f521cc7540b in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#15 0x7f521cc7e76b in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#16 0x7f520db3fd99 in
KWayland::Client::PlasmaWindowManagement::~PlasmaWindowManagement
(this=0x55b107e0aaa0, __in_chrg=) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/plasmawindowmanagement.cpp:252
#17 0x7f521cc7540b in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#18 0x7f521cc7e76b in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#19 0x7f520a7b0a93 in WaylandIntegration::~WaylandIntegration
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.11.90git.20170914T114718~1d8054b/src/windowsystem/waylandintegration.cpp:54
#20 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.11.90git.20170914T114718~1d8054b/src/windowsystem/waylandintegration.cpp:40
#21 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.11.90git.20170914T114718~1d8054b/src/windowsystem/waylandintegration.cpp:46
#22 0x7f522069bce8 in __run_exit_handlers () from /lib64/libc.so.6
#23 0x7f522069bd3a in exit () from /lib64/libc.so.6
#24 0x7f5220683f51 in __libc_start_main () from /lib64/libc.so.6
#25 0x55b1071b681a in _start ()

Possible duplicates by query: bug 381226, bug 379728.

Reported using DrKonqi

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

[plasmashell] [Bug 385632] New: System tray crash

[Adam]

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

Bug ID: 385632
   Summary: System tray crash
   Product: plasmashell
   Version: 5.11.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: adam...@techie.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.0)

Qt Version: 5.9.2
Frameworks Version: 5.38.0
Operating System: Linux 4.13.5-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
I was changing a setting in the system tray settings  in the entries. It was
"your system is up-to-date" I was changing it from auto to hidden then clicked
OK

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

Thread 6 (Thread 0x7efda6b18700 (LWP 915)):
#0  0x7efe56c36d4b in poll () at /usr/lib/libc.so.6
#1  0x7efe51535ed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7efe51535fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7efe57573cf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7efe5751748b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7efe5733027e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7efe5b05029b in  () at /usr/lib/libQt5Quick.so.5
#7  0x7efe57334fcb in  () at /usr/lib/libQt5Core.so.5
#8  0x7efe564ee08a in start_thread () at /usr/lib/libpthread.so.0
#9  0x7efe56c4124f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7efe32b9c700 (LWP 879)):
#0  0x7efe564f438d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7efe5cd65ef7 in  () at /usr/lib/libQt5Script.so.5
#2  0x7efe5cd65f39 in  () at /usr/lib/libQt5Script.so.5
#3  0x7efe564ee08a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7efe56c4124f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7efe3cd55700 (LWP 864)):
#0  0x7efe56c32868 in read () at /usr/lib/libc.so.6
#1  0x7efe5155d521 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7efe5153490b in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7efe51535e76 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7efe51535fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7efe57573cf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7efe5751748b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7efe5733027e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7efe5a4a3bc9 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7efe57334fcb in  () at /usr/lib/libQt5Core.so.5
#10 0x7efe564ee08a in start_thread () at /usr/lib/libpthread.so.0
#11 0x7efe56c4124f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7efe3f1e1700 (LWP 844)):
#0  0x7efe5155d5f9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7efe5152f3b2 in g_main_context_query () at /usr/lib/libglib-2.0.so.0
#2  0x7efe51535e4c in  () at /usr/lib/libglib-2.0.so.0
#3  0x7efe51535fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7efe57573cf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7efe5751748b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7efe5733027e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7efe5a4a3bc9 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7efe57334fcb in  () at /usr/lib/libQt5Core.so.5
#9  0x7efe564ee08a in start_thread () at /usr/lib/libpthread.so.0
#10 0x7efe56c4124f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7efe44cdf700 (LWP 756)):
#0  0x7efe5155d5f9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7efe5153577d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7efe51535df6 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7efe51535fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7efe57573cf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7efe5751748b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7efe5733027e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7efe5798f376 in  () at /usr/lib/libQt5DBus.so.5
#8  0x7efe57334fcb in  () at /usr/lib/libQt5Core.so.5
#9  0x7efe564ee08a in start_thread () at /usr/lib/libpthread.so.0
#10 0x7efe56c4124f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7efe5d699800 (LWP 723)):
[KCrash Handler]
#5  0x7efe5a3d4375 in
QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, int, bool) ()
at /usr/lib/libQt5Qml.so.5
#6  0x7efe5a3e806c in

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Kai Uwe Broulik]

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

--- Comment #15 from Kai Uwe Broulik  ---
> Design-wise, is that actually a desirable goal?

Yes it is. This is the way desktop files are supposed to work and work
everywhere else. (Except for the icon plasmoid because that's a whole other
story)

Anyway, from what I can tell is that the startup task matches to
/usr/share/applications/org.kde.dolphin.desktop whereas the running application
ends up being mapped to applications:org.kde.dolphin.desktop

Eike is at Qt World Summit right now, I'll try to have a look as to why that
happens.

> Regardless, this is quite a niche corner case; how many people even have 
> .desktop files in ~/.local/share that would otherwise conflict with the ones 
> in /usr/local/share?

Apps can do that, cf. dynamic jump list actions in Kate, users can also edit
applications to their liking, etc.

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

[kscreenlocker] [Bug 385610] Lockscreen: don't time block password entry - only login attempts.

[Pascal d'Hermilly]

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

--- Comment #2 from Pascal d'Hermilly  ---
Right. But could it wait with the annoying part until after 3 failed attempts?
3 attempts isn't exactly "brute force".

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Nate Graham]

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

--- Comment #14 from Nate Graham  ---
Design-wise, is that actually a desirable goal?

Let's say I have a desktop file for a program in /usr/local/share/ and I pin a
Task Manager entry for it. All is well. Now for whatever reason I create a
.desktop file for it in ~/.local/share/, and perhaps that .desktop file is
slightly different. My expectation is that the Task Manager icon still opens
the original thing I told it to open, and that if I wanted a Task Manager icon
open the one in ~/.local/share, I would make one myself. Having it open the one
in ~/.local/share without warning strikes me as something that could cause
surprise.

Regardless, this is quite a niche corner case; how many people even have
.desktop files in ~/.local/share that would otherwise conflict with the ones in
/usr/local/share?

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #13 from Kai Uwe Broulik  ---
> I dont know what is the developer's intended behavior.. The first one or the 
> latter one ?

The new applications: type URL is so we can handle when a system-wide desktop
file (in /usr/share) gets overriden by a user-local one in ~/.local/share. From
what I can tell it *should* treat both the same but the rewriting or mapping
between the absolute path and applications path causes trouble here?

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

[kdevelop] [Bug 383875] After unchecking plugin CMake Documentation disappears view with Qt Documentation

[Piotr Mierzwinski]

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

--- Comment #5 from Piotr Mierzwinski  ---
I confirm. After this fix "Documentation" view (only with Qt) works fine for
me.
Thanks.

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

[plasmashell] [Bug 385631] New: Launch feedback on icon-only taskbar moves launcher icon

[bugzilla_noreply]

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

Bug ID: 385631
   Summary: Launch feedback on icon-only taskbar moves launcher
icon
   Product: plasmashell
   Version: 5.11.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: chris.vansteenla...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

When I launch an application from the icon-only taskbar, a duplicate of the
application icon moves to the first empty place on the taskbar, shows the
feedback effect and then disappears again. The original application icon on the
taskbar shows correctly that the application is launched by adding an extra
thick line under the icon. This behavior did not show up in plasma 5.10.

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

[kwayland-integration] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session

[Tony]

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

Tony  changed:

   What|Removed |Added

 CC||jodr...@live.com

--- Comment #41 from Tony  ---
There is a bit of a regression related to this one. On wayland you can click on
"Graphical information>opengl" all good, but if you click on "wayland"  and
then "opengl" again, infocenter will close with not triggering drkonqui.

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

[plasmashell] [Bug 385619] Regression: Icons Only Taskbar pinned items change positions when opened.

[Nate Graham]

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

--- Comment #5 from Nate Graham  ---
Please add any new comments to https://bugs.kde.org/show_bug.cgi?id=385594. The
more we centralize information in a single bug report, the faster it gets
fixed. Thanks!

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

[frameworks-knotifications] [Bug 383709] Systray icons under Gnome only expose XEmbed, not KSNI

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Component|general |general
 CC||k...@davidedmundson.co.uk,
   ||kdelibs-b...@kde.org
Product|frameworks-frameworkintegra |frameworks-knotifications
   |tion|

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

[plasmashell] [Bug 385619] Regression: Icons Only Taskbar pinned items change positions when opened.

[Shitikanth]

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

Shitikanth  changed:

   What|Removed |Added

 CC||golu3...@gmail.com

--- Comment #4 from Shitikanth  ---
For Icons-only Task Manager, you can delete the task manager, create a new one
and pin your applications afresh, and after that it seems to work (except that
you see an additional icon at end of taskbar for a brief second after launching
an application).

This doesn't workaround doesn't work on regular Task Manager for me.

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

[digikam] [Bug 385630] Views Requiring Maps Takes ~30s to Launch

[Maik Qualmann]

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

--- Comment #5 from Maik Qualmann  ---
You can also trigger the problem by opening the online manual via the built-in
webkit browser.

Maik

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

[digikam] [Bug 385630] Views Requiring Maps Takes ~30s to Launch

[Maik Qualmann]

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

--- Comment #4 from Maik Qualmann  ---
No, Marble is ok. I've been watching this delay for some time. But I am of the
opinion that it is so extreme only in the virtual machine. I test it tomorrow
on a real Windows machine. I use the current Windows-5.8.0 build.

Maik

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

[digikam] [Bug 385630] Views Requiring Maps Takes ~30s to Launch

[bugzilla_noreply]

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

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

The guy who report this file has previously seen a problem with a bad
installation of Marble files in Windows bundle. I fixed that and now, the
Geolocation map view take a while to be suitable. So i suspect that Marble
plugins introduce a dysfunction here, because when no marble plugins are
loaded, the problem do not exist.

Gilles

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

[digikam] [Bug 385630] Views Requiring Maps Takes ~30s to Launch

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
The problem is not Marble under Windows. Google maps stops after 50% maps
loading and then hang a while. If Marble is set as display, the dialog will
open quickly.

Maik

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

[digikam] [Bug 385630] Views Requiring Maps Takes ~30s to Launch

[bugzilla_noreply]

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

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

   What|Removed |Added

   Platform|Other   |MS Windows

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

[digikam] [Bug 385630] Views Requiring Maps Takes ~30s to Launch

[bugzilla_noreply]

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

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

   What|Removed |Added

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

--- Comment #1 from caulier.gil...@gmail.com ---
this is due certainly of a Marble plugin playing with a remote web service hile
the map is displayed.

Go to the directory where is installed digiKam. There is a plugins/ sub
directory containing a lot of lib*plugin.dll files. There are Marble plugins.
Do not look in others sub directories inside plugins/ there are here for others
reasons.

To find the right dll file introducing this time latency, remove step by step
one dll file and restart digiKam to try to reproduce the problem.

Gilles Caulier

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Nate Graham]

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

--- Comment #12 from Nate Graham  ---
Looks like the second style ("Applications:something.desktop") is indeed
expected now, and was introduced in https://phabricator.kde.org/D7561 and
https://phabricator.kde.org/D7562

I guess it caused some unexpected fallout.

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Michail Vourlakos]

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

--- Comment #11 from Michail Vourlakos  ---
(In reply to Nate Graham from comment #10)
> Great investigation, Michail! Maybe this was introduced by
> https://cgit.kde.org/plasma-desktop.git/commit/
> ?id=b293137ed955e076d72f47c86ea1a8539632bf5a
> 
> ?

maybe... Only the developer can answer this.

One more important thing I observed is that old launchers are in style:
file:///usr/share/applications/systemsettings.desktop

but all the new pinned launchers are in the form:
applications:systemsettings.desktop

I dont know what is the developer's intended behavior..
The first one or the latter one ?

If it is the latter then there should be and update mechanism between plasma
5.10 and 5.11 or the user should be informed that must readd all its launchers
from scratch.
If it is the first one then this is very important because 5.11.0 damages
launchers data.

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

[isoimagewriter] [Bug 385581] write image tells me there is data to be lost when disk is already empty

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|write image tells me there  |write image tells me there
   |is data to be lost when |is data to be lost when
   |there is not|disk is already empty
 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 385599] https links in notifications are opened as local filesystem paths

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[plasma-pa] [Bug 385602] Add option to show volume level in OSD

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
What do you mean by "the current volume level"? Like, in textual form (e.g.
"40%") as well as the visual bar?

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Vasyl Demin]

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

Vasyl Demin  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 385563] Regression: Taskbar pinned items change positions when opened

[Vasyl Demin]

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

Vasyl Demin  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 385619] Regression: Icons Only Taskbar pinned items change positions when opened.

[Vasyl Demin]

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

Vasyl Demin  changed:

   What|Removed |Added

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

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

[Akonadi] [Bug 376220] Crash in Akonadi::Monitor::mimeTypesMonitored

[ralph]

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

--- Comment #19 from ralph  ---
Is this fix present in Plasma 5.11?

Today I have received an automatic update to Plasma 5.11 and, at the end of the
installation, Plasma5 has crashed. As usual, the screen goes black and Plasma5
restarts.

Also, Plasma5 still crashes if I try to configure the SysTray.

If I try to configure the digital watch, the screen goes black and Plasma does
not restart anymore. I have to switch to a Virtual Terminal and run poweroff.

Some weeks ago I had sent a bug report (generated by DrKonqi):
https://bugs.kde.org/show_bug.cgi?id=384945
but you have marked it as duplicate of this bug.

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Nate Graham]

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

--- Comment #10 from Nate Graham  ---
Great investigation, Michail! Maybe this was introduced by
https://cgit.kde.org/plasma-desktop.git/commit/?id=b293137ed955e076d72f47c86ea1a8539632bf5a

?

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

[krusader] [Bug 384653] [zip kioslave] Journal spammed with “kf5.kio.core: error() called twice! Please fix the KIO slave.”

[Erik Quaeghebeur]

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

--- Comment #18 from Erik Quaeghebeur  ---
(In reply to Martin Kostolný from comment #17)
> […] is it possible that you have krarc
> binaries installed twice in different locations in your system? Can you
> check in running processes that while browsing archive with krarc protocol,
> only one kio_krarc.so process is running?
Only one instance of krarc on-disk and only one krarc process running.

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Michail Vourlakos]

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

--- Comment #9 from Michail Vourlakos  ---
I forgot to mention the functions that I think they are broken from TasksModel
because I copy pasted from another issue. The functions in question are:

launcherPosition, launcherActivities

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

[plasmashell] [Bug 385616] launcherPosition, launcherActivities are broken in libtaskmanager

[Michail Vourlakos]

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

--- Comment #2 from Michail Vourlakos  ---
of course, no prob

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Michail Vourlakos]

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

--- Comment #8 from Michail Vourlakos  ---
These two functions from TasksModel are also broken, what is happening is the
following.

Plasma possibly added new functionality in 5.11 for which a task's launcher url
is changed in something more generic. For systemsettings that would be,
applications:systemsettings.desktop . I found that this is happening for
launchers and windows in 5.11, I dont know for startups. Because of this
launcherPosition and launcherActivities return -1 and null accordingly. For
cases that instead of the above the desktop url is used e.g.
file:///usr/share/applications/systemsettings.desktop

then the functions I think they worked correctly. I used the following code on
the click event of a task in Latte in order to check the behavior.


console.log("POS  "+ tasksModel.launcherPosition(LauncherUrlWithoutIcon) +
" - " + tasksModel.launcherPosition(LauncherUrl) + " - "   
  + tasksModel.launcherActivities(LauncherUrl));

at all cases of launchers and windows the results where "POS  -1 - -1 -"

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

[frameworks-khtml] [Bug 377490] build failure with qt-5.9

[Pino Toscano]

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

--- Comment #6 from Pino Toscano  ---
Git commit 3def65075c09af4961cd399e8e78ed78cca72e65 by Pino Toscano, on behalf
of Wolfgang Bauer.
Committed on 11/10/2017 at 20:17.
Pushed by pino into branch '0.12'.

Fix build with Qt 5.9

Summary:
moc 5.9 errors out when building:
Error: Plugin Metadata file "" could not be opened: file to open is a directory

Same issue and fix as https://phabricator.kde.org/D5392 for khtml.

Test Plan: builds fine now with Qt 5.9.0rc and also earlier versions.

Reviewers: vriezen, pino

Reviewed By: pino

Subscribers: pino

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

M  +1-1src/kmplayer_part.h

https://commits.kde.org/kmplayer/3def65075c09af4961cd399e8e78ed78cca72e65

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

[plasmashell] [Bug 385616] launcherPosition, launcherActivities are broken in libtaskmanager

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---
Would you mind adding your comment and the result of any further investigations
to https://bugs.kde.org/show_bug.cgi?id=385594?

The bug will be fixed faster if we centralize information there. Thanks!

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

[digikam] [Bug 385630] New: Views Requiring Maps Takes ~30s to Launch

[bugzilla_noreply]

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

Bug ID: 385630
   Summary: Views Requiring Maps Takes ~30s to Launch
   Product: digikam
   Version: 5.8.0
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Geolocation
  Assignee: digikam-bugs-n...@kde.org
  Reporter: hardy.pub...@gmail.com
  Target Milestone: ---

Created attachment 108289
  --> https://bugs.kde.org/attachment.cgi?id=108289=edit
Unusable Map Dialogie

In the following use-cases, it takes approximately 30-35s for the map to appear
after the first launch. Thereafter there is no problem:

1. Clicking either Map in the fly-out menus.
2. Selecting a thumbnail then Ctrl_Shft+G.
3. If a map was visible when digiKam was shutdown previously, it then takes 30s
for main digiKam window to appear after splash screen disappears on next
relaunch.

See attached screenshot while waiting for map to load when starting Geo Editor.

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[Breeze] [Bug 385627] GTK2 scrollbars look weird

[Yannick]

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

Yannick  changed:

   What|Removed |Added

   Platform|Other   |Archlinux Packages

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Michail Vourlakos]

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

--- Comment #7 from Michail Vourlakos  ---
I played a bit with the icon-only plasma taskmanager by enforcing
separateLaunchers:false the experience was very broken when the user was
pinning launchers in different activities and windows in specific activities.
The launchers were changing positions without predictability and there was a
case in an activity that I ended up with two different kwrite launchers (one in
the beginning and one at the end) without having a kwrite window in that
activity...

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

[plasmashell] [Bug 385560] Crash when pressing the sandwich button in the panel on Wayland

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 385560] Crash when pressing the sandwich button in the panel on Wayland

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||matthewtresc...@gmail.com

--- Comment #1 from Nate Graham  ---
*** Bug 385629 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 385629] Opening and closing panel menu crashes Plasma on Wayland

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---


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

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

[frameworks-kirigami] [Bug 385547] Ugly scaling of text and icons in QML apps

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

Summary|ugly scaling of text and|Ugly scaling of text and
   |icons   |icons in QML apps

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

[frameworks-kirigami] [Bug 385547] ugly scaling of text and icons

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Target Milestone|--- |Not decided
   Assignee|plasma-b...@kde.org |notm...@gmail.com
Version|5.11.0  |unspecified
  Component|general |general
 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
Product|systemsettings  |frameworks-kirigami

--- Comment #4 from Nate Graham  ---
Moving to Kirigami since this seems more widespread than just System Settings,
and affects other Kirigami QML apps too.

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

[plasmashell] [Bug 385629] New: Opening and closing panel menu crashes Plasma on Wayland

[Matthew Trescott]

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

Bug ID: 385629
   Summary: Opening and closing panel menu crashes Plasma on
Wayland
   Product: plasmashell
   Version: 5.11.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: matthewtresc...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.0)

Qt Version: 5.9.2
Frameworks Version: 5.38.0
Operating System: Linux 4.13.5-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

I opened the panel settings using the hamburger menu at the bottom (formerly
the "cashew" thing). When I hit that button again or used the X button to close
the Panel settings, Plasma crashed.

- Custom settings of the application:

I have the weather widget on the desktop and I have two panels: one on the left
side with a Kicker menu at the top, followed by an icons-only task manager,
then a window minimizer widget and a digital clock. On the top menu I have a
global menu widget, a spacer, and the system tray and another digital clock.
Overall it's similar to the United theme, but using the Oxygen desktop style.

-

I hope the backtrace is useful---Dr. Konqi claims it is but I know it's usually
difficult to get good backtraces on ArchLinux.

The crash can be reproduced every time.

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

Thread 19 (Thread 0x7f4197fff700 (LWP 1330)):
[KCrash Handler]
#5  0x7f42a5fc7c81 in wl_proxy_create_wrapper () at
/usr/lib/libwayland-client.so.0
#6  0x7f4282ba07ea in  () at /usr/lib/libEGL_mesa.so.0
#7  0x7f4282b8d70f in  () at /usr/lib/libEGL_mesa.so.0
#8  0x7f42831d9722 in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#9  0x7f42831d7bce in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#10 0x7f42a81cdc89 in QOpenGLContext::makeCurrent(QSurface*) () at
/usr/lib/libQt5Gui.so.5
#11 0x7f42ab559976 in  () at /usr/lib/libQt5Quick.so.5
#12 0x7f42ab561636 in  () at /usr/lib/libQt5Quick.so.5
#13 0x7f42ab56084b in  () at /usr/lib/libQt5Quick.so.5
#14 0x7f42ab560c44 in  () at /usr/lib/libQt5Quick.so.5
#15 0x7f42a77c3fcb in  () at /usr/lib/libQt5Core.so.5
#16 0x7f42a697d08a in start_thread () at /usr/lib/libpthread.so.0
#17 0x7f42a70d024f in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f41ad71b700 (LWP 1329)):
#0  0x7f42a19c34ed in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f42a19c469b in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f42a19c4df6 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f42a19c4fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f42a7a02cf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f42a79a648b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f42a77bf27e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f42aa932bc9 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7f42a77c3fcb in  () at /usr/lib/libQt5Core.so.5
#9  0x7f42a697d08a in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f42a70d024f in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f41ae5ff700 (LWP 1328)):
#0  0x7f42a698338d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f42a77c545c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f42ab5607ba in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f42ab560c44 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f42a77c3fcb in  () at /usr/lib/libQt5Core.so.5
#5  0x7f42a697d08a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f42a70d024f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f41aeffd700 (LWP 1327)):
#0  0x7f42a698338d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f42a77c545c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f42ab5607ba in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f42ab560c44 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f42a77c3fcb in  () at /usr/lib/libQt5Core.so.5
#5  0x7f42a697d08a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f42a70d024f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f41af7fe700 (LWP 1326)):
#0  0x7f42a698338d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f42a77c545c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  

[Breeze] [Bug 385627] GTK2 scrollbars look weird

[Yannick]

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

--- Comment #2 from Yannick  ---
Actually the scrollbar goes a bit beyond its frame, hence the weird look.

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

[kate] [Bug 385628] New: [Wayland] Kate crash on close.

[Tony]

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

Bug ID: 385628
   Summary: [Wayland] Kate crash on close.
   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: jodr...@live.com
  Target Milestone: ---

Application: kate (17.11.70)

Qt Version: 5.9.2
Frameworks Version: 5.39.0
Operating System: Linux 4.13.5-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

I had open /etc/resolv.conf and a back up of it, i made no changes to either
file. I did not run kate as root.
Crash pop as soon as i close kate.

The crash can be reproduced sometimes.

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

Thread 2 (Thread 0x7f0d4b832700 (LWP 7218)):
#0  0x7f0d5df14808 in read () from /lib64/libc.so.6
#1  0x7f0d5815d3c0 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f0d58118c2b in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f0d581190f0 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f0d5811925c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f0d5e84825b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f0d5e7f073a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f0d5e6201fa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f0d5eccaa45 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#9  0x7f0d5e624c0e in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7f0d59c42558 in start_thread () from /lib64/libpthread.so.0
#11 0x7f0d5df2345f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f0d63604900 (LWP 7217)):
[KCrash Handler]
#6  0x7f0d509c5099 in wl_map_insert_at (map=,
flags=flags@entry=0, i=, data=) at
src/wayland-util.c:249
#7  0x7f0d509c11ae in proxy_destroy (proxy=0x5558b92b2670) at
src/wayland-client.c:411
#8  wl_proxy_destroy (proxy=0x5558b92b2670) at src/wayland-client.c:442
#9  0x7f0d4ef7f6a7 in org_kde_plasma_window_destroy
(org_kde_plasma_window=0x5558b92b2670) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/build/src/client/wayland-plasma-window-management-client-protocol.h:634
#10 KWayland::Client::WaylandPointer::release (this=0x5558b91b5090,
this=0x5558b91b5090) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/wayland_pointer_p.h:53
#11 KWayland::Client::PlasmaWindow::release (this=this@entry=0x5558b88b0980) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/plasmawindowmanagement.cpp:745
#12 0x7f0d4ef7f6ca in KWayland::Client::PlasmaWindow::~PlasmaWindow
(this=0x5558b88b0980, __in_chrg=) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/plasmawindowmanagement.cpp:735
#13 0x7f0d4ef7f7c9 in KWayland::Client::PlasmaWindow::~PlasmaWindow
(this=0x5558b88b0980, __in_chrg=) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/plasmawindowmanagement.cpp:736
#14 0x7f0d5e81d40b in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#15 0x7f0d5e82676b in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#16 0x7f0d4ef7fd99 in
KWayland::Client::PlasmaWindowManagement::~PlasmaWindowManagement
(this=0x5558b91809c0, __in_chrg=) at
/usr/src/debug/kwayland-5.39.0git.20171010T183056~daec657/src/client/plasmawindowmanagement.cpp:252
#17 0x7f0d5e81d40b in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5
#18 0x7f0d5e82676b in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#19 0x7f0d419e8a93 in WaylandIntegration::~WaylandIntegration
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.11.90git.20170914T114718~1d8054b/src/windowsystem/waylandintegration.cpp:54
#20 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.11.90git.20170914T114718~1d8054b/src/windowsystem/waylandintegration.cpp:40
#21 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder
(this=, __in_chrg=) at
/usr/src/debug/kwayland-integration-5.11.90git.20170914T114718~1d8054b/src/windowsystem/waylandintegration.cpp:46
#22 0x7f0d5de63ce8 in __run_exit_handlers () from /lib64/libc.so.6
#23 0x7f0d5de63d3a in exit () from /lib64/libc.so.6
#24 0x7f0d5de4bf51 in __libc_start_main () from /lib64/libc.so.6
#25 0x5558b669925a in _start ()

Possible duplicates by query: bug 379728, bug 377962.

Reported using DrKonqi

-- 
You are 

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

   Severity|normal  |major
 CC||pointedst...@zoho.com

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pip@gmx.com

--- Comment #6 from Nate Graham  ---
*** Bug 385619 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 385619] Regression: Icons Only Taskbar pinned items change positions when opened.

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Nate Graham  ---


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

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

[Breeze] [Bug 385627] GTK2 scrollbars look weird

[Yannick]

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

--- Comment #1 from Yannick  ---
Created attachment 108288
  --> https://bugs.kde.org/attachment.cgi?id=108288=edit
scrollbar highlighted by mouse cursor

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

[gwenview] [Bug 385622] Please add Back Button to Gwenview

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[systemsettings] [Bug 385621] Settings blurry with HiDPI scaling

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||pointedst...@zoho.com

--- Comment #1 from Nate Graham  ---


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

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

[Breeze] [Bug 385627] New: GTK2 scrollbars look weird

[Yannick]

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

Bug ID: 385627
   Summary: GTK2 scrollbars look weird
   Product: Breeze
   Version: 5.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: gtk theme
  Assignee: scionicspec...@gmail.com
  Reporter: leguen.yann...@gmail.com
  Target Milestone: ---

Created attachment 108287
  --> https://bugs.kde.org/attachment.cgi?id=108287=edit
scrollbar at the bottom extremity

After upgrading to Plasma 5.11.0, I noticed weird scrollbars on GTK2 apps using
the breeze-gtk theme.

When a scrollbar is at the very top or bottom of a window, it looks like you
can still scroll a bit. Hovering the mouse cursor over it displays it
correctly, though :)

See screenshots in attachment.

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

[systemsettings] [Bug 385547] ugly scaling of text and icons

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||zachho...@gmail.com

--- Comment #3 from Nate Graham  ---
*** Bug 385621 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||joaomiguelb...@gmail.com

--- Comment #5 from Nate Graham  ---
*** Bug 385618 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 385618] Lauching a pinned application moves the pinned icon to the front of all other pinned applicatons

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Nate Graham  ---


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

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

[plasmashell] [Bug 385563] Regression: Taskbar pinned items change positions when opened

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 Resolution|FIXED   |DUPLICATE
 CC||pointedst...@zoho.com

--- Comment #7 from Nate Graham  ---
This definitely seems like a regression and not a case of misconfiguration or
user error.

Marking this as a duplicate of 385594 since there's more technical information
in that bug.

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

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

[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||golu3...@gmail.com

--- Comment #4 from Nate Graham  ---
*** Bug 385563 has been marked as a duplicate of this bug. ***

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

[rust-qt-binding-generator] [Bug 385341] Support member functions in the interface

[Pearce Keesling]

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

--- Comment #2 from Pearce Keesling  ---
Something else I was wondering. Is there a particular reason that we're
requiring argument names? As far as I can tell there is never really a place
that those are needed from a developer's perspective. The Rust-C interface
doesn't care about argument names so we could just call it arg1, arg2, etc. as
long as we get the types and order correct.

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

[rust-qt-binding-generator] [Bug 385341] Support member functions in the interface

[Pearce Keesling]

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

--- Comment #1 from Pearce Keesling  ---
I've got most of the this solved. The only thing that's left as far as I can
tell is the interface going back from rust String to a QString. I'll need to
take a look at that when I get the time. I was able to make use of this in the
qml_todo example I wrote. The only problem I'm having with that is that I can't
find any way to batch together all of the removals. QT seems to require that
you do a begin_removal before each set of consecutive removals. There doesn't
seem to be a way to start a removal then remove items 1, 3, 5 or something like
that.

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

[systemsettings] [Bug 385609] Switching from 3 column to 2 column view should show submodules in left column

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[Discover] [Bug 385587] tasks view not too compatible with local package install

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[Spectacle] [Bug 385559] "Copy to Clibboard" CLI option for spectacle

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||pointedst...@zoho.com

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

[kwin] [Bug 385626] New: KWin crashed when Alt+Tab-ing through open windows

[Dennis Schridde]

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

Bug ID: 385626
   Summary: KWin crashed when Alt+Tab-ing through open windows
   Product: kwin
   Version: 5.10.5
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: devuran...@gmx.net
  Target Milestone: ---

Application: kwin_x11 (5.10.5)

Qt Version: 5.9.2
Frameworks Version: 5.38.0
Operating System: Linux 4.13.5-gentoo x86_64
Distribution: "Gentoo Base System release 2.4.1"

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

I was Alt+Tab-ing through the open windows, when KWin crashed.

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

Thread 14 (Thread 0x7f17519da700 (LWP 12411)):
#0  0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f174279b7f3 in cnd_wait (mtx=0x2a72ab8, cond=0x2a72ae0) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x28b1910) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/src/util/u_queue.c:158
#3  0x7f174279b717 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:87
#4  0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0
#5  0x7f177132160f in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f172fe6c700 (LWP 12392)):
#0  0x7f17713165c3 in ppoll () from /lib64/libc.so.6
#1  0x7f176f244419 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at
/usr/include/bits/poll2.h:77
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f1724000c38) at
kernel/qcore_unix.cpp:81
#3  qt_safe_poll (fds=0x7f1724000c38, nfds=nfds@entry=1,
timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:102
#4  0x7f176f245663 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500
#5  0x7f176f1f866a in QEventLoop::exec (this=this@entry=0x7f172fe6bd50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f176f05c3bb in QThread::exec (this=this@entry=0x27e4150) at
thread/qthread.cpp:515
#7  0x7f1769eb3675 in QQmlThreadPrivate::run (this=0x27e4150) at
qml/ftw/qqmlthread.cpp:147
#8  0x7f176f0605e0 in QThreadPrivate::start (arg=0x27e4150) at
thread/qthread_unix.cpp:368
#9  0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0
#10 0x7f177132160f in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f172f635700 (LWP 5779)):
#0  0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f176e366634 in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f176e366679 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0
#4  0x7f177132160f in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f173066d700 (LWP 5749)):
#0  0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f174279b7f3 in cnd_wait (mtx=0x25bb758, cond=0x25bb780) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x2464d20) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/src/util/u_queue.c:158
#3  0x7f174279b717 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:87
#4  0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0
#5  0x7f177132160f in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f1730e6e700 (LWP 5748)):
#0  0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f174279b7f3 in cnd_wait (mtx=0x2460710, cond=0x2460738) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x249f350) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/src/util/u_queue.c:158
#3  0x7f174279b717 in impl_thrd_routine (p=) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:87
#4  0x7f176afe2617 in start_thread () from /lib64/libpthread.so.0
#5  0x7f177132160f in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f173166f700 (LWP 5747)):
#0  0x7f176afe9466 in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f174279b7f3 in cnd_wait (mtx=0x2460710, cond=0x2460738) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/include/c11/threads_posix.h:159
#2  util_queue_thread_func (input=input@entry=0x247e640) at
/var/tmp/portage/media-libs/mesa-17.2.2/work/mesa-17.2.2/src/util/u_queue.c:158
#3  0x7f174279b717 in impl_thrd_routine