[valgrind] [Bug 383811] Support macOS High Sierra (10.13)

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=383811

suhrspama...@gmail.com changed:

   What|Removed |Added

 CC||suhrspama...@gmail.com

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

[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore

2018-10-22 Thread Marc Cousin
https://bugs.kde.org/show_bug.cgi?id=395711

Marc Cousin  changed:

   What|Removed |Added

 CC||cousinm...@gmail.com

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

[latte-dock] [Bug 400180] New: Java apps cannot be pinned

2018-10-22 Thread Denis Nelubin
https://bugs.kde.org/show_bug.cgi?id=400180

Bug ID: 400180
   Summary: Java apps cannot be pinned
   Product: latte-dock
   Version: 0.8.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: mvourla...@gmail.com
  Reporter: dnelu...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Run an Java application in any way: "java -jar jarfile.jar" in console,
shellscript with "java -jar jarfile.jar" in it, .desktop file with "Exec=java
-jar jarfile.jar" in ~/.local/share/applications launched from the main menu.
2. Pin the application in Latte dock.
3. Close the application.
4. Try to start it by clickin on the pinned icon in the dock.

OBSERVED RESULT
The application is not started.
The ~/.config/latte/*.layout.latte file contains in
[Containments][38][Applets][43][Configuration][General] section, parameter
launchers59 the string: "file:///usr/bin/java?iconData=..." which is not the
correct command line for the application.

EXPECTED RESULT
The application is started with the correct command line used with the initial
run (including shell script or desktop file).

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.0
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 396011] Dragging icons doesn't work most of the time

2018-10-22 Thread Eike Hein
https://bugs.kde.org/show_bug.cgi?id=396011

--- Comment #13 from Eike Hein  ---
Unfortunately I've never encountered this problem on any of my systems. Qt
5.12, though.

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

[krita] [Bug 400179] Brush stroke mirror copy has rectangular "hole" artifacts

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=400179

hitjim+...@gmail.com changed:

   What|Removed |Added

 CC||hitjim+...@gmail.com

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

[plasmashell] [Bug 400158] Cannot reorder tasks after upgrading to Plasma 5.14.1

2018-10-22 Thread Eike Hein
https://bugs.kde.org/show_bug.cgi?id=400158

--- Comment #1 from Eike Hein  ---
I can't reproduce that. Anyone else?

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

[krita] [Bug 400179] New: Brush stroke mirror copy has rectangular "hole" artifacts

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=400179

Bug ID: 400179
   Summary: Brush stroke mirror copy has rectangular "hole"
artifacts
   Product: krita
   Version: 4.1.5
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: hitjim+...@gmail.com
  Target Milestone: ---

Created attachment 115841
  --> https://bugs.kde.org/attachment.cgi?id=115841=edit
rectangular hole artifacts in mirrored brush strokes

SUMMARY
Quick, high-thickness strokes appear to get rectangular "hole" artifacts
erratically.  I've exported to PNG to verify it's not just an editor view
artifact.  These holes appear in the PNG as well.

I'm using a new laptop with 1060 maxq video card.  Dell G7 16GB RAM.  Windows
10 Home.  I've updated NVidia drivers.  I've tried turning OpenGL off, and a
few different options in that same view... but not all of them.

STEPS TO REPRODUCE
1. new document 3508x2480
2. select a basic-5-size brush
3. Make numerous strokes of varying width, usually quickly, using varying
pressure on tablet

OBSERVED RESULT
The painted line will draw correctly, as will the mirror preview on the left -
however after releasing the stylus, the line may exhibit rectangular "hole"
artifacts.  I've verified that this happens regardless of which side of the
mirror I make my marks on.

EXPECTED RESULT
I would expect to not be missing rectangular chunks of the mirrored marks


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Krita
  Version: 4.1.5

Qt
  Version (compiled): 5.9.3
  Version (loaded): 5.9.3

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.17134
  Pretty Productname: Windows 10 (10.0)
  Product Type: windows
  Product Version: 10

OpenGL Info
  **OpenGL not initialized**

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

[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly

2018-10-22 Thread Andras
https://bugs.kde.org/show_bug.cgi?id=400178

Andras  changed:

   What|Removed |Added

 CC||andrasszerencs...@gmail.com

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

[kwin] [Bug 400135] Hot Corners Deactivate on Second Try

2018-10-22 Thread Andres Betts
https://bugs.kde.org/show_bug.cgi?id=400135

--- Comment #7 from Andres Betts  ---
Thanks for your answer. I think we should always keep an open mind to think
differently. To "not" question decisions made 10 years ago is something I will
not do. Is there room to remove that delay?

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

[kdeconnect] [Bug 400178] New: KDEConnect fails to open remote phone directory as it says protocol died unexpectedly

2018-10-22 Thread Andras
https://bugs.kde.org/show_bug.cgi?id=400178

Bug ID: 400178
   Summary: KDEConnect fails to open remote phone directory as it
says protocol died unexpectedly
   Product: kdeconnect
   Version: 1.3.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: andrasszerencs...@gmail.com
  Target Milestone: ---

SUMMARY
KDEConnect fails to open remote phone directory as it says protocol died
unexpectedly


STEPS TO REPRODUCE
1. Turn on Kdeconnect on PC and on Android too
2. Pair the two devices
3. In Dolphin, click on the name of the phone created by Kdeconnect

OBSERVED RESULT
The process for the kdeconnect://... protocol died unexpectedly

EXPECTED RESULT
Open given remote phone directory

SOFTWARE VERSIONS
(available in About System)
KDE neon 5.14
KDE Plasma Version: 5.14.1
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2
Kernel Version: 4.15.0-38-generic
OS Type: 64-bit

ADDITIONAL INFORMATION
Hi, I have this issue for a while now on Ubuntu 18.04 based KDE neon 5.14.1, QT
Version 5.11.2, Kernel 4.15.0-38, kdeconnect 1.3.1-0
I try to access Kdeconnect through Dolphin what says:
The process for the kdeconnect://... protocol died unexpectedly
Anybody experienced similar issue? What could be the problem?
It seems everything else functional, I mean I get the notification and remote
input, etc, the phone name appears in Dolphin, only directory access won't
work.
Firewall ports 1714-1764 udp tcp implemented.
Tried several workaround, full reinstall, erase related folders, on android
too.
I have to note, very rarely it come alive, for example when I installed an
other Android app for ftp and connected to it with Dolphin. I was able the
access the phone by rightclicking on the phone name given by kdeconnect (not
the one connected with other app obviously) / edit and click on open file
dialog and examining finished pop up message appeard. It worked only once. 
It's issue on two different desktop pc with same KDE neon OS and with two
different phone.
Also I found this in journalctl for example:
kdeconnect.plugin.notification: Not found noti by internal Id:
"0|com.samsung.tmowfc.wfccontroller|2131165186|null|1000"

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

[kwin] [Bug 400135] Hot Corners Deactivate on Second Try

2018-10-22 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=400135

--- Comment #6 from Martin Flöser  ---
(In reply to Andres Betts from comment #5)
> Maybe that is something that can be addressed. What is the logic behind the
> delay in activation/deactivation?

Without, a fast movement wuld make it activate/deactivate several times and it
becomes almost impossible to trigger the edge.

Please don't question everything we did. These are things we worked 10 years
ago  to make them work well.

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

[kwin] [Bug 400171] QuickTiled Windows Should Not be Shadowed

2018-10-22 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=400171

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #1 from Martin Flöser  ---
This is fully under control of the window decoration.

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

[plasmashell] [Bug 396011] Dragging icons doesn't work most of the time

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=396011

--- Comment #12 from tr...@yandex.com ---
(In reply to trmdi from comment #11)
> (In reply to Patrick Silva from comment #9)
> > upstream bug was closed because requested info was not provided. :(
> 
> I can not reproduce the bug on that example.
> But the bug still happens on Plasma 5.14.0 / openSUSE Tumbleweed

This means it's a Plasma bug ?

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

[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C

2018-10-22 Thread Diane Trout
https://bugs.kde.org/show_bug.cgi?id=399590

--- Comment #10 from Diane Trout  ---
Created attachment 115840
  --> https://bugs.kde.org/attachment.cgi?id=115840=edit
log of plugging in external dock after rebooting

It didn't detect the monitor connected to the external dock either.

Any suggestions for udevadm info commands you'd like?

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

[plasmashell] [Bug 396011] Dragging icons doesn't work most of the time

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=396011

tr...@yandex.com changed:

   What|Removed |Added

Version|5.13.2  |5.14.0
   Platform|Gentoo Packages |openSUSE RPMs

--- Comment #11 from tr...@yandex.com ---
(In reply to Patrick Silva from comment #9)
> upstream bug was closed because requested info was not provided. :(

I can not reproduce the bug on that example.
But the bug still happens on Plasma 5.14.0 / openSUSE Tumbleweed

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

[kwin] [Bug 400135] Hot Corners Deactivate on Second Try

2018-10-22 Thread Andres Betts
https://bugs.kde.org/show_bug.cgi?id=400135

--- Comment #5 from Andres Betts  ---
Maybe that is something that can be addressed. What is the logic behind the
delay in activation/deactivation?

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

[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C

2018-10-22 Thread Diane Trout
https://bugs.kde.org/show_bug.cgi?id=399590

--- Comment #9 from Diane Trout  ---
I haven't used those before, udev-browse isn't available for debian, so I went
with udevadm monitor. Hope that's useful.

I started udevadm monitor | tee udev.monitor.log in a tmux session so even if
plasma locked up I should still get some log messages.

I started it while plugged into the smaller USB C dongle connected to 1600x1200
monitor over VGA, and then I suspend the computer. I took it home and plugged
it into a USB C dock and opened the computer.

I looked at twitter and watched a bit of a video, and then killed udevadm
monitor. There was only one display listed in Displays and the scale for the
laptop display had defaulted to 1x instead of 2x.

See log of udevadm monitor after resuming...

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

[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C

2018-10-22 Thread Diane Trout
https://bugs.kde.org/show_bug.cgi?id=399590

--- Comment #8 from Diane Trout  ---
Created attachment 115839
  --> https://bugs.kde.org/attachment.cgi?id=115839=edit
log of udevadm monitor after resuming connected to a different USB C dock

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

[okular] [Bug 400089] Previously closed PDF's open at startup, accompanied by an error message

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=400089

--- Comment #4 from dustin.fens...@gmail.com ---
(In reply to Tobias Deiminger from comment #3)
> (In reply to dustin.fenster from comment #2)
> > they are under the section [Session: saved at previous
> > logout]--maybe that is what you meant.
> No, I guessed "saved by user", because you initially wrote okular documents
> "were all closed after use". If okular had actually been closed when you
> logged out, okular can't appear in "saved at previous logout". That's at
> least how I understand the XSMP protocol and ksmserver. We can discuss
> details in the mailing list if you want.

Hmm. Don't know what happened, then.

> 
> But you also write "now open upon each restart". That's wired. Can you check
> the timestamp of ksmserverrc for when it was last modified, and reconsider
> if that timestamp matches with the last time you logged out/shutdown? On
> logout ksmserver should update the "saved at previous logout" section, and
> possibly existing okular entries should be vanished (unless okular is still
> open).

I don't see a timestamp.  Also, there have been several restarts and okular is
definitely not open.

> 
> > There are also some lines such as:
> > discardCommand14[$e]=rm,$HOME/.config/session/
> > okular_102b23022f728500015379368860013880083_1538059437_972466.  Just
> > pointing this out because it references okular, don't know if that's normal.
> That's fine, ksmserver needs the entries to clean up old sessions.
> 
> > > Do you still get "Could not open file" this way?
> > 
> > Doing this does not produce the error.
> Ok, sounds like your cloud service is also started during KDE login, and the
> local storage is not yet available at the early stage when ksmserver
> restores application sessions. Might that be?

Could be.  

> 
> > There are several with one of two url's, which is odd because 6 or 7 files
> > are opening
> Sorry, no idea about that.
> 
> > Should I simply delete all of the
> > "restartCommand13=/usr/bin/okular,-session,
> > 102b23022f728500015379368600013880082_1538059437_972580", etc. lines?
> The cleanest way is probably to backup ~/.config/ksmserverrc and
> $HOME/.config/session/*, then remove all those files, and restart. You
> should start with a "clean" session again.

I have deleted the lines and everything is good.  I also start with a new
session now at login.  
Thanks for your help.

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

[digikam] [Bug 400139] Titles are not exported anymore on google photos

2018-10-22 Thread Mat
https://bugs.kde.org/show_bug.cgi?id=400139

--- Comment #2 from Mat  ---
Hi Maik,

I was thinking it was a regression because it was working on 5.9.
If this is a coincidence, you can close the ticket.

Kind regards

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

[krita] [Bug 400177] New: Scale to New Size Doesn't Do Arithmetic Right

2018-10-22 Thread Kenneth Evans
https://bugs.kde.org/show_bug.cgi?id=400177

Bug ID: 400177
   Summary: Scale to New Size Doesn't Do Arithmetic Right
   Product: krita
   Version: 4.1.5
  Platform: MS Windows
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Resize/Scale Image/Layer
  Assignee: krita-bugs-n...@kde.org
  Reporter: k...@kenevans.net
  Target Milestone: ---

Created attachment 115838
  --> https://bugs.kde.org/attachment.cgi?id=115838=edit
Screenshot of Scale to New Size Dialog

I resized an image to 18" x 12" at 300 dpi.  It didn't come out as 5400 x 3600,
rather 5405 x 3602.  I then tried sizing it to 5400 x 3600, and the size was
17.99" x 11.99".  There seems to be an error somewhere.  Even if done in float,
it should have more precision than this.


STEPS TO REPRODUCE
1. With an existing image, attempt to resize it to 18" x 12" @300 dpi.
2. Just look at the dialog.  (You don't have to actually do it.)
3. 

OBSERVED RESULT
5405 x 3602 (or 17.99 x 11.99)

EXPECTED RESULT
5400 x 3600 (or 18.00 x 12.00)

Image attached of the setting 5400 x 3600 case.

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

[plasmashell] [Bug 400176] New: Panel freezes and reverts to an arbitary state when compositing is disabled

2018-10-22 Thread Carson Black
https://bugs.kde.org/show_bug.cgi?id=400176

Bug ID: 400176
   Summary: Panel freezes and reverts to an arbitary state when
compositing is disabled
   Product: plasmashell
   Version: 5.14.0
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: uhh...@gmail.com
  Target Milestone: 1.0

Created attachment 115837
  --> https://bugs.kde.org/attachment.cgi?id=115837=edit
a difference showing the panel before and after disabling compositing w/out any
changes in open applications

SUMMARY
The panels graphically freeze whenever compositing is turned off. No
exceptions, all widgets don't update their look, including the window list
plasmoids. It still works as behaved, except the graphical freezing makes it
near impossible to identify where everything is. This does not apply to
pop-outs like launchers and the color picker plasmoid. Also, the panel doesn't
just freeze, it reverts to a seemingly arbitrary state.

STEPS TO REPRODUCE
1. Disable compositing by pressing Alt-Shift-F12 or launching an application
that disables it.
2. The panel reverts to an arbitrary state and freezes graphically.

OBSERVED RESULT
Panel reverts to a seemingly arbitrary state.

EXPECTED RESULT
Panel has graphical effects disabled but everything still works.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.0
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
The graphics card is a Nvidia GT1030 with propietary drivers at version
390.87-10.1.

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

[ksysguard] [Bug 400175] New: CPU History and Memory History show extreme values after some time

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=400175

Bug ID: 400175
   Summary: CPU History and Memory History show extreme values
after some time
   Product: ksysguard
   Version: 5.8.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: sjx2...@hotmail.com
  Target Milestone: ---

SUMMARY
After running System Monitor (ksysguard) for several minutes, the value for the
eighth thread becomes 3e+06% and its line in the graph goes to the top. Also
the value for memory usage drops to zero. Closing the application and reopening
temporarily corrects the problem.

STEPS TO REPRODUCE
1. Open ksysguard (system monitor)
2. Leave application running
3. 

OBSERVED RESULT
Unreasonable values for some system metrics

EXPECTED RESULT
Accurate values for all system metrics

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.8.7
KDE Frameworks Version: 5.32.0
Qt Version: 5.6.2

ADDITIONAL INFORMATION

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

[Spectacle] [Bug 351963] Missing Comment in desktop file

2018-10-22 Thread Alex
https://bugs.kde.org/show_bug.cgi?id=351963

Alex  changed:

   What|Removed |Added

   Assignee|ase...@kde.org  |m...@baloneygeek.com
 Ever confirmed|0   |1
 Resolution|UNMAINTAINED|---
  Component|general |General
Product|ksnapshot   |Spectacle
 Status|RESOLVED|REOPENED

--- Comment #2 from Alex  ---
Missing Comment in desktop file for Spectacle too.

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

[kdeconnect] [Bug 400174] New: let's generate a manpage for kdeconnect-cli!

2018-10-22 Thread Nicholas D Steeves
https://bugs.kde.org/show_bug.cgi?id=400174

Bug ID: 400174
   Summary: let's generate a manpage for kdeconnect-cli!
   Product: kdeconnect
   Version: 1.3.1
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: nstee...@gmail.com
  Target Milestone: ---

Hi Albert, Nico, and possibly other maintainers,

Debian has an English language manpage for kdeconnect-cli in troff format:

 
https://salsa.debian.org/qt-kde-team/extras/kdeconnect/blob/master/debian/kdeconnect-cli.1

This last summer I noticed that it was four years out of date

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900710

I really don't like working with troff, internationalisation is obviously
non-existent, and updates are currently a manual affair.  It would also be
really nice if they could be generated from existing strings and PO files as
part of the release process!  Would you please point me documentation or put me
in touch with someone who would know how KDE/Plasma Desktop applications
conventionally handle internationalised manpages?

Warm regards,
Nicholas

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

[ark] [Bug 399949] Can't extract from files with extension ".zip.NNN"

2018-10-22 Thread Rafael Linux User
https://bugs.kde.org/show_bug.cgi?id=399949

Rafael Linux User  changed:

   What|Removed |Added

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

--- Comment #2 from Rafael Linux User  ---
I followed your instructions and it worked. But I have a suggestion: If using
that plugin doesn't work, why is not disabled by default? That's to say, I
think that this issue will happen to all users managing this kind of files and
they will find same problem. Thinking on myself, I should remember to disable
this plugin each time I install a new version of my s.o. ... That's my opinion
as user.

Thank you!

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

[plasmashell] [Bug 396011] Dragging icons doesn't work most of the time

2018-10-22 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=396011

Nate Graham  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|UPSTREAM|---
 Ever confirmed|0   |1

--- Comment #10 from Nate Graham  ---
Eike, any chance you could take a look here when you get some breathing room?

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

[plasmashell] [Bug 399216] No desktop icons, background image on primary screen (DP & HDMI combo)

2018-10-22 Thread Serhiy Zahoriya
https://bugs.kde.org/show_bug.cgi?id=399216

Serhiy Zahoriya  changed:

   What|Removed |Added

 CC||serhiy@gmail.com

--- Comment #1 from Serhiy Zahoriya  ---
Looks like at least related to https://bugs.kde.org/show_bug.cgi?id=391531 if
not a duplicate

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

[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling

2018-10-22 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=373232

--- Comment #63 from Nate Graham  ---
That's correct, there is no *official* support. However KScreen allows you to
set a fractional scale factor on X11, and quite a few people do so for what I
consider to be legitimate reasons (e.g some 4k screens are 13 inches, others
are 27 inches).

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

[plasmashell] [Bug 391531] Desktop wallpaper is black and I cannot interact with the desktop

2018-10-22 Thread Serhiy Zahoriya
https://bugs.kde.org/show_bug.cgi?id=391531

Serhiy Zahoriya  changed:

   What|Removed |Added

 CC||serhiy@gmail.com

--- Comment #5 from Serhiy Zahoriya  ---
I had similar behaviour several times, but not every time on login. In my case
external display is bigger than the LVDS one and with the latter being disabled
I see black part only on the left of a larger screen with the desktop being
moved to the right and only part of it visible.

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

[akregator] [Bug 186946] hacker news feed cannot be loaded

2018-10-22 Thread Adnilson Dingao
https://bugs.kde.org/show_bug.cgi?id=186946

Adnilson Dingao  changed:

   What|Removed |Added

 CC||dingaopaica...@gmail.com

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

[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it

2018-10-22 Thread Serhiy Zahoriya
https://bugs.kde.org/show_bug.cgi?id=364915

Serhiy Zahoriya  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #11 from Serhiy Zahoriya  ---
I've seen this happening too, changing status to Confirmed.

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

[konqueror] [Bug 213606] Segfault opening the url "http://www.androidiani.com/forum/android-caf/5001-maemo-vs-android.html"

2018-10-22 Thread Adnilson Dingao
https://bugs.kde.org/show_bug.cgi?id=213606

Adnilson Dingao  changed:

   What|Removed |Added

 CC||dingaopaica...@gmail.com

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

[frameworks-kholidays] [Bug 400165] Allerheiligen (1. Nov) is not marked as a holiday for de-NW

2018-10-22 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=400165

--- Comment #6 from Christoph Feck  ---
Restarting plasmashell indeed fixed it. Interestingly, other German holidays
(e.g. 3. Okt, Tag der Deutschen Einheit) were displayed, but Allerheiligen was
missing. Now I see it.

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

[kscreenlocker] [Bug 364915] After a suspend/resume cycle, desktop is shown for a moment before locker hides it

2018-10-22 Thread Serhiy Zahoriya
https://bugs.kde.org/show_bug.cgi?id=364915

Serhiy Zahoriya  changed:

   What|Removed |Added

 CC||serhiy@gmail.com

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

[frameworks-kirigami] [Bug 399959] Could use a separator element that's just 18px of whitespace, not a line

2018-10-22 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=399959

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from Nate Graham  ---
Talked to Marco and found out this is not actually needed.

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

[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly

2018-10-22 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=399430

Patrick Silva  changed:

   What|Removed |Added

 CC||lcswill...@gmail.com

--- Comment #7 from Patrick Silva  ---
*** Bug 400172 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 400172] The drag-n-drop in Dolphin places is not working

2018-10-22 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=400172

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com
 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Patrick Silva  ---


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

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

[kde] [Bug 400173] New: Upon wake from sleep external monitors are no longer detected.

2018-10-22 Thread James
https://bugs.kde.org/show_bug.cgi?id=400173

Bug ID: 400173
   Summary: Upon wake from sleep external monitors are no longer
detected.
   Product: kde
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: schlinkh...@gmail.com
  Target Milestone: ---

SUMMARY

When waking from sleep external monitor is not recognized.
Using thunderbolt to display port connector.  Must reboot machine for monitor
to become available.  External display is not recognized at any time if not
plugged in before boot.


STEPS TO REPRODUCE
1. Let computer go to sleep.
2. 
3. 

OBSERVED RESULT
Computer wakes only laptop screen.  External monitor is not recognized until
reboot.

EXPECTED RESULT
Wake computer and all screens become available.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
Laptop: MacBook Pro 11,5 (Mid 2015) 
Monitor make and model: HP 27" Z27X 
Connection: Thunderbolt to Display Port  (Laptop <-> Monitor)

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

[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=399590

--- Comment #7 from David Edmundson  ---
>From kwin's POV we monitor udev for events from the "drm" subsystem

Can you plug it in and using udevadm/udev-browse find some details for your DRM
device.

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

[kwin] [Bug 399499] KWin Seg Fault on Startup

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=399499

David Edmundson  changed:

   What|Removed |Added

 CC||chadmcla...@gmail.com

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

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

[kwin] [Bug 400016] Resume from Suspend crashes KWIN

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=400016

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #6 from David Edmundson  ---


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

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

[kwin] [Bug 399499] KWin Seg Fault on Startup

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=399499

David Edmundson  changed:

   What|Removed |Added

 CC||123gop...@mail.ru

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

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

[kwin] [Bug 398860] Plasma not responding

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=398860

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||k...@davidedmundson.co.uk

--- Comment #1 from David Edmundson  ---


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

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

[kwin] [Bug 400016] Resume from Suspend crashes KWIN

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=400016

David Edmundson  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 CC||k...@davidedmundson.co.uk
 Resolution|BACKTRACE   |---

--- Comment #5 from David Edmundson  ---
thanks

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

[kwin] [Bug 398114] Crash in libepoxy after suspending compositing

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=398114

--- Comment #7 from David Edmundson  ---
Extra twist:
 - with my own built libepoxy (At the same version as my system!) it doesn't
crash. Changing from system to my version without recompiling kwin will
trigger/fix the crash.

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

[kwin] [Bug 400016] Resume from Suspend crashes KWIN

2018-10-22 Thread Chad Clancy
https://bugs.kde.org/show_bug.cgi?id=400016

--- Comment #4 from Chad Clancy  ---
(In reply to Chad Clancy from comment #2)
> Sorry for the delay, I hope I've done this right. I installed kwin-debug and
> resumed from suspend again today. I'll attach the debug report.

kwin-dbg, sorry.

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

[kwin] [Bug 400016] Resume from Suspend crashes KWIN

2018-10-22 Thread Chad Clancy
https://bugs.kde.org/show_bug.cgi?id=400016

--- Comment #3 from Chad Clancy  ---
Created attachment 115836
  --> https://bugs.kde.org/attachment.cgi?id=115836=edit
Crash report for kwin suspend crash

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

[kwin] [Bug 400016] Resume from Suspend crashes KWIN

2018-10-22 Thread Chad Clancy
https://bugs.kde.org/show_bug.cgi?id=400016

--- Comment #2 from Chad Clancy  ---
Sorry for the delay, I hope I've done this right. I installed kwin-debug and
resumed from suspend again today. I'll attach the debug report.

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

[frameworks-kholidays] [Bug 400165] Allerheiligen (1. Nov) is not marked as a holiday for de-NW

2018-10-22 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=400165

--- Comment #5 from Christophe Giboudeaux  ---
and last detail, after disabling / re-enabling the holidays plugin, the public
days are localized (I tried adding the de-nw_de ones to test and
'Allerheiligen' is displayed)

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

[frameworks-kholidays] [Bug 400165] Allerheiligen (1. Nov) is not marked as a holiday for de-NW

2018-10-22 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=400165

--- Comment #4 from Christophe Giboudeaux  ---
even unchecking / checking again the box has no effect. I have to uncheck/check
the 'holidays' and 'astronomical events' boxes on the calendar options tab

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

[kwin] [Bug 393167] [Wayland] Child toplevel window placement doesn't work

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=393167

David Edmundson  changed:

   What|Removed |Added

  Flags||ReviewRequest+

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

[frameworks-kholidays] [Bug 400165] Allerheiligen (1. Nov) is not marked as a holiday for de-NW

2018-10-22 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=400165

--- Comment #3 from Christophe Giboudeaux  ---
and if I restart plasmashell (kquitapp5 plasmashell && plasmashell) the
holidays are not displayed anymore (nor are the astronomical events)

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

[kwin] [Bug 398018] Kwin_x11 crash when toggling Compositing

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=398018

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #7 from David Edmundson  ---
Can you include your libepoxy version?

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

[frameworks-kholidays] [Bug 400165] Allerheiligen (1. Nov) is not marked as a holiday for de-NW

2018-10-22 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=400165

--- Comment #2 from Christophe Giboudeaux  ---
tested locally. If I enable the fr_fr holiday, plasma_calendar_holiday_regions
in ~/.config contains:

[General]
selectedRegions=fr_fr

but the holidays shown in the clock applet are the us_en-us ones. My system
isn't localized

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

[kwin] [Bug 398114] Crash in libepoxy after suspending compositing

2018-10-22 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=398114

--- Comment #6 from David Edmundson  ---
Unhelpful notes from today's investigation:
 - it also doesn't crash if GDB is attached

 - ASAN (address or memory sanitizers) don't print anything useful

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

[dolphin] [Bug 400172] New: The drag-n-drop in Dolphin places is not working

2018-10-22 Thread Lucas Willems
https://bugs.kde.org/show_bug.cgi?id=400172

Bug ID: 400172
   Summary: The drag-n-drop in Dolphin places is not working
   Product: dolphin
   Version: 18.04.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: panels: places
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: lcswill...@gmail.com
  Target Milestone: ---

Created attachment 115835
  --> https://bugs.kde.org/attachment.cgi?id=115835=edit
An animation showing the bug

The drag-n-drop in Dolphin places is not working

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

[digikam] [Bug 399923] Segmentation fault during face detection

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399923

--- Comment #28 from caulier.gil...@gmail.com ---
"debug" do the stuff here.

backtrace are not suitable because there is not source code lines where the
debugger list the function calls until the crash, at least in libdigikam.so.

Gilles Caulier

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

[frameworks-kholidays] [Bug 400165] Allerheiligen (1. Nov) is not marked as a holiday for de-NW

2018-10-22 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=400165

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #1 from Allen Winter  ---
this is strange.  I verify that Allerheiligen doesn't show in KOrganizer on 1
November

well, for some German regions anyway
$ grep -c Allerheiligen holiday_de*
holiday_de-bb_de:0
holiday_de-bw_de:1
holiday_de-by_de:1
holiday_de_de:0
holiday_de-hh_de:0
holiday_de-mv_de:0
holiday_de-nw_de:1
holiday_de-rp_de:1
holiday_de-sh_de:0
holiday_de-sl_de:1
holiday_de-sn_de:0
holiday_de-st_de:0
holiday_de-th_de:0

I'm running KOrganizer in the US_en locale so maybe I'm using a German holiday
file that doesn't contain Allerheiligen

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

[kwin] [Bug 400171] New: QuickTiled Windows Should Not be Shadowed

2018-10-22 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=400171

Bug ID: 400171
   Summary: QuickTiled Windows Should Not be Shadowed
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: alexmason...@outlook.com
  Target Milestone: ---

SUMMARY
Windows that have been QuickTiled (snapped to the side of the screen) draw
shadows, which is inconsistent with how other platforms manage tiling (GNOME,
macOS SplitView). Suggest removing property _KDE_NET_WM_SHADOW from QuickTiled
windows.

STEPS TO REPRODUCE
1. Enable window decoration shadows in Breeze.
2. QuickTile two windows side by side.
3. Observe shadow overlapping the unfocused window.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.1 and below
KDE Frameworks Version: 5.51 and below
Qt Version: 5.11 and below

ADDITIONAL INFORMATION
Ideally the two tiled windows would still have shadows but be on an equal
'z-index', but it seems easier to just remove the shadows to fix the issue.

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

[Discover] [Bug 400123] Discover on Kubuntu 18.10 not showing items

2018-10-22 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=400123

Nate Graham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #4 from Nate Graham  ---
Darn.

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

[Discover] [Bug 400123] Discover on Kubuntu 18.10 not showing items

2018-10-22 Thread Angel
https://bugs.kde.org/show_bug.cgi?id=400123

--- Comment #3 from Angel  ---
(In reply to Nate Graham from comment #1)
> Does this reproduce after a restart?

yes, it does.

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

[kwin] [Bug 400170] New: KWin crashed when using the Slide effect and Alt+F2 shortcut

2018-10-22 Thread ultr
https://bugs.kde.org/show_bug.cgi?id=400170

Bug ID: 400170
   Summary: KWin crashed when using the Slide effect and Alt+F2
shortcut
   Product: kwin
   Version: 5.14.1
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: u...@ultr.pl
  Target Milestone: ---

Application: kwin_x11 (5.14.1)

Qt Version: 5.11.1
Frameworks Version: 5.51.0
Operating System: Linux 4.18.0-15.1-liquorix-amd64 x86_64
Distribution: Ubuntu 18.10

-- Information about the crash:
- What I was doing when the application crashed:
I was switching desktops with the Slide virtual desktop effect by pressing a
global shortcut for Desktop 2.
Before the Slide animation finished I pressed Alt+F2 to run a command.

- Effect:
KWin crashed and restarted.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3127d01840 (LWP 4285))]

Thread 6 (Thread 0x7f311700 (LWP 7264)):
#0  0x7f31322f37d6 in __GI_ppoll (fds=0x7f3114001138, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f3130eb7141 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f3130eb85b9 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f3130e6816b in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3130cb70b6 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f3130cc0c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f312fac4164 in start_thread (arg=) at
pthread_create.c:486
#7  0x7f31322ffdef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f311ca39700 (LWP 4481)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x7f31308a7fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x7f31308a7f68,
cond=0x7f31308a7f90) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x7f31308a7f90, mutex=0x7f31308a7f68) at
pthread_cond_wait.c:655
#3  0x7f31307b0e2a in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f31307b0e49 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f312fac4164 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f31322ffdef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f311f7fe700 (LWP 4453)):
#0  0x7f31322f37d6 in __GI_ppoll (fds=0x7f310c000d28, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f3130eb7141 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f3130eb85b9 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f3130e6816b in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3130cb70b6 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f312f2f41f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f3130cc0c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f312fac4164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f31322ffdef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f3125baa700 (LWP 4317)):
#0  0x7f31322f37d6 in __GI_ppoll (fds=0x7f311800e818, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f3130eb7141 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f3130eb85b9 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f3130e6816b in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f3130cb70b6 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f312edd8545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#6  0x7f3130cc0c87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f312fac4164 in start_thread (arg=) at
pthread_create.c:486
#8  0x7f31322ffdef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f3126ed0700 (LWP 4309)):
#0  0x7f31322f36d9 in __GI___poll (fds=0x7f3126ecfc78, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f3130be0917 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f3130be253a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f31273b2159 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5

[akregator] [Bug 262271] Akregator fetched feeds with incorrect content (overlapping with each other) with dates in future.

2018-10-22 Thread Massimiliano
https://bugs.kde.org/show_bug.cgi?id=262271

Massimiliano  changed:

   What|Removed |Added

 CC||leoni.massimiliano1@gmail.c
   ||om

--- Comment #17 from Massimiliano  ---
The bug is still present in Akregator 5.7.3 on Kubuntu 18.04 + backports
repositories.

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

[konqueror] [Bug 400169] New: A tab opened from a link that opens itself in a new tab/window becomes blank when the original tab is closed

2018-10-22 Thread Ethan Black
https://bugs.kde.org/show_bug.cgi?id=400169

Bug ID: 400169
   Summary: A tab opened from a link that opens itself in a new
tab/window becomes blank when the original tab is
closed
   Product: konqueror
   Version: 5.0.97
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: tabbing
  Assignee: konq-b...@kde.org
  Reporter: golemw...@gmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Go to a website that has ads (like yahoo.com) and left-click on an ad (or
any other link that opens itself in a new tab/window).
2. Close the original tab.

OBSERVED RESULT
  The new tab becomimg blank.

EXPECTED RESULT
  The new tab not becoming blank.
  ‾‾‾
SOFTWARE VERSIONS
  KDE Plasma Version:  5.13.5
  KDE Frameworks Version:  4.49.0
  Qt Version:  5.11.1
  Konqueror Version:   5.0.97

ADDITIONAL INFORMATION
  I'm using the WebEngine View Mode. (View -> View Mode -> WebEngine)

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

[kdevelop] [Bug 400168] New: Recheck tab repositioning for open files

2018-10-22 Thread Markus Elfring
https://bugs.kde.org/show_bug.cgi?id=400168

Bug ID: 400168
   Summary: Recheck tab repositioning for open files
   Product: kdevelop
   Version: 5.2.4
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: All editors
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: markus.elfr...@web.de
  Target Milestone: ---

I am used keep a bunch of files open for my projects in the program “KDevelop
5.2.4-43.4”. One usual consequences is then than a tab list is presented by the
editor widget on the top. I would like to switch quickly between tabs which fit
on my screen width.

It can happen then that a file with a tab on the top right corner was active
for a moment until I choose to switch to a file with a tab in the left area.
The simple change of a single character (or an explicit file storage action by
the shortcut “Ctrl+s”) can move the tab which got my editing focus to the
middle in the list. I find this software behaviour unpleasant. I would find it
nicer if the selected file tab can stay at a known position instead.

If I would like to return to the previous file, I need to scroll some times
which I would prefer to avoid often enough.

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

[KScreen] [Bug 400080] There seems to be a huge regression in multi-monitor support in 14.1

2018-10-22 Thread Richard Gladman
https://bugs.kde.org/show_bug.cgi?id=400080

Richard Gladman  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #3 from Richard Gladman  ---
(In reply to Nate Graham from comment #2)
> None of that should have been related at all. Before installing them, had
> you rebooted since upgrading to 5.14.1?

Once. Straight after the update.

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

[kdenlive] [Bug 400152] Kdenlive: save followed by kdeinit5 segfault

2018-10-22 Thread Vincent PINON
https://bugs.kde.org/show_bug.cgi?id=400152

--- Comment #3 from Vincent PINON  ---
the backtrace shows the crash in mltpreview.so called from kio/thumbnail.so...
can you determine what kind of clip (video / title / ...) triggers the crash?

also, which ubuntu packages are you using: official or from PPA?
can you also try with latest release AppImage?

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

[dolphin] [Bug 400167] New: New button: LA (Last Action)

2018-10-22 Thread Modirama Kopelke
https://bugs.kde.org/show_bug.cgi?id=400167

Bug ID: 400167
   Summary: New button: LA (Last Action)
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: r...@soltuuli.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Created attachment 115834
  --> https://bugs.kde.org/attachment.cgi?id=115834=edit
Picture of the LA-button

No Bug but an idea for Dolphin.
(This is the bug-center but where is the ideas-center???)

Very often it is necessary to jump between different folders. So you must climb
the whole folder tree up and down. There is a way to open more than one folder,
but after it, you must close it. Sometimes you forget it...

But here is an easier solution: The LA-Button!
LA stands for: last action.

If you press the LA button with the mouse the navigator jumps just to the
folder where the last action happened (marking, copying, deleting ...) and not
to the transit folders

This is faster :-)

Rama



SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[knotes] [Bug 399551] Knotes Crash on start

2018-10-22 Thread Paul Heeg
https://bugs.kde.org/show_bug.cgi?id=399551

Paul Heeg  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #8 from Paul Heeg  ---
Update in Debian testing fixes the startup crashes?

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

[Discover] [Bug 399540] Discover crash when click to categories

2018-10-22 Thread vector
https://bugs.kde.org/show_bug.cgi?id=399540

vector  changed:

   What|Removed |Added

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

--- Comment #6 from vector  ---
Sorry, this crash problem still exists, when the user sufing in menu. I do not
found any information or patches on Fedora.

Tested versions:
Latest Git version and all previous as well.

Backtrace:

Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
28return SYSCALL_CANCEL (nanosleep, requested_time, remaining);
[Current thread is 1 (Thread 0x7f90d7a99c80 (LWP 23972))]

Thread 10 (Thread 0x7f90a632d700 (LWP 24016)):
#0  0x7f90d98d1769 in __GI___poll (fds=0x7f908c014a90, nfds=1,
timeout=118390) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f90d8357bee in g_main_context_poll (priority=,
n_fds=1, fds=0x7f908c014a90, timeout=, context=0x7f908c000bf0)
at gmain.c:4221
#2  0x7f90d8357bee in g_main_context_iterate
(context=context@entry=0x7f908c000bf0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3915
#3  0x7f90d8357cfc in g_main_context_iteration (context=0x7f908c000bf0,
may_block=may_block@entry=1) at gmain.c:3981
#4  0x7f90d9fdb6bb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f908c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f90d9f8b34b in
QEventLoop::exec(QFlags) (this=0x7f90a632cde0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:71
#6  0x7f90d9de2796 in QThread::exec() (this=) at
thread/qthread.cpp:525
#7  0x7f90d9debdfc in QThreadPrivate::start(void*) (arg=0x3709970) at
thread/qthread_unix.cpp:367
#8  0x7f90d8daf037 in start_thread (arg=0x7f90a632d700) at
pthread_create.c:486
#9  0x7f90d98dd47f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f90a6ffd700 (LWP 23988)):
#0  0x7f90d839cc99 in g_mutex_lock (mutex=mutex@entry=0x7f9098000bf0) at
gthread-posix.c:1343
#1  0x7f90d8357ce8 in g_main_context_iteration (context=0x7f9098000bf0,
may_block=may_block@entry=1) at gmain.c:3980
#2  0x7f90d9fdb6bb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f9098000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7f90d9f8b34b in
QEventLoop::exec(QFlags) (this=0x7f90a6ffcde0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:71
#4  0x7f90d9de2796 in QThread::exec() (this=) at
thread/qthread.cpp:525
#5  0x7f90d9debdfc in QThreadPrivate::start(void*) (arg=0x572d730) at
thread/qthread_unix.cpp:367
#6  0x7f90d8daf037 in start_thread (arg=0x7f90a6ffd700) at
pthread_create.c:486
#7  0x7f90d98dd47f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f90b8ba8700 (LWP 23984)):
#0  0x7f90d98d1769 in __GI___poll (fds=0x7f90a006e4a0, nfds=1,
timeout=71377) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f90d8357bee in g_main_context_poll (priority=,
n_fds=1, fds=0x7f90a006e4a0, timeout=, context=0x7f90abf0)
at gmain.c:4221
#2  0x7f90d8357bee in g_main_context_iterate
(context=context@entry=0x7f90abf0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3915
#3  0x7f90d8357cfc in g_main_context_iteration (context=0x7f90abf0,
may_block=may_block@entry=1) at gmain.c:3981
#4  0x7f90d9fdb6bb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f90ab20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f90d9f8b34b in
QEventLoop::exec(QFlags) (this=0x7f90b8ba7de0,
flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:71
#6  0x7f90d9de2796 in QThread::exec() (this=) at
thread/qthread.cpp:525
#7  0x7f90d9debdfc in QThreadPrivate::start(void*) (arg=0x263df90) at
thread/qthread_unix.cpp:367
#8  0x7f90d8daf037 in start_thread (arg=0x7f90b8ba8700) at
pthread_create.c:486
#9  0x7f90d98dd47f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f90b95de700 (LWP 23980)):
#0  0x7f90d98ccfb4 in __GI___libc_read (fd=15,
buf=buf@entry=0x7f90b95ddbd0, nbytes=nbytes@entry=16) at
../sysdeps/unix/sysv/linux/read.c:26
#1  0x7f90d839b9d0 in read (__nbytes=16, __buf=0x7f90b95ddbd0,
__fd=) at /usr/include/bits/unistd.h:44
#2  0x7f90d839b9d0 in g_wakeup_acknowledge (wakeup=0x7f90a8003d80) at
gwakeup.c:210
#3  0x7f90d835773b in g_main_context_check
(context=context@entry=0x7f90ac000bf0, max_priority=2147483647,
fds=fds@entry=0x7f90ac004e10, n_fds=n_fds@entry=1) at gmain.c:3698
#4  0x7f90d8357b98 in g_main_context_iterate
(context=context@entry=0x7f90ac000bf0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3917
#5  0x7f90d8357cfc in g_main_context_iteration (context=0x7f90ac000bf0,
may_block=may_block@entry=1) at gmain.c:3981
#6  

[konqueror] [Bug 28037] a link to a mime type configured to use an external viewer opens blank konqueror window

2018-10-22 Thread Ethan Black
https://bugs.kde.org/show_bug.cgi?id=28037

Ethan Black  changed:

   What|Removed |Added

 CC||golemw...@gmail.com

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

[krunner] [Bug 400057] krunner crashes when starting another app

2018-10-22 Thread Anatoly Berbeka
https://bugs.kde.org/show_bug.cgi?id=400057

--- Comment #3 from Anatoly Berbeka  ---
(In reply to Kai Uwe Broulik from comment #1)
> Can you try to reproduce with debugging symbols for qtcore? Also perhaps run
> krunner from console and see what it outputs there.
> 
> #11 0x7fbf544c4dc5 in qt_assert(char const*, char const*, int) () at
> /usr/lib64/libQt5Core.so.5
> #12 0x7fbf544c7198 in  () at /usr/lib64/libQt5Core.so.5 ← This line I'm
> interested but you lack debug symbols
> #13 0x7fbf52c8f554 in start_thread () at /lib64/libpthread.so.0
> #14 0x7fbf53fe2ccf in clone () at /lib64/libc.so.6

I'm not very familiar with Qt, is rebuilding qtcore with debug support is the
only option? I couldn't find how to do this without rebuilding.

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

[krunner] [Bug 400057] krunner crashes when starting another app

2018-10-22 Thread Anatoly Berbeka
https://bugs.kde.org/show_bug.cgi?id=400057

--- Comment #2 from Anatoly Berbeka  ---
Ok, so I tried to run krunner from console, then pushed Alt+F2 and started
typing, then krunner instantly crashed with this output:

--- krunner crash output from console ---

terminate called after throwing an instance of 'Xapian::DatabaseModifiedError'
org.kde.plasma.runner.appstream: Had errors when loading AppStream metadata
pool ""
KCrash: Attempting to start /usr/bin/krunner from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: Application 'krunner' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
QSocketNotifier: Invalid socket 20 and type 'Read', disabling...
QSocketNotifier: Invalid socket 22 and type 'Exception', disabling...
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
QSocketNotifier: Invalid socket 21 and type 'Read', disabling...
radeon: Failed to allocate a buffer:
radeon:size  : 4096 bytes
radeon:alignment : 4096 bytes
radeon:domains   : 4
radeon:flags : 4
radeon: The kernel rejected CS, see dmesg for more information (-9).
radeon: Failed to allocate a buffer:
radeon:size  : 4096 bytes
radeon:alignment : 4096 bytes
radeon:domains   : 4
radeon:flags : 4
radeon: Failed to allocate a buffer:
radeon:size  : 4096 bytes
radeon:alignment : 4096 bytes
radeon:domains   : 2
radeon:flags : 0
radeon: Failed to allocate a buffer:
radeon:size  : 4096 bytes
radeon:alignment : 4096 bytes
radeon:domains   : 2
radeon:flags : 0
radeon: The kernel rejected CS, see dmesg for more information (-9).
radeon: Failed to allocate a buffer:
radeon:size  : 4096 bytes
radeon:alignment : 4096 bytes
radeon:domains   : 4
radeon:flags : 4
radeon: Failed to allocate a buffer:
radeon:size  : 4096 bytes
radeon:alignment : 4096 bytes
radeon:domains   : 4
radeon:flags : 4
[1]  + 27744 suspended (signal)  krunner

-- END ---

Those errors about 'Failed to allocate a buffer' repeats many times, so I cut
most of them. But they are absolutely the same like 2 last.

-- dmesg last line (because previous lines are too old) --

[102873.345766] radeon_dp_aux_transfer_native: 242 callbacks suppressed

--- END ---

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

[kwin] [Bug 398772] copying text crashes kwin_wayland, then black screen

2018-10-22 Thread Patrick Silva
https://bugs.kde.org/show_bug.cgi?id=398772

--- Comment #9 from Patrick Silva  ---
today wayland session crashed twice after I copy text in konsole and info
center.


SOFTWARE VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.14.1
Qt Version: 5.12.0 beta2
KDE Frameworks Version: 5.51.0

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

[kwin] [Bug 400135] Hot Corners Deactivate on Second Try

2018-10-22 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=400135

Martin Flöser  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from Martin Flöser  ---
Just tried, works just fine.

You are aware that there is a short reactivation timeout? Give it some time and
move the mouse properly away.

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

[kwin] [Bug 400135] Hot Corners Deactivate on Second Try

2018-10-22 Thread Andres Betts
https://bugs.kde.org/show_bug.cgi?id=400135

--- Comment #3 from Andres Betts  ---
Interesting! It doesn't behave like that for me right now. I am using neon git
unstable.

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

[calligrawords] [Bug 400166] New: Crash in thumbnailer, probably a badly imported emf file

2018-10-22 Thread Jaime Torres
https://bugs.kde.org/show_bug.cgi?id=400166

Bug ID: 400166
   Summary: Crash in thumbnailer, probably a badly imported emf
file
   Product: calligrawords
   Version: 3.1.0
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: doc
  Assignee: calligra-words-bugs-n...@kde.org
  Reporter: jtam...@gmail.com
  Target Milestone: ---

Created attachment 115833
  --> https://bugs.kde.org/attachment.cgi?id=115833=edit
The simplified file to reproduce the crash

The calligra words thumbnailer crashes with this file (with only a picture in
the header and another in the footer).

STEPS TO REPRODUCE
1. Copy the attached file to a directory.
2. Enable the previews in that directory. 
or Open the file with calligra-words.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: (git master)
KDE Frameworks Version: 5.51 (git)
Qt Version: 5.11.2

[KCrash Handler]
#5  0x7f241c09c544 in convertIndexedToARGB32PM(uint*, uint const*, int,
QVector const*, QDitherInfo*) (buffer=0x7ffcb9c704f0,
src=0x7ffcb9c704f0, count=33, clut=0x0) at painting/qdrawhelper.cpp:491
#6  0x7f241c0b134e in BlendSrcGeneric::fetch(int, int, int) (len=, y=0, x=0, this=0x7ffcb9c6e450) at painting/qdrawhelper.cpp:4015
#7  0x7f241c0b134e in handleSpans(int, QT_FT_Span_ const*,
QSpanData const*, BlendSrcGeneric&) (count=count@entry=11,
spans=spans@entry=0x7ffcb9c7a5e0, data=data@entry=0x4864c20, handler=...) at
painting/qdrawhelper.cpp:3959
#8  0x7f241c0aff7e in blend_src_generic_rgb64(int, QSpan const*, void*)
(count=11, spans=0x7ffcb9c7a5e0, userData=0x4864c20) at
painting/qdrawhelper.cpp:4077
#9  0x7f241c0d7c81 in fillRect_normalized(QRect const&, QSpanData*,
QRasterPaintEnginePrivate*) (r=..., data=data@entry=0x4864c20,
pe=pe@entry=0x4864830) at painting/qpaintengine_raster.cpp:1556
#10 0x7f241c0dd932 in QRasterPaintEngine::drawImage(QRectF const&, QImage
const&, QRectF const&, QFlags) (this=0x1bf36f0, r=...,
img=..., sr=...) at ../../include/QtCore/../../src/corelib/tools/qrect.h:184
#11 0x7f241c0f5365 in QPainter::drawImage(QRectF const&, QImage const&,
QRectF const&, QFlags)
(this=this@entry=0x7ffcb9c7b5d8, targetRect=..., image=..., sourceRect=...,
flags=flags@entry=...) at
../../include/QtCore/../../src/corelib/tools/qrect.h:644
#12 0x7f23eeb2d3b6 in QPainter::drawImage(QRect const&, QImage const&,
QRect const&, QFlags) (flags=...,
sourceRect=..., image=..., targetRect=..., this=0x7ffcb9c7b5d8) at /usr/include/qt5/QtCore/qrect.h:269
#13 0x7f23eeb2d3b6 in
Libemf::OutputPainterStrategy::stretchDiBits(Libemf::StretchDiBitsRecord&)
(this=0x7ffcb9c7b440, record=...) at
/g/5kde/calligra/calligra/libs/vectorimage/libemf/EmfOutputPainterStrategy.cpp:1367
#14 0x7f23eeb204df in Libemf::Parser::readRecord(QDataStream&)
(this=this@entry=0x7ffcb9c7b430, stream=...) at
/g/5kde/calligra/calligra/libs/vectorimage/libemf/EmfParser.cpp:819
#15 0x7f23eeb20d82 in Libemf::Parser::loadFromStream(QDataStream&)
(this=this@entry=0x7ffcb9c7b430, stream=...) at
/g/5kde/calligra/calligra/libs/vectorimage/libemf/EmfParser.cpp:123
#16 0x7f23eeb21379 in Libemf::Parser::load(QByteArray const&)
(this=0x7ffcb9c7b430, contents=...) at
/g/5kde/calligra/calligra/libs/vectorimage/libemf/EmfParser.cpp:100
#17 0x7f23ed69be54 in  () at
/usr/lib64/qt5/plugins/calligra/shapes/calligra_shape_vector.so
#18 0x7f23ed69c101 in  () at
/usr/lib64/qt5/plugins/calligra/shapes/calligra_shape_vector.so
#19 0x7f23ed69b5c7 in  () at
/usr/lib64/qt5/plugins/calligra/shapes/calligra_shape_vector.so
#20 0x7f23fc0e752e in KWPage::thumbnail(QSize const&, KoShapeManager*,
bool) const (this=this@entry=0x7ffcb9c7b830, size=..., shapeManager=0x6d726b0,
asPrint=asPrint@entry=true) at
/g/5kde/calligra/calligra/words/part/KWPage.cpp:339
#21 0x7f23fc0d5488 in KWDocument::generatePreview(QSize const&)
(this=, size=...) at /usr/include/qt5/QtCore/qflags.h:120
#22 0x7f23fec0985b in CalligraCreator::create(QString const&, int, int,
QImage&) (this=0x1e82180, path=..., width=128, height=128, image=...) at
/g/5kde/calligra/calligra/extras/thumbnail/calligracreator.cpp:125
#23 0x7f2416003835 in ThumbnailProtocol::get(QUrl const&)
(this=0x7ffcb9c7bbd0, url=...) at /usr/include/qt5/QtCore/qflags.h:120
#24 0x7f2415c1c57c in KIO::SlaveBase::dispatch(int, QByteArray const&)
(this=0x7ffcb9c7bbd0, command=, data=...) at
/g/5kde/frameworks/kio/src/core/slavebase.cpp:1119
#25 0x7f2415c1d8ed in KIO::SlaveBase::dispatchLoop()
(this=this@entry=0x7ffcb9c7bbd0) at
/g/5kde/frameworks/kio/src/core/slavebase.cpp:318
#26 0x7f241600102f in kdemain(int, char**) (argc=,
argv=) at
/g/5kde/kde/kdenetwork/kio-extras/thumbnail/thumbnail.cpp:138
#27 0x00409a56 in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) 

[kwin] [Bug 400135] Hot Corners Deactivate on Second Try

2018-10-22 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=400135

--- Comment #2 from Martin Flöser  ---
Ehm, That has always been a toggle.

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

[okular] [Bug 400146] Okular crashes when showing print preview

2018-10-22 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=400146

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||aa...@kde.org
 Status|REPORTED|NEEDSINFO

--- Comment #1 from Albert Astals Cid  ---
Does it also crash when you go to print->properties->advanced?

which printer do you have?

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

[okular] [Bug 399870] save (of annotations) overwrites symlinked PDF with copy

2018-10-22 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=399870

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/oku
   ||lar/99fe8fa6cfa7741351844f7
   ||0fb86ff297378e4c2

--- Comment #3 from Albert Astals Cid  ---
Git commit 99fe8fa6cfa7741351844f70fb86ff297378e4c2 by Albert Astals Cid.
Committed on 22/10/2018 at 19:41.
Pushed by aacid into branch 'Applications/18.08'.

Resolve symlinks before saving so we don't "break" them

Summary: BUGS: 399870

Reviewers: ngraham

Reviewed By: ngraham

Subscribers: shubham, ngraham, okular-devel

Tags: #okular

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

M  +9-5part.cpp

https://commits.kde.org/okular/99fe8fa6cfa7741351844f70fb86ff297378e4c2

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

[KScreen] [Bug 400080] There seems to be a huge regression in multi-monitor support in 14.1

2018-10-22 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=400080

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #2 from Nate Graham  ---
None of that should have been related at all. Before installing them, had you
rebooted since upgrading to 5.14.1?

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

[cervisia] [Bug 104316] support remote sandboxes by making cervisia network aware

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=104316

pos...@posteo.eu changed:

   What|Removed |Added

 CC|pos...@posteo.eu|

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

[konqueror] [Bug 157866] Run konqueror in sandbox for webbrowsing

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=157866

pos...@posteo.eu changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[cervisia] [Bug 116466] Add a note about changing sandboxes to the log area

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=116466

pos...@posteo.eu changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[cervisia] [Bug 159617] Current sandbox checkbox changed during error

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=159617

pos...@posteo.eu changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[dolphin] [Bug 378613] Add auto preview support for audio files (dolphin/phonon)

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=378613

pos...@posteo.eu changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[cervisia] [Bug 104316] support remote sandboxes by making cervisia network aware

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=104316

pos...@posteo.eu changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[dolphin] [Bug 297005] Run programs sandboxed.

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=297005

pos...@posteo.eu changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[frameworks-kio] [Bug 387215] KDE Let Applications Escape Firejail's Sandbox

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=387215

pos...@posteo.eu changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[kdelibs] [Bug 145671] sandboxing of kpart components

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=145671

pos...@posteo.eu changed:

   What|Removed |Added

 CC||pos...@posteo.eu

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

[digikam] [Bug 399923] Segmentation fault during face detection

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399923

--- Comment #27 from timo...@zoho.com ---
Why are the traces not suitable?

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

[digikam] [Bug 399923] Segmentation fault during face detection

2018-10-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=399923

--- Comment #26 from timo...@zoho.com ---
Yes I'm passing `-DCMAKE_BUILD_TYPE=debugfull` as I've seen in some
instructions. The boostrap script instead only passes
`-DCMAKE_BUILD_TYPE=debug`, is `debugfull` incorrect?

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

[Plasma Vault] [Bug 399643] Can't open vaults stored outside default path anymore

2018-10-22 Thread Oleg
https://bugs.kde.org/show_bug.cgi?id=399643

Oleg  changed:

   What|Removed |Added

 CC||mehanoid...@gmail.com

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

[Plasma Vault] [Bug 399643] Can't open vaults stored outside default path anymore

2018-10-22 Thread Oleg
https://bugs.kde.org/show_bug.cgi?id=399643

Oleg  changed:

   What|Removed |Added

 CC||mehanoid...@gmail.com

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

[frameworks-kholidays] [Bug 400165] New: Allerheiligen (1. Nov) is not marked as a holiday for de-NW

2018-10-22 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=400165

Bug ID: 400165
   Summary: Allerheiligen (1. Nov) is not marked as a holiday for
de-NW
   Product: frameworks-kholidays
   Version: 5.51.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: cf...@kde.org
  Target Milestone: ---

SUMMARY
Allerheiligen (1. Nov) is not marked as a holiday for de-nw_de

STEPS TO REPRODUCE
1. Configure Plasma calendar to show Holidays
2. Activate de-nw_de Holiday region

OBSERVED RESULT
Nov 1st is not shown as a Holiday

EXPECTED RESULT
Nov 1st shown as Holiday "Allerheiligen"

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.80-git
KDE Frameworks Version: 5.52.0-git
Qt Version: 5.11.2

ADDITIONAL INFORMATION
none

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

[valgrind] [Bug 400164] New: helgrind test encounters mips x-compiler warnings and assembler error

2018-10-22 Thread Randy MacLeod
https://bugs.kde.org/show_bug.cgi?id=400164

Bug ID: 400164
   Summary: helgrind test encounters mips x-compiler warnings and
assembler error
   Product: valgrind
   Version: 3.14 SVN
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: helgrind
  Assignee: jsew...@acm.org
  Reporter: rwmacl...@gmail.com
  Target Milestone: ---

Created attachment 115832
  --> https://bugs.kde.org/attachment.cgi?id=115832=edit
Patch: Make local functions static to avoid assembler error

SUMMARY

When building valgrind for Yocto-2.6 and using the musl libc rather than glibc,
a file in helgrind encounters an assembler error when building for
qemumips/qemumips64.

STEPS TO REPRODUCE

On any desktop Linux system such as Ubuntu-18.04,
0. sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib
\
 build-essential chrpath socat cpio python python3 python3-pip python3-pexpect
\
 xz-utils debianutils iputils-ping libsdl1.2-dev xterm
1. git clone git://git.pokylinux.org/poky.git
2. cd poky.git
3. git checkout bc98a1e89dcd7b3f59f99e4382439d9028ba4db2
4. mkdir ../proj; cd ../proj
5. . ../poky.git/oe-init-build-env vg-bug
6. MACHINE=qemumips TCLIBC=musl bitbake valgrind

OBSERVED RESULT

the valgrind build fails an error:

several warnings:
 ../../../valgrind-3.14.0/helgrind/tests/annotate_hbefore.c:360:6: warning: no
previous prototype for 'do_signal' [-Wmissing-prototypes]
|  void do_signal ( UWord* w )
|   ^


error:

/tmp/cce22iiw.s: Assembler messages:
/tmp/cce22iiw.s:446: Error: symbol `exit_0' is already defined
/tmp/cce22iiw.s:448: Error: symbol `exit' is already defined
/tmp/cce22iiw.s:915: Error: symbol `exit_0' is already defined
/tmp/cce22iiw.s:917: Error: symbol `exit' is already defined


EXPECTED RESULT

valgrind builds without error.


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: N/A
KDE Frameworks Version: N/A 
Qt Version: N/A

ADDITIONAL INFORMATION

Patch attached.

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

[kdenlive] [Bug 377184] Load Title default path is not taken from previous load

2018-10-22 Thread emohr
https://bugs.kde.org/show_bug.cgi?id=377184

emohr  changed:

   What|Removed |Added

Version|16.12.0 |18.08.2
   Keywords||junior-jobs
 Status|REOPENED|CONFIRMED

--- Comment #4 from emohr  ---
Thanks for testing. Opened a task to solve it.

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

[kdenlive] [Bug 400008] it crushed despite reinstalling it several times

2018-10-22 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=48

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED

--- Comment #2 from Christoph Feck  ---
You are missing a Qt platform integration plugin for your desktop, or at least
"qt5ct". Please ask for help in a forum of your distribution how to install and
configure these.

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

[plasma-nm] [Bug 400163] New: When plasma-nm asks for password to kdewallet the window ddoesnt open in foreground

2018-10-22 Thread mthw0
https://bugs.kde.org/show_bug.cgi?id=400163

Bug ID: 400163
   Summary: When plasma-nm asks for password to kdewallet the
window ddoesnt open in foreground
   Product: plasma-nm
   Version: 5.14.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jgrul...@redhat.com
  Reporter: jari...@hotmail.com
  Target Milestone: ---

...but rather behind the main window so user might not even notice it

EXPECTED RESULT
Prompt for password should open in front of all other windows.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.1
KDE Frameworks Version: 5.51
Qt Version: 5.12-beta2

ADDITIONAL INFORMATION

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

  1   2   3   >