[kdevelop] [Bug 371474] New: "Use KDE color scheme" in "Fonts & Colors" options dialog is saving new color scheme without clicking save button destroying color scheme

2016-10-21 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371474

Bug ID: 371474
   Summary: "Use KDE color scheme" in "Fonts & Colors" options
dialog is saving new color scheme without clicking
save button destroying color scheme
   Product: kdevelop
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: edwin.jablonski...@gmail.com

As title says. 

Example: When I choose Dark breeze and click Use KDE color scheme, Dark breeze
scheme will be rewritten without asking my If I'm sure or waiting for me to
click save. This can't be undone so Dark breeze is rewritten by whatever color
scheme KDE actually used.

That operation should be reversible AND saved to config file or whatever AFTER
clicking save button.  

Reproducible: Always

Steps to Reproduce:
Click "Use KDE color scheme" in "Fonts & Colors" options.

Actual Results:  
Color scheme changed without my permission

Expected Results:  
Waiting for save button

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


[kwin] [Bug 370917] KWin is putting newly opened windows on random screen

2016-10-19 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370917

--- Comment #8 from Edwin  ---
(In reply to Martin Gräßlin from comment #7)
> please also xprop

_NET_WM_ICON_GEOMETRY(CARDINAL) = 269, 741, 34, 26
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE,
_NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT,
_NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN,
_NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 0, 0, 27, 0
_NET_FRAME_EXTENTS(CARDINAL) = 0, 0, 27, 0
_NET_WM_DESKTOP(CARDINAL) = 0
_KDE_NET_WM_ACTIVITIES(STRING) = "c626d536-f6d6-4f54-bc60-be04d1f16682"
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_STATE(ATOM) = 
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x4400020
bitmap id # of mask for icon: 0x4400023
window id # of group leader: 0x441
XdndAware(ATOM) = BITMAP
_MOTIF_DRAG_RECEIVER_INFO(_MOTIF_DRAG_RECEIVER_INFO) = 0x6c, 0x0, 0x5, 0x0,
0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x10, 0x0, 0x0, 0x0
_NET_WM_ICON(CARDINAL) =Icon (22 x 22):


  ░░  
  ▒▒  
 ▒  ▒ 
▒░  ░▒
   ░░░░   
  ░▒  ▒░  
  ▒░  ░▒  
 ▒░░▒▒▓▓▒ 
▒▒░░▒▒▓▓▓▒
   ░▒░░▒▓▓░   
   ▓▓░░▒▓▓▓   
  ▒▓▓▓▒░▓▓▓▒  
  ░▒▓▓▓░  
▒▒
 ░▓▓░ 
   ▒▓▓▒   
▒▒
  ▓▓░ 



Icon (16 x 16):


   ▒▒   
  ░  ░  
 ░░  ░░ 
 ▒░ 
▒░░▒
   ▒░░▒▒▒▓▓▓▒   
  ░▒░▒▓▓▓░  
 ░▓▓░▒░ 
  ▒▓▓▒▓▓▓▒░ 
   ▒▒   
░▓▓░
  ▒▓▓▒  
   ░░   


Icon (48 x 48):




   ░░   
   ▒▒   
    
 ▒▒░░▒▒ 
░▒▒  ▒▒░
▒▒▒▒
   ▒▒░░▒▒   
  ▒▒▒  ░▒▒  
 ░▓▒▒▓░ 
 ▒▒  ▒▒ 
▒▓░  ░▓▒
   ▒▓▒  ░ ░▓▒   
  ░▓▒░ ▒▓░  
 ░▓▓░ ░░▒▓░ 
 ▒▓░  ░░░▓▒ 
▒▓▒  ░░░▒▓▓▒
   ▒▓▒░   ░░▒▓▓▓▒   
  ░▓▓░ ░░▒▓▓▓░  
  ▓▓▒ ░░░▒  
 ▒▓▒░░▒▓▓▓▒ 
▒▓▒░▓▓▓▒
   ░▓▓░░▒▓▓▓░   
   ▓▓▓▒░░░  
  ▒▒░▒  
 ▒▓▓▒▓▒ 
▒▒░░░▒▓▒
░▓▓░░▒▓▒
  ▓▓▒▒  
   ▒▓▒▓▓▒   
░▓▓░
  ▒▓▓▒  
   ░░   
 ▒▓ 
  ░▓▓▒  

 ▒▒ 
  ░▓▓░  
▒▓▓▒
 ░░ 
   ▓▓   





Icon (24 x 24):


   ░░   
   ▒▒   
  ▒  ▒  
 ▒░  ░▒ 
░▒▒░
▒  ▒
   ▒░  ░▒   
  ▒░   ░▒▒  
 ░▒░░▒▒▓▓▓░ 
 ▒░░░▒▒ 
▒░░░▓▓▓▒
   ▒▓▒░░▒▓▓▓▒   
  ▒▓▓▓▒░▒▒  
  

[kwin] [Bug 370917] KWin is putting newly opened windows on random screen

2016-10-18 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370917

--- Comment #6 from Edwin  ---
(In reply to Martin Gräßlin from comment #5)
> > Setting to 'Focus follows mouse' definitely made things better for every 
> > application except GTK based. Not sure if it's KWin's issue or just GTK do 
> > not follow rules. If latter then this bug report can be closed. Thank you.
> 
> Please provide output of xwininfo on such a window.

xwininfo: Window id: 0x42b "New document 1 - Inkscape"

  Absolute upper-left X:  1366
  Absolute upper-left Y:  27
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 1360
  Height: 711
  Depth: 24
  Visual: 0x20
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x22 (installed)
  Bit Gravity State: NorthWestGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +1366+27  -0+27  -0-30  +1366-30
  -geometry 1360x711-0+0


Document properties dialog window goes **always** to primary screen.

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

[kwin] [Bug 370917] KWin is putting newly opened windows on random screen

2016-10-17 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370917

--- Comment #4 from Edwin  ---
(In reply to Martin Gräßlin from comment #3)
> > Active screen follows mouse: no
> 
> Please try changing this option and check whether it works better for you.
> It's Systemsettings -> Window Behavior -> Window Actions and Behavior, all
> way down checkbox "active screen follows mouse".

Setting to 'Focus follows mouse' definitely made things better for every
application except GTK based. Not sure if it's KWin's issue or just GTK do not
follow rules. If latter then this bug report can be closed. Thank you.

BUT! There is 'Placement' option in 'Advanced' tab in 'Window Action and
Behavior' and I did set it to 'Under mouse' and I was sure this is what should
make windows appear on a screen I'm currently on. This is kinda confusing and
made me believe that regardless of this setting plasma is placing windows in
willy-nilly fashion. Some clarification in options would be great. Anyways -
thanks again.

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

[kwin] [Bug 370917] KWin is putting newly opened windows on random screen

2016-10-16 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370917

--- Comment #2 from Edwin  ---
(In reply to Martin Gräßlin from comment #1)
> Please provide output of:
> qdbus org.kde.KWin /KWin supportInformation

KWin Support Information:
The following information should be used when requesting support on e.g.
http://forum.kde.org.
It provides information about the currently running instance, which options are
used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a
paste bin service
like http://paste.kde.org instead of pasting into support threads.

==

Version
===
KWin version: 5.8.1
Qt Version: 5.7.0
Qt compile version: 5.7.0
XCB compile version: 1.11.1

Operation Mode: X11 only

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

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

Decoration
==
Plugin: org.kde.breeze
Theme: 
Blur: 0
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 2
decorationButtonsRight: 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

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

Screen Edges

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

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

Screen 0:
-
Name: LVDS1
Geometry: 0,0,1366x768
Refresh Rate: 60.0629

Screen 1:
-
Name: VGA1
Geometry: 1366,0,1360x768
Refresh Rate: 60.0629


Compositing
===
Compositing is active
Compositing Type: XRender

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

Currently Active Effects:
-

Effect Settings:

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

slidingpopups:
fadeInTime: 150
fadeOutTime: 250

kwin4_effect_login:

slide:

kwin4_effect_translucency:

screenshot:

kwin4_effect_windowaperture:

minimizeanimation:

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

kwin4_effect_fade:

kwin4_effect_morphingpopups:

kwin4_effect_maximize:

presentwindows:
layoutMode: 0
showCaptions: true
showIcons: true
doNotCloseWindows: false
ignoreMinimized: false
accuracy: 20
fillGaps: true
fadeDuration: 150
showPanel: false
leftButtonWindow: 1
rightButtonWindow: 2
middleButtonWindow: 0
leftButtonDesktop: 2
middleButtonDesktop: 0

[plasmashell] [Bug 370917] New: Plasma is putting newly opened windows on random screen

2016-10-15 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370917

Bug ID: 370917
   Summary: Plasma is putting newly opened windows on random
screen
   Product: plasmashell
   Version: master
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: edwin.jablonski...@gmail.com
CC: plasma-b...@kde.org

Laptop. KDE Neon 5.8.1 up-to-date, intel hd 3000 graphic card, open source
drivers.

When I plug in second screen plasma is showing windows randomly on one of the
screens. Got two panels, one for each screen. Plasma is randomly showing newly
opened windows on one of screens. No matter from what panel I start an
application. No matter how I will start an application - for example from
kicker, konsole, whatever. No matter if I click on one of the screens to
'activate' it or make a current one. Same with 'under mouse' placement option -
it's not working. There is no logic in where plasma is putting newly opened
windows.

Only setting KWin rule to show windows on screen: 1 is working but if I want
every new application to be shown on primary I need to set '*' rule what makes
dialogs of applications currently on second screen be shown on first screen.
And without this rule dialogs will, in many cases, be shown on different screen
that parent currently us. 

Reproducible: Always

Steps to Reproduce:
1. Install plasma 5
2. Plug in second monitor
3. Open new application, window, dialog

Actual Results:  
Windows and dialogs are randomly distributed between screens.

Expected Results:  
To follow 'Under mouse' option.
Keep dialogs on same screen that parent is.
When application is opened from a panel to show that application on a screen
that panel belongs to.

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


[plasmashell] [Bug 358471] Plasma desktop can crash when panels move between screens

2016-10-15 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358471

Edwin  changed:

   What|Removed |Added

 CC||edwin.jablonski...@gmail.co
   ||m

--- Comment #7 from Edwin  ---
Can confirm. Moving panel back and forth between screens will always crash
plasmashell.

KDE Neon 5.8.1, intel hd 3000

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


[valgrind] [Bug 328357] vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xEF 0x3 0x5 0x0

2016-04-29 Thread Török Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=328357

Török Edwin  changed:

   What|Removed |Added

 CC||edwin+...@etorok.net

--- Comment #8 from Török Edwin  ---
FWIW objdump  2.25.1 can decode these instructions.

$ valgrind /bin/ls
==6429== Memcheck, a memory error detector
==6429== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==6429== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==6429== Command: /bin/ls
==6429== 
vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xC6 0x5 0x3
0x0
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==6429== valgrind: Unrecognised instruction at address 0x40e62c.
==6429==at 0x40E62C: ??? (in /bin/ls)

$ objdump -d /bin/ls|grep 40e62c
40e62c:   8f ea f8 10 c6 05 03bextr  $0x305,%rsi,%rax

As a workaround I can compile my code with '-march=native -mno-tbm' instead of
just '-march=native', but it would be nice if valgrind supported this
instruction:
https://bugs.gentoo.org/show_bug.cgi?id=563796

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

[gwenview] [Bug 359091] New: Gwenview is taking >600MB of RAM when opening file.

2016-02-07 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359091

Bug ID: 359091
   Summary: Gwenview is taking >600MB of RAM when opening file.
   Product: gwenview
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: edwin.jablonski...@gmail.com
CC: myr...@kde.org

Gwenview is taking >600MB of RAM when opening file. File size/extension does
not matter.

Reproducible: Always

Steps to Reproduce:
1. Open image file in Gwenview
2.
3.

Actual Results:  
Gwenview is eating 1/4 of my RAM

Expected Results:  
I expect it to not eating 1/4 of my RAM

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


[kdialog] [Bug 358817] New: kdialog --passivepopup is not working

2016-01-31 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358817

Bug ID: 358817
   Summary: kdialog --passivepopup is not working
   Product: kdialog
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: br...@frogmouth.net
  Reporter: edwin.jablonski...@gmail.com

Plasma 5.5.3
Kubuntu 15.10 (with backports)
kdialog --passivepopup is not working. Console gives me nothing. 

Reproducible: Always


Actual Results:  
No notifications.

Expected Results:  
Notifications should be shown.

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


[dolphin] [Bug 357762] Opening root folder in Dolphin hangs entire system (Macbook 8,1) indefinitely.

2016-01-11 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357762

Edwin  changed:

   What|Removed |Added

 CC||edwin.jablonski...@gmail.co
   ||m

--- Comment #1 from Edwin  ---
Got same issue. Opening root dir in dolphin is killing any KB/MOUSE input - OS
is working, for example music still playing, ksysguard graphs still changing,
but keyboard and mouse are not responsive so I need to hard reset my machine.

Reproducible: Always

Plasma 5.4.3
Frameworks 5.15
Ubuntu 15.10 (Qt 5.4.2)

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


[kwin] [Bug 357837] New: All windows goes to secondary monitor when plugged in.

2016-01-11 Thread Edwin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357837

Bug ID: 357837
   Summary: All windows goes to secondary monitor when plugged in.
   Product: kwin
   Version: 5.4.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: edwin.jablonski...@gmail.com

No matter what options I will choose in settings (Primary, Secondary Display)
or what rules I will create when I plug in secondary monitor all windows goes
to that secondary monitor. I can move them back to primary but dialogs appears
on secondary even if application window is on primary. Does not matter if
application is GTK or QT based but java applications just appears on center of
both screens (one half on secondary, one half on primary). 

Ubuntu 15.10
QT 5.4.2
Plasma 5.4.3
Frameworks 5.15
Open source intel (HD3000) drivers

Reproducible: Always

Steps to Reproduce:
1. Plug in secondary monitor


Actual Results:  
Windows goes to secondary screen when plugged in.

Expected Results:  
Windows stays on primary when pluggin in secondary monitor.

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