[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable

[Ted Parvu]

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

--- Comment #31 from Ted Parvu  ---
Found a work-a-round that is working for me.

https://bbs.archlinux.org/viewtopic.php?pid=2166339#p2166339

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

[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable

[Ted Parvu]

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

--- Comment #30 from Ted Parvu  ---
(In reply to Ed Tomlinson from comment #29)
> No this is NOT a fix.   As mentioned above see: 
> https://issues.chromium.org/issues/336449364

So, where is this bug? 

It seems to be on all Chromium based browsers but that the bug is really in
KWin?

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

[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable

[Ted Parvu]

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

--- Comment #28 from Ted Parvu  ---
(In reply to Ted Parvu from comment #27)
> Reproducible by trying to drag and drop anything in Vivaldi.
> 
> Arch Linux
> plasma-desktop 6.0.4-1
> wayland 1.22.0-1
> 
> additionally I get this clue
> 
> > 12/100737.466353:ERROR:wayland_data_drag_controller.cc(147)] Invalid state 
> > when trying to start drag. source=kMouse

Looks like this was  fixed
https://chromium.googlesource.com/chromium/src/+/b3319430c1155a1716b441f225ef93f16493b5cb

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

[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable

[Ted Parvu]

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

Ted Parvu  changed:

   What|Removed |Added

 CC||t...@tedstechshack.com

--- Comment #27 from Ted Parvu  ---
Reproducible by trying to drag and drop anything in Vivaldi.

Arch Linux
plasma-desktop 6.0.4-1
wayland 1.22.0-1

additionally I get this clue

> 12/100737.466353:ERROR:wayland_data_drag_controller.cc(147)] Invalid state 
> when trying to start drag. source=kMouse

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

[kwin] [Bug 465190] New: With dual displays and scaling enabled menu widgets not rendering properly

[Ted Parvu]

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

Bug ID: 465190
   Summary: With dual displays and scaling enabled menu widgets
not rendering properly
Classification: Plasma
   Product: kwin
   Version: git-stable-Plasma/5.26
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: t...@tedstechshack.com
  Target Milestone: ---

SUMMARY

With dual displays and scaling enabled menu widgets not rendering properly
I can only reproduce this bug with my primary monitor scaled and a secondary
monitor is enabled.

Just the primary, no bug.
No scaling on primary, no bug.


STEPS TO REPRODUCE
1. secondary 1080p monitor scaling 100%
2. primary 4K monitor scaling 150%
3. left-click desktop background to get a menu

OBSERVED RESULT

Please see this video;

https://youtu.be/xryTPiuQFgM

EXPECTED RESULT

properly rendered menu

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Archlinux kwin 5.26.5-2, although this exists in many
previous versions
(available in About System)
KDE Plasma Version: 5.26.5-3
KDE Frameworks Version: 5.102.0-1
Qt Version: 6.4.2-1

ADDITIONAL INFORMATION

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

[digikam] [Bug 435085] New: Some DNG files cause program to abort.

[Ted Cash]

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

Bug ID: 435085
   Summary: Some DNG files cause program to abort.
   Product: digikam
   Version: 7.2.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-bugs-n...@kde.org
  Reporter: t...@tevern.us
  Target Milestone: ---

SUMMARY
Scanning some DNG photos causes program to exit immediately.

STEPS TO REPRODUCE
1. Scan files to Add Collection
2. Program exits if certain .DNG files are present
3. All .DNG files were created with Adobe DNG Converter.  Most files created do
not produce a problem.
4. I have about 10 files that will cause the program to crash every time. 
Lightroom sees no problem with these files.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 10 Pro 21H1
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
I am attaching one file that causes the program to crash.  I have several
others if that would be helpful.

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

[Spectacle] [Bug 422860] Screenshot taken on Wayland via keyboard shortcuts is neither copied to clipboard nor saved to default location

[Ted Sadler]

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

Ted Sadler  changed:

   What|Removed |Added

 CC||tsad...@integral-blue.com

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

Ted Sadler  changed:

   What|Removed |Added

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

--- Comment #22 from Ted Sadler  ---
@Méven Car

Under this revision, when using a keyboard shortcut with Spectacle closed, the
screenshots are copied to the clipboard as expected but the "autosave the image
to default directory" function no longer works. If Spectacle is open while
using the shortcut, the image is both copied to the clipboard and saved. 

This is the same behavior that I experienced with @Antonio's revision.

Ted

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

[Akonadi] [Bug 422017] New: akonadi crashed while deleting emails

[Ted Parvu]

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

Bug ID: 422017
   Summary: akonadi crashed while deleting emails
   Product: Akonadi
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: t...@tedstechshack.com
  Target Milestone: ---

Application: akonadiserver (5.14.1 (20.04.0))

Qt Version: 5.14.2
Frameworks Version: 5.70.0
Operating System: Linux 5.6.14-arch1-1 x86_64
Windowing system: X11
Distribution: "Arch Linux"

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

I was deleting a bunch of emails from my inbox. Happens a lot. I am using IMAPS

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd29238ec80 (LWP 1810))]

Thread 40 (Thread 0x7fd1e0ff9700 (LWP 948438)):
#0  0x7fd29639005f in poll () from /usr/lib/libc.so.6
#1  0x7fd294d47f38 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fd294cf9221 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fd29695a11c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fd296901c0c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x5641548ad5bc in ?? ()
#6  0x7fd29692f142 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#7  0x7fd2969032b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#8  0x7fd296905ce3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#9  0x7fd29695aab4 in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7fd294cfa43c in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#11 0x7fd294d47fa9 in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x7fd294cf9221 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#13 0x7fd29695a101 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#14 0x7fd296901c0c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#15 0x7fd296722c02 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#16 0x7fd296723dcf in ?? () from /usr/lib/libQt5Core.so.5
#17 0x7fd295a2b422 in start_thread () from /usr/lib/libpthread.so.0
#18 0x7fd29639abf3 in clone () from /usr/lib/libc.so.6

Thread 39 (Thread 0x7fd1e17fa700 (LWP 3463)):
#0  0x7fd29639005f in poll () from /usr/lib/libc.so.6
#1  0x7fd294d47f38 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fd294cf9221 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fd29695a11c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fd296901c0c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x5641548ad5bc in ?? ()
#6  0x7fd29692f142 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#7  0x7fd2969032b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#8  0x7fd296905ce3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#9  0x7fd29695aab4 in ?? () from /usr/lib/libQt5Core.so.5
#10 0x7fd294cfa43c in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#11 0x7fd294d47fa9 in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x7fd294cf9221 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#13 0x7fd29695a101 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#14 0x7fd296901c0c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#15 0x7fd296722c02 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#16 0x7fd296723dcf in ?? () from /usr/lib/libQt5Core.so.5
#17 0x7fd295a2b422 in start_thread () from /usr/lib/libpthread.so.0
#18 0x7fd29639abf3 in clone () from /usr/lib/libc.so.6

Thread 38 (Thread 0x7fd1e1ffb700 (LWP 3430)):
#0  0x7fd29639005f in poll () from /usr/lib/libc.so.6
#1  0x7fd294d47f38 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fd294cf9221 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fd29695a11c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fd296901c0c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x5641548ad5bc in ?? ()
#6  0x7fd29692f142 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#7  0x7fd2969032b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#8  0x7fd296905ce3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#9  0x7fd29695aab4 in ?? () from /usr/lib/libQt5Core.so.5

[frameworks-kio] [Bug 421374] Service file specifiying 'Run in terminal' gives "Error code 100, Could not find the program ‘konsole’" after Plasma 5.18.5 update.

[Ted Sadler]

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

Ted Sadler  changed:

   What|Removed |Added

 CC||tsad...@integral-blue.com

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

Ted Sadler  changed:

   What|Removed |Added

 CC||tsad...@integral-blue.com

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

--- Comment #19 from Ted Sadler  ---
(In reply to Curtis Parfitt-Ford from comment #18)
> Perhaps it might be an idea to add a separate "When Spectacle is activated
> by a hotkey" section with those same options, such that the two scenarios
> could be controlled separately.

That would probably be helpful. It's also misleading that the "Autosave the
image to the default location" option is under "When Spectacle is Running" but
Spectacle doesn't need to be running for that to work. Hotkey activation saves
the screenshots when that option is enabled, even with Spectacle's UI closed. I
think that behavior is what led me to believe that the failure to copy the
image to the clipboard is a bug, not an intended behavior.

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

--- Comment #17 from Ted Sadler  ---
(In reply to David Redondo from comment #16)
> This is not a bug but is working as implemented. This is also the reason the
> setiing is in the "When Spectacle is running" section like what should
> happen if you press the print key again. I will leave this bug open as it is
> evident that the current situation is not clear at all and I'm not happy
> with it either.

David, thank you for the clarification -- and you're right. The section does
say "When Spectacle is Running," but at the same time I think the interface is
a bit misleading given that Spectacle has to be running *somewhere* in order
for the hotkey combinations to work at all. Thanks for leaving it open.

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

Ted Sadler  changed:

   What|Removed |Added

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

--- Comment #13 from Ted Sadler  ---
Antonio,

It appears I spoke too soon... while this fix does resolve the clipboard
problem, the captures are no longer auto-saving to their configured destination
when using the hotkeys with Spectacle closed. This behavior was working fine
before the bugfix...

Re-opening this bug for now, but I can file a new one if desired.

Thanks,
Ted

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

Ted Sadler  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #12 from Ted Sadler  ---
(In reply to Antonio from comment #11)
> @Ted Sadler , I've found an approach to make this work, tested it on my side
> and now it works as expected. Let's see if this is acceptable and if it will
> be merged: https://phabricator.kde.org/D29596

Hey, that did it! Spectacle now copies the capture to the clipboard even when
the UI is closed. I also am now seeing the new toast notification. Verified
with paste and everything works as expected.

Thank you Antonio! I'll change the status to Resolved.

Cheers,
Ted

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

--- Comment #10 from Ted Sadler  ---
(In reply to Antonio from comment #9)
> 
> Well, deleted the old spectaclerc and let spectacle create a new one.
> Now I could reproduce. Took the old spectaclerc from a backup and tried it
> again, still reproducible.
> I don't know why it was working fine last night :s

that's certainly strange... you must have been testing after the bugs had gone
to bed! ;)

Thanks for looking into this -- let me know what you find in the source!

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

--- Comment #8 from Ted Sadler  ---
Thanks @Antonio! Out of curiosity, what did you do differently from your
previous steps to reproduce the issue?

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

--- Comment #6 from Ted Sadler  ---
(In reply to Antonio from comment #5)
> Can you check ~/.config/spectaclerc ?

This is mine:

[$Version]
update_info=spectacle_newConfig.upd:spectacle-new-config

[General]
alwaysRememberRegion=false
autoSaveImage=true
copyImageToClipboard=true
printKeyActionRunning=0
rememberLastRectangularRegion=true
showMagnifier=true
useLightMaskColour=false
useReleaseToCapture=true

[GuiConfig]
captureMode=5 #This was 4 previously. I changed it to 5 but the bug persists
cropRegion=4321,175,854,639
includePointer=false
window-position=124,154

[KFileDialog Settings]
detailViewIconSize=0

[Save]
compressionQuality=100
copySaveLocation=false
defaultSaveImageFormat=png
lastUsedSaveMode=0
saveFilenameFormat=Screenshot_%Y%M%D_%H%m%S

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

--- Comment #4 from Ted Sadler  ---
(In reply to @Antonio from comment #3)

I am on v20.04.0 now, yes. However, I am still experiencing the same problem...

If I just press PrntScrn alone, I get a full-image capture that I can paste.
But if I press any hotkey configured in Spectacle (including any shortcuts for
"full desktop capture", the capture is saved and I get a popup but my clipboard
doesn't contain the image if Spectacle was not running in the foreground
already.

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

[Spectacle] [Bug 420477] Spectacle hotkey captures do not copy to clipboard

[Ted Sadler]

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

--- Comment #2 from Ted Sadler  ---
(In reply to Nate Graham from comment #1)

Nate, thanks for the confirmation. I was able to reproduce that specific test
also with the same results.

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

[krita] [Bug 409899] New: brush size display does not change with []

[Ted]

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

Bug ID: 409899
   Summary: brush size display does not change with []
   Product: krita
   Version: unspecified
  Platform: Other
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: tro...@sympatico.ca
  Target Milestone: ---

SUMMARY
brush size tool display does not change when using [] keyboard keys

STEPS TO REPRODUCE
1. press [ or ]
2. 
3. 

OBSERVED RESULT
brush size changes but displayed size does not change

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(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.

[kleopatra] [Bug 398556] New: changing key expiration reports success after 3 failed passphrase attempts

[Ted Parvu]

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

Bug ID: 398556
   Summary: changing key expiration reports success after 3 failed
passphrase attempts
   Product: kleopatra
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: t...@tedstechshack.com
CC: kdepim-b...@kde.org, m...@kde.org
  Target Milestone: ---

Version 3.1.2

Key has expired. I edit the key to change the expiration. But I seem to have
forgotten my passphrase.

An empty passphrase reports success. Expiration unchanged.


3 invalid passphrases, after the 3rd Kleo reports;

"Expiry date changed successfully."

Expiration unchanged.

I would expect to see something reporting that I got the passphrase incorrect
not that the expiration was changed.

cheers,

--Ted

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

[okular] [Bug 393972] New: Okular Does not print PDF 1:1 scale

[Ted Becker]

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

Bug ID: 393972
   Summary: Okular Does not print PDF 1:1 scale
   Product: okular
   Version: 1.3.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: rail.b...@att.net
  Target Milestone: ---

Created attachment 112488
  --> https://bugs.kde.org/attachment.cgi?id=112488=edit
PDF Template that should print to proper scale.

PDF printed image is approximately 92% of full size.  PDF is displayed properly
to scale on screen.  Margins are are adequate for printer.  Paper size and
orientation are set properly. Setting margins to 0.0 in printer properties has
no effect.

Printer is Brother HL-L2300D
Driver is current.
OS  Kubuntu 18.04
KDE Plasman 5.12.4
Okular 1.3.3
Paper set to Letter, Lanscape

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

[kwin] [Bug 388127] New: Kwin crashes when switching desktops

[Ted Parvu]

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

Bug ID: 388127
   Summary: Kwin crashes when switching desktops
   Product: kwin
   Version: 5.11.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: t...@tedstechshack.com
  Target Milestone: ---

This could be the same bug as #386370 but I am not sure. I don't have a
backtrace. I'll try and install versions with debug info but I wanted to file
this now.

I have tried different desktop switching effects, and I think what is causing
the issue is the "Desktop Switch On-Screen Display" option.

kwin crashes somewhat randomly when switching desktops. But it is fairly
regularly. I ran "kwin_x11" in a Konsole and before it crashes I get messages
like this;


QOpenGLContext::swapBuffers() called with non-exposed window, behavior is
undefined
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is
undefined
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is
undefined
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is
undefined
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is
undefined
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is
undefined
QXcbConnection: XCB error: 3 (BadWindow), sequence: 64494, resource id:
130023438, major code: 18 (ChangeProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 1686, resource id:
130023438, major code: 18 (ChangeProperty), minor code: 0
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is
undefined
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is
undefined
QOpenGLContext::swapBuffers() called with non-exposed window, behavior is
undefined
The X11 connection broke: No error (code 0)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
  after 96363 requests (96363 known processed) with 0 events remaining.


As this might help as well;

>kwin_x11 
QXcbConnection: XCB error: 3 (BadWindow), sequence: 172, resource id:
127926294, major code: 20 (GetProperty), minor code: 0
OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce GTX 760/PCIe/SSE2
OpenGL version string:  4.6.0 NVIDIA 387.34
OpenGL shading language version string: 4.60 NVIDIA
Driver: NVIDIA
Driver version: 387.34
GPU class:  Unknown
OpenGL version: 4.6
GLSL version:   4.60
X server version:   1.19.5
Linux kernel version:   4.14.7
Requires strict binding:no
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no


Just by experiment I turned off the "Desktop Switch On-Screen Display" option
and I don't seem to be crashing now.

You can try and reproduce by turning that option on and switching desktops
multiple times until kwin crashes. Once kwin crashes, I am able to run it again
in a console and continue working.

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

[kdelibs] [Bug 385179] New: Knotify crashes in backbround

[Ted Ma]

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

Bug ID: 385179
   Summary: Knotify crashes in backbround
   Product: kdelibs
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: knotify
  Assignee: ogoff...@kde.org
  Reporter: ma...@arcturusnetworks.com
  Target Milestone: ---

Application: knotify4 (4.14.25)
KDE Platform Version: 4.14.25
Qt Version: 4.8.6
Operating System: Linux 4.4.87-18.29-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
Crash report pops up instead of a Knotify popup. I recently updated a number of
libraries in order to install MCUExpresso and LPC Expresso (NXP IDE's). I
suspect an incompatibility with one of the shared libraries I updated.

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

Thread 3 (Thread 0x7f3096b74700 (LWP 10605)):
#0  0x7f30b379228d in read () at /lib64/libc.so.6
#1  0x7f30ae8e79e1 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-11.1.so
#2  0x7f30b348c1ce in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7f30b348cbe2 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7f30b348cca0 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7f30b349ade6 in  () at /usr/lib64/libpulse.so.0
#6  0x7f30ae916708 in  () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so
#7  0x7f30b2d50744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f30b379eaad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f30a3139700 (LWP 4564)):
#0  0x7f30b379620d in poll () at /lib64/libc.so.6
#1  0x7f30b0bdb314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f30b0bdb42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f30b3f90fce in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f30b3f62d3f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f30b3f63035 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f30b3e6049f in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f30b3f4779d in  () at /usr/lib64/libQtCore.so.4
#8  0x7f30b3e62b7f in  () at /usr/lib64/libQtCore.so.4
#9  0x7f30b2d50744 in start_thread () at /lib64/libpthread.so.0
#10 0x7f30b379eaad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f30b665a900 (LWP 4563)):
[KCrash Handler]
#6  0x7f30a214dce7 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#7  0x7f30a214dee2 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#8  0x7f30a214f2e3 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#9  0x7f30a2153d10 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#10 0x7f30a2155091 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#11 0x7f30b3f780ea in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#12 0x7f30a215acff in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#13 0x7f30a2160b81 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#14 0x7f30b0261760 in g_cclosure_marshal_VOID__BOXEDv () at
/usr/lib64/libgobject-2.0.so.0
#15 0x7f30b025eb37 in  () at /usr/lib64/libgobject-2.0.so.0
#16 0x7f30b0277918 in g_signal_emit_valist () at
/usr/lib64/libgobject-2.0.so.0
#17 0x7f30b0278592 in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
#18 0x7f30a1dfb88a in gst_bus_sync_signal_handler () at
/usr/lib64/libgstreamer-1.0.so.0
#19 0x7f30a1dfbb33 in gst_bus_post () at /usr/lib64/libgstreamer-1.0.so.0
#20 0x7f30a1e10928 in  () at /usr/lib64/libgstreamer-1.0.so.0
#21 0x7f30a1dedccf in  () at /usr/lib64/libgstreamer-1.0.so.0
#22 0x7f30a1e13633 in gst_element_post_message () at
/usr/lib64/libgstreamer-1.0.so.0
#23 0x7f30a1e15094 in gst_element_continue_state () at
/usr/lib64/libgstreamer-1.0.so.0
#24 0x7f30a1e14903 in gst_element_change_state () at
/usr/lib64/libgstreamer-1.0.so.0
#25 0x7f30a1e14ebc in  () at /usr/lib64/libgstreamer-1.0.so.0
#26 0x7f30a215e9c3 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#27 0x7f30a2153f61 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#28 0x7f30a2154245 in  () at
/usr/lib64/kde4/plugins/phonon_backend/phonon_gstreamer.so
#29 0x0040fa41 in  ()
#30 0x0040bcd5 in  ()
#31 0x0040c69f in  ()
#32 0x0040cf3c in  ()
#33 0x0040d2d0 in  ()
#34 0x0040d433 in  ()
#35 0x7f30b42f1ced in  () at /usr/lib64/libQtDBus.so.4
#36 0x7f30b42f2e79 in  () at /usr/lib64/libQtDBus.so.4
#37 

[dolphin] [Bug 384978] New: Dolphon crashes when deleting small downloaded .zip file (either to waste or DELETE)

[Ted Ma]

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

Bug ID: 384978
   Summary: Dolphon crashes when deleting small downloaded .zip
file (either to waste or DELETE)
   Product: dolphin
   Version: 16.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ma...@arcturusnetworks.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (16.08.2)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.87-18.29-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- trying to delete the second copy ( (1)) of a file using right click and with
right-click with SHIFT

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7fadb7245700 (LWP 26088)):
#0  0x7fadeb6d328d in read () at /lib64/libc.so.6
#1  0x7faddc8829e1 in pa_read () at
/usr/lib64/pulseaudio/libpulsecommon-11.1.so
#2  0x7fade0bfc1ce in pa_mainloop_prepare () at /usr/lib64/libpulse.so.0
#3  0x7fade0bfcbe2 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0
#4  0x7fade0bfcca0 in pa_mainloop_run () at /usr/lib64/libpulse.so.0
#5  0x7fade0c0ade6 in  () at /usr/lib64/libpulse.so.0
#6  0x7faddc8b1708 in  () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so
#7  0x7fade1044744 in start_thread () at /lib64/libpthread.so.0
#8  0x7fadeb6dfaad in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fadc3ca6700 (LWP 26064)):
#0  0x7fadeb6d720d in poll () at /lib64/libc.so.6
#1  0x7fade04bd314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fade04bd42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fade59b133b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fade595efeb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fade5799f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fade579e9e9 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7fade1044744 in start_thread () at /lib64/libpthread.so.0
#8  0x7fadeb6dfaad in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fadd2f5f700 (LWP 26062)):
#0  0x7fadeb6d720d in poll () at /lib64/libc.so.6
#1  0x7fade04bd314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fade04bd42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fade59b133b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fade595efeb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fade5799f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fade5dc5295 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7fade579e9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fade1044744 in start_thread () at /lib64/libpthread.so.0
#9  0x7fadeb6dfaad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fadd4679700 (LWP 26061)):
#0  0x7fadeb6d720d in poll () at /lib64/libc.so.6
#1  0x7fadde4783e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7fadde479fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7fadd6bd3839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fade579e9e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7fade1044744 in start_thread () at /lib64/libpthread.so.0
#6  0x7fadeb6dfaad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fadebe19900 (LWP 26060)):
[KCrash Handler]
#6  0x7fadc0f4e277 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#7  0x7fadc0f4e4a2 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#8  0x7fadc0f4fe13 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#9  0x7fadc0f509f4 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#10 0x7fadc0f536a1 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#11 0x7fade598abc1 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#12 0x7fadc0f5973f in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#13 0x7fadc0f5bcc4 in  () at
/usr/lib64/qt5/plugins/phonon4qt5_backend/phonon_gstreamer.so
#14 0x7fade0794760 in g_cclosure_marshal_VOID__BOXEDv () at
/usr/lib64/libgobject-2.0.so.0
#15 0x7fade0791b37 in  () at /usr/lib64/libgobject-2.0.so.0
#16 0x7fade07aa918 in g_signal_emit_valist () at
/usr/lib64/libgobject-2.0.so.0
#17 0x7fade07ab592 in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
#18 0x7fadc0c3788a in gst_bus_sync_signal_handler () at
/usr/lib64/libgstreamer-1.0.so.0
#19 

[kwin] [Bug 381748] New: KDE5 crash

[Ted Kandell]

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

Bug ID: 381748
   Summary: KDE5 crash
   Product: kwin
   Version: 5.9.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ted_kand...@yahoo.com
  Target Milestone: ---

Application: kwin_x11 (5.9.5)

Qt Version: 5.8.0
Frameworks Version: 5.33.0
Operating System: Linux 4.4.73-18.17-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
Trying to access a Gimp window on another desktop. I clicked on the Task
Manager entry for this window and KDE crashed.

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

Thread 5 (Thread 0x7f2f2e365700 (LWP 1610)):
#0  0x7f2fd28f32cf in ppoll () at /lib64/libc.so.6
#1  0x7f2fcfffa8b1 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2  0x7f2fcfffbe7f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f2fcffae6ab in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f2fcfdf69aa in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f2fca8fb108 in  () at /usr/lib64/libQt5Qml.so.5
#6  0x7f2fcfdfb019 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f2fd2bc2744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f2fd28fbaad in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f2fb248f700 (LWP 1589)):
#0  0x7f2fd2bc70bf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f2fcef6db1b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f2fcef6db49 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f2fd2bc2744 in start_thread () at /lib64/libpthread.so.0
#4  0x7f2fd28fbaad in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f2fb3d31700 (LWP 1573)):
#0  0x7f2fd28f32cf in ppoll () at /lib64/libc.so.6
#1  0x7f2fcfffa8b1 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2  0x7f2fcfffbe7f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f2fcffae6ab in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f2fcfdf69aa in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f2fca8fb108 in  () at /usr/lib64/libQt5Qml.so.5
#6  0x7f2fcfdfb019 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f2fd2bc2744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f2fd28fbaad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f2fba9e9700 (LWP 1480)):
#0  0x7f2fd2bc9d2d in read () at /lib64/libpthread.so.0
#1  0x7f2fc735e670 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f2fc731de49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f2fc731e2a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f2fc731e42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f2fcfffe8ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f2fcffae6ab in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f2fcfdf69aa in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f2fc9aabd15 in  () at /usr/lib64/libQt5DBus.so.5
#9  0x7f2fcfdfb019 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f2fd2bc2744 in start_thread () at /lib64/libpthread.so.0
#11 0x7f2fd28fbaad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f2fd3193940 (LWP 1453)):
[KCrash Handler]
#6  0x7f2fcffdcf4e in QObject::connect(QObject const*, char const*, QObject
const*, char const*, Qt::ConnectionType) () at /usr/lib64/libQt5Core.so.5
#7  0x7f2fcefb1aab in  () at /usr/lib64/libQt5Script.so.5
#8  0x7f2fcefb1b94 in  () at /usr/lib64/libQt5Script.so.5
#9  0x7f2fcefb1e72 in QScriptEngine::newQObject(QObject*,
QScriptEngine::ValueOwnership, QFlags const&)
() at /usr/lib64/libQt5Script.so.5
#10 0x7f2fd24fecec in  () at /usr/lib64/libkwin.so.5
#11 0x7f2fcefb215c in  () at /usr/lib64/libQt5Script.so.5
#12 0x7f2fcefd4cde in  () at /usr/lib64/libQt5Script.so.5
#13 0x7f2fcefdc3e5 in  () at /usr/lib64/libQt5Script.so.5
#14 0x7f2fcffd869c in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#15 0x7f2fcf7a8398 in
KWin::EffectsHandler::desktopPresenceChanged(KWin::EffectWindow*, int, int) ()
at /usr/lib64/libkwineffects.so.10
#16 0x7f2fcf7a93ce in  () at /usr/lib64/libkwineffects.so.10
#17 0x7f2fcffd9886 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#18 0x7f2fd0c6c1bc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#19 0x7f2fd0c730f0 in 

[gwenview] [Bug 380977] New: When opening an image file from Dolphin with Gwenview a "same shortcut (Shift+Del)" warning dialog appears

[Ted Kandell]

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

Bug ID: 380977
   Summary: When opening an image file from Dolphin with Gwenview
a "same shortcut (Shift+Del)" warning dialog appears
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: ted_kand...@yahoo.com
CC: myr...@kde.org
  Target Milestone: ---

Created attachment 105989
  --> https://bugs.kde.org/attachment.cgi?id=105989=edit
Gwenview Ambiguious Shortcuts modal dialog

Upon clicking on an image file in Dolphin Version 16.08.2, Gwenview 16.08.2
opens a modal dialog saying the following:

Ambiguous Shortcuts - Gwenview: There are two actions (Cut, Delete) that want
to use the same shortcut (Shift+Del). This is most probably a bug. Please
report it in bugs.kde.org

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

[kdevelop] [Bug 379317] Clang parser issues

[Ted]

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

--- Comment #3 from Ted <tedfed...@gmail.com> ---
(This is on Fedora 24)
Problem appears to be an installation issue.
I fully removed kdevelop and kdevplatform which also cause a removal of several
other packages.  I then did a fresh install of kdevelop (sudo yum install
kdevelop) which installed the following below and I think the issues are
resolved:

Installed:
  grantlee-qt5.x86_64 5.1.0-2.fc24kdevelop.x86_64 9:5.1.0-1.fc24   
  kdevelop-libs.x86_64 9:5.1.0-1.fc24
  kdevplatform.x86_64 5.1.0-1.fc24kdevplatform-libs.x86_64 5.1.0-1.fc24
  kf5-kactivities-libs.x86_64 5.33.0-1.fc24  
  kf5-kitemmodels.x86_64 5.22.0-1.fc24kf5-krunner.x86_64 5.22.0-1.fc24 
  kf5-ktexteditor.x86_64 5.22.0-1.fc24   
  kf5-plasma.x86_64 5.22.0-1.fc24 kf5-threadweaver.x86_64 5.22.0-1.fc24
  libgit2.x86_64 0.24.6-1.fc24   
  libkomparediff2.x86_64 16.12.3-1.fc24   libksysguard.x86_64 5.8.6-1.fc24 
  libserf.x86_64 1.3.8-2.fc24
  qt5-qtwebkit.x86_64 5.6.2-1.fc24subversion-libs.x86_64 1.9.4-2.fc24  
  zsh.x86_64 5.2-5.fc24

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

[kdevelop] [Bug 379317] Clang parser issues

[Ted]

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

Ted <tedfed...@gmail.com> changed:

   What|Removed |Added

   Platform|Other   |RedHat RPMs

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

[kdevelop] [Bug 379317] Clang parser issues

[Ted]

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

--- Comment #2 from Ted <tedfed...@gmail.com> ---
I tried the AppImage, no better.
I will take a look at 5.0.4.

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

[kdevelop] [Bug 379317] Clang parser issues

[Ted]

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

--- Comment #1 from Ted <tedfed...@gmail.com> ---
I am going to try the AppImage to see if that behaves any differently.
What I have now is not very usable.

I may try the 5.0.4 version to see if that behaves better than 5.1.0.

Does anyone know what had changed in the clang parser between these versions?

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

[kdevelop] [Bug 379317] New: Clang parser issues

[Ted]

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

Bug ID: 379317
   Summary: Clang parser issues
   Product: kdevelop
   Version: 5.1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: tedfed...@gmail.com
  Target Milestone: ---

In upgrading from Kdevelop 5.0.3 to 5.1.0 I find there are some new issues with
the Clang parser.  
I finally figured out in 5.0.3 that when I wasn't getting parsing in a file
that needed to look in the "Problems" tab which would show me which include
files that were not found.  Once I resolved the issue with the include files
then the parsing would work.

5.1.0 appears to take much longer to try to parse the file and then does not
appear to list unresolved paths to include files as "Problems".  And also
doesn't always flag the include file as an issue (In 5.0.3 there would be a red
tilda mark to indicate an issue with the include file). It could be if I waited
long enough then 5.1.0 would eventually tag the problem include files.  The
parser though seems to get stuck and never shows me the issues.  I have to go
through the include files one-by-one to figure out which is a problem.  Once I
finally get this right then the parse works, but again it is slower than in
5.0.3.

I would just go back to 5.0.3, but I found that in the 5.0.3 the modification
times on my files would mysteriously change just by opening Kdevelop even
though I had not changed the file or even had that particular file open in the
editor.

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

[Discover] [Bug 376241] software centre is empty

[Ted Becker]

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

--- Comment #34 from Ted Becker <rail.b...@att.net> ---
Sorry I won't be able to test it.  There were enough other issues with 16.04
that I switched back to 14.04.

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

[Discover] [Bug 378257] New: Discover not display packages

[Ted Becker]

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

Bug ID: 378257
   Summary: Discover not display packages
   Product: Discover
   Version: 5.6.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: rail.b...@att.net
  Target Milestone: ---

"Installed" => software shows 0 items installed.
"Discover"  => "Most Popular"%"Best Rating" lists are blank.
Opening any of the Categories displays a blank screen.
Clicking on the one of the banner ads does go to an information and
installation screen.

Kubuntu 16.04

KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

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

[plasmashell] [Bug 377925] New: When grouping is on Task Manager tooltips should have left-right scrolling for more than 5 entries

[Ted Kandell]

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

Bug ID: 377925
   Summary: When grouping is on Task Manager tooltips should have
left-right scrolling for more than 5 entries
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: ted_kand...@yahoo.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

When grouping and "Show Toolips" are selected, the horizontal tooltip can only
display 5 preview windows at a time in the horizontal tooltip. There is no way
to scroll through these previews if there are more than 5 windows in a group. 

Not grouping windows in the taskbar and having one tooltip preview for each
window isn't practical when there are a large number of windows for one
application.

The tooltip bar should have some ability to scroll right and left through all
window previews.

This is particularly important because the grouping popup list has no ability
to scroll either so there is no way to access all windows from the taskbar when
the  windows are grouped.

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

[plasmashell] [Bug 377923] New: Task manager grouping popup list only shows 15 windows, no option to scroll

[Ted Kandell]

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

Bug ID: 377923
   Summary: Task manager grouping popup list only shows 15
windows, no option to scroll
   Product: plasmashell
   Version: master
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: ted_kand...@yahoo.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

The Task Manager option, "Open groups in popups", produces a vertical list of
windows for the group (e.g. by program name), which only shows entries. The
rendering of the last in the list appears to be below the taskbar. Open users
have many more windows open for a program than 15, for example many more
Dolphin windows, which can serve as a reminder for various tasks. The inability
to scroll this list means that all windows cannot be accessed from the taskbar
when grouped. 

Not grouping with a large number of windows causes each window to have a very
tiny icon which is almost indistinguishable from the others. Scrolling through
a large number of ungrouped windows in the taskbar, even with tooltips, is very
time consuming.

Another option, the Window List which has a scrollable popup, does not have the
ability to group windows by program name, and in fact has no settings at all.

This happens even if the "maximum rows" is set to 99. (Apparently this has
nothing to do with the popups.)

A simple solution is to have the popup list be scrollable when the list exceeds
a certain number or height.

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

[kdevelop] [Bug 372286] C Parser fails to parse headers and reports errors

[Ted]

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

Ted <tedfed...@gmail.com> changed:

   What|Removed |Added

 CC||tedfed...@gmail.com

--- Comment #1 from Ted <tedfed...@gmail.com> ---
This is something that I ran into.  The problem I had was by use of pkg-config
in a Makefile that was not resolved by the parser.  I added all of these paths
manually into Project->Open Configuration->Includes/Imports.

Also take a look at the "Problems" tab.  If there are any issues shown in RED
due to missing include files then the parse will not work at all.

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

[kdevelop] [Bug 370928] Kdevelop parser issues with with typedefs not recognized.

[Ted]

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

--- Comment #3 from Ted <tedfed...@gmail.com> ---
I would like to add a comment that may help others stumbling across this issue.

If there are any RED issues reported in Problems for include files, the parser
will not work.  You must resolve these problems in order for the parser to work
again.

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

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

[Ted]

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

--- Comment #7 from Ted <tedfed...@gmail.com> ---
I would like to add a comment that may help others stumbling across this issue.

If there are any RED issues reported in Problems for include files, the parser
will not work.  You must resolve these problems in order for the parser to work
again.

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

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

[Ted]

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

--- Comment #5 from Ted <tedfed...@gmail.com> ---
I must say that with my issues resolved, the Background parser is working very
well.  I am very impressed with Kdevelop 5.x.x.

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

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

[Ted]

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

Ted <tedfed...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #4 from Ted <tedfed...@gmail.com> ---
The whole problem was relying on the Makefile to supply the include paths.
Apparently KDevelop does not parse pkg-config entires in the Makefile.
I added the needed include files paths in Kdevelop and resolved the problem.

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

[kdevelop] [Bug 370928] Kdevelop parser issues with with typedefs not recognized.

[Ted]

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

Ted <tedfed...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #2 from Ted <tedfed...@gmail.com> ---
The whole problem was relying on the Makefile to supply the include paths.
Apparently KDevelop does not parse pkg-config entires in the Makefile.
I added the needed include files paths in Kdevelop and resolved the problem.

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

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

[Ted]

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

--- Comment #3 from Ted <tedfed...@gmail.com> ---
Looks like this has boiled down to the lack of pkg-config support.
I am using glib and in my Makefile I use `pkg-config  glib-2.0 --cflags`
As you may know, this will provide the paths:
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
It appears that the clang parser will not be able to parse if these paths are
not present and hence the strange behavior with the STL includes.

Is there a way to add the pkg-config support into the parser?

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

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

[Ted]

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

--- Comment #2 from Ted <tedfed...@gmail.com> ---
Further strangeness:

I have found while initially reparsing my project with the only change in 
project->Open Configuration...->Language Support
_GLIBCXX_USE_CXX11_ABI 0

std::string
Show correctly
typedef basic_string< char, std< char >, std< char > > string
Container: std Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

But somewhere during the reparsing back to this:

typedef int string
Container: std Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

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

[kdevelop] [Bug 373973] Kdevelop clang parser has many issues

[Ted]

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

--- Comment #1 from Ted <tedfed...@gmail.com> ---
The settings I am referring to are under 
project->Open Configuration...->Language Support

Maybe this is an issue with c++11 v.s. older ABI
When I pulled up a project that had c++11 for the language version then I do
see std::string interpreted correctly:

typedef basic_string< char, std< char >, std< char > > string
Container: __cxx11 Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

If I try to use 03 it reverts to this:
typedef int string
Container: __cxx11 Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

If I include the define for _GLIBCXX_USE_CXX11_ABI 0 then back to this:
(Using 03 or 11, doesn't matter).
typedef int string
Container: std Kind: Typedef 
Decl.: stringfwd.h :74 Show uses

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

[kdevelop] [Bug 373973] New: Kdevelop clang parser has many issues

[Ted]

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

Bug ID: 373973
   Summary: Kdevelop clang parser has many issues
   Product: kdevelop
   Version: 5.0.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (Clang-based)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: tedfed...@gmail.com
  Target Milestone: ---

I have spent a lot of time playing with the Kdevelop configuration for the C++
parser.  However I cannot get the clang parser to work with STL header (for
example).

I am not using c++11 but even with the default settings of std=c++11, the STL
headers are not fully recognized.  

If I explicitly include a path to find /usr/include/c++/6.2.1 then the STL
headers are found, but typedefs are not recognized.

Simple example.

#include 
using namespace std;

string myString;

This is what the parser will show for string.

typedef int string
Container: std Kind: Typedef 
Decl.: stringfwd.h :74 Show uses


It does not seem to find the real typedef which should be:

typedef basic_stringstring;

My guess is that the clang parser is not going deep enough to resolve these
types.  It appears it gives up and the uses the default type of int for
anything it doesn't know.

What are the correct settings to get the clang parser to work?
I have spent hours on trying to find a solution to no avail.

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

[kdevelop] [Bug 370928] Kdevelop parser issues with with typedefs not recognized.

[Ted via KDE Bugzilla]

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

--- Comment #1 from Ted <tedfed...@gmail.com> ---
Forgot one typedef:

typedef int afdx_hdl_t;

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

[kdevelop] [Bug 370928] New: Kdevelop parser issues with with typedefs not recognized.

[Ted via KDE Bugzilla]

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

Bug ID: 370928
   Summary: Kdevelop parser issues with with typedefs not
recognized.
   Product: kdevelop
   Version: 5.0.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP (old)
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: tedfed...@gmail.com

I have  a CPP file with some typedef's and variables declarations.
These do not appear to get recognized by the parser unless I have the
declaration right before the usage in the .cpp file.




Reproducible: Always


Actual Results:  
Parser flags valid code as error.

Expected Results:  
Parser should not flag these as errors.

Here is an example:

typedef map TX_PORT_MAP_T;
typedef struct VL_ENTRY_T
{
afdx_hdl_tVL_Hdl;
TX_PORT_MAP_TportMap;
}VL_ENTRY;
typedef map TX_VL_MAP_T;
TX_VL_MAP_T m_TxVlMap;

.

TX_VL_MAP_T::iterator vlMapIter = m_TxVlMap.find(txVLInfo.VL_ID);

I show these errors with the parser unless the above declarations appear
immediately above the usage.

Problem in Semantic analysis
'TX_VL_MAP_T' (aka 'int') is not a class, namespace, or enumeration

m_TxVlMap
Problem in Semantic analysis
Member reference base type 'TX_VL_MAP_T' (aka 'int') is not a structure or
union

This code compiles with no warnings/errors.

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

[kdevelop] [Bug 369883] New: Ctrl-f only works first time to select text for Find

[Ted via KDE Bugzilla]

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

Bug ID: 369883
   Summary: Ctrl-f only works first time to select text for Find
   Product: kdevelop
   Version: 5.0.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: all editors
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: tedfed...@gmail.com

The first time I bring up Kdevelop with the Kate editor I can select some text
in the code and press Ctrl-f to use the selected text for Find (i.e. search the
code for the next or previous instance of the text).

Subsequent selections of text do not use the selected text for Find, but
instead I only get the first selection.
I have to use Ctrl-c, Ctrl-v to get new text in the Find selection box. 

Reproducible: Always

Steps to Reproduce:
1. Highlight text with mouse
2. Press Ctrl-f to use highlighted text for Find
3. Try this again

Actual Results:  
Works first time, not subsequent times.

Expected Results:  
Should work every time.

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

[dolphin] [Bug 368465] New: Dolphin crashed on its own

[Ted Ma via KDE Bugzilla]

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

Bug ID: 368465
   Summary: Dolphin crashed on its own
   Product: dolphin
   Version: 15.04.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ma...@arcturusnetworks.com

Application: dolphin (15.04.0)
KDE Platform Version: 4.14.9 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 3.16.7-42-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
  - 30 minutes after reboot after Power Failure
  - Many windows restored (KDE automatic)
  - accessing Chrom via Thunderbird
  - may have been swapping
  - three Dolphin instances crashed (of 30-40)

The crash does not seem to be reproducible.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff8006c7780 (LWP 3654))]

Thread 3 (Thread 0x7ff7e2975700 (LWP 3657)):
#0  0x7ff7fdcf888d in poll () at /lib64/libc.so.6
#1  0x7ff7fae0bbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff7fae0bcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff7ff3590de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7ff7ff32ae6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7ff7ff32b165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7ff7ff2280bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7ff7ff30f8dd in  () at /usr/lib64/libQtCore.so.4
#8  0x7ff7ff22a79f in  () at /usr/lib64/libQtCore.so.4
#9  0x7ff7fef940a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7ff7fdd00cbd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7ff7e1b47700 (LWP 3674)):
#0  0x7ff7fdcf888d in poll () at /lib64/libc.so.6
#1  0x7ff7fae0bbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff7fae0bcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff7ff3590de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7ff7ff32ae6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7ff7ff32b165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7ff7ff2280bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7ff7ff22a79f in  () at /usr/lib64/libQtCore.so.4
#8  0x7ff7fef940a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7ff7fdd00cbd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7ff8006c7780 (LWP 3654)):
[KCrash Handler]
#5  0x7ff7fdc510a7 in raise () at /lib64/libc.so.6
#6  0x7ff7fdc52458 in abort () at /lib64/libc.so.6
#7  0x7ff7f8f7f2a5 in  () at /lib64/libdbus-1.so.3
#8  0x7ff7f8f75ee1 in  () at /lib64/libdbus-1.so.3
#9  0x7ff7f8f76481 in  () at /lib64/libdbus-1.so.3
#10 0x7ff7f8f6bb59 in dbus_get_local_machine_id () at /lib64/libdbus-1.so.3
#11 0x7ff7e0cae06c in IBus::Bus::getSocketPath() () at
/usr/lib64/libibus-qt.so.1
#12 0x7ff7e0cb0a36 in IBus::Bus::slotAddressChanged(QString const&) () at
/usr/lib64/libibus-qt.so.1
#13 0x7ff7e0cc2132 in  () at /usr/lib64/libibus-qt.so.1
#14 0x7ff7ff3401fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#15 0x7ff7ff2fbe95 in QFileSystemWatcher::directoryChanged(QString const&)
() at /usr/lib64/libQtCore.so.4
#16 0x7ff7ff34459e in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#17 0x7ff7fe4a876c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#18 0x7ff7fe4aecad in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#19 0x7ff8000cfe0a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#20 0x7ff7ff32c2ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#21 0x7ff7ff32f57d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#22 0x7ff7ff3598fe in  () at /usr/lib64/libQtCore.so.4
#23 0x7ff7fae0ba04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#24 0x7ff7fae0bc48 in  () at /usr/lib64/libglib-2.0.so.0
#25 0x7ff7fae0bcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#26 0x7ff7ff3590be in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#27 0x7ff7fe545676 in  () at /usr/lib64/libQtGui.so.4
#28 0x7ff7ff32ae6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#29 0x7ff7ff32b165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#30 0x7ff7ff3305b9 in 

[krita] [Bug 359014] Top most text-menu (File, edit, view...) gets unresponsive when in fullscreen mode on windows 10.

[Ted Nielsen via KDE Bugzilla]

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

--- Comment #9 from Ted Nielsen <ted.project@gmail.com> ---
I´ll see if I can find another system to test on. For now, it works to just use
the shortcut (ctrl+shift+F) to get out of fullscreen mode when I need to. Guess
I´ll just have to learn common shortcuts ;)

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

[muon] [Bug 359430] New: could not finish updater

[ted via KDE Bugzilla]

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

Bug ID: 359430
   Summary: could not finish updater
   Product: muon
   Version: 2.2.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: notifier
  Assignee: echidna...@kubuntu.org
  Reporter: te...@o2.pl
CC: aleix...@kde.org, sit...@kde.org

not finish update  video core

Reproducible: Always


Actual Results:  
could not finish process

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

[krita] [Bug 359014] Top most text-menu (File, edit, view...) gets unresponsive when in fullscreen mode on windows 10.

[Ted Nielsen via KDE Bugzilla]

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

--- Comment #6 from Ted Nielsen <ted.project@gmail.com> ---
That´s really odd then. It´s definitely not present in the latest official
(2.9) release.

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

[krita] [Bug 359014] Top most text-menu (File, edit, view...) gets unresponsive when in fullscreen mode on windows 10.

[Ted Nielsen via KDE Bugzilla]

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

--- Comment #4 from Ted Nielsen <ted.project@gmail.com> ---
Tried again as soon as I came home, tried to pinpoint whats happening. If I
just open up Krita and go fullscreen before opening a canvas, the menus still
work fine, but as soon as I create a canvas, the menu then becomes
unresponsive. I can still paint, change brushes, and other parts of the UI
remain responsive.

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

[krita] [Bug 359014] Top most text-menu (File, edit, view...) gets unresponsive when in fullscreen mode on windows 10.

[Ted Nielsen via KDE Bugzilla]

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

--- Comment #1 from Ted Nielsen <ted.project@gmail.com> ---
bug was presenty in alpha 1 as well for me

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

[krita] [Bug 359014] New: Top most text-menu (File, edit, view...) gets unresponsive when in fullscreen mode on windows 10.

[Ted Nielsen via KDE Bugzilla]

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

Bug ID: 359014
   Summary: Top most text-menu (File, edit, view...) gets
unresponsive when in fullscreen mode on windows 10.
   Product: krita
   Version: 3.0 Alpha
  Platform: MS Windows
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: ted.project@gmail.com

Top most text-menu (File, edit, view...) gets unresponsive when in fullscreen
mode on windows 10. This is for the pre-alpha 2 build provided on krita.org

Reproducible: Always

Steps to Reproduce:
1. put krita in full screen mode through the view menu
2. draw some strokes (not sure if this is needed, but it was what I did)
3. try to click on any of the text menus

Actual Results:  
no menus appear when clicking

Expected Results:  
menus should appear when clicking

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

[plasmashell] [Bug 349519] plasmashell occasionally crashes

[Ted Henscheid via KDE Bugzilla]

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

Ted Henscheid <thensch...@yahoo.com> changed:

   What|Removed |Added

 CC||thensch...@yahoo.com

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

[dolphin] [Bug 356375] New: Dolphin crashes (only one instance)

[Ted Ma via KDE Bugzilla]

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

Bug ID: 356375
   Summary: Dolphin crashes (only one instance)
   Product: dolphin
   Version: 15.04.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ma...@arcturusnetworks.com

Application: dolphin (15.04.0)
KDE Platform Version: 4.14.9 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 3.16.7-29-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
Opening a link (from Thunderbird 38.3.0) -> Chrome (47.0.2526.73 (64-bit)). 
Only the Dolphin instances in one Virtual Desktop seem to be affected

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1e6f132780 (LWP 20331))]

Thread 3 (Thread 0x7f1e518e9700 (LWP 20332)):
#0  0x7f1e6da02a9d in read () at /lib64/libpthread.so.0
#1  0x7f1e698b4750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f1e69873714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f1e69873b7b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f1e69873cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f1e6ddc10de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#6  0x7f1e6dd92e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f1e6dd93165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#8  0x7f1e6dc900bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#9  0x7f1e6dd778dd in  () at /usr/lib64/libQtCore.so.4
#10 0x7f1e6dc9279f in  () at /usr/lib64/libQtCore.so.4
#11 0x7f1e6d9fc0a4 in start_thread () at /lib64/libpthread.so.0
#12 0x7f1e6c76908d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f1e50ac9700 (LWP 20333)):
#0  0x7f1e6c760c5d in poll () at /lib64/libc.so.6
#1  0x7f1e69873be4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f1e69873cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f1e6ddc10de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#4  0x7f1e6dd92e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#5  0x7f1e6dd93165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f1e6dc900bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x7f1e6dc9279f in  () at /usr/lib64/libQtCore.so.4
#8  0x7f1e6d9fc0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f1e6c76908d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f1e6f132780 (LWP 20331)):
[KCrash Handler]
#5  0x7f1e6c6b9187 in raise () at /lib64/libc.so.6
#6  0x7f1e6c6ba538 in abort () at /lib64/libc.so.6
#7  0x7f1e679e82a5 in  () at /lib64/libdbus-1.so.3
#8  0x7f1e679deee1 in  () at /lib64/libdbus-1.so.3
#9  0x7f1e679df481 in  () at /lib64/libdbus-1.so.3
#10 0x7f1e679d4b59 in dbus_get_local_machine_id () at /lib64/libdbus-1.so.3
#11 0x7f1e4bba606c in IBus::Bus::getSocketPath() () at
/usr/lib64/libibus-qt.so.1
#12 0x7f1e4bba8a36 in IBus::Bus::slotAddressChanged(QString const&) () at
/usr/lib64/libibus-qt.so.1
#13 0x7f1e4bbba132 in  () at /usr/lib64/libibus-qt.so.1
#14 0x7f1e6dda81fa in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#15 0x7f1e6dd63e95 in QFileSystemWatcher::directoryChanged(QString const&)
() at /usr/lib64/libQtCore.so.4
#16 0x7f1e6ddac59e in QObject::event(QEvent*) () at
/usr/lib64/libQtCore.so.4
#17 0x7f1e6cf1076c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#18 0x7f1e6cf16cad in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#19 0x7f1e6eb37e0a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#20 0x7f1e6dd942ad in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#21 0x7f1e6dd9757d in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQtCore.so.4
#22 0x7f1e6ddc18fe in  () at /usr/lib64/libQtCore.so.4
#23 0x7f1e69873a04 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#24 0x7f1e69873c48 in  () at /usr/lib64/libglib-2.0.so.0
#25 0x7f1e69873cec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#26 0x7f1e6ddc10de in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#27 0x7f1e6cfad676 in  () at /usr/lib64/libQtGui.so.4
#28 0x7f1e6dd92e6f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#29 0x7f1e6dd93165 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#30 0x7f1e6dd985b9 in