[kdeplasma-addons] [Bug 476161] Ability to use the new Cube effect as animation when switching virtual desktops

2024-03-01 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=476161

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.eu

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

[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB

2024-01-16 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=389848

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.eu

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

[plasmashell] [Bug 436318] Save session doesn't work under Wayland

2023-11-11 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=436318

--- Comment #66 from Oleg Girko  ---
(In reply to Charles Dennett from comment #63)
> Will what is planned for KDE 6 take into account multiple monitors and
> multiple virtual desktops so that apps start in the desired monitor/virtual
> desktop?

And please don't forget about activities!
I'm tired of moving Firefox windows to different activities manually each time
after login even on KDE 5 X11 session.

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

[plasmashell] [Bug 336990] Chromium and Firefox does not remember their virtual desktops on session restore

2023-05-17 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=336990

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.eu

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

[kwin] [Bug 468252] Desktop Session does not restore windows to proper screen

2023-05-16 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=468252

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.eu

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

[ksmserver] [Bug 421870] windows on wrong desktop after session restore on Wayland

2023-05-16 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=421870

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.eu

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

[ksmserver] [Bug 436318] Save session doesn't work under Wayland

2023-05-16 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=436318

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.eu

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

[NeoChat] [Bug 465143] crash after logging in

2023-02-18 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=465143

--- Comment #3 from Oleg Girko  ---
Created attachment 156448
  --> https://bugs.kde.org/attachment.cgi?id=156448=edit
New crash information added by DrKonqi

neochat (23.01) using Qt 5.15.8

Crash happening after logging in and then opening settings without selecting a
room. Opening settings when a room is selected doesn not cause crash.

-- Backtrace (Reduced):
#4  0x7f76634fd534 in Quotient::Room::id() const () from
/lib64/libQuotient.so.0.7
#5  0x55d86935845b in
Controller::handleNotifications(QPointer)::{lambda()#1}::operator()()
const ()
#6  0x7f76618d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#7  0x7f76634bf7d6 in Quotient::BaseJob::success(Quotient::BaseJob*) ()
from /lib64/libQuotient.so.0.7
#8  0x7f76635546a1 in Quotient::BaseJob::finishJob() () from
/lib64/libQuotient.so.0.7

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

[NeoChat] [Bug 465143] crash after logging in

2023-02-18 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=465143

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.eu

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

[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API

2022-09-13 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=438883

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.ru

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

[konsole] [Bug 429600] Highlight the lines coming into view (HighlightScrolledLines) feature breaks Initial terminal size

2020-11-24 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=429600

--- Comment #1 from Oleg Girko  ---
Why was severity downgraded to minor?
Being unable to start Konsole with the size specified in settings is quite a
major annoyance.

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

[konsole] [Bug 429600] Highlight the lines coming into view (HighlightScrolledLines) feature breaks Initial terminal size

2020-11-24 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=429600

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.ru

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

[konsole] [Bug 429600] New: Highlight the lines coming into view (HighlightScrolledLines) feature breaks Initial terminal size

2020-11-24 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=429600

Bug ID: 429600
   Summary: Highlight the lines coming into view
(HighlightScrolledLines) feature breaks Initial
terminal size
   Product: konsole
   Version: 20.08.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: ol+...@infoserver.ru
  Target Milestone: ---

SUMMARY

The new HighlightScrolledLines (Highlight the lines coming into view) feature
appeared in Konsole 20.08.
This feature is on by default and it causes several pixels of Konsole width to
be used for indicating lines coming into view.
However these pixels are not taken into account when calculating initial window
size. This breaks Initial terminal size feature.

STEPS TO REPRODUCE
1. Set Initial terminal size in Profile -> your profile name -> General to the
size you like.
2. Set "restore window size" to false in Konsole settings -> General.
3. Start new Konsole instance.
4. Run "stty -a" in Konsole you've just started and observe "columns"
parameter.

OBSERVED RESULT
The "columns" parameter in "stty -a" output is less than you configured in
Initial terminal size.

EXPECTED RESULT
The "columns" parameter in "stty -a" output should match the one you configured
in Initial terminal size.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 32 with Konsole 20.08.3, Fedora 33 with Konsole
20.08.1
KDE Plasma Version: 5.18.5, 5.19.5
KDE Frameworks Version: 5.75.0
Qt Version: 5.14.2, 5.15.1

ADDITIONAL INFORMATION
This problem goes away when setting HighlightScrolledLines (Highlight the lines
coming into view) to false.

Although I've selected "Fedora RPMs" as the Platform, I presume that this
problem is not specific to Fedora. However, I didn't test on other platforms.

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

[konsole] [Bug 359662] Terminal Rows are miscalculated if Menu Bar is turned off

2019-11-25 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=359662

--- Comment #7 from Oleg Girko  ---
Looks like this problem is fixed.

Probably, by this commit:
https://cgit.kde.org/konsole.git/commit/?id=efb621d091c05f1195982667782507ffe27ed8cf

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

[konsole] [Bug 359662] Terminal Rows are miscalculated if Menu Bar is turned off

2019-06-19 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=359662

--- Comment #6 from Oleg Girko  ---
I've spent several days trying to understand what's going on, but my knowledge
of layout mechanics in Qt is not sufficient to find out the root cause. I'll
try to summarise my findings here in hope that it will be helpful for somebody
more knowledgeable than me to solve this bug.

# My setup

I have konsole5-18.12.3-2.fc30.x86_64 package installed in Fedora 30.
My laptop's screen size is 3200x1800 pixels (295x167 millimeters).
DPI is explicitly set to 192 in KDE settings.
Font in Konsole profile is set to Consolas, size 7 (yes, this is small).
Menu and tabbar in Konsole are disabled.
I've added tons of debug prints to konsole5 source code, but except of debug
print statements (using qWarning()), the source code and build procedure is
identical to this Fedora package:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1247868
I've set "Use current window size on next startup" to false, and Terminal Size
in my only profile to 80x24.

# What's going on

Everything is happening in Application::newInstance() method.

1. MainWindow is created. Then MainWindow::createSession() is called that in
turn calls ViewManager::createView(Session *) that creates TabbedViewContainer.
Constructor of TabbedViewContainer calls
TabbedViewContainer::konsoleConfigChanged() that calls
tabBar()->setVisible(false);

2. Later in ViewManager::createView(Session *) another overload with the same
name is called: ViewManager::createView(Session *, TabbedViewContainer *, int)
that creates TerminalDisplay. Then it calls TerminalDisplay::setSize(80, 24) on
newly created TerminalDisplay.

I have the following before TerminalDisplay::setSize(80, 24):

ViewSplitter:
- isVisible() = false
- contentsRect() =  QRect(0,0 640x480)
- sizeHint() =  QSize(8, 8)
- size() =  QSize(640, 480)
- geometry() =  QRect(0,0 640x480)
TabbedViewContainer:
- isVisible() = false
- contentsRect() =  QRect(0,0 640x480)
- sizeHint() =  QSize(8, 8)
- size() =  QSize(640, 480)
- geometry() =  QRect(0,0 640x480)
QTabBar:
- isVisible() = false
- contentsRect() =  QRect(0,0 0x0)
- sizeHint() =  QSize(0, 0)
- size() =  QSize(0, 0)
- geometry() =  QRect(0,0 0x0)
TerminalDisplay:
- isVisible() = false
- contentsRect() =  QRect(0,0 640x480)
- sizeHint() =  QSize(-1, -1)
- size() =  QSize(640, 480)
- geometry() =  QRect(0,0 640x480)

As you see, these values are just placeholders, nothing interesting.

I have the following after TerminalDisplay::setSize(80, 24):

ViewSplitter:
- isVisible() = false
- contentsRect() =  QRect(0,0 640x480)
- sizeHint() =  QSize(8, 8)
- size() =  QSize(640, 480)
- geometry() =  QRect(0,0 640x480)
TabbedViewContainer:
- isVisible() = false
- contentsRect() =  QRect(0,0 640x480)
- sizeHint() =  QSize(8, 8)
- size() =  QSize(640, 480)
- geometry() =  QRect(0,0 640x480)
QTabBar:
- isVisible() = false
- contentsRect() =  QRect(0,0 0x0)
- sizeHint() =  QSize(0, 0)
- size() =  QSize(0, 0)
- geometry() =  QRect(0,0 0x0)
TerminalDisplay:
- isVisible() = false
- contentsRect() =  QRect(0,0 640x480)
- sizeHint() =  QSize(819, 482)
- size() =  QSize(640, 480)
- geometry() =  QRect(0,0 640x480)

What changed here is TerminalDisplay::sizeHint() changed to something that
makes sense for 80x24 display.

3. Later in ViewManager::createView(Session *, TabbedViewContainer *, int),
container->addView() is called. TabbedViewContainer::addView() method just
calls QTabWidget::addTab() method with newly created TerminalDisplay as its
first argument, but it causes geometry of widgets to be recalculated
dramatically. This is what I have after this:

ViewSplitter:
- isVisible() = false
- contentsRect() =  QRect(0,0 640x480)
- sizeHint() =  QSize(827, 535)
- size() =  QSize(640, 480)
- geometry() =  QRect(0,0 640x480)
TabbedViewContainer:
- isVisible() = false
- contentsRect() =  QRect(0,0 640x480)
- sizeHint() =  QSize(827, 535)
- size() =  QSize(640, 480)
- geometry() =  QRect(0,0 640x480)
QTabBar:
- isVisible() = false
- contentsRect() =  QRect(0,0 0x0)
- sizeHint() =  QSize(129, 45)
- size() =  QSize(0, 0)
- geometry() =  QRect(0,0 0x0)
TerminalDisplay:
- isVisible() = false
- contentsRect() =  QRect(0,0 640x480)
- sizeHint() =  QSize(819, 482)
- size() =  QSize(640, 480)
- geometry() =  QRect(0,0 640x480)

Look at sizeHint() of TabbedViewContainer and ViewSplitter that encloses it.
827x535 is way bigger than 819x482 of TerminalDisplay. Height of 535 is even 8
pixels higher that 482 (height of TerminalDisplay) + 45 (height of QTabBar).

I think, the key question to understand the cause of the problem is what
happened here.

How sizeHint() of TabbedViewContainer (that is essentially QTabWidget) became
significantly bigger than one of TerminalDisplay that was just added to it,
despite its tabBar() being hidden?

Remember this size: 827x535, it is what will cause problems later.

4. In the end of Application::newInstance(),
Application::finalizeNewMainWindow(MainWindow *) 

[konsole] [Bug 402446] Konsole Column Count is Incorrect

2019-06-03 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=402446

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.ru

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

[konsole] [Bug 359662] Terminal Rows are miscalculated if Menu Bar is turned off

2019-06-03 Thread Oleg Girko
https://bugs.kde.org/show_bug.cgi?id=359662

Oleg Girko  changed:

   What|Removed |Added

 CC||ol+...@infoserver.ru

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

[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window

2015-12-13 Thread Oleg Girko via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355275

Oleg Girko <ol+...@infoserver.ru> changed:

   What|Removed |Added

 CC||ol+...@infoserver.ru

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