[yakuake] [Bug 470144] Yakuake: Wayland keep above other windows not functional

[Jetchko Jekov]

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

--- Comment #6 from Jetchko Jekov  ---
I tested with Konsole for example.
If I select 'Keep Above Others' in the window menu -> More Actions it works as
expected.

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

[yakuake] [Bug 483326] New: 'Keep window above other windows' option does not work

[Jetchko Jekov]

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

Bug ID: 483326
   Summary: 'Keep window above other windows'  option does not
work
Classification: Applications
   Product: yakuake
   Version: 24.02.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: jetchko.je...@gmail.com
  Target Milestone: ---

Created attachment 167019
  --> https://bugs.kde.org/attachment.cgi?id=167019=edit
the relevant yakuake settings

The option 'Keep window above other windows' does not work anymore.

STEPS TO REPRODUCE
1. set the option according to the attached screenshot
2. focus another window 

OBSERVED RESULT
the new windows go above the Yakuake window

EXPECTED RESULT
Yakuake window stays on top

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: Wayland

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

[yakuake] [Bug 482119] Opening new tab in yakuake does not bring it in a focus.

[Jetchko Jekov]

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

--- Comment #5 from Jetchko Jekov  ---
(In reply to Christian Muehlhaeuser from comment #4)
> Can reproduce this. Provided a fix in
> https://invent.kde.org/utilities/yakuake/-/merge_requests/121

Thank you, Christian. That was a very annoying and frustrating (to me) problem.
I can confirm this fixes it.

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

[dolphin] [Bug 482142] New: drag in drop files in Google Chrome renders Chrome unusable

[Jetchko Jekov]

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

Bug ID: 482142
   Summary: drag in drop files in Google Chrome renders Chrome
unusable
Classification: Applications
   Product: dolphin
   Version: 24.02.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: jetchko.je...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Dragging a file from Dolphin to Google Chrome renders Chrome unusable.
Mouse clicks are not accepted anymore by Chrome. Keyboard work though.

This started after the plasma 6 upgrade.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 14 5401

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

[yakuake] [Bug 482119] Opening new tab in yakuake does not bring it in a focus.

[Jetchko Jekov]

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

--- Comment #2 from Jetchko Jekov  ---
Actually, the situation is "interesting":
If I hit  in the new unfocused tab the subshell is spawned and the
tab gets focus.
In this case, when I try to move between tabs with hotkeys I get the error
shown in the attachment.
If I leave the subshell (still staying in the newly opened tab) I can use
hotkeys to move between tabs.

For testing, I moved away both my .bashrc and .bash_profile to rule out
something in them triggers this effect but there was not change.
This all started with the recent upgrade to Plasma 6, There were no issues
before the upgrade.

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

[yakuake] [Bug 482119] Opening new tab in yakuake does not bring it in a focus.

[Jetchko Jekov]

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

--- Comment #1 from Jetchko Jekov  ---
Created attachment 166248
  --> https://bugs.kde.org/attachment.cgi?id=166248=edit
error while try to move between tabs

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

[yakuake] [Bug 482119] New: Opening new tab in yakuake does not bring it in a focus.

[Jetchko Jekov]

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

Bug ID: 482119
   Summary: Opening new tab in yakuake does not bring it in a
focus.
Classification: Applications
   Product: yakuake
   Version: 24.02.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: jetchko.je...@gmail.com
  Target Milestone: ---

SUMMARY
The new open tab in yakuake does not have a focus. It does not matter if it is
triggered via hotkey or clicking '+'  via mouse.


STEPS TO REPRODUCE
1. Open a new tab

OBSERVED RESULT
Not focused

EXPECTED RESULT
The new tab should have a focus

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-21-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 14 5401

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

[yakuake] [Bug 474284] New: Yakuake crash on start

[Jetchko Jekov]

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

Bug ID: 474284
   Summary: Yakuake crash on start
Classification: Applications
   Product: yakuake
   Version: 23.08.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: jetchko.je...@gmail.com
  Target Milestone: ---

Application: yakuake (23.08.0)

Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.2.0-32-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.7 [KCrashBackend]

-- Information about the crash:
after recent kde plasma update yakuake crashes on start

The crash can be reproduced every time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault

[KCrash Handler]
#4  0x7f5d29368adb in QScopedPointer >::operator-> (this=) at
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118
#5  qGetPtrHelper > > (ptr=...) at
../../include/QtCore/../../src/corelib/global/qglobal.h:1151
#6  QAction::d_func (this=) at
../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63
#7  QAction::setVisible (this=0x0, b=true) at kernel/qaction.cpp:1051
#8  0x7f5cf42d92b6 in Konsole::Screen::setReplMode(int) () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#9  0x7f5cf42f5257 in
Konsole::Vt102Emulation::processSessionAttributeRequest(int, unsigned int) ()
from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#10 0x7f5cf42e769f in
Konsole::Vt102Emulation::switchState(Konsole::Vt102Emulation::ParserStates,
unsigned int) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#11 0x7f5cf42e7ab0 in
Konsole::Vt102Emulation::receiveChars(QVector const&) () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#12 0x7f5cf42c1d88 in Konsole::Emulation::receiveData(char const*, int) ()
from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#13 0x7f5d286f4924 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3dfe2770,
r=0x559b89970de0, this=0x559b899d2990) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#14 doActivate (sender=0x559b899c9cd0, signal_index=17,
argv=0x7ffd3dfe2770) at kernel/qobject.cpp:3925
#15 0x7f5cf42b02d1 in Konsole::Pty::receivedData(char const*, int) () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#16 0x7f5cf42c7766 in Konsole::Pty::dataReceived() () from
/lib/x86_64-linux-gnu/libkonsoleprivate.so.1
#17 0x7f5d286f4924 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3dfe2840,
r=0x559b899c9cd0, this=0x559b899d2850) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#18 doActivate (sender=0x559b899c9d50, signal_index=3,
argv=0x7ffd3dfe2840) at kernel/qobject.cpp:3925
#19 0x7f5d286ed9f7 in QMetaObject::activate
(sender=sender@entry=0x559b899c9d50, m=m@entry=0x7f5d2895a960
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x0) at kernel/qobject.cpp:3985
#20 0x7f5d285e7394 in QIODevice::readyRead (this=this@entry=0x559b899c9d50)
at .moc/moc_qiodevice.cpp:190
#21 0x7f5d0c007a04 in KPtyDevicePrivate::_k_canRead (this=0x559b89951ee0)
at ./src/kptydevice.cpp:291
#22 0x7f5d0c007d39 in KPtyDevice::qt_static_metacall (_c=,
_a=0x7ffd3dfe29d0, _id=, _o=) at
./obj-x86_64-linux-gnu/src/KF5Pty_autogen/include/moc_kptydevice.cpp:84
#23 KPtyDevice::qt_static_metacall (_o=, _c=,
_id=, _a=0x7ffd3dfe29d0) at
./obj-x86_64-linux-gnu/src/KF5Pty_autogen/include/moc_kptydevice.cpp:77
#24 0x7f5d286f4958 in doActivate (sender=0x559b899c9e10,
signal_index=5, argv=0x7ffd3dfe29d0) at kernel/qobject.cpp:3937
#25 0x7f5d286ed9f7 in QMetaObject::activate
(sender=sender@entry=0x559b899c9e10, m=m@entry=0x7f5d2895e1a0
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd3dfe29d0)
at kernel/qobject.cpp:3985
#26 0x7f5d286f7ed8 in QSocketNotifier::activated
(this=this@entry=0x559b899c9e10, _t1=, _t2=...) at
.moc/moc_qsocketnotifier.cpp:185
#27 0x7f5d286f86ad in QSocketNotifier::event (this=0x559b899c9e10,
e=0x7ffd3dfe2ae0) at kernel/qsocketnotifier.h:115
#28 0x7f5d2936c763 in QApplicationPrivate::notify_helper (this=, receiver=0x559b899c9e10, e=0x7ffd3dfe2ae0) at
kernel/qapplication.cpp:3640
#29 0x7f5d286bce7a in QCoreApplication::notifyInternal2
(receiver=0x559b899c9e10, event=0x7ffd3dfe2ae0) at
kernel/qcoreapplication.cpp:1064
#30 0x7f5d28716f75 in socketNotifierSourceDispatch (source=0x559b8971a4d0)
at kernel/qeventdispatcher_glib.cpp:107
#31 0x7f5d26b20d3b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x7f5d26b76258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x7f5d26b1e3e3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x7f5d28716368 in QEventDispatcherGlib::processEvents
(this=0x559b8971b860, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#35 

[yakuake] [Bug 451860] yakuake always opens in the second monitor even if set to open in the screen at mouse location

[Jetchko Jekov]

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

Jetchko Jekov  changed:

   What|Removed |Added

 CC||jetchko.je...@gmail.com

--- Comment #1 from Jetchko Jekov  ---
I observe the same symptom here. Or almost the same.
Yakuake does not respect the setting "Screen at mouse location" it opens the
window at the last configured fixed screen.
This is observed only under Wayland. Under X11 it works as expected.

Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-41-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics

Yakuake version:
  22.04.1-0xneon+20.04+focal+release+build35

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

[Powerdevil] [Bug 450757] Lid close does not turn off external monitor even when configured to do so

[Jetchko Jekov]

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

--- Comment #7 from Jetchko Jekov  ---
(In reply to Nate Graham from comment #6)
> Thanks for the info, and sorry for the delayed reply. Your expectations are
> correct.
> 
> In the meantime, maybe you want to set the action to "sleep" rather than
> "turn off the screen?" That might work.

Well, I choose "turn of monitor" deliberately. As part of my job, I am
executing long-running tasks (6-7-8h and even longer) remotely connected via
VPN. "Sleep" is not an option in my case.

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

[Powerdevil] [Bug 450757] Lid close does not turn off external monitor

[Jetchko Jekov]

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

--- Comment #5 from Jetchko Jekov  ---
OK, so that is how I understand these settings:
- the combo box provides a means to select an action to be executed when I
close the laptop lid.
- the check box gives me a choice to override this action i.e. to NOT execute
the action when the external monitor is connected.

Currently on the lid close the laptop screen is turned off, no matter what,
even if I chose the action 'Do nothing'. That does not respect the settings but
 I have no objection to that, there is no point for the laptop screen to be on
while the lid is closed.
But, when I chose 'Turn off screen' I expect the action to depend on the check
box 'Even when an external monitor is connected'
if that check box is not checked -  the external monitor(s) should stay on when
I close the lid(with the layout rearranging and all), but if it is checked all
external monitor(s) should also go off.
Otherwise, these settings are not consistent and confusing.

Did I misunderstand the settings and are my expectations not correct?

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

[Powerdevil] [Bug 450757] Lid close does not turn off external monitor

[Jetchko Jekov]

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

--- Comment #3 from Jetchko Jekov  ---
Besides, it does not matter if that check box is selected or not, currently
closing the lid always switches off the laptop screen and rearranges the
display configuration

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

[Powerdevil] [Bug 450757] Lid close does not turn off external monitor

[Jetchko Jekov]

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

Jetchko Jekov  changed:

   What|Removed |Added

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

--- Comment #2 from Jetchko Jekov  ---
(In reply to Nate Graham from comment #1)
> > When laptop lid closed" -> Turn off the screen
> That's referring to the laptop screen, not any connected external screens.
I am sorry but it was not working that way in the past. Besides that make no
sense at all, If I close the lid why should I care if the laptop screen is on
or off? 
> 
> > Actually, at the time I close the lid, *both* screens go off. But in the 
> > next second my
> > external monitor turns back on and the display setup gets rearranged in a 
> > single monitor
> > setup with the external monitor as primary.
> This is exactly what's supposed to happen when you close your laptop lid
> with that option checked and an external monitor connected.
> 
> To put the system to sleep when you have a laptop connected to an external
> screen, you'll need to use the explicit "Sleep" action found the Application
> Launcher or KRunner.

I don't want to put my system to sleep, I want *both* of my monitors off

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

[Powerdevil] [Bug 450757] New: Lid close does not turn off external monitor

[Jetchko Jekov]

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

Bug ID: 450757
   Summary: Lid close does not turn off external monitor
   Product: Powerdevil
   Version: 5.24.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jetchko.je...@gmail.com
  Target Milestone: ---

SUMMARY
In dual monitor setup (notebook + external monitor) the external monitor does
not turn off when I close the lid even though I have the relevant option
enabled in the settings.
My settings are: "When laptop lid closed" -> Turn off the screen
"Even when an external monitor is connected" is checked

Actually, at the time I close the lid, *both* screens go off. But in the next
second my external monitor turns back on and the display setup gets rearranged
in a single monitor setup with the external monitor as primary.

I found bug 438716 which looks relevant but it's the opposite of my problem and
on Wayland.
My platform is X11.

kscreen-doctor -o
Output: 66 eDP-1 enabled connected primary Panel Modes: 71:1920x1080@60*!
72:1920x1080@60 73:1920x1080@60 
---
158:320x240@60 159:360x202@60 160:360x202@59 161:320x180@60 162:320x180@59
Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable
RgbRange: unknown primary
Output: 67 HDMI-1 disabled disconnected  HDMI Modes: Geometry: 0,0 0x0 Scale: 1
Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 68 DP-1 enabled connected  DisplayPort Modes: 76:1680x1050@60
84:1280x1024@60 97:1280x800@60 
---
184:640x480@60 185:720x400@70 Geometry: 1920,0 2560x1440 Scale: 1 Rotation: 1
Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 69 HDMI-2 disabled disconnected  HDMI Modes: Geometry: 0,0 0x0 Scale: 1
Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown

❯ xrandr -q
Screen 0: minimum 320 x 200, current 4480 x 1440, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 309mm x 173mm
1920x1080 60.00*+  59.9759.9659.9348.01  
---
320x180   59.8459.32
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected 2560x1440+1920+0 (normal left inverted right x axis y axis)
597mm x 336mm
2560x1440 59.95*+
---
720x400   70.08
HDMI-2 disconnected (normal left inverted right x axis y axis)

SOFTWARE/OS VERSIONS

Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-28-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics

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

[krdc] [Bug 448761] KRDC does not support the /smart-sizing input argument

[Jetchko Jekov]

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

Jetchko Jekov  changed:

   What|Removed |Added

 CC||jetchko.je...@gmail.com

--- Comment #3 from Jetchko Jekov  ---
I don't know why do you want  "/smart-sizing". Nowadays xfreerdp has an option
"/dynamic-resolution" which works great when I use xfreerdp directly but does
not work if I use KRDC even if I put it as an additional argument to the
session. Even though I see that xfreerdp is invoked with the option.

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

[plasma-browser-integration] [Bug 419381] New: Preview tooltip in task manager is updated for every single window when media is playing

[Jetchko Jekov]

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

Bug ID: 419381
   Summary: Preview tooltip in task manager is updated for every
single window  when media is playing
   Product: plasma-browser-integration
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: jetchko.je...@gmail.com
  Target Milestone: ---

SUMMARY
In case there is a (youtube) video playing in some browser window the preview
tooltip is updated for every opened browser window.
Tested it both Google Chrome and Firefox

STEPS TO REPRODUCE
1. start some clip on youtube
2. open more than one browser window
3. inspect preview tooltips in task manager

OBSERVED RESULT
All the tooltips are showing the cover of media playing.

EXPECTED RESULT

To see the preview only in the window in which video is playing. And I would
add only if the selected tab is with the video playing.

SOFTWARE/OS VERSIONS

Operating System: Fedora 31
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.67.0
Qt Version: 5.13.2

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

[kdenetwork-filesharing] [Bug 407845] After installing Samba, recommend rebooting

[Jetchko Jekov]

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

Jetchko Jekov  changed:

   What|Removed |Added

 CC||jetchko.je...@gmail.com

--- Comment #3 from Jetchko Jekov  ---
I am sorry but that's wrong. You don't need a reboot for change in group
membership to be taken into account, you need only to perform logout/login
sequence.

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

[Breeze] [Bug 384166] Dropbox icon set clash with owncloud icons

[Jetchko Jekov]

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

--- Comment #7 from Jetchko Jekov <jetchko.je...@gmail.com> ---
I am not sure how this is connected to the problem at hand. If the icons are
not used (but they are) why are they included in the icon set? The real
question is why included icons are "stolen" from another app?

But here are the answers:
instalation on fedora: dns install dropbox (rpmfusion-nonfree repo)

I also included some screenshots

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

[Breeze] [Bug 384166] Dropbox icon set clash with owncloud icons

[Jetchko Jekov]

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

--- Comment #6 from Jetchko Jekov <jetchko.je...@gmail.com> ---
Created attachment 107798
  --> https://bugs.kde.org/attachment.cgi?id=107798=edit
dropbox tray icon with relevant icons in breeze icon theme removed

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

[Breeze] [Bug 384166] Dropbox icon set clash with owncloud icons

[Jetchko Jekov]

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

--- Comment #5 from Jetchko Jekov <jetchko.je...@gmail.com> ---
Created attachment 107797
  --> https://bugs.kde.org/attachment.cgi?id=107797=edit
dropbox tray icon with breeze icon theme

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

[Breeze] [Bug 384166] Dropbox icon set clash with owncloud icons

[Jetchko Jekov]

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

--- Comment #4 from Jetchko Jekov <jetchko.je...@gmail.com> ---
Created attachment 107796
  --> https://bugs.kde.org/attachment.cgi?id=107796=edit
owncloud tray icon

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

[Breeze] [Bug 384166] Dropbox icon set clash with owncloud icons

[Jetchko Jekov]

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

--- Comment #2 from Jetchko Jekov <jetchko.je...@gmail.com> ---
Well that's reasonable but using owncloud's icons is not acceptable solution to
this problem.

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

[Breeze] [Bug 384166] New: Dropbox icon set clash with owncloud icons

[Jetchko Jekov]

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

Bug ID: 384166
   Summary: Dropbox icon set clash with owncloud icons
   Product: Breeze
   Version: 5.10.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: jetchko.je...@gmail.com
CC: kain...@gmail.com
  Target Milestone: ---

I have no idea why this set of icons are chosen for Dropbox in breeze icon set.
Why not use original Dropbox icons? 
Anyway current icons are virtually the same as owncloud's client icon set.
And because of that I have 2 indistinguishable icons in tray area and its not
so obvious which icon is for which app.

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

[plasmashell] [Bug 370143] Desktop Settings doesn't save changes after logout

[Jetchko Jekov]

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

Jetchko Jekov <jetchko.je...@gmail.com> changed:

   What|Removed |Added

 CC|jetchko.je...@gmail.com |

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

[plasmashell] [Bug 370143] Desktop Settings doesn't save changes after logout

[Jetchko Jekov]

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

--- Comment #9 from Jetchko Jekov <jetchko.je...@gmail.com> ---
For me this problem got fixed with upgrading to plasma 5.8.4

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

[plasmashell] [Bug 370143] Desktop Settings doesn't save changes after logout

[Jetchko Jekov]

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

Jetchko Jekov <jetchko.je...@gmail.com> changed:

   What|Removed |Added

 CC||jetchko.je...@gmail.com

--- Comment #8 from Jetchko Jekov <jetchko.je...@gmail.com> ---
I can confirm that weird behavior on Fedora 25 / Plasma 5.8.3 / Intel IGC
Dual monitor setup.

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

[plasma-nm] [Bug 365816] New: Openvpn - Advanced - LZO compression

[Jetchko Jekov via KDE Bugzilla]

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

Bug ID: 365816
   Summary: Openvpn - Advanced - LZO compression
   Product: plasma-nm
   Version: 5.7.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: lu...@kde.org
  Reporter: jetchko.je...@gmail.com
CC: jgrul...@redhat.com

With openvpn-2.3.x --comp-lzo is no more simple boolean (yes/no) option. 
There is one more valid option  'adaptive'.

Whats more there there is some difference  between between presence and absence
of --comp-lzo option on command line.
I have server which is started without such option and I can't make successful
connection to it with any of options --comp-lzo . The only way
for successful connect is to leave out --com-lzo option.
(maybe this last one is an openvpn bug actually but that's what I have
observed) 

Reproducible: Always




plasma-nm-5.7.1-1.fc24.x86_64
plasma-nm-openvpn-5.7.1-1.fc24.x86_64

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