[kde] [Bug 473683] SDDM Mixes seats in multi-seat setup (Failed to create session: TTY tty1 is virtual console but seat seat1 is not seat0)
https://bugs.kde.org/show_bug.cgi?id=473683 --- Comment #4 from dimanne --- It has been reported 4 times so far: * Jul 14: https://github.com/sddm/sddm/issues/1762 (SDDM 0.20.0 fails to create session in multi-seat configuration) * Jul 23: https://github.com/sddm/sddm/issues/1769 (SDDM doesn't seem to handle starting Wayland sessions on seats without VTs well) * Aug 3: https://github.com/sddm/sddm/issues/1778 (Wayland multiseat) * today by me: https://github.com/sddm/sddm/issues/1786 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473683] SDDM Mixes seats in multi-seat setup (Failed to create session: TTY tty1 is virtual console but seat seat1 is not seat0)
https://bugs.kde.org/show_bug.cgi?id=473683 --- Comment #2 from dimanne --- Sorry, yes, it is SDDM issue. I guess it does not have anything to do with KDE... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473683] New: SDDM Mixes seats in multi-seat setup (Failed to create session: TTY tty1 is virtual console but seat seat1 is not seat0)
https://bugs.kde.org/show_bug.cgi?id=473683 Bug ID: 473683 Summary: SDDM Mixes seats in multi-seat setup (Failed to create session: TTY tty1 is virtual console but seat seat1 is not seat0) Classification: I don't know Product: kde Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: causal.consiste...@proton.me Target Milestone: --- # SUMMARY It looks like login session from a second seat does get initialised properly. ### This is what I observe: Only one session is reported by loginctl: Only one session is detected ``` loginctl list-sessions SESSION UID USERSEAT TTY 4 1000 dimanne seat0 tty2 1 sessions listed. ``` Directory `/run/user/1001` is not created. `DBUS_SESSION_BUS_ADDRESS` of the second user is empty. systemctl --user list-units prints: ``` Failed to connect to bus: No medium found ``` Finally, `loginctl session-status` says: ``` Could not get properties: Unknown object 'org/freedesktop/login1/session/auto' ``` ### Why it happens I think this happens because sddm failed to properly initialise login session. This is how sddm logs look for "good" login: ``` Aug 20 09:52:17 impedance sddm[8212]: Authentication for user "dimanne" successful Aug 20 09:52:17 impedance sddm-greeter[8590]: Message received from daemon: LoginSucceeded Aug 20 09:52:17 impedance sddm-helper[9033]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred Aug 20 09:52:17 impedance sddm-helper[9033]: pam_limits(sddm:session): Could not set limit for 'nofile' to soft=16777216, hard=16777216: Operation not permitted; uid=0,euid=0 Aug 20 09:52:17 impedance sddm-helper[9033]: pam_unix(sddm:session): session opened for user dimanne(uid=1000) by (uid=0) Aug 20 09:52:17 impedance sddm-helper[8362]: [PAM] Closing session Aug 20 09:52:17 impedance sddm-helper[8362]: pam_unix(sddm-greeter:session): session closed for user sddm Aug 20 09:52:17 impedance sddm-helper[8362]: [PAM] Ended. Aug 20 09:52:17 impedance sddm[8212]: Auth: sddm-helper exited successfully Aug 20 09:52:17 impedance sddm[8212]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS Aug 20 09:52:17 impedance sddm-helper[9033]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session Aug 20 09:52:17 impedance sddm-helper[9078]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket Aug 20 09:52:17 impedance sddm-helper[9033]: pam_env(sddm:session): deprecated reading of user environment enabled Aug 20 09:52:17 impedance sddm-helper[9033]: Writing cookie to "/tmp/xauth_vDhCDz" Aug 20 09:52:17 impedance sddm-helper[9033]: Starting X11 session: "" "/etc/sddm/Xsession \"/usr/bin/startplasma-x11\"" Aug 20 09:52:17 impedance sddm[8212]: Session started true Aug 20 12:27:05 impedance sddm-greeter[8534]: Reading from "/usr/share/xsessions/plasma.desktop" ``` And this is how they look for 2nd seat ``` Aug 20 12:27:05 impedance sddm[8212]: Authentication for user "yulia" successful Aug 20 12:27:05 impedance sddm-greeter[8534]: Message received from daemon: LoginSucceeded Aug 20 12:27:05 impedance sddm-helper[56829]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred Aug 20 12:27:05 impedance sddm-helper[56829]: pam_limits(sddm:session): Could not set limit for 'nofile' to soft=16777216, hard=16777216: Operation not permitted; uid=0,euid=0 Aug 20 12:27:05 impedance sddm-helper[56829]: pam_unix(sddm:session): session opened for user yulia(uid=1001) by (uid=0) Aug 20 12:27:05 impedance sddm-helper[56829]: pam_systemd(sddm:session): Failed to create session: TTY tty1 is virtual console but seat seat1 is not seat0 Aug 20 12:27:05 impedance sddm-helper[56829]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session Aug 20 12:27:05 impedance sddm-helper[56832]: pam_kwallet5: final socket path: /tmp/kwallet5_yulia.socket Aug 20 12:27:05 impedance sddm-helper[56829]: pam_env(sddm:session): deprecated reading of user environment enabled Aug 20 12:27:05 impedance sddm-helper[56829]: Writing cookie to "/tmp/xauth_MzDsqA" Aug 20 12:27:05 impedance sddm-helper[56829]: Starting X11 session: "" "/etc/sddm/Xsession \"/usr/bin/startplasma-x11\"" Aug 20 12:27:05 impedance sddm[8212]: Session started true Aug 20 12:27:05 impedance sddm-helper[8399]: [PAM] Closing session Aug 20 12:27:05 impedance sddm-helper[8399]: pam_unix(sddm-greeter:session): session closed for user sddm Aug 20 12:27:05 impedance sddm-helper[8399]: [PAM] Ended. Aug 20 12:27:05 impedance sddm[8212]: Auth: sddm-helper exited successfully Aug 20 12:27:05 impedance sddm[8212]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS ``` STEPS TO REPRODUCE 1. Create two seats 2. Login 1st seat. 3.
[kwin] [Bug 444261] Wayland is unusable
https://bugs.kde.org/show_bug.cgi?id=444261 --- Comment #3 from DimanNe --- Thank you for the quick reply. Yes, probably it is a duplicate. But what about font rendering & scaling? If you are interested as to why it is important: There is this use-case when you have two displays of different _physical_ size (32 inches and 27 inches, for example), but the _same_ _resolution_. So, if you do not make any tweaks, the same character (GUI element) has different size on one display and the other. So, the only solution is to scale one of them. And that is where we are starting to have huge problems - check my "problems with fonts" screenshot - they are very blurry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444261] Wayland is unusable
https://bugs.kde.org/show_bug.cgi?id=444261 DimanNe changed: What|Removed |Added CC||dima...@gmail.com --- Comment #1 from DimanNe --- Created attachment 142785 --> https://bugs.kde.org/attachment.cgi?id=142785=edit problems with fonts Another attachment where problems with fonts are visible much better -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444261] New: Wayland is unusable
https://bugs.kde.org/show_bug.cgi?id=444261
Bug ID: 444261
Summary: Wayland is unusable
Product: kwin
Version: 5.23.1
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: dima...@gmail.com
Target Milestone: ---
Created attachment 142784
--> https://bugs.kde.org/attachment.cgi?id=142784=edit
upside down
SUMMARY
(you can see most of the issues described below on the screenshots)
* There are various artefacts:
* text shown upside down with 4x scale (see upside_down_wayland.png)
* some windows become filled with black colour permanently (see
upside_down_wayland.png)
* some windows become filled with black colour temporarily (for ~0.1s)
while resizing.
* duplicate content of a window flashing in a random place (for ~0.1s)
* It is very slow:
* When I move a window I can see how it is shown in one place, then in
~0.3s it is shown where the cursor is. It is like fps = 3 (instead of usual
60-100).
* Open and play any 4k 60fps Youtube video in Chrome in full screen, then
open "Stats for nerds" (right click on video and click "Stats for nerds") and
you will see that approximately HALF of all frames is dropped.
* Text is extremely blurry when display is scaled (it looks and feels as if
scale was implemented as jpg scale, instead of rendering image with different
settings/dpi/whatever).
* Also, some characters in text missing parts ("i" does not have the dot).
* The panel at the bottom disappears (see upside_down_wayland.png)
A couple more words about upside_down_wayland.png - one of the windows is
Firefox, the other is System settings (but for some reason it displays parts of
Konsole...)
STEPS TO REPRODUCE
1. Just try using it for about 5-10 min.
OBSERVED RESULT
See the attachments.
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-20-generic (64-bit)
Graphics Platform: X11# < I am reporting this bug in X session.
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 125.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 417013] New terminals in split screen seem to be treated as a new tab
https://bugs.kde.org/show_bug.cgi?id=417013 --- Comment #9 from DimanNe --- Yes, you are right. Thank you for the video, I did not realise that I **can** move splits from one tab to another. It answers my question and solves my issue. Sorry for bothering. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 417013] New terminals in split screen seem to be treated as a new tab
https://bugs.kde.org/show_bug.cgi?id=417013 --- Comment #6 from DimanNe --- To me it should have never been done. But at least there should be an option to restore the old behaviour. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 417013] New terminals in split screen seem to be treated as a new tab
https://bugs.kde.org/show_bug.cgi?id=417013 --- Comment #5 from DimanNe --- (In reply to Nate Graham from comment #1) > Keeping this open to gather feedback about the change. Ok, I realised how I can try to *prove* that it was a totally wrong change. Entire purpose of having splits (anywhere, your IDE, console, whatever) is being able to **COLLOCATE** different contexts (panes/tasks/outputs). The problem is that the current behaviour has almost zero capacity for achieving this. Imagine I have an existing split (split1 at the top, split2 at the bottom). Imagine now I want to open another split3. I can either open split in the existing tab (but it means it will be a 3rd split, and it will be too small, and therefore I cannot do it forever), or (eventually) I will need to open another tab. Now, how can I achieve the task of collocating the splits? For example I want to bring split1 next to split3, what do I do? With previous behaviour I could do it easily. Now it is impossible. Does it make sense? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 419370] [regression] New tab does not create tab in a view
https://bugs.kde.org/show_bug.cgi?id=419370 DimanNe changed: What|Removed |Added CC||kurt.hindenb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 419370] [regression] New tab does not create tab in a view
https://bugs.kde.org/show_bug.cgi?id=419370 DimanNe changed: What|Removed |Added CC||tcanabr...@kde.org --- Comment #2 from DimanNe --- *perhaps* it is this commit - https://cgit.kde.org/konsole.git/commit/?id=6e8153a78e3c63e514a6ecb62f6c9b4b504e7eb7 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 419370] [regression] New tab does not create tab in a view
https://bugs.kde.org/show_bug.cgi?id=419370 --- Comment #1 from DimanNe --- P.S. It is so annoying that I am fine with the option of recompiling Konsole from sources with the commits (that introduced this behaviour) reverted. So if the change was intentional, can you please share which commits it were? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 419370] New: [regression] New tab does not create tab in a view
https://bugs.kde.org/show_bug.cgi?id=419370 Bug ID: 419370 Summary: [regression] New tab does not create tab in a view Product: konsole Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split-view Assignee: konsole-de...@kde.org Reporter: dima...@gmail.com Target Milestone: --- SUMMARY Today I upgraded to Kubuntu 20.04 (beta) and discovered that "New Tab" and "Split View" features interaction has been drastically changed (looks like a regression). The problem is that it has become impossible to open tab *in* a view. On the contrary, I can only split views in different tabs. STEPS TO REPRODUCE 1. Open Konsole 2. Split view (View -> Split View -> Split view Top/Bottom) 3. Try to open a tab in the current view (File -> New Tab) OBSERVED RESULT New tab is opened, but there is no previously created views (in step 2), instead it is just new completely blank space without the views I have create at the second step. EXPECTED RESULT A new tab is opened in an *existing* view. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.5 Kernel Version: 5.4.0-18-generic OS Type: 64-bit Processors: 6 × , 6 × Intel® Core™ i7-8700K CPU @ 3.70GHz Memory: 62.7 GiB of RAM ADDITIONAL INFORMATION I will be happy to any workaround... The new behaviour makes me switch the context/attention frequently. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402939] Annotation workflow is completely broken
https://bugs.kde.org/show_bug.cgi?id=402939 --- Comment #2 from DimanNe --- Yes, I can. Do you know where exactly in code I can start to look? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402939] New: Annotation workflow is completely broken
https://bugs.kde.org/show_bug.cgi?id=402939 Bug ID: 402939 Summary: Annotation workflow is completely broken Product: okular Version: 1.4.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: dima...@gmail.com Target Milestone: --- I wanted to add my signature (image, not cryptographic one) into a pdf document. So I decided to use the Annotation feature of Okular, found that Stamp was what I looking for. Here was the first problem - it is completely impossible (from the given interface) to understand how I am supposed to add my own image in the list of available stamps. Well, after some googling I found your help (which is wrong, actually): https://docs.kde.org/trunk5/en/kdegraphics/okular/configannotations.html Using Custom Stamps * Create the icon you want to use for your own stamp and save it in any graphics format supported by Okular * Click the Add button, select type Stamp and enter a name for your stamp. * Enter the full path to your custom icon into the dropdown box in the Stamp Symbol group My path was "/home/dimanne/Downloads/DimanNeSignature.png" - it did not work. After more googling I found out that I should have somehow understood that the path must be in lowercase - https://superuser.com/a/1325085/981679 At least, you should have written it in the help, instead of making people debug Okular with strace. Well, after renaming to lowercase I managed to get it on my PDF (it is still ugly since you downscale it drastically and it looks distorted, but anyway, it was passable). Finally, I have went all the path only to know that the signature can not be saved in resulting (annotated) PDF - https://bugs.kde.org/show_bug.cgi?id=383651 What is wrong with Okular? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364509] Applications window disappears while dragging them through Desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=364509 --- Comment #13 from DimanNe --- Any progress? The bug is still here... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 --- Comment #74 from DimanNe <dima...@gmail.com> --- > As you can see this is a long standing issue dating back to 2011. If we > could apply a workaround, we would have done it years ago. The current > situation is that: > * X11 will not see any more features > * Wayland lacks Activity support in general Well, of course, it is wiser to invest resources in improving and supporting shiny new wayland instead of obsolete XOrg, which is in its senectitude. > Unfortunately we don't have activities support yet as there is no clear > understanding on where to go with activities from window management > perspective and how they relate to virtual desktops. While it is not too late, as a KDE user, I would suggest that the current relation of activities to virtual desktops is convenient. The fact that I have separate set of virtual desktops in each activity totally corresponds to my workflow. Anyway, thanks for the clarification. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 DimanNe <dima...@gmail.com> changed: What|Removed |Added CC||dima...@gmail.com --- Comment #71 from DimanNe <dima...@gmail.com> --- I have started using activities and stumbled upon this issue too. Any progress or (at least) workarounds? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388276] New: KWin crashes with an nvidia card and proprietary drivers (Xid 31)
https://bugs.kde.org/show_bug.cgi?id=388276 Bug ID: 388276 Summary: KWin crashes with an nvidia card and proprietary drivers (Xid 31) Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: dima...@gmail.com Target Milestone: --- kwin_x11 crashes (and all the desktop effects are disabled). I am using this card: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1) and this drivers: $ dpkg -l | grep nvidia | tr -s ' ' ii nvidia-384 384.90-0ubuntu3.17.10.1 amd64 NVIDIA binary driver - version 384.90 Just after crashing I get this error message in dmesg: kernel: NVRM: Xid (PCI::01:00): 31, Ch 0020, engmask 0101, intr 1000 Here is description of what xid 31 means: http://docs.nvidia.com/deploy/xid-errors/index.html#topic_2 Restaring kwin in such a way: "$ kwin_x11 --replace&" helps $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 381905] The key sequence 'Home' is ambiguous
https://bugs.kde.org/show_bug.cgi?id=381905 DimanNe <dima...@gmail.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |WONTFIX Status|NEEDSINFO |RESOLVED --- Comment #6 from DimanNe <dima...@gmail.com> --- Well, I reinstalled Kubuntu and the bug is not being reproduced anymore, so, I suppose, it can be closed. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 381905] The key sequence 'Home' is ambiguous
https://bugs.kde.org/show_bug.cgi?id=381905 --- Comment #4 from DimanNe <dima...@gmail.com> --- Ok, here is another example of ambiguous shortcuts in Kate. When I press Shift+Ins (to paste text) I again got this message - https://drive.google.com/open?id=1A3s-2WpdLgJ1G1-PDAEAtCKjfFx21XD5 There is nothing wrong with shortcut settings in Kate settings - https://drive.google.com/open?id=1w3PxKyqxjEkxFUGJlEt5cbCgDiVVXYAk Also everything is find in System-wide Global shortcuts - https://drive.google.com/open?id=1wwlffmU1GZdbP1alpwfdATAS4wlxmWdQ But still I can't use it. Any ideas? My version is that there are probably several config files where this shortcut might be stored. This might be especially true in the light that I have not (completely) reinstalled my OS since 14.04 (almost 4 years) and you might broke some compatibility around shortcut settings. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 381905] The key sequence 'Home' is ambiguous
https://bugs.kde.org/show_bug.cgi?id=381905 --- Comment #1 from DimanNe <dima...@gmail.com> --- Forgot to add questions: 1. How it could happen? Who and when has assign another action on Home button? 2. How do I fix it? Versions of KDE components: plasma version 5.9.4 framework 5.31.0-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 381905] New: The key sequence 'Home' is ambiguous
https://bugs.kde.org/show_bug.cgi?id=381905 Bug ID: 381905 Summary: The key sequence 'Home' is ambiguous Product: krusader Version: 2.5.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: shortcuts Assignee: m...@fork.pl Reporter: dima...@gmail.com Target Milestone: --- When I try to open a text file for editing (F4 shortcut) and then press Home, I get the following message box: "The key sequence 'Home' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered" But when I try to solve the ambiguity by opening Settings-> Configure Shortcuts, then there is no such shortcut at all. Here is the first screenshot with message box - https://drive.google.com/open?id=0B4r5nJvpzEHGdWdlWFozVDdxaUU and the second example with all available shortcuts - https://drive.google.com/open?id=0B4r5nJvpzEHGdy1lRXN6MGYzbUE -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 377483] Huge repainting periodicity. Or clock does not show me every second.
https://bugs.kde.org/show_bug.cgi?id=377483 --- Comment #5 from DimanNe <dima...@gmail.com> --- By the way, here is another demonstration of the bug: https://drive.google.com/file/d/0B4r5nJvpzEHGZm9pSXRZV1RTRU0/view Look at task manager panel. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 377483] Huge repainting periodicity. Or clock does not show me every second.
https://bugs.kde.org/show_bug.cgi?id=377483 --- Comment #4 from DimanNe <dima...@gmail.com> --- KDE Plasma Version: 5.9.3 KDE Frameworks Version: 5.31.0 Qt Version: 5.7.1 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 377483] Huge repainting periodicity. Or clock does not show me every second.
https://bugs.kde.org/show_bug.cgi?id=377483 --- Comment #2 from DimanNe <dima...@gmail.com> --- 5.31.0-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 377483] New: Huge repainting periodicity. Or clock does not show me every second.
https://bugs.kde.org/show_bug.cgi?id=377483 Bug ID: 377483 Summary: Huge repainting periodicity. Or clock does not show me every second. Product: kdelibs Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kdecore Assignee: kdelibs-b...@kde.org Reporter: dima...@gmail.com Target Milestone: --- Here is video - https://drive.google.com/file/d/1kjaJ53ie0LaKz2W7fq_h8A-t3-B5E403pg/view. Watch for seconds. Digital clock show me every second or third second. If I force updating/repainting of the area by making KDE show popups, everything starts to work and every second is shown. Digital clock start misbehaving, as soon as I leave the area. Such behaviour occurs after relatively long uptimes. My current uptime is 5 days. My graphical card is GeForce GTX 650 Ti BOOST $ nvidia-smi Sat Mar 11 10:23:03 2017 +-+ | NVIDIA-SMI 375.39 Driver Version: 375.39| |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 650... Off | :01:00.0 N/A | N/A | | 10% 36CP8N/A / N/A | 1143MiB / 1996MiB | N/A Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 Not Supported | +-+ -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377329] [Regression] "Del" does not work anymore
https://bugs.kde.org/show_bug.cgi?id=377329 --- Comment #3 from DimanNe <dima...@gmail.com> --- My apologies, I overlooked the option. Everything is fine now. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377329] [Regression] "Del" does not work anymore
https://bugs.kde.org/show_bug.cgi?id=377329 DimanNe <dima...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377329] [Regression] "Del" does not work anymore
https://bugs.kde.org/show_bug.cgi?id=377329 DimanNe <dima...@gmail.com> changed: What|Removed |Added CC||dima...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377329] [Regression] "Del" does not work anymore
https://bugs.kde.org/show_bug.cgi?id=377329 --- Comment #1 from DimanNe <dima...@gmail.com> --- And if you try to delete everything in ~/.local/share/Trash/ manually, Krusader will tell you: Could not rename file /home/dimanne/.local/share/Trash/files. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377329] New: [Regression] "Del" does not work anymore
https://bugs.kde.org/show_bug.cgi?id=377329 Bug ID: 377329 Summary: [Regression] "Del" does not work anymore Product: krusader Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: shortcuts Assignee: m...@fork.pl Reporter: dima...@gmail.com Target Milestone: --- If you press Del, Krusader will MOVE files into Trash, instead of deleting them permanently. Shift+Del does not work as well (just nothing happens) I believe it is a regression, because before upgrading KUbuntu to 17.04 beta old Krusader worked perfectly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374853] New: kwin hangs on an attempt to trigger Show Desktop Grid effect
https://bugs.kde.org/show_bug.cgi?id=374853 Bug ID: 374853 Summary: kwin hangs on an attempt to trigger Show Desktop Grid effect Product: kwin Version: 5.8.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: dima...@gmail.com Target Milestone: --- kwin (and all desktop UI) had hanged just after I pressed Ctrl+F8 (Show Desktop Grid). It was eating 100% of CPU. The bug is not reproduced very often. I have encountered the bug just once, so far. perf top says this function Children SelfShared ObjectSymbol 29.20% 25.51% libQt5Core.so.5.6.1 [.] _ZNK11QMetaObject15indexOfPropertyEPKc eats 100% of CPU Here is backtrace (obtained with attached gdb): info threads Id Target Id Frame * 1Thread 0x7fb5d1e16940 (LWP 3310) "kwin_x11" 0x7fb5e6316a2b in QMetaObject::indexOfProperty(char const*) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 2Thread 0x7fb5d1e12700 (LWP 3328) "QDBusConnection" 0x7fb5e84fb0bd in poll () at ../sysdeps/unix/syscall-template.S:84 3Thread 0x7fb5cbfff700 (LWP 3346) "QXcbEventReader" 0x7fb5e84fb0bd in poll () at ../sysdeps/unix/syscall-template.S:84 4Thread 0x7fb5c890e700 (LWP 3551) "QQmlThread" 0x7fb5e84fcea3 in select () at ../sysdeps/unix/syscall-template.S:84 5Thread 0x7fb5b9459700 (LWP 3566) "kwin_x11" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 6Thread 0x7fb5b9c5a700 (LWP 6119) "QQmlThread" 0x7fb5e84fcea3 in select () at ../sysdeps/unix/syscall-template.S:84 backtrace #0 0x7fb5e6316a2b in QMetaObject::indexOfProperty(char const*) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fb5e633963b in QObject::property(char const*) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fb5e5adefc2 in KWin::EffectWindow::height() const () from /usr/lib/x86_64-linux-gnu/libkwineffects.so.9 #3 0x7fb5e563d575 in ?? () from /usr/lib/x86_64-linux-gnu/libkwin4_effect_builtins.so.1 #4 0x7fb5e563e819 in ?? () from /usr/lib/x86_64-linux-gnu/libkwin4_effect_builtins.so.1 #5 0x7fb5e5643dc1 in ?? () from /usr/lib/x86_64-linux-gnu/libkwin4_effect_builtins.so.1 #6 0x7fb5e561ac18 in ?? () from /usr/lib/x86_64-linux-gnu/libkwin4_effect_builtins.so.1 #7 0x7fb5e633ab49 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb5e5af0327 in KWin::EffectsHandler::windowGeometryShapeChanged(KWin::EffectWindow*, QRect const&) () from /usr/lib/x86_64-linux-gnu/libkwineffects.so.9 #9 0x7fb5e633abec in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb5e814af47 in KWin::Toplevel::geometryShapeChanged(KWin::Toplevel*, QRect const&) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #11 0x7fb5e802dabb in ?? () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #12 0x7fb5e802dc6b in ?? () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #13 0x7fb5e80313f3 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5 #14 0x7fb5e630a23f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fb5d1105c75 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #16 0x7fb5d1106c0b in QXcbConnection::processXcbEvents() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #17 0x7fb5e633b699 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fb5e6c488ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fb5e6c4dd4f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fb5e630d3b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fb5e630f33c in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fb5e6360b52 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fb5d117e94d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #24 0x7fb5e630b0fa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fb5e631390c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fb5e87cf206 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kwin_x11.so #27 0x7fb5e841f3f1 in __libc_start_main (main=0x55733fba17e0, argc=3, argv=0x7ffe63edc418,
[kwin] [Bug 374607] New: [Regression] Show Desktop Grid effect is broken
https://bugs.kde.org/show_bug.cgi?id=374607 Bug ID: 374607 Summary: [Regression] Show Desktop Grid effect is broken Product: kwin Version: 5.8.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: dima...@gmail.com Target Milestone: --- "Show Desktop Grid" effect (the effect which is triggered with Ctrl+F8 shortcut) is broken. 1) Just after I click a window and try to drag it (to another desktop for example) it instantly disappears. 2) Hovering over a window does not enlarge it anymore. 3) It seems that the size of dropped window is calculated incorrectly I recorded two videos: Working effect (kwin version is 5.5.5) - https://drive.google.com/file/d/0B4r5nJvpzEHGVWVLVTlzYm5pY3M/view?usp=sharing Not working effect (kwin version is 5.8.5) - https://drive.google.com/file/d/0B4r5nJvpzEHGamVDQnU5djRscHc/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373248] New: KWin crashes during switching from another session + distortions.
https://bugs.kde.org/show_bug.cgi?id=373248 Bug ID: 373248 Summary: KWin crashes during switching from another session + distortions. Product: kwin Version: 5.7.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: dima...@gmail.com Target Milestone: --- Application: kwin_x11 (5.7.5) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.8.0-28-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: - What I was doing when the application crashed: I was working in session of another account. And just prior to crash I switched to my account and logged in. The next thing I saw - was black background and window with crash report. - Unusual behavior I noticed: Almost every time I have more than one active (logged in) account, I see lock screen with distortions. See screenshots here - 1. https://drive.google.com/file/d/0B4r5nJvpzEHGM1FyUXBnZWUyVUk/view 2. https://drive.google.com/file/d/0B4r5nJvpzEHGMHBWNnZucW9Kc0E/view 3. https://drive.google.com/file/d/0B4r5nJvpzEHGWnh2Q1NmSlo0SEE/view And at this time I saw third screenshot. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f839d3fb900 (LWP 5099))] Thread 4 (Thread 0x7f83876fe700 (LWP 5194)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f83afb07574 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f83afb075b9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f83ac0c070a in start_thread (arg=0x7f83876fe700) at pthread_create.c:333 #4 0x7f83b2b240af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f838f7fe700 (LWP 5164)): #0 0x7f83b2b19ea3 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f83b099bcaf in qt_safe_select (nfds=14, fdread=fdread@entry=0x7f838a78, fdwrite=fdwrite@entry=0x7f838d08, fdexcept=fdexcept@entry=0x7f838f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7f83b099d754 in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7f838f98, writefds=0x7f838d08, readfds=0x7f838a78, nfds=, this=0x7f8388c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f8388e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7f83b099dc6a in QEventDispatcherUNIX::processEvents (this=0x7f8388c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7f83b09480fa in QEventLoop::exec (this=this@entry=0x7f838f7fdca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f83b076dd43 in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7f83ab21ec65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f83b0772c68 in QThreadPrivate::start (arg=0x557c2ee7b150) at thread/qthread_unix.cpp:341 #9 0x7f83ac0c070a in start_thread (arg=0x7f838f7fe700) at pthread_create.c:333 #10 0x7f83b2b240af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f839ce65700 (LWP 5111)): #0 0x7f83b2b180bd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f83a96219d6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f83a9621aec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f83b09a04ab in QEventDispatcherGlib::processEvents (this=0x7f83980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f83b09480fa in QEventLoop::exec (this=this@entry=0x7f839ce64c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f83b076dd43 in QThread::exec (this=this@entry=0x7f83b31a1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #6 0x7f83b312d575 in QDBusConnectionManager::run (this=0x7f83b31a1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:171 #7 0x7f83b0772c68 in QThreadPrivate::start (arg=0x7f83b31a1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:341 #8 0x7f83ac0c070a in start_thread (arg=0x7f839ce65700) at pthread_create.c:333 #9 0x7f83b2b240af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7f839d3fb900 (LWP 5099)): [KCrash Handler] #6 KWin::ContrastEffect::uploadRegion (this=this@entry=0x557c2f0ab870, map=@0x7ffe076ae3c8: 0x7f838c17e110, region=...) at ./effects/backgroundcontrast/contrast.cpp:259 #7 0x7f83afcbafd4 in
[plasmashell] [Bug 364061] plasmashell using 100% CPU time
https://bugs.kde.org/show_bug.cgi?id=364061 --- Comment #6 from DimanNe <dima...@gmail.com> --- One more observation. I have encountered this bug twice recently, and I managed to workaround this bug by erasing all user-specific config files of KDE -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364061] plasmashell using 100% CPU time
https://bugs.kde.org/show_bug.cgi?id=364061 --- Comment #4 from DimanNe <dima...@gmail.com> --- I have recently encountered this problem again at my notebook. System info: plasmashell 5.5.5 OS: Kubuntu 16.04 Also, I have two (physical) monitors, and I noticed this problem began to arise after I detached/attached notebook from dock station or after hibernation Backtraces, perf top: I ran "top -H" and it said there are two threads on my system, which are eating CPU - plasmashell and Xorg, so here is "hottest" backtraces of these threads collected with perf top -t 3136 -d 5 --call-graph dwarf (where 3136 is thread Id from top output) Thread of plasmashell - http://pastebin.com/GPMkrWz8 (see text after RAW Paste Data) Thread of Xorg - http://pastebin.com/ZH0x7F7i (see text after RAW Paste Data) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364061] plasmashell using 100% CPU time
https://bugs.kde.org/show_bug.cgi?id=364061 --- Comment #3 from DimanNe <dima...@gmail.com> --- No. No animations, no blinking icons at the time of CPU spike. By the way, I found workaround - I just cleared all kde settings (~/.kde, ~/.config/, ~/.local/share/) and the problem has gone. All is working perfectly now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364061] plasmashell using 100% CPU time
https://bugs.kde.org/show_bug.cgi?id=364061 DimanNe <dima...@gmail.com> changed: What|Removed |Added CC||dima...@gmail.com --- Comment #1 from DimanNe <dima...@gmail.com> --- Same for me. Bug report - https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1592668 Plasmashell thread http://pastebin.com/CZtfCq7m Xorg thread http://pastebin.com/eAi9Ua9N -- You are receiving this mail because: You are watching all bug changes.
