[okular] [Bug 432271] Can't save a file out of Okular

2024-06-01 Thread gggeri91
https://bugs.kde.org/show_bug.cgi?id=432271

--- Comment #12 from gggeri91  ---
This may be relevant: The issue happens to me only when I open files from a
CIFS mount. If I copy over the file to my local home directory it never
crashes. Maybe Okular uses the tmp files when opening from a CIFS file system?

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

[okular] [Bug 432271] Can't save a file out of Okular

2024-06-01 Thread gggeri91
https://bugs.kde.org/show_bug.cgi?id=432271

gggeri91  changed:

   What|Removed |Added

 CC||geloczig...@gmail.com

--- Comment #11 from gggeri91  ---
The very same thing happened to me today. It happened to me several times in
the past, but today I decided to google about this issue more and found this
bug report. This ticket describes the bug very well.  

What lead to the issue in my case:
STEPS TO REPRODUCE
1. Open a PDF file in Okular
2. Make annotations, then press "Save" button. 
3. Make annotations, add text with the type tool, then press "Save" button. 
4. Repeat steps 2 and 3, keep doing modifications and then save the file. After
some time you will run into the bug. 



OBSERVED RESULT
When pressing the "Save" button an error is shown: "File could not be saved in
'/tmp/okular.bvEIkY'. Try to save it to another location."
The "Save As..." button also does not work, the file cannot be saved to any
other location (for example, any folder in my home folder). 

As a work-around, to not loose an hour of work I had to print into PDF, that
works but it is far from the ideal solution.

EXPECTED RESULT
File is saved, no data loss.

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

[plasmashell] [Bug 462316] With all-DisplayPort monitor setup, containment on secondary DisplayPort monitor gets lost when it turn off and then back on, but returns when plasmashell is restarted

2023-02-20 Thread gggeri91
https://bugs.kde.org/show_bug.cgi?id=462316

--- Comment #10 from gggeri91  ---
KDE neon 5.27 works fine, I could not reproduce the bug!

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-32-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: ASUS

Many thanks!

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

[plasmashell] [Bug 462316] With all-DisplayPort monitor setup, containment on secondary DisplayPort monitor gets lost when it turn off and then back on, but returns when plasmashell is restarted

2023-01-21 Thread gggeri91
https://bugs.kde.org/show_bug.cgi?id=462316

--- Comment #9 from gggeri91  ---
Tested with neon-testing-20230119-1946.iso -> it works!

---
I'm aware about the refactor happened regarding multi-monitor support, and I am
very happy to see it works on my computer using the new testing version. Big
thanks to the developers!  :)

So this works perfectly on my computer, I cannot reproduce the bug: 

Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.26.90
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 5.15.0-58-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT
Manufacturer: ASUS

Source: neon-testing-20230119-1946.iso

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

[plasmashell] [Bug 462316] Black background after monitors were in standby

2022-12-03 Thread gggeri91
https://bugs.kde.org/show_bug.cgi?id=462316

--- Comment #5 from gggeri91  ---
Update: more tests with AMD RX 580 GPU

I put back my RX 580 into my system and ran more tests, because that card has a
DVI output as well. I restarted my PC before each test to make sure it is a
clean starting state. Please see the results below.

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-56-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series

---

#1 Test with DVI-D-0 + DisplayPort-1
Result: OK.  

#2 Test with DisplayPort-0 + DisplayPort-1
Result: FAILED.  

---

Conclusions:
 - The issue is related to the video output type (DisplayPort)
 - It is not related to a specific GPU model

My thoughts on DisplayPort:
DisplayPort has more capabilities than DVI/HDMI regarding power states. 
- If you turn off a monitor connected to DVI/HDMI the OS won't know about it,
so the desktop layout also won't change. 
- If you turn off a DisplayPort monitor, the desktop layout changes
accordingly.
So what happens when both monitors in a dual monitor setup are connected via
DisplayPort? The moment they enter standby I guess both of them are "lost" to
the OS which causes issues like this. This is just my theory, trying to find
logic in this, please correct me if I'm wrong :)

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

[plasmashell] [Bug 462316] Black background after monitors were in standby

2022-11-27 Thread gggeri91
https://bugs.kde.org/show_bug.cgi?id=462316

--- Comment #2 from gggeri91  ---
I forgot to mention that the bug does not happen with a single monitor
attached.
Seems like it is somehow related to amdgpu, I'm not sure.

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

[plasmashell] [Bug 462316] Black background after monitors were in standby

2022-11-27 Thread gggeri91
https://bugs.kde.org/show_bug.cgi?id=462316

--- Comment #1 from gggeri91  ---
Created attachment 154085
  --> https://bugs.kde.org/attachment.cgi?id=154085=edit
Case when two desktops went black with KDE Neon

Happened when repeated the test scenario the second time.

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

[plasmashell] [Bug 462316] New: Black background after monitors were in standby

2022-11-27 Thread gggeri91
https://bugs.kde.org/show_bug.cgi?id=462316

Bug ID: 462316
   Summary: Black background after monitors were in standby
Classification: Plasma
   Product: plasmashell
   Version: 5.24.7
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: plasma-b...@kde.org
  Reporter: geloczig...@gmail.com
CC: notm...@gmail.com
  Target Milestone: 1.0

Created attachment 154084
  --> https://bugs.kde.org/attachment.cgi?id=154084=edit
Screenshot with latest KDE Neon

SUMMARY
By default the monitors turn off after 10 minutes of inactivity. Then if you
move the mouse they turn back on again. After this my primary desktop turns to
black and you can't right click (menu does not appear).

This command restart the shell so I can continue my work:
kquitapp5 plasmashell || killall plasmashell && kstart5 plasmashell

STEPS TO REPRODUCE
1. Boot Kubuntu 22.04 or latest KDE Neon or Fedora 37 KDE Plasma Desktop from
USB stick or install it
2. Turn off monitors with "sleep 1 && xset -display :0.0 dpms force off"
3. WAIT until the monitors enter standby mode (backlight goes off)
4. After your monitors turned off, move your mouse.
5. One of the desktops will have a black background and right-click menu does
not appear.

OBSERVED RESULT
One of the desktops will have a black background and right-click menu does not
appear.
Repeating the test may produce two black desktops.

EXPECTED RESULT
Desktop functions without glitches.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: reproduced with 5.24.6, 5.24.7, and 5.26.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
I use two identical EIZO EV2750 60Hz 2560x1440 monitors on DisplayPort-0 and
DisplayPort-1 in dual monitor mode (horizontally extended). Primary monitor is
in center, second monitor is on my right.
Observed workaround: Plugging my second monitor to HDMI instead of
DisplayPort-1 makes this bug disappear. 

- This bug does happen with my AMD RX 6600 XT, but not with my older AMD RX 580
8GB.
- Reproduced with latest Kubuntu LTS (22.04.1)
- Reproduced with latest KDE Neon (neon-user-20221117-0714.iso)
- Reproduced with Fedora 37 KDE edition (Fedora-KDE-Live-x86_64-37-1.7.iso),
interesting it uses Wayland instead X11 and the same bug happens.
- Does not happen with Kubuntu 20.04.5, plasmashell 5.18.8 works fine.

As you see I could reproduce this bug just by booting from a USB stick, so I
used always the default settings, did not change anything.

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