[gwenview] [Bug 378061] Display full path of image on main window

2024-07-04 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=378061

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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

[gwenview] [Bug 242332] Sort by file's Date Modified time

2022-07-12 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=242332

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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

[frameworks-kio] [Bug 452074] Deleting files to trash with kio very slow | trash-cli and rm work correctly

2022-04-09 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=452074

--- Comment #5 from Ruman Gerst  ---
I think BTRFS is not the cause. I have the same issue on EXT4.  From my
experience it's related to operations that should take only a short time, e.g.,
deleting (or more precisely moving) a file/directory with the size of a few
kilobytes.

I tried it now on a few directories (100MB each) and saw something interesting: 

Moving them to trash should have taken less than one second, but it took
approx. 30s; how this was achieved is of interest:

1. Select 3 directories, press Delete key
2. Notification status appears. It is in the indeterminate state
(back-and-forth animation)
3. Few seconds later: Two directories disappeared in Dolphin
4. Notification switches to 1/3 state
5. Seconds later: Switches to 2/3 state, followed by 3/3
6. Third directory disappears from Dolphin

I repeated this for different directories, where it worked as expected
(although still quite slow).

It's also not consistent for me. Sometimes it works, sometimes it doesn't.
Maybe it's a weird concurrently bug somewhere?

Plasma 5.24.4, Frameworks 5.92.0, Kubuntu 21.10 (via kubuntu-backports)

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

[frameworks-kio] [Bug 452074] Deleting files to trash with kio very slow | trash-cli and rm work correctly

2022-04-09 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=452074

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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

[ark] [Bug 185209] Include a global option in Ark to set modification date to current date

2021-03-09 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=185209

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

--- Comment #3 from Ruman Gerst  ---
(In reply to Justin Zobel from comment #2)
> Thank you for the bug report.
> 
> As this report hasn't seen any changes in 5 years or more, we ask if you can
> please confirm that the issue still persists.
> 
> If this bug is no longer persisting or relevant please change the status to
> resolved.

I still have this issue with latest Ubuntu packages. It slows down my workflows
considerably.

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

[kdenlive] [Bug 410726] Audio artifacts in export

2021-03-08 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=410726

--- Comment #27 from Ruman Gerst  ---
Created attachment 136502
  --> https://bugs.kde.org/attachment.cgi?id=136502&action=edit
Audio artifact is not reproducible in 24 FPS

> Could you confirm that this isn't happening in say a 30fps or 24fps project?

I tried to cut the audio the same in two projects (60 FPS and 24 FPS). I could
not get the 24 FPS project to make audio artifacts.

But I noticed something interesting: In the 24 FPS project, the rendered result
contains still a part of the "uuuh" (very hard to notice, but it's there). With
60 FPS it's exactly at the time where the audio artifact happens.

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

[kdenlive] [Bug 410726] Audio artifacts in export

2021-03-08 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=410726

--- Comment #25 from Ruman Gerst  ---
(In reply to farid from comment #22)
> Hi Ruman
> 
> (In reply to Ruman Gerst from comment #21)
> > (In reply to farid from comment #20)
> > The audio was captured using the recording track and I cut the beginning and
> > end of them, before putting them to their destined located.
> > Rendering audio only (FLAC) had the "pop"/"click" sounds at beginning of
> > some clips (which are also present in the preview).
> > These should have been fixed in MLT, but I managed to break them ...
> 
> Can you upload one of your flacs so I can test? 

Thank you for your reply! I uploaded an attachment that contains the original
audio plus rendered audio (the original audio was cut in Kdenlive to remove an
"uuhhh").

> 
> > 
> > I edited the audio file in Audacity and imported it back into Kdenlive. I
> > was required to make edits to this track, which also involved cuts.
> > Interestingly, here I have an additional artifact: The rendered video (as
> > well as the preview) contains "lags", similar to if the real-time preview
> > gets stuck on some effects 
> > and slows down/distorts the audio - just in the final render.
> > 
> > This "lag" appears in renders created by Kdenlive (Ubuntu PPA), Kdenlive
> > (Appimage), and MLT CLI, so this might be an upstream issue.
> 
> Can you share your MLT command?

Fortunately ZSH remembered my command: melt video.kdenlive -consumer
avformat:output.mp4

> Doing some debugging in another similar issue I saw that your artifacts might 
> > be related to 60fps projects. What is your project profile?

This is quite interesting ... I used 1080p, 60FPS as preset.

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

[kdenlive] [Bug 410726] Audio artifacts in export

2021-03-08 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=410726

--- Comment #24 from Ruman Gerst  ---
Created attachment 136501
  --> https://bugs.kde.org/attachment.cgi?id=136501&action=edit
Original audio vs rendered audio with cut in-between

As requested the original audio file and the Kdelive render (FLAC)

The original audio was cut to remove the "uuhh" part. This yielded in the audio
artifact.

Preset: 1080p, 60FPS

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

[kdenlive] [Bug 431606] New: Title clip editor background is low-resolution

2021-01-14 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=431606

Bug ID: 431606
   Summary: Title clip editor background is low-resolution
   Product: kdenlive
   Version: 20.12.1
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: mrbo...@live.de
  Target Milestone: ---

Created attachment 134861
  --> https://bugs.kde.org/attachment.cgi?id=134861&action=edit
(left) The original image that was put into the video. (right) The titler show
a very low-res version of this image

SUMMARY
The title clip editor has an option to display a render of the current preview
as background. This background is very low-resolution, making it hard to add
precise annotations (see attachment).


STEPS TO REPRODUCE
1. Put a screenshot (1920x1080) into the project (resolution 1920x1080) and add
it as a clip
2. Move time cursor to where the screenshot is visible
3. Add a new title clip
4. Enable "Show background"
5. Zoom in (e.g., fit to the screen)

OBSERVED RESULT
The background is shown in a very low resolution; text is almost unreadable.


EXPECTED RESULT
The background (screenshot) is displayed in full resolution.


SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: 5.8 / 5.19.5
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
The resolution of the generated background is not affected by the size of the
preview panel (e.g., by double-clicking it to make it full-screen).
The resolution cannot be controlled by changing the window size of the title
clip editor.
Happens in PPA (Ubuntu 20.10) and AppImage

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

[kdenlive] [Bug 431604] New: Transition *.pgm locations are saved as absolute paths

2021-01-14 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=431604

Bug ID: 431604
   Summary: Transition *.pgm locations are saved as absolute paths
   Product: kdenlive
   Version: 20.12.1
  Platform: Ubuntu Packages
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: mrbo...@live.de
  Target Milestone: ---

SUMMARY
*.kdenlive files store the location of transitions as absolute path. This
disrupts interop between different operating systems.

For example, my current project saves the location of the transition as
following:

/usr/share/kdenlive/lumas/HD/linear_x.pgm

As this is located in the Kdenlive shared folder, it should be stored as
following:

linear_x.pgm


STEPS TO REPRODUCE
1. Create a simple project with a wipe transition on Linux 
2. Copy the project to a Windows computer
3. Try to open it in Kdenlive

OBSERVED RESULT
Kdenlive (Windows) does not find the transition(*.pgm) file.


EXPECTED RESULT
Kdenlive opens the project without complaining about missing files.


SOFTWARE/OS VERSIONS
Windows: 10
macOS: -
Linux/KDE Plasma: 5.8 / 5.19.5
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION

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

[kdenlive] [Bug 410726] Audio artifacts in export

2021-01-13 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=410726

--- Comment #21 from Ruman Gerst  ---
(In reply to farid from comment #20)
> (In reply to Ruman Gerst from comment #19)
> > Sorry, I went a bit on autopilot and added myself to the mailing list.
> > 
> > I have a similar bug on my current project that I was trying to get info
> > about
> > 
> > Sorry!
> 
> What version are you using? Canyou try with the latest AppImage.

I tried it with the newest appimage and still have the audio artifacts with my
newest project. 
My non-appimage version should be up-to-date as well, as I am using the Ubuntu
20.10 PPA (comes with 20.12.1 and MLT 6.25.0).

The audio was captured using the recording track and I cut the beginning and
end of them, before putting them to their destined located.
Rendering audio only (FLAC) had the "pop"/"click" sounds at beginning of some
clips (which are also present in the preview).
These should have been fixed in MLT, but I managed to break them ...

I edited the audio file in Audacity and imported it back into Kdenlive. I was
required to make edits to this track, which also involved cuts.
Interestingly, here I have an additional artifact: The rendered video (as well
as the preview) contains "lags", similar to if the real-time preview gets stuck
on some effects 
and slows down/distorts the audio - just in the final render.

This "lag" appears in renders created by Kdenlive (Ubuntu PPA), Kdenlive
(Appimage), and MLT CLI, so this might be an upstream issue.


For now I edited everyting in Audacity and just put the final audio over the
video and it rendered fine.

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

[kdenlive] [Bug 410726] Audio artifacts in export

2021-01-13 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=410726

--- Comment #19 from Ruman Gerst  ---
Sorry, I went a bit on autopilot and added myself to the mailing list.

I have a similar bug on my current project that I was trying to get info about

Sorry!

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

[kdenlive] [Bug 410726] Audio artifacts in export

2021-01-13 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=410726

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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

[kdenlive] [Bug 426803] New: Audio recordings are not put into the project folder

2020-09-21 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=426803

Bug ID: 426803
   Summary: Audio recordings are not put into the project folder
   Product: kdenlive
   Version: 20.08.1
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: mrbo...@live.de
  Target Milestone: ---

SUMMARY
On creating a audio recording via the recording track, the clips are not stored
into the project folder, but into $HOME/Videos.


STEPS TO REPRODUCE
1. Create a new project
2. Add some video or image to allow the project to save
3. Save the project into an empty folder
4. Add a new audio recording track
5. Hit the record button and record a clip

OBSERVED RESULT
The recording is added into the track as expected, but the audio file is stored
into some default directory (for me it is ~/Videos)


EXPECTED RESULT
The clip file is added into the folder that contains the project file.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 20.04, Linux 5.4.0, Plasma 5.18.5
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
Kdenlive version is from the PPA for Ubuntu 20.04

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

[kdenlive] [Bug 423005] New: Non-modal or dockable title clip editor

2020-06-15 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=423005

Bug ID: 423005
   Summary: Non-modal or dockable title clip editor
   Product: kdenlive
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: mrbo...@live.de
  Target Milestone: ---

SUMMARY
I am working on a video project that involves lots close interaction between
title clips and the video content. While it is possible to show the current
project monitor output in the title clip editor, it is not possible to switch
to another time point without closing the editor.
Making the title clip editor non-modal would definitively increase the
efficiency in such cases. 

Ideally, due to the new feature set of the title editor, it would be dockable
like any other component (a good location would be next to the clip monitor and
project monitor).


STEPS TO REPRODUCE
1. Edit a title clip
2. Enable "Show background" to display the current project monitor contents

OBSERVED RESULT
Unable to change to a different time point as the dialog is modal.


EXPECTED RESULT
Change the displayed video background by selecting another time point.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 20.04 LTS
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.4.0-37-generic

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 415953] Plasma Desktop Manager keeps crashing

2020-01-13 Thread Ruman
https://bugs.kde.org/show_bug.cgi?id=415953

Ruman  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Ruman  ---
(In reply to David Edmundson from comment #1)
> Crashes should have a backtrace otherwise we can't do much
> 
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

Hi,
Thanks for the response. Yes, it seems like some application running backend
with infinite loop because when I ran the `apt dist-upgrade` resolved the
issue.

Thanks again.

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

[plasmashell] [Bug 415953] New: Plasma Desktop Manager keeps crashing

2020-01-06 Thread Ruman
https://bugs.kde.org/show_bug.cgi?id=415953

Bug ID: 415953
   Summary: Plasma Desktop Manager keeps crashing
   Product: plasmashell
   Version: master
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: ruman@gmail.com
  Target Milestone: 1.0

SUMMARY
Plasma Desktop Manager keeps crashing after my recent apt upgrade ( 01/02/2020
)
After I logged into my Linux, it crashed and I have run command `plasmashell`
to start that again and again crashed.

OBSERVED RESULT:
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kipiplugin_sendimages.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/dolphinpart.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_trash.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/powerdevilwirelesspowersavingaction_config.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/systemsettings_sidebar_mode.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_componentchooser.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kscreen.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/powerdevildpmsaction_config.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/windowsimagethumbnail.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/classic_mode.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kwinscreenedges.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_bluetooth.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kipiplugin_googleservices.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/icon_mode.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_colors.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kipiplugin_rajce.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_placesrunner.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphinservices.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/audiothumbnail.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_about_distro.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/powerdevilbrightnesscontrolaction_config.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/user_manager.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_dolphinnavigation.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kwinoptions.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_recentdocuments.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_ssl.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kded_touchpad.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_powerdevilglobalconfig.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/notepadpart.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_kwin.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_konq.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_fonts.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/libkcm_qtquicksettings.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma_engine_testengine.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_info.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_opengl.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kipiplugin_piwigo.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kipiplugin_smug.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_powerdevilactivitiesconfig.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_filetypes.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_krunner_kill.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_locations.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_fontinst.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_kwintabbox.so"
invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/exrthumbnail.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/opendocumentthumbnail.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/libkcm_device_automounter.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_bookmarksrunner.so"
invalid metadata
"/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner

[dolphin] [Bug 343620] Places get deleted if device could not be mounted by KDE

2018-05-06 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=343620

Ruman Gerst  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #5 from Ruman Gerst  ---
Oh sorry, I forgot that I submitted this bug (and I sometimes don't get mails).
Seems to work for me with the current version. Thank you!

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

[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering

2017-07-03 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=353983

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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

[plasmashell] [Bug 336736] Show exact pixel size when resizing panel

2017-04-17 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=336736

--- Comment #4 from Ruman Gerst  ---
If showing the exact pixel size clutters the UI, would it be possible to
include panel size and position settings into the panel options dropdown (or a
separate dialog window). 

Not only would this feature usable for people who like to adjust everything
pixel-perfect, but also for users that have problems with drag & drop or laptop
users without any mouse.

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

[plasmashell] [Bug 336736] Show exact pixel size when resizing panel

2017-04-17 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=336736

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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

[plasmashell] [Bug 371219] Plasma going in to visual stasis when a game that block compositing, starts

2016-12-09 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=371219

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

2016-11-17 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=356225

--- Comment #242 from Ruman Gerst  ---
I have two screens: HDMI (left) and DVI (right). Mainboard, BIOS and boot logo
show up on DVI.

It now seems to work for me after setting the primary screen to DVI.
It seems that on first start, the primary screen seems to be the the one
defined by the system (DVI). Killing and restarting Plasma worked as then the
primary was HDMI. After I set the primary screen to the one my system expected
(?), it now works flawlessly so far.

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

2016-10-26 Thread Ruman Gerst
https://bugs.kde.org/show_bug.cgi?id=356225

--- Comment #217 from Ruman Gerst  ---
The update didn't fix it for me, either. It made it better, at least. So no
more panels on top of each other, no black desktop screen, no more flickering
where it adapts the controls to the resolution (and going back and forth).

Now my panels are on the opposite screen. Always. Even after reconfiguring.
Manually running kquitapp plasmashell; kstart plasmashell magically fixes this
for more.

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

[plasmashell] [Bug 361692] Clock doesn't update while compositing is off

2016-09-12 Thread Ruman Gerst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361692

--- Comment #5 from Ruman Gerst  ---
This happens for me on Plasma 5.7.3 ... and not only the clock - everything
that is in the panels stop updating (e.g the Teamspeak 3 indicator that shows
the microphone status).
The task manager does not update, too and often doesn't even show an entry for
the game. It's there - it will react if you click on it. Also menus etc. are
working fine.

If I try to restart plasmashell (kquitapp plasmashell; kstart plasmashell), the
panel of the secondary monitor flickers quickly between the primary and the
secondary monitor. If I start plasmashell in a terminal, it spams following
message:
: QML QQuickLayoutAttached: Binding loop detected for property
"preferredWidth"

If I exit the game, the problem persists (even a plasmashell restart doesn't
help). Only kwin_x11 --replace fixes the problem. 

So far caused by following games: Starbound and Stardew Valley
HW: Nvidia GTX 660, prorietary drivers (367.44)
OS: Manjaro, Kernel 4.7

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


[plasmashell] [Bug 361692] Clock doesn't update while compositing is off

2016-09-12 Thread Ruman Gerst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361692

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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


[gwenview] [Bug 336436] Switch to webkit or blink when rendering SVG files

2016-09-12 Thread Ruman Gerst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336436

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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


[kio] [Bug 252026] kioexec dont transfer modified files back to remote storage

2016-08-26 Thread Ruman Gerst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=252026

--- Comment #17 from Ruman Gerst  ---
KIO should automatically upload files if they change in cache. Would make KIO
much more usable. Currently it's more like a Filezilla with more features -
good for viewing or moving stuff, but really bad for editing.
I am forced to use GVFS that allows everything I need.

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


[kio] [Bug 252026] kioexec dont transfer modified files back to remote storage

2016-08-26 Thread Ruman Gerst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=252026

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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


[kio] [Bug 367796] New: GVFS SSH mount - Dolphin can't write anything

2016-08-25 Thread Ruman Gerst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367796

Bug ID: 367796
   Summary: GVFS SSH mount - Dolphin can't write anything
   Product: kio
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: mrbo...@live.de

I have a remote directory over SSH that is mounted via GVFS (by using Gigolo).
The problem is that Dolphin refuses to write anything to these folders (Create
a new file via menu, pasting, ...). Deleting and opening works fine. Using the
console works fine. Other programs (e.g. Emacs) and other file managers don't
have any problems.
If I create a file, you can see that some error message pops up (at the error
bar), but disappears within milliseconds.
Dolphin reports unknown size of the file system (0 of 0 bytes).

I set this bug as Major one as basic operations are not possible and Dolphin is
pretty much unusable now.

Reproducible: Always

Steps to Reproduce:
1. Mount a SSH directory via GVFS (e.g. use Gigolo)
2. Go into the mounted folder
3. Create a new file via context menu or paste something into the folder

Actual Results:  
File won't be created / pasted. A error appears for some milliseconds (but
quickly disappears).

Expected Results:  
File is created / pasted

Other people reported similar bugs ( eg
https://bugs.kde.org/show_bug.cgi?id=357930). Could the be related?
Are there any space checks that don't respect the "Unknown size" case?

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


[kio] [Bug 357930] SSHFS mount - Dolphin complains disk is full

2016-08-25 Thread Ruman Gerst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357930

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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


[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

2016-07-30 Thread Ruman Gerst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356225

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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


[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers

2015-12-04 Thread Ruman Gerst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343803

Ruman Gerst  changed:

   What|Removed |Added

 CC||mrbo...@live.de

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