[dolphin] [Bug 373141] New: Folders created with bash appear in wrong places
https://bugs.kde.org/show_bug.cgi?id=373141 Bug ID: 373141 Summary: Folders created with bash appear in wrong places Product: dolphin Version: 15.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: unf...@gmail.com Target Milestone: --- Created attachment 102560 --> https://bugs.kde.org/attachment.cgi?id=102560&action=edit A screenshot shoiwng that Dolphin shows a folder where it doesn't exist - as proven by ls command in the commandline panel. I have a script that creates new folders under /Autowiz/Temp dir. Sometimes these folders appear in Dolphin as if they were one level above - directly in the /Autowiz dir. I thought it's a bug in the script, but I can verify that there are no temp folders in /Autowiz - with ls command. I attach a screenshot where a folder with a name created with uuid-gen is shown under /Autowiz, but ls command below shows there is no such folder here. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373141] Folders created with bash appear in wrong places
https://bugs.kde.org/show_bug.cgi?id=373141 --- Comment #1 from unfa --- After refreshing the view with F5 it sometimes catches up and shows the folders as they are, but sometimes this persists either way. The folder in question starts with "12e09fde-" - it's a string created with command uuidgen. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373142] New: Can't copy and paste file names
https://bugs.kde.org/show_bug.cgi?id=373142 Bug ID: 373142 Summary: Can't copy and paste file names Product: dolphin Version: 15.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: unf...@gmail.com Target Milestone: --- One function I always was relying on is the ability to Ctrl+C on a file in the file manager, and to then Ctrl+V in a text editor/ text field to paste it's complete path. I sometimes copied a lot of files to clipboard and than pasted their paths into Kate, to then process the directories (like cut off the unnecessary bits of the path. I used also this to attach files to emails, or to copy file paths to terminal windows. After switching to KDE5 (Linux Mint 18) I've noticed I can no longer do this - I really miss this functionality, and I can't find a way to enable it. It this still possible in Dolphin? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 373142] Can't copy and paste file names
https://bugs.kde.org/show_bug.cgi?id=373142 unfa changed: What|Removed |Added Platform|Other |Mint (Ubuntu based) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 455710] New: Elisa truncates the end of a FLAC file
https://bugs.kde.org/show_bug.cgi?id=455710 Bug ID: 455710 Summary: Elisa truncates the end of a FLAC file Product: Elisa Version: 22.04.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: unf...@gmail.com Target Milestone: --- Created attachment 150002 --> https://bugs.kde.org/attachment.cgi?id=150002&action=edit Screenshot of Elisa after the playback stops automatically. I'm using Elisa on Windows 10. I've played a first track in FLAC format, and Elisa stops playback at 3:17, while the song is 3:19. It skips the last 2 seconds and I was unable to play them in any way using Elisa. Other audio playback software has no issue playing the file in full. STEPS TO REPRODUCE 1. Load a FLAC file as the only on the playlist 2. Play it without looping enabled until the end 3. Note the final playhead position vs the track length. OBSERVED RESULT The file is stopped 2 seconds short of the end. EXPECTED RESULT The whole file is played until the end. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION See the attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 456212] New: Error message on Windows 10 Login Screen
https://bugs.kde.org/show_bug.cgi?id=456212 Bug ID: 456212 Summary: Error message on Windows 10 Login Screen Product: kdeconnect Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: windows-application Assignee: piyushaggarwal...@gmail.com Reporter: unf...@gmail.com Target Milestone: --- Created attachment 150325 --> https://bugs.kde.org/attachment.cgi?id=150325&action=edit error message This problem occurred on Windows 10. After resuming from hibernation KDE Connect shown an error about a memory address not being accessible on top of the Windows Login screen. This has never happened before, I have no idea how to reproduce that, but wondered if anybody had the same problem. The application seems to be working regardless of the error message. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429312] New: Icons disapearing form icon-only task manager unless Caps Lock is enabled
https://bugs.kde.org/show_bug.cgi?id=429312 Bug ID: 429312 Summary: Icons disapearing form icon-only task manager unless Caps Lock is enabled Product: plasmashell Version: 5.20.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: unf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Some programs don't show in Icon-only Task manager, unless Caps Lock is enabled. STEPS TO REPRODUCE ? OBSERVED RESULT Video: https://youtu.be/b8XpraybRKw EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 81576] gmail.com or gmail.google.com say the browser's not supported
https://bugs.kde.org/show_bug.cgi?id=81576 unfa changed: What|Removed |Added CC||unf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 432272] New: Gmail refuses to log me in saying the browser is unsupported
https://bugs.kde.org/show_bug.cgi?id=432272 Bug ID: 432272 Summary: Gmail refuses to log me in saying the browser is unsupported Product: Falkon Version: 3.1.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: now...@gmail.com Reporter: unf...@gmail.com Target Milestone: --- Created attachment 135277 --> https://bugs.kde.org/attachment.cgi?id=135277&action=edit Screenshot showing Gmail refusing to log me in in Falkon (in Polish). SUMMARY STEPS TO REPRODUCE 1. Open Gmail.com 2. Attempt to log in 3. Fail OBSERVED RESULT Browser is declared unspported. EXPECTED RESULT Logging in. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux, KDE edition (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434938] New: Blur Filter Layers break on seams in Wrap Around Mode
https://bugs.kde.org/show_bug.cgi?id=434938 Bug ID: 434938 Summary: Blur Filter Layers break on seams in Wrap Around Mode Product: krita Version: 4.4.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: unf...@gmail.com Target Milestone: --- Created attachment 137058 --> https://bugs.kde.org/attachment.cgi?id=137058&action=edit Blur Layer doesn't work with Wrap Around Mode SUMMARY Filter Layers using Blur are not seamless, when using Wrap Ardoun Mode. STEPS TO REPRODUCE 1. Create a new document from a 1K texture template 2. Enable Wrap Around Mode 3. Add a Gaussian Blur or Blur Filter Layer 4. Paint across the image border OBSERVED RESULT The Blur creates visible seams on the image border, breaking the wraparound effect. EXPECTED RESULT The blur should repeat seamlessly across image borders. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.12.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I know this was reported and supposedly fixed before, but I think it's a regression. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 393802] New: GUI freezes as soon as I click somewhere
https://bugs.kde.org/show_bug.cgi?id=393802 Bug ID: 393802 Summary: GUI freezes as soon as I click somewhere Product: kdenlive Version: 18.04.0 Platform: Mint (Debian based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: unf...@gmail.com Target Milestone: --- I've tried using the 18.4.0 AppImage from the official website. When I run it, it seems to work fine , but then I click in the timeline it stops responding at all. It doesn't crash though, I have to manually kill it. I've run it in gdb, here's the output: (process:28117): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/app././/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory [producer_xml] failed to load filter "ladspa.1904" [producer_xml] failed to load filter "ladspa.1913" [producer_xml] failed to load filter "ladspa.1904" [producer_xml] failed to load filter "ladspa.1913" QXcbConnection: XCB error: 3 (BadWindow), sequence: 1679, resource id: 25171069, major code: 40 (TranslateCoords), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 4075, resource id: 25171097, major code: 40 (TranslateCoords), minor code: 0 ^C Program received signal SIGINT, Interrupt. 0x776ac07a in __GI___waitpid (pid=-1, stat_loc=0x7fffd5a0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 29 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. (gdb) threall apply all bt Undefined command: "threall". Try "help". (gdb) thread apply all bt Thread 1 (process 28072): #0 0x776ac07a in __GI___waitpid (pid=-1, stat_loc=0x7fffd5a0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 #1 0x0044706d in ?? () #2 0x0044854b in wait_for () #3 0x004384bf in execute_command_internal () #4 0x0043851e in execute_command () #5 0x0042139e in reader_loop () #6 0x0041fdb1 in main () (gdb) When I've run it without gdb the last message in the terminal was always something similar to this: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1679, resource id: 25171069, major code: 40 (TranslateCoords), minor code: 0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 393802] GUI freezes as soon as I click somewhere
https://bugs.kde.org/show_bug.cgi?id=393802 --- Comment #1 from unfa --- I've realized that this also affected older Kdenlive version I have installed, and after reboot the problem went away. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375500] New: Very high CPU usage, goes away after restarting the process
https://bugs.kde.org/show_bug.cgi?id=375500 Bug ID: 375500 Summary: Very high CPU usage, goes away after restarting the process Product: krunner Version: 5.6.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: unf...@gmail.com Target Milestone: --- I've found that krunner sometimes eats all of the available CPU time. It also spawns a dozen of threads as htop shows. If I kill it and restart, everything's back to normal (CPU usage 0.0% and 3 threads). No idea what triggers that though. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389220] New: "alphain" transition doesn't work
https://bugs.kde.org/show_bug.cgi?id=389220 Bug ID: 389220 Summary: "alphain" transition doesn't work Product: kdenlive Version: 17.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: unf...@gmail.com Target Milestone: --- I use an alphain transition (as compositor basically) to use a grayscale image on one track as an alpha mask for video underneath - this way I can achieve a nice composit of two videos. In Kdenlive 17.04.3 it works. In kdenlive 17.12.0 it doesn't work any more. Another effects seem to work fine, but this one that I need so much doesn't. I don't know of another way to achieve this effect in Kdenlive and it's key to do what I want to do. I tried everything for hours and came up with "alphain". I know I could use multiply with an inverted mask on the background and multiply with non-inverted mask on the foreground and then add both together. However that adds more layers to achieve the same effect and probably also will hit the rendering performance. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389220] "alphain" transition doesn't work
https://bugs.kde.org/show_bug.cgi?id=389220 unfa changed: What|Removed |Added CC||unf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368303] Crash when resizing clip
https://bugs.kde.org/show_bug.cgi?id=368303 unfa changed: What|Removed |Added CC||unf...@gmail.com --- Comment #5 from unfa --- Created attachment 109164 --> https://bugs.kde.org/attachment.cgi?id=109164&action=edit Full GDB output with backtrace and system info -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368303] Crash when resizing clip
https://bugs.kde.org/show_bug.cgi?id=368303 --- Comment #6 from unfa --- I think I might have the same bug. I have a bunch of tracks with clips synced together (4 video clips and an audio clip). There's an SVG mask on one track that uses a transition to apply the mask to a video clip. When I move the start point of one of the tracks to the left, revealing more material that I have trimmed off before - Kdenlive crashes, always on the same length. I uploaded a complete GDB output with thread apply all bt and system information. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368303] Crash when resizing clip
https://bugs.kde.org/show_bug.cgi?id=368303 --- Comment #7 from unfa --- In the freeze frame I see that my clips were resized beyond their initial length. Kdenlive didn't stop me when I reached the end of the clip when I was zoomed out and crashed, because it allowed the clip to be longer than the assigned video file (I guess). When I did it slowly while zoomed-in, Kdenlive stopped resizing the clip when I reached the input file start boundary, and didn't crash. I resized the rest of the files with no crash! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387655] New: "Disable Clip" affects all clips in a group, even when user selected just one
https://bugs.kde.org/show_bug.cgi?id=387655 Bug ID: 387655 Summary: "Disable Clip" affects all clips in a group, even when user selected just one Product: kdenlive Version: 17.04.3 Platform: Mint (Debian based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: unf...@gmail.com Target Milestone: --- I synced and grouped multicam footage to then do my cuts and choose angles by disabling unneeded clips in the timeline. The problem is - every time I try to do this, all clips in the group react. The clips that were disabled, become enabled, and the clips that were enabled become disabled. I select an individual clip in the group by holding Ctrl and using Left Mouse Button. My selected clip highligths, but the rest of the group remains unselected. however when I use a hotkey or the context menu to Disable the selected clip, all clips react as if I selected them all, which I haven't. To get this to work properly I have to ungroup my clips, but then I risk breaking the sync and messing up badly. I tried installing a newer version of Kdenlive from the PPAs to test this, but I couldn't. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 297666] split view: active window is closed when disabling split view
https://bugs.kde.org/show_bug.cgi?id=297666 unfa changed: What|Removed |Added CC||unf...@gmail.com --- Comment #6 from unfa --- Since this is a wontfix, could there be an option added in the Dolphin configuration to make it close the inactive view instead of the active one? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385772] New: Various windows randomly stop redrawing (unless I move them)
https://bugs.kde.org/show_bug.cgi?id=385772 Bug ID: 385772 Summary: Various windows randomly stop redrawing (unless I move them) Product: plasmashell Version: 5.8.7 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: unf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 A few weeks ago I started seeing a strange problem on two remote PCs in different locations, built from different components that run Linux Mint 18.2 with KDE 5. Both use Nvidia GPUs, one has an Intel processor and uses it's IGPU for desktop, the other has a Ryzen processor and uses Nvidia or display. Some Windows randomly stop redrawing. They will redraw if I move them around the screen, but as soon as I stop moving them, they'll freeze again. The only way to get the program to work back again is restarting it. Programs seem to recieve keyboard input and respond o it, but can't refresh their windows. Most often this causes my Plasma Panel to not refresh, and flip between two frames back and forth in a glitched-out manner. Other programs that are affected are: Ardour, Firefox and LMMS (happened once so far). I didn't have that happen to Blender or Inkscape (and I use these a lot too). So there is clearly something that relates to the way the application handles display, and if it's affected. The problems started in similar time period on two machines, so I suspect a recent update must have broken something. I keep both systems updated almost daily, but the problem persists on both machines. The strangest thing is if I move the affected window around the screen it'll refresh for every frame that it's position changed. I work a lot in Ardour with 2 windows (Editor and Mixer) opened - often one will be affected, but not the other, no real rule which one and when however, this seems completely random. PS: I've reported this problem on Linux Mint forums first but maybe this is a better place. (here's the original post: https://forums.linuxmint.com/viewtopic.php?f=56&t=255375&p=1376381#p1376381 ) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 373507] New: Plasma Panel keeps resetting to "Windows go Below"
https://bugs.kde.org/show_bug.cgi?id=373507 Bug ID: 373507 Summary: Plasma Panel keeps resetting to "Windows go Below" Product: kde Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: unf...@gmail.com Target Milestone: --- I once have set a panel to use "Windows go below" instead of "Always visible" and now every time my desktop loads - the panel uses "Windows go below". It forgets that I change it to "Always visible" and I have to change this every time I reboot or logout/login. I use a laptop with external display - the main display panel was once set to "Auto-hide" but remebered when I have changed it back to "Always visible". The secondary display however is stuck with "Windows go below" and I can't get it to remember anything else. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373635] New: Panel popups display on the other monitor
https://bugs.kde.org/show_bug.cgi?id=373635 Bug ID: 373635 Summary: Panel popups display on the other monitor Product: plasmashell Version: 5.6.5 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: unf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I use a dual-screen setup at work. Both screens have panels with a task manager and a clock. When I click on the clock on my right screen, the calendar pop-up shows up on the left screen (near the right edge). When I hover my mouse over a task on the Task Manager on the right screen - the window preview shows up on the left screen (near the left edge). The screns are identical AOC displays, connected to a DVI and DisplayPort. In the Display Configuratio, the left one shows up as a HDMI3, the right as HDMI2. What's weird: the right screen is set as the primary display in Display Configuration - why the panel pup-ups that should appear there are shown on the "secondary" screen on it's left? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373636] New: Display configuration is lost after restart
https://bugs.kde.org/show_bug.cgi?id=373636 Bug ID: 373636 Summary: Display configuration is lost after restart Product: plasmashell Version: 5.6.5 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: unf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I use two identical monitors at work. Each has it's own panel and widgets. After a reboot they are being set to cloned output - same image on both monitors, and every time I need to restore my configuration manually, move around the panels and widgets to get back to the point where I was before rebooting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373786] New: Secondary display's panel is misplaced after disconnecting it - assignig panels and widgets to display devices?
https://bugs.kde.org/show_bug.cgi?id=373786 Bug ID: 373786 Summary: Secondary display's panel is misplaced after disconnecting it - assignig panels and widgets to display devices? Product: plasmashell Version: 5.6.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: unf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I use a laptop with an external monitor. When I disconnect the external monitor, the panel that I placed there jumps back onto my primary display - covering the panel that's already there. To access my primary display's panel, I have to move the secondary display's panel away - I usually put it on top of the screen. They both have task managers (showing only their current screen's task). I would like to have the panel for the secondary monitor remain hidden and show itself up only when I connect the secondary monitor - and to hide itself again when I disconnect it, instead of cramming itself on my other monitor. Right now when I connect the secondary monitor again I have to manually move the secondary panel there. --- A slightly dodgy feature requestish part (Sorry if this is not a good place for such ideas. Please let me know where shold I got to discuss such matters if so): Would it be possible to make sure that some panels and widgets are assigned to a particular physical display, and will only be presented when that particular device is connected? For example I might not want the stuff I put on a secondary monitor to show up on a projector if I connect it. Accessing, reviewing and modifying panels and widgets assigned to particular display devices could be helpful - for example if I configured a panel for a particular monitor, but I'd want to copy it to another monitor (but I don't have access to the previous device that was assigned to that panel). Maybe a matrix of panels and widgets with a checklist of currently and previously connected display devices and/or categories (monitors, TVs, projectors etc) would be good? The user could easily assign what should be displayed where. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373836] New: Cannot use more than 1 screen
https://bugs.kde.org/show_bug.cgi?id=373836 Bug ID: 373836 Summary: Cannot use more than 1 screen Product: plasmashell Version: 5.8.4 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: unf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I'm using a laptop with external monitor. I have internal laptop display - let's call it A. I have an external monitor connected via VGA - let's call it B. I had severe problems with using the external monitor with Plasma 5.6.4. Now I upgraded to 5.8.4 and initially I thought my problems are gone - I connected B - it was on, with it's own panel there. I disconnected B - it was off, the B's panel was hidden, not falling back onto A, covering it's panel. Great! I suspened and restored the machine - now the problems are even worse. I reid rebooting - no luck. I am unable to use two monitors at the same time now after the upgrade. When I run the laptop with B unconnected, A is running fine. As soon as I connect B, A goes off. Panel and windows from A move to B, and now B is my only display. When I disconnect B, A goes back on and the panel and windows go back to A. In Plasma 5.6.4 I was able to finally get both A and B working by reconnecting B several times and reopening the Display Configuration several times. Now it doesn't help - I can never have both A and B on at the same time. After connecting B I open the Display Configuration and I can see B enabled there, and A disabled - I enable A and hit Apply. As a result B is on, but goes all black and I only see the mouse cursor on it, while A is still off - not just black, there's no backlight. I'm recovering my system to a state before upgrade to be able to use both screens again. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 373636] Display configuration is lost after restart
https://bugs.kde.org/show_bug.cgi?id=373636 --- Comment #2 from unfa --- I'm reporting the problems using two different machines - a laptop and a desktop both running Linux Mint 18 KDE5 64-bit. I can't tell if the issue is gone. I had other problems so I'm not staying with the newer Plasma for production right now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374862] New: Cannot place windows on the second screen
https://bugs.kde.org/show_bug.cgi?id=374862 Bug ID: 374862 Summary: Cannot place windows on the second screen Product: plasmashell Version: 5.6.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: unf...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 When I drag a window from the first screen ot the second one - it finally snaps back to the first screen. If a window opens on the second screen - once I start dragging it, it momentarily snaps back to the first screen. The only think I can do is drag the window so that it's over 50% on the second screen and then maximize the window - which maximizes it on the second screen. But trying to do anything else will snap the window back onto to first screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374862] Cannot place windows on the second screen
https://bugs.kde.org/show_bug.cgi?id=374862 --- Comment #2 from unfa --- No, each screen has it's own panel on the bottom - they are placed side-to-side. This has started randomly after a regular system power cycle. Didn't upgrade anything else than CUDA and nVidia drivers lately. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374862] Cannot place windows on the second screen
https://bugs.kde.org/show_bug.cgi?id=374862 --- Comment #4 from unfa --- Created attachment 103350 --> https://bugs.kde.org/attachment.cgi?id=103350&action=edit My desktop This is how my desktop looks. Trying to move a window forces the mouse to never cross the border between the monitors - the window itself can cross it though. I can maximize it on the right screen even, but not place it anywhere manually - the mouse will snap back to the left screen's right edge. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374862] Cannot place windows on the second screen
https://bugs.kde.org/show_bug.cgi?id=374862 --- Comment #5 from unfa --- I uploaded "My desktop" PNG image. I tried placing the panels on outer vertical edges of my screens (away from the middle) - but the window moving behaviour didn't change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374862] Cannot place windows on the second screen
https://bugs.kde.org/show_bug.cgi?id=374862 --- Comment #7 from unfa --- I have found a solution! Changing the Primary Display in Display Configuration seems to have fixed the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369614] New: Inkscape Icons are hard to distinguish and break common standards
https://bugs.kde.org/show_bug.cgi?id=369614 Bug ID: 369614 Summary: Inkscape Icons are hard to distinguish and break common standards Product: Breeze Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: unf...@gmail.com CC: kain...@gmail.com I'm using Mint 18 KDE 5 64-bit. 1. The Color Picker icon resembles a Blur Tool icon from GIMP - why break the convention of using an eyedropper symbol? 2. Layer stack - layer visibility icon - the standard for this is an open/closed eye symbol. The current icon represents stack of layers, and become crossed over when a layer is hidden - please get back to eye symbol. 3. Spiral tool icon - it has a strange double edged path drawn there? Why not a single-edged but maybe a wider stroke instead? 4. Path corners and endings icons - again, the double-edge of the drawn curvers make it unreadable, also the knee is very small, I can hardly see any difference between the corner type icons. The differences are hardly visible. 5. Bounding box snapping modes icons - they are readable, but also the differences are minute and very hard to notice at first glance. The green square is so tiny and the color blends with the bright background making it difficult to spot. (that's also a problem I have with Synaptic icons used for package state (Installed/Updatable/Install/Update/Remove etc. - they differ so slightly I need to stare for 2 seconds each time to know if a package is already installed or not.) I have many years of experience working with Inkscape and it's an essential part of my daily job but this icon set makes me feel like I'm just making my first steps. The usability was sacrificed for aesthetics in my opinion, and my productivity is badly reduced because I can't recognize the tools and buttons that were always there. For example GIMP installed and is using it's own icon set - and I have no problem with that. But I can't force Inkscape to fall back to the default icon set and that's really frustrating, especially when some tools have been given icons that break standards so baldy like the eyedropper replaced with an ink droplet. I know it looks cool, but it makes me work 5 times slower. Reproducible: Always Actual Results: An experienced user feels lost in the Inkscape GUI, becasue of the new icon set, not resembling the standard set. Expected Results: The Inkscape icons may be stylized t fit the overall system theme, but without altering them beyond recognition. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369614] Inkscape Icons are hard to distinguish and break common standards
https://bugs.kde.org/show_bug.cgi?id=369614 unfa changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369614] Inkscape Icons are hard to distinguish and break common standards
https://bugs.kde.org/show_bug.cgi?id=369614 --- Comment #2 from unfa --- (In reply to andreas from comment #1) > 5. Bounding box snapping modes icons > I NEVER, NEVER understood the bounding box icons from inkscape. As I have > some years of experience in AutoCAD I had a look at there icons. I understand this, but I for example learned these icons, knowing no AutoCad and the change is difficult for me to see what is what. Maybe more poeple can relate to that. I have more suggestions: The Add/Remove path node icons are totally different. I'd make them identical, but give one a green + symbol and the other one a red - (minus) symbol. -- You are receiving this mail because: You are watching all bug changes.
