[kwin] [Bug 401535] New: group windows with tabs

2018-11-29 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=401535

Bug ID: 401535
   Summary: group windows with tabs
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br
  Target Milestone: ---

This is a very interesting function.  To group windows with tabs as a browser
do.

There is a software that does that for windows, which looks very nice: Groupy
-> https://www.stardock.com/products/groupy/

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

[systemsettings] [Bug 396878] New: Display scaling does not work when going back to 1

2018-07-26 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=396878

Bug ID: 396878
   Summary: Display scaling does not work when going back to 1
   Product: systemsettings
   Version: 5.12.6
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_fonts
  Assignee: unassigned-b...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br
CC: unassigned-b...@kde.org
  Target Milestone: ---

Under System Setings -> Display and Monitor -> Display -> Scale Display.

If I change it from 1, when I want to reset to 1, it will behave as a 2.

I can see that changing here, seems to be the same as changing SS -> Fonts ->
Force fonts DPI.  It will be enabled and changed to a 96 factor (192 in 2x).

When I go back to 1x, this option will be unchecked and the default should be
96, which is not applied.  I have to force 96 dpi in order to get what I had in
the first place.

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

[yakuake] [Bug 396814] New: Yakuake does not like scaled display

2018-07-24 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=396814

Bug ID: 396814
   Summary: Yakuake does not like scaled display
   Product: yakuake
   Version: 3.0.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br
  Target Milestone: ---

Created attachment 114094
  --> https://bugs.kde.org/attachment.cgi?id=114094&action=edit
yakuake white lines on scale

I have my display scaled to 1.3.

This makes yakuake get its position wrong - on a dual head, it aligns left on
the right head and aligns right on the left head, where should it be centered.

Most of time it display a few white lines in the terminal, as if it has lost a
pixel in the scaling process.

I know kde scaling is far from optimal, however this behaviour is not shown in
Konsole.

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

[plasma-pa] [Bug 389622] can't switch output over multiple HDMIs/DPs

2018-01-30 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=389622

Raul Kde Bugzilla  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

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

[plasma-pa] [Bug 389622] New: can't switch output over multiple HDMIs/DPs

2018-01-29 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=389622

Bug ID: 389622
   Summary: can't switch output over multiple HDMIs/DPs
   Product: plasma-pa
   Version: 5.11.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: raul_kde_bugzi...@dias.com.br
CC: plasma-b...@kde.org
  Target Milestone: ---

When there are more than one HDMI or Display Port display connected, plasma-pa
does not let you switch which HDMI/DP should receive the audio stream.

Using other frontends this can be done fine.

e.g. on pavucontrol-qt, I can go to Configuration tab and switch the profile
over  all available ports.

In case this is a video card specific bug, mine is a Nvidia 1080 GTX.

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

[plasmashell] [Bug 386717] New: Panel stops updating when running Coutner-Strike: Global Offensive in the background

2017-11-10 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=386717

Bug ID: 386717
   Summary: Panel stops updating when  running Coutner-Strike:
Global Offensive in the background
   Product: plasmashell
   Version: 5.11.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br
  Target Milestone: 1.0

When running CS:GO (fullscreen), if I ALT-TAB it to the desktop, the panel is
does not update.

However it still works.  Mouse over, tooltips still responds fine.  The
displayed data is the same as the time the game started.

If I close the game, the panel comes back to updating itself.

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

[dolphin] [Bug 380349] Some remote (sftp) files are opened via temp-file instead of remote URL although command is "kwrite %u"

2017-09-06 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=380349

Raul Kde Bugzilla  changed:

   What|Removed |Added

 CC||raul_kde_bugzi...@dias.com.
   ||br

--- Comment #3 from Raul Kde Bugzilla  ---
This bug has being around for a long time.
Since kde 4 if I am not mistaken.

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

[dolphin] [Bug 384437] New: Dolphin does not respect Command arguments for opening remote file types

2017-09-06 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=384437

Bug ID: 384437
   Summary: Dolphin does not respect Command arguments for opening
remote file types
   Product: dolphin
   Version: 16.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br
CC: elvis.angelac...@kde.org
  Target Milestone: ---

This might be owned by kio sftp or some other generic component.

When opening a remote ssh text file (sftp) in dolphin:
1 - Right click on the file
2 - Open With... (or other if there is an association already)
3 - type: kate %U
4 - Mark the checkbox "Remember application "
5 - OK

The file will open in kate and kate will know it is a remote file and save it
thru sftp as expected.
e.g. [10.1.2.3]folder\_file

Now with the association, there is a context menu "Open with kate".
When using it it shows as:
14213_0\_file

As I understand, in this case is the same behaviour as not using %U in the kate
call.

Dolphin/kio copies the file to some temporary folder and then passes to kate.

If I enter the file association in Properties -> File Type Options ->
Application Preference Order -> kate -> Edit -> Application:

The command is "kate %U" as expected.

So, Dolphin does not respect the %U argument in the associated call.

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

[kate] [Bug 383005] New: line-height smaller than font size

2017-08-01 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=383005

Bug ID: 383005
   Summary: line-height smaller than font size
   Product: kate
   Version: 16.12
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br
  Target Milestone: ---

When using HiDPI with dpi set to 120, the line height of the text becomes too
small to acommodate the text heigh.

When this happens, some parts of the text are cropped.

If there is some ""_"" (underlines) in the text, it is shown as blanks.

On dpi 96 this does not happen.

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

[KScreen] [Bug 382277] New: Scale display below 1

2017-07-12 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=382277

Bug ID: 382277
   Summary: Scale display below 1
   Product: KScreen
   Version: 5.10.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: se...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br
  Target Milestone: ---

The scale in Scale display option should allow for values below 1.

Without it, we are only able to work around with the xrand option --scale which
is not optimal.

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

[plasmashell] [Bug 382276] Plasma does not detect total display area when scaling

2017-07-12 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=382276

--- Comment #2 from Raul Kde Bugzilla  ---
The display card is a NVidia.
Driver: nvidia-375
Kubuntu (ubuntu + kubuntu backports) 17.04

About the Screenshot, the black area in the left is where plasma fails to see
and use.  Note the "add widgets" button on the top right, not being in the top
right.

Also note that I am able to use this space fine, as I placed a konsole terminal
in there.

The black area in the top of the right display is correct, as there is an
height offset between the two displays to match the physical position.

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

[plasmashell] [Bug 382276] Plasma does not detect total display area when scaling

2017-07-12 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=382276

--- Comment #1 from Raul Kde Bugzilla  ---
raul@nostromo:~$ xrandr --verbose
Screen 0: minimum 8 x 8, current 5440 x 1740, maximum 32767 x 32767
HDMI-0 disconnected (normal left inverted right x axis y axis)
Identifier: 0x1be
Timestamp:  594350
Subpixel:   unknown
Clones:
CRTCs:  0 1 2 3
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
BorderDimensions: 4 
supported: 4
Border: 0 0 0 0 
range: (0, 65535)
SignalFormat: TMDS 
supported: TMDS
ConnectorType: HDMI 
ConnectorNumber: 2 
_ConnectorLocation: 2 
DP-0 connected primary 2560x1440+2880+300 (0x1c0) normal (normal left inverted
right x axis y axis) 382mm x 214mm
Identifier: 0x1bf
Timestamp:  594350
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2 3
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
Backlight: 100 
range: (0, 100)
EDID: 
000006af9610e426e270
001a0104a52615780230c0a556559e26
0d4f560001010101010101010101
01010101010128c300a0a0a05a503020
35007ed6101828c300a0a0a05456
302035007ed6101800fe0041
554f0a20202020202020202000fe
004231373351544e30312e30200a0060
BorderDimensions: 4 
supported: 4
Border: 0 0 0 0 
range: (0, 65535)
SignalFormat: DisplayPort 
supported: DisplayPort
ConnectorType: Panel 
ConnectorNumber: 3 
_ConnectorLocation: 3 
  2560x1440 (0x1c0) 499.600MHz -HSync -VSync *current +preferred
h: width  2560 start 2608 end 2640 total 2720 skew0 clock 183.68KHz
v: height 1440 start 1443 end 1448 total 1530   clock 120.05Hz
  2560x1440 (0x1c1) 499.600MHz -HSync -VSync
h: width  2560 start 2608 end 2640 total 2720 skew0 clock 183.68KHz
v: height 1440 start 1443 end 1448 total 3060   clock  60.02Hz
DP-1 disconnected (normal left inverted right x axis y axis)
Identifier: 0x1c2
Timestamp:  594350
Subpixel:   unknown
Clones:
CRTCs:  0 1 2 3
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
BorderDimensions: 4 
supported: 4
Border: 0 0 0 0 
range: (0, 65535)
SignalFormat: DisplayPort 
supported: DisplayPort
ConnectorType: DisplayPort 
ConnectorNumber: 4 
_ConnectorLocation: 4 
DP-2 connected 2880x1620+0+0 (0x1c4) normal (normal left inverted right x axis
y axis) 477mm x 268mm
Identifier: 0x1c3
Timestamp:  594350
Subpixel:   unknown
Gamma:  1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC:   1
CRTCs:  0 1 2 3
Transform:  1.50 0.00 0.00
0.00 1.50 0.00
0.00 0.00 1.00
   filter: 
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0 
EDID: 
000010ac72a04d5a5731
1616010380301b78ea01f5a257529f27
0a5054a54b00714f8180d1c001010101
010101010101023a801871382d40582c
4500dd0c111e00ff004e3846
334d32354f31575a4d0a00fc0044
454c4c204532323131480a2000fd
00384c1e5311000a202020202020001f
BorderDimensions: 4 
supported: 4
Border: 0 0 0 0 
range: (0, 65535)
SignalFormat: TMDS 
supported: TMDS
ConnectorType: DisplayPort 
ConnectorNumber: 4 
_ConnectorLocation: 4 
  1920x1080 (0x1c4) 148.500MHz +HSync +VSync *current +preferred
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  67.50KHz
v: height 1080 start 1084 end 1089 total 1125   clock  60.00Hz
  1280x1024 (0x1c5) 135.000MHz +HSync +VSync
h: width  1280 start 1296 end 1440 total 1688 skew0 clock  79.98KHz
v: height 1024 start 1025 end 1028 total 1066   clock  75.02Hz
  1280x1024 (0x1c6) 108.000MHz +HSync +VSync
h: width  1280

[plasmashell] [Bug 382276] New: Plasma does not detect total display area when scaling

2017-07-12 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=382276

Bug ID: 382276
   Summary: Plasma does not detect total display area when scaling
   Product: plasmashell
   Version: 5.10.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: raul_kde_bugzi...@dias.com.br
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 106583
  --> https://bugs.kde.org/attachment.cgi?id=106583&action=edit
Screenshot of plasma not detecting full display scaled

When rescaling one monitor in a dual-head setup, plasma does not detect to new
display area and leave it blank (black).

In this sample the display on the left is a 1920x1080 and the one on the right
is 2560x1440 (notebook).

This is the xrandr line to set it up:
xrandr --output DP-2 --mode 1920x1080 --scale 1.5x1.5 --output DP-0 --pos
2880x300

I will post the output of xrandr --verbose in the next comment.

Attached is a screenshot of the effect.

It is important to note that this would not be necessary if the Scale (in
System Settings -> Display and Monitor -> Scale Display) accepted values below
1.

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

[kscreenlocker] [Bug 374289] multiscreen locks stealing focus

2016-12-29 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=374289

Raul Kde Bugzilla  changed:

   What|Removed |Added

 CC||raul_kde_bugzi...@dias.com.
   ||br

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

[kscreenlocker] [Bug 374289] New: multiscreen locks stealing focus

2016-12-29 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=374289

Bug ID: 374289
   Summary: multiscreen locks stealing focus
   Product: kscreenlocker
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br
CC: bhus...@gmail.com, mgraess...@kde.org
  Target Milestone: ---

kscreenlocker is 5.8.4.  Not in bugzilla version list.

Using more than one head (2 or 3) with a notebook.
After screens are off, waking up the system, like with a key press, the
displays turns on in very slow way.  This is probably xorg, xrandr, prime
issue.

The primary display (LVDS1) turns on very fast, the others about 3s-5s each
(serialized).

The problem with this is that each screen has its one locker password widgets. 
And each time one screen comes on, it will steal the focus from the previous.

So, If it is a 3-head, and the password is "foobaragain", I might get "foo" in
the first head, "bar" in the second and "again" in the 3rd.

This is very annoying, btw.

I understand what is going on.  Each screen have different resolution, DPI,
etc.  So each needs each on control set.  

The first one needs to steal the focus as it could be with any application.  
However, this is not true for the 2nd and 3rd controls.

At least the controls should be able to sync the input and then wouldn't matter
who really have the focus.

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

[kde] [Bug 371710] New: About KDE Menu entry does not show verions

2016-10-26 Thread Raul Kde Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371710

Bug ID: 371710
   Summary: About KDE Menu entry does not show verions
   Product: kde
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br
  Target Milestone: ---

Using KDE 4.7.5 in Kubuntu 16.10.
First, notice that the version in bugzilla stops at 4.14.1!!

Using the Menu:
Help -> About KDE
It is expected to see which version KDE is running (at least this particular
application was compiled against).
This is specially important on upgrades and multiple versions concurrent.

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

[yakuake] [Bug 366087] yakuake should have an option to be centered in a specific DISPLAY

2016-07-25 Thread Raul Kde Bugzilla via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366087

Raul Kde Bugzilla  changed:

   What|Removed |Added

   Platform|Other   |Kubuntu Packages

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


[yakuake] [Bug 366087] yakuake should have an option to be centered in a specific DISPLAY

2016-07-25 Thread Raul Kde Bugzilla via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366087

Raul Kde Bugzilla  changed:

   What|Removed |Added

 CC||raul_kde_bugzi...@dias.com.
   ||br

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


[yakuake] [Bug 366087] New: yakuake should have an option to be centered in a specific DISPLAY

2016-07-25 Thread Raul Kde Bugzilla via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366087

Bug ID: 366087
   Summary: yakuake should have an option to be centered in a
specific DISPLAY
   Product: yakuake
   Version: 2.9.9
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: raul_kde_bugzi...@dias.com.br

Yakuake is a great Terminal.

However, it is not obvious (probably), but it should have an option to be
centered/aligned in relation to a specfic DISPLAY.

This can be done (faked), by setting the Left/Right position in the options.
The problem is that this method uses the whole Framebuffer size and not
indivudual displays.

The incovenience arises, for example, in a notebook that has different display
configurations at different locations.

The worst thing that can happen to a Terminal application is to be divided
between 2 displays of different sizes.



Reproducible: Always

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